On Wed, Mar 9, 2016 at 7:37 PM, Stas Malyshev smalyshev@wikimedia.org wrote:
I don't see why it is an issue that some external identifiers don't translate to URIs. What complex logic is involved here? In RDF we should just add the plain identifier like we have it now as the default value,
If we say "since external IDs are in fact URIs, since they refer to external databases, then let's mark them as URI property and render them as full URI - i.e. let's instead of:
wd:Q1000336 wdt:P646 "/m/03pvzn"
say this:
wd:Q1000336 wdt:P646 https://www.freebase.com/m/03pvzn
This may make a lot of sense, since the interesting URL that people would like to see may be the latter, and the former is kind of chopped-off form of it we use for our internal purposes. OTOH, what if it wasn't easy or possible to generate the latter from the former automatically? Then we need some logic to figure that out.
From a machine processing point of view, a more interesting statement is
probably:
wd:Q1000336 owl:sameAs <https://rdf.freebase.com/ns/m.03pvzn https://www.freebase.com/m/03pvzn>
This is supposed to redirect to either RDF https://rdf.freebase.com/rdf/m.03pvzn https://www.freebase.com/m/03pvzn or HTML https://www.freebase.com/m/03pvzn based on content negotiation, but that seems to be broken right now and it always returns RDF.
Tom