[OASIS Issue Tracker] Updated: (ODATA-366) Clarify whether server-generated properties can be omitted in POST, even if they are not nullable

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

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

Ralf Handl updated ODATA-366:
-----------------------------

             Proposal: 
Protocol section "11.5.2.2 Create Related Entities When Creating an Entity" states

"Properties computed by the service, along with properties of related entities that are tied to key properties of the principal entity by a referential constraint, MAY be omitted from the request. If the inline representation contains a value for a computed or dependent property, the service MUST ignore that value when creating the related entity."

Split that statement and move the "computed" part to the enclosing section "11.5.2 Create an Entity" because it is true in general.

Also refer to the term StoreGeneratedPattern in the Core vocabulary as a means for clients to find out which properties are computed by the service.

OPTIONAL: Simplify the term to two tagging terms with more intuitive names:

<Term Name="Computed" Type="Core.Tag" DefaultValue="true" AppliesTo="Property" />
<Term Name="Immutable" Type="Core.Tag" DefaultValue="true" AppliesTo="Property" />
          Environment: [Proposed]
          Component/s: OData Protocol 
                           (was: OData ATOM Format )
                           (was: OData JSON Format)
        Fix Version/s: V4.0_CSD02
    Affects Version/s: V4.0_CSD01
                           (was: V4.0_WD01)

> Clarify whether server-generated properties can be omitted in POST, even if they are not nullable
> -------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-366
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-366
>             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
>
>
> It is conventional to define primary key properties (and other properties such as "creationTime") as non-nullable.
> However if properties (such as primary keys) are server-generated, the client cannot provide an appropriate initial value in POST.
> The spec appears to be silent on this issue.
> What should be done?
> (1) Define the properties as nullable, and require the client to pass null values on POST.
> (2) Define the properties as nullable, and allow the client to omit them from the payload (even for a "complete" entity) on POST.
> (3) Define the properties as non-nullable, and require the client to pass junk values on POST.
> (4) Define the properties as non-nullable, and allow the client to omit them from the payload (even for a "complete" entity) on POST.
> It might help to understand what variations are supported (or "intended" to be supported) by OData V1-V3 in this respect, before we proceed to make a poposal for V4.

-- 
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