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

Rules "ordinalIndex" and "complexColPath" are too restrictive: negative indexes and index with type-cast

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: V4.01_OS
    • Fix Version/s: V4.01_ERRATA01
    • Component/s: ABNF
    • Labels:
      None
    • Environment:

      Proposed

    • Proposal:
      Hide

      Allow negative values for index segments in paths.

      Allow index segments after type-cast segments.

      Rephrase optional path segments to not be empty.

      Show
      Allow negative values for index segments in paths. Allow index segments after type-cast segments. Rephrase optional path segments to not be empty.
    • Resolution:
      Hide

      https://github.com/oasis-tcs/odata-abnf/pull/29/files

       

      Show
      https://github.com/oasis-tcs/odata-abnf/pull/29/files  

      Description

      4.01 added the ability to index into ordered collections from the end, using negative values for index segments, see 11.2.6.8 Requesting an Individual Member of an Ordered Collection.

      The specification does not explicitly forbid this indexing after a type-cast segment, but it is not allowed by rule complexColPath. This seems to be an accident as it is also not mentioned in ODATA-820.

      Trivial: some optional path segments have empty alternatives, making them "doubly optional". This complicates automatic processing of the ABNF and is bad style.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              handl Ralf Handl
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: