[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-94) 9.1.1: edm:UnderlyingType should be optional in <EnumType> definition
[ http://tools.oasis-open.org/issues/browse/ODATA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralf Handl updated ODATA-94:
----------------------------
Description:
(related to: ODATA-53)
The current specification for the Edm:UnderlyingType attribute reads as follows:
"An enumeration type has an underlying type which specifies the allowable values for member mapping. The enumeration type MUST assign an value of Edm.Byte, Edm.SByte, Edm.Int16, Edm.Int32, or Edm.Int64 to the edm:UnderlyingType attribute. If the underlying type is not specified, a 32-bit integer MUST be used as the underlying type."
edm:UnderlyingTYpe attribute should be optional, as implied by the third sentence, so the "MUST" in the second sentence should be changed to "MAY".
Also, the text reads a bit strange after application of ODATA-53 ("...MUST assign *an* value"), and the enumeration type doesn't assign a value, the edm:UnderlyingType attribute MAY BE assigned a value.
Suggest rewording as per proposal.
was:
(related to: https://tools.oasis-open.org/issues/browse/ODATA-53)
The current specification for the Edm:UnderlyingType attribute reads as follows:
"An enumeration type has an underlying type which specifies the allowable values for member mapping. The enumeration type MUST assign an value of Edm.Byte, Edm.SByte, Edm.Int16, Edm.Int32, or Edm.Int64 to the edm:UnderlyingType attribute. If the underlying type is not specified, a 32-bit integer MUST be used as the underlying type."
edm:UnderlyingTYpe attribute should be optional, as implied by the third sentence, so the "MUST" in the second sentence should be changed to "MAY".
Also, the text reads a bit strange after application of ODATA-53 ("...MUST assign *an* value"), and the enumeration type doesn't assign a value, the edm:UnderlyingType attribute MAY BE assigned a value.
Suggest rewording as per proposal.
> 9.1.1: edm:UnderlyingType should be optional in <EnumType> definition
> ---------------------------------------------------------------------
>
> Key: ODATA-94
> URL: http://tools.oasis-open.org/issues/browse/ODATA-94
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Bug
> Components: OData CSDL v1.0
> Affects Versions: WD01
> Environment: [Proposed]
> Reporter: Michael Pizzo
> Assignee: Ralf Handl
> Fix For: WD01
>
>
> (related to: ODATA-53)
> The current specification for the Edm:UnderlyingType attribute reads as follows:
> "An enumeration type has an underlying type which specifies the allowable values for member mapping. The enumeration type MUST assign an value of Edm.Byte, Edm.SByte, Edm.Int16, Edm.Int32, or Edm.Int64 to the edm:UnderlyingType attribute. If the underlying type is not specified, a 32-bit integer MUST be used as the underlying type."
> edm:UnderlyingTYpe attribute should be optional, as implied by the third sentence, so the "MUST" in the second sentence should be changed to "MAY".
> Also, the text reads a bit strange after application of ODATA-53 ("...MUST assign *an* value"), and the enumeration type doesn't assign a value, the edm:UnderlyingType attribute MAY BE assigned a value.
> Suggest rewording as per proposal.
--
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]