← Prev in month ← Prev in thread

[OASIS Issue Tracker] Commented: (ODATA-472) Explicitly state how dynamic properties are represented if they are not defined on an entity

From
OASIS Issues Tracker <>
Date
2013-09-23T22:09:51+00:00
ID
523781248.14321379974240143.JavaMail.tomcat@customer-jira
Thread
[OASIS Issue Tracker] Commented: (ODATA-472) Explicitly state how dynamic properties are represented if they are not defined on an entity
[ http://tools.oasis-open.org/issues/browse/ODATA-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34727#action_34727 ] 

Michael Pizzo commented on ODATA-472:
-------------------------------------

I agree with all but the last point in the proposal. If a type is open it should be valid to ask for any property, whether it exists on any instance or not.

For open properties, the set of properties is really data-dependent, and having queries that fail based on data is bad practice.

For example, if I try and select a particular property, but happen to have filtered out all instances that support that particular property, it should not be an error.

> Explicitly state how dynamic properties are represented if they are not defined on an entity
> --------------------------------------------------------------------------------------------
>
>                 Key: ODATA-472
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-472
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ATOM Format , OData JSON Format, OData Protocol 
>    Affects Versions: V4.0_CS01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_CSD03
>
>


-- 
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
← Prev in month ← Prev in thread