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] Commented: (ODATA-497) Make type prefix optional for URL literals

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

Michael Pizzo commented on ODATA-497:

prefixing the literal so we know the type enables parsing/AST generation with minimal/no metadata.

> 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


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