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


Help: OASIS Mailing Lists Help | MarkMail Help

odata-comment message

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

Subject: Re: [odata-comment] Non-updatable properties?

Hello Danny,

I acknowledge receipt of your comments.
The Technical Committee will discuss this and respond soon.
Thank you for your comments.

All the best,
Stefan Drees.

Am 27.03.14 20:32, schrieb Danny Thorpe:
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

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?




*Danny Thorpe *

Authorization Architect

*Dell*| Identity & Access Management, Quest Software

Quest Software is now part of Dell.

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