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-655) The atom:id element is mandatory, but clients (doing POST of a new entity) might not know an appropriate value


    [ https://tools.oasis-open.org/issues/browse/ODATA-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37489#comment-37489 ] 

Evan Ireland commented on ODATA-655:
------------------------------------

Note that atom:id must be a valid URI (minimally a scheme name and a colon). It cannot be an empty string.

We could use "unknown:”. It could be defined to mean a URI that you include where a URI is required, but the client does not or cannot know an appropriate value.

Or without defining a new URI scheme, we could use a urn:uuid:… value, e.g.

  “urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6”

(See http://tools.ietf.org/html/rfc4122)

In that case, we must be clear that if the client provides such an entity id, that the service is allowed to override it with a different id (e.g. one that includes key values, or some other scheme for non-canonical URLs).


> 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://tools.oasis-open.org/issues/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)


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