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-479) Allow Content-ID referencing in request bodies for inserting links to newly created entities


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

Ralf Handl commented on ODATA-479:
----------------------------------

Both odata.id and odata.bind require URI values, either relative or absolute. Content-Ids can only contain unreserved characters (ALPHA / DIGIT / "-" / "." / "_" / "~"), so any character sequence matching a content-id reference pattern (i.e. starting with a $ and followed only by unreserved characters) either is a content-id reference or a resource relative to the batch request URL, i.e. a top-level resource. 

For collisions between content-id references and top-level system resources we already defined that the system resource wins, so adding this feature would not have undesirable side-effects for services that use conventional IDs.

The only problematic situation is for services that use unconventional IDs that start with the service root followed by a $.

> Allow Content-ID referencing in request bodies for inserting links to newly created entities
> --------------------------------------------------------------------------------------------
>
>                 Key: ODATA-479
>                 URL: https://issues.oasis-open.org/browse/ODATA-479
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Batch Processing Format, OData Protocol
>    Affects Versions: V4.0_CS01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_ERRATA03
>
>
> Object graphs that are not trees can require inserting links to entities that just have been created in the same change set. This can only be done with content-id references within request bodies.



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