Changes to Normative Text - OASIS



Changes to OData 4.0 CSD03Changes to Normative TextAppendix B of all prose documents: changed date for CSD03 from 2013-10-xx to 2013-10-03Filling in the correct day does not add or remove a feature, so it is a non-material change.Part 1: ProtocolSection 5.1: protocol versions are compared as numbers HYPERLINK "" ODATA-548 clarifies that protocol versions are numbers.Making this explicit does not add or remove a feature, so it is a non-material change.Sections 8.2.7.5, 11.2.5.2, and 11.2.5.5: replaced “entities” with “items” in several placesServer-driven paging, $orderby and $count can be used with all collection-valued resources and are is not limited to collections of entities, so “itementities” is less misleading. Section 8.2.7.5 should have been changed when applying HYPERLINK "" ODATA-519, the other sections when applying HYPERLINK "" ODATA-375 and HYPERLINK "" ODATA-393.Expressing this more clearly 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 placesIn 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 $orderbyExpressions 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.5.5: Changed “An $count” to “A $count”Correcting this typo does not add or remove a feature, so it is a non-material change.Section 11.2.8: Changed /$entity to $entityThe 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 $batchThe 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 ConventionsSection 4.3.4: Changed /$entity to $entityThe 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 /$countAdapted 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 /$valueThe 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 = signThe 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 quotesThe 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 WKTThe 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: CSDLSections 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.1Section 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 commaCorrecting this typo does not add or remove a feature, so it is a non-material change.EDMX Schema MetadataService.edmxEntityType 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 plexType Collection: BaseType changed to AnnotationExpressionThis should have been changed when applying ODATA-436.Correcting this typo does not add or remove a feature, so it is a non-material .OData.Core.V1.xmlAdded comment with “title page” materialThe 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 RequiresTypeThe 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 .OData.Capabilities.V1.xmlAdded comment with “title page” materialThe 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 elementThe 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 NavigationPropertyRestrictionThe 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.txtChanged comment with “title page” materialAdded 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.Adapted rule for odata-maxversion header HYPERLINK "" ODATA-548 defines the pattern for future version numbers.Defining this now does not add or remove a feature for version 4.0, so it is a non-material change.odata-abnf-testcases.xmlChanged comment with “title page” materialAdded 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.Added test cases for odata-maxversion header HYPERLINK "" ODATA-548 defines the pattern for future version numbers.Defining this now does not add or remove a feature for version 4.0, so it is a non-material .OData.Measures.V1.xmlAdded comment with “title page” materialThe 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 elementThe 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.xsdAdded comment with “title page” materialThe 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.xsdAdded comment with “title page” materialThe 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.JSON FormatChapter 3: added list of defined format parameters with links to corresponding sectionsFeedback from the implementation team: the format parameters defined by the specification were sprinkled throughout the following sections and somewhat hard to find.Adding this list does not add or remove a feature, so it is a non-material change.Atom FormatSection 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.xsdAdded comment with “title page” materialThe 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 ExamplesExamples 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: CSDLSection 15.4, Example 74: added missing single quotesString key values need to be enclosed in single quotes.Section 15.7, Picture: Added arrow for attribute BaseTermThe arrow should have been added when applying ODATA-535.Section 15.7, Examples 83 and 84: changed data for term OptimisticConcurrencyThe examples should have been adapted when applying ODATA-531.Section 15.7, Example 84: removed Annotation within CollectionThis should have been changed when applying ODATA-436.JSON FormatChapter 8.3, Example 17: Removed double quotes around 42The value of odata.count is an Edm.Int64 number, and these are rendered as JSON numbers unless explicitly requested as IEEE754compatible. Two other examples showed the correct format.Chapter 14, Example 30: Consistent indentationRemoved blanks to consistently indent by two spaces per level.Unchanged DocumentsNone ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download