On 11/26/14 11:39 AM, Daniel Kinzler wrote:
Am 26.11.2014 15:05, schrieb Kingsley Idehen:
All,
Given the Wikidata Entity URI:
http://www.wikidata.org/wiki/Q569 The is the URI of
the HTML representation of the description of concept Q569.
The canonical URI of the concept Q569 is <http://www.wikidata.org/entity/Q569>.
Should I be able to issue an HTTP GET based
lookup that resolves to an RDF
document that describes what the URI above identifies? Or is this strictly about
periodic RDF dumps loaded to various Linked Open Data (LOD) cloud data spaces etc?
When you resolve <http://www.wikidata.org/entity/Q569> via HTTP, content
negotiation is applied, and you will get a 303 redirecting to
<http://www.wikidata.org/wiki/Q569> if your agent asks for HTML, or to
<http://www.wikidata.org/wiki/Special:EntityData/Q569.ttl> or
<http://www.wikidata.org/wiki/Special:EntityData/Q569.json> respectively, if you
ask for Turtle or JSON.
Note that our RDF mapping is still very incomplete. Statements are not covered
at all at the moment. The JSON representation is complete.
Daniel,
How about the following approach, which broadens the kinds of agents
that can discover what's accessible via a given Wikidata URI.
Using <link/> and @rel in <head/> of HTML Document:
http://www.wikidata.org/wiki/Q569, simply add:
<link rel="related" type="text/turtle"
href="http://www.wikidata.org/entity/Q569" />
On the server side (if possible) replicate the relation above using
"Link:" based relations:
Link: <http://www.wikidata.org/entity/Q569> ; rel="related" .
The suggestions above simply compliment content negotiation [1], and
keeps <http://www.wikidata.org/wiki/Q569> as an entry point into the
Wikidata Linked Open Data cloud enclave [2].
We should minimize the memory burden on Web users, even I (who lives in
this world and even loaded Wiki data into the LOD cloud) completely
forget about how the HTML entity description document and actual entity
URIs are connected :)
Naturally, you can add more relations e.g., foaf:primaryTopic,
dcterms:subject etc.., but via Link: and <link/> you will need to use
their full URIs, that's all.
Links
[1]
http://bit.ly/wikidata-entity-uri-vapour-report -- Vapor Report for
your current Entity URI
[2]
http://bit.ly/wikidata-entity-html-document-uri-report -- Vapor
Report for your current HTML based Entity Description Document URI .
--
Regards,
Kingsley Idehen
Founder & CEO
OpenLink Software
Company Web:
http://www.openlinksw.com
Personal Weblog 1:
http://kidehen.blogspot.com
Personal Weblog 2:
http://www.openlinksw.com/blog/~kidehen
Twitter Profile:
https://twitter.com/kidehen
Google+ Profile:
https://plus.google.com/+KingsleyIdehen/about
LinkedIn Profile:
http://www.linkedin.com/in/kidehen
Personal WebID:
http://kingsley.idehen.net/dataspace/person/kidehen#this