[OASIS Issue Tracker] (ODATA-1415) Allow Type of Singleton to be a Primitive, EnumType, or ComplexType

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

George Ericson created ODATA-1415:
-------------------------------------

             Summary: Allow Type of Singleton to be a Primitive, EnumType, or ComplexType
                 Key: ODATA-1415
                 URL: https://issues.oasis-open.org/browse/ODATA-1415
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: CSDL JSON , CSDL XML
    Affects Versions: V4.02_WD01
         Environment: Specification of service level attributes.
            Reporter: George Ericson


In the context of an EntityContainer, it is more difficult than necessary to include a service level property or set of properties.ÂÂ

For example, if we want to expose the service name as a simple string property in the entity container (i.e. as a Singleton).

We could add this to a *Details* entity type without a key, and then reference this via a Singleton. Then _GET_Â_get <service>/details/name._ÂIt would be more natural to simply _GETÂ<service>/name._ In another example, suppose we want to reuse this structure within other entity types. If *Details*Âis specified as aÂ_complex type_, then the natural thing is to define a scalarÂ_property_ *detail*Âwith type *Details*. However, if *Details* is an entity type, we instead use a scalarÂ_navigation property with attribute_Â_ContainsTarget=true_ _and annotate_ with Core._AutoExpand_Âto get the same behavior.

Â

Â

Â



--
This message was sent by Atlassian Jira
(v8.3.3#803004)