[OASIS Issue Tracker] Updated: (ODATA-303) Support abstract entity types without key properties

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

     [ http://tools.oasis-open.org/issues/browse/ODATA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-303:
--------------------------------

    Proposal: 
1) Clarify that abstract entities can only derive from other abstract entities
2) Specify that an entity with abstract=true does not need to define, or derive from a base type that has defined, a key property
3) Specify that an entity that does not specify abstract=true must define a key, or derive from a base type that has a key defined (directly or indirectly)
4) Specify that an EntityType with a base type that has a key defined, or is defined with abstract=true, does not need to define any properties

Note: the key must only be defined once. If a base type defines a key the derived type must not define the key

  was:
1) Clarify that abstract entities can only derive from other abstract entities
2) Specify that an entity with abstract=true does not need to define, or derive from a base type that has defined, a key property
3) Specify that an entity that does not specify abstract=true must define a key, or derive from a base type that has a key defined (directly or indirectly)
4) Specify that an EntityType with a base type that has a key defined, or is defined with abstract=true, does not need to define any properties


> Support abstract entity types without key properties
> ----------------------------------------------------
>
>                 Key: ODATA-303
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-303
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_WD01
>
>
> Today EntityTypes require key properties, and all entity types within a type hierarchy must have the same key.
> There are cases where it would be very useful to define abstract entity types without a key field, but define that they key fields must be specified before the entity type can be used in an entity set, following the exact same rules as we have defined for the new abstract base Edm.EntityType.
> In particular, this would allow an organization like schema.org to define an ontology in terms of abstract entities and relationships. A service would then have the choice of directly deriving from those types, specifying the keys used by that particular service (and potentially introducing additional properties), or using those types as terms and applying the terms to their model.
> I think this will be critical for organizations like schema.org to adopt odata vocabularies.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira