[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xri] priority attribute question
Re removing the priority attribute. I
think we can do that fairly easily but I’ll need to check with the
i-brokers to see what that means to them. It should be a non-issue.
The one problem I do have is that for the GRS the LocalId is the local portion
of the CID and uses the same priority. Since the LocalId is system
generated the i-brokers are not able to populate it with other values. So
Drummond, do I remove the priority from the localId also … for the GRS
that would seem to make sense. From: Gabe Wachob
[mailto:gabe.wachob@amsoft.net] We can put that language in, but no
resolvers will work until neustar changes the GRS, unless they actually
implement this hack. That’s kind of lame – so
I’d hope that Neustar would remove the priority attribute since it does *nothing* now anyway. From: Drummond Reed
[mailto:drummond.reed@cordance.net] Good point about the xri.net XRDS. I
don’t know about others via Barx, ooTao, FreeXRI, etc. Since it will be relatively common for a
WD10 XRDS to have a CanonicalID element with a priority attribute, I’m
thinking we should put a backwards compatability note in the spec recommending
that implementations accept it. What do you think? =Drummond From: OK, then this means that all of the XRDs
being served by xri.net are broken w/r/t WD11ED06… they all have a
priority attribute on the CanonicalID element. I don’t think anyone else is serving
out Canonical IDs now, are they?
-Gabe From: Drummond Reed
[mailto:drummond.reed@cordance.net] Ah, Gabe, good catch, that’s my
mistake. The fact that the CanonicalID element allows the priority attribute
was a legacy of drafts before ED03 (or ED04, I can’t remember) when the
CanonicalID element cardinality was zero-or-more. Now that it is zero-or-one, neither the
CanonicalID or CanonicalEquivID should accept the priority attribute. BTW, are you going to also put out an
updated XSD schemas for XRDS and XRD when you are done? All these final fixes
should be reflected in both even if the RelaxNG version will be normative. Thanks, =Drummond From: I see the barx resolver returns me an XRD with a priority
attribute on the CanonicalID element. I was a bit surprised to see that since section 4.3.3 of
WD11/ED 06 doesn’t mention CanonicalID as an element that can have a
priority attribute and neither does section 4.2.3. I *do* notice that the XSD schema from WD11/ED
06 allows it. So which is it? What elements can have the priority
attribute?
-Gabe |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]