Extend applicability of Core.MediaType and Core.AcceptableMediaTypes to non-stream (string/binary) properties and terms

XMLWordPrintable

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

      Proposed

    • Hide

      Change the description of Core.MediaType and Core.AcceptableMediaTypes to state that it is also applicable to regular (non-stream) properties of type Edm.Binary or Edm.String, and change the AppliesTo so those terms can be applicable to Term elements of type Edm.Binary or Edm.String.

      Show
      Change the description of Core.MediaType and Core.AcceptableMediaTypes to state that it is also applicable to regular (non-stream) properties of type Edm.Binary or Edm.String, and change the AppliesTo so those terms can be applicable to Term elements of type Edm.Binary or Edm.String.
    • Hide

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

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

       

      Show
      https://github.com/oasis-tcs/odata-vocabularies/pull/58/files https://github.com/oasis-tcs/odata-vocabularies/pull/61/files  

      We have some cases where the value of a String-typed Term may be expected to contain JSON, XML or SQL (i.e. the annotation values have a constrained media type).

      It would be helpful if we could change the description of Core.MediaType and Core.AcceptableMediaTypes to state that it is also applicable to regular (non-stream) properties of type Edm.Binary or Edm.String, as well as changing the AppliesTo so those terms can be applicable to Term elements of type Edm.Binary or Edm.String.

            Assignee:
            Unassigned
            Reporter:
            evan.ireland.2
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: