It appears to me the parser functions are intended to be executed by the client. I suggest instead interwiki transclusions, meaning all content is built on the wikidata host. Specialized facilities & data models implemented by the host are a black box to everyone else. If a specialized infobox is wanted by a client, then the person needs to develop it on the wikidata host, and request it by name in her transclusion. The host could then offer a page-layout user interface, appropriate for more advanced users than the typical.
On 30.05.2012 12:44, [email protected] wrote: > Not only are comments welcome but, everyone is invited to update the text however they see fit. Please do not be argumentative - save that for its talk page. At a minimum, the proposal suggests that wiki transclusion of content from the wikidata repository is an interesting alternative to the display inclusion parser functions. This approach keeps development of wikidata resources within the wikidata community, which is perfectly appropriate. > > On 30.05.2012 12:21, [email protected] wrote: > >> I have updated the page [1] I started containing requirements and design notes for a topicmap-based wikidata repository. Comments are welcomed and I'll continue to rationalize the material I have to offer. >> >> Thanks, >> John McClure >> Belltower Wikis >> >> [1] https://meta.wikimedia.org/wiki/Wikitopics [1] Links: ------ [1] https://meta.wikimedia.org/wiki/Wikitopics
_______________________________________________ Wikidata-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-l
