Aggregation vocabulary: Create container-level term for ApplySupported defaults

XMLWordPrintable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Minor
    • None
    • Affects Version/s: None
    • Component/s: Vocabularies
    • None
    • Environment:

      Proposed

    • Hide
      • Create new term at container with all settings from existing terms that do not reference individual properties:
      • Refactor the existing complex types used by the existing terms to be derived from base types used for the properties of the new container-level term.
      • naming pattern for container-level types: <name>Base instead of proposed Common<name>Type
      Show
      Create new term at container with all settings from existing terms that do not reference individual properties: Refactor the existing complex types used by the existing terms to be derived from base types used for the properties of the new container-level term. naming pattern for container-level types: <name>Base instead of proposed Common<name>Type
    • Hide

      https://github.com/oasis-tcs/odata-vocabularies/pull/127

      https://github.com/oasis-tcs/odata-vocabularies/pull/130

      Show
      https://github.com/oasis-tcs/odata-vocabularies/pull/127 https://github.com/oasis-tcs/odata-vocabularies/pull/130

      Currently, term ApplySupported can also be applied to entity containers, which the semantics that its settings propagate to all sets in the container except for those with their own annotation.

      A similar topic is discussed in ODATA-1412, where the approach is to introduce a dedicated term for specifying set capabilities at container-level that describes only the common capabilities and does not reference individual properties of the sets.

      The ways to describe core and aggregation capabilities at container level should be aligned.

            Assignee:
            Unassigned
            Reporter:
            gerald.krause1
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: