[OASIS Issue Tracker] (OSLCCORE-178) Treatment of unknown properties needs to be reviewed and clarified

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

James Amsden created OSLCCORE-178:
-------------------------------------

             Summary: Treatment of unknown properties needs to be reviewed and clarified
                 Key: OSLCCORE-178
                 URL: https://issues.oasis-open.org/browse/OSLCCORE-178
             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
          Issue Type: Bug
          Components: Core
            Reporter: James Amsden
            Assignee: James Amsden


[OSLC Core 2.0|http://open-services.net/bin/view/Main/OslcCoreSpecification#Unknown_properties_and_content] 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|https://tools.oasis-open.org/version-control/browse/wsvn/oslc-core/trunk/supporting-docs/changes-from-v2.html#diff-from-2]Âsays: "Unknown properties and content MUST NOT be ignored by servers or clients" and references LDP.

[LDP|https://www.w3.org/TR/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|https://www.w3.org/TR/ldp/#dfn-ldp-server] _must_ respond with an appropriate 4xx range status code [??[RFC7231|https://www.w3.org/TR/ldp/#bib-RFC7231]??]. [LDP servers|https://www.w3.org/TR/ldp/#dfn-ldp-server] _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|https://www.w3.org/TR/ldp/#ldpr-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.



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)