Am 27.02.2014 09:44, schrieb Markus Krötzsch:
Yes. However, for metadata it is usually preferred to
use the entity URI, since
the document
http://wikidata.org/wiki/Qetc is just an automatic UI rendering of
the data, and as such relatively uninteresting. One will eventually get (using
content negotiation) all data in RDF from
http://www.wikidata.org/entity/Qetc
(JSON should already work, and html works of course, when opening the entity URI
in normal browsers). The only reason for using the wiki URI directly would be if
one uses a property that requires a document as its value, but in this case one
should probably better use another property.
To recap and add some details:
http://www.wikidata.org/entity/Q12345 is the canonical URI for the concept
http://www.wikidata.org/wiki/Special:EntityData/Q12345 is the format-agnostic
canonical URI of the *description* of the object (the data URI, for short).
http://www.wikidata.org/wiki/Q12345 is the URL of the HTML representation of the
description of the concept (i.e. the wiki page)
http://www.wikidata.org/wiki/Special:EntityData/Q12345.json is the URL of the
JSON representation of the description of the concept
http://www.wikidata.org/entity/Q12345.json works as a redirect to the above, but
is discouraged, since it mixes the concept URI with a format suffix that is
meaningful only for the description, not the concept.
HTH
Daniel
--
Daniel Kinzler
Senior Software Developer
Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.