[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xri] Update to Metadata Issue #1: Add $t Tag for Identifier Metadata
Mike, two quick notes RE this thread: 1) The concept of resolution of $ space XRIs is pretty new and applies (IMHO) only to "dictionary" services -- something we talk about extensively in the context of XDI (which I fully recognize is a different TC). But the XRI specs says nothing about resolution of the $ space and I don't think they need to. What's been being discussed is simply how it might work if it was applied (given that Marty has a use case for doing so). 2) Marty's "dreaming" about a $t type definition language and local resolution service is forward thinking about how it might work and not at all in the scope of XRI 2.0. The only thing being discussed in the scope of 2.0 is the addition of a $t tag to Metadata (item #3, after the two Syntax items, on tonight's/tomorrow's calls.) I'd suggest we talk over the use cases and requirements on the call. If more documentation is needed, we can agree on that and assign the action item. =Drummond -----Original Message----- From: Lindelsee, Mike [mailto:mlindels@visa.com] Sent: Thursday, September 22, 2005 3:56 PM To: xri@lists.oasis-open.org Subject: RE: [xri] Update to Metadata Issue #1: Add $t Tag for Identifier Metadata Comments inline... >-----Original Message----- >From: Schleiff, Marty [mailto:marty.schleiff@boeing.com] >Sent: Thursday, September 22, 2005 1:32 PM >To: Wachob, Gabe; Drummond Reed; xri@lists.oasis-open.org >Subject: RE: [xri] Update to Metadata Issue #1: Add $t Tag for >Identifier Metadata > >Hi All, > >Regarding #3: I think this just means if an application encounters an >XRI including something like ($t*uuidpair), the application >will be able >to know that it can use a different aproach for resolution (Open Group >proposes a pair of UUIDs where one represents the issuing >authority that >can be looked-up for resolution purposes). It's not XRI >resolution, it's >UUID Pair resolution. I keep trying to fit this idea of using a different approach to resolution of an XRI into the XRI architecture and continue to have a hard time understanding why local access isn't the appropriate solution.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]