Explicitly mention dynamic navigation properties in [Core]

XMLWordPrintable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Minor
    • V4.0_WD01
    • Affects Version/s: V4.0_WD01
    • Component/s: Protocol
    • None
    • Environment:

      [Proposed]

    • Hide

      New wording in Section 3, Data Model, describing navigation properties:

      Entities may have relationships to other entities, represented in entity types as navigation properties. Navigation properties are generally defined as part of an entity type, but may also appear on entity instances as undeclared dynamic navigation properties. Relationships may be addressed directly through a navigation link representing the relationship itself. Each relationship has a cardinality.

      Show
      New wording in Section 3, Data Model, describing navigation properties: Entities may have relationships to other entities, represented in entity types as navigation properties. Navigation properties are generally defined as part of an entity type, but may also appear on entity instances as undeclared dynamic navigation properties. Relationships may be addressed directly through a navigation link representing the relationship itself. Each relationship has a cardinality.
    • Hide

      Taking out of proposed state.

      We already agreed, in ODATA-74, to document support of open navigation properties, so I don't we don't need a proposal to add to OData Core; instead we need an issue to track any new semantics around open navigation properties (for example, optionally being able to specify the type/set of a navigation property, use of the URL for POST/PUT, or the use of open navigation properties in $filter or $expand.).

      Keeping this issue open to track any proposed semantics around open navigation properties.

      Applied:https://www.oasis-open.org/committees/download.php/48216/odata-core-v1.0-wd01-part1-protocol-2013-2-11-MP.docx
      New wording in Section 3:
      Entities may have relationships to other entities, represented as navigation properties. Navigation properties are generally defined as part of an entity type, but may also appear on entity instances as undeclared dynamic navigation properties

      Accepted: https://www.oasis-open.org/committees/download.php/48549/odata-meeting-29_on-20130314-minutes.html#odata-129

      Show
      Taking out of proposed state. We already agreed, in ODATA-74 , to document support of open navigation properties, so I don't we don't need a proposal to add to OData Core; instead we need an issue to track any new semantics around open navigation properties (for example, optionally being able to specify the type/set of a navigation property, use of the URL for POST/PUT, or the use of open navigation properties in $filter or $expand.). Keeping this issue open to track any proposed semantics around open navigation properties. Applied: https://www.oasis-open.org/committees/download.php/48216/odata-core-v1.0-wd01-part1-protocol-2013-2-11-MP.docx New wording in Section 3: Entities may have relationships to other entities, represented as navigation properties. Navigation properties are generally defined as part of an entity type, but may also appear on entity instances as undeclared dynamic navigation properties Accepted: https://www.oasis-open.org/committees/download.php/48549/odata-meeting-29_on-20130314-minutes.html#odata-129

      This is a clone of ODATA-74 (https://tools.oasis-open.org/issues/browse/ODATA-74) which clarifies that types may have open navigation properties that aren't explicitly mentioned. The application of ODATA-74 applies this change to CSDL. This issue is to track any required changes to [Core] so that we can accept/close the applied changes to ODATA-74.

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

              Created:
              Updated:
              Resolved: