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-1120) Put entity set restrictions on NavigationPropertyDescriptions

    [ https://issues.oasis-open.org/browse/ODATA-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67804#comment-67804 ] 

Michael Pizzo commented on ODATA-1120:

We don't really need ExpandRestrictions, NavigationRestrictions, CountRestrictions as they already have property paths.

> Put entity set restrictions on NavigationPropertyDescriptions
> -------------------------------------------------------------
>                 Key: ODATA-1120
>                 URL: https://issues.oasis-open.org/browse/ODATA-1120
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: Vocabularies
>    Affects Versions: V4.01_CS01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.01_CS02, V4.0_CSD02
> In OData-958 we added FilterRestrictions and SortRestrictions to NavigationPropertyDescriptions.  This gave us a place to define such restrictions on collection-valued navigation properties.  However, we missed some other restrictions and, in OData-1055, proposed to add one of these (DeepInsertSupport) as an annotation that could be applied to a "Collection" (i.e., a collection-valued navigation property).  This has a number of issues:
> 1) It uses the new "Collection" value in AppliesTo, which we did not want to return to OData 4.0 clients,
> 2) It underspecifies where DeepInsertSupport can be applied (i.e., it doesn't make sense for collection-valued structural properties),
> 3) It creates multiple places for the client to look to figure out what it can/can't do for a particular navigation property
> 4) It puts the annotation on the navigation property within the type, which makes it difficult to re-use that type.
> A better, more consistent approach would be to add to NavigationPropertyRestrictions all of the restrictions we currently have for EntitySets.

This message was sent by Atlassian JIRA

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