Linked Data Platform 1.0 : 7.2 Preferences on the Prefer Request Header

good afternoon;

is there anywhere to be found a concise, normative logic tree for the application of the various content preference constituents?

the recommendation itself enumerates several uri, but restricts itself to several non-normative, non-exhaustive, strictly illustrative examples of their possible effects, based upon which the respective terms’ significance is less than clear.

for example, to pose a simple question, what would the consequence be for

    omit="http://www.w3.org/ns/ldp#PreferMinimalContainer”

?
it would appear, there are three aspects of the response content to which this should apply:
- the core content statements
- the containment/membership statements - including secondary assertions
- the (core) content of contained resources.

it would be useful to have a normative specification for the ways the appearance of the respective url(s) in prefer header(s) should affect the presence of the respective content in a response.

it is also difficult to discern the intent for recursive structures.
wrt delete operations, there are indications in the recommendation, but no clarity, beyond “may”.
wrt get responses, among the various ldp documents, the only evident mention is in a read-me for solid, which indicates the document construction is not recursive, but that seems a rather indirect specification.

both of these aspects would seem particularly important from an interoperability perspective.

best regards, from berlin,
---
james anderson | james@dydra.com | http://dydra.com

Received on Wednesday, 18 November 2015 11:39:28 UTC