[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xri] Aligning XRD with Link (Header/Element)
John, As Drummond mentioned this is the best time... As adoption is not huge, and we can end of life the Service nodes, while supporting Link too. So that can be an option for backwards compatability. Nika From: John Bradley <jbradley@mac.com> Date: Tue, 25 Nov 2008 12:38:45 -0800 To: Drummond Reed<drummond.reed@cordance.net> CC: OASIS XRI TC<xri@lists.oasis-open.org>; David Orchard<orchard@pacificspirit.com>; David Recordon<recordond@gmail.com> Subject: Re: [xri] Aligning XRD with Link (Header/Element) I am really hesitant to abandon backwards compatibility with openID mostly. Not all openID RPs are going to upgrade to XRD overnight if at all. Existing parsers are looking for Type and Service. I can see making Type deprecated and allowing both Type and Rel during the transition. Service is harder to deal with unless we do a similar thing and perhaps allow a mix of SEPs Like: <XRD> <Service> <Type>http://example.com/relationship</Type> <MediaType>application/xml</MediaType> <URI>http://example.org/document</URI> </Service> <Link> <Rel>http://example.com/relationship</Type> <MediaType>application/xml</MediaType> <URI>http://example.org/document</URI> </Link> </XRD> On the other hand as Services directly encode API endpoints should we keep them for such and use <Link> to indicate that the URI is abstract and is something that needs to be resolved to get the meta-data for the Link? I don't think abandoning some sort of backwards compatibility is a good idea. =jbradley On 25-Nov-08, at 12:17 PM, Drummond Reed wrote:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]