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

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

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

Ralf Handl commented on ODATA-1007:
-----------------------------------

CSDL 4.0 Errata03 states in section 3.3 Element edmx:Reference, http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part3-csdl/odata-v4.0-errata03-os-part3-csdl-complete.html#_Toc453752504

"All [...] named elements in scope [...] can be accessed [...] by their namespace-qualified names."

Section 3.4.2 Attribute Alias states

"[The alias] only provides a more convenient notation. Every model element that can be used via an alias-qualified name can alternatively also be used via its full namespace-qualified name."

This implies that the namespace-qualified name must be unique within a scope. Including the same namespace twice with different aliases would not allow using the namespace-qualified name instead of the alias-qualified name.

> 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: Bug
>          Components: OData CSDL JSON 
>    Affects Versions: V4.01_WD01
>            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)