- From: KANZAKI Masahide <mkanzaki@gmail.com>
- Date: Wed, 11 Jul 2012 23:33:48 +0900
- To: Gregg Kellogg <gregg@greggkellogg.net>
- Cc: Kuno Woudt <kuno@frob.nl>, "public-linked-json@w3.org" <public-linked-json@w3.org>
Hello,
I think there are real use cases for id to IRI conversion.
For example, many bibliographic records contain variety of
identifiers, and one of them could be used as subject IRI in order to
turn those records into Linked Data. However, identifiers in bib
records are most likely simple strings, not IRIs, e.g.
{
"isbn" : "006251587X",
"title" : "Weaving the Web",
"creator": "Tim Berners-Lee"
}
We may want to turn this ISBN code into <urn:isbn:006251587X> or
<http://www.amazon.com/exec/obidos/ASIN/006251587X>, but for either
case, it is not possible to put the JSON-LD file on the location where
the ISBN resolves to those IRIs.
cheers,
2012/7/11 Gregg Kellogg <gregg@greggkellogg.net>:
> As Markus noted, @id references will be resolved against the document location, so if you were to make your identifier "fcbcdc39-8851-4efc-a02a-ab0e13be224f#_", it would likely resolve to "http://musicbrainz.org/release/abcd76db-7d5f-3eb7-b386-051c97bfe2e4#_".
>
--
@prefix : <http://www.kanzaki.com/ns/sig#> . <> :from [:name
"KANZAKI Masahide"; :nick "masaka"; :email "mkanzaki@gmail.com"].
Received on Wednesday, 11 July 2012 14:34:18 UTC