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-1049) Content referencing in batch requests


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

Michael Pizzo updated ODATA-1049:
---------------------------------

    Proposal: 
Allow referencing values from response bodies in subsequent requests
- in $filter
- in request bodies of subsequent modification requests

Value references use JSON Pointer syntax to address parts of the response body, e,g.

$filter=City eq $42/Addresses/3/City

Point out that content-id value must not collide with $root or any other $ literal valid in expressions

  was:
Allow referencing values from response bodies in subsequent requests
- in $filter
- in request bodies of subsequent modification requests

Value references use JSON Pointer syntax to address parts of the response body, e,g.

$filter=City eq $42/Addresses/3/City


> Content referencing in batch requests
> -------------------------------------
>
>                 Key: ODATA-1049
>                 URL: https://issues.oasis-open.org/browse/ODATA-1049
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: New Feature
>          Components: Protocol
>    Affects Versions: V4.01_CSD01
>         Environment: Proposed
>            Reporter: Ralf Handl
>             Fix For: V4.01_CSD02
>
>
> If a data modification is implemented as an action, a subsequent GET request may need to use values from the action response body as parameters for a filter.



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