[OASIS Issue Tracker] Updated: (ODATA-140) Describe rules for accessing derived entity and complex types in URLs

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Ralf Handl updated ODATA-140:
-----------------------------

       Proposal: 
Any resource path or path expression identifying a collection of entities or complex type instances may be suffixed with "/" and the qualified name of a type derived from the declared type of the collection. The result will be restricted to instances of the derived type and may be empty.

Any resource path or path expression identifying a single entity or complex type instance may be suffixed with "/" and the qualified name of a type derived from the declared type of the identified resource. If used in a resource path and the identified resource is not an instance of the derived type, the request will result in a 404 Not Found error. If used in a path expression that is part of a boolean expression, the boolean expression will evaluate to false.

  was:Exactly describe desired restriction and cast expresssions in prose specification

    Environment: [Proposed]

> Describe rules for accessing derived entity and complex types in URLs
> ---------------------------------------------------------------------
>
>                 Key: ODATA-140
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-140
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData URL Conventions v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: WD01
>
>
> OData allows inheritance for entity types and complex types, and since V3 allows restricting to derived types in URLs, e.g.
> GET ~/Customers/Model.VipCustomer                 (restrict result to VipCustomer instances)
> GET ~/Customers/Model.VipCustomer(1)            (404 if customer 1 is no VipCustomer)
> GET ~/Customers(1)/Model.VipCustomer            (same as above)
> GET ~/Customers(1)/Address/Model.AddressWithLotsOfDetails/SomeDetailNotInPlainAddress/$value         (cast complex property to subtype, then follow path)
> The current ABNF rules allow the above resource paths, plus "casting" to derived types in system query options (curiously enough only for entity types, but not for complex types):
> GET ~/Customers?$filter=Model.VipCustomer/PercentageOfVipPromotionProductsOrdered gt 80          (false for all non-VipCustomers)

-- 
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