-
Type: Bug
-
Status: Closed
-
Priority: Minor
-
Resolution: Fixed
-
Component/s: Core
-
Labels:None
-
Proposal:
OSLC Core 2.0 provides clear guidance on client and server treatment of unknown properties.
I can't find any statement about unknown properties in OSLC Core 3.0, but the old, and outdated changes-from-v2 supporting document says: "Unknown properties and content MUST NOT be ignored by servers or clients" and references LDP.
LDP says:
4.2.4.4 If an otherwise valid HTTP PUT request is received that contains properties the server chooses not to persist, e.g. unknown content, LDP servers must respond with an appropriate 4xx range status code ??[RFC7231. LDP servers should provide a corresponding response body containing information about which properties could not be persisted. The format of the 4xx response body is not constrained by LDP. LDP servers expose these application-specific constraints as described in section 4.2.1 General.
We should discuss this and see what the intent should be and if there is any need to clarify in OSLC Core 3.0.