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

XML

Word

Printable

Proposal:

Hide

Redefine the maxdatetime/mindatetime/now rules to use OPEN and CLOSE thus permitting %-encoded parentheses.

Show
Redefine the maxdatetime/mindatetime/now rules to use OPEN and CLOSE thus permitting %-encoded parentheses.

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.