Changes to OData4.0 CSD03

Changes to Normative Text

Appendix B of all prose documents: changed date for CSD03 from 2013-10-xx to 2013-10-03

Filling in the correct day does not add or remove a feature, so it is a non-material change.

Part 1: Protocol

Sections 8.2.7.5, 11.2.5.2, and 11.2.5.5: replaced "entities" with "items" in several places

$orderby is not limited to collections of entities, so "item" is less misleading.

Making this explicit does not add or remove a feature, so it is a non-material change.

Sections 11.2.5.1, 11.2.5.2, and 11.2.5.9: replaced "elements" with "items" in several places

In most places the "things" within a collection are called "item" to avoid confusion with "XML element". This section was forgotten during the cleanup.

Consistently using the same term does not add or remove a feature, so it is a non-material change.

Section 11.2.3.1: Added reference to [OData-ABNF]

The text just said "ABNF rules".

Expressing this more clearly does not add or remove a feature, so it is a non-material change.

Section 11.2.5.2: Explicitly state effect of multiple expressions in $orderby

Expressions are evaluated left to right, and then used to sort items that do not differ in the preceding expression values.

Making this explicit does not add or remove a feature, so it is a non-material change.

Section 11.2.8: Changed /$entity to $entity

The text continues with "relative to the service root", and the service root already ends with a /.

Correcting this typo does not add or remove a feature, so it is a non-material change.

Section 11.7.1: Changed /$batch to $batch

The text continues with "relative to the service root", and the service root already ends with a /.

Correcting this typo does not add or remove a feature, so it is a non-material change.

Part 2: URL Conventions

Section 4.3.4: Changed /$entity to $entity

The text continues with "relative to the service root", and the service root already ends with a /.

Correcting this typo does not add or remove a feature, so it is a non-material change.

Section 4.8: Reformulated text for resource path suffix /$count

Adapted text to match text for path suffix /$value.

Expressing this consistently does not add or remove a feature, so it is a non-material change.

Section 4.10: Reformulated text for resource path suffix /$value

The text said "a path segment containing the string $value", and in fact the path suffix is /$value.

Expressing this more clearly does not add or remove a feature, so it is a non-material change.

Section 5.1.1.2.5: Deleted superfluous = sign

The text said "returns = NaN".

Expressing this more clearly does not add or remove a feature, so it is a non-material change.

Section 5.1.1.3: Changed straight double quotes to typographical double quotes

The straight quotes were hard to distinguish from the enclosed code fragment.

Expressing this more clearly does not add or remove a feature, so it is a non-material change.

Section 5.1.1.4.29: Explained abbreviation WKT

The abbreviation is used only once and was never explained.

Expressing this more clearly does not add or remove a feature, so it is a non-material change.

Part 3: CSDL

Sections 7.1.5 and 15.1: Replaced "multiplicity" with "cardinality"

The other specification documents consistently use "cardinality".

Expressing this consistently does not add or remove a feature, so it is a non-material change.

Section 10.1.1 Move paragraph to Section 10.1

Section 10.1.1 describes the Name attribute of an enumeration type. The second paragraph describes the edm:Member element that is a child of the edm:EnumType element described in 10.1, and should go there (error was likely introduced as a result of promoting the paragraph describing the Name attribute to its own subsection).

Moving this paragraph does not add or remove a feature, so it is a non-material change.

Sections 14.4.4.1: Deleted superfluous comma

Correcting this typo does not add or remove a feature, so it is a non-material change.

EDMX Schema MetadataService.edmx

EntityType Term: Added navigation property “BaseTerm”

The navigation property should have been added when applying ODATA-535.

Correcting this typo does not add or remove a feature, so it is a non-material change.

ComplexType Collection:BaseType changed to AnnotationExpression

This should have been changed when applyingODATA-436.

Correcting this typo does not add or remove a feature, so it is a non-material change.

Org.OData.Core.V1.xml

Added comment with "title page" material

The comment allows recognizing the XML file as part of OData Version 4.0 and links to the TC page.

Adding the comment does not add or remove a feature, so it is a non-material change.

Changed descriptive text of term RequiresType

The text did not clearly convey the meaning of the term.

Correcting the description does not add or remove a feature, so it is a non-material change.

Org.OData.Capabilities.V1.xml

Added comment with "title page" material

The comment allows recognizing the XML file as part of OData Version 4.0 and links to the TC page.

Adding the comment does not add or remove a feature, so it is a non-material change.

Changed value of Uri attribute in edmx:Reference element

The value was a link to the CS01 copy instead of a link to the future publishing location of the CS02 copy.

Changing the link does not add or remove a feature, so it is a non-material change.

Changed descriptive text of properties in complex type NavigationPropertyRestriction

The text for properties NavigationProperty and Navigability did not clearly convey the meaning of the properties.

Correcting the description does not add or remove a feature, so it is a non-material change.

odata-abnf-construction-rules.txt

Changed comment with "title page" material

Added link to TC page and aligned comment text with title page of prose specification documents.

Changing the comment does not add or remove a feature, so it is a non-material change.

odata-abnf-testcases.xml

Changed comment with "title page" material

Added link to TC page and aligned comment text with title page of prose specification documents.

Changing the comment does not add or remove a feature, so it is a non-material change.

Org.OData.Measures.V1.xml

Added comment with "title page" material

The comment allows recognizing the XML file as part of OData Version 4.0 and links to the TC page.

Adding the comment does not add or remove a feature, so it is a non-material change.

Changed value of Uri attribute in edmx:Reference element

The value was a link to the CS01 copy instead of a link to the future publishing location of the CS02 copy.

Changing the link does not add or remove a feature, so it is a non-material change.

XML Schema edmx.xsd

Added comment with "title page" material

The comment allows recognizing the XML file as part of OData Version 4.0 and links to the TC page.

Adding the comment does not add or remove a feature, so it is a non-material change.

XML Schema edm.xsd

Added comment with "title page" material

The comment allows recognizing the XML file as part of OData Version 4.0 and links to the TC page.

Adding the comment does not add or remove a feature, so it is a non-material change.

Atom Format

Section 4.2: replaced "entries" with "items"

Entry has a special meaning in Atom that does not apply here.

Using the neutral term does not add or remove a feature, so it is a non-material change.

XML Schema metadata.xsd

Added comment with "title page" material

The comment allows recognizing the XML file as part of OData Version 4.0 and links to the TC page.

Adding the comment does not add or remove a feature, so it is a non-material change.

Changes to Non-Normative Examples

Examples are explicitly called out as non-normative in the last section of chapter 1 in each document.

Changing the non-normative examples does not add or remove a feature and constitutes an error correction, so it is a non-material change.

Part 3: CSDL

Section 15.4, Example 74: added missing single quotes

Stringkey values need to be enclosed in single quotes.

Section 15.7, Picture: Addedarrow for attribute BaseTerm

The arrowshould have beenadded when applyingODATA-535.

Section 15.7, Examples 83 and 84: changed data for term OptimisticConcurrency

The examples should have been adapted when applying ODATA-531.

Section 15.7, Example 84: removed Annotation within Collection

This should have been changed when applyingODATA-436.

JSON Format

Chapter 14, Example 30: Consistent indentation

Removed blanks to consistently indent by two spaces per level.

Unchanged Documents

  • None