[OASIS Issue Tracker] Commented: (ODATA-497) Make type prefix optional for URL literals

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

    [ http://tools.oasis-open.org/issues/browse/ODATA-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34530#action_34530 ] 

Ralf Handl commented on ODATA-497:
----------------------------------

Wouldn't parsers/AST generators need metadata anyway to determine whether

   Address/Street

is a) valid and b1) a property of a complex property or b2) a property of a related entity?

> Make type prefix optional for URL literals
> ------------------------------------------
>
>                 Key: ODATA-497
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-497
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ABNF Construction Rules, OData URL Conventions 
>    Affects Versions: V4.0_CS
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.1_WD01
>
>
> Currently we require literals for e.g. Date and DateTimeOffset to be prefixed with a type identifier, e.g.
>    $filter=StartDate ge date'2013-09-02'
> In most cases the type of the literal can be deduced from the context, e.g. type of other comparison operand. 
> The only case in which this cannot be done is when comparing two literals, which is rare.
> So we can make the prefixes at least optional, or even completely get rid of them

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