[OASIS Issue Tracker] (ODATA-655) The atom:id element is mandatory, but clients (doing POST of a new entity) might not know an appropriate value

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

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

Ralf Handl updated ODATA-655:
-----------------------------

    Proposal: Use the constant value odata:unknown  (was: Allow an empty element for atom:id when the client issues a POST request.
(Or some other text to distinguish this case).)

> The atom:id element is mandatory, but clients (doing POST of a new entity) might not know an appropriate value
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-655
>                 URL: https://issues.oasis-open.org/browse/ODATA-655
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ATOM Format 
>    Affects Versions: V4.0_CS02
>            Reporter: Evan Ireland
>             Fix For: V4.0_CSD04
>
>
> 6.2 Element atom:id
>   "The atom:id element MUST contain the entity-id"
> This is a problem for clients creating new entities. In the case of a server supporting canonical URLs, if some of the key properties are server-generated, the client won't know what is an appropriate entity-id.
> Also, the ATOM Syndication spec makes it clear that atom:entry must have an atom:id.
> For OData, we need to define what value a client should pass for atom:id (in POST) when atom:id is not knowable to the client.



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