Decide how to use V4.01 features in OASIS vocabularies

XMLWordPrintable

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Affects Version/s: V4.0_CSD01
    • Component/s: Vocabularies
    • None
    • Hide

      Deferred by unanimous consent 2017-7-6.

      In ODATA-958 we worked around the issue by defining the extension in a way that didn't require 4.01 syntax. We should try and do similar, and consider consequences on a case-by-case basis.

      Show
      Deferred by unanimous consent 2017-7-6. In ODATA-958 we worked around the issue by defining the extension in a way that didn't require 4.01 syntax. We should try and do similar, and consider consequences on a case-by-case basis.

      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?

            Assignee:
            Michael Pizzo (Inactive)
            Reporter:
            handl
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: