I've *finally* updated my wikidata URI pattern picture based on this and an earlier
conversation from back in August :
(you need to click the image before it's readable)
Hoping it looks a little more correct. Certainly makes more sense in my head.
My only concern is that (like DBpedia) it seems to conflate the 303 (can't send you
that) step with the content negotiation step.
is the entity / non-information resource URI
are information resource representation URIs
there's no generic information resource URI in the scheme.
In BBC-land we try to never expose the information resource representation URIs except as
location headers. So
is the NIR
is the generic IR which connegs to:
bbc.co.uk/programmes/:programme.html < desktop html
bbc.co.uk/programmes/:programme.mp < mobile html
bbc.co.uk/programmes/:programme.json < json
bbc.co.uk/programmes/:programme.xml < xml
bbc.co.uk/programmes/:programme.rdf < rdf
and the .html, .mp, .json, .xml, .rdf are never exposed except as location headers for
conneg on the generic IR and the #programme bit is never used except when we want to make
RDF(a) statements about the NIR
Wondering if the 303 / conneg conflation will make it more difficult to understand
what's going on, more difficult to work with and more difficult to host if you pick up
a 303 for every link (as in DBpedia)
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to