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] Created: (ODATA-453) deal with KEY function


deal with KEY function
----------------------

                 Key: ODATA-453
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-453
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: OData ABNF Construction Rules
    Affects Versions: V4.0_CSD01
            Reporter: Michael Pizzo
             Fix For: V4.0_CSD02


today the KEY function can be used to pass a reference to an existing entity as a parameter value. i.e.;

~foo(KEY(Customers('ALFKI')))

The name "KEY" is poor; really this is similar to the urlref annotation expression.

We want a way to pass relative to the root of the service or the "current" entity.

Option 1: rename "KEY" to "urlref" and constrain this to only take the canonical url of an entity for 4.0 (we can relax this in the future). url may be relative to the service if it starts with "/", otherwise it's relative to the "current" resource. only support as a function parameter (as today). 

Option 2: Allow use of a first member expression rooted at current instance, or / for relative to root service. so

~foo(entity=$root/Customers('ALFKI'))

rooted at service always uses "/"

/Orders/ns.foo(entity=$root/Customers('ALFKI'))

/Orders/ns.foo(entity

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

        


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