oasis-member-discuss — archive

[Drummond Reed]

 MHonArc v2.5.0b2 -->

















oasis-member-discuss message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: RE: [oasis-member-discuss] Comments on Artifact ID requirements




From: "Drummond Reed" <drummond.reed@cordance.net>
To: <peter@justbrown.net>,<oasis-member-discuss@lists.oasis-open.org>
Date: Tue, 2 Aug 2005 16:06:35 -0700






Although I just returned from an extended vacation (and must admit that I
have not had time to review the Artifact ID requirements in depth yet),
nonetheless the points Peter makes in this message are very good ones, and
in fact are central to XRI (Extensible Resource Identifiers) specifications
developed by the XRI TC (http://www.oasis-open.org/committees/xri). XRIs
extend (and are backwards compatible with) URI/IRI syntax and add features
designed explicitly for abstract identification of resources -- and
resolution into concrete representations of those resources -- following the
precise guidelines Peter describes.

A further benefit is that XRIs standardize several of the key types of
identifier metadata Peter enumerates (such as version, language, date -- see
the XRI Metadata Specification V2 Committee Draft 01,
http://www.oasis-open.org/committees/download.php/11854/xri-metadata-V2.0-cd
-01.pdf). 

Lastly, the XRI 2.0 specifications include full support for HTTP proxy
resolution so all XRI syntax and resolution capabilities can be deployed
immediately using available HTTP infrastructure.

A suggestion, then, is to arrange a meeting between the Artifact ID team and
the XRI TC to discuss the requirements and see if XRI 2.0 can help OASIS
solve its resource identification needs.

Mary, Jamie - who should we contact about this?

=Drummond 
================
Drummond Reed
Co-Chair, OASIS XRI & XDI TCs
http://public.xdi.org/=Drummond.Reed