Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-60 Allow complex properties or components of complex properties as key parts
  3. ODATA-355

Define how property paths are represented in key part of URL

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: V4.0_WD01
    • Fix Version/s: V4.0_WD01
    • Component/s: ABNF, CSDL XML, URL Conventions
    • Labels:
      None
    • Environment:

      [Applied]

      Description

      The key of an entity is part of the URl path, so we can't use forward slashes for complex key parts:

      Problem(Header/ID=42) cannot be used as this defines two path segments Problem(Header and ID=42

      Alternatives:

      • Problem(Header%2fID=42) - Encode / as %2f
      • Problem(Header-ID=42) - Use a dash instead of /
      • Problem(Header.ID=42) - Use a dot instead of /
      • Problem/Header/ID=42 - Use forward slashes as key delimiters instead of parentheses
      • Reject ODATA-60 and disallow parts of complex properties as key values
      • Problem(42) - do not state property names in key expressions, instead require key values to appear in the order of the key definition

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: