[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (ODATA-77) Are Edm primitive type names case-insensitive?
[ http://tools.oasis-open.org/issues/browse/ODATA-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31371#action_31371 ]
Ralf Handl commented on ODATA-77:
---------------------------------
Unfortunately, ABNF defines that strings enclosed in double quotes are case-insensitivie, see http://tools.ietf.org/html/rfc5234#section-2.3, and doesn't provide a means for literally stating case-insensitive strings
So our rules would have to look like
primitiveTypeName = [ %x45.64.6d "." ] ; Edm.
( %x42.69.6e.61.72.79 ; Binary
/ ...
)
If we go for case-sensitivity, I'd prefer the CamelCase names used in section 3.5 of the CSDL specification.
> Are Edm primitive type names case-insensitive?
> ----------------------------------------------
>
> Key: ODATA-77
> URL: http://tools.oasis-open.org/issues/browse/ODATA-77
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Bug
> Components: OData ABNF Construction Rules v1.0, OData CSDL v1.0
> Affects Versions: WD01
> Environment: [Proposed]
> Reporter: Ralf Handl
> Assignee: Michael Pizzo
> Priority: Minor
> Fix For: WD01
>
>
> The current ABNF defines the Edm primitive type names case-insensitive, yet all examples use Edm.Binary etc.
> As they only appear within null'Xxx', isof() and cast() expressions, case doesn't matter as long as we reserve the "Edm" namespace in all case variants.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]