atom feed6 messages in org.oasis-open.lists.xriUpdated error codes
FromSent OnAttachments
Tan, WilliamFeb 26, 2006 8:57 am.doc
Drummond ReedFeb 26, 2006 5:56 pm 
Tan, WilliamFeb 26, 2006 6:43 pm 
Drummond ReedFeb 27, 2006 7:00 pm 
Tan, WilliamFeb 27, 2006 8:25 pm 
Drummond ReedFeb 27, 2006 10:25 pm 
Subject:Updated error codes
From:Tan, William (Will@neustar.biz)
Date:Feb 26, 2006 8:57:40 am
List:org.oasis-open.lists.xri
Attachments:
doc00000.doc - 1.5MB

Hi Drummond,

Here's an updated error code table containing changes that we agreed upon on Thursday's TC call.

With regards to the interaction between AUTH_RES_NOT_FOUND and no-follow-ref, in order for me to understand it I divided it into 4 scenarios:

Let's set up a common QXRI =a*b, and the result of resolution is that =a's XRD has neither an $res*auth service nor a Ref element.

1. Proxy server is given a media type of xrds or xrds+saml with the no-follow-ref flag set -> return all the XRD's successfully resolved so far. Or should we return all the successfully resolved XRD's followed by AUTH_RES_NOT_FOUND? 2. Proxy server is given any other media type with no-follow-ref flag set -> return HTTP 200 with error message in text/plan or html. 3. Proxy server is given a media type of xrds or xrds+saml *without* no-follow-ref -> return *a's XRD followed by *b's XRD with status = AUTH_RES_NOT_FOUND (Isn't this the purpose of REF_NOT_FOUND?) 4. Proxy server is given any other media type *without* no-follow-ref -> return HTTP 200 with error message in text/plain or html.

Thoughts?

=wil (http://xri.net/=wil)