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] (ODATA-1462) in operator should allow empty collection literals


Michael Pizzo created ODATA-1462:
------------------------------------

             Summary: in operator should allow empty collection literals
                 Key: ODATA-1462
                 URL: https://issues.oasis-open.org/browse/ODATA-1462
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: New Feature
          Components: ABNF
    Affects Versions: V4.01_OS
         Environment: [Proposed]

Â
            Reporter: Michael Pizzo
             Fix For: V4.01_ERRATA01


Currently, the ABNF requires that a collection literal used in an "in" clause requires at least one element:

Â

inExpr = RWS "in" RWS ( listExpr / commonExpr )

listExpr = OPEN BWS primitiveLiteral BWS *( COMMA BWS primitiveLiteral BWS ) CLOSE

Â

There may be scenarios in which the user intends to provide an empty collection (for example, to reflect that there are no items selected in a drop-down list box). This should evaluate to false.

Also, note that commonExpr may be empty, so it would seem we should have equal expressivity between commonExpr and listExpr



--
This message was sent by Atlassian Jira
(v8.3.3#803004)


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