[OASIS Issue Tracker] (ODATA-847) Clarification: use of Schema namespace aliases within URLs

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

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

Ralf Handl updated ODATA-847:
-----------------------------

    Proposal: 
Clarify that the aliases used in urls must be defined in the $metadata document of the service. Aliases defined in referenced documents are out of scope.



  was:
Clarify that the aliases used in urls must be defined in the $metadata document of the service. Aliases defined in referenced metadata documents are out of scope.




> Clarification: use of Schema namespace aliases within URLs
> ----------------------------------------------------------
>
>                 Key: ODATA-847
>                 URL: https://issues.oasis-open.org/browse/ODATA-847
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL, OData URL Conventions
>    Affects Versions: V4.0_ERRATA02
>            Reporter: Evan Ireland
>            Priority: Minor
>             Fix For: V4.0_ERRATA03
>
>
> CSDL spec section 3.4.2 states:
> "An alias is only valid within the document in which it is declared; a referencing document has to define its own aliases with the edmx:Include element."
> Protocol spec section "11.2.4.1 System Query Option $select" states:
> "The value of the $select query option is a comma-separated list of properties, qualified action names, qualified function names, the star operator (*), or the star operator prefixed with the namespace or alias of the schema in order to specify all operations defined in the schema."
> So now we see that aliases can be valid/referenced outside their defining document.
> If a URL uses an alias, is it limited to using an alias defined in the outermost CSDL document, i.e. it a URL prohibited from using aliases defined within referenced CSDL documents? If it is not so limited, then how do we resolve ambiguity of potentially multiple-defined aliases (defined with two different meanings in referncing and referenced CSDL documents)?



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)