- From: Patrick Stickler <patrick.stickler@nokia.com>
- Date: Wed, 01 Oct 2003 11:48:32 +0300
- To: "ext Hammond, Tony (ELSLON)" <T.Hammond@elsevier.com>, <www-rdf-interest@w3.org>, <uri@w3.org>
On 2003-09-30 17:23, "ext Hammond, Tony (ELSLON)" <T.Hammond@elsevier.com> wrote: > The "info" URI > scheme will facilitate the referencing of information assets that have > identifiers in such public namespaces by means of URIs. The "info" scheme is > based on a Registry that invites the registration of public namespaces used > for the identification of information assets, by the parties that maintain > the namespaces. Rather than create yet another URI scheme, particularly one which is not meaningful to HTTP and the presently defined web architecture, why not set up the equivalent using http: URIs, and a (distributively) managed domain name space? C.f. http://lists.w3.org/Archives/Public/uri/2003Jul/0005.html E.g. > * the Dewey Decimal Classification 22/eng//004.678 (for the term "Internet") > could be expressed as the "info" URI <info:ddc/22/eng//004.678> http://ddc.some.root.domain/22/eng/004.678 > * the Library of Congress Control Number 2002022641 could be expressed as > the "info" URI <info:lccn/2002022641> http://lccn.some.root.domain/2002022641 etc. where 'some.root.domain' is the root domain of the organization granting sub-namespaces specific to particular naming schemes/organizations such as DDC, LCCN, etc. Then, if the owners/managers of those particular naming schemes wish to publish representations and/or descriptions of the particular resources, they can, and that information is then available to both Web and Semantic Web agents. Why define and manage the URI space outside the scope of the core Web and SW machinery? Regards, Patrick -- Patrick Stickler Nokia, Finland patrick.stickler@nokia.com
Received on Wednesday, 1 October 2003 04:48:44 UTC