OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (ODATA-635) Clarify if a PUT request is allowed to change the odata.type of the entity (public comment c201403e00002)


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

Stefan Drees updated ODATA-635:
-------------------------------

    Summary: Clarify if  a PUT request is allowed to change the odata.type of the entity (public comment c201403e00002)  (was: Clarify if  a PUT request allowed to change the odata.type of the entity (public comment c201403e00002))

> Clarify if  a PUT request is allowed to change the odata.type of the entity (public comment c201403e00002)
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-635
>                 URL: https://tools.oasis-open.org/issues/browse/ODATA-635
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>            Reporter: Stefan Drees
>
> We received the public Comment #20140300002 on 2014-03-27 with title "Non-updatable properties?".
> Text was:
> """
> From
> http://docs.oasis-open.org/odata/odata/v4.0/os/part1-protocol/odata-v4.0-os-part1-protocol.html#_Toc372793719,
> section 11.4.3 Update An Entity
> “Key and other non-updatable properties, as well as dependent properties
> that are not tied to key properties of the principal entity, can be
> omitted from the request. If the request contains a value for one of
> these properties, the service MUST ignore that value when applying the
> update.”
> Is there a definition of what “other non-updatable properties” means
> elsewhere in the spec?  I haven’t had much success finding a reference.
> I’m trying to understand this section of the spec to answer a specific
> use case:
> Is a PUT request allowed to change the odata.type of the entity?
> Clearly this is not allowed by PATCH and MERGE because they operate on
> the original object, but for PUT I’m not sure. I would like to say no,
> the entity type should not be altered in any kind of update, but since
> PUT requires complete replacement of the original entity, constructing a
> different type in its place is not beyond the realm of possibility.
> Are there OData implementations that allow changing the type of an
> entity in a PUT?
> Thoughts?
> """



--
This message was sent by Atlassian JIRA
(v6.1.1#6155)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]