No minimal requirements for the "service" ?

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Affects Version/s: OData JSON Format for Common Schema Definition Language (CSDL) Version 4.0
    • Component/s: Public reviews
    • None
    • Environment:

      Conformance

      The conformance clause for "service" is conditional to only those artifacts (models?) that the service chooses to "expose". Does that mean in fact that a service can decide to NOT support any or some of these artifacts? Shouldn't there be a minimum set of features that a service MUST always support, if only for interoperability? (just asking) - because right now I could claim conformance with a "service" that simply chooses to not expose anything?

            Assignee:
            Unassigned
            Reporter:
            Jacques Durand (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: