[ https://issues.oasis-open.org/browse/ODATA-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralf Handl updated ODATA-1085:
------------------------------
Description:
In ODATA-958 we decided to use the new abstract types Edm.AnyPropertyPath in terms of the Capabilities vocabulary.
Technically this requires to use Version="4.01" in the Edmx wrapper element (which we don't do yet).
Should we provide to "versions" of the Capabilities vocabulary, one restricted to Version="4.0" constructs, and one using Version="4.01"?
If yes, how should we do this technically: by creating a new schema name, e.g. Org.OData.Capabilities.V1_01, or by having two branches of the well-known current schema name. If the latter, which one is the "master" branch?
How should this be reflected in the OData Vocabularies work product: should we continue to publish CSDs for version 4.0 and in parallel have CSDs for version 4.01?
was:
In ODATA-958 we decided to use the new abstract types Edm.AnyPropertyPath in terms of the Capabilities vocabulary.
Technically this requires to use Version="4.01" in the Edmx wrapper element (which we don't do yet).
Should we provide to "versions" of the Capabilities vocabulary, one restricted to Version="4.0" constructs, and one using Version="4.01"?
If yes, how should we do this technically: by creating a new schema name, e.g. Org.OData.Capabilities.V1_01, or by having two branches of the well-known current schema name. If the latter, which one is the "master" branch?
> Decide how to use V4.01 features in OASIS vocabularies
> ------------------------------------------------------
>
> Key: ODATA-1085
> URL: https://issues.oasis-open.org/browse/ODATA-1085
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Task
> Components: URL Conventions
> Affects Versions: V4.0_CSD01
> Reporter: Ralf Handl
> Fix For: V4.01_CSD01, V4.0_CSD02
>
>
> In ODATA-958 we decided to use the new abstract types Edm.AnyPropertyPath in terms of the Capabilities vocabulary.
> Technically this requires to use Version="4.01" in the Edmx wrapper element (which we don't do yet).
> Should we provide to "versions" of the Capabilities vocabulary, one restricted to Version="4.0" constructs, and one using Version="4.01"?
> If yes, how should we do this technically: by creating a new schema name, e.g. Org.OData.Capabilities.V1_01, or by having two branches of the well-known current schema name. If the latter, which one is the "master" branch?
> How should this be reflected in the OData Vocabularies work product: should we continue to publish CSDs for version 4.0 and in parallel have CSDs for version 4.01?
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
