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:comment-tabpanel&focusedCommentId=61504#comment-61504 ] 

Michael Pizzo commented on ODATA-895:

Yes; allowing singletons to be complex types would be another way to address the requirement, but we have a similar request for the target of a to 0..1 containment navigation property. I may want to define a type that is used as the target in a 0..1 containment navigation property, but (since it's 0..1) there is no need to define a key.

> 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
>            Reporter: Michael Pizzo
> 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

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