Re: [Wikidata-l] Wikidata Transclusions

2012-06-14 Thread Nikola Smolenski
On 14/06/12 00:39, jmccl...@hypergrove.com wrote: Transclusion is surely fundamental to wiki application design. The [[wikidata]] proposal by contrast is a client-server API, such things an artifact of the 20th century. What is the point of it here? Ultimately the problem you're grappling with

Re: [Wikidata-l] Wikidata Transclusions

2012-06-14 Thread Gregor Hagedorn
While I agree that it is desirable to support simple, preformatted Infoboxes that can, with minimal effort be re-used in a large number of language versions of Wikipedia, I strongly disagree with the demand to make this the only choice. I think the present Wikidata approach to allow local

Re: [Wikidata-l] Wikidata Transclusions

2012-06-14 Thread Gerard Meijssen
Hoi, Technically there is nothing stopping Wikidata from hosting multiple infoboxes on the same subject. The big thing about such infoboxes is that their layout is the same for all subjects in the same category. This does not mean that every one looks the same but it does mean they follow a

Re: [Wikidata-l] Wikidata Transclusions

2012-06-14 Thread Gregor Hagedorn
On 14 June 2012 12:33, Gerard Meijssen gerard.meijs...@gmail.com wrote: Finally, when Wikidata provides data and info boxes, it does not mean that any project is compelled to use it. As Wikidata matures, it will become increasingly clear that it is not the best practice. that may be, but

Re: [Wikidata-l] Wikidata Transclusions

2012-06-14 Thread jmcclure
Wikidata publishing infoboxes and Wikipedias using them is again the client-server model. Not sure where this chestnut is coming from. Transclusion is as close to client-server as my cooking is to being gourmet! There's NO API. so I don't understand your commenst at all, sorry. On

Re: [Wikidata-l] Wikidata Transclusions

2012-06-14 Thread jmcclure
I strongly disagree with the demand to make this the only choice. - Gregor, I'm a bit confused -- are you talking about the transclusion design approach in this statement? because, if so, I'd think there'd be a number of infobox styles that can be selected by an author on the wikidata

Re: [Wikidata-l] Wikidata Transclusions

2012-06-14 Thread Gregor Hagedorn
Gregor, I'm a bit confused -- are you talking about the transclusion design approach in this statement? Yes, in the sense that it demands to be the only access to wiki data content in a Wikipedia. because, if so, I'd think there'd be a number of infobox styles that can be selected by an

Re: [Wikidata-l] Wikidata Transclusions

2012-06-14 Thread jmcclure
Gregor says Or are you proposing to simply use the existing template programming with the only the difference that wikidata is the only mediawiki where the properties can be accessed within templates? Much of my argument assumes that you are looking for a non-template based infobox renderer, I

Re: [Wikidata-l] Wikidata test wikis are getting spammed

2012-06-14 Thread Lydia Pintscher
On Thu, Jun 14, 2012 at 7:57 PM, Erik Moeller e...@wikimedia.org wrote: http://wikidata-test-client.wikimedia.de/wiki/Special:RecentChanges It might be best to limit editing, or try to rope stewards into running their anti-spambots there ... Uff of course it could only be so long until

Re: [Wikidata-l] [[meta:wikitopics]] updated

2012-06-14 Thread Nadja Kutz
John McClure wrote: Of course, thanks for the pointer. Yes, I'd agree that 19788's ontology be closely reviewed for inclusion. 19788:2 standardizes the Dublin Core properties, the same I recommend for [[wikidata]] provenance data, the same slated for the [[wikidata]] ontology. But more to