[OASIS Issue Tracker] (ODATA-683) Clients should be prepared to deal with new derived types

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

Michael Pizzo created ODATA-683:
-----------------------------------

             Summary: Clients should be prepared to deal with new derived types
                 Key: ODATA-683
                 URL: https://tools.oasis-open.org/issues/browse/ODATA-683
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: OData Protocol 
    Affects Versions: V4.0_OS
         Environment: [Proposed]
            Reporter: Michael Pizzo
            Priority: Minor
             Fix For: V4.0_ERRATA02


In metadata versioning we currently say that it's safe to add a new type as long as it "does not derive from any entity types exposed by existing entity sets, or returned by existing functions or actions"

This implies that it is not safe to add a new entity type that derives from an entity type used in an entity set/function/action. But this restriction is unnecessary, as clients should always be prepared for new types not specified in $metadata (for example, types of dynamic properties).

For such derived types, the payload will contain the @odata.type annotation with the qualified name of the metadata describing the type, and clients should always be prepared for such types.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)