ABNF for key values is overly generous

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Minor
    • V4.01_ERRATA01
    • Affects Version/s: V4.01_OS
    • Component/s: ABNF
    • None
    • Hide
      • Restrict key property values to literals of allowed types
      • Consistently name rules for these types
        • URL literals with suffix Literal
        • body values with suffix Value
        • no suffix where both representations are identical
      • Split rules for these types where differences exist, especially for representations with PLUS or COLON characters (no percent-encoding in values, allowed percent-encoding in literals)
      • Add test cases for full coverage
      Show
      Restrict key property values to literals of allowed types Consistently name rules for these types URL literals with suffix Literal body values with suffix Value no suffix where both representations are identical Split rules for these types where differences exist, especially for representations with PLUS or COLON characters (no percent-encoding in values, allowed percent-encoding in literals) Add test cases for full coverage
    • Show
      https://github.com/oasis-tcs/odata-abnf/pull/108

      ABNF rule keyPropertyValue is too generous and just references rule primitiveValue.

      It should explicitly list primitive values of the types allowed for key properties in 6.5 Key

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

              Created:
              Updated:
              Resolved: