[OASIS Issue Tracker] (ODATA-1007) Consider how to handle namespace conflicts in JSON CSDL format

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

Ralf Handl updated ODATA-1007:
------------------------------

     Issue Type: Improvement  (was: Bug)
    Environment: Proposed
       Proposal: 
Clarify in Part 3: CDSL that a namespace-qualified name must be unique within a scope (document plus directly referenced documents) and that a schema cannot be included twice via different URIs.

This follows from existing normative text that aliases are only shortcuts, alias-qualified names are interchangeable with namespace-qualified names, and that a schema cannot span more than one document.

> Consider how to handle namespace conflicts in JSON CSDL format
> --------------------------------------------------------------
>
>                 Key: ODATA-1007
>                 URL: https://issues.oasis-open.org/browse/ODATA-1007
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL JSON 
>    Affects Versions: V4.01_WD01
>         Environment: Proposed
>            Reporter: Michael Pizzo
>             Fix For: V4.01_WD01
>
>
> In our XML format we are able to define aliases for namespaces referenced in external metadata documents, which allows us to disambiguate cases where referenced metadata documents may use the same namespace name.
> In the JSON format we want to make things indexed by the namespace-qualified name, which makes it easy and natural to lookup by name.
> We need to figure out if/how we address the (presumably uncommon) scenario where two referenced metadata documents use the same name.



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