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:comment-tabpanel&focusedCommentId=61781#comment-61781 ] 

Ralf Handl commented on ODATA-906:
----------------------------------

We represent <Include> as name-value pairs of the "schemas" object whose value is a JSON Reference to a resource describing the included schema/namespace. If the <Include> element defines an alias we add another name-value pair for the alias with the same JSON reference as its value (here "Vocabulary1"):

    "schemas": {
        "ODataDemo": {
            "$ref": "http://host/service/$metadata#/schemas/ODataDemo";
        },
        "Some.Vocabulary.V1": {
            "$ref": "http://somewhere/Vocabulary/V1#/schemas/Some.Vocabulary.V1";
        },
        "Vocabulary1": {
            "$ref": "http://somewhere/Vocabulary/V1#/schemas/Some.Vocabulary.V1";
        },

We could embed an annotation @odata.isDefaultNamespace in this reference:

    "schemas": {
        "ODataDemo": {
            "$ref": "http://host/service/$metadata#/schemas/ODataDemo";
        },
        "Some.Vocabulary.V1": {
            "$ref": "http://somewhere/Vocabulary/V1#/schemas/Some.Vocabulary.V1";,
            "@odata.isDefaultNamespace": true
        },
        "Vocabulary1": {
            "$ref": "http://somewhere/Vocabulary/V1#/schemas/Some.Vocabulary.V1";
        },

If we have two name-value pairs - for the namespace as well as its alias - it is probably sufficient to annotate only the namespace one as we ultimately want to determine the namespace-qualified name.

> 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 Protocol
>    Affects Versions: V4.0_ERRATA02
>            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]