Next in thread → Next in month →

[OASIS Issue Tracker] (ODATA-1084) Rule searchWord is too restrictive

From
OASIS Issues Tracker <>
Date
2017-06-20T14:44:07+00:00
ID
Thread
[OASIS Issue Tracker] (ODATA-1084) Rule searchWord is too restrictive
[ https://issues.oasis-open.org/browse/ODATA-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-1084:
------------------------------

    Resolution: 
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/4.01%20spec/ABNF/odata-abnf-construction-rules.txt?op=diff&rev=1052
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/4.01%20spec/ABNF/odata-abnf-testcases.xml?op=diff&rev=1052

  was:
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-aggregation-abnf.txt?op=diff&rev=1052
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-aggregation-testcases.xml?op=diff&rev=105


> Rule searchWord is too restrictive
> ----------------------------------
>
>                 Key: ODATA-1084
>                 URL: https://issues.oasis-open.org/browse/ODATA-1084
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: ABNF Construction Rules
>    Affects Versions: V4.01_CSD01
>         Environment: Proposed and optimistically applied
>            Reporter: Ralf Handl
>             Fix For: V4.01_CSD02
>
>
> The searchWord rule is overly restrictive as it only allows ALPHA and DIGIT whereas the comment states that any Unicode letter or number is allowed.
> In other places where the ABNF does not exactly describe the syntax, it allows a superset that is then further restricted by the prose specification.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
Next in thread → Next in month →