odata message

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

From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
To: odata@lists.oasis-open.org
Date: Tue, 16 Oct 2012 03:50:24 -0400 (EDT)

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