Equivalence of NavigationProperty and Singleton or EntitySet

XMLWordPrintable

    • Type: New Feature
    • Resolution: Unresolved
    • Priority: Major
    • V5.0
    • Affects Version/s: V4.01_CSD02
    • Component/s: CSDL JSON, CSDL XML
    • Hide

      There are two aspects of the proposal.

      1) Allow Properties to be declared within an EntityContainer.

      2) Deprecate contained Navigation Properties (ContainsTarget = True) in favor of using EntitySet and Singleton declarations within EntityType and ComplexType declarations.

      Show
      There are two aspects of the proposal. 1) Allow Properties to be declared within an EntityContainer. 2) Deprecate contained Navigation Properties (ContainsTarget = True) in favor of using EntitySet and Singleton declarations within EntityType and ComplexType declarations.

      A Service often needs to provide additional data, such as service name, organization, model version, ....  This can be defined in an entity type referenced by a Singleton in the service document, but there really is no need to define a separate type for this purpose or for the additional complexity.

      Currently the Service document (EntityContainer) is restricted to two specially defined property meta types: Singleton and EntitySet.  Assuming null for Singleton is allowed, ODATA-1183, the functionality of these types is equivalent to functionality provided by containment Navigation Properties.  

            Assignee:
            Unassigned
            Reporter:
            george.ericson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: