Re: today's meeting discussion on Create - wording proposal + fix scope of what's covered by the words

Per WG discussion and this email thread, I went ahead and made this change.

I took the text pretty much as-is from John and placed in 4.2.12 and
removed 5.4.8.1.

- Steve Speicher


On Mon, Jul 15, 2013 at 12:09 PM, John Arwe <johnarwe@us.ibm.com> wrote:

> Correction (thanks Steve)
>
> > LDPC servers *MUST* assign the default base-URI for [*RFC3987*<https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC3987>]
> relative-URI resolution to be the HTTP Request-URI when the resource
> already exists, and to the URI of the created resource when the request
> results in the creation of a new resource.
>
> should have read LDPR not LDPC, as in (corrected version)
>
> > LDPR servers *MUST* assign the default base-URI for [*RFC3987*<https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC3987>]
> relative-URI resolution to be the HTTP Request-URI when the resource
> already exists, and to the URI of the created resource when the request
> results in the creation of a new resource.
>
>  Best Regards, John
>
> Voice US 845-435-9470  BluePages<http://w3.ibm.com/jct03019wt/bluepages/simpleSearch.wss?searchBy=Internet+address&location=All+locations&searchFor=johnarwe>
> Tivoli OSLC Lead - Show me the Scenario
>
>
>
>
> From:        John Arwe/Poughkeepsie/IBM@IBMUS
> To:        public-ldp-wg@w3.org,
> Date:        07/15/2013 11:54 AM
> Subject:        today's meeting discussion on Create - wording proposal +
> fix scope of  what's covered by the words
> ------------------------------
>
>
>
> wrt to today's meeting discussion on Create, Steve pointed out afterward
> something that my quick scan of the editor's draft missed. *
> **https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-5_4_8_1*<https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-5_4_8_1>says (and this text is not at all new).
>
> > 5.4.8.1 For RDF representations, LDPC servers *MUST* assign the
> base-URI for [*RFC3987*<https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC3987>]
> relative-URI resolution to be the URI of the created subject resource.
>
> I think that is language that could cover the general create case.  It is
> listed under LDPC-POST however, which could lead a reasonable reader (not
> implementing POST, but allowing PUT-creates) to miss it and ultimately to
> argue that it applies only to LDPC-POST.
>
> I think our common understanding is that it should apply to all LDP
> "write" requests, so I propose moving it to 4.1 General (under 4 LDPRs) and
> changing it to read:
>
> > LDPC servers *MUST* assign the default base-URI for [*RFC3987*<https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#bib-RFC3987>]
> relative-URI resolution to be the HTTP Request-URI when the resource
> already exists, and to the URI of the created resource when the request
> results in the creation of a new resource.
>
> 3987 defers (in 6.5) to 3986 for relative references.  The language above
> makes it clear (via the explicit use of "default base URI" as a term of
> art, which is also the title of 3986 section 5.1.4 facilitating any "follow
> your nose" attempts) that we are not stepping on 5.1.1-5.1.3.  I.e. if the
> media type (say RDF/XML) contains a base URI, that gets used; if there's an
> encapsulating entity, ...; if retrieval context exists (HTTP GET), ...;
> else we get to say what the behavior is (we are the app, in 3986 terms),
> exactly as 5.1.4 warrants.  Moving it to LDPRs makes it cover PUT/PATCH for
> them as well.
>
>  Best Regards, John
>
> Voice US 845-435-9470  *BluePages*<http://w3.ibm.com/jct03019wt/bluepages/simpleSearch.wss?searchBy=Internet+address&location=All+locations&searchFor=johnarwe>
> Tivoli OSLC Lead - Show me the Scenario
>
>