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] Adding XDI as a service in XRIDs


If you think there should be a registry for service types, we should bring this up with OASIS - I know there are multiple folks talking about registry issues for reasons very similar to this. 

Whether or not XDI is referenced in the XRI spec, it will be good to have a registry of known local access services (and authority access services if I write that in to the XRI 2.0 spec this week).

But this is not a reason to stick XDI in the XRI spec. XRI has no (and should not have) dependencies on XDI specifications. 

	-Gabe

__________________________________________________ 
gwachob@visa.com
Chief Systems Architect
Technology Strategies and Standards
Visa International 
Phone: +1.650.432.3696   Fax: +1.650.554.6817


> -----Original Message-----
> From: Drummond Reed [mailto:drummond.reed@cordance.net]
> Sent: Monday, January 10, 2005 4:13 PM
> To: Wachob, Gabe; xri@lists.oasis-open.org
> Subject: RE: [xri] Adding XDI as a service in XRIDs
> 
> 
> Gabe,
> 
> I understand your point about not making a normative reference to an
> unfinished spec. But this raises the larger issue: what do 
> you think should
> be the process for adding a service identifier to the 
> namespaces defined in
> section 2.1.4 of your draft Res spec at
> http://www.oasis-open.org/committees/download.php/10733/xri20res.doc? 
> 
> In other words, once the XDI TC has published the XDI 
> specifications, how
> would the XDI TC go about having XDI registered as an XRIAuthority and
> LocalAccess protocol?
> 
> (I will also put in a plug that XDI deserves a *non-normative 
> reference* as
> an example of at least one XRIAuthority/LocalAccess Service 
> that is under
> development specifically for XRI-identified resources.)
> 
> =Drummond 
> 
> 
> -----Original Message-----
> From: Wachob, Gabe [mailto:gwachob@visa.com] 
> Sent: Monday, January 10, 2005 11:52 AM
> To: Drummond Reed; xri@lists.oasis-open.org
> Subject: RE: [xri] Adding XDI as a service in XRIDs
> 
> Drummond-
> 	Strong objection to the first. I don't see why referring to a
> non-existent spec normatively at this point makes any sense, 
> especially when
> the current wording doesn't *prevent* future use of XDI as a 
> local access
> protocol specified in the Service element for Local Access. 
> 
> 	Agreement that the second would be reasonable. If for no other
> reason than parallelism to Local Access. 
> 
> 	-Gabe
> 
>  
> __________________________________________________ 
> gwachob@visa.com
> Chief Systems Architect
> Technology Strategies and Standards
> Visa International 
> Phone: +1.650.432.3696   Fax: +1.650.554.6817
> 
> 
> > -----Original Message-----
> > From: Drummond Reed [mailto:drummond.reed@cordance.net]
> > Sent: Sunday, January 09, 2005 10:44 PM
> > To: xri@lists.oasis-open.org
> > Subject: [xri] Adding XDI as a service in XRIDs
> > 
> > 
> > Gabe et al:
> > 
> > In discussing XDI and XRI resolution with Loren and Dave at 
> > an overnight
> > last week, one obvious suggestion came up: with the XDI TC 
> > well on its way
> > to defining its first specs for "XRI Data Interchange", the XRI 2.0
> > Resolution spec should add "XDI" as a second standard service 
> > type alongside
> > "X2R". That way any service provider that supports XDI as a means of
> > interaction with a XRI-identified resource could indicate 
> > that in the XRID.
> > 
> > While that's pretty obvious, a related point occurred to me 
> > that may not be
> > so obvious: we should do the same thing for XRI Authorities. 
> > In other words,
> > XDI will also be a way to interact with some (perhaps many) 
> > XRI Authorities
> > to get the XDI equivalent of an XRID.
> > 
> > So this raises the need in the XRI 2.0 Resolution spec for 
> > the XRIAuthority
> > element of XRIDs to include a "Service" element just like the 
> > LocalAccess
> > element does. This way XRI Authorities that support XDI for 
> > XRI resolution
> > (or any other future XRI resolution protocol, such as DNS/XRI) could
> > advertise that fact to a resolver.
> > 
> > Make sense?
> > 
> > =Drummond 
> > 
> > 
> > 
> > To unsubscribe from this mailing list (and be removed from 
> > the roster of the OASIS TC), go to 
> > http://www.oasis-open.org/apps/org/workgroup/xri/members/leave
> > _workgroup.php.
> > 
> > 
> 
> 
> 
> To unsubscribe from this mailing list (and be removed from 
> the roster of the OASIS TC), go to 
> http://www.oasis-open.org/apps/org/workgroup/xri/members/leave
> _workgroup.php.
> 
> 


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