Comments on: info-uris and opening up library data http://inkdroid.org/journal/2006/05/16/info-uris-and-opening-up-library-data/ $pithy_personal_mission_statement Wed, 10 Mar 2010 02:04:23 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: ed http://inkdroid.org/journal/2006/05/16/info-uris-and-opening-up-library-data/comment-page-1/#comment-37649 ed Wed, 11 Jul 2007 13:27:49 +0000 http://www.inkdroid.org/journal/?p=99#comment-37649 Total agreement Pete :-) One of the benefits of writing down ones thoughts is to see how much they change over time. Total agreement Pete :-) One of the benefits of writing down ones thoughts is to see how much they change over time.

]]> By: PeteJ http://inkdroid.org/journal/2006/05/16/info-uris-and-opening-up-library-data/comment-page-1/#comment-1149 PeteJ Tue, 11 Jul 2006 11:30:29 +0000 http://www.inkdroid.org/journal/?p=99#comment-1149 I don't think it is correct to say that "info-uris are designed to identify persistent namespaces not the resources themselves". RFC 4452 refers to the use of info URIs to describe "information assets", and says When referencing an information asset by means of its "info" URI, the asset SHALL be considered a "resource" as defined in RFC 3986 And your examples above refer to info URIs for people, i.e. resources/things other than "persistent namespaces". The examples of info URIs from the LCCN namespace does raise an interesting question. According to http://www.loc.gov/marc/lccn-namespace.html and http://info-uri.info/registry/OAIHandler?verb=GetRecord&metadataPrefix=reg&identifier=info:lccn/ An LCCN is an identifier assigned by the Library of Congress for a metadata record (e.g., bibliographic record, authority record) which seems quite unambiguous that an LCCN (and an info URI in the LCCN namespace?) is an identifier for LoC's metadata record. If that is the case, then I think using that same identifier for the subject of the metadata record (the person etc) contradicts that statement by LoC and introduces ambiguity about what asset/resource is identified. The person who created the LoC authority record describing the Notorious B.I.G.is a different person from the one who created the Notorious B.I.G. (Probably.) But I'm really of the school that says anything the info URI scheme provides could be achieved more easily and cheaply - still without writing an RFC to refister my namespace ;-) - using the http URI scheme e.g. as suggested here http://lists.w3.org/Archives/Public/www-rdf-interest/2003Oct/0000 Cheers PeteJ I don’t think it is correct to say that “info-uris are designed to identify persistent namespaces not the resources themselves”. RFC 4452 refers to the use of info URIs to describe “information assets”, and says

When referencing an information asset by means of its “info” URI, the asset SHALL be considered a “resource” as defined in RFC 3986

And your examples above refer to info URIs for people, i.e. resources/things other than “persistent namespaces”.

The examples of info URIs from the LCCN namespace does raise an interesting question. According to http://www.loc.gov/marc/lccn-namespace.html and http://info-uri.info/registry/OAIHandler?verb=GetRecord&metadataPrefix=reg&identifier=info:lccn/

An LCCN is an identifier assigned by the Library of Congress for a
metadata record (e.g., bibliographic record, authority record)

which seems quite unambiguous that an LCCN (and an info URI in the LCCN namespace?) is an identifier for LoC’s metadata record. If that is the case, then I think using that same identifier for the subject of the metadata record (the person etc) contradicts that statement by LoC and introduces ambiguity about what asset/resource is identified. The person who created the LoC authority record describing the Notorious B.I.G.is a different person from the one who created the Notorious B.I.G. (Probably.)

But I’m really of the school that says anything the info URI scheme provides could be achieved more easily and cheaply – still without writing an RFC to refister my namespace ;-) – using the http URI scheme e.g. as suggested here

http://lists.w3.org/Archives/Public/www-rdf-interest/2003Oct/0000

Cheers
PeteJ

]]> By: inkdroid » more on web identifiers http://inkdroid.org/journal/2006/05/16/info-uris-and-opening-up-library-data/comment-page-1/#comment-1146 inkdroid » more on web identifiers Tue, 11 Jul 2006 11:25:28 +0000 http://www.inkdroid.org/journal/?p=99#comment-1146 [...] I monitor the www-tag discussion list, but half of it goes right over my head–so I was pleased when a colleague forwarded URNs, Namespaces and Registries to me. Don’t let the 2001 in the URL fool you, it has been updated quite recently. This finding provides an interesting counterpoint to rfc 4452 which I wrote about earlier. [...] [...] I monitor the www-tag discussion list, but half of it goes right over my head–so I was pleased when a colleague forwarded URNs, Namespaces and Registries to me. Don’t let the 2001 in the URL fool you, it has been updated quite recently. This finding provides an interesting counterpoint to rfc 4452 which I wrote about earlier. [...]

]]>