[OASIS Issue Tracker] Updated: (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:all-tabpanel ]

Ralf Handl updated ODATA-77:
----------------------------

       Proposal: 
Treat them case-sensitive, using the CamelCasing from section 3.5 of the CSDL specification

Accepted: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/47096/latest/odata_meeting-10_on-20121004-minutes.html

  was:
Treat them case-insensitive in URLs and reserve the "Edm" namespace in all case variants

Accepted: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/47096/latest/odata_meeting-10_on-20121004-minutes.html

    Component/s:     (was: OData CSDL v1.0)

> 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
>    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