Odata Version 4.0 Errata 01

OData Version 4.0 Errata 01

Working Draft 01

05 13 September 2013

Technical Committee: OASIS Open Data Protocol (OData) TC Chairs: Barbara Hartel ([email protected]), SAP AG Ram Jeyaraman ([email protected]), Microsoft Editors: Michael Pizzo ([email protected]), Microsoft Ralf Handl ([email protected]), SAP AG Martin Zurmuehl ([email protected]), SAP AG Additional artifacts: This prose specification is one component of a Work Product that also includes the following items which differ from the versions published with the OASIS Standard: XML schemas: (list file names or directory name) Other parts (list titles and/or file names) Note: TC Admin will include reference to the “complete” change-marked version, if the TC produces it. Related work: This specification lists Errata for: OData Version 4.0, a multi-part Work Product which includes: OData Version 4.0 Part 1: Protocol. Latest version. http://docs.oasis- open.org/odata/odata/v4.0/odata-v4.0-part1-protocol.html OData Version 4.0 Part 2: URL Conventions. Latest version. http://docs.oasis- open.org/odata/odata/v4.0/odata-v4.0-part2-url-conventions.html OData Version 4.0 Part 3: Common Schema Definition Language (CSDL). Latest version. http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part3-csdl.html ABNF components: OData ABNF Construction Rules Version 4.0 and OData ABNF Test Cases. 14 August 2013. http://docs.oasis-open.org/odata/odata/v4.0/cs01/abnf/ Vocabulary components: OData Core Vocabulary, OData Measures Vocabulary and OData Capabilities Vocabulary. 14 August 2013. http://docs.oasis- open.org/odata/odata/v4.0/cs01/vocabularies/ Note: TC Admin will set all references above to the OASIS Standard links. Abstract: This document lists Errata for OData Version 4.0. Status: This Working Draft (WD) has been produced by one or more TC Members; it has not yet been voted on by the TC or approved as a Committee Draft (Committee Specification Draft or a Committee Note Draft). The OASIS document Approval Process begins officially with a TC vote to approve a WD as a Committee Draft. A TC may approve a Working Draft, revise it, and re- approve it any number of times as a Committee Draft. Initial URI pattern: http://docs.oasis-open.org/odata/odata/v4.0/errata01/csd01/odata-v4.0-errata01-csd01.doc (Managed by OASIS TC Administration; please don’t modify.) odata-v4.0-errata01-wd01 Working Draft 01 05 September 2013 Standards Track Draft Copyright © OASIS Open 2013. All Rights Reserved. Page 1 of 20 Copyright © OASIS Open 2013. All Rights Reserved. All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

odata-v4.0-errata01-wd01 Working Draft 01 05 September 2013 Standards Track Draft Copyright © OASIS Open 2013. All Rights Reserved. Page 3 of 20 Appendix A. Introduction This document lists the approved changes to the OData Version 4.0 specification and contains one chapter per changed part of the specification. Additional documents containing the final specification text with these changes applied are also available and linked in section "Additional artifacts" on the title page.

odata-v4.0-errata01-wd01 Working Draft 01 05 September 2013 Standards Track Draft Copyright © OASIS Open 2013. All Rights Reserved. Page 4 of 20 A.1 Terminology The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [RFC2119].

odata-v4.0-errata01-wd01 Working Draft 01 05 September 2013 Standards Track Draft Copyright © OASIS Open 2013. All Rights Reserved. Page 5 of 20 A.2 Normative References [RFC2119] Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels”, BCP 14, RFC 2119, March 1997. http://www.ietf.org/rfc/rfc2119.txt. [OData-Protocol] OData Version 4.0 Part 1: Protocol. See link in “Related work” section on cover page.

odata-v4.0-errata01-wd01 Working Draft 01 05 September 2013 Standards Track Draft Copyright © OASIS Open 2013. All Rights Reserved. Page 6 of 20 1.1 Typographical Conventions Changes are described in tabular format. The first column refers to a point in the changed document. For prose specification this is the chapter or section number. For ABNF and XML files this is the line number of the SVN revision the change was applied in, and the. line number links to this SVN revision. The second column describes the changes shows original text in black. Inserted text is blue and underlined, removed text is red and striked through. It can contain instructions or references to a specific part of the section in italic and enclosed in square double brackets. The third column contains the JIRA issue number and links to the corresponding Jira issue, which in turn links to the SVN revision containing this change. Example for prose specifications: Sectio Change Issue n 3 Original text is black. Inserted text is blue and underlined, removed text is red and 504 striked through.

3.1.4 〚Instructions and other notations that are not the texts themselves are included in 506 these brackets.〛 Original text is black. Inserted text is blue and underlined, removed text is red and striked through. Example for ABNF and XML files: Line Change Issue 100 Original text is black. Inserted text is blue and underlined 504 removed text is red and striked through.lambdaPredicateExpr = boolCommonExpr ; containing at least one lambdaVariablePredicatePrefixExpr

200 Original text is black. 506 - 201 Inserted text is blue and underlined, removed text is red and striked through.

Sectio Change Issue n

4.4 〚Table line for Edm.Binary, column 2〛 484 Fixed-length or variable-length bBinary data 〚Table line for Edm.Stream, column 2〛 Fixed-length or variable-lengthBinary data stream 〚Table line for Edm.String, column 2〛 Fixed-length or variable-length sSequence of UTF-8 characters

4.4 〚Table line for Edm.Double, column 2〛 495 IEEE 754 binary64 fFloating-point number with(15-17 decimal digits)precision 〚Table line for Edm.Single, column 2〛 IEEE 754 binary32 fFloating-point number with 7 ( 6 - 9 decimal digits)precision

7.1.3 〚First sentence〛 499 The edm:NavigationProperty element MAY contain the Nullable attribute whose a Boolean value specifies whether a navigation target is required for the navigation property.

7.3 〚First sentence〛 489 A navigation property MAY define one edm:OnDelete element. It describes the action the service will take on related entities when the source entity on which the navigation property is defined is deleted.

13.6 〚Word "unbound" now links to section 12.2.3〛 511

13.6.2 〚Word "unbound" now links to section 12.2.3〛 511

14 〚Example 33, line 10 and following〛 486

Products( ID )

14.2 〚Second sentence〛 509 odata-v4.0-errata01-wd01 Working Draft 01 05 September 2013 Standards Track Draft Copyright © OASIS Open 2013. All Rights Reserved. Page 10 of 20 A term allows annotating a CSDL element or OData resource representation with additional data..

14.5.11 〚Example 63, line 3 and following〛 486 Supplier Category

14.5.13 〚Example 65, line 3 and following〛 486 CreatedAt ChangedAt

14.5.15 〚Example 67, line 13 and following〛 485

http://host/wiki/HowToUse

15.5 〚Example 78, response, line 10〛 510

"IsBoundindable":false, "IsComposable":false,

Line Change Issue 456 lambdaPredicateExpr = boolCommonExpr ; containing at least one 504 lambdaVariablePredicatePrefixExpr

853 day = ( "0" / "1" / "2" ) oneToNine 506 - 854 / ( "1" / "2" ) DIGIT / "3" ( "0" / "1" )

Line Change Issue

237 date'2012-09-10' date'2012-09-20'

Line Change Issue 223 488 251 488

680 488

odata-v4.0-errata01-wd01 Working Draft 01 05 September 2013 Standards Track Draft Copyright © OASIS Open 2013. All Rights Reserved. Page 18 of 20 Appendix L. Acknowledgments The contributions of the OASIS OData Technical Committee members, enumerated in Error: Reference source not found, are gratefully acknowledged.

Revision Date Editor Changes Made WD01 [Rev Date] Editors First version