10.13: Simplify context URL for Property Value

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • V4.01_CSD02
    • Affects Version/s: V4.0_ERRATA03, V4.01_CSD01
    • Component/s: Protocol
    • None
    • Environment:

      Applied

    • Hide

      Allow the context URL pattern

      {context-url}#{type-name}{select-list}

      also for property values.

      If something more specific is desired, the pattern could be

      {context-url}

      #

      {entity-set}

      /

      {property-path} {select-list}
      Show
      Allow the context URL pattern {context-url}#{type-name}{select-list} also for property values. If something more specific is desired, the pattern could be {context-url} # {entity-set} / {property-path} {select-list}
    • Hide

      https://www.oasis-open.org/committees/download.php/60256/odata-v4.01-wd02-part1-protocol-2017-03-10.docx

      Show
      https://www.oasis-open.org/committees/download.php/60256/odata-v4.01-wd02-part1-protocol-2017-03-10.docx

      The context URL for a property value contains the keys of the entity.
      This seems overly specific as the context URL is a pointer to structural metadata, so why should it vary from entity to structurally identical entity?
      Note that the context URL for an entity does not contain the key, nor is it required that the key properties are always present in the response.

            Assignee:
            Unassigned
            Reporter:
            handl
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: