OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (ODATA-906) Consider how to specify an included namespace as a default in JSON CSDL


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

Ralf Handl updated ODATA-906:
-----------------------------

    Environment: Proposed
       Proposal: 
Both document-defined and included namespaces are represented as properties of the /x-schemas object. The Core.DefaultNamespace annotation will in both cases be represented as a name/value pair within the object describing the namespace, e.g. 

    "x-schemas": {
        "Org.OData.Core.V1": {
            "uri": "http://localhost/examples/Org.OData.Core.V1.openapi.json";,
            "@Core.DefaultNamespace": true
        },
        "Core": {
            "aliasFor": "Org.OData.Core.V1"
        },
        "Org.OData.Measures.V1": {
            "uri": "http://localhost/examples/Org.OData.Measures.V1.openapi.json";
        },
        "UoM": {
            "aliasFor": "Org.OData.Measures.V1"
        },
        "ODataDemo": {
            "@Core.DefaultNamespace": true
        }
    },

> Consider how to specify an included namespace as a default in JSON CSDL
> -----------------------------------------------------------------------
>
>                 Key: ODATA-906
>                 URL: https://issues.oasis-open.org/browse/ODATA-906
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData JSON CSDL, OData Protocol
>    Affects Versions: V4.0_ERRATA02
>         Environment: Proposed
>            Reporter: Michael Pizzo
>            Assignee: Michael Pizzo
>              Labels: AdoptionBlocker
>             Fix For: V4.01_WD01
>
>
> In ODATA-812 we added the concept of a default namespace, and allowed annotations from these default namespaces to be represented without namespace qualification.  We said that the service defined certain namespaces as default in $metadata by annotating the <Include> element.
> While <Include> is not currently an annotatable element, there doesn't seem to be any problem making it annotatable. However, we have to consider how we would annotate this element in JSON CSDL.



--
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]