-
Type:
Improvement
-
Status: Closed
-
Priority:
Trivial
-
Resolution: Fixed
-
Affects Version/s: V4.0_WD01
-
Fix Version/s: V4.0_WD01
-
Component/s: ATOM Format
-
Labels:None
-
Environment:
[Proposed]
-
Proposal:
-
Resolution:
Field | Original Value | New Value |
---|---|---|
Proposal | See summary |
The metadata:type attribute is required for properties with types other than Edm.String Accepted: https://www.oasis-open.org/committees/download.php/48411/odata-meeting-27_on-20130228-minutes.html#odata-200 |
Description |
The metadata:type attribute is only required for complex properties with a declared type that has derived types. Using them also for primitive properties in the prominent example may mislead readers to think it is also required for primitive types. |
|
Status | New [ 10000 ] | Open [ 1 ] |
Summary | Remove metadata:type attribute from example in section 5.1 | Handling of metadata:type attribute |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Assignee | Ralf Handl [ ralfhandl ] |
Resolution |
https://www.oasis-open.org/committees/download.php/48441/odata-atom-format-v4.0-wd01-2013-03-05-RH.doc https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/metadata.xsd?rev=205 |
|
Status | Resolved [ 5 ] | Applied [ 10002 ] |
Reporter | Ralf Handl [ ralfhandl ] | Ralf Handl [ handl ] |
Assignee | Ralf Handl [ ralfhandl ] | Ralf Handl [ handl ] |
The rules are not clearly defined in the contribution, but the intent was that, if metadata:type is not specified, the type is assumed to be string. So it is optional for primitive types, but its absence implies string.
ATOM was intended to be self-describing. Currently you do not need metadata in order to interpret the payload. Not defining a specific meaning to metadata:type being missing for a primitive type would be the first case where metadata was required to interpret the ATOM payload.