User:Skierpage/SMW/examples

General comments/TODOs

categorize more

People don't categorize pages on the wiki enough. Categorization is the best and easiest way to find pages in a wiki, a moment spent putting in anything that makes a query, Category:Makes semantic annotation in any template that does so, etc. will save someone else time later.

document

in the [[Property:My property name]] page say what your property is for, link to pages querying on it, link to templates and forms setting the property.

need a {{deleteme}} template

people create test properties and don't have the rights to get rid of them. The moment you realize the property isn't right, say so on its page, get rid of all use of it, and flag the page.

restrict early

• if you're going to limit a property to certain values, use [[Allows value::OK, At risk, delayed]]

  another way is to make the property's type Page, so that any new value will show up in red. This only makes sense if the property's values make sense as articles — a page titled At risk probably doesn't make sense, and a page titled Status/at risk is not going to display well in query results.

organize queries and pull them in

maybe pages with queries should separate them out into e.g. Semantic queries/Firefox features so they can be browse, and so generally useful ones can be transcluded on other pages. E.g. the queries on this page. Otherwise it's quite hard to find all pages that query on some property in order to fix them.

Firefox features

There are a lot of feature properties, here are the ones starting with "Feature"

• Feature accessibility lead
• Feature accessibility notes
• Feature accessibility review
• Feature accessibility status
• Feature additional members
• Feature dependencies
• Feature engineering notes
• Feature engineering status
• Feature engineering team
• Feature feature manager
• Feature functional spec
• Feature health
• Feature implementation notes
• Feature implementation plan
• Feature landing criteria
• Feature lead engineer
• Feature list
• Feature localization lead
• Feature localization notes
• Feature localization review
• Feature localization status
• Feature name
• Feature non-goals
• Feature open issues and risks
• Feature operations lead
• Feature operations notes
• Feature operations status
• Feature overview
• Feature priority
• Feature privacy lead
• Feature privacy notes
• Feature privacy review
• Feature privacy status
• Feature product manager
• Feature product marketing lead
• Feature product marketing notes
• Feature product marketing status
• Feature products notes
• Feature products status
• Feature project
• Feature qa lead
• Feature qa notes
• Feature qa review
• Feature qa status
• Feature rank
• Feature requirements
• Feature roadmap
• Feature secondary roadmap
• Feature security health
• Feature security lead
• Feature security notes
• Feature security review
• Feature security status
• Feature stage
• Feature status
• Feature status note
• Feature theme
• Feature users and use cases
• Feature ux design
• Feature ux lead
• Feature ux notes
• Feature ux status
• Feature version

Comments

• You can't get the strings "Firefox 8" and "Firefox 10" to sort correctly. This is another reason to move to versions like 2011.3 ;-) , which do sort properly so long as there are never more than 10 releases a year.
• Perhaps some of the properties should be limited to certain values (using Property:Allows value), such as "Feature health", "Feature ux status", etc.
• Related, maybe some of the properties should be of Type:Page, so that they link to a page (if it exists) rather than just a string. E.g. if Property:Feature version were of type page, then the page for Firefox 8 could show the features likely to be in it. (You want relevant queries on relevant pages, few people using the wiki will know how to make queries or use Special:Browse.)

A query for Firefox features' status

Look for Special:Feature version starting with Firefox*, sort on that, display some feature health fields. (Click Edit tab to see the ask: syntax.)

Nothing found with Feature version starting with "Firefox"

Event queries

There are a number of event properties, here are the ones starting with "event"

• Event Participated
• Eventattendance
• Eventdate
• Eventdays
• Eventdescription
• Eventenddate
• Eventname
• Eventowner
• Eventregion
• Eventstartdate
• Eventwebsite

Comments

• Property:eventstartdate and the other event properties are betterwrittenas separate words, same for all the event properties.
• eventstartdate should be a subproperty of a generic Property:Start date, so you can do a generic query for all upcoming things in the wiki.

A query for future events

Query for anything with eventstartdate or eventenddate in the future. (Click Edit tab to see the ask: syntax.)

Nothing found with an eventstartdate in the future?

People queries

It looks like someone changed a person template so that it the template parameter Surname: makes a Property:Surname annotation. This is great! a fantastic way to get existing info annotated.

Query on surnames

Anything with a surname, displaying all the properties possibly set by template {{Remobox}}