[OASIS Issue Tracker] Updated: (ODATA-434) Introduce path segment for cross-joins on entity-container level

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

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

Ralf Handl updated ODATA-434:
-----------------------------

    Environment: [Applied]  (was: [Applying])
     Resolution: 
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-construction-rules.txt?rev=377
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-testcases.xml?rev=377

> Introduce path segment for cross-joins on entity-container level
> ----------------------------------------------------------------
>
>                 Key: ODATA-434
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-434
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ABNF Construction Rules, OData URL Conventions 
>    Affects Versions: V4.0_CSD01
>         Environment: [Applied]
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>             Fix For: V4.0_CSD02
>
>
> The current URL convention allows querying the cross-join of entity sets via requests targeting the entity container.
> This leads to potential name clashes:
> 	GET ~/Foo.Fred.Waldo
> can be a query targeting the entity container Waldo in schema Foo.Fred, or a query targeting entity set Waldo in container Fred of schema Foo.
> This clash can be avoided by using a path segment, similar to the path segment /$all that we use to address the union of all entities in a container.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira