RE: [xri-comment] Basic comment on XRI necessity and scope

["Drummond Reed" <drummond.reed@cordance.net>]

Mr. Nebert,

Thank you very much for submitting your comment on XRI Resolution 2.0
Committee Draft 03. 

Because work on XRI Resolution 2.0 has been ongoing for over two years, this
specification has been separated in time quite some distance from its base
specification, XRI Syntax 2.0, which was approved as an XRI Technical
Committee Specification in November 2005:

	http://www.oasis-open.org/committees/download.php/15377  

Being the first specification in the XRI suite, XRI Syntax 2.0 specification
contains more information about the motivations for XRI infrastructure and
how it differs from URN infrastructure. In addition, both XRI Syntax 2.0 and
XRI Resolution 2.0 contain references (in their Informative References
sections) to the two XRI TC documents that most deeply answer your
questions:

	OASIS XRI Technical Committee, XRI 2.0 FAQ
	http://www.oasis-open.org/committees/xri/faq.php, Work-In-Progress,
March 2006.

	G. Wachob, D. Reed, M. Le Maitre, D. McAlpin, D. McPherson,
Extensible Resource Identifier (XRI) Requirements and Glossary v1.0,
http://www.oasis-open.org/committees/download.php/2523/xri-requirements-and-
glossary-v1.0.doc, June 2003.

We hope these documents will address your concerns.

Best,

=Drummond 
================
Drummond Reed
Cordance Corporation
Co-Chair, OASIS XRI & XDI TCs
i-name: =drummond.reed
http://xri.net/=drummond.reed 


> -----Original Message-----
> From: Doug Nebert [mailto:ddnebert@usgs.gov]
> Sent: Tuesday, March 11, 2008 8:34 AM
> To: xri-comment@lists.oasis-open.org
> Subject: [xri-comment] Basic comment on XRI necessity and scope
> 
> It is not clear from reading the documentation why the authors chose to
> develop a new specification instead of re-use and embellish the Uniform
> Resource Name (URN) scheme and resolver (IETF RFC 2141) which was
> designed for this purpose. I don't understand why a XRI is needed when
> URN management through IANA and designated authorities is already in
> place.
> 
> Proposed document should include a scope and explanation for the
> standing and capabilities of the XRI with respect to the existing URN
> practices, or be withdrawn as a proposed OASIS resolution.
> 
> Doug.
> --
> Douglas D. Nebert
> Staff Geospatial Technology Advisor, System-of-Systems Architect
> FGDC Secretariat   Phone: +1 703 648 4151   Fax: +1 703 648-5755
> 
> 
> --
> This publicly archived list offers a means to provide input to the
> OASIS Extensible Resource Identifier (XRI) TC.
> 
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
> 
> Subscribe: xri-comment-subscribe@lists.oasis-open.org
> Unsubscribe: xri-comment-unsubscribe@lists.oasis-open.org
> List help: xri-comment-help@lists.oasis-open.org
> List archive: http://lists.oasis-open.org/archives/xri-comment/
> Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
> Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xri