[OASIS Issue Tracker] (ODATA-783) Is it intentional that mindatetime/maxdatetime/now don't permit %-encoded parentheses in ABNF?

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

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

Ralf Handl updated ODATA-783:
-----------------------------

    Environment: [Applying]

> Is it intentional that mindatetime/maxdatetime/now don't permit %-encoded parentheses in ABNF?
> ----------------------------------------------------------------------------------------------
>
>                 Key: ODATA-783
>                 URL: https://issues.oasis-open.org/browse/ODATA-783
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ABNF Construction Rules
>    Affects Versions: V4.0_OS
>         Environment: [Applying]
>            Reporter: Evan Ireland
>            Priority: Minor
>             Fix For: V4.0_ERRATA03
>
>
> See ABNF for year:
>   yearMethodCallExpr               = 'year'               OPEN BWS commonExpr BWS CLOSE
> Then see ABNF for mindatetime/maxdatetime/now:
>   minDateTimeMethodCallExpr = 'mindatetime(' BWS ')'
>   maxDateTimeMethodCallExpr = 'maxdatetime(' BWS ')'
>   nowMethodCallExpr         = 'now(' BWS ')'
> Now OPEN and CLOSE are defined as:
>   OPEN  = "(" / "%28"
>   CLOSE = ")" / "%29"
> Thus permitting %-encoded parentheses for most functions except mindatetime/maxdatetime/now.
> If this is intentional, we should explain the rationale.
> If not intentional, then we should fix the ABNF construction rules.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)