- From: Jonathan Rees <jar@creativecommons.org>
- Date: Tue, 24 Nov 2009 08:19:56 -0500
- To: AWWSW TF <public-awwsw@w3.org>
the remainder of the URI is
considered to be identifying data corresponding to a resource for
which that server might provide an HTTP interface
I misread this... I think it's actually OK, although the sentence is
hard to parse ("identifying data" vs. "data corresponding to ...") and
the use of the word "corresponding" is unfortunate because the word is
used for a different kind of correspondence elsewhere in the spec. So
I won't be sending a comment, at least not now.
But the description of GET is still screwed up. At least now I can ask
them to make GET consistent with the semantics given in the
registration (URI identifies resource, not data).
On Tue, Nov 24, 2009 at 8:02 AM, Jonathan Rees <jar@creativecommons.org> wrote:
> The section on the http: scheme is inconsistent on what the URI is
> supposed to identify. I will send a comment to the list asking for a
> correction.
Received on Tuesday, 24 November 2009 13:20:29 UTC