[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-892) Clarify dynamic properties support in $filter, $orderby, $expand
[ https://issues.oasis-open.org/browse/ODATA-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Pizzo updated ODATA-892:
--------------------------------
Proposal:
Add to section 5.1.17 Path Expressions:
"If the property (or navigation property) is not defined for the type of the resource, and that type is defined supports dynamic properties (navigation properties), then the property (or navigation property) is treated as null for all instances on which it has no value."
"If the property (or navigation property) is not defined for the type of the resource, and that type does not support dynamic properties (navigation properties), then the request may be considered malformed."
In section 5.1.2, System Query Option $expand, replace:
"The navigationProperty segment MUST identify a navigation property defined on the entity type of the request, the derived entity type specified in the type cast, or the last complex type identified by the complex property path. "
with:
"If the type does not support dynamic navigation properties, then the navigationProperty segment MUST identify a navigation property defined on the entity type of the request, the derived entity type specified in the type cast, or the last complex type identified by the complex property path. Otherwise, if the type does support dynamic navigation properties, if the navigationProperty segment does not identify a declared navigation property, the expanded property appears only for those instance on which it has a value."
(more specifically: at any point in the path, if a segment does not match a member of the previous segment, then the type of the previous segment must allow dynamic properties.)
was:
Add to section 5.1.17 Path Expressions:
"If the property (or navigation property) is not defined for the type of the resource, and that type is defined supports dynamic properties (navigation properties), then the property (or navigation property) is treated as null for all instances on which it has no value."
"If the property (or navigation property) is not defined for the type of the resource, and that type does not support dynamic properties (navigation properties), then the request may be considered malformed."
In section 5.1.2, System Query Option $expand, replace:
"The navigationProperty segment MUST identify a navigation property defined on the entity type of the request, the derived entity type specified in the type cast, or the last complex type identified by the complex property path. "
with:
"If the type does not support dynamic navigation properties, then the navigationProperty segment MUST identify a navigation property defined on the entity type of the request, the derived entity type specified in the type cast, or the last complex type identified by the complex property path. Otherwise, if the type does support dynamic navigation properties, if the navigationProperty segment does not identify a declared navigation property, the expanded property appears only for those instance on which it has a value."
> Clarify dynamic properties support in $filter, $orderby, $expand
> ----------------------------------------------------------------
>
> Key: ODATA-892
> URL: https://issues.oasis-open.org/browse/ODATA-892
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Bug
> Components: OData URL Conventions
> Affects Versions: V4.0_ERRATA02
> Environment: [Proposed]
> Reporter: Michael Pizzo
> Fix For: V4.0_ERRATA03
>
>
> Section 5.1.1.7 Path Expressions in [URL] describes how properties and navigation properties can be used as operands or function parameters.
> We do not explicitly call out (as we do in $select) how dynamic properties are treated.
--
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]