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] (ODATA-895) Support keyless entities for singletons


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

Michael Pizzo updated ODATA-895:
--------------------------------

    Proposal: 
Relax the requirement that only abstract entity types aren't required to have keys, but require that any entity type used in a collection must have a key. 

Allow a singleton or single-valued containment navigation property to use a type without having to define an arbitrary/meaningless key property.

It is a breaking schema change to add/modify/remove a key in an entity definition. 

  was:
Relax the requirement that only abstract entity types aren't required to have keys, but require that any entity type used in a collection must have a key. 

It is a breaking schema change to add/modify/remove a key in an entity definition. 


> Support keyless entities for singletons
> ---------------------------------------
>
>                 Key: ODATA-895
>                 URL: https://issues.oasis-open.org/browse/ODATA-895
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>    Affects Versions: V4.0_ERRATA02
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.01_WD01
>
>
> Entity types that are used for singletons, or targets of a single-valued containment navigation property, don't need keys. Keys are only required when accessing an entity within a collection.
> We could consider relaxing the requirement that entity types used exclusively for singletons/single-valued containment nav props have keys. We would have to carefully think through the ramifications of doing this, but they should always be able to be accessed through their canonical URL without a key. 



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


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