ࡱ>  tbbjbjWW s55X{$$8282828282$\2\2\2P2d7\28 Vd W W W>X@%~}t ?AAAAAA$Xhe82>X>Xe8282 W W4zrrr82 W82 W?r?rr~+L W7n"w X+0   0 82xreer $ 0:  OData JSON Format Version 4.0 OASIS Standard 24 February 2014 Specification URIs This version:  HYPERLINK "http://docs.oasis-open.org/odata/odata-json-format/v4.0/os/odata-json-format-v4.0-os.doc" http://docs.oasis-open.org/odata/odata-json-format/v4.0/os/odata-json-format-v4.0-os.doc (Authoritative)  HYPERLINK "http://docs.oasis-open.org/odata/odata-json-format/v4.0/os/odata-json-format-v4.0-os.html" http://docs.oasis-open.org/odata/odata-json-format/v4.0/os/odata-json-format-v4.0-os.html  HYPERLINK "http://docs.oasis-open.org/odata/odata-json-format/v4.0/os/odata-json-format-v4.0-os.pdf" http://docs.oasis-open.org/odata/odata-json-format/v4.0/os/odata-json-format-v4.0-os.pdf Previous version:  HYPERLINK "http://docs.oasis-open.org/odata/odata-json-format/v4.0/cs01/odata-json-format-v4.0-cs01.doc" http://docs.oasis-open.org/odata/odata-json-format/v4.0/cs01/odata-json-format-v4.0-cs01.doc (Authoritative)  HYPERLINK "http://docs.oasis-open.org/odata/odata-json-format/v4.0/cs01/odata-json-format-v4.0-cs01.html" http://docs.oasis-open.org/odata/odata-json-format/v4.0/cs01/odata-json-format-v4.0-cs01.html  HYPERLINK "http://docs.oasis-open.org/odata/odata-json-format/v4.0/cs01/odata-json-format-v4.0-cs01.pdf" http://docs.oasis-open.org/odata/odata-json-format/v4.0/cs01/odata-json-format-v4.0-cs01.pdf Latest version:  HYPERLINK "http://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.doc" http://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.doc (Authoritative)  HYPERLINK "http://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.html" http://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.html  HYPERLINK "http://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.pdf" http://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.pdf Technical Committee: HYPERLINK "https://www.oasis-open.org/committees/odata/"OASIS Open Data Protocol (OData) TC Chairs: Barbara Hartel ( HYPERLINK "mailto:barbara.hartel@sap.com" barbara.hartel@sap.com),  HYPERLINK "http://www.sap.com/" SAP AG Ram Jeyaraman ( HYPERLINK "mailto:Ram.Jeyaraman@microsoft.com" Ram.Jeyaraman@microsoft.com),  HYPERLINK "http://www.microsoft.com/" Microsoft Editors: Ralf Handl ( HYPERLINK "mailto:ralf.handl@sap.com" ralf.handl@sap.com),  HYPERLINK "http://www.sap.com/" SAP AG Michael Pizzo ( HYPERLINK "mailto:mikep@microsoft.com" mikep@microsoft.com),  HYPERLINK "http://www.microsoft.com/" Microsoft Mark Biamonte ( HYPERLINK "mailto:mark.biamonte@progress.com" mark.biamonte@progress.com),  HYPERLINK "http://www.progress.com/" Progress Software Related work: This specification is related to: OData Version 4.0. Edited by Michael Pizzo, Ralf Handl, and Martin Zurmuehl. A multi-part Work Product which includes: OData Version 4.0 Part 1: Protocol. Latest version.  HYPERLINK "http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part1-protocol.html" 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.  HYPERLINK "http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part2-url-conventions.html" 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.  HYPERLINK "http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part3-csdl.html" 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. 24 February 2014.  HYPERLINK "http://docs.oasis-open.org/odata/odata/v4.0/os/abnf/" http://docs.oasis-open.org/odata/odata/v4.0/os/abnf/ Vocabulary components: OData Core Vocabulary, OData Measures Vocabulary and OData Capabilities Vocabulary. 24 February 2014. HYPERLINK "http://docs.oasis-open.org/odata/odata/v4.0/os/vocabularies/"http://docs.oasis-open.org/odata/odata/v4.0/os/vocabularies/ OData Atom Format Version 4.0. Edited by Martin Zurmuehl, Michael Pizzo, and Ralf Handl. Latest version.  HYPERLINK "http://docs.oasis-open.org/odata/odata-atom-format/v4.0/odata-atom-format-v4.0.html" http://docs.oasis-open.org/odata/odata-atom-format/v4.0/odata-atom-format-v4.0.html. Abstract: The Open Data Protocol (OData) for representing and interacting with structured content is comprised of a set of specifications. The core specification for the protocol is in OData Version 4.0 Part 1: Protocol. This document extends the core specification by defining representations for OData requests and responses using a JSON format. Status: This document was last revised or approved by the membership of OASIS on the above date. The level of approval is also listed above. Check the Latest version location noted above for possible later revisions of this document. Technical Committee members should send comments on this specification to the Technical Committees email list. Others should send comments to the Technical Committee by using the HYPERLINK "https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=odata"Send A Comment button on the Technical Committees web page at HYPERLINK "https://www.oasis-open.org/committees/odata/"https://www.oasis-open.org/committees/odata/. For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (HYPERLINK "https://www.oasis-open.org/committees/odata/ipr.php"https://www.oasis-open.org/committees/odata/ipr.php). Citation format: When referencing this specification the following citation format should be used: [OData-JSON-Format-v4.0] OData JSON Format Version 4.0. Edited by Ralf Handl, Michael Pizzo, and Mark Biamonte. 24 February 2014. OASIS Standard.  HYPERLINK "http://docs.oasis-open.org/odata/odata-json-format/v4.0/os/odata-json-format-v4.0-os.html" http://docs.oasis-open.org/odata/odata-json-format/v4.0/os/odata-json-format-v4.0-os.html. Latest version:  HYPERLINK "http://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.html" http://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.html. Notices Copyright OASIS Open 2014. 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 HYPERLINK "https://www.oasis-open.org/policies-guidelines/ipr"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. OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so. OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims. The name "OASIS" is a trademark of HYPERLINK "https://www.oasis-open.org/"OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see HYPERLINK "https://www.oasis-open.org/policies-guidelines/trademark"https://www.oasis-open.org/policies-guidelines/trademark for above guidance. Table of Contents  TOC \o "1-6" \h \z \u  HYPERLINK \l "_Toc372793034" 1 Introduction  PAGEREF _Toc372793034 \h 6  HYPERLINK \l "_Toc372793035" 1.1 Terminology  PAGEREF _Toc372793035 \h 6  HYPERLINK \l "_Toc372793036" 1.2 Normative References  PAGEREF _Toc372793036 \h 6  HYPERLINK \l "_Toc372793037" 1.3 Typographical Conventions  PAGEREF _Toc372793037 \h 7  HYPERLINK \l "_Toc372793038" 2 JSON Format Design  PAGEREF _Toc372793038 \h 8  HYPERLINK \l "_Toc372793039" 3 Requesting the JSON Format  PAGEREF _Toc372793039 \h 9  HYPERLINK \l "_Toc372793040" 3.1 Controlling the Amount of Control Information in Responses  PAGEREF _Toc372793040 \h 9  HYPERLINK \l "_Toc372793041" 3.1.1 odata.metadata=minimal  PAGEREF _Toc372793041 \h 9  HYPERLINK \l "_Toc372793042" 3.1.2 odata.metadata=full  PAGEREF _Toc372793042 \h 10  HYPERLINK \l "_Toc372793043" 3.1.3 odata.metadata=none  PAGEREF _Toc372793043 \h 10  HYPERLINK \l "_Toc372793044" 3.2 Controlling the Representation of Numbers  PAGEREF _Toc372793044 \h 10  HYPERLINK \l "_Toc372793045" 4 Common Characteristics  PAGEREF _Toc372793045 \h 12  HYPERLINK \l "_Toc372793046" 4.1 Header Content-Type  PAGEREF _Toc372793046 \h 12  HYPERLINK \l "_Toc372793047" 4.2 Message Body  PAGEREF _Toc372793047 \h 12  HYPERLINK \l "_Toc372793048" 4.3 Relative URLs  PAGEREF _Toc372793048 \h 12  HYPERLINK \l "_Toc372793049" 4.4 Payload Ordering Constraints  PAGEREF _Toc372793049 \h 13  HYPERLINK \l "_Toc372793050" 4.5 Control Information  PAGEREF _Toc372793050 \h 14  HYPERLINK \l "_Toc372793051" 4.5.1 Annotation odata.context  PAGEREF _Toc372793051 \h 14  HYPERLINK \l "_Toc372793052" 4.5.2 Annotation odata.metadataEtag  PAGEREF _Toc372793052 \h 14  HYPERLINK \l "_Toc372793053" 4.5.3 Annotation odata.type  PAGEREF _Toc372793053 \h 14  HYPERLINK \l "_Toc372793054" 4.5.4 Annotation odata.count  PAGEREF _Toc372793054 \h 15  HYPERLINK \l "_Toc372793055" 4.5.5 Annotation odata.nextLink  PAGEREF _Toc372793055 \h 15  HYPERLINK \l "_Toc372793056" 4.5.6 Annotation odata.deltaLink  PAGEREF _Toc372793056 \h 15  HYPERLINK \l "_Toc372793057" 4.5.7 Annotation odata.id  PAGEREF _Toc372793057 \h 16  HYPERLINK \l "_Toc372793058" 4.5.8 Annotation odata.editLink and odata.readLink  PAGEREF _Toc372793058 \h 16  HYPERLINK \l "_Toc372793059" 4.5.9 Annotation odata.etag  PAGEREF _Toc372793059 \h 17  HYPERLINK \l "_Toc372793060" 4.5.10 Annotation odata.navigationLink and odata.associationLink  PAGEREF _Toc372793060 \h 17  HYPERLINK \l "_Toc372793061" 4.5.11 Annotation odata.media*  PAGEREF _Toc372793061 \h 17  HYPERLINK \l "_Toc372793062" 5 Service Document  PAGEREF _Toc372793062 \h 18  HYPERLINK \l "_Toc372793063" 6 Entity  PAGEREF _Toc372793063 \h 20  HYPERLINK \l "_Toc372793064" 7 Structural Property  PAGEREF _Toc372793064 \h 21  HYPERLINK \l "_Toc372793065" 7.1 Primitive Value  PAGEREF _Toc372793065 \h 21  HYPERLINK \l "_Toc372793066" 7.2 Complex Value  PAGEREF _Toc372793066 \h 22  HYPERLINK \l "_Toc372793067" 7.3 Collection of Primitive Values  PAGEREF _Toc372793067 \h 22  HYPERLINK \l "_Toc372793068" 7.4 Collection of Complex Values  PAGEREF _Toc372793068 \h 22  HYPERLINK \l "_Toc372793069" 8 Navigation Property  PAGEREF _Toc372793069 \h 23  HYPERLINK \l "_Toc372793070" 8.1 Navigation Link  PAGEREF _Toc372793070 \h 23  HYPERLINK \l "_Toc372793071" 8.2 Association Link  PAGEREF _Toc372793071 \h 23  HYPERLINK \l "_Toc372793072" 8.3 Expanded Navigation Property  PAGEREF _Toc372793072 \h 23  HYPERLINK \l "_Toc372793073" 8.4 Deep Insert  PAGEREF _Toc372793073 \h 24  HYPERLINK \l "_Toc372793074" 8.5 Bind Operation  PAGEREF _Toc372793074 \h 24  HYPERLINK \l "_Toc372793075" 9 Stream Property  PAGEREF _Toc372793075 \h 25  HYPERLINK \l "_Toc372793076" 10 Media Entity  PAGEREF _Toc372793076 \h 26  HYPERLINK \l "_Toc372793077" 11 Individual Property  PAGEREF _Toc372793077 \h 27  HYPERLINK \l "_Toc372793078" 12 Collection of Entities  PAGEREF _Toc372793078 \h 28  HYPERLINK \l "_Toc372793079" 13 Entity Reference  PAGEREF _Toc372793079 \h 29  HYPERLINK \l "_Toc372793080" 14 Delta Response  PAGEREF _Toc372793080 \h 30  HYPERLINK \l "_Toc372793081" 14.1 Added/Changed Entity  PAGEREF _Toc372793081 \h 31  HYPERLINK \l "_Toc372793082" 14.2 Deleted Entity  PAGEREF _Toc372793082 \h 31  HYPERLINK \l "_Toc372793083" 14.3 Added Link  PAGEREF _Toc372793083 \h 31  HYPERLINK \l "_Toc372793084" 14.4 Deleted Link  PAGEREF _Toc372793084 \h 31  HYPERLINK \l "_Toc372793085" 15 Bound Function  PAGEREF _Toc372793085 \h 33  HYPERLINK \l "_Toc372793086" 16 Bound Action  PAGEREF _Toc372793086 \h 34  HYPERLINK \l "_Toc372793087" 17 Action Invocation  PAGEREF _Toc372793087 \h 35  HYPERLINK \l "_Toc372793088" 18 Instance Annotations  PAGEREF _Toc372793088 \h 36  HYPERLINK \l "_Toc372793089" 18.1 Annotate a JSON Object  PAGEREF _Toc372793089 \h 36  HYPERLINK \l "_Toc372793090" 18.2 Annotate a JSON Array or Primitive  PAGEREF _Toc372793090 \h 36  HYPERLINK \l "_Toc372793091" 19 Error Response  PAGEREF _Toc372793091 \h 37  HYPERLINK \l "_Toc372793092" 20 Extensibility  PAGEREF _Toc372793092 \h 38  HYPERLINK \l "_Toc372793093" 21 Security Considerations  PAGEREF _Toc372793093 \h 39  HYPERLINK \l "_Toc372793094" 22 Conformance  PAGEREF _Toc372793094 \h 40  HYPERLINK \l "_Toc372793095" Appendix A. Acknowledgments  PAGEREF _Toc372793095 \h 41  HYPERLINK \l "_Toc372793096" Appendix B. Revision History  PAGEREF _Toc372793096 \h 42  Introduction The OData protocol is comprised of a set of specifications for representing and interacting with structured content. The core specification for the protocol is in  REF odata \h [OData-Protocol]; this document is an extension of the core protocol. This document defines representations for the OData requests and responses using the JavaScript Object Notation (JSON), see  REF rfc4627 \h [RFC4627]. An OData JSON payload may represent: a  HYPERLINK \l "_Primitive_Value" single primitive value a  HYPERLINK \l "CollectionOfPrimitive" collection of primitive values a  HYPERLINK \l "ComplexValue" single complex type value a  HYPERLINK \l "_Collection_of_Complex" collection of complex type values a  HYPERLINK \l "_Entity" single entity or  HYPERLINK \l "ResourceReference" entity reference a  HYPERLINK \l "CollectionOfEntities" collection of entities or  HYPERLINK \l "_Entity_Reference" entity references a  HYPERLINK \l "DeltaResponse" collection of changes a  HYPERLINK \l "_Representing_the_Service" service document describing the top-level resources exposed by the service an  HYPERLINK \l "_Representing_Errors_in" error. 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  REF rfc2119 \h [RFC2119]. Normative References [GeoJSON] Butler, H., Daly, M., Doyle, A., Gillies, S., Schaub, T., Schmidt, C., "The GeoJSON Format Specification", Revision 1.0, June 2008.  HYPERLINK "http://geojson.org/geojson-spec.html" http://geojson.org/geojson-spec.html. [OData-ABNF] OData ABNF Construction Rules Version 4.0. See link in Related work section on cover page. [OData-CSDL] OData Version 4.0 Part 3: Common Schema Definition Language (CSDL). See link in Related work section on cover page. [OData-Protocol] OData Version 4.0 Part 1: Protocol. See link in Related work section on cover page. [OData-URL] OData Version 4.0 Part 2: URL Conventions. See link in "Related work" section on cover page. [OData-VocCap] OData Capabilities Vocabulary. See link in "Related work" section on cover page. [RFC2119] Bradner, S., Key words for use in RFCs to Indicate Requirement Levels, BCP 14, RFC 2119, March 1997.  HYPERLINK "http://www.ietf.org/rfc/rfc2119.txt" http://www.ietf.org/rfc/rfc2119.txt. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, Uniform Resource Identifier (URI): Generic Syntax, IETF RFC3986, January 2005.  HYPERLINK "http://www.ietf.org/rfc/rfc3986.txt" http://www.ietf.org/rfc/rfc3986.txt. [RFC3987] Duerst, M. and, M. Suignard, Internationalized Resource Identifiers (IRIs), RFC 3987, January 2005.  HYPERLINK "http://www.ietf.org/rfc/rfc3987.txt" http://www.ietf.org/rfc/rfc3987.txt. [RFC4627] Crockford, D., The application/json Media Type for JavaScript Object Notation (JSON), RFC 4627, July 2006.  HYPERLINK "http://tools.ietf.org/html/rfc4627" http://tools.ietf.org/html/rfc4627. [RFC5646] Phillips, A., Ed., and M. Davis, Ed., Tags for Identifying Languages, BCP 47, RFC 5646, September 2009.  HYPERLINK "http://tools.ietf.org/html/rfc5646" http://tools.ietf.org/html/rfc5646. [ECMAScript] ECMAScript Language Specification Edition 5,1. June 2011. Standard ECMA-262.  HYPERLINK "http://www.ecma-international.org/publications/standards/Ecma-262.htm" http://www.ecma-international.org/publications/standards/Ecma-262.htm. Typographical Conventions Keywords defined by this specification use this monospaced font. Normative source code uses this paragraph style. Some sections of this specification are illustrated with non-normative examples. Example  SEQ Example \* ARABIC 1: text describing an example uses this paragraph style Non-normative examples use this paragraph style. All examples in this document are non-normative and informative only. All other text is normative unless otherwise labeled. JSON Format Design JSON, as described in  REF rfc4627 \h [RFC4627], defines a text format for serializing structured data. Objects are serialized as an unordered collection of name-value pairs. JSON does not define any semantics around the name/value pairs that make up an object, nor does it define an extensibility mechanism for adding control information to a payload. ODatas JSON format extends JSON by defining general conventions for name-value pairs that annotate a JSON object, property or array. OData defines a set of canonical annotations for control information such as ids, types, and links, and custom annotations MAY be used to add domain-specific information to the payload. A key feature of ODatas JSON format is to allow omitting predictable parts of the wire format from the actual payload. To reconstitute this data on the receiving end, expressions are used to compute missing links, type information, and other control data. These expressions (together with the data on the wire) can be used by the client to compute predictable payload pieces as if they had been included on the wire directly. Annotations are used in JSON to capture control information that cannot be predicted (e.g., the next link of a collection) as well as a mechanism to provide values where a computed value would be wrong (e.g., if the media read link of one particular entity does not follow the standard URL conventions). Computing values from metadata expressions is compute intensive and some clients might opt for a larger payload size to avoid computational complexity; to accommodate for this the Accept header allows the client to control the amount of control information added to the response. To optimize streaming scenarios, there are a few restrictions that MAY be imposed on the sequence in which name/value pairs appear within JSON objects. For details on the ordering requirements see  HYPERLINK \l "_Payload_Ordering_Constraints_1" Payload Ordering Constraints. Requesting the JSON Format The OData JSON format can be requested using the $format query option in the request URL with the MIME type application/json, optionally followed by format parameters, or the case-insensitive abbreviation json which MUST NOT be followed by format parameters. Alternatively, this format can be requested using the Accept header with the MIME type application/json, optionally followed by format parameters. If specified, $format overrides any value specified in the Accept header. Possible format parameters are:  HYPERLINK \l "_Controlling_the_Amount" odata.metadata  HYPERLINK \l "_Controlling_the_Representation" IEEE754Compatible  HYPERLINK \l "_Payload_Ordering_Constraints_1" odata.streaming Services SHOULD advertise the supported MIME types by annotating the entity container with the term Capabilities.SupportedFormats defined in  REF VocCapabilities \h [OData-VocCap], listing all available formats and combinations of supported format parameters. Controlling the Amount of Control Information in Responses The amount of  HYPERLINK \l "_Control_Information" control information needed (or desired) in the payload depends on the client application and device. The odata.metadata parameter can be applied to the Accept header of an OData request to influence how much control information will be included in the response. Other Accept header parameters (e.g., odata.streaming) are orthogonal to the odata.metadata parameter and are therefore not mentioned in this section. If a client prefers a very small wire size and is intelligent enough to compute data using metadata expressions, the Accept header should include  HYPERLINK \l "_odata=minimalmetadata" odata.metadata=minimal. If compute is more expensive than wire size or the client is incapable of computing control information,  HYPERLINK \l "_odata.metadata=full" odata.metadata=full directs the service to inline the control information that normally would be computed from metadata expressions in the payload.  HYPERLINK \l "_odata=nometadata" odata.metadata=none is an option for clients that have out-of-band knowledge or don't require control information. odata.metadata=minimal The odata.metadata=minimal format parameter indicates that the service SHOULD remove computable control information from the payload wherever possible. This is the default value for the odata.metadata parameter and will be assumed if no other value is specified in the Accept header or $format query option. The response payload MUST contain at least the following common  HYPERLINK \l "_Instance_Annotations" annotations:  HYPERLINK \l "_The_odata.metadata_Annotation_1" odata.context: the root context URL of the payload and the context URL for any deleted entries or added or deleted links in a delta response, or for entities or entity collections whose set cannot be determined from the root context URL  HYPERLINK \l "odataEtag" odata.etag: the ETag of the entity, as appropriate  HYPERLINK \l "odataCount" odata.count: the total count of a collection of entities or collection of entity references, if requested  HYPERLINK \l "odataNext" odata.nextLink: the next link of a collection with partial results  HYPERLINK \l "odataDelta" odata.deltaLink: the delta link for obtaining changes to the result, if requested In addition, odata annotations MUST appear in the payload for cases where actual values are not the same as the computed values and MAY appear otherwise. When odata annotations appear in the payload, they are treated as exceptions to the computed values. Media entities and stream properties MAY in addition contain the following annotations:  HYPERLINK \l "_Annotation_odata.media*" odata.mediaEtag: the ETag of the stream, as appropriate  HYPERLINK \l "_Annotation_odata.media*" odata.mediaContentType: the content type of the stream odata.metadata=full The odata.metadata=full format parameter indicates that the service MUST include all control information explicitly in the payload. The full list of annotations that may appear in an odata.metadata=full response is as follows:  HYPERLINK \l "_The_odata.metadata_Annotation_1" odata.context: the context URL for a collection, entity, primitive value, or service document.  HYPERLINK \l "odataCount" odata.count: the total count of a collection of entities or collection of entity references, if requested.  HYPERLINK \l "odataNext" odata.nextLink: the next link of a collection with partial results  HYPERLINK \l "odataDelta" odata.deltaLink: the delta link for obtaining changes to the result, if requested  HYPERLINK \l "_The_odata.id_Annotation_1" odata.id: the ID of the entity  HYPERLINK \l "odataEtag" odata.etag: the ETag of the entity  HYPERLINK \l "_Annotation_odata.editLink_and" odata.readLink: the link used to read the entity, if the edit link cannot be used to read the entity  HYPERLINK \l "_Annotation_odata.editLink_and" odata.editLink: the link used to edit/update the entity, if the entity is updatable and the odata.id does not represent a URL that can be used to edit the entity  HYPERLINK \l "_Annotation_odata.navigationLink_and" odata.navigationLink: the link used to retrieve the values of a navigation property  HYPERLINK \l "_Annotation_odata.navigationLink_and" odata.associationLink: the link used to describe the relationship between this entity and related entities  HYPERLINK \l "odataType" odata.type: the type of the containing object or targeted property if the type of the object or targeted property cannot be heuristically determined Media entities and stream properties may in addition contain the following annotations:  HYPERLINK \l "_Annotation_odata.media*" odata.mediaReadLink: the link used to read the stream  HYPERLINK \l "_Annotation_odata.media*" odata.mediaEditLink: the link used to edit/update the stream  HYPERLINK \l "_Annotation_odata.media*" odata.mediaEtag: the ETag of the stream, as appropriate  HYPERLINK \l "_Annotation_odata.media*" odata.mediaContentType: the content type of the stream odata.metadata=none The odata.metadata=none format parameter indicates that the service SHOULD omit control information other than  HYPERLINK \l "odataNext" odata.nextLink and  HYPERLINK \l "odataCount" odata.count. These annotations MUST continue to be included, as applicable, even in the odata.metadata=none case. It is not valid to specify odata.metadata=none on a  HYPERLINK \l "_Delta_Response" delta request. Controlling the Representation of Numbers The IEEE754Compatible=true format parameter indicates that the service MUST serialize Edm.Int64 and Edm.Decimal numbers (including the  HYPERLINK \l "_Annotation_odata.count" odata.count, if requested) as strings. If not specified, or specified as IEEE754Compatible=false, all numbers MUST be serialized as JSON numbers. This enables support for JavaScript numbers that are defined to be 64-bit binary format IEEE 754 values  REF ECMAScript \h [ECMAScript] (see  HYPERLINK "http://www.ecma-international.org/ecma-262/5.1/" \l "sec-4.3.19" section 4.3.1.9) resulting in integers losing precision past 15 digits, and decimals losing precision due to the conversion from base 10 to base 2. OData JSON payloads that format Edm.Int64 and Edm.Decimal values as strings MUST specify this format parameter in the media type returned in the  HYPERLINK \l "_Header_Content-Type" Content-Type header. Common Characteristics This section describes common characteristics of the representation for OData values in JSON. A request or response body consists of several parts. It contains OData values as part of a larger document. Requests and responses are structured almost identical; the few existing differences will be explicitly called out in the respective subsections. Header Content-Type Requests and responses with a JSON message body MUST have a Content-Type header value of application/json. Requests MAY add the charset parameter to the content type. Allowed values are UTF-8, UTF-16, and UTF-32. If no charset parameter is present, UTF-8 MUST be assumed. Responses MUST include the  HYPERLINK \l "_Controlling_the_Amount" odata.metadata parameter to specify the amount of metadata included in the response. Responses MUST include the  HYPERLINK \l "_Controlling_the_Representation" IEEE754Compatible parameter if Edm.Int64 and Edm.Decimal numbers are represented as strings. Requests and responses MAY add the odata.streaming parameter with a value of true or false, see section  HYPERLINK \l "_Payload_Ordering_Constraints_1" Payload Ordering Constraints. Message Body Each message body is represented as a single JSON object. This object is either the representation of an  HYPERLINK \l "Entitiy" entity, an  HYPERLINK \l "ResourceReference" entity reference or a  HYPERLINK \l "_Representing_a_Complex" complex type instance, or it contains a name/value pair whose name MUST be value and whose value is the correct representation for a  HYPERLINK \l "_Primitive_Value" primitive value, a  HYPERLINK \l "CollectionOfPrimitive" collection of primitive values, a  HYPERLINK \l "_Collection_of_Complex" collection of complex values, a  HYPERLINK \l "CollectionOfEntities" collection of entities, or a collection of objects that represent  HYPERLINK \l "DeltaResponse" changes to a previous result. Client libraries MUST retain the order of objects within an array in JSON responses. Relative URLs URLs present in a payload (whether request or response) MAY be represented as relative URLs. Relative URLs, other than those in odata.type, are relative to their base URL, which is the  HYPERLINK \l "_Annotation_odata.metadata" context URL of the same JSON object, if one exists, otherwise the context URL of the enclosing object, if one exists, otherwise the context URL of the next enclosing object, if one exists, etc. until the document root, otherwise the request URL. For context URLs these rules apply starting with the second bullet point. Within the  HYPERLINK \l "_Annotation_odata.type" odata.type annotation, relative URLs are relative to the base type URL, which is the odata.type of the enclosing object, if one exists, otherwise the odata.type of the next enclosing object, if one exists, etc. until the document root, otherwise the context URL of the document root, if one exists, otherwise the request URL. Processors expanding the URLs MUST use normal URL expansion rules as defined in  REF RFC3986 \h [RFC3986]. This means that if the base URL is a context URL, the part starting with $metadata# is ignored when resolving the relative URL. Clients that receive relative URLs in response payloads SHOULD use the same relative URLs, where appropriate, in request payloads (such as  HYPERLINK \l "_Bind_Operation" bind operations and batch requests) and in system query options (such as $id). Example  SEQ Example \* ARABIC 2: { "@odata.context": "http://host/service/$metadata#Customers/$entity", ... "@odata.editLink": "Customers('ALFKI')", ... "Orders@odata.navigationLink": "Customers('ALFKI')/Orders", ... } The resulting absolute URLs are http://host/service/Customers('ALFKI') and http://host/service/Customers('ALFKI')/Orders. Payload Ordering Constraints Ordering constraints MAY be imposed on the JSON payload in order to support streaming scenarios. These ordering constraints MUST only be assumed if explicitly specified as some clients (and services) might not be able to control, or might not care about, the order of the JSON properties in the payload. Clients can request that a JSON response conform to these ordering constraints by specifying a media type of application/json with the odata.streaming=true parameter in the Accept header or $format query option. Services MUST return 406 Not Acceptable if the client only requests streaming and the service does not support it. Processors MUST only assume streaming support if it is explicitly indicated in the Content-Type header via the odata.streaming=true parameter. Example  SEQ Example \* ARABIC 3: a payload with Content-Type: application/json;odata.metadata=minimal;odata.streaming=true can be assumed to support streaming, whereas a payload with Content-Type: application/json;odata.metadata=minimal cannot be assumed to support streaming. JSON producers are encouraged to follow the payload ordering constraints whenever possible (and include the odata.streaming=true content type parameter) to support the maximum set of client scenarios. To support streaming scenarios the following payload ordering constraints have to be met: If present, the odata.context annotation MUST be the first property in the JSON object. The odata.type annotation, if present, MUST appear next in the JSON object. The odata.id and odata.etag annotations MUST appear before any property or property annotation. All annotations for a structural or navigation property MUST appear as a group immediately before the property they annotate. The one exception is the odata.nextLink annotation of an expanded collection which MAY appear after the navigation property it annotates. All other odata annotations can appear anywhere in the payload as long as they do not violate any of the above rules. Annotations for navigation properties MUST appear after all structural properties. Control Information In addition to the pure data a message body MAY contain control information that is represented as  HYPERLINK \l "_Instance_Annotations" annotations whose names start with odata followed by a dot. Clients that encounter unknown annotations in any namespace, including the odata namespace, MUST NOT stop processing and MUST NOT signal an error. Annotation odata.context The odata.context annotation returns the context URL (see  REF protocol \h [OData-Protocol]) for the payload. This URL can be absolute or  HYPERLINK \l "_Relative_URLs" relative. The odata.context annotation MUST be the first property of any JSON response that does not specify  HYPERLINK \l "_odata.metadata=none" odata.metadata=none. The odata.context annotation MUST also be included for entities whose entity set cannot be determined from the context URL of the collection. For more information on the format of the context URL, see  REF protocol \h [OData-Protocol]. Request payloads in JSON do not require context URLs. It MAY be included as a base URL for  HYPERLINK \l "_Relative_URLs" relative URLs in the request payload. Response payloads SHOULD NOT contain the context URL if  HYPERLINK \l "_odata.metadata=none" odata.metadata=none is requested. Example  SEQ Example \* ARABIC 4: { "@odata.context": "http://host/service/$metadata#Customers/$entity", "@odata.metadataEtag": "W/\"A1FF3E230954908F\"", ... } Annotation odata.metadataEtag The odata.metadataEtag annotation MAY appear in a response in order to specify the entity tag (ETag) that can be used to determine the version of the metadata of the response. For details on how ETags are used, see  REF OData \h [OData-Protocol]. Annotation odata.type The odata.type annotation specifies the type of a JSON object or name/value pair. Its value is a URI that identifies the type of the property or object. For built-in primitive types the value is the unqualified name of the primitive type, specified as a URI fragment. For all other types, the URI may be absolute or relative to the odata.type of the containing object. The root odata.type may be absolute or relative to the root  HYPERLINK \l "_Annotation_odata.context" context URL. For non-built in primitive types, the URI contains the namespace-qualified or alias-qualified type, specified as a URI fragment. For properties that represent a collection of values, the fragment is the namespace-qualified or alias-qualified element type enclosed in parentheses and prefixed with Collection. The odata.type annotation MUST appear in  HYPERLINK \l "_odata=minimalmetadata" minimal or  HYPERLINK \l "_odata.metadata=full" full metadata if the type cannot be heuristically determined, as described below, and one of the following is true: The type is derived from the type specified for the (collection of) entities or (collection of) complex type instances, or The type is for a property whose type is not declared in $metadata. The following heuristics are used to determine the primitive type of a dynamic property in the absence of the odata.type annotation: Boolean values have a first-class representation in JSON and do not need any additional annotations. Numeric values have a first-class representation in JSON and do not need any additional annotations. If the value of a property is represented as a number without a dot (.), e or E embedded, the type should be interpreted as an integer value, otherwise as a decimal, double, or single value. The floating-point values NaN, INF, and -INF are serialized as strings and MUST have an  HYPERLINK \l "_Annotation_odata.type" odata.type annotation to specify the numeric type. String values do have a first class representation in JSON, but there is an obvious collision: OData also encodes a number of other primitive types as strings, e.g. DateTimeOffset, Int64 in the presence of the  HYPERLINK \l "_Controlling_the_Representation" IEEE754Compatible format parameter etc. If a property appears in JSON string format, it should be treated as a string value unless the property is known (from the metadata document) to have a different type. For more information on namespace- and alias-qualified names, see  REF odataCSDL \h [OData-CSDL]. Example  SEQ Example \* ARABIC 5: entity of type Model.VipCustomer defined in the metadata document of the same service with a dynamic property of type Edm.Double and a value of positive infinity { "@odata.context": "http://host/service/$metadata#Customers/$entity", "@odata.type": "#Model.VipCustomer", "ID": 2, "DynamicLimit": "INF", "DynamicLimit@odata.type": "#Double", ... } Example  SEQ Example \* ARABIC 6: entity of type Model.VipCustomer defined in the metadata document of a different service { "@odata.context": "http://host/service/$metadata#Customers/$entity", "@odata.type": "http://host/alternate/$metadata#Model.VipCustomer", "ID": 2, ... } Annotation odata.count The odata.count annotation contains the count of a  HYPERLINK \l "_Representing_Multiple_Entities" collection of entities or a  HYPERLINK \l "_Entity_Reference" collection of entity references, see  REF odata \h [OData-Protocol] section 11.2.4.5 System Query Option $count. Its value is an Edm.Int64 value corresponding to the total count of members in the collection represented by the request. Annotation odata.nextLink The odata.nextLink annotation indicates that a response is only a subset of the requested collection of entities or collection of entity references. It contains a URL that allows retrieving the next subset of the requested collection. This annotation can also be applied to  HYPERLINK \l "_Expanded_Navigation_Property" expanded to-many navigation properties. Annotation odata.deltaLink The odata.deltaLink annotation contains a URL that can be used to retrieve changes to the current set of results. The odata.deltaLink annotation MUST only appear on the last page of results. A page of results MUST NOT have both an odata.deltaLink annotation and an odata.nextLink annotation. Annotation odata.id The odata.id annotation contains the entity-id; see  REF protocol \h [OData-Protocol]. By convention the entity-id is identical to the canonical URL of the entity, as defined in  HYPERLINK \l "ODataURLRef"  REF ODataURLRef \h [OData-URL]. The odata.id annotation MUST appear if  HYPERLINK \l "_odata.metadata=full" odata.metadata=full is requested or if the entity-id is not identical to the canonical URL of the entity after IRI-to-URI conversion as defined in  REF RFC3987 \h [RFC3987], resolution of relative URLs and percent-encoding normalization as defined in  REF RFC3986 \h [RFC3986]. Note that the entity-id MUST be invariant across languages, so if key values are language dependent then the odata.id MUST be included if it does not match convention for the localized key values. If the odata.id is represented, it MAY be a  HYPERLINK \l "_Relative_URLs" relative URL. If the entity is transient (i.e. cannot be read or updated), the odata.id annotation MUST appear and have the null value. The odata.id annotation MUST NOT appear for a collection. Its meaning in this context is reserved for future versions of this specification. Entities with odata.id equal to null cannot be compared to other entities, reread, or updated. If  HYPERLINK \l "_odata=minimalmetadata" odata.metadata=minimal is specified and the odata.id is not present in the entity then the canonical URL MUST be used as the entity-id. Annotation odata.editLink and odata.readLink The odata.editLink annotation contains the edit URL of the entity; see  REF protocol \h [OData-Protocol]. The odata.readLink annotation contains the read URL of the entity or collection; see  REF protocol \h [OData-Protocol]. The default value of both the edit URL and read URL is the entity's  HYPERLINK \l "_The_odata.id_Annotation_1" entity-id appended with a cast segment to the type of the entity if its type is derived from the declared type of the entity set. If neither the odata.editLink nor the odata.readLink annotation is present in an entity, the client uses this default value for the edit URL. For updatable entities: The odata.editLink annotation is written if  HYPERLINK \l "_odata.metadata=full" odata.metadata=full is requested or if the edit URL differs from the default value of the edit URL. The odata.readLink annotation is written if the read URL is different from the edit URL. If no odata.readLink annotation is present, the read URL is identical to the edit URL. For read-only entities: The odata.readLink annotation is written if  HYPERLINK \l "_odata.metadata=full" odata.metadata=full is requested or if its value differs from the default value of the read URL. The odata.readLink annotation may also be written if  HYPERLINK \l "_odata=minimalmetadata" odata.metadata=minimal is specified in order to signal that an individual entity is read-only. For collections: The odata.readLink annotation, if written, MUST be the request URL that produced the collection. The odata.editLink annotation MUST NOT be written as its meaning in this context is reserved for future versions of this specification. Annotation odata.etag The odata.etag annotation MAY be applied to an  HYPERLINK \l "_Entity" entity. The value of the annotation is an entity tag (ETag) which is an opaque string value that can be used in a subsequent request to determine if the value of the entity has changed. For details on how ETags are used, see  REF OData \h [OData-Protocol]. Annotation odata.navigationLink and odata.associationLink The odata.navigationLink annotation contains a navigation URL that can be used to retrieve an entity or collection of entities related to the current entity via a  HYPERLINK \l "_Navigation_Property" navigation property. The default computed value of a navigation URL is the value of the  HYPERLINK \l "_Annotation_odata.editLink_and" read URL appended with a segment containing the name of the navigation property. The service MAY omit the odata.navigationLink annotation if  HYPERLINK \l "_odata=minimalmetadata" odata.metadata=minimal has been specified on the request and the navigation link matches this computed value. The odata.associationLink annotation contains an association URL that can be used to retrieve a reference to an entity or a collection of references to entities related to the current entity via a navigation property. The default computed value of an association URL is the value of the navigation URL appended with /$ref. The service MAY omit the odata.associationLink annotation if the association link matches this computed value. Annotation odata.media* For  HYPERLINK \l "_Media_Entity" media entities and  HYPERLINK \l "_Stream_Property" stream properties that don't follow standard URL conventions as defined in  HYPERLINK \l "ODataURLRef"  REF ODataURLRef \h [OData-URL], at least one of the annotations odata.mediaEditLink and odata.mediaReadLink MUST be included. The odata.mediaEditLink annotation contains a URL that can be used to update the binary stream associated with the media entity or stream property. It MUST be included for updatable media entities if it differs from the value of the odata.id, and for updatable stream properties if it differs from standard URL conventions. The odata.mediaReadLink annotation contains a URL that can be used to read the binary stream associated with the media entity or stream property. It MUST be included if its value differs from the value of the associated odata.mediaEditLink, if present, or the value of the odata.id for media entities if the associated odata.mediaEditLink is not present. The odata.mediaContentType annotation MAY be included; its value SHOULD match the content type of the binary stream represented by the odata.mediaReadLink URL. This is only a hint; the actual content type will be included in a header when the resource is requested. The odata.mediaEtag annotation MAY be included; its value is the ETag of the binary stream represented by this media entity or stream property. Example  SEQ Example \* ARABIC 7: { "@odata.context": "http://host/service/$metadata#Employees/$entity", "@odata.mediaReadLink": "Employees(1)/$value", "@odata.mediaContentType": "image/jpeg", "EmployeeID": 1, ... } Service Document A service document in JSON is represented as a single JSON object with at least two properties; odata.context and value. The value of the odata.context property MUST be the URL of the metadata document, without any fragment part. The value of the value property MUST be a JSON Array containing one element for each entity set and function import with an explicit or default value of true for the attribute IncludeInServiceDocument and each singleton exposed by the service, see  REF odataCSDL \h [OData-CSDL]. Each element MUST be a JSON object with at least two name/value pairs, one with name name containing the name of the entity set, function import, or singleton, and one with name url containing the URL of the entity set, which may be an absolute or a  HYPERLINK \l "_Relative_URLs" relative URL. It MAY contain a name/value pair with name title containing a human-readable, language-dependent title for the object. JSON objects representing an entity set MAY contain an additional name/value pair with name kind and a value of EntitySet. If the kind name/value pair is not present, the object MUST represent an entity set. JSON objects representing a function import MUST contain the kind name/value pair with a value of FunctionImport. JSON objects representing a singleton MUST contain the kind name/value pair with a value of Singleton. JSON objects representing a related service document MUST contain the kind name/value pair with a value of ServiceDocument. Clients that encounter unknown values of the kind name/value pair not defined in this version of the specification MUST NOT stop processing and MUST NOT signal an error. Example  SEQ Example \* ARABIC 8: { "@odata.context": "http://host/service/$metadata", "value": [ { "name": "Orders", "kind": "EntitySet", "url": "Orders" }, { "name": "OrderItems", "title": "Order Details", "url": "OrderItems" }, { "name": "TopProducts", "title": "Best-Selling Products", "kind": "FunctionImport", "url": "TopProducts" }, { "name": "Contoso", "title": "Contoso Ltd.", "kind": "Singleton", "url": "Contoso" }, { "name": "Human Resources", "kind": "ServiceDocument", "url": "http://host/HR/" } ] } Entity An entity is serialized as a JSON object. Each  HYPERLINK \l "_Structural_Property" property to be transmitted is represented as a name/value pair within the object. The order properties appear within the object is considered insignificant. An entity in a payload may be a complete entity, a projected entity (see System Query Option $select  REF odata \h [OData-Protocol]), or a partial entity update (see Update an Entity in  REF odata \h \* MERGEFORMAT [OData-Protocol]). An entity representation can be (modified and) round-tripped to the service directly. The  HYPERLINK \l "_The_odata.metadata_Annotation_1" context URL is used in requests only as a base for  HYPERLINK \l "_Relative_URLs" relative URLs. Example  SEQ Example \* ARABIC 9: entity with odata.metadata=minimal { "@odata.context": "http://host/service/$metadata#Customers/$entity", "ID": "ALFKI", "CompanyName": "Alfreds Futterkiste", "ContactName": "Maria Anders", "ContactTitle": "Sales Representative", "Phone": "030-0074321", "Fax": "030-0076545", "Address": { "Street": "Obere Str. 57", "City": "Berlin", "Region": null, "PostalCode": "D-12209" } } Example  SEQ Example \* ARABIC 10: entity with odata.metadata=full { "@odata.context": "http://host/service/$metadata#Customers/$entity", "@odata.id": "Customers('ALFKI')", "@odata.etag": "W/\"MjAxMy0wNS0yN1QxMTo1OFo=\"", "@odata.editLink": "Customers('ALFKI')", "ID": "ALFKI", "CompanyName": "Alfreds Futterkiste", "ContactName": "Maria Anders", "ContactTitle": "Sales Representative", "Phone": "030-0074321", "Fax": "030-0076545", "Address": { "Street": "Obere Str. 57", "City": "Berlin", "Region": null, "PostalCode": "D-12209", "Country@odata.associationLink":"Customers('ALFKI')/Address/Country/$ref", "Country@odata.navigationLink": "Customers('ALFKI')/Address/Country" }, "Orders@odata.associationLink": "Customers('ALFKI')/Orders/$ref", "Orders@odata.navigationLink": "Customers('ALFKI')/Orders" } Structural Property A property within an entity or complex type instance is represented as a name/value pair. The name MUST be the name of the property; the value is represented depending on its type as a  HYPERLINK \l "_Primitive_Value" primitive value, a  HYPERLINK \l "_Complex_Value" complex value, a  HYPERLINK \l "_Collection_of_Primitive" collection of primitive values, or a  HYPERLINK \l "_Collection_of_Complex" collection of complex values. Primitive Value Primitive values are represented following the rules of  REF rfc4627 \h [RFC4627]. Null values are represented as the JSON literal null. Values of type Edm.Boolean are represented as the JSON literals true and false Values of types Edm.Byte, Edm.SByte, Edm.Int16, Edm.Int32, Edm.Int64, Edm.Single, Edm.Double, and Edm.Decimal are represented as JSON numbers, except for NaN, INF, and INF which are represented as strings. Values of type Edm.String are represented as JSON strings, using the JSON string escaping rules. Values of type Edm.Binary, Edm.Date, Edm.DateTimeOffset, Edm.Duration, Edm.Guid, and Edm.TimeOfDay as well as enumeration values are represented as JSON strings whose content satisfies the rules binaryValue, dateValue, dateTimeOffsetValue, durationValue, guidValue, timeOfDayValue, and enumValue, respectively, in  REF abnf \h [OData-ABNF]. Geography and geometry values are represented as defined in  REF GeoJSON \h [GeoJSON], with the following modifications: Keys SHOULD be ordered with type first, then coordinates, then any other keys The coordinates member of a LineString can have zero or more positions If the optional CRS object is present, it MUST be of type name, where the value of the name member of the contained properties object is an EPSG SRID legacy identifier. Example  SEQ Example \* ARABIC 11: { "NullValue": null, "TrueValue": true, "FalseValue": false, "BinaryValue": "T0RhdGE", "IntegerValue": -128, "DoubleValue": 3.1415926535897931, "SingleValue": "INF", "DecimalValue": 34.95, "StringValue": "Say \"Hello\",\nthen go", "DateValue": "2012-12-03", "DateTimeOffsetValue": "2012-12-03T07:16:23Z", "DurationValue": "P12DT23H59M59.999999999999S", "TimeOfDayValue": "07:59:59.999", "GuidValue": "01234567-89ab-cdef-0123-456789abcdef", "Int64Value": 0, "ColorEnumValue": "Yellow", "GeographyPoint": {"type": "point","coordinates":[142.1,64.1]} } Complex Value A complex value is represented as a single JSON object containing one name/value pair for each property that makes up the complex type. Each property value is formatted as appropriate for the type of the property. It MAY have name/value pairs for instance annotations, including odata annotations. Example  SEQ Example \* ARABIC 12: { "@odata.context": "http://host/service/$metadata#Customers/$entity", ... "Address": { "Street": "Obere Str. 57", "City": "Berlin", "Region": null, "PostalCode": "D-12209" } } Collection of Primitive Values A collection of primitive values is represented as a JSON array; each element in the array is the representation of a  HYPERLINK \l "_Primitive_Value" primitive value. A JSON literal null represents a null value within the collection. An empty collection is represented as an empty array. Example  SEQ Example \* ARABIC 13: partial collection of strings with next link { "@odata.context": "http://host/service/$metadata#Customers/$entity", ... "EmailAddresses": [ "Julie@Swansworth.com", "Julie.Swansworth@work.com" ], "EmailAddresses@odata.nextLink": "..." } Collection of Complex Values A collection of complex values is represented as a JSON array; each element in the array is the representation of a  HYPERLINK \l "_Representing_a_Complex" complex value. A JSON literal null represents a null value within the collection. An empty collection is represented as an empty array. Example  SEQ Example \* ARABIC 14: partial collection of complex values with next link { "PhoneNumbers": [ { "Number": "425-555-1212", "Type": "Home" }, { "@odata.type": "#Model.CellPhoneNumber", "Number": "425-555-0178", "Type": "Cell", "Carrier": "Sprint" } ], "PhoneNumbers@odata.nextLink": "..." } Navigation Property A navigation property is a reference from a source entity to zero or more related entities. Navigation Link The navigation link for a navigation property is represented as a name/value pair. The name is the name of the property, followed by @odata.navigationLink. The value is an absolute or  HYPERLINK \l "_Relative_URLs" relative URL that allows retrieving the related entity or collection of entities. The navigation link for a navigation property is only represented if the client requests odata.metadata=full or the navigation link cannot be computed, e.g. if it is within a collection of complex type instances. If it is represented it MUST immediately precede the expanded navigation property if the latter is represented. Example  SEQ Example \* ARABIC 15: { "@odata.context": "http://host/service/$metadata#Customers/$entity", ... "Orders@odata.navigationLink": "Customers('ALFKI')/Orders", ... } Association Link The association link for a navigation property is represented as a name/value pair. The name is the name of the property, followed by @odata.associationLink. The value is an absolute or  HYPERLINK \l "_Relative_URLs" relative URL that can be used to retrieve the reference or collection of references to the related entity or entities. The association link for a navigation property is only represented if the client requests odata.metadata=full or the association link cannot be computed by appending /$ref to the navigation link. If it is represented, it MUST immediately precede the navigation link if the latter is represented, otherwise it MUST immediately precede the expanded navigation property if it is represented. Example  SEQ Example \* ARABIC 16: { "@odata.context": "http://host/service/$metadata#Customers/$entity", ... "Orders@odata.associationLink": "Customers('ALFKI')/Orders/$ref", ... } Expanded Navigation Property An expanded navigation property is represented as a name/value pair where the name is the name of the navigation property, and the value is the representation of the related entity or collection of entities. If at most one entity can be related, the value is the representation of the related entity, or null if no entity is currently related. If a collection of entities can be related, it is represented as a JSON array. Each element is the  HYPERLINK \l "_Entity" representation of an entity or the  HYPERLINK \l "ResourceReference" representation of an entity reference. An empty collection of entities (one that contains no entities) is represented as an empty JSON array. The navigation property MAY be annotated with  HYPERLINK \l "_The_odata.metadata_Annotation_1" odata.context,  HYPERLINK \l "_Annotation_odata.count" odata.count or odata.nextLink. Example  SEQ Example \* ARABIC 17: { "@odata.context": "http://host/service/$metadata#Customers/$entity", ... "Orders@odata.count": 42, "Orders": [ ... ], "Orders@odata.nextLink": "...", ... } Deep Insert When inserting a new entity with a POST request, related new entities MAY be specified using the same representation as for an  HYPERLINK \l "_Expanded_Navigation_Property" expanded navigation property. Deep inserts are not allowed in update operations using PUT or PATCH requests. Example  SEQ Example \* ARABIC 18: inserting a new order for a new customer with order items related to existing products: { "Customer": { "ID": "ANEWONE", ... }, "Items": [ { "Product@odata.bind": "Products(28)", ... }, { "Product@odata.bind": "Products(39)", ... } ], "ID": 11643, ... } Bind Operation When inserting or updating an entity, relationships of navigation properties MAY be inserted or updated via bind operations. A bind operation is encoded as a property annotation odata.bind on the navigation property it belongs to and has a single value for singleton navigation properties or an array of values for collection navigation properties. The values are the  HYPERLINK \l "_Annotation_odata.id" ids of the related entities. They MAY be absolute or  HYPERLINK \l "_Relative_URLs" relative URLs. For insert operations collection navigation property bind operations and deep insert operations can be combined. In this case, the bind operations MUST appear before the deep insert operations in the payload. For update operations a bind operation on a collection navigation property adds additional relationships, it does not replace existing relationships, while bind operations on an entity navigation property update the relationship. Example  SEQ Example \* ARABIC 19: assign an existing product to an existing category with a partial update request PATCH http://host/service/Products(42) HTTP/1.1 { "Category@odata.bind": "Categories(6)" } Stream Property An entity or complex type instance can have one or more stream properties. The actual stream data is not contained in the representation. Instead stream property data is read and edited via URLs. The value for a stream property contains the URLs for reading and editing the stream data along with other metadata for the stream. The value of a stream property is represented as a set of  HYPERLINK \l "_Annotation_odata.media*" odata.media* annotations. Example  SEQ Example \* ARABIC 20: { "@odata.context": "http://host/service/$metadata#Products/$entity", ... "Thumbnail@odata.mediaReadLink": "http://server/Thumbnail546.jpg", "Thumbnail@odata.mediaEditLink": "http://server/uploads/Thumbnail546.jpg", "Thumbnail@odata.mediaContentType": "image/jpeg", "Thumbnail@odata.mediaEtag": "W/\"####\"", ... } Media Entity Media entities are entities that describe a media resource, for example a photo. They are represented as entities that contain additional  HYPERLINK \l "_Annotation_odata.media*" odata.media* annotations. Example  SEQ Example \* ARABIC 21: { "@odata.context": "http://host/service/$metadata#Employees/$entity", "@odata.mediaReadLink": "Employees(1)/$value", "@odata.mediaContentType": "image/jpeg", "ID": 1, ... } Individual Property An individual property is represented as a JSON object. A single-valued property that has the null value does not have a representation; see  REF protocol \h [OData-Protocol]. A property that is of a primitive type is represented as an object with a single name/value pair, whose name is value and whose value is a  HYPERLINK \l "_Primitive_Value" primitive value. A property that is of complex type is represented as a  HYPERLINK \l "_Representing_a_Complex" complex value. A property that is of a collection type is represented as an object with a single name/value pair whose name is value. Its value is the JSON representation of a  HYPERLINK \l "_Collection_of_Complex" collection of complex type values or  HYPERLINK \l "_Collection_of_Primitive" collection of primitive values. Example  SEQ Example \* ARABIC 22: primitive value { "@odata.context": "http://host/service/$metadata#Edm.String", "value": "Pilar Ackerman" } Example  SEQ Example \* ARABIC 23: collection of primitive values { "@odata.context": "http://host/service/$metadata#Collection(Edm.String)", "value": ["small", "medium", "extra large"] } Example  SEQ Example \* ARABIC 24: empty collection of primitive values { "@odata.context": "http://host/service/$metadata#Collection(Edm.String)", "value": [] } Example  SEQ Example \* ARABIC 25: complex value { "@odata.context": "http://host/service/$metadata#Model.Address", "Street": "12345 Grant Street", "City": "Taft", "Region": "Ohio", "PostalCode": "OH 98052", "Country@odata.navigationLink": "Countries('US')" } Example  SEQ Example \* ARABIC 26: empty collection of complex values { "@odata.context":"http://host/service/$metadata#Collection(Model.Address)", "value": [] } Note: the context URL is optional in requests. Collection of Entities A collection of entities is represented as a JSON object containing a name/value pair named value. It MAY contain  HYPERLINK \l "_The_odata.metadata_Annotation_1" odata.context,  HYPERLINK \l "_Annotation_odata.count" odata.count,  HYPERLINK \l "odataNext" odata.nextLink, or  HYPERLINK \l "odataDelta" odata.deltaLink annotations. If present, the odata.context annotation MUST be the first name/value pair in the response. The odata.count name/value pair represents the number of entities in the collection. If present, it MUST come before the value name/value pair. The value of the value name/value pair is a JSON array where each element is  HYPERLINK \l "_Entity" representation of an entity or a  HYPERLINK \l ResourceReference representation of an entity reference. An empty collection is represented as an empty JSON array. Functions or actions that are bound to this collection of entities are advertised in the wrapper object in the same way as  HYPERLINK \l "_Bound_Function" functions or  HYPERLINK \l "_Bound_Action" actions are advertised in the object representing a single entity. The  HYPERLINK \l "_Annotation_odata.nextLink" odata.nextLink annotation MUST be included in a response that represents a partial result. Example  SEQ Example \* ARABIC 27: { "@odata.context": "...", "@odata.count": 37, "value": [ { ... }, { ... }, { ... } ], "@odata.nextLink": "...?$skiptoken=342r89" } Entity Reference An entity reference (see  REF protocol \h [OData-Protocol]) MAY take the place of an entity instance in a JSON payload, based on the client request. It is serialized as a JSON object that MUST contain the  HYPERLINK \l "_The_odata.id_Annotation_1" id of the referenced entity and MAY contain the  HYPERLINK \l "odataType" odata.type. A collection of entity references is represented as a  HYPERLINK \l "_Collection_of_Entities" collection of entities, with entity reference representations instead of entity representations as items in the array value of the value name/value pair. The outermost JSON object MUST contain an  HYPERLINK \l "_The_odata.metadata_Annotation_1" odata.context annotation and MAY contain  HYPERLINK \l "_Annotation_odata.count" odata.count,  HYPERLINK \l "odataNext" odata.nextLink, or  HYPERLINK \l "odataDelta" odata.deltaLink annotations. Example  SEQ Example \* ARABIC 28: entity reference to order 10643 { "@odata.context": "http://host/service/$metadata#$ref", "@odata.id": "Orders(10643)" } Example  SEQ Example \* ARABIC 29: collection of entity references { "@odata.context": "http://host/service/$metadata#Collection($ref)", "value": [ { "@odata.id": "Orders(10643)" }, { "@odata.id": "Orders(10759)" } ] } Delta Response The non-format specific aspects of the delta handling are described in the section Requesting Changes in  REF protocol \h [OData-Protocol]. Responses from a delta request are returned as a JSON object. The JSON object MUST contain an array-valued property named value containing all  HYPERLINK \l "_Added/Changed_Entity" added,  HYPERLINK \l "_Representing_Added/Changed_Entities_1" changed, or  HYPERLINK \l "_Deleted_Entity" deleted entities, as well as  HYPERLINK \l "_Added_Link" added or  HYPERLINK \l "_Deleted_Link" deleted links between entities, and MAY contain additional, unchanged entities. If the delta response contains a partial list of changes, it MUST include a  HYPERLINK \l "_Annotation_odata.nextLink" next link for the client to retrieve the next set of changes. The last page of a delta response SHOULD contain a  HYPERLINK \l "_Annotation_odata.deltaLink" delta link for retrieving subsequent changes once the current set of changes has been applied to the initial set. If the response from the delta link contains an  HYPERLINK \l "_Annotation_odata.count" odata.count annotation, the returned number MUST include all added, changed, or deleted entities, as well as added or deleted links. Example  SEQ Example \* ARABIC 30: delta response with five changes, in order of occurrence ContactName for customer 'BOTTM' was changed to "Susan Halvenstern" Order 10643 was removed from customer 'ALFKI' Order 10645 was added to customer 'BOTTM' The shipping information for order 10643 was updated Customer 'ANTON' was deleted { "@odata.context":"http://host/service/$metadata#Customers/$delta", "@odata.count":5, "value": [ { "@odata.id":"Customers('BOTTM')'", "ContactName":"Susan Halvenstern" }, { "@odata.context":"#Customers/$deletedLink", "source":"Customers('ALFKI')'", "relationship":"Orders", "target":"Orders(10643)" }, { "@odata.context":"#Customers/$link", "source":"Customers('BOTTM')", "relationship":"Orders", "target":"Orders(10645)" }, { "@odata.context":"#Orders/$entity", "@odata.id":"Orders(10643)", "ShippingAddress":{ "Street":"23 Tsawassen Blvd.", "City":"Tsawassen" "Region":"BC", "PostalCode":"T2F 8M4" }, }, { "@odata.context":"#Customers/$deletedEntity", "id":"Customers('ANTON')", "reason":"deleted" } ], "@odata.deltaLink": "Customers?$expand=Orders&$deltatoken=8015" } Added/Changed Entity Added or changed entities within a delta response are represented as  HYPERLINK \l "_Entity" entities Added entities MUST include all available selected properties and MAY include additional, unselected properties. Collection-valued properties are treated as atomic values; any collection-valued properties returned from a delta request MUST contain all current values for that collection. Changed entities MUST include all available selected properties that have changed and MAY include additional properties. Entities that are not part of the entity set specified by the context URL MUST include the  HYPERLINK \l "_Annotation_odata.metadata" odata.context annotation to specify the entity set of the entity. Entities include annotations for selected navigation links based on  HYPERLINK \l "_Controlling_the_Amount" odata.metadata but MUST NOT include expanded navigation properties inline. Deleted Entity Deleted entities in JSON are returned as deleted-entity objects. Delta responses MUST contain a deleted-entity object for each deleted entity. The deleted-entity object MUST include the following properties:  HYPERLINK \l "_The_odata.metadata_Annotation_1" odata.context the context URL fragment MUST be #{entity-set}/$deletedEntity, where {entity-set} is the entity set of the deleted entity id The  HYPERLINK \l "_The_odata.id_Annotation_1" id of the deleted entity (same as the  HYPERLINK \l "_The_odata.id_Annotation_1" odata.id returned or computed when calling GET on resource), which may be absolute or  HYPERLINK \l "_Relative_URLs" relative reason An optional string value; either deleted, if the entity was deleted (destroyed), or changed if the entity was removed from membership in the result (i.e., due to a data change). Added Link Links within a delta response are represented as link objects. Delta responses MUST contain a link object for each added link that corresponds to a $expand path in the initial request. The link object MUST include the following properties:  HYPERLINK \l "_The_odata.metadata_Annotation_1" odata.context the context URL fragment MUST be #{entity-set}/$link, where {entity-set} is the entity set containing the source entity source The  HYPERLINK \l "_The_odata.id_Annotation_1" id of the entity from which the relationship is defined, which may be absolute or  HYPERLINK \l "_Relative_URLs" relative relationship The name of the relationship property on the parent object target The  HYPERLINK \l "_The_odata.id_Annotation_1" id of the related entity, which may be absolute or  HYPERLINK \l "_Relative_URLs" relative Deleted Link Deleted links within a delta response are represented as deleted-link objects. Delta responses MUST contain a deleted-link object for each deleted link that corresponds to a $expand path in the initial request, unless either of the following is true: The source or target entity has been deleted The maximum cardinality of the related entity is one and there is a subsequent  HYPERLINK \l "_Added_Link" link object that specifies the same source and relationship. The deleted-link object MUST include the following properties:  HYPERLINK \l "_The_odata.metadata_Annotation_1" odata.context the context URL fragment MUST be #{entity-set}/$deletedLink, where {entity-set} is the entity set containing the source entity source The  HYPERLINK \l "_The_odata.id_Annotation_1" id of the entity from which the relationship is defined, which may be absolute or  HYPERLINK \l "_Relative_URLs" relative relationship The name of the relationship property on the parent object target The  HYPERLINK \l "_The_odata.id_Annotation_1" id of the related entity, which may be absolute or  HYPERLINK \l "_Relative_URLs" relative Bound Function A function that is bound to the current entity is advertised via a name/value pair where the name is a hash (#) character followed by the namespace- or alias-qualified name of the function. Functions that are bound to a collection of entities are advertised in representations of that collection. A function may have multiple overloads with different parameters. If function overloads exist that cannot be bound to the current entity type, the name SHOULD address a specific function overload by appending the parentheses-enclosed, comma-separated list of non-binding parameter names, see rule qualifiedFunctionName in  REF abnf \h [OData-ABNF]. If  HYPERLINK \l "_odata.metadata=full" odata.metadata=full is requested, each value object MUST have at least the two name/value pairs title and target. It MAY contain  HYPERLINK \l "_Instance_Annotations" annotations. The order of the name/value pairs MUST be considered insignificant. The target name/value pair contains a bound function or action URL. If the URL in the  HYPERLINK \l "_Attribute_target" target name/value pair cannot be used to invoke all overloads for the function, then the function name MUST be distinguished by appending the parentheses-enclosed, comma-separated list of non-binding parameter names. The title name/value pair contains the function or action title as a string. If  HYPERLINK \l "_odata=minimalmetadata" odata.metadata=minimal is requested, the target name/value pair MUST be included if its value differs from the canonical function or action URL. Example  SEQ Example \* ARABIC 31: minimal representation of a function where all overloads are applicable { "@odata.context": "http://host/service/$metadata#Employees/$entity", "#Model.RemainingVacation": {}, ... } Example  SEQ Example \* ARABIC 32: full representation of a specific overload { "@odata.context": "http://host/service/$metadata#Employees/$entity", "#Model.RemainingVacation(Year)": { "title": "Remaining vacation from year...", "target": "Employees(2)/RemainingVacation(Year=@Year)" }, ... } Example  SEQ Example \* ARABIC 33: full representation in a collection { "@odata.context": "http://host/service/$metadata#Employees", "#Model.RemainingVacation": { "title": "Remaining Vacation", "target": "Managers(22)/Employees/RemainingVacation" }, "value": [ ... ] } Bound Action An action that is bound to the current entity is advertised via a name/value pair where the name is a hash (#) character followed by the namespace- or alias-qualified name of the action. Actions that are bound to a collection of entities are advertised in representations of that collection. If  HYPERLINK \l "_odata.metadata=full" odata.metadata=full is requested, each value object MUST have at least the two name/value pairs title and target. It MAY contain  HYPERLINK \l "_Instance_Annotations" annotations. The order of these name/value pairs MUST be considered insignificant. The target name/value pair contains a bound function or action URL. The title name/value pair contains the function or action title as a string. If  HYPERLINK \l "_odata=minimalmetadata" odata.metadata=minimal is requested, the target name/value pair MUST be included if its value differs from the canonical function or action URL. Example  SEQ Example \* ARABIC 34: minimal representation in an entity { "@odata.context": "http://host/service/$metadata#LeaveRequests/$entity", "#Model.Approval": {}, ... } Example  SEQ Example \* ARABIC 35: full representation in an entity: { "@odata.context": "http://host/service/$metadata#LeaveRequests/$entity", "#Model.Approval": { "title": "Approve Leave Request", "target": "LeaveRequests(2)/Approval" }, ... } Example  SEQ Example \* ARABIC 36: full representation in a collection { "@odata.context": "http://host/service/$metadata#LeaveRequests", "#Model.Approval": { "title": "Approve All Leave Requests", "target": "Managers(22)/Inbox/Approval" }, "value": [ ... ] } Action Invocation Action parameter values are encoded in a single JSON object in the request body. Each non-binding parameter value is encoded as a separate name/value pair in this JSON object. The name is the name of the parameter. The value is the parameter value in the JSON representation appropriate for its type. Any parameter values not specified in the JSON object are assumed to have the null value. Example  SEQ Example \* ARABIC 37: { "param1": 42, "param2": { "Street": "One Microsoft Way", "Zip": 98052 }, "param3": [ 1, 42, 99 ], "param4": null } Instance Annotations Annotations are an extensibility mechanism that allows services and clients to include information other than the raw data in the request or response. Annotations are used to include control information in many payloads. Annotations are name/value pairs that have a dot (.) as part of the name. All annotations that start with odata are reserved for future extensions of the protocol and format. Custom annotations are annotations that have a non-empty prefix that is different from odata. Annotations can be applied to any name/value pair in a JSON payload that represents a value of any type from the entity data model (see  REF odataCSDL \h [OData-CSDL]). Example  SEQ Example \* ARABIC 38: { "@odata.context": "http://host/service/$metadata#Customers", "@com.contoso.customer.setkind": "VIPs", "value": [ { "@com.contoso.display.highlight": true, "ID": "ALFKI", "CompanyName@com.contoso.display.style": { "title": true, "order": 1 }, "CompanyName": "Alfreds Futterkiste", "Orders@com.contoso.display.style": { "order": 2 } } ] } 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. Annotate a JSON Object When annotating a name/value pair for which the value is represented as a JSON object, each annotation is placed within the object and represented as a single name/value pair. The name always starts with the "at" sign (@), followed by the namespace- or alias-qualified name of the annotation, i.e. the namespace or alias of the schema that defines the term, followed by a dot (.), followed by the name of the term. The namespace or alias MUST be defined in the metadata document, see  REF odataCSDL \h [OData-CSDL]. The value MUST be an appropriate value for the annotation. Annotate a JSON Array or Primitive When annotating a name/value pair for which the value is represented as a JSON array or primitive value, each annotation that applies to this name/value pair MUST be placed next to the annotated name/value pair and represented as a single name/value pair. The name is the same as the name of the name/value pair being annotated, followed by the at sign (@), followed by the namespace- or alias-qualified name of the annotation, followed by a dot (.), followed by the name of the term. The namespace or alias MUST be defined in the metadata document, see  REF odataCSDL \h [OData-CSDL]. The value MUST be an appropriate value for the annotation. Error Response The error response MUST be a single JSON object. This object MUST have a single name/value pair named error. The value must be a JSON object. This object MUST contain name/value pairs with the names code and message, and it MAY contain name/value pairs with the names target, details and innererror. The value for the code name/value pair is a language-independent string. Its value is a service-defined error code. This code serves as a sub-status for the HTTP error code specified in the response. The value for the message name/value pair MUST be a human-readable, language-dependent representation of the error. The Content-Language header MUST contain the language code from  REF rfc5646 \h [RFC5646] corresponding to the language in which the value for message is written. The value for the target name/value pair is the target of the particular error (for example, the name of the property in error). The value for the details name/value pair MUST be an array of JSON objects that MUST contain name/value pairs for code and message, and MAY contain a name/value pair for target, as described above. The value for the innererror name/value pair MUST be an object. The contents of this object are service-defined. Usually this object contains information that will help debug the service. The innererror name/value pair SHOULD only be used in development environments in order to guard against potential security concerns around information disclosure. Error responses MAY contain  HYPERLINK \l "_Instance_Annotations" annotations in any of its JSON objects. Example  SEQ Example \* ARABIC 39: { "error": { "code": "501", "message": "Unsupported functionality", "target": "query", "details": [ { "code": "301", "target": "$search" "message": "$search query option not supported", } ] "innererror": { "trace": [...], "context": {...} } } } Extensibility Implementations can add  HYPERLINK \l "_Instance_Annotations" custom annotations of the form namespace.termname or  HYPERLINK "mailto:property@namespace.termname" property@namespace.termname to any JSON object, where property MAY or MAY NOT match the name of a name/value pair within the JSON object. However, the namespace MUST NOT start with odata and SHOULD NOT be required to be understood by the receiving party in order to correctly interpret the rest of the payload as the receiving party MUST ignore unknown annotations not defined in this version of the OData JSON Specification. Security Considerations This specification raises no security issues. This section is provided as a service to the application developers, information providers, and users of OData version 4.0 giving some references to starting points for securing OData services as specified. OData is a REST-full multi-format service that depends on other services and thus inherits both sides of the coin, security enhancements and concerns alike from the latter. For JSON-relevant security implications please cf. at least the relevant subsections of  REF rfc4627 \h [RFC4627] as starting point. Conformance Conforming clients MUST be prepared to consume a service that uses any or all of the constructs defined in this specification. The exception to this are the constructs defined in  HYPERLINK \l "_Delta_Response" Delta Response, which are only required for clients that request changes. In order to be a conforming consumer of the OData JSON format, a client or service: MUST either: understand odata.metadata=minimal (section  REF _Ref359603569 \r \h 3.1.1) or explicitly specify odata.metadata=none (section  REF _Ref356829825 \r \h 3.1.3) or odata.metadata=full (section  REF _Ref356829837 \r \h 3.1.2) in the request (client) MUST be prepared to consume a response with full metadata MUST be prepared to receive all data types (section  REF _Ref356829873 \r \h 7.1) defined in this specification (client) exposed by the service (service) MUST interpret all odata annotations defined according to the OData-Version header of the payload (section  REF _Ref356829936 \r \h 4.5) MUST be prepared to receive any annotations, including custom annotations and odata annotations not defined in the OData-Version header of the payload (section  REF _Ref356829963 \r \h 20) MUST NOT require odata.streaming=true in the Content-Type header (section  REF _Ref354567725 \r \h 4.4) In addition, in order to conform to the OData JSON format, a service: MUST comply with one of the conformance levels defined in  REF protocol \h [OData-Protocol] MUST support the application/json media type in the Accept header (section  REF _Ref356829677 \r \h 3) MUST return well-formed JSON payloads MUST support odata.metadata=full (section  REF _Ref356829691 \r \h \* MERGEFORMAT 3.1.2) MUST include the odata.nextLink annotation in partial results for entity collections (section  REF odataNext \r \h 4.5.5) MUST support entity instances with external metadata (section  REF _Ref356921125 \r \h 4.5.1) MUST support properties with externally defined data types (section  REF odataType \r \h 4.5.3) MUST NOT violate any other aspects of this OData JSON specification SHOULD support the $format system query option (section  REF _Ref356829731 \r \h 3) MAY support the odata.streaming=true parameter in the Accept header (section  REF _Ref354567725 \r \h 4.4) MAY return full metadata regardless of odata.metadata (section  REF _Ref356829691 \r \h \* MERGEFORMAT 3.1.2) Acknowledgments The contributions of the OASIS OData Technical Committee members, enumerated in  REF protocol \h [OData-Protocol], are gratefully acknowledged. Revision History RevisionDateEditorChanges MadeWorking Draft 012012-08-22Michael PizzoTranslated Contribution to OASIS format/templateWorking Draft 01.12013-1-31Ralf HandlAdopted new, more concise JSON format Committee Specification Draft 012013-04-26Ralf Handl Michael PizzoExpanded error information Added enumerations Fleshed out descriptions and examples and addressed numerous editorial and technical issues through processed through the TC Added Conformance sectionCommittee Specification Draft 022013-07-01Ralf Handl Michael PizzoImproved rules for odata.id, odata.editLink, and odata.readLink Improved action/function advertisement Improved entity references Improved rules for relative URLs Simplified delta responses GeoJSON for Geo types Improved description of primitive value representation Improved examples, aligned with Atom format specification Aligned terms across specificationsCommittee Specification 012013-07-30Ralf Handl Michael PizzoNon-Material ChangesCommittee Specification Draft 032013-10-03Ralf Handl Michael PizzoAnnotations start with @ Next link for collections of primitive and complex type Null values in collections of primitive and complex type Improved description of relative URL resolution     odata-json-format-v4.0-os 24 February 2014 Standards Track Work Product Copyright OASIS Open 2014. All Rights Reserved. Page  PAGE 1 of  NUMPAGES 42  MACROBUTTON NoMacro [document identifier]   MACROBUTTON NoMacro [specification date]  Copyright OASIS Open 2004.All Rights Reserved. Page  PAGE 5 of  NUMPAGES 41  ./?@MSXY_abn! " # 2 3 4 @  \ ^ _ sjh{lsh{lsB*Uph hb0Jhlh\<`0JhOh\<`0JB*phhhN 0JhN hN 0J hN 0JjhN 0JUh1Dh]Qh7;h.h)CJaJhWCJaJhn(h)hN h<0'h<0'hIjhIU, /@Sa3 s > N %gdgdggd gd{lsgd7;gd\<`gd1Dgd)gd gd )gd  6 7 8    q r s t < = > E F N O wxy􏋏xe$j h{lsh{lsB*Uph$jk h{lsh{lsB*Uphh]Qh7;$j@ h{lsh{lsB*Uph$jh{lsh{lsB*Uph h{lsh{lsh?2B*phh{lsh{ls0Jjh{lsh{lsB*Uph$jh{lsh{lsB*Uphh{lsh{lsB*ph'/01>?@VWZ[|ŵ~wlw^lUlwlwhh0JjhhUjhhU hhh}h.hghgB*phh<hS0J$j h<hSB*UphhSB*phjh<hSB*UphhCLh{lsh{ls0J$j h{lsh{lsB*Uphh{lsh{lsB*phjh{lsh{lsB*Uph|}~#%12YZ[mnqrֺ液{wijuhhUhSjhhUhh0Jj7hhUjhhU hhh.hxjhhUjhhU hhhh0JjhhUjBhhU)%#eA2%1;y0 ">gd >gdIgdI>gdS>gd gd  & F gd"t@ & F gdC] & Fgd"t@gdrHagd gd!"23bcd~:;<e>?@Aj䶯|shC]hC]0JjhC]UhC]jhC]U hC]hC] hL:hShShrHahrHa6] hrHahrHah jvhhUjhhUjhhU hhhh0JjhhU-j{|}/012t"#$56_`cdz{OPSTqrsĝ}ĝhhE,Q0J hE,QhE,QhE,QjhE,QUhN h?26]h|he0J hehehejheUh?2hrHahrHa6]hShC]hC]0Jj8hC]UhC]jhC]U hC]hC] hrHahrHa1s  +,-7W[egvwx./01;  (yundnnnhXhXhi hXhXh}hrHahrHa0JjPhrHahrHaUjhrHahrHaU h{hShS hY0hShrHahrHa6]hN 0JmHsHh EAhh)0JmHsHjehE,QUmHsHhE,QmHsHjhh)UmHsHh?2 hrHahrHahN &(:$,-4owxy./-./0-.mnoʃvjghS0JU hihSh@hS0JB*phjhS0JUh9hS0JjihS0JU hS0JjhS0JUhSh $hh,hihYEhXhc5hq#oh}h?2 hXhX hXh?2-   !"?AWY^y   ] ^ p q '!(!)!¾ɮ¾wng hShSVh{lshYE0J$jXh{lshYEB*Uphh{lshYEB*phjh{lshYEB*UphhhYE0JjhYEUhN hShYE hYEhYE h\*h\<`h h\<`6 hX0J- hV0J-h^hc5hQhIh $hB*ph'"*!+!3!e!t"% &b')*(//101B111Y223o33O44 5 $  $  $ gdlgdS?gd >gd gdYE)!*!+!2!3!N!" "G"H"I"O"P"R",/8/9/G/H/K/L/s/t/u/z/{//0000011.1/101A1B1C1O1Z1[1ײߨƛƨߔ{h h)1jh Uh} h.>* h.h.j!hS0JUjhS0JUh*KhS0Jj`hSU hS0JjqhSUjhSU h.hShShwhs3~ hihI hSh *[1\1]1y1z1{1|1}1~111111111111111111111111111߬ߡjߡX#j!hps>UmHnHu*j!h{hps>0JUmHnHu#j hps>UmHnHujhps>UmHnHuhps>mHnHu'hX{ hps>CJOJQJaJmHnHu*j h{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu$jh{hps>0JUmHnHu"1122222728292S2T2U2V2W2X2Y2Z2[2w2x2y2z2222222222222ߵjߵX#j#hps>UmHnHu*j #h{hps>0JUmHnHu'hX{ hps>CJOJQJaJmHnHu#j"hps>UmHnHujhps>UmHnHuhps>mHnHu*j"h{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu$jh{hps>0JUmHnHu"2222222222 3 3 3 333333.3/303132333M3N3O3i3j3k3l3m3n3o3ҿ蠑i蠑W#j{%hps>UmHnHu*j$h{hps>0JUmHnHu#j$hps>UmHnHujhps>UmHnHuhps>mHnHu'hX{ hps>CJOJQJaJmHnHu$jh{hps>0JUmHnHu*j$h{hps>0JUmHnHuh{hps>0JmHnHuhps>mHnHu"o3p3q3333333333333333344444-4.4/4I4ߵjX#h{hps>0JOJQJmHnHu*j&h{hps>0JUmHnHu'hX{ hps>CJOJQJaJmHnHu#ju&hps>UmHnHujhps>UmHnHuhps>mHnHu*j%h{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu$jh{hps>0JUmHnHuI4J4K4L4M4N4O4P4Q4m4n4o4p4u444444444444444m[#ji(hps>UmHnHu#h{hps>0JOJQJmHnHu*j'h{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu'hX{ hps>CJOJQJaJmHnHu$jh{hps>0JUmHnHuhps>mHnHujhps>UmHnHu#jo'hps>UmHnHu4444444555555 5 5 5'5(5)5*5W5X5Y5s5t5u5w5x5ɷwnXɬF#j]*hps>UmHnHu*j)h{hps>0JUmHnHuhps>mHnHu'hX{ hps>CJOJQJaJmHnHu#jc)hps>UmHnHujhps>UmHnHuhps>mHnHu#h{hps>0JOJQJmHnHuh{hps>0JmHnHu$jh{hps>0JUmHnHu*j(h{hps>0JUmHnHux5y5z5{5|555555555555555555555556666*6ˬˡjX#h{hps>0JOJQJmHnHu*j+h{hps>0JUmHnHu#jW+hps>UmHnHujhps>UmHnHuhps>mHnHu*j*h{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu'hX{ hps>CJOJQJaJmHnHu$jh{hps>0JUmHnHu 5z551666>777b88!999E::;;<V<<<R== >q>>!? $  $  $ *6+6,6.6/606162636O6P6Q6R6b6c6d6~66666666666666666mW*j-h{hps>0JUmHnHu#jK-hps>UmHnHu*j,h{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu'hX{ hps>CJOJQJaJmHnHu$jh{hps>0JUmHnHuhps>mHnHujhps>UmHnHu#jQ,hps>UmHnHu 6666666666666777778797;7<7=7>7?7@7\7]7^7_7v7w7x77mW*j/h{hps>0JUmHnHu#j?/hps>UmHnHu*j.h{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu'hX{ hps>CJOJQJaJmHnHu$jh{hps>0JUmHnHuhps>mHnHujhps>UmHnHu#jE.hps>UmHnHu 7777777777777777777777777788m[#j31hps>UmHnHu#h{hps>0JOJQJmHnHu*j0h{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu'hX{ hps>CJOJQJaJmHnHu$jh{hps>0JUmHnHuhps>mHnHujhps>UmHnHu#j90hps>UmHnHu888-8?8@8A8[8\8]8_8`8a8b8c8d8888888888888ɷwnXɷF#j'3hps>UmHnHu*j2h{hps>0JUmHnHuhps>mHnHu'hX{ hps>CJOJQJaJmHnHu#j-2hps>UmHnHujhps>UmHnHuhps>mHnHu#h{hps>0JOJQJmHnHuh{hps>0JmHnHu$jh{hps>0JUmHnHu*j1h{hps>0JUmHnHu8888888888888999999 9!9"9#9?9@9A9B9S9a9b9c9}9ݻݻmݻWݻ*j4h{hps>0JUmHnHu#j!4hps>UmHnHuhps>mHnHu#h{hps>0JOJQJmHnHu*j3h{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu'hX{ hps>CJOJQJaJmHnHu$jh{hps>0JUmHnHujhps>UmHnHu}9~9999999999999999999999999::m[#j6hps>UmHnHu#h{hps>0JOJQJmHnHu*j5h{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu'hX{ hps>CJOJQJaJmHnHu$jh{hps>0JUmHnHuhps>mHnHujhps>UmHnHu#j5hps>UmHnHu:: ::":#:$:>:?:@:B:C:D:E:F:G:c:d:e:f:w::::::::ɷwnXɷɷF#j 8hps>UmHnHu*j7h{hps>0JUmHnHuhps>mHnHu'hX{ hps>CJOJQJaJmHnHu#j7hps>UmHnHujhps>UmHnHuhps>mHnHu#h{hps>0JOJQJmHnHuh{hps>0JmHnHu$jh{hps>0JUmHnHu*j6h{hps>0JUmHnHu::::::::::::::::;;;;;;;;;8;9;:;;;M;a;f;{;|;};ҾҰҰmҾҰWҰ*j9h{hps>0JUmHnHu#j9hps>UmHnHu#h{hps>0JOJQJmHnHu*j8h{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu'hX{ hps>CJOJQJaJmHnHu$jh{hps>0JUmHnHuhps>mHnHujhps>UmHnHu"};;;;;;;;;;;;;;;;;;;;;;;;<<<<<n\#j:hps>UmHnHu#h{hps>0JOJQJmHnHu*jz:h{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu'hX{ hps>CJOJQJaJmHnHu$jh{hps>0JUmHnHujhps>UmHnHu#j9hps>UmHnHuhps>mHnHu< <!<"<#<3<4<5<O<P<Q<S<T<U<V<W<X<t<u<v<w<x<y<<<<<<<<<<<<<ɵɪ׵ɀjɵɪX׵#j<hps>UmHnHu*jn<h{hps>0JUmHnHuhps>mHnHu#j;hps>UmHnHujhps>UmHnHuhps>mHnHu'hX{ hps>CJOJQJaJmHnHuh{hps>0JmHnHu$jh{hps>0JUmHnHu*jt;h{hps>0JUmHnHu"<<<<<<<<<<<<<<<<<<<====/=0=1=K=L=M=O=P=Q=R=S=T=ҿ蠑i蠑W#j>hps>UmHnHu*jb>h{hps>0JUmHnHu#j=hps>UmHnHujhps>UmHnHuhps>mHnHu'hX{ hps>CJOJQJaJmHnHu$jh{hps>0JUmHnHu*jh=h{hps>0JUmHnHuh{hps>0JmHnHuhps>mHnHu"T=p=q=r=s====================>>> > > > >>>+>,>ҿ败i败W#j@hps>UmHnHu*jV@h{hps>0JUmHnHu'hX{ hps>CJOJQJaJmHnHu#j?hps>UmHnHujhps>UmHnHuhps>mHnHu$jh{hps>0JUmHnHu*j\?h{hps>0JUmHnHuh{hps>0JmHnHuhps>mHnHu",>->.>N>O>P>j>k>l>n>o>p>q>r>s>>>>>>>>>>>>>>>>>>>>>ɾ׉ɀjɉɾX׉ɀ#jBhps>UmHnHu*jJBh{hps>0JUmHnHuhps>mHnHu'hX{ hps>CJOJQJaJmHnHu#jAhps>UmHnHujhps>UmHnHuhps>mHnHuh{hps>0JmHnHu$jh{hps>0JUmHnHu*jPAh{hps>0JUmHnHu">>>>>?????? ?!?"?#???@?A?B?V?W?X?r?s?t?v?w?x?y?z?{???ɾ׉ɀjɾX׉ɀ#jDhps>UmHnHu*j>Dh{hps>0JUmHnHuhps>mHnHu'hX{ hps>CJOJQJaJmHnHu#jChps>UmHnHujhps>UmHnHuhps>mHnHuh{hps>0JmHnHu$jh{hps>0JUmHnHu*jDCh{hps>0JUmHnHu !?y??0@@@.AAAUmHnHu*j2Fh{hps>0JUmHnHuhps>mHnHu'hX{ hps>CJOJQJaJmHnHu#jEhps>UmHnHujhps>UmHnHuhps>mHnHuh{hps>0JmHnHu$jh{hps>0JUmHnHu*j8Eh{hps>0JUmHnHu O@P@Q@c@d@e@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ɾ׉ɀjɉɾX׉ɀ#jHhps>UmHnHu*j&Hh{hps>0JUmHnHuhps>mHnHu'hX{ hps>CJOJQJaJmHnHu#jGhps>UmHnHujhps>UmHnHuhps>mHnHuh{hps>0JmHnHu$jh{hps>0JUmHnHu*j,Gh{hps>0JUmHnHu"@@@@@ A A A'A(A)A+A,A-A.A/A0ALAMANAOAQARAeAfAgAAAAAAAAAAɵɪ׵ɀjɵɪX׵#jJhps>UmHnHu*jJh{hps>0JUmHnHuhps>mHnHu#jIhps>UmHnHujhps>UmHnHuhps>mHnHu'hX{ hps>CJOJQJaJmHnHuh{hps>0JmHnHu$jh{hps>0JUmHnHu*j Ih{hps>0JUmHnHu"AAAAAAAAAAAAAAAAAAABBBBB BBBB5B6B7B9B:B;BUmHnHu*jLh{hps>0JUmHnHu#jKhps>UmHnHujhps>UmHnHuhps>mHnHu'hX{ hps>CJOJQJaJmHnHu$jh{hps>0JUmHnHu*jKh{hps>0JUmHnHuh{hps>0JmHnHuhps>mHnHu"BZB[B\B]B_B`BnBoBpBBBBBBBBBBBBBBBBBBBBBBBB߬ߡjߡX#jNhps>UmHnHu*jNh{hps>0JUmHnHu#jMhps>UmHnHujhps>UmHnHuhps>mHnHu'hX{ hps>CJOJQJaJmHnHu*jMh{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu$jh{hps>0JUmHnHu"BBB C CCC"C#C$C>C?C@CBCCCDCECFCGCcCdCeCfCuCvCwCCCCCCCCCCߵjߵX#jsPhps>UmHnHu*jOh{hps>0JUmHnHu'hX{ hps>CJOJQJaJmHnHu#jyOhps>UmHnHujhps>UmHnHuhps>mHnHu*jNh{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu$jh{hps>0JUmHnHu"CCCCCCCCCCCCCCCCC D D DDDDD D!D;DUmHnHu*jQh{hps>0JUmHnHu'hX{ hps>CJOJQJaJmHnHu#jmQhps>UmHnHujhps>UmHnHuhps>mHnHu$jh{hps>0JUmHnHu*jPh{hps>0JUmHnHuh{hps>0JmHnHuhps>mHnHu"DD`DaDbDcDeDfDrDsDtDDDDDDDDDDDDDDDDDDDDDDDDDDҿ蠑i蠑W#j[Thps>UmHnHu*jSh{hps>0JUmHnHu#jaShps>UmHnHujhps>UmHnHuhps>mHnHu'hX{ hps>CJOJQJaJmHnHu$jh{hps>0JUmHnHu*jRh{hps>0JUmHnHuh{hps>0JmHnHuhps>mHnHu"DDD E E EEEE%E&E'EAEBECEEEFEGEHEIEJEfEgEhEiEEEEEEEEEEE߬ߡjߡX#jOVhps>UmHnHu*jUh{hps>0JUmHnHu#jUUhps>UmHnHujhps>UmHnHuhps>mHnHu'hX{ hps>CJOJQJaJmHnHu*jTh{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu$jh{hps>0JUmHnHu"EEEEEEEEEE F F FFFFFFF0F1F2F3F5F6FDFEFFF`FaFbFdFeFfFgFߵj߀ߵX#jCXhps>UmHnHu*jWh{hps>0JUmHnHu'hX{ hps>CJOJQJaJmHnHu#jIWhps>UmHnHujhps>UmHnHuhps>mHnHu*jVh{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu$jh{hps>0JUmHnHu"gFhFiFFFFFFFFFFFFFFFFFFFFFFFFFFFFGGGGG߬ߡj߬ߡX#j7Zhps>UmHnHu*jYh{hps>0JUmHnHu#j=Yhps>UmHnHujhps>UmHnHuhps>mHnHu'hX{ hps>CJOJQJaJmHnHu*jXh{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu$jh{hps>0JUmHnHu"GGGGG7G8G9G:GUmHnHu*j[h{hps>0JUmHnHu#j1[hps>UmHnHujhps>UmHnHuhps>mHnHu*jZh{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu'hX{ hps>CJOJQJaJmHnHu$jh{hps>0JUmHnHu"GGGGGGGGGGGGGHH H#H$H%H'H(H)H*H+H-H.H:H;HHHHӿӱӱӿxtmibiZijhZU h.hZhZ h}h}h}jh U#j%]hps>UmHnHu*j\h{hps>0JUmHnHuhps>mHnHuh{hps>0JmHnHu'hX{ hps>CJOJQJaJmHnHu$jh{hps>0JUmHnHujhps>UmHnHuhps>mHnHu*H,H-H.H;HII5JJJKtKK+LLLLMMN-OOP(gdZ  & F gdZ\ & F dgdZgdZ & F Q^`QgdZ@gd HHHHIIIIIIIIIIIIJJJ2J3J7J8J^J_J`JjJ~JJJJJJJJJJJJJJJK K K KK캰쟖산w쟖j `hZUh{/hZ0Jj_hZUh UhZ0J hZ0Jj_hZUjhZ0JUhNhZ0Jj^hZUh9hZ0J-j^hZUhZ hZ0J-jhZUj]hZU.KK)K*K+K8K9K=K>K`KaKbKrKsKvKwKKKKKKKKKKKKKKKKKKLLLL)L*L-L.LXLYLZLjLkLLLLLLLLղ߹jchZUjchZUjbhZUjbhZU h:hZ hZ0JjahZUj ahZUjhZ0JUh UhZ0Jj`hZUhZjhZU4LLLLLMM M M M MMMMMMM!M"M+M,M.M/M5M6M8M9MCMDMFMGMRMSMUMVMYMZM`MaMiMMMMMMMMMM'N(NJNKNLNdNeNh~hZB*ph""" h~hZhZB*ph"""h9hZ6 h.hZh.hZ0J-^JaJh9hZ0J-jCdh0,hZU h0,hZjh0,hZU hDhZhZ hehZ7eNfNNNNNNNNNNNNNNOO+O,O9O:OHOIOJOZOuOvOOOOOOOOOOOOPPPPP%P&P'P}s}hZ5B*phh]rhZ5B*phh#hZ5 hyehZ h9hZhZB*^JaJph""" h4xhZ hZ6h9hZ6hZ hZ0J-hZB*ph"""hBhZ0JjdhBB*Uph"""hBB*ph"""jhBB*Uph"""-'P-PAPPP`PlPPPPPPPPPPPPPWQXQQQQQQQQQQQQQQQQQQQQӻxqjjjjq h$nkhZ hEthZhEthZ0J- hZ0J- hw7hZjhZ0JUhw7hZ0JjehZUjhZU h9hZh9hZ0J- hIhZhnOhZ6 hnOhZ hZ5hnOhZ5 h4xhZhZ hZ6hMzhZ6&PPPQRcS3TUUVTVVV1WbWWWWXVYZA\^_ & F Q^`QgdZgdZ;gdZZgdZgdZ & FgdZ(gdZQQQ R RRR!R%R&R)R-R/R;R=R>RoRpRqRRRRRRRRRRRRRRRRRSS S:S;Sbnbob»騳ujjalhZUjkhZUhMhZ0JOJQJjhZ0JOJQJUhMhZ0JOJQJj/khZUjhZU h [hZhhZ0J h<hZ h$hZh hZ0J h$hZhZjhZ0JUhjhZ0J)__`Raaaa=bbccee-hDhikckkNllm\ & F dgdZ  & F gdZ  & F gdZ\ & F*gdZgdZ & F Q^`QgdZobpbbbbbbccc'c(c)c4c6c7c8c9c:cccccc ddddidrdddee(e.e7eOeTe]eff+f,fżر؝ؒvvvmvvvh2FGhZ0JhGhZ0JjhZ0JUhIahZ0JjmhZU haWkhZ hZ5hnOhZ5jmhZUhhZ0J hZ0Jh3hZOJQJ^JhZjhZ0JOJQJUhMhZ0JOJQJjhZU*,fSfTfUfZfcfkflffffffg gggggggggg-h.h2h;hChIhNhWhXh_hhi iRiXicijiiiiiiujohZUh^hZ0Jh\hZ0JhMhZ0J hZ0JhPhZ0JOJQJj(ohZUjnhZUjhZ0JOJQJUhZ0JOJQJhjhZ0JOJQJjhZUjnhZUhZ-iiiiii"j#j$j*j1j2jkk-k.k/k9k:kckdkkkkkkkkl l lllNlOljlklll{l|lùۓë}ërehJ$LhZ0JOJQJj>rhZUjqhZUjRqhZUh hZ0JOJQJjphZUjhZ0JOJQJUhZ0JOJQJh`hZ0JOJQJj:phZUjhZUhZ hZ0JjhZ0JUh=hZ0J'|lll^mcmnn@nAnBnQnRn{n|nnnnnnnnnnnno ooooooo p p ppppkplppppppppq듉~j~thZUhZ0JOJQJh`hZ0JOJQJjshZUhrhZ0J hZ0JjHshZUjhZ0JOJQJUh9.hZ0JOJQJjrhZUjhZUh\hZ0JhZ0mn{nnnxookppVqqrVrrsPttuubvv1wwwxAy$gdZ  & F gdZ\ & F dgdZgdZqqq q!qVqWqrqsqtqqqqqqqqqqrr0r1r2rv?vbvcvvvvvvvvvvvww1w2wͷѣͣͣ̀͘uj{hZUjzhZUh9.hZ0JOJQJjyhZU h"ohZh"ohZ0JOJQJjyhZUjxhZUhZjhZ0JOJQJUh hZ0JOJQJjhZUj+xhZU.2w[w\w]wswtwwwwwwwwwxx3x4x5xCxDxIxJxexfxgxrxsxxxxxyyy/y0y1y>y?yoyſſſΠſxnjhZ0JUh}hZ0Jj.}hZUh}hZ0Jj|hZU hhZhWNhZ0JOJQJjB|hZU hZ0JhOhZ0JjhZ0JOJQJUh9.hZ0JOJQJjhZUj{hZUhZ(Aykyz'|| }j~~~~,؀VaƆ׆!\ & FgdZ & F Q^`QgdZgdZ  & F gdZoyyyyyyyyyyyyyzzz(z)z9zDzgzxz~zzzz{{,{-{.{:{;{A{B{{{{{{{{{{%|Ĵޒ~tjhZ0JUh.hZ0Jj~hZUh!DhZ0J-j@~hZU h+>hZ h4hZjhZ0JOJQJU^Jh^hZ0JOJQJ^Jj}hZUjhZU hhZhZ hZ0JhZhZ0J,%|&|G|P|U|`|||||||||||| }$}>}}q~}~~~~~~9>?FLRx}*̾vhghZ0JOJQJj-hZUhhZ0Jht4ShZ0JhcHhZ0J h0hZ hhZ hX-hZjhZ0JOJQJUhpLhZ0JOJQJjhZUjhZUhpLhZ0JhZ hpLhZ,*+GHxyz̀ր %)-2@Aqrs !"#)*,/0R푇|smf hxhZ hZ0JhHhZ0JjhZUjhZ0JUhjhZ0Jj_hZUh hZ0Jh2FGhZ0J hhZhZhZ0JjhZ0JOJQJUhy<@hZ0JOJQJjhZUjhZUhZ hZhg'RSTdekl>?@OPTU{|}ȃɃʃջհ՜ٌzqٌfj&hZUh;dhZ0JjhZU h;dhZ htghZhrhZ0Jj hZUhhZ0JjhZU hZ0JhHhZ0JjhZUhZjhZ0JUhOphZ0JjhZUjqhZU()*?FVWuvwyޅ߅,-TUV`aڥڄvkjThZUjhZ0JOJQJUh4(%hZ0JOJQJjņhZUh ]AhZ0J hZ0Jj.hZUh hZ0J h~8hZh ^hZ0JjhZUjhZUhZ htghZjhZ0JUhrhZ0J'M%)eik2y >  & F gdZgdZ`gdZ $`gdZ$gdZ;gdZgdZ\ & FgdZ U_89:IJŠϊ "$)*0ERSZ\bdijȾ鵧h hZ0J h3XhZ h'(qhZjhZUmHnHuhZmHnHujhZ0JUhhZ0JjŇhZUhZ%hZ0JhZjhZUhEthZ0J- hZ0J-8:Cȍ͍ߍ-y̎؎ߎ)*+,/=GJLbktzƏȏΏЏӏԏ$&'ֵjhZUmHnHuhZmHnHujhZU hyhZhKuhZOJQJ^Jh|hZOJQJ^JhyhZ0Jh2FGhZ0JhrhZOJQJ^J hZhohZ:Ǐ'JOW͓ 4fD  & F gdZ  & F gdZ\ & F dgdZgdZgdZ;gdZZ`gswɑʑΑ c~˒͒Β#4Uafsv ”͔Δ̸ hShZhhZ0JjhZ0JUh=hZ0JjFhZUjhZUh,|hZ0JhhZ0JhZ hZ0J hyhZhhZ0J<*JOZ[` 9:YZ[߲߲{qi^iXiiMijFhZU hZ0J-jӈhZUjhZUhZOJQJ^JhhZOJQJ^J hZ0JhhdhZ0JhZ,hZ0JRB*^JaJfHphq (hZB*^JaJfHphq h"lhZ0J hZaJh2ghZaJ.h? hZB*^JaJfHphq h? hZaJ[cdjpwɖʖ ~їҗSTstuʰ醚xmg\jÊhZU hZ0J-jPhZU h.}ehZ hf8hZ h ]AhZhHhZOJQJ^J hZ0JjhZ0JOJQJU^JhhZ0JOJQJ^JjʼnhZUjhZUhZOJQJ^JhhZOJQJ^JhZjhZ0JUhXhZ0J"uԘ՘'(?@ABFIJPWYZfoәٙử鞦镏鈏hhZ0J hhZ hZ0JhOhZ0JhZB*ph h=ihZjhZUmHnHuhZmHnHuhYhZ0Jho+1hZ0JjBhZUjhZUhZjhZ0JUhhhZ0J2DFƙșПUߡkѤ;gdZ\ & F dgdZgdZ  & F gdZgdZ$gdZKm͚̚ΚޚߚDNr|МќҜݜޜ`a #>?fghopt흓xohhZ0JjόhZUh:thZ0J h6hZjhZ0JUhhZ0Jj:hZUhK$hZ0Jh 5hZ0Jh\hZ0JhhdhZ0J hZhmS hZ0J-j͋hZUjhZU hhZhZ+tuşΟ>HUpqՠ֠_dehimnšˡ̡͡סݡ 78_`akhXhZ0JjhZUh6hZ0JhwphZ0Jh%khZ0Jh&hZ0J h4hZh\hZ0Jh<hZ0JjhZ0JUhhZ0Jj^hZUhZjhZU0kl:HJOghãģƣǣ4Qk¤ΤϤѤ٤ڤٿِـrehhZOJQJ^JjhZUmHnHuhZmHnHu h?hZ hZ0J-jhZU hXhZ h6hZjhZ0JOJQJU^JhhZ0JOJQJ^JjxhZUjhZUhJhZ0J h4hZhZjhZ0JU'lv{ץޥ T\]tuvwxyҦӦ֦צئަ+ȿЪhZOJQJ^JhhZOJQJ^J hfXhZjhZUmHnHuhZmHnHujhZU h?hZ h'(qhZ h[ghZ hJuhZh-[HhZ0JhZ hChZ:(NRTҦԦalpr!;&ªgdZ  & F gdZ`gdZ$gdZ;gdZgdZ $`gdZ+,-M`chik} /01PQRSWXfghxyzʾ۠}woh hwhZh:<hZ5 hZ0J-jhZ5U hZ5jhZ5U h;^NhZhRhZ0Jj/hZUjhZ0JUhRhZhh0J hZ0JjhZUjhZUhRhZ0JhOhZ0J h'(qhZhZ&,:?MMN|}~ƪ̪ժ8>G˫ѫ٫./@ABȷٗЗЗЗЗٗ|jhZUhhZ0J hhZ hZ0J hOhZjhZ0JUh-hZ0J hZ0Jj!hZUjhZUhRhZ0JhOhZ0JhxhZOJQJ^JhZhwhZOJQJ^J0BRSTUͬάϬЬCDEJSXYgi٭ڭͶ򊀊rj_jhZUhT3yhZ6jhZ0JOJQJUhZ0JOJQJh;?XhZ0JOJQJj#hZU hZ0Jh\hZ0J hZ5h]rhZ5jhZ0J5UjhZ0J5Uj1hZUhhZh0hZjhZU hZ0J-$EFVWX`abѮٮ08UVuvwǯϯ '(/ﴪwmwmhZ0JOJQJh;?XhZ0JOJQJjhZUh hZ0JhrhZ0JhQ;hZ0JjhZ0JUhhhZ0JjhZUh>hZ0JhnhZ0J hZ0J-jhZUhZjhZUhEthZ0J-(б?>V׵L]G]bȺd>.z\ & F dgdZ  & F gdZgdZ/0FNϱбԱ)*+;<=>?CQвղ+,-67햼턼{qjhZ0JUh hZ0JjhZU hhZjhZUhhZh`qK hZ0J-jhZUjhZUhOhZ0J hhZhLhZ0J hZh+Q<hnhZ0JhZjhZ0JOJQJU,7ͳֳܳ Zh̴δ!:;jkn|׵۵)*+09սrhhZ0JOJQJh;?XhZ0JOJQJjhZU hZh h%FhZ0J h hZ hhZ hy hZjhZ0JOJQJUhZ hZ0JOJQJjhZUjhZUhOhZ0J h`qKhZ hZ0JhnhZ0JhZ(9>?MO¶ö,7=>Jao÷ѷҷFQRX\]ab¨~wpgaa hZ0JhOhZ0J hZh_B hA%hZ hthZ hhXhZjhZ0JOJQJU^JhZ0JOJQJ^JhhZ0JOJQJ^Jj1hZUjhZUhZ hZ0J hhZ hy hZhZjhZ0JOJQJUh;?XhZ0JOJQJ%bfkmab̹ѹ׹$źƺ̺ ;ޯzz hZ6hD}hZ0JjhZUh hZ6h0hZOJQJhOhZ0J hZ0J-j1hZUjhZ0JUh#"@hZ0JjhZUjhZUhZ hhZ hZ0JhhZ0J.;<=AEF˻̻ dh}B\nƽѽս!-23QRSϻ쮠ϓππ{ulajWhZUhz(hZ0J hZ0J hZ6h hZ6h0hZOJQJh9hZ0JOJQJjhZ0JOJQJUh hZ0JOJQJjȚhZUh hZ0JhZjhZ0JUh hZ0J hZ0JjhZUj)hZU#Sabgh׾ؾ <BGOTgz~ckmO鰿靔鍇~qj~~ h<hZh:^[hZOJQJ^JhOhZ0J hZ0J hhZhQ.lhZ0J hZ0J hZ5h]rhZ5jМhZ0J5UjhZ0J5UjWhZUjԛhZUjhZUhZjhZ0JUh|_hZ0J)OP%178;</6:<> &(+,-BCY\]^vw hOJhZjhZUmHnHuhZmHnHujhZU h?hZhQ.lhZ0J hZ0JhpLhZOJQJ^J h KhZ hZ0Jh74hZ0JhZ hhZ;!+)Z+W'|&KM & F Q^`QgdZgdZ$gdZ;gdZgdZ#(<BI15H` gj zpi h /hZjhZ0JUhphZ0JjhZUhghZ0J hZ0J-jIhZUjhZU hZ5 hL<hZh'}_hZ0JhR:hZ0Jh+^hZ0JhZOJQJ^JhLhZOJQJ^J hZhI hZ hOJhZ) VW`dhiBFJKkz|}$%󱙐{d,hZ0JRB*^JaJfHphq (hZB*^JaJfHphq h2ghZaJ.h? hZB*^JaJfHphq h? hZaJh7X%hZOJQJ^J hZ0J hZaJ hZh!-h-hZ0JhghZ0J h\hZhZh\hZ0J'%&./FGHIJv} ()*23%&'-./=>?OPo褚䒋ynh hZ0J-jȞhZUhZhh0JhVhZ0J hZhphM\hZ6jhZ0JUhyhZ0Jj=hZU hi3hZ hZh\I h;hZjhZUmHnHuhZmHnHuhZjhZU h?hZh? hZaJ((DKRp8QX^$gdZgdZ`gdZBQw+=WY[`gdZ;gdZgdZ & F Q^`QgdZgdZorsIJKVWڿ墭儭{tk]tjhZUmHnHuhZmHnHu h?hZh5hZ0JjEhZUjhZ0JUhWrhZ0JjhZUjhZUhhhZhM\ hZ0J-j5h:<hZU h:<hZjh:<hZUhZhM\hZ6h:<hZ5 hhhZ# $8?ABGHPQ_`vw !*-67<?LMNPVWXY[cd{|~hZmHnHujhZU h?hZhZnHtHh|2hZnHtHhZ hZ0Jh`hZ0JH~ 7PYbcejkst()9<CDMPźūh`[hZmHnHsHtHh(p(hZnHtHhZnHtHh|2hZnHtHh`hZ0J hZ0JhZ h?hZjhZUmHnHuC[ <et:N`{X & F Q^`QgdZ`gdZgdZ;gdZ7@UVzde!"#JKLhκݥκݚκ݂yh.hZ0JjYhZU hZ0J hhZjơhZUjGhZUjhZ0JUhJhZ0JjĠhZUjhZU h.hZhZh|2hZnHtHhZnHtHhZmHnHsHtH/hijk"HLQVgkoquz|䰧䰕䰕䰕䰕䰌䰆䰕䰌}h,hZ0J hZ0Jh ;hZ0JhY /hZ0Jh|JhZ0Jh1khZ0Jh:hZ0JhbhZ0J hZ0J-h9hZ0J-jhZUjhZUhZ hlhZ hZ0JjhZ0JU1k{W&^/Rh`gdZgdZ;gdZ\ & F dgdZ  & F gdZgdZ%&59?KVX\acqvx˾ hZ5jhZ5UheAThZ0J h#hZhahZ0JhuhZ0JhhZ0Jh:hZ0JOJQJh PhZ0J hZ0Jh(hZ0Jh:hZ0J hZh9hZh,hZ0J3./09:;<-12JNgq>ORиرب؟ؖؖؖ؈qjc h9hZ h,ajhZjhZUmHnHuhZmHnHu h?hZ hhZho0hZ0JhhZ0Jh\&hZ0J ho0hZh.hZ0J-^JaJjģhZUjhZUhZ h:YhZ hZ0J-jhZ5UjYhZ5U&R^_ghvx~"#35DEPRSwyz!)*ABDEF.>GHNOQmtõj5hZU h`&hZjhZUmHnHuhZmHnHujhZU h?hZh<hZ0JhZhU<0JSh'>hZ0JShZ hZ0JS@#Ez!GI  $`gdZ$gdZ;gdZgdZ  & F gdZgdZ`gdZ.S %DGpr'-Ofms$gdZ`gdZgdZ;gdZgdZ  & F gdZS[\stvwxFG,-.5;<=>MQ.CabĻܦܛĻ܂hHhZ0J hTbhZh\hZ0JjhZU hihZjhZUmHnHuhZmHnHujhZU h?hZhbhZ0JhZ h`&hZjhZ0JUhrhZ0J hZ0J3')=BD<;gdZ  & F gdZgdZ & F Q^`QgdZ$gdZgdZb/4=B#$;<>?@DGHNUWXdmnu|驛}}hHhZ0J h~8hZ hhZ h=ihZjhZUmHnHuhZmHnHu h?hZ h`7hZ hcahZ hZ0Jh=ihZ0JjhZ0JUhS`QhZ0JjhZUjIhZUhZ. './019GRVZsxy\]uսն즘ՑՑՑՑՑՑՑՊՊՊՊՃzhBShZ0J h~8hZ hhZ h=ihZjhZUmHnHuhZmHnHu h?hZ h`7hZhUhZ0J hZ0Jh=ihZ0JhZjhZ0JUhS`QhZ0JjhZUjȥhZU017{q 35| $`gdZ$gdZ;gdZgdZ  & F gdZgdZuvw}~ ,պկ좔Չ|u|k|d] h?hZ h~8hZhZ0JOJQJ ht;}hZh\s"hZ0JOJQJjhZUjhZ0JOJQJUh=(hZ0JOJQJj=hZU hZhhhBhZ0JjhZUhZjhZ0JUhBhZ0JjhZUjGhZU$,-/01589?FHIU^ryz{| bc "#%&'ƻղէՅՅzzh0 hZnHtHh \~hZ0JjhZ0JUhBp0hZ0J hZ0JjqhZUhBp0hZ0JhU;hZnHtHhZnHtH h=ihZhZ h?hZjhZUmHnHuhZmHnHujhZU0 !"#,./012@ADFQUZ\k'(/:IhӻjhZUhqUhZ0J hEUhZhZhZhU&`nHtHh2$6hZnHtHh0 hZnHtHhZnHtHJ2<BGVZ\kl=#;gdZgdZ  & F gdZgdZ`gdZ:;Z[\ijnw<="#+,CDFGH üռ쬞՗՗Տh2$6hZnHtHhZnHtH hhZjhZUmHnHuhZmHnHu h?hZ hBp0hZ hqUhZjhZUhZjhZ0JUhm hZ0JjhZUjhZU, QAG :@BO GI;gdZgdZ & F Q^`QgdZgdZ /Q #.67>?@AchkϼǭϏdžxqqqqqqqqjj h|hZ h=ihZjhZUmHnHuhZmHnHu h?hZ hhhZjhZ0JOJQJU^JhhhZ0JOJQJ^JjhZUjhZUhZ(hZB*^JaJfHphq .hChZB*^JaJfHphq )  ()@ACDEGHKLMSZ\]kmnopqͳ͌~skskskskskskskshZnHtHhhZnHtHjhZUmHnHuhZmHnHu h?hZ hhhZjhZ0JOJQJU^JhhhZ0JOJQJ^JjhZUjhZU hZ0JhZmHsHhYShZmHsH h:hZ h|hZhZ*qu7<RStuvkpتت h2hZj4hZUjhZ0JUhrhZ0JjhZUhrhZ0J hZ0J-j>hZUjhZUh;:hZ0JhZhhZnHtHhZnHtH3K:qse/=?su;gdZgdZ & F Q^`QgdZgdZ67:BCZ[]^_?GH_`bcdRZ[rsuvwռ쳥ռ쳥ռ쳥ռ쳥ռ쳥՟ՔjhZU hZ0JjhZUmHnHuhZmHnHu h?hZjThZU h2hZhZjhZ0JUh2hZ0JjhZUjŬhZU:PR*A > e g        & F Q^`QgdZgdZ;gdZgdZ !"-.01KLM[\`ab}~rwΫҤΙΆΆ}wΆljhZU hZ0Jht4ShZ0J hZ0JhhZ0JOJQJjhZU h|hZjhZUhL)hZ0JOJQJjhZUhZjhZ0JOJQJUhZ0JOJQJhhZ0JOJQJjhZU( 789^_  : ; < E F J K i j k r s         > F G ^ _ a ԵجԚجԏ؂tmdhZmHnHu h?hZjhZ0JOJQJUhhhZ0JOJQJjhZUj~hZU hhhZhhhZ0JjhZUhBhZ0JjxhZUhZjhZU hGY#hZ hZ0JjhZ0JUh$hZ0J'a b c ) * ; < = M N O P        @ A [ \ ] g h        O T    ߳ߑxofhsNhZ0JhsNhZ0JjhZUjhZ0JOJQJUh"ohZ0JOJQJjhZUjhZ0JUhhZ0JjhZU h^LhZ hZ0J-jhZUjhZUhZ h?hZjhZUmHnHu%     j f 57~.\`gdZ;gdZgdZ & F Q^`QgdZgdZ        $%'(BCDRSWXYtuvøàǙÅxqhZqjhZUmHnHuhZmHnHu h?hZhhZ0JOJQJjKhZUh$hZ0J h|hZjֵhZUhL)hZ0JOJQJjEhZUhZjhZ0JOJQJUhZ0JOJQJhhZ0JOJQJjhZUjhZU#567?@WXZ[\~$:?OPvwx}~}rj·hZUjhZ0JUhMghZ0Jj5hZUhghZ0J hZ0J-j¶hZU h\hZ hohZ h?hZjhZUmHnHuhZmHnHujhZUhhZnHtHhZnHtHhZ, %&',-12PQRYZ&'ab{qjhZ0JUh6@hZ0JjhZUjhZUh-hZ0JjhZUjkhZUh)h|hZ0JjhZUh^hZ0JjqhZUjhZUhZjhZ0JUhMghZ0J,\1rC`b!(.`gdZ$gdZ\$ & F(^`gdZm$;gdZgdZ34678r}_`deflsu}.2456<CEFG]ǹ樝zpzpzppppppzpzpzpphZ0J1CJaJhohZ0J1CJaJhthZ0J1CJaJhhZ0J!hhZ0J!CJ hhZ0J!CJOJQJ^JjhZUmHnHuhZmHnHujhZU h?hZ h`hZhZ hhZ hZ0Jh6@hZ0J,]z{P\stz KQRUVaeghiovxyzǼhmhZ0J1CJh<hZ0J1CJh<hZ0J1CJaJhZ0J1aJhohZ0J1CJaJhZ0J1CJaJhthZ0J1CJaJD!@_fl,KT[a3gdZ  & F gdZ$gdZgdZ23xyGHpqrਜzm_RhZhZOJQJaJjhZ0JOJQJUh$hZ0JOJQJjhZU hZhf(+jhZ0JOJQJU^JhZ0JOJQJ^JhhZ0JOJQJ^JjhZUjhZ0JUh.}ehZ0JjhZUjhZU h"hZhZh45ThZ0J1CJaJ 6\\k &!1!q!!"""##~$$$%%a&&d'#gdZ#$gdZ\ & F dgdZ  & F gdZgdZ!'3[\^efξulbWj|hZUjhZ0JUhhZ0JjhZUhrEhZ0JhCMhZ0J hZ^J hBhZhBhZ0J hZ0JhZshZ0J hVhZjhZ0JOJQJU^JhZ0JOJQJ^JhZshZ0JOJQJ^JjhZUjBhZUhZ" $ % & ? @ _ ` a i j k q      $!%!_!o!p!!!!!"""#"T"咁tg]ghZOJPJQJh.$hZOJPJQJhow7hZOJQJ^J hZhZCJOJQJ^JaJ hXhZhZhZ^JhP+whZ0JhrEhZ0JjhZ0JU^Jh2ahZ0J^JjhZU hZ^Jh{hZ^JhZ hVhZ hBhZjhZU#T"U"V"\"c"d"g"""""""""""""######R#m#n####tkaVjhZUjhZ0JUhhZ0Jj5hZUhrhZ^JhrEhZ0JhCMhZ0J hZ^J h*hZ hZ0JhZshZ0JhZ hVhZjhZ0JOJQJU^JhZ0JOJQJ^JhZshZ0JOJQJ^JjhZUjhZU###########$$$ $!$"$7$R$S$r$s$t$|$}$~$$$$% %%(%)%:%A%%%źɱŜɑŁŁŁzm`h2|hZOJQJ^JhWfhZOJQJ^J hWfhZ h|hZh4yhZ^JhS`QhZ0J^JjhZUjhZ0JUhhZ0JjKhZUhZjhZU hZ^JhrEhZ0JhrhZ^JjhZ0JU^Jh2ahZ0J^J%%%%&&!&"&#&'&.&/&H&N&S&_&a&q&x&y&&&&&&&&&&&&'''' '璆voof`fWhhZ0J hZ0JhZshZ0J hVhZjhZ0JOJQJU^JhZ0JOJQJ^JhZshZ0JOJQJ^JjhZUhZOJPJQJh#hZOJPJQJjhZ0JU hZ0Jh1YhZ0JjahZUjhZUh2|hZOJQJ^JhZ" '!'('4'c'd'j'q'r''''''''''''((((((*(h(n(u(v(((((((((((((ա݃xmj*hZUjhZUh~0hZ^Jh4yhZ^JjhZ0JU^Jh2ahZ0J^JjhZUjhZ0JUhhZ0Jj}hZUjhZUhhZ0J hVhZhCMhZ0J hZ^JhZ*d'(h()));*+,.f.%/////00U0W0000gdZ`gdZ$gdZ;gdZgdZ & F Q^`QgdZ\ & F dgdZ(())))d+y+}+~+++++++++++++++(,-,2,8,:,<,I,J,p,q,r,ܿܮ܀܀xmbjhZUhi3hZ^JaJhZ^JaJht4ShZ0JjhZ0JOJQJUhZ0JOJQJh;?XhZ0JOJQJjhZU hZ0J-jhZUhihZ0Jh8\'hZ0JhZjhZ0JU^JhS`QhZ0J^JjhZU"r,},~,,,,,----=->-?-E-F-.".i.j........-/./E/F/H/I//ξζΫζ΅{rζζi[jhZUmHnHuhZmHnHuh+JhZ0JhZ0JOJQJjhZUjhZ0JOJQJUhohZ0JOJQJj,hZUjhZU hlqhZht4ShZ0JhZhZ^JaJhi3hZ^JaJjhZ0JU^JaJhi3hZ0J^JaJ!//////////////////////00 0 0$0%0'0(0U0V0W0X0Y0_0f0h0i0v0}00000000000000000000001 1)1*1-1/1617181@1A1X1Y1[1\1111111 h~8hZjhZUmHnHuhZmHnHujhZUhZ h1PhZR0+101618111112;2@2S2U2b23344A56J6L66$gdZgdZ & F Q^`QgdZ`gdZ;gdZgdZ111111111111111111222222292:2=2?2S2T222333333333444"4$4&43444Z4[4\4̴jhZUhi3hZ^JaJhZ^JaJht4ShZ0JjhZ0JOJQJUhZ0JOJQJh;?XhZ0JOJQJj@hZUjhZUh8\'hZ0J h1PhZhZ4\4g4h4i4j44444D5E5l5m5n555556 6 6!6#6$6J6K6L6M6N6T6[6]6^6k6r666666666666νβΑννzssssssssssν h1PhZjhZUmHnHuhZmHnHuh+JhZ0JjhZ0JOJQJUhZ0JOJQJjXhZUjhZUht4ShZ0JhZhZ^JaJhi3hZ^JaJjhZ0JU^JaJhi3hZ0J^JaJ-666667I7^77777788H8]888888829gdZ & F Q^`QgdZ`gdZ$gdZ;gdZgdZ666666677777777&7?7F7H7I7[7\7]7b7j7k7r7777777777777777778888 88888&8-8G8H8Z8[8\8a8i8j8q8888888888888888]: h~8hZ h1PhZjhZUmHnHuhZmHnHujhZUhZO29:j::::::::;;;/; <====0>[>h>n>>> & F Q^`QgdZ`gdZgdZ;gdZgdZ]:a:r:s:::::;; <<=<?<@<B<M<U<w<|<================p?@@WAAA!B"BBBBƽ}hthZ0Jh hZ0JhZB*ph hNhZ hZ0J-jhZU hZ5hGhZ0Jh[yhZ0J h[yhZ h&M?hZjhZUmHnHuhZmHnHujhZUhZhhZ0J.>>+?d?j?n?p?@@XABBCD_EEE7FFGH:IJaKK & F Q^`QgdZ  & F gdZgdZgdZBBBBBCDsDtDDD;EjhZ0J$KKKKK8M9MGMWMZM_M`MMMMMMMMMMMMM N N N(N0NNNNN'O(OOO_QgQhQQQQQQυ~~sjhZU hBhZ hrhZ hoAhZjhZ0JUjhZUh9hZ0JjhZ0JUh9hZ0JjDhZU hhZ h~8hZjhZUmHnHuhZmHnHujhZUhZ,KKKLLCLZLkLsLLLLLLMM-M3M7M9MGMOOO_QQgdZ & F Q^`QgdZgdZ;gdZQQQQQQQrRsRRRRRRRRSSSSSSSSSSSSSTTTTT!T4T>T?TXTYTZT_T`TzTTTTU鼲שמשדש׈ׁ hZhTjthZUjhZUjzhZUh.-\hZ0JjhZ0JUhd2hZ0JjhZU hchZhZ h |hZ hBhZjhZU hZ0J-h9hZ0J-/QQSiSwSSzTT U1URUUV W WSWWXDXX\ & F gdZ \ & F gdZ \ & F gdZ \ & F gdZ \ & F gdZgdZgdZ & F Q^`QgdZUUUUUeUjUkUvUUUUUUUUUUV(V)V-V2VRV_VVVVVVVVVVVVVVWWW W WWWW責vjhhZUhZOJQJ^Jh$hZOJQJ^JjhZUhDhZ0J hZ0J h$hZjnhZUhA,hZOJQJ^J h.-\hZ h-FhZh.-\hZ0JhZjhZUjhZU-WWWWWWWWWWWXXXXXXXCXDXQXdXeXnXoXXXXXXXXXXYYYȫwm`h/EhZ0JB*phhZ0JB*ph(jhA,hZ0JB*Uph"jhA,hZ0JB*UphhA,hZ0JB*phh_hZ0J^J h/EhZjXhZUh$hZOJQJ^Jh hZOJQJ^JhZ hZ0J-jhZUjhZU$YYYYY^Y_YxYyYzYYYYYYYYYY=ZDZbZcZ|Z}Z~ZZZZZZZZZZZZZZZZ[&[0[1[{jh_hZ0JUhNPhZOJQJ^Jj6hZUhThZOJQJ^JhZhZOJQJaJjhZUh$hZOJQJ^JjDhZUjhZUhZjhZUjRhZU,X YYY*ZZZd[t[\\"\'\.\;\ $Ifgd` $$Ifa$gd`gdZ, gdZ\ & F gdZ \ & F gdZ1[J[Z[[[\[a[b[c[d[t[x[[[[[[[[[[[\\\\;\<\K^S^U^c^i^w^S`T`U``üÙÃ|sssjd hZ0Jh]hZ0Jh]5ZhZ0J h2hZh2hZ5 *hT~hZ hZ0J-j0hZUjhZUhmhZ^J hmhZ h/>5hZhZh,4hZ0JB*phjh_hZ0JUjh_hZ0JU hZ0Jh_hZ0J$;\<\M\X\f\\^UUUU $Ifgd`kd$$Ifl\T $TFL t0644 lalyt`\\\\\\\^UUUUU $Ifgd`kdG$$Ifl\T $TFL t0644 lalyt`\\ ]]]-]H][]]]^UUUUUUUU $Ifgd`kd$$Ifl\T $TFL t0644 lalyt` ]]^^*^8^x^^^^^UUUUUUUU $Ifgd`kd$$Ifl\T $TFL t0644 lalyt` ^^ _C_}______Ukd3$$Ifl\T $TFL t0644 lalyt` $Ifgd` ____`#`.`<`U``Ukd$$Ifl\T $TFL t0644 lalyt` $Ifgd` `````````UPKKKKgd gdJ7Nkd{$$Ifl\T $TFL t0644 lalyt` $Ifgd````aa a aaaaa6a8a:aJaKagarasauaaaaaaaaaaaaaaaaaaaaĹᛊ}n}}nbjhCJUaJhA0J+CJaJmHnHuh dQh0J+CJaJ!jh dQh0J+CJUaJh dQhCJaJh.hCJaJhE,QCJaJh(hCJaJhCJ^JaJh,hCJaJhN CJaJhCJaJhh\kjh\kU hJ7NhJ7N&```aaaaaaaa a a a aaaaaaaaaaaaaaagd aaaaKaaabqbrbsbtbgdJ7N * !#gdv * !$gd,* !H$gdV* !H$gdVgd  aaaabb%b&bLbMbSbTbZb[b\b]babbblbmbobpbqbrbsbtbƵƵƵƵ hJ7NhJ7Nh\khhi0J+CJaJmHnHuh0J+CJaJmHnHu!jhvh0J+CJUaJhvh0J+CJaJhvhCJ^JaJhvhCJaJhCJaJjhCJUaJ90&P1h:pE=/ =!"#$% 6&P1h:p"t@/ =!"#$% DdJ0!H  C $A oasisbL @K@2rl(Dn  @K@2rlPNG  IHDRJzPLTE:o[+~Xք=X*bKGDH cmPPJCmp0712OmIDATho:9 QgRV\(3QA_=|II;ǟ'c7IFmFmž~OwOF6ؘƭOKc;Vh<魴W4{5xizۆ^:`fefd$[CoURk炳mfVfG>ȟVgʇ{d8uh%M 42>xQgjyF}X0Ag->E8i#B8iO}8iqj!(YIԱAѹq荢NvQe."pKx38VQǡoD.!_S7 _]B*qIcdi gE[{1 2t*@f82rC*IDATL['<Ox9†?HSxA< 6A^=2EIbK ̒nf1E"+LF85-;([~Ì=(8C?֋3(upv؊M4i09e8sRQu݁8^,=w>T<'7 ^Ccqz8x?8A @,'wwC g`E*+3.YD=Dk(V1Ιq MhߏP+8 upgG8M C#mGX--iwFw& УrC=!`P ۣ1;ꇌhVlj[QңqҰto1LC1 h\&yK4ۙ[ӗ#yP3.c5_>4ѯXfk2^]!KwU2h6dJ-IENDB`+DyK yK http://docs.oasis-open.org/odata/odata-json-format/v4.0/cs01/odata-json-format-v4.0-cs01.doc-DyK yK http://docs.oasis-open.org/odata/odata-json-format/v4.0/cs01/odata-json-format-v4.0-cs01.html+DyK yK http://docs.oasis-open.org/odata/odata-json-format/v4.0/cs01/odata-json-format-v4.0-cs01.pdfDyK yK http://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.docDyK yK http://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.htmlDyK yK http://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.pdfDyK yK rhttps://www.oasis-open.org/committees/odata/yX;H,]ą'cDyK yK <mailto:barbara.hartel@sap.comDyK yK (http://www.sap.com/DyK yK Fmailto:Ram.Jeyaraman@microsoft.comDyK yK 4http://www.microsoft.com/DyK yK 4mailto:ralf.handl@sap.comDyK yK (http://www.sap.com/DyK yK 6mailto:mikep@microsoft.comDyK yK 4http://www.microsoft.com/DyK yK Dmailto:mark.biamonte@progress.comDyK yK 2http://www.progress.com/DyK yK http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part1-protocol.htmlyX;H,]ą'c-DyK yK http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part2-url-conventions.htmlyX;H,]ą'cDyK yK zhttp://docs.oasis-open.org/odata/odata/v4.0/os/vocabularies/DyK yK http://docs.oasis-open.org/odata/odata-atom-format/v4.0/odata-atom-format-v4.0.htmlDyK yK https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=odatayX;H,]ą'cDyK yK rhttps://www.oasis-open.org/committees/odata/yX;H,]ą'cDyK yK https://www.oasis-open.org/committees/odata/ipr.phpyX;H,]ą'cDyK yK http://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.htmlDyK yK ~https://www.oasis-open.org/policies-guidelines/ipryX;H,]ą'cDyK yK Phttps://www.oasis-open.org/yX;H,]ą'cDyK yK https://www.oasis-open.org/policies-guidelines/trademarkyX;H,]ą'c}DyK _Toc372793034}DyK _Toc372793034}DyK _Toc372793035}DyK _Toc372793035}DyK _Toc372793036}DyK _Toc372793036}DyK _Toc372793037}DyK _Toc372793037}DyK _Toc372793038}DyK _Toc372793038}DyK _Toc372793039}DyK _Toc372793039}DyK _Toc372793040}DyK _Toc372793040}DyK _Toc372793041}DyK _Toc372793041}DyK _Toc372793042}DyK _Toc372793042}DyK _Toc372793043}DyK _Toc372793043}DyK _Toc372793044}DyK _Toc372793044}DyK _Toc372793045}DyK _Toc372793045}DyK _Toc372793046}DyK _Toc372793046}DyK _Toc372793047}DyK _Toc372793047}DyK _Toc372793048}DyK _Toc372793048}DyK _Toc372793049}DyK _Toc372793049}DyK _Toc372793050}DyK _Toc372793050}DyK _Toc372793051}DyK _Toc372793051}DyK _Toc372793052}DyK _Toc372793052}DyK _Toc372793053}DyK _Toc372793053}DyK _Toc372793054}DyK _Toc372793054}DyK _Toc372793055}DyK _Toc372793055}DyK _Toc372793056}DyK _Toc372793056}DyK _Toc372793057}DyK _Toc372793057}DyK _Toc372793058}DyK _Toc372793058}DyK _Toc372793059}DyK _Toc372793059}DyK _Toc372793060}DyK _Toc372793060}DyK _Toc372793061}DyK _Toc372793061}DyK _Toc372793062}DyK _Toc372793062}DyK _Toc372793063}DyK _Toc372793063}DyK _Toc372793064}DyK _Toc372793064}DyK _Toc372793065}DyK _Toc372793065}DyK _Toc372793066}DyK _Toc372793066}DyK _Toc372793067}DyK _Toc372793067}DyK _Toc372793068}DyK _Toc372793068}DyK _Toc372793069}DyK _Toc372793069}DyK _Toc372793070}DyK _Toc372793070}DyK _Toc372793071}DyK _Toc372793071}DyK _Toc372793072}DyK _Toc372793072}DyK _Toc372793073}DyK _Toc372793073}DyK _Toc372793074}DyK _Toc372793074}DyK _Toc372793075}DyK _Toc372793075}DyK _Toc372793076}DyK _Toc372793076}DyK _Toc372793077}DyK _Toc372793077}DyK _Toc372793078}DyK _Toc372793078}DyK _Toc372793079}DyK _Toc372793079}DyK _Toc372793080}DyK _Toc372793080}DyK _Toc372793081}DyK _Toc372793081}DyK _Toc372793082}DyK _Toc372793082}DyK _Toc372793083}DyK _Toc372793083}DyK _Toc372793084}DyK _Toc372793084}DyK _Toc372793085}DyK _Toc372793085}DyK _Toc372793086}DyK _Toc372793086}DyK _Toc372793087}DyK _Toc372793087}DyK _Toc372793088}DyK _Toc372793088}DyK _Toc372793089}DyK _Toc372793089}DyK _Toc372793090}DyK _Toc372793090}DyK _Toc372793091}DyK _Toc372793091}DyK _Toc372793092}DyK _Toc372793092}DyK _Toc372793093}DyK _Toc372793093}DyK _Toc372793094}DyK _Toc372793094}DyK _Toc372793095}DyK _Toc372793095}DyK _Toc372793096}DyK _Toc372793096mDyK odataqDyK rfc4627DyK _Primitive_ValueDyK CollectionOfPrimitive{DyK  ComplexValueDyK _Collection_of_ComplexqDyK _EntityDyK ResourceReferenceDyK CollectionOfEntitiesDyK _Entity_Reference}DyK DeltaResponseDyK _Representing_the_ServiceDyK _Representing_Errors_inqDyK rfc2119DyK yK bhttp://geojson.org/geojson-spec.htmlyX;H,]ą'cDyK yK Hhttp://www.ietf.org/rfc/rfc2119.txtDyK yK Hhttp://www.ietf.org/rfc/rfc3986.txtDyK yK Hhttp://www.ietf.org/rfc/rfc3987.txtDyK yK Fhttp://tools.ietf.org/html/rfc4627DyK yK Fhttp://tools.ietf.org/html/rfc5646DyK yK http://www.ecma-international.org/publications/standards/Ecma-262.htmqDyK rfc4627DyK  _Payload_Ordering_Constraints_1DyK _Controlling_the_AmountDyK  _Controlling_the_RepresentationDyK  _Payload_Ordering_Constraints_1DyK VocCapabilitiesDyK _Control_InformationDyK _odata=minimalmetadataDyK _odata.metadata=fullDyK _odata=nometadataDyK _Instance_AnnotationsDyK !_The_odata.metadata_Annotation_1uDyK  odataEtagwDyK  odataCountuDyK  odataNextwDyK  odataDeltaDyK _Annotation_odata.media*DyK _Annotation_odata.media*DyK !_The_odata.metadata_Annotation_1wDyK  odataCountuDyK  odataNextwDyK  odataDeltaDyK _The_odata.id_Annotation_1uDyK  odataEtagDyK _Annotation_odata.editLink_andDyK _Annotation_odata.editLink_andDyK %_Annotation_odata.navigationLink_andDyK %_Annotation_odata.navigationLink_anduDyK  odataTypeDyK _Annotation_odata.media*DyK _Annotation_odata.media*DyK _Annotation_odata.media*DyK _Annotation_odata.media*uDyK  odataNextwDyK  odataCountDyK _Delta_ResponseDyK _Annotation_odata.countwDyK  ECMAScriptDyK  yK `http://www.ecma-international.org/ecma-262/5.1/ sec-4.3.19DyK _Header_Content-TypeDyK _Controlling_the_AmountDyK  _Controlling_the_RepresentationDyK  _Payload_Ordering_Constraints_1qDyK EntitiyDyK ResourceReferenceDyK _Representing_a_ComplexDyK _Primitive_ValueDyK CollectionOfPrimitiveDyK _Collection_of_ComplexDyK CollectionOfEntities}DyK DeltaResponseDyK _Annotation_odata.metadataDyK _Annotation_odata.typeqDyK RFC3986DyK _Bind_OperationDyK _Instance_AnnotationssDyK  protocolDyK _Relative_URLsDyK _odata.metadata=nonesDyK  protocolDyK _Relative_URLsDyK _odata.metadata=nonemDyK ODataDyK _Annotation_odata.contextDyK _odata=minimalmetadataDyK _odata.metadata=fullDyK _Annotation_odata.typeDyK  _Controlling_the_RepresentationuDyK  odataCSDLDyK  _Representing_Multiple_EntitiesDyK _Entity_ReferencemDyK odataDyK _Expanded_Navigation_PropertysDyK  protocolyDyK  ODataURLRefyDyK  ODataURLRefDyK _odata.metadata=fullqDyK RFC3987qDyK RFC3986DyK _Relative_URLsDyK _odata=minimalmetadatasDyK  protocolsDyK  protocolDyK _The_odata.id_Annotation_1DyK _odata.metadata=fullDyK _odata.metadata=fullDyK _odata=minimalmetadataqDyK _EntitymDyK ODataDyK _Navigation_PropertyDyK _Annotation_odata.editLink_andDyK _odata=minimalmetadata}DyK _Media_EntityDyK _Stream_PropertyyDyK  ODataURLRefyDyK  ODataURLRefuDyK  odataCSDLDyK _Relative_URLsDyK _Structural_PropertymDyK odatamDyK odataDyK !_The_odata.metadata_Annotation_1DyK _Relative_URLsDyK _Primitive_ValueDyK _Complex_ValueDyK _Collection_of_PrimitiveDyK _Collection_of_ComplexqDyK rfc4627kDyK abnfqDyK GeoJSONDyK _Primitive_ValueDyK _Representing_a_ComplexDyK _Relative_URLsDyK _Relative_URLsqDyK _EntityDyK ResourceReferenceDyK !_The_odata.metadata_Annotation_1DyK _Annotation_odata.countDyK _Expanded_Navigation_PropertyDyK _Annotation_odata.idDyK _Relative_URLsDyK _Annotation_odata.media*DyK _Annotation_odata.media*sDyK  protocolDyK _Primitive_ValueDyK _Representing_a_ComplexDyK _Collection_of_ComplexDyK _Collection_of_PrimitiveDyK !_The_odata.metadata_Annotation_1DyK _Annotation_odata.countuDyK  odataNextwDyK  odataDeltaqDyK _EntityDyK ResourceReferenceDyK _Bound_Function}DyK _Bound_ActionDyK _Annotation_odata.nextLinksDyK  protocolDyK _The_odata.id_Annotation_1uDyK  odataTypeDyK _Collection_of_EntitiesDyK !_The_odata.metadata_Annotation_1DyK _Annotation_odata.countuDyK  odataNextwDyK  odataDeltasDyK  protocolDyK _Added/Changed_EntityDyK '_Representing_Added/Changed_Entities_1DyK _Deleted_EntityyDyK  _Added_Link}DyK _Deleted_LinkDyK _Annotation_odata.nextLinkDyK _Annotation_odata.deltaLinkDyK _Annotation_odata.countqDyK _EntityDyK _Annotation_odata.metadataDyK _Controlling_the_AmountDyK !_The_odata.metadata_Annotation_1DyK _The_odata.id_Annotation_1DyK _The_odata.id_Annotation_1DyK _Relative_URLsDyK !_The_odata.metadata_Annotation_1DyK _The_odata.id_Annotation_1DyK _Relative_URLsDyK _The_odata.id_Annotation_1DyK _Relative_URLsyDyK  _Added_LinkDyK !_The_odata.metadata_Annotation_1DyK _The_odata.id_Annotation_1DyK _Relative_URLsDyK _The_odata.id_Annotation_1DyK _Relative_URLskDyK abnfDyK _odata.metadata=fullDyK _Instance_AnnotationsDyK _Attribute_targetDyK _odata=minimalmetadataDyK _odata.metadata=fullDyK _Instance_AnnotationsDyK _odata=minimalmetadatauDyK  odataCSDLuDyK  odataCSDLuDyK  odataCSDLqDyK rfc5646DyK _Instance_AnnotationsDyK _Instance_AnnotationsDyK yK Fmailto:property@namespace.termnameqDyK rfc4627DyK _Delta_Response}DyK _Ref359603569}DyK _Ref356829825}DyK _Ref356829837}DyK _Ref356829873}DyK _Ref356829936}DyK _Ref356829963}DyK _Ref354567725sDyK  protocol}DyK _Ref356829677}DyK _Ref356829691uDyK  odataNext}DyK _Ref356921125uDyK  odataType}DyK _Ref356829731}DyK _Ref354567725}DyK _Ref356829691sDyK  protocol$$Ifl!vh#vT#vF#v#vL:V l t065T5F55Lalyt`$$Ifl!vh#vT#vF#v#vL:V l t065T5F55Lalyt`$$Ifl!vh#vT#vF#v#vL:V l t065T5F55Lalyt`$$Ifl!vh#vT#vF#v#vL:V l t065T5F55Lalyt`$$Ifl!vh#vT#vF#v#vL:V l t065T5F55Lalyt`$$Ifl!vh#vT#vF#v#vL:V l t065T5F55Lalyt`$$Ifl!vh#vT#vF#v#vL:V l t065T5F55Lalyt`^_ pppp08002 0P`p2( 0@P`0( 0@P`p 0@Pp 0@P`p 0@P`p 0@P`p8XV~_HmH nH sH tH L`L  Normal PPOJQJ_HaJmH sH tH x@x ]A Heading 1+$$ & Fx$d@&N5B* CJ$KH \^JaJ$ph;od@d  Heading 2,H2$$ & F$d@&NCJ\]aJJ@!J  Heading 3,H3  & F@& CJ\aJJ@1J  Heading 4,H4  & F@& CJ\aJB@AB  Heading 5  & F@& \]aJD@QD  Heading 6  & F@& CJ\aJ8@a8  Heading 7  & F@&>@q>  Heading 8  & F@&6]8 8  Heading 9 & F@&DA`D Default Paragraph FontVi@V  Table Normal :V 44 la (k (0No List `>@` ]ATitle$dN5B* CJ0KH\^JaJ0ph;o>J@> ]ASubtitleB* CJ$aJ$ph;oVO"V ]ATitle page info $5B* aJph;opOp E=Title page info description$P^m$ 5B*ph2O!22 U Contributor@!B@ Legal notice^0oQ0 DatatypeOJQJ6U`a6 0 Hyperlink >*B*ph.@. pTOC 1 <<6@6 pTOC 2<<^6@6 pTOC 3<<^~O~ CodeP$$d&d-DM NP]^ CJOJQJNO!N ]AAppendixHeading2  & F B* ph;oFV`F FollowedHyperlink >*B* ph2o2 Element CJOJQJ6o6 Attribute CJOJQJ&O& KeywordR^@R Normal (Web) dd[$\$OJPJQJ^J.X`. Emphasis6]Ng`!N HTML TypewriterCJOJPJQJ^JaJe@2 Q0HTML Preformatted?# 2( Px 4 #\'*.25@9OJPJQJ^JaJ4O4 Note Heading$<< Note%xx]^JOrJ Definition term &@ ]@ 5PJ@Ob@ Definition'x^PJFOF Ref(p((^p` B*\ph4@4 Header ) !4 @4 :Footer * !.)@. Page NumberdOd J7NAppendixHeading1, & Fdd[$\$B* KH$aJ$ph;o,o, Ref term5.(. Line Number66 TOC 7/x^^O^ Example50$d&d-DM NP6o6 CODE temp CJOJQJFO"F Code small2-DM CJ:O2: Example small3CJ:0B: List Bullet 4 & F2@2 pTOC 4 5^CJ,oa, Variable6.Q. TOC 5 7^2@2 TOC 6 8^CJXX   Heading 1 WP&9$ & F Q^`Q:o: *  Footer Char OJQJaJ@"@@ Caption ;xx6CJ\aJ>6> List Bullet 2 < & F<!< |ML Related Work = & F0O!0 iAbstract>m$<O< ]ANotices?$ B* aJ$ph;o:O: w Text Body @$^rr   Table Grid7:VA0 APPNO1N ]AAppendixHeading3 B & F B* ph;oX@2X D  Balloon Text CCJOJQJaJmHsHtHVoAV C Balloon Text CharCJOJQJaJmHsHtHn`Rn  Medium Shading 1 - Accent 2EOJQJ_HaJmH sH tH B'`aB Comment ReferenceCJaJ8@r8 H 0 Comment TextGaJBoB G 0Comment Text CharOJQJ@j@qr@ J Comment SubjectI5\NoN I Comment Subject Char5OJQJ\^^   Colorful Shading - Accent 3 K^m$^O^ N  Code BlockL-DM OJPJ QJ^JaJ`O` Grid Table 3 - Accent 21:VM0j@ j jF jF jF jF j j j j 44 Mfa$DCJOJPJ QJ^JaJ6]6]5\5\\o\ L Code Block Char%OJPJ QJ^JaJfHq ``` 0Dark List - Accent 3OOJQJ_HaJmH sH tH  / propToT # 0HTML Preformatted CharOJPJQJ^JBo!B apple-converted-space$o1$ stringOC Grid Table 1 Light1f:VT04j fffj fff 44T4nHtH5\5\5\5\DOSD  Grid Table 41:VU0ffffffffffffffffff4j@ j j jQ 44U=nHtH5\5\5\5B*\ph@c Medium Grid 3 - Accent 5:VV0j.@j.j.j 44(Vfdfd=nHtH5\5\5\5B*\phFB@rF X  Body Text WxCJOJPJQJHoH W Body Text CharCJOJPJQJaJBoB Z  Verbatim CharOJQJ^JaJROR Y  Source CodeZxx4$^ OJQJ^Jn`n ZMedium Shading 1 - Accent 1[OJQJ_HaJmH sH tH X@X Z Medium Grid 1 - Accent 2 \^m$h`hZ0Medium List 2 - Accent 2]OJQJ_HaJmH sH tH @ ZMedium List 1 - Accent 4:V^0j.@j.j.j 44(^fdfd=nHtH5\5\5\5B*\phPK![Content_Types].xmlN0EH-J@%ǎǢ|ș$زULTB l,3;rØJB+$G]7O٭V$ !)O^rC$y@/yH*񄴽)޵߻UDb`}"qۋJחX^)I`nEp)liV[]1M<OP6r=zgbIguSebORD۫qu gZo~ٺlAplxpT0+[}`jzAV2Fi@qv֬5\|ʜ̭NleXdsjcs7f W+Ն7`g ȘJj|h(KD- dXiJ؇(x$( :;˹! I_TS 1?E??ZBΪmU/?~xY'y5g&΋/ɋ>GMGeD3Vq%'#q$8K)fw9:ĵ x}rxwr:\TZaG*y8IjbRc|XŻǿI u3KGnD1NIBs RuK>V.EL+M2#'fi ~V vl{u8zH *:(W☕ ~JTe\O*tHGHY}KNP*ݾ˦TѼ9/#A7qZ$*c?qUnwN%Oi4 =3N)cbJ uV4(Tn 7_?m-ٛ{UBwznʜ"Z xJZp; {/<P;,)''KQk5qpN8KGbe Sd̛\17 pa>SR! 3K4'+rzQ TTIIvt]Kc⫲K#v5+|D~O@%\w_nN[L9KqgVhn R!y+Un;*&/HrT >>\ t=.Tġ S; Z~!P9giCڧ!# B,;X=ۻ,I2UWV9$lk=Aj;{AP79|s*Y;̠[MCۿhf]o{oY=1kyVV5E8Vk+֜\80X4D)!!?*|fv u"xA@T_q64)kڬuV7 t '%;i9s9x,ڎ-45xd8?ǘd/Y|t &LILJ`& -Gt/PK! ѐ'theme/theme/_rels/themeManager.xml.relsM 0wooӺ&݈Э5 6?$Q ,.aic21h:qm@RN;d`o7gK(M&$R(.1r'JЊT8V"AȻHu}|$b{P8g/]QAsم(#L[PK-![Content_Types].xmlPK-!֧6 0_rels/.relsPK-!kytheme/theme/themeManager.xmlPK-!0C)theme/theme/theme1.xmlPK-! ѐ' theme/theme/_rels/themeManager.xml.relsPK] .@tZ&&; $$'''zzzzzzz} |js()![112o3I44x5*66788}9::};<<T=,>>?O@@A?@BCEGHIJKLNOPRSUWYZ[]_`ackn%" 5!?*HP_mAyD[ \d'0629>KQX;\\\]^_``atb  #'(*-1379=ADFMQTVX\^bdefghijlma!3^7qs<Nx0?VZ}  1 Z m q  ! 2 c ~ > | / " w..--n]p'HOK't'z'(()B)Z)[){))))))))))))*8*T*V*W*Y*y******** + +++0+N+j+l+m+o+++++++,.,J,L,M,O,o,,,,,,,,--- -)-X-t-w-x-z--------.+.../.1.Q.c............/8/;//^/w///////////0@0\0_0`0b000000000111!1A1b1~11111111112#2?2B2C2E2e222222223333:3|33333333334 444P4S4T4V4v444444444444505L5O5P5R5r555555556 6 6 6-6O6k6n6o6q666666666777!7A7W7s7v7w7y777777778*8-8.808P8d888888888888 9(9+9,9.9N9f99999999999::6:9:::<:\:o:::::::::::;#;?;B;C;E;e;v;;;;;;;;;;; < <<<?<@<B<b<s<<<<<<<<<<< =&=B=E=F=H=h======== >>>>2>E>a>d>e>g>>>>>>>>>????9?I?e?h?i?k????????@$@'@(@*@@@@AAAAB2B7B_B~BBBBBB CC*C8C=CaCrCvCCCCCCCD)D-DYDjDDDDEEEeFFFWIII=JpJJK;K_KK L/LLLLZMMMNNNPP#PNWWWYYYY)Z;Z=ZoZZ[([7[[[ \+^T^k^^^____aaaa#b1bc.c9cccccc ddNdkd{dfAfQf{fffg hhkhhhhi iVisiiiiij1jnbnnnnno1o\osop4pCpIpfprpq0q>qqr(rs-s:sAssstttwwwGxyxx@yryyz"z)z/zSzdzkzzz{?{O{T{|{{{{{{|)|V|v||}}},U` 9I)+͌ 9ZcɎяStԐ'?A͒ޒєݔ>got7`kgΜٜ\tv 0PWgxM}.ARΤϤDX٥EWaUv/*;,6*>®Ų <E˳ 2Rag׶ ûۻݻпݿ.FH)2.>OJVc{~d"Kh/9)AD[sv-;a#;>\v} ,/b "%:[i+CF(@CRu6BZ]G_bZru!-0L[a~ 8^;EJjrF^a)<M@\g$'CRXu?WZO w }        & , 1 Q Y   &    a    3 6 xGqe?`i"Ucm Rs|".q  u     !}######I$q$}$%>%E%i&&&-'E'H' ($('(@)X)[)+++3,[,g,D-m--. .#....///r222555555:::;=O=\=Q@c@m@}CCCCCC_EEEEE FIIIJJJKKKKLL>LYL_LLMMMMMNNNNO OOOOOPPnPPPQQQ^QyQQQQQbR}RRRRR0S[SaSSSStZXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%̕XXXXXXXXXXXXXXXXXX XXtXtXTXXXXXXXtXX4XXXXXX4XXXXXTXXXTXXXXXXXXXXXXXXXXXXXXXXXX  XXXXX XXXXX  XXXXXXXXXXXXXXXXXX X XXX  XXXX  X X X X XXXX X XX X X XXXX     XXXXXXXXX XXXXXXX  XXXXXXXX XXXX4XXXXXXXXXXXXXXXXXX   XXX     X XXX![bditw}!33!@ @H 0(  0(  B S  ?. _Hlt255486618 _Toc368563066 _Toc370365570 _Toc372793034 _Toc368563067 _Toc370365571 _Toc372793035 _Ref7502892 _Toc368563068 _Toc370365572 _Toc372793036GeoJSONabnf odataCSDLprotocolodata ODataURLRefVocCapabilitiesrfc2119RFC3986RFC3987rfc4627rfc5646 ECMAScript _Toc368563069 _Toc370365573 _Toc372793037 _Toc368563070 _Toc370365574 _Toc372793038_Requesting_the_JSON _Ref356829677 _Ref356829731 _Toc368563071 _Toc370365575 _Toc372793039_Controlling_the_Amount _Toc368563072 _Toc370365576 _Toc372793040_odata=minimalmetadata_odata.metadata=minimal _Ref359603569 _Toc368563073 _Toc370365577 _Toc372793041_odata.metadata=full _Ref356829691 _Ref356829810 _Ref356829837 _Toc368563074 _Toc370365578 _Toc372793042_odata=nometadata_odata=nometadata_1_odata.metadata=none _Ref356829825 _Toc368563075 _Toc370365579 _Toc372793043_Controlling_the_Representation _Toc368563076 _Toc370365580 _Toc372793044 _Toc368563077 _Toc370365581 _Toc372793045_Header_Content-Type _Toc368563078 _Toc370365582 _Toc372793046 _Toc368563079 _Toc370365583 _Toc372793047_Relative_URLs_1 RelativeURLs_Relative_URLs _Toc368563080 _Toc370365584 _Toc372793048_Payload_Ordering_Constraints_1 _Ref354567725 _Toc368563081 _Toc370365585 _Toc372793049_Control_Information _Ref356829936 _Toc368563082 _Toc370365586 _Toc372793050 _The_odata.metadata_Annotation_1_Annotation_odata.metadata_Annotation_odata.context _Ref356921125 _Toc368563083 _Toc370365587 _Toc372793051 _Toc368563084 _Toc370365588 _Toc372793052_Annotation_odata.type odataType _Toc368563085 _Toc370365589 _Toc372793053_Annotation_odata.count odataCount _Toc368563086 _Toc370365590 _Toc372793054_Annotation_odata.nextLink odataNext _Toc368563087 _Toc370365591 _Toc372793055_The_odata.deltaLink_Annotation_Annotation_odata.deltaLink odataDelta _Toc368563088 _Toc370365592 _Toc372793056_The_odata.id_Annotation_1_Annotation_odata.id _Toc368563089 _Toc370365593 _Toc372793057_Annotation_odata.editLink_and _Toc368563090 _Toc370365594 _Toc372793058 odataEditLink odataEtag _Toc368563091 _Toc370365595 _Toc372793059$_Annotation_odata.navigationLink_and _Toc368563092 _Toc370365596 _Toc372793060odataNavigationLinkodataAssocLink_Annotation_odata.media* _Toc368563093 _Toc370365597 _Toc372793061_Representing_the_Service _Toc368563094 _Toc370365598 _Toc372793062_EntityEntitiy _Toc368563095 _Toc370365599 _Toc372793063 _Properties_Structural_Property _Toc368563096 _Toc370365600 _Toc372793064_Primitive_Value _Ref356829873 _Toc368563097 _Toc370365601 _Toc372793065_Representing_a_Complex_Complex_Value _Ref332032621 _Ref332033656 ComplexValue _Toc368563098 _Toc370365602 _Toc372793066_Representing_an_Individual_Collection_of_PrimitiveCollectionOfPrimitive_Representing_a_Collection _Toc368563099 _Toc370365603 _Toc372793067_Collection_of_Complex _Toc368563100 _Toc370365604 _Toc372793068_Navigation_Property _Toc368563101 _Toc370365605 _Toc372793069_Representing_a_Deferred _Toc368563102 _Toc370365606 _Toc372793070 _Toc368563103 _Toc370365607 _Toc372793071_Expanded_Navigation_Property _Toc368563104 _Toc370365608 _Toc372793072 _Toc368563105 _Toc370365609 _Toc372793073_Bind_Operation _Toc368563106 _Toc370365610 _Toc372793074_Stream_Property _Toc368563107 _Toc370365611 _Toc372793075 _Media_Entity _Toc368563108 _Toc370365612 _Toc372793076 _Toc368563109 _Toc370365613 _Toc372793077_Representing_Multiple_Entities_Collection_of_EntitiesCollectionOfEntities _Toc368563110 _Toc370365614 _Toc372793078CollectionOfLinksCollectionOfEntityRef _Representing_Changes_(Deltas)_1_Entity_ReferenceResourceReference _Toc368563111 _Toc370365615 _Toc372793079_Entity_References_as_Delta_Response DeltaResponse _Toc368563112 _Toc370365616 _Toc372793080&_Representing_Added/Changed_Entities_1_Added/Changed_Entity _Toc368563113 _Toc370365617 _Toc372793081 _Representing_Deleted_Entities_1_Deleted_Entity _Toc368563114 _Toc370365618 _Toc372793082 _Added_Link _Toc368563115 _Toc370365619 _Toc372793083_Representing_Deleted_Links_1 _Deleted_Link _Toc368563116 _Toc370365620 _Toc372793084_Bound_Function _Ref332031391 _Ref332033268 _Ref332033292 _Toc368563117 _Toc370365621 _Toc372793085 _Bound_Action _Toc368563118 _Toc370365622 _Toc372793086 _Toc368563119 _Toc370365623 _Toc372793087_Instance_Annotations _Toc368563120 _Toc370365624 _Toc372793088_Representing_Annotations _Toc368563121 _Toc370365625 _Toc372793089 _Toc368563122 _Toc370365626 _Toc372793090_Representing_Errors_in _Toc368563123 _Toc370365627 _Toc372793091_The_Content-Type_Header_Payload_Ordering_Constraints _Ref356829963 _Toc368563124 _Toc370365628 _Toc372793092 _Toc368563125 _Toc370365629 _Toc372793093 _Toc368563126 _Toc370365630 _Toc372793094 _Toc368563127 _Toc370365631 _Toc372793095 _Toc368563128 _Toc370365632 _Toc372793096.@.@.@DDDEEEEEF-GGGHHHIJcK3LMMMMOOOWWWWWW[[[[-`-`-`-`-`-`fffffffoooooooAqAqAqAqtttjvjvjvjvyyy|||||| ȑȑȑrrrrr!!!!!ԩGGGGh[kkkkkrrrr))))\\\\BBBB******>&&&&~~~~~!!!!!!!U*U*U*U*0003333/3888:::====9E9E9E9E9E9EGGGIIIdSdSdSTTTuZ@  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJLKMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-:@:@:@DDDEEEEEF9GGG&HHHIJlK----222&000~~!!!!!!!U*a*a*a*0003.3.3.3:3888 ; ; ;====9E9EFEFEFEFEGGGIIIsSsSsSTTTuZa"##3 * / ( 0 : ; < @ | 1 $,g/0y-"'PUY^_dow^3.)))))8*W****+N+m+++.,M,,,,-X-x---./.c..../E>e>>>>?I?i???@(@@AAAEEEEFFFF-F4FeFFHHHHIIJJJJmKvKKKM M MMCNMNNNP$P3X7XXX!Y%YYYpZZZ[[8[d\r\(]7]O]]]U^c^^ ___-`;`I`W`` a$b1b/c9c@cDccc ddld{ddd^eceBfQfXf\ffffffggg hhhhi itii2jnnnnooo]osooooo5pCpgprppppqqqr(rs;sUt`tvvwwxxx yy}}V` *Eȅ,XklZg afJO jw я 'BJWӑEIߒDNr|#>Hak:HϜٜlv)@\w؞)}Wy,:?MƢբ8Gˣ٣.SϤES٥Eb'ϩԩ<CQͫ֫Zh!n|ۭ+9aoïѯR\akްuẕѱh}յ!,<OTg~¸ո%;/>lpû޻-@^t<IH` gjkz.IQ^/28Bbm?B.P R]ahitx @Jc >Lu*/P`p{3[v"goqz5?KVXacvx: &0;S^iu$2FO)EMZ[wJg"{/C/=#?HUo:V 09F & '+G Jg )(DMZB^w*Gcy ;Zv"-M[Fbkx)N]g$DRv?[   7 r }    6CR]gy(=GVt )iv rVc d#y#}####&&-'I''''' (((Y(f((( ))@)\)))))(*9*++n-|-.$.N.[.....//K/Y///// 00J0X0r22w4|45555555646P6v666677777(727R7::;=]=>>Q@n@BBBBCCDDEEFFIIKKKKKKKL!L/L>L`LLMeMjMMM-N2NNNNNN OOOOOOPQP_PnPPPPQQ^QQQQbRRRRRRS&S0SbSSS`TeTTTUU'U,U$V)V2V7VUVcViVwVVVWWWW(X-X6X;XXXYY Y YYYYYYYYYSZ]ZaZpZrZuZ "@Ax3OAADDFFHHmKK=LL8M:MGMYMD`W`eeww~~IS5;Զ׶DNgj/2Y]w| #'?BeiPZP_bz}7AzZd#, LWhm!27?I&-1    gm (4GMkq(((((())* *C*H*c/h///b0g0000022^6c666U7X7CC D DD#DHDND_DfD{DDDDDDDDE EE$EFFXYY Y YYYYYY8YrZuZ333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333## : ; < ? @ 0 1 #$,g/0yY^3.)XXYYYYuZ).pi ZlfYaqNq BVJux= ^`OJQJo( 8^8`OJQJo(^`OJQJ^Jo(o  p^ `OJ QJ o(  @ ^ `OJ QJ o( x^x`OJQJo(H^H`OJQJ^Jo(o ^`OJ QJ o( ^`OJ QJ o(^`QJo(  hh^h`OJQJo( ^`OJQJo(^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o(8^8`.^`. L^ `L. ^ `.x^x`.HL^H`L.^`.^`.L^`L. ^`OJQJo(^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o(h^h`.P^`P.^`...x^`x.... ^` .....  X^ `X ......  ^ `....... 8^`8........ `^``......... ^`OJQJo(^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o(8^8`.^`. L^ `L. ^ `.x^x`.HL^H`L.^`.^`.L^`L. ^`OJQJo(^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o(h^h`)^`.8^8`)^`()^`()p^p`() ^ `.@ ^@ `. ^ `. ^`OJQJo(^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o(^`.^`.pL^p`L.@ ^@ `.^`.L^`L.^`.^`.PL^P`L. h^h`OJQJo(8^8`OJQJ^Jo(o ^`OJ QJ o(  ^ `OJQJo( ^ `OJQJ^Jo(o x^x`OJ QJ o( H^H`OJQJo(^`OJQJ^Jo(o ^`OJ QJ o(^`OJPJQJ^Jo(^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o(^`CJ.^`.pL^p`L.@ ^@ `.^`.L^`L.^`.^`.PL^P`L. ^`OJQJo(p^p`OJQJ^Jo(o @ ^@ `OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(P^P`OJQJ^Jo(o  ^ `OJ QJ o(8^8`.^`. L^ `L. ^ `.x^x`.HL^H`L.^`.^`.L^`L. ^`OJQJo(^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o(8^8`.^`. L^ `L. ^ `.x^x`.HL^H`L.^`.^`.L^`L.^`o(.^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o(h^h`OJQJ^Jo(.P^`P..^`...x^`x.... ^` .....  X^ `X ......  ^ `....... 8^`8........ `^``.........h8^8`OJQJo(hHh^`OJQJo(hHoh ^ `OJ QJ o(hHh ^ `OJQJo(hHhx^x`OJQJo(hHohH^H`OJ QJ o(hHh^`OJQJo(hHh^`OJQJo(hHoh^`OJ QJ o(hHP^`Po(@^@`o(.0^`0o(..`^``o(... ^`o( .... ^`o( ..... ^`o( ...... `^``o(....... 00^0`o(........ h h^h`o(hH Appendix . @^@`o(hH. 0^`0o(hH.. `^``o(hH...  ^`o(hH .... ^`o(hH ..... ^`o(hH ......  `^``o(hH.......  00^0`o(hH........h8^8`OJQJo(hHh^`OJQJo(hHh ^ `OJ QJ o(hHh ^ `OJQJo(hHhx^x`OJQJo(hHohH^H`OJ QJ o(hHh^`OJQJo(hHh^`OJQJo(hHoh^`OJ QJ o(hHP^`Po(@@^@`o(.0^`0o(..``^``o(... ^`o( .... ^`o( ..... ^`o( ...... `^``o(....... 00^0`o(........h^h`)^`)8^8`)^`()^`()p^p`() ^ `.@ ^@ `. ^ `. ^`OJQJo(^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o p^p`OJ QJ o( @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o P^P`OJ QJ o(h^h`.P^`P..^`...x^`x.... ^` .....  X^ `X ......  ^ `....... 8^`8........ `^``.........h88^8`OJQJo(hHh^`OJQJ^Jo(hHoh  ^ `OJ QJ o(hHh  ^ `OJQJo(hHhxx^x`OJQJ^Jo(hHohHH^H`OJ QJ o(hHh^`OJQJo(hHh^`OJQJ^Jo(hHoh^`OJ QJ o(hH*fW_W_BVJuq d/WA.=e_wGvV6+.bC2W7?fYaqnB\7y%k-Qr! U2/)%C\qwW//o<7qiKM8!h Ic1R/^GZl;1n-KJ))                                                                                                                                                         ~6l                 L>                 2                                            Z$%                           t,        V _Q0Vdo|TU]MVdCU]MVd&WtY9 _Q0VdU]Mw`QU]MVdc~9#h)_Q0X;_Q0Vd-U}<U?= n?C':\DU]MVdfD_Q0Vdm NH_Q0Vd I_Q0Vd;SU]MVd ']U]MVdz|^[4{_Wa_Q0VdU Ms_Q0VdONsU]MVd1itU]MVdnt 2zv~XW_:k(5CL$A0e%9I @n,N -n  n X{  (Wm/?c}2S+xl4FK[Q$<"s"#W%Y&'<0'r'n(h)+{+~&+~+h,a/* 010)1x1?2 14`!6 l67A?7uy8G :7;[;< <a<=E=1g>ps>:.@"t@K*A&B/'B?Cf C/FI%INIAJ> K*K|ML^MJ7N 9O[O&QE,QdIQ dQ R~RcS!T}T;~T?MUV~V+WY1YsY;)ZA^ZJ\.]C]r]\<`G`arHapSc\gRhijC4jI,k1moq#opcFpJpWp|!q2q9qeqgqr{ls@YE$RRS^D(%8}_6NqVU@<`^s:Z /Ov PeE0F\^?(qZ*`]Ais8 f R8il-KX5&DQ.]QI2lly6Yd&d&()1^rd,Y5Sb J:lfB|g<z 1DJ6n%\k!DRauT\k'<|.X ]o)^gb60U9o)SV>QOg4P__Annotation_odata.nextLink ;_Deleted_Linkhc8 _Added_Linkb}5_Deleted_Entitydy2'_Representing_Added/Changed_Entities_1J/_Added/Changed_Entity~y# odataDelta   odataNextA_Annotation_odata.countm~!_The_odata.metadata_Annotation_1fH_Collection_of_Entities odataType _The_odata.id_Annotation_1C_Annotation_odata.nextLink _Bound_Action~`_Bound_FunctionResourceReferenceXe_Entity~y odataDelta  odataNextA_Annotation_odata.countm~!_The_odata.metadata_Annotation_14_Collection_of_PrimitiverR_Collection_of_ComplexXb_Representing_a_Complex _Primitive_Value?'_Annotation_odata.media*?'_Annotation_odata.media*NB_Relative_URLs>e_Annotation_odata.id !_Expanded_Navigation_PropertyA_Annotation_odata.countm~!_The_odata.metadata_Annotation_1ResourceReferenceXe_EntityNB_Relative_URLsNB_Relative_URLsXb_Representing_a_Complex _Primitive_ValuerR~_Collection_of_Complex4{_Collection_of_Primitivenex_Complex_Value u_Primitive_ValueNBl_Relative_URLsm~i!_The_odata.metadata_Annotation_1: `_Structural_PropertyNBZ_Relative_URLsolN ODataURLRef-6K_Stream_Property H_Media_EntityiE_odata=minimalmetadatahB_Annotation_odata.editLink_and?2?_Navigation_PropertyXe9_Entityi6_odata=minimalmetadataoB3_odata.metadata=fulloB0_odata.metadata=full -_The_odata.id_Annotation_1i$_odata=minimalmetadataNB!_Relative_URLsoB_odata.metadata=fullol ODataURLRef ! _Expanded_Navigation_Property)<_Entity_ReferencenS _Representing_Multiple_EntitiesCa _Controlling_the_RepresentationS_Annotation_odata.typeoB_odata.metadata=fulli_odata=minimalmetadata?b_Annotation_odata.contexteQ_odata.metadata=noneNB_Relative_URLseQ_odata.metadata=noneNB_Relative_URLs. _Instance_AnnotationsPJ_Bind_OperationS_Annotation_odata.type^_Annotation_odata.metadata DeltaResponseCollectionOfEntitiesrR_Collection_of_ComplexCollectionOfPrimitive _Primitive_ValueXb_Representing_a_ComplexResourceReferenceenEntitiypf _Payload_Ordering_Constraints_1Ca _Controlling_the_RepresentationYl_Controlling_the_Amount4w_Header_Content-Type 0http://www.ecma-international.org/ecma-262/5.1/ sec-4.3.19A_Annotation_odata.countjt_Delta_Responsenr odataCount  odataNext?'_Annotation_odata.media*?'_Annotation_odata.media*?'_Annotation_odata.media*?'|_Annotation_odata.media*y odataTypehv%_Annotation_odata.navigationLink_andhs%_Annotation_odata.navigationLink_andhp_Annotation_odata.editLink_andhm_Annotation_odata.editLink_andj odataEtag g_The_odata.id_Annotation_1~yd odataDelta a odataNextnr^ odataCountm~[!_The_odata.metadata_Annotation_1?'X_Annotation_odata.media*?'U_Annotation_odata.media*~yR odataDelta O odataNextnrL odataCountI odataEtagm~F!_The_odata.metadata_Annotation_1. C_Instance_Annotationsx@_odata=nometadataoB=_odata.metadata=fulli:_odata=minimalmetadata7_Control_Informationpf1 _Payload_Ordering_Constraints_1Ca. _Controlling_the_RepresentationYl+_Controlling_the_Amountpf( _Payload_Ordering_Constraints_1WNFhttp://www.ecma-international.org/publications/standards/Ecma-262.htmb$#http://tools.ietf.org/html/rfc5646e%#http://tools.ietf.org/html/rfc4627!7$http://www.ietf.org/rfc/rfc3987.txt 7$http://www.ietf.org/rfc/rfc3986.txt'?$http://www.ietf.org/rfc/rfc2119.txtA %http://geojson.org/geojson-spec.htmla@_Representing_Errors_in"_Representing_the_Service DeltaResponse)<_Entity_ReferenceCollectionOfEntitiesResourceReferenceXe_EntityrR_Collection_of_Complex ComplexValueCollectionOfPrimitive _Primitive_Value8_Toc3727930968_Toc3727930958_Toc3727930948_Toc3727930938_Toc3727930928_Toc3727930918_Toc3727930908_Toc3727930898_Toc3727930888_Toc3727930878_Toc3727930868_Toc3727930858_Toc3727930848_Toc3727930838_Toc3727930828_Toc3727930818|_Toc3727930808v_Toc3727930798p_Toc3727930788j_Toc3727930778d_Toc3727930768^_Toc3727930758X_Toc3727930748R_Toc3727930738L_Toc3727930728F_Toc3727930718@_Toc3727930708:_Toc37279306984_Toc3727930688._Toc3727930678(_Toc3727930668"_Toc3727930658_Toc3727930648_Toc3727930638_Toc3727930628 _Toc3727930618_Toc3727930608_Toc3727930598_Toc3727930588_Toc3727930578_Toc3727930568_Toc3727930558_Toc3727930548_Toc3727930538_Toc3727930528_Toc3727930518_Toc3727930508_Toc3727930498_Toc3727930488_Toc3727930478_Toc3727930468_Toc3727930458_Toc3727930448_Toc3727930438_Toc3727930428_Toc3727930418_Toc3727930408_Toc3727930398_Toc3727930388z_Toc3727930378t_Toc3727930368n_Toc3727930358h_Toc372793034 Vc9https://www.oasis-open.org/policies-guidelines/trademarky{`https://www.oasis-open.org/r7]3https://www.oasis-open.org/policies-guidelines/iprqaZThttp://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.htmlKYWZhttp://docs.oasis-open.org/odata/odata-json-format/v4.0/os/odata-json-format-v4.0-os.html2+T4https://www.oasis-open.org/committees/odata/ipr.phpYQ-https://www.oasis-open.org/committees/odata/XiNIhttps://www.oasis-open.org/committees/comments/index.php?wg_abbrev=odata~nKThttp://docs.oasis-open.org/odata/odata-atom-format/v4.0/odata-atom-format-v4.0.htmlGH=http://docs.oasis-open.org/odata/odata/v4.0/os/vocabularies/CE5http://docs.oasis-open.org/odata/odata/v4.0/os/abnf/?BGhttp://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part3-csdl.htmlPS?Rhttp://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part2-url-conventions.html)e<Khttp://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part1-protocol.html][9http://www.progress.com/x6"mailto:mark.biamonte@progress.com_3http://www.microsoft.com/I`0mailto:mikep@microsoft.comp&-http://www.sap.com/G7*mailto:ralf.handl@sap.com_'http://www.microsoft.com/k$#mailto:Ram.Jeyaraman@microsoft.comp&!http://www.sap.com/ mmailto:barbara.hartel@sap.comY-https://www.oasis-open.org/committees/odata/arShttp://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.pdfqaThttp://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.htmljcShttp://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.doc[J]http://docs.oasis-open.org/odata/odata-json-format/v4.0/cs01/odata-json-format-v4.0-cs01.pdfKY ^http://docs.oasis-open.org/odata/odata-json-format/v4.0/cs01/odata-json-format-v4.0-cs01.htmlP[ ]http://docs.oasis-open.org/odata/odata-json-format/v4.0/cs01/odata-json-format-v4.0-cs01.doc[JYhttp://docs.oasis-open.org/odata/odata-json-format/v4.0/os/odata-json-format-v4.0-os.pdfKYZhttp://docs.oasis-open.org/odata/odata-json-format/v4.0/os/odata-json-format-v4.0-os.htmlP[Yhttp://docs.oasis-open.org/odata/odata-json-format/v4.0/os/odata-json-format-v4.0-os.doc OASIS TC4Work Product abbreviation without version or stage TC Chair Editor #1 Editor #2 namespace  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnoqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnpqrstuvxyz{|}~Root Entry F7Data p1Tablep!WordDocumentsSummaryInformation(oDocumentSummaryInformation8w