James M Snell wrote:
James Holderness wrote:
James M Snell wrote:
Having the ability to separate the edit and alternate URI's is very
important, particularly in cases where your public alternate URI is
being served up by a content distribution network or your edit API is
sitting behind a firewall.
It may be important to separate the edit and alternate URIs, but
that's not a feature of the existing spec (AFAIK). Section 5.2 describes
Not so much a "feature" as it is simply left unspecified. the IRI
returned in the Location header is used for editing the resource as per
5.2. The IRI returned in the [EMAIL PROTECTED] is used for public,read-only
...
(nit, and reminder to the editors:) HTTP doesn't use IRIs, it uses URIs.
The location header will always contain a URI, not an IRI (unless the
IRI happens to be a URI :-).
Best regards, Julian
