31: Yes, we should clarify HTTP style redirects that contains XRIs
73: Can we just make an explicit reference to SAML that talks about this concept of "negligible probability"?
90: Shouldn't this be "would be constructed as "xr...@example2.home.base/foo.bar" (using a @ instead of an =)?
106: Shouldn't the example XRI start with a "@"?
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.
From: Dave McAlpin [mailto:dave...@epok.net]
Sent: Saturday, March 13, 2004 9:36 AM
Subject: [xri] Errata proposals
I just posted proposed errata that
1) Adds the ability to do "redirects" at the XML level during resolution,
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.