Make examples 8 (entity type) and 86 (record expression) consistent

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Minor
    • V4.01_CS02
    • Affects Version/s: V4.01_CS01
    • Component/s: CSDL JSON, CSDL XML
    • None
    • Environment:

      Proposed, optimistically applied

    • Hide

      Example 8:

      • Add navigation property "CostCenter"

      Example 86:

      • Reference example 8 in the example headline
      • Rename property "GivenName" to "FirstName" (FirstName is used in other examples)
      • Rename property "SurName" to "LastName" (LastName is used in another example)

      Note: this is a non-material change that only affects non-normative examples.

      Show
      Example 8: Add navigation property "CostCenter" Example 86: Reference example 8 in the example headline Rename property "GivenName" to "FirstName" (FirstName is used in other examples) Rename property "SurName" to "LastName" (LastName is used in another example) Note: this is a non-material change that only affects non-normative examples.
    • Show
      https://www.oasis-open.org/committees/download.php/66162/odata-csdl-json-v4.01-wd07-2019-11-05-redlined.docx https://www.oasis-open.org/committees/download.php/66163/odata-csdl-xml-v4.01-wd08-2019-11-05-redlined.docx

      Example 86 for record expressions wants to point out that there's no representation difference between structural properties and navigation properties. It does this so successfully that only the specification authors can tell which of the four properties are structural, and which are navigation

      We should give readers a hint.

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

              Created:
              Updated:
              Resolved: