[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xri] Order of child Service elements from Neustar GRS not right
Here’s the XRD I was referring to
(retrieved using wget 'http://xri.net/=gmw?_xrd_r=application/xrd%2Bxml%3Bsep=false') <?xml
version="1.0" encoding="UTF-8"?> <XRD
xmlns="xri://$xrd*($v*2.0)"> <Query>*gmw</Query> <Status
code="100"/> <Expires>2007-10-26T04:07:00.000Z</Expires> <ProviderID>xri://=</ProviderID> <LocalID
priority="10">!5F54.52A4.C55A.5E23</LocalID> <CanonicalID
>=!5F54.52A4.C55A.5E23</CanonicalID> <Service
priority="10"> <Type
select="true">xri://+i-service*(+forwarding)*($v*1.0)</Type> <Type
match="null"/>
<ProviderID/> <Path
match="default"/> <Path
select="true">(+index)</Path> <URI append="qxri"
priority="1">http://2idi.com/forwarding/</URI> </Service> <Service
priority="10"> <Type
select="true">http://openid.net/signon/1.0</Type>
<ProviderID/> <URI append="qxri"
priority="2">http://2idi.com/openid/</URI> <URI
append="qxri"
priority="1">https://2idi.com/openid/</URI> </Service> <Service
priority="10"> <Type
select="true">xri://+i-service*(+contact)*($v*1.0)</Type> <Type match="default"/>
<ProviderID/> <Path
select="true">(+contact)</Path> <Path
match="null"/> <URI
append="qxri"
priority="1">http://2idi.com/contact/</URI> </Service> </XRD> From: It appears that the current GRS is not producing correct
XRDs. TO wit, the following XML produced by the GRS has the
ProviderID AFTER the Type element. However, the XSD schema in the document has
the ProviderID as the very first element. The text in the spec is otherwise
ambiguous since the ProviderID is defined in a separate section from the other
Service child elements. I don’t know what the correct ordering is supposed to
be – the on implement by the Neustar code or the one in the XSD, or some
other one? Need to know this for the RelaxNG schema.
-Gabe |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]