Markus Krötzsch wrote:
On 01/11/11 14:11, Jonathan Lang wrote:
This is a very true point.  Then again, creating a spinoff of #subobject strictly to add an optional visualization feature to it feels a little awkward.  Still, it would be a good learning experience.

It does not have to be a spinoff. I am happy to include contributed code into SMW as long as there are some maintainers for it.

OK; I'll look into it - though hopefully the result won't be something that needs maintenance.  (I know; wishful thinking.)

I understand, but #subobject calls do not return anything anyway. So you can simply write

Jon Lang{{#subobject name|personal=Jonathan|nickname=Jon|family=Lang}}

if you like. I don't see a real advantage of piping this string through the parser function.

Hmm; I overlooked that. 

I was drawn to SMW due to its dual-nature approach of tagging human-readable text (arguably the primary purpose of MW) with machine-readable data (the S in SMW); an SMW parser function that merely provides data without having any sort of presence in the human-readable side of things just feels wrong to me, like adding Properties to a page without them showing up in the page's text.  From a page author's perspective, I would expect "{{#subobject ...}}" to show up in some manner when the page is displayed.  As well, decoupling the #subobject from any sort of wiki text makes it difficult to write other extensions that might do such things as, say, presenting the semantics of a term on a page as a footnote or tooltip. 

--
Jonathan "Dataweaver" Lang