Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-363

specifiying selected properties in metadataurl is broken

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V4.0_WD01
    • Fix Version/s: V4.0_WD01
    • Component/s: Protocol
    • Labels:
      None
    • Environment:

      [Applied]

      Description

      The current metadataurl pattern for specifying a subset of properties is broken for selects on expanded navigation props.

      We need to know the projected properties in order to know, for example, whether missing navigation properties are omitted because they matched a convention (in which case they can be constructed on the client) or because they weren't selected (in which case they should not be constructed on the client because they may not match convention)..
      Also, we don't want to have to have the client parse select (and nested expands, etc.)

        Attachments

          Activity

          mikep Michael Pizzo (Inactive) created issue -
          sdrees Stefan Drees (Inactive) made changes -
          Field Original Value New Value
          Component/s OData URL Conventions [ 10270 ]
          Fix Version/s V4.0_WD01 [ 10247 ]
          Affects Version/s V4.0_WD01 [ 10247 ]
          Status New [ 10000 ] Open [ 1 ]
          sdrees Stefan Drees (Inactive) made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]
          sdrees Stefan Drees (Inactive) made changes -
          Environment [Proposed] [Resolved]
          ralfhandl Ralf Handl made changes -
          Environment [Resolved] [Applied]

            People

            • Assignee:
              Unassigned
              Reporter:
              mikep Michael Pizzo (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: