[OASIS Issue Tracker] (ODATA-660) Clarify whether or not PATCH can be used to update a primitive property using its edit URL

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

     [ https://tools.oasis-open.org/issues/browse/ODATA-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-660:
--------------------------------

    Proposal: 
We want to give direction to the client to use PUT for this. Services can support PATCH -- that would be outside of the pattern we are prescribing for updating a primitive property, but there is no reason for us to explicitly prohibit it.

Propose no change.

  was:We want to give direction to the client to use PUT for this. Services can support PATCH -- that would be outside of the pattern we are prescribing for updating a primitive property, but there is no reason for us to explicitly prohibit it.


> Clarify whether or not PATCH can be used to update a primitive property using its edit URL
> ------------------------------------------------------------------------------------------
>
>                 Key: ODATA-660
>                 URL: https://tools.oasis-open.org/issues/browse/ODATA-660
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol 
>    Affects Versions: V4.0_OS
>         Environment: [Applied]
>            Reporter: Matthew Borges
>            Assignee: Michael Pizzo
>            Priority: Minor
>             Fix For: V4.0_ERRATA01
>
>
> Section 11.4.9.1 only mentions PUT as a method for updating a primitive property using its edit URL.  Sections 11.4.9.3 and 11.4.9.4 specifically mention the rules regarding both PUT and PATCH.
> We should clarify whether or not PATCH is allowed in 11.4.9.1.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)