[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: ----------------------------- Labels: (was: AdoptionBlocker) Fix Version/s: V4.01_CSD01 V4.01_WD01 (was: V4.0_CSD02) Proposal: Embed the corresponding annotation within the JSON object representing a schema or reference to an included schema: { "$Version": "4.01", "$EntityContainer": "ODataDemo.DemoService", "$Reference": { "http://docs.oasis-open.org/odata/odata-vocabularies/v4.0/vocabularies/Org.OData.Core.V1.json": { "$Include": [ { "Org.OData.Core.V1.": "Core", "@Org.OData.Core.V1.DefaultNamespace": true } ] } }, "ODataDemo.": { "$kind": "Schema", "@Org.OData.Core.V1.DefaultNamespace": true }, was: 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 CSDL JSON > Environment: Proposed > Reporter: Michael Pizzo > Assignee: Michael Pizzo > Fix For: V4.01_CSD01, 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]