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


Help: OASIS Mailing Lists Help | MarkMail Help

xri message

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

Subject: RE: [xri] cross-reference-based version proposal

Actually, your desire is our intent, I think.

The idea is that +version/cvs is actually (potentially) a resolvable xri in and of itself. So you could try to resolve it to discover info about it.

Also, we discussed (though I did not mention it) the ability to "locally extend" the types of versions in much the way you propose. Remember that cross references can include references to any URI (the use of +, =, @ is a special short-cut case for XRI URIs):


Now, this starts to get painfully long and verbose, but it does work, IMHO. We are really starting to get into the area of sticking metadata (and even metadata about metadata) into URIs, and i don't think thats ever going to *look* pretty. But in this case, looking ugly is not neccesarily a problem.


> -----Original Message-----
> From: Peter C Davis [mailto:peter.davis@neustar.biz]
> Sent: Wednesday, April 30, 2003 9:34 AM
> To: Dave McAlpin
> Cc: 'Wachob, Gabe'; xri@lists.oasis-open.org
> Subject: Re: [xri] cross-reference-based version proposal
> Dave McAlpin wrote:
> >Thanks for summarizing this Gabe. I'll just make comments on 
> two of the
> >examples
> >
> >xri://naming.authority/local/part/(+version/1.2)
> >
> >It seems wrong to me that 1.2 is an immediate child of 
> +version in that it
> >pollutes a namespace we intend to use for version types. An 
> example like
> >this might be better.
> >
> >xri://naming.authority/local/part/(+version/numeric/2)
> >
> >  
> >
> I would prefer if we also allowed for version types themselves to be 
> dereferencable.  That way, we can accomodate an open versioning 
> framework, rather than attempting to define all possible 
> version types.  
> This is the way Liberty handles the Attribute-portion of the identity 
> framework (ID-WSF: SIS).
> so a valid version string may look like:
> xri://naming.authority/local/part/[+version/urn:version-author
> ity:dottedalphanum/1.2a]
> or even:
> xri://naming.authority/local/part/[+version/urn:xri:version-au
> thority:dottedalphanum/1.2a]
> etc...  of course, a version-spec referenced as 
> xri://version.name.authority/spec/namespace may be difficult 
> for parsers.
> --- peterd

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