|Subject:||RE: [xri] Errata proposals|
|From:||Dave McAlpin (dave...@epok.net)|
|Date:||Mar 15, 2004 1:29:52 pm|
Thanks for doing this Dave.
I have only a few items of feedback:
31: Yes, we should clarify HTTP style redirects that contains XRIs
Can you take that?
73: Can we just make an explicit reference to SAML that talks about this concept of "negligible probability"?
We could, but it would be our first dependency on SAML. Seems like an odd place to start.
90: Shouldn't this be "would be constructed as "xr...@example2.home.base/foo.bar" (using a @ instead of an =)?
Good catch. I fixed by changing @ to = instead of the other way around.
106: Shouldn't the example XRI start with a "@"?
Yep. Changed to = to match fix above.
I haven't gone over the schema in detail - but we'll definitely want to do that just before publishing as a final technical check.
Yeah, I'd appreciate that. At this point the changes aren't too drastic so it's probably easier to look at a diff between the old and the new.
I just posted proposed errata that
1) Adds the ability to do "redirects" at the XML level during resolution, and 2) Adds an ID attribute at the root of the XRIDescriptor.
The redirect issue was mostly an oversight. I intended to have it in the original spec and just overlooked it. The proposal adds a new element, xri:AlternativeXRI, explains the behavior associated with this element and clarifies the intent of xri:Mapping.
The ID attribute makes it easy to unambiguously refer to the XRIDescriptor's root in XPath. The trusted res draft makes use of this attribute.
I'm not sure what the process is for approving errata, but comments are welcome while we sort out the logistics.
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.