oasis-member-discuss — archive

[William Cox]

 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: William Cox <wtcox@comcast.net>
To: Drummond Reed <drummond.reed@cordance.net>
Date: Fri, 12 Aug 2005 12:43:48 -0400






Drummond -

I'm interested in such a discussion; I will also volunteer Mary (subject 
to Jamie and Mary's veto).

Per the Member Review AIR WD 15.pdf document distributed with AIR WD15,

####################
"7. This document specifies a set of Required Metadata for OASIS 
artifacts to be available in the document and/or associated metadata, 
and also as a basis for exposing selected metadata in the Artifact 
Identifier. Comments would be appreciated on the following plan for 
XHTML metadata in the next Working Draft, and would be inserted into 
section 5.5.2 and 5.5.3 (lines 438-450):

Use the style of “Expressing Dublin Core in HTML/XHTML meta and link 
elements,” Dublin Core Metadata Initiative Recommendation, November 30, 
2003, http://dublincore.org/documents/dcq-html/. The intent is to follow 
the style, but not to make normative reference to the Recommendation 
There will be one meta element per name-value pair. We may need to 
define an OASIS metadata namespace to use as a prefix for the metadata 
names.
The compatibility for versions of HTML before XHTML 1.0 would parallel 
that for the DCMI Recommendation."
####################

Your proposed discussion addresses closely related issues.

When can we get together? This strikes me as a phone discussion at first.

Thanks.

bill cox


Drummond Reed wrote:

>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 
>
>
>