[OASIS Issue Tracker] Created: (ODATA-371) Clearly describe behavior of PUT for structural and navigation properties

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

Clearly describe behavior of PUT for structural and navigation properties
-------------------------------------------------------------------------

                 Key: ODATA-371
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-371
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData Protocol 
    Affects Versions: V4.0_CSD01
         Environment: [Proposed]
            Reporter: Evan Ireland
             Fix For: V4.0_CSD02


Would it be fair to assume that because the section 8.5.4 uses the word "MAY", that if a client does not provide any bindings for navigation properties when using "PUT", the relationship(s) should remain unaffected?

The JSON spec section 8.5.4 states:

  "For update operations a bind operation on a collection navigation property adds additional relationships, it does not replace existing relationships."

The protocol spec section 11.4.3 "Update an Entity" states:

  "Services that support PUT MUST replace all property values with those specified in the request body. Missing properties MUST be set to their default values."

Is that only meant to apply to structural properties (if so, perhaps we should state it explicitly)? Because otherwise, it seems to conflict with the JSON section 8.5.4.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira