[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-862) Represent all types as JSON Schema types, term definitions, parameters, return types, entity sets, singletons
[ https://issues.oasis-open.org/browse/ODATA-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralf Handl updated ODATA-862: ----------------------------- Resolution: https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/vocabularies/Org.OData.Aggregation.V1.json?op=diff&rev=746 https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/vocabularies/Org.OData.Capabilities.V1.json?op=diff&rev=746 https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/vocabularies/Org.OData.Core.V1.json?op=diff&rev=746 https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/vocabularies/Org.OData.Measures.V1.json?op=diff&rev=746 This change shows that many of the terms in our standard vocabularies are nullable: we should check whether this makes sense for the term semantics, especially for all of the tagging terms using type Core.Tag. > Represent all types as JSON Schema types, term definitions, parameters, return types, entity sets, singletons > ------------------------------------------------------------------------------------------------------------- > > Key: ODATA-862 > URL: https://issues.oasis-open.org/browse/ODATA-862 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData JSON CSDL > Affects Versions: V4.0_WD01 > Reporter: Ralf Handl > > The value of the "type" keyword should always be a JSON Schema (reference) instead of a qualified type name. -- 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]