[OASIS Issue Tracker] Commented: (ODATA-77) Are Edm primitive type names case-insensitive?

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/ODATA-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31364#action_31364 ] 

Andrew Eisenberg commented on ODATA-77:
---------------------------------------

I believe that the ABNF defines the primitive type names as case-sensitive:

primitiveTypeName = ["edm."] (
 "binary" /
 "boolean" /
  .
  .

OData should treat all names (entitySetName, entityTypeName, complexTypeName, etc.), including primitiveTypeName, as case sensitive.

I'm agnostic on whether we use binary, Binary, or BINARY.



> 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