Oops, never mind - I just re-read the original email, and realized that your proposed <subpage> tag has nothing to do with MediaWiki subpages (i.e., pages of the form "A/B"). So actually, your proposed syntax might be nice; though I would recommend to change the name of the tag. :) Maybe <section> or <subsection> instead?


On Tue, Nov 15, 2011 at 11:03 AM, Yaron Koren <yaron@wikiworks.com> wrote:
Hi Jon,

Unless I'm missing something, I don't see much benefit to having this. If the data is on another page (whether it's a subpage or not), you can already query its data in the same way that you would query a subobject's (or internal object's) data. The only benefit I see for this is that it would define a semantic linkage between the subpage and the main page. Which could be useful; but on the other hand, if the subpage contains a template, you could do that automatically via that template as well.


On Tue, Nov 15, 2011 at 8:12 AM, Jon Lang <dataweaver@gmail.com> wrote:
How hard would it be to write a lightweight <subpage> tag that scans its contents for properties, extracts them, and appends a {{#subobject}} built out of the properties that it found? For example:

<subpage name="Forrest Gump">
[[given::Forrest]] [[surname::Gump]] is the [[title::Shrimp Man]] of [[org::Bubba Gump Shrimp Co.]]

would become something like:

Forrest Gump is the [[Shrimp Man]] of [[Bubba Gump Shrimp Co.]]
{{#subobject:Forrest Gump|given=Forrest|surname=Gump|title=Shrimp Man|org=Bubba Gump Shrimp Co.}}

I suspect that <subpage> would be at least as popular as {{#subobject}} as a way of adding SIO-like semantics to a page.

Jonathan "Dataweaver" Lang

RSA(R) Conference 2012
Save $700 by Nov 18
Register now
Semediawiki-devel mailing list

WikiWorks MediaWiki Consulting http://wikiworks.com

WikiWorks MediaWiki Consulting http://wikiworks.com