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.
Accepted: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/47020/latest/odata_meeting-9_on-20120927_minutes.html
Improvement
Minor