[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-753) Minor typo in references to bound function calls
Michael Pizzo created ODATA-753: ----------------------------------- Summary: Minor typo in references to bound function calls Key: ODATA-753 URL: https://issues.oasis-open.org/browse/ODATA-753 Project: OASIS Open Data Protocol (OData) TC Issue Type: Bug Components: OData URL Conventions Affects Versions: V4.0_ERRATA02 Environment: [Proposed] Reporter: Michael Pizzo Priority: Trivial Fix For: V4.0_ERRATA03 The second bullet in section 4.5.2 of [URL] references the following rules in [ABNF]: boundComplexFunctionCall, boundComplexColFunctionCall, boundEntityFunctionCall, boundEntityColFunctionCall, boundPrimitiveFunctionCall and boundPrimitiveColFunctionCall However, the actual rules in [ABNF] abbreviate "Function" as "Func": boundComplexFuncCall, boundComplexColFuncCall, boundEntityFuncCall, boundEntityColFunctionCall, boundPrimitiveFuncCall and boundPrimitiveColFuncCall Note that other functions in [ABNF] spell out "Function", as in: complexFunctionImportCall, complexColFunctionImportCall, entityFunctionImportCall, entityColFunctionImportCall, primitiveFunctionImportCall, and primitiveColFunctionImportCall So we could change the [ABNF] to consistently spell out "Function" or [URL] to use the abbreviations already in [ABNF]. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]