LOL, I work with Semantic MediaWiki and have yet another syntax to
tickle your delight. As JSON is for _javascript_ (same as specifying a
JS object), this format is for wikis -- here, these are MediaWiki
template invocations.
{{propertyname
|property-value(s), per wiki's language
|@=zu (for this example)
|@zu=isiZulu-specific value(s)
|label=user property name(s)
|option=processing options(s)
|provenance=named value(s)
|qualifier=adverb(s)/adjective(s)/past participle(s)
|subject=optional topic name(s)
|time=iso time period(s)
}}
These templates package validation logic (eg axioms) and storage
logic applicable to a property into code modules. This minimalist
format handles multiple subjects and multiple and multilingual
property values, even for relations. It allows for user-labels
(one-off properties); provenance specifications (dublin core);
time-series; and value qualifiers (like 'temporarily', 'estimated'
etc). Afaik no other syntax can do this. The tricky part is updating
the triple store, amenable to queries. Upon storage, each wikipage
has its own 'topicmap'. Wikis export data in MediaWiki XML or in RDF
XML; in MediaWiki XML, these calls are within the text content for a
wikipage.
/jmc
|
_________________________________________________________________
Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/
Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
Community Files: http://ontolog.cim3.net/file/work/OntologySummit2014/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2014
Community Portal: http://ontolog.cim3.net/wiki/ (01)
|