OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Created: (ODATA-303) Support abstract entity types without key 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
         Environment: [Proposed]
            Reporter: Michael Pizzo

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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]