Krinkle,
When you say "Whether some Wikipedia's output is
semantically correct is important, but (afaik) has *zero* relationship
with Wikidata. And as such is not relevant here" then I feel compelled
to point out that an ontology is most certainly envisioned -- wikidata
is implementing the SMW
With regard to wikidata infoboxes, it is either
* that the usual
technical APIs implemented as parser functions must be learned by every
Wikipedian
* or that simple interwiki transclusions are entered via
the emerging WYSIWYG tools for Wikipedia
With regard to the content of
wikidata infob
Hi Ryan,
Normal wiki rules of the road are about who can edit what
and when, not so much how, that I was referencing; I was responding to
the concern about "control".
You say: "Housing the infoboxes on
WikiData would be a terrible idea for several reasons:
* Every
Wikipedia does infoboxes dif
ven more so, over infobox content & styling.
Thanks - john
On
10.07.2012 14:08, Daniel Kinzler wrote:
> On 10.07.2012 16:47,
jmcclure@hypergrove.comwrote:
>
>> I am concerned about the performance
impact of every wikipedia calling an API for each property that it
wishes to f
Hi Denny,
I am concerned about the performance impact of every
wikipedia calling an API for each property that it wishes to format as
content in pages' infoboxes, as I understand is the design the project
is pursuing. Could you please explain to this community why it's
technically superior to
Hi Daniel,
Thanks for the background about wikidata's caching
requirements. A few questions:
1. Will wikidata have any transcludable
pages that contain just infoboxes?
Seems to me that
{{wikidata:en:infobox:Thomas Jefferson}}
could be transformed quite
readily into
[http://www.wikidata.org/w
