OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

codelist message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [codelist] Fwd: Re: Impact of changing a specification from URI to IRI and XRI

I have not had a chance to look into the XRI question since the last  
telecon (I've been focussing on the UML model).  My open questions are:

If we allow XRIs for identifying code lists, code list versions,  
column/keys, column/key versions, are their any special semantics that the  
XRI spec would apply to the construction of these?
If so, what would that be, and what would be need to put in the spec?
Would the XRI semantics change the nature of the way URIs currently work  
as identifiers in the spec?

Has anyone had a chance to look at this?  Thanks,

Cheers, Tony.

On Thu, 30 Nov 2006 22:52:28 -0000, G. Ken Holman  
<gkholman@CraneSoftwrights.com> wrote:

> Fellow CLRTC members,
> I've asked someone I highly respect regarding markup and the Internet  
> about any impact we have of changing our use of URI strings.
> He can only comment on the use of IRI strings and from what I see there  
> is no impact for us to simply say a string is an IRI wherever we say it  
> is a URI.
> http://en.wikipedia.org/wiki/XRI states there is some disagreement  
> regarding the problems being addressed by XRI strings.  Perhaps we  
> should wait to say anything about XRI until it is more widely accepted.
> . . . . . . . . . . Ken

Anthony B. Coates
Senior Partner
Miley Watts LLP
Experts In Data
+44 (79) 0543 9026
Data standards participant: ISO 20022 (ISO 15022 XML), ISO 19312,  

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]