Semantic MediaWiki/Activities

More details on some of the ideas in Semantic MediaWiki/#For activities

Unify the OBX box and semantic properties

A typical activity like Colors! uses the following Category:OBX templates

Template:Olpcboxtop

{{olpcboxtop|toptext=[[{{PAGENAME}}|Colors!]]}}

• toptext param is just the Semantic MediaWiki/Activities, alt text is unneeded unless overridden

Template:OBX activity

Pulls in Template:OBX boilerplate html

{{ OBX activity | [[Image:colors-activity.svg|40px]]|extra}}

• First param gives icon image, equivalent to Property:Sugar icon.
• Second identifies as "core" or whatever, is "core"/"bundled"/etc. an obsolete concept; Property:Activity group is a better fit.

Template:OBX source dev

{{ OBX source dev|activities/colors}}

pulls in Template:OBX source and Template:OBX boilerplate params

• First param turns into link on standard git server, ths link is equivalent to Property:Source code

Template:OBX xobundle

{{ OBX xobundle|http://www.wadeb.com/Colors-4.xo}}

• First param is link to download, equivalent to Property:Activity bundle

Template:OBX pootle

{{ OBX pootle|1=http://dev.laptop.org/git?p=activities/colors;a=blob_plain;f=po/colors.pot;hb=HEAD}}

• param 1 is equivalent to Property:Localization URL is there ever more than one?

Template:OBX team

{{ OBX team | [[User:Wade|Wade Brainerd]], Jens Andersson, Robert Anderberg }}

• First param is arbitrary wiki text for people who works on it, equivalent to Property:Team member string.
• Second optional param is a specific contact person who appears first in bold, equivalent is Property:Contact person,

Template:Olpcboxbottom

Meanwhile, Form:Activity fills in Template:Activity page, which makes all the semantic annotations but has no appearance styling. It has some additional properties not shown in OBX:

• Property:Activity genre should be a subcategory of Activities!?
• Property:Activity version, sort of implied by the OBX xobundle URL.
• Property:Short description, can be used to make table row elsewhere.
• Property:Description, not sure what the point of this is
• Property:Available languages
• Property:Devel status
• Property:Software release
• Property:Available languages (should be singular!), Property:Language code — why both?!

Some choices for unification:

1. Template:Activity page can invoke all the OBX templates
2. the OBX templates can default to using #show: to redisplay the facts
3. a Template:Display OBX for activity can invoke all the OBX template crap, defaulting to pass them the info from the semantics if not overridden.

First option makes it hard for an activity page to slap in extra OBX crap in its box. Second involves lots of hacking. Third seems to be the way to go, but still limits the OBX to what the covering template allows.