[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-98) 3.8 Representing Annotations: avoid the undefined terms "internally" and "externally"
[ http://tools.oasis-open.org/issues/browse/ODATA-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Biamonte updated ODATA-98:
--------------------------------
Proposal:
Section 3.8, paragraph after example
OLD: In general, it is possible to express an annotation internally or externally to a value. However, an annotation is always a name/value pair. Therefore, it can only be expressed within a JSON object. Some EDM constructs are not represented with JSON objects. Therefore some types may only be annotated externally.
NEW: Annotations are always expressed as name/value pairs. For entity data model constructs represented as JSON objects the annotation name/value pairs are placed within the object; for constructs represented as JSON arrays or primitives they are placed next to the annotated model construct.
Section 3.8.1, beginning of the section
OLD: This section applies when annotating a name/value pair for which the value is represented as a JSON object. Each annotation MUST be applied internally. Each annotation MUST be represented as a single name/value pair.
NEW: This section applies when annotating a name/value pair for which the value is represented as a JSON object. Each annotation MUST be applied within the object. Each annotation MUST be represented as a single name/value pair.
3.8.2, beginning of the section
OLD: This section applies when annotating a name/value pair for which the value is not represented as a JSON object. The set of all annotations that apply to this name/value pair MUST be applied externally. This set of annotations is represented as a single name/value pair.
NEW: This section applies when annotating a name/value pair for which the value is not represented as a JSON object. The set of all annotations that apply to this name/value pair MUST be be placed next to the annotated model construct. This set of annotations is represented as a single name/value pair.
was:
Section 3.8, paragraph after example
OLD: In general, it is possible to express an annotation internally or externally to a value. However, an annotation is always a name/value pair. Therefore, it can only be expressed within a JSON object. Some EDM constructs are not represented with JSON objects. Therefore some types may only be annotated externally.
NEW: Annotations are always expressed as name/value pairs. For entity data model constructs represented as JSON objects the annotation name/value pairs are placed within the object; for constructs represented as JSON arrays or primitives they are placed next to the annotated model construct.
Updated proposal to add changes to sections 3.8.1 and 3.8.2
> 3.8 Representing Annotations: avoid the undefined terms "internally" and "externally"
> -------------------------------------------------------------------------------------
>
> Key: ODATA-98
> URL: http://tools.oasis-open.org/issues/browse/ODATA-98
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Improvement
> Components: OData JSON Format v1.0
> Affects Versions: WD01
> Environment: [Proposed]
> Reporter: Mark Biamonte
> Priority: Minor
> Fix For: WD01
>
>
> Section 3.8 uses the phrase "express an annotation internally or externally" without defining the terms.
> Instead just point out that the representation of annotation depends on the representation of the annotated model construct.
--
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]