[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-792) 8.4 Deep Insert: how to handle href attribute
[ https://issues.oasis-open.org/browse/ODATA-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralf Handl updated ODATA-792:
-----------------------------
Proposal:
Clients MAY provide any valid IRI, e.g. odata:dummy.
Services MUST ignore the provided href attribute value.
Use odata:dummy in example 22, lines 5 and 20
was:
Clients MAY provide any valid IRI, e.g. odata:dummy.
Services MUST ignore the provided href attribute value.
> 8.4 Deep Insert: how to handle href attribute
> ---------------------------------------------
>
> Key: ODATA-792
> URL: https://issues.oasis-open.org/browse/ODATA-792
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Bug
> Components: OData ATOM Format
> Affects Versions: V4.0_CS02
> Reporter: Ralf Handl
> Fix For: V4.0_CSD04
>
>
> New related entities are specified using the same representation as for an expanded navigation property, i.e. as an atom:link element. This element requires an href attribute with a valid IRI value.
> Which href value should consumers provide? They cannot know (in all cases) what the final URI of the newly created entity will be
--
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]