From nobody Fri Aug 23 14:55:34 2019 Return-Path: X-Original-To: ietf-message-headers@ietfa.amsl.com Delivered-To: ietf-message-headers@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6049F120124 for ; Fri, 23 Aug 2019 14:55:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oasis-open-org.20150623.gappssmtp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UdYgXuqMVkwo for ; Fri, 23 Aug 2019 14:55:29 -0700 (PDT) Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 614B612011E for ; Fri, 23 Aug 2019 14:55:29 -0700 (PDT) Received: by mail-ed1-x52b.google.com with SMTP id s49so15598423edb.1 for ; Fri, 23 Aug 2019 14:55:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oasis-open-org.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=fEPxKl6g5j+J5+NJda/v+U+Rc0ZMEW42i4bVkU74hok=; b=iowzleiJ0ZE0ItqDYwMHpJXB8uirPS0yj+KHqb39KpsYDjw+5P4o4MbX9EeWmXVHe8 P/gq2GaFmks1QR1KV+5Q+vh0W4PSRPIhf3XGXhTSliUHXNbsJEYdqQSwy0lqhR6KGqYk tYM06OaUV44rDmKWOW+2jsrTjJWZnawqamzaubthDuP7XumJ46Ol0q4FX6mHLVPc+Hyz dD1OF7aLNLaT9nlKPOhbaqx8tIJKnxt1xKz2jezv+pW1lgyySAF0truIcYjNNunpGpy5 i4jhMHVKl6ByVB5WS/gmPjmLmFeYe0czNbdQHZhP5uoF1DW3wE/fR1zmXGDhCVaty9lo 41aw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=fEPxKl6g5j+J5+NJda/v+U+Rc0ZMEW42i4bVkU74hok=; b=cbkRAr0G87QcuqXrFfqVJd6HIgxBt3BMrZhTyDiVlpxIBjUlCNvzXecStBXVh76Xb4 TNmncZNHUdO7n243nDTrsOLGJnrHN5g7j/gOKiAtHT7oQf4PLc/LWdh0s5R0xqn8Sbg+ xGQU2PV/w1wEcYP9AhIXvA/EJ0I/PM71qHR+yP3Sk+C4ymvQ5IXovhxEhD9pmHq1LNzK een58myMtPCjSaOuTcomaS8CsH/T7B6d1W34vp3kMzL0Cyecc9hE4sVZL9wOH8mcuLwx E13MA6sE1UXoB1Tt+XhUBSd5Hm4twVTq1B1TrQHAHquU/Ncq5VLX1/jIEIEg4Lv2WnqR Bjyg== X-Gm-Message-State: APjAAAWFyuYoK1ze1/T5G+JepkxTrrpfrdOEnZGahZhebhMk+gL+Nbw9 IggEQdrQeCk6HswObGKrNH/4iePah8LZ9jWY/1B+ZH+l3g== X-Google-Smtp-Source: APXvYqyBGUAWvLs/ZU3S0ol1dkaokEbm0pON1k5VL4UR2GsnyPImxDQozDtsN6+7+nRU39BxbA5GFEo0ZJigHK9t62w= X-Received: by 2002:a17:907:208f:: with SMTP id pv15mr6349333ejb.103.1566597327583; Fri, 23 Aug 2019 14:55:27 -0700 (PDT) MIME-Version: 1.0 From: Chet Ensign Date: Fri, 23 Aug 2019 17:55:15 -0400 Message-ID: To: ietf-message-headers@ietf.org Cc: "Mark Biamonte (Progress)" , "Ralf Handl (SAP)" Content-Type: multipart/alternative; boundary="000000000000378d910590cfdd09" Archived-At: Subject: [Ietf-message-headers] Updates to registration request for OData-EntityId, OData-Isolation, OData-MaxVersion, and OData-Version X-BeenThere: ietf-message-headers@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion list for header fields used in Internet messaging applications." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2019 21:55:34 -0000 --000000000000378d910590cfdd09 Content-Type: text/plain; charset="UTF-8" This message contains an update to the registration request submitted on 06 December 2018 in https://mailarchive.ietf.org/arch/msg/ietf-message-headers/oRU8ChCoUXV-DU5Vh6PAxKF9NZs In response to the feedback received, the OData Technical Committee updated the registration documents to include the OData prefix in the Header and Preference names as suggested. Below, please find the revised request. I have included the prior values in [ ]s so that all the changes are visible. --- Open Data (OData) Protocol IANA Header registration request 22-Jul-2019 ------------------------------------------------------------ This documentation contains the information needed for Permanent Registration of the OData specific request headers with IANA as called out in RFC 3864 - Registration Procedures for Message Header Fields. The OData headers to be registered as Permanent Headers are OData-EntityId [OData-]Isolation [was Isolation] OData-MaxVersion OData-Version The details as required by RFC 3864 for these headers are listed below. #### Header field name: OData-EntityId Applicable protocol: HTTP Status: Standard Author/Change controller: OASIS Specification document(s): OData Version 4.01 Part 1: Protocol - http://docs.oasis-open.org/odata/odata/v4.01/csprd05/part1-protocol/odata-v4.01-csprd05-part1-protocol.html#_Toc14172735 Related information: #### Header field name: [OData-]Isolation [was Isolation] Applicable protocol: HTTP Status: Standard Author/Change controller: OASIS Specification document(s): OData Version 4.01 Part 1: Protocol - http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_HeaderIsolationODataIsolation Related information: [was "The Isolation header was named OData-Isolation in OData version 4.0. The OData Protocol document referenced above defines one valid value, snapshot. To make this header useful to applications other than OData this registration also defines the values read-uncommitted, read-committed, repeatable-read and serializable. These correspond to the standard transaction isolation levels exposed by most database systems.] #### Header field name: OData-MaxVersion Applicable protocol: HTTP Status: Standard Author/Change controller: OASIS Specification document(s): OData Version 4.01 Part 1: Protocol - http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_HeaderODataMaxVersion Related information: #### Header field name: OData-Version Applicable protocol: HTTP Status: Standard Author/Change controller: OASIS Specification document(s): OData Version 4.01 Part 1: Protocol - http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_HeaderODataVersion Related information: -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393 --000000000000378d910590cfdd09 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
This message contains an update to the registration reques= t submitted on 06 December 2018 in https://mailarch= ive.ietf.org/arch/msg/ietf-message-headers/oRU8ChCoUXV-DU5Vh6PAxKF9NZs<= br>
In response to the feedback received, the OData Technical Committee = updated the registration documents to include the OData prefix in the Heade= r and Preference names as suggested. =C2=A0

Below, please find the r= evised request. I have included the prior values in [ ]s so that all the ch= anges are visible.

---

Open Data (OData) Protocol IANA Heade= r registration request
22-Jul-2019
----------------------------------= --------------------------

This documentation contains the informati= on needed for Permanent Registration of the OData specific request headers = with IANA as called out in RFC 3864 - Registration Procedures for Message H= eader Fields.

The OData headers to be registered as Permanent Header= s are

OData-EntityId
[OData-]Isolation =C2=A0[was Isolation]
O= Data-MaxVersion
OData-Version

The details as required by RFC 3864= for these headers are listed below.

####
Header field name:
= OData-EntityId

Applicable protocol:
HTTP

Status:
Stan= dard

Author/Change controller:
OASIS

Specification docume= nt(s):
OData Version 4.01 Part 1: Protocol -
http://docs.oasis-open.org/odata/odata/v= 4.01/csprd05/part1-protocol/odata-v4.01-csprd05-part1-protocol.html#_Toc141= 72735 =C2=A0

Related information:
<None>

####<= br>Header field name:
[OData-]Isolation =C2=A0[was Isolation]

Ap= plicable protocol:
HTTP

Status:
Standard

Author/Chang= e controller:
OASIS

Specification document(s):
OData Version = 4.01 Part 1: Protocol -
http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.= html#sec_HeaderIsolationODataIsolation

Related information:
&= lt;none> =C2=A0
[was "The Isolation header was named OData-Isola= tion in OData version 4.0.=C2=A0 The OData Protocol document referenced abo= ve defines one valid value, snapshot.=C2=A0 To make this header useful to a= pplications other than OData this registration also defines the values read= -uncommitted, read-committed, repeatable-read and serializable.=C2=A0 These= correspond to the standard transaction isolation levels exposed by most da= tabase systems.]

####
Header field name:
OData-MaxVersion
Applicable protocol:
HTTP

Status:
Standard

Autho= r/Change controller:
OASIS

Specification document(s):
OData V= ersion 4.01 Part 1: Protocol -
http://d= ocs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_He= aderODataVersion =C2=A0

Related information:
<none><= br>--
<= div>

/chet= =C2=A0
----------------
Chet Ensign
Chief Technical Community Stew= ard
OASIS: Advancing open standards for the information societyhttp://www.oasis-= open.org

Mobile: +1 201-341-1393=C2=A0
<= /div>
--000000000000378d910590cfdd09-- From nobody Fri Aug 23 15:01:13 2019 Return-Path: X-Original-To: ietf-message-headers@ietfa.amsl.com Delivered-To: ietf-message-headers@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD864120128 for ; Fri, 23 Aug 2019 15:01:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oasis-open-org.20150623.gappssmtp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VrBqzjN4xnH6 for ; Fri, 23 Aug 2019 15:01:04 -0700 (PDT) Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DB8212011E for ; Fri, 23 Aug 2019 15:01:04 -0700 (PDT) Received: by mail-ed1-x534.google.com with SMTP id g8so15578778edm.6 for ; Fri, 23 Aug 2019 15:01:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oasis-open-org.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=t3TF6685c2WJdfJNI/FI0hp1VdsTJRBj/93i0/tT4D8=; b=yFbO0dS1r1w5vzWzGmMN/8DBam0yyP85rfkZKcdgCNy5Jt0/BZfmGyaX3KmUhcWkj0 px8soaozTBtCGUGpwqMg0GUF0hIJmnysTSkl0c8dokagGs75rgyoX5eczhsr2NBpvUMB f1F56VTejt8iHxuVIsmyp5AvQGt+x/9IwJu7fUt8xwPHbyuqI16imUAMTWt4Zvpvw5Zc 7yA8LlxHBoyn9JISdja/r9lWAiZogbskA5d7J29YmuFt8Pjzj3ReEppdpv9KcU1KNzdo QdlKclk3TnvP7Z/XkGgh9COuf4srqG37E/DsywMzPtRR56rwYryK52Qw8y7id8YdaiA7 LrOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=t3TF6685c2WJdfJNI/FI0hp1VdsTJRBj/93i0/tT4D8=; b=HGqbyGA0GGLgWWkq9VtCCeu2XuPN3KQSpf39hP4DAbW5KqZVAVOu6tyNAWkPWBMKUG HWbDrFEpAm4ZrY+w05WGq245bySKI2Hba/Ia2lob55K9MsIlo9DWLHck7A545JvxJR8J bBJ0Zf3+kPKg2aktMVV8JurDRTLpIJnbz50zRPpWHMSYiJuXNCFOdIAan2DueSrnxeHl Nv3d7N1cI+qKSsgdsltLeWXybqGWpVoFoh+ocykAiIJhZ7L/YgvujBB5Gg/Aa+pc8CCL FlGU7p0/D80XQE7GYSmwPWigjHoaTaVobI+62/Xwy08BOQ+yRB8wlQlBqSbiAZwZCo5U zqGQ== X-Gm-Message-State: APjAAAWPKzo2BJ5FdE88KZIYwlrO/q17Kkexb12fBV5iPBJUs07GHIwE VBqhsyc2RF7zG200EpCFVIakMe/EaEWc1yMZ4Y1u/PQPSA== X-Google-Smtp-Source: APXvYqz78jOS7sKRiOL+JOPfAykpEf/X7u0UR4urkuwH8gc+wTjkqPhGEpeibe0HI7bhJ/amjyTOCGxfIlnvzoU7gX8= X-Received: by 2002:a17:906:30d1:: with SMTP id b17mr6413288ejb.9.1566597662589; Fri, 23 Aug 2019 15:01:02 -0700 (PDT) MIME-Version: 1.0 From: Chet Ensign Date: Fri, 23 Aug 2019 18:00:52 -0400 Message-ID: To: ietf-message-headers@ietf.org Cc: "Mark Biamonte (Progress)" , "Ralf Handl (SAP)" Content-Type: multipart/alternative; boundary="0000000000002f58eb0590cff11b" Archived-At: Subject: [Ietf-message-headers] Update to NEW PREFERENCE - allow-entityreferences, callback, continue-on-error, include-annotations, maxpagesize, omit-values, and track-changes X-BeenThere: ietf-message-headers@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion list for header fields used in Internet messaging applications." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2019 22:01:08 -0000 --0000000000002f58eb0590cff11b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable This message contains an update to the registration request submitted on 29 August 2018 in https://lists.w3.org/Archives/Public/ietf-http-wg/2018JulSep/0277.html In response to the feedback received (summed up nicely in https://lists.w3.org/Archives/Public/ietf-http-wg/2018OctDec/0279.html), the OData Technical Committee updated the registration documents to include the OData prefix in the Header and Preference names as suggested. Below, please find the revised request. I have included the prior values in [ ]s so that all the changes are visible. --- Open Data (OData) Protocol IANA Prefer Header Preference registration request 22-Jul-2019 ---------------------------------------------------------------------------= --- This documentation contains the information needed for Registration of the OData specific Prefer Header Preferences with IANA as called out in RFC 7240 - Prefer Header for HTTP. The OData Prefer Header Preferences to be registered are [odata.]allow-entityreferences [was allow-entityreferences and etc.] [odata.]callback [odata.]continue-on-error [odata.]include-annotations [odata.]maxpagesize omit-values [odata.]track-changes The details as required by RFC 7240 for registering these preferences are listed below #### Preference: [odata.]allow-entityreferences [was allow-entityreferences] Value: Optional Parameters: Description: Indicates that the service is allowed to return references in place of resources that have previously been returned, with at least the properties requested, in the same response. Reference: OData Version 4.01 Part 1: Protocol =E2=80=93 http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.htm= l#sec_Preferenceallowentityreferencesodata Notes: [optional] [was "The allow-entityreferences preference was named odata.allow-entityreferences in OData version 4.0."] #### Preference: [odata.]callback [was callback] Value: Optional Parameters: url - The URL of a callback endpoint to be invoked by the service when data is available. The URL parameter is required Description: Requests that the service invoke the specified URL to signal some service state, such as the completion of an asynchronous result or availability of new or modified information. The service state that triggers the change is dependent upon the request Reference: OData Version 4.01 Part 1: Protocol =E2=80=93 http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.htm= l#sec_Preferencecallbackodatacallback Notes: [optional] [was The callback preference was named odata.callback in OData version 4.0.= ] #### Preference: [odata.]continue-on-error [was continue-on-error] Value: Optional Parameters: Description: Requests that the service attempt to continue processing a request that encounters non-fatal errors, for example in a multi-part request. The response SHOULD indicate what portions of the request were and were not able to be successfully handled. Reference: OData Version 4.01 Part 1: Protocol =E2=80=93 http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.htm= l#sec_Preferencecontinueonerrorodatacontin Notes: [optional] [was The continue-on-error preference was named odata.continue-on-error in OData version 4.0.] #### Preference: [odata.]include-annotations [was include-annotations] Value: Comma-separated list of terms to include or, when prefixed with a minus sign (-), exclude from the response. Terms MUST be namespace-qualified and MAY specify just a namespace to include or exclude all terms within that namespace. The special value "*" matches all annotations. Optional Parameters: Description: Specifies the set of annotations the client requests to be included, where applicable, or excluded in the response. Reference: OData Version 4.01 Part 1: Protocol =E2=80=93 http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.htm= l#sec_Preferenceincludeannotationsodatainc Notes: [optional] [was The include-annotations preference was named odata.include-annotations in OData version 4.0.] #### Preference: [odata.]maxpagesize [was maxpagesize] Value: a positive integer that represents the maximum number of items each collection in a response SHOULD contain Optional Parameters: Description: Requests that each collection within the response contain no more than the number of items specified as the positive integer value of this preference. Reference: OData Version 4.01 Part 1: Protocol =E2=80=93 http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.htm= l#sec_Preferencemaxpagesizeodatamaxpagesiz Notes: [optional] [was The maxpagesize preference was named odata.maxpagesize in OData version 4.0.] #### Preference: omit-values [was Omit-values] Value: One of nulls - properties containing null values may be omitted from the response defaults - properties containing the property default value may be omitted from the response Optional Parameters: Description: Specifies whether a server can omit properties with a null value or properties set to their default value from a response Reference: OData Version 4.01 Part 1: Protocol =E2=80=93 http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.htm= l#sec_Preferenceomitvalues Notes: [optional] #### Preference: [odata.]track-changes [was track-changes] Value: Optional Parameters: Description: Requests that the service initiate change tracking on the result of this request, according to the underlying protocol. Reference: OData Version 4.01 Part 1: Protocol =E2=80=93 http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.htm= l#sec_Preferencetrackchangesodatatrackchan Notes: [optional] [was The track-changes preference was named odata.track-changes in OData version 4.0.] --=20 /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393 --0000000000002f58eb0590cff11b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
This message contains an update to the registration reques= t submitted on 29 August 2018 in https://lists.w3.org/Archives/Publ= ic/ietf-http-wg/2018JulSep/0277.html

In response to the feedback= received (summed up nicely in https://lists.w3.org/Archives/Public= /ietf-http-wg/2018OctDec/0279.html), the OData Technical Committee upda= ted the registration documents to include the OData prefix in the Header an= d Preference names as suggested. =C2=A0

Below, please find the revis= ed request. I have included the prior values in [ ]s so that all the change= s are visible.

---

Open Data (OData) Protocol IANA Prefer Hea= der Preference registration request
22-Jul-2019
---------------------= ---------------------------------------------------------

This docum= entation contains the information needed for Registration of the OData spec= ific Prefer Header Preferences with IANA as called out in RFC 7240 - Prefer= Header for HTTP. =C2=A0


The OData Prefer Header Preferences to = be registered are

[odata.]allow-entityreferences [was allow-entityre= ferences and etc.]
[odata.]callback
[odata.]continue-on-error
[od= ata.]include-annotations
[odata.]maxpagesize
omit-values
[odata.]t= rack-changes

The details as required by RFC 7240 for registering the= se preferences are listed below

####
Preference:
[odata.]allo= w-entityreferences =C2=A0[was allow-entityreferences]
=C2=A0
Value: =
<none>

Optional Parameters:
<none>

Desc= ription:
Indicates that the service is allowed to return references in p= lace of resources that have previously been returned, with at least the pro= perties requested, in the same response.

Reference:
OData Version= 4.01 Part 1: Protocol =E2=80=93
http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-= part1-protocol.html#sec_Preferenceallowentityreferencesodata

Not= es: [optional]
<None>
[was "The allow-entityreferences pre= ference was named odata.allow-entityreferences in OData version 4.0."]=

####
Preference:
[odata.]callback =C2=A0[was callback]
= =C2=A0
Value:
<none>

Optional Parameters:
url - T= he URL of a callback endpoint to be invoked by the service when data is ava= ilable.=C2=A0 The URL parameter is required

Description:
Request= s that the service invoke the specified URL to signal some service state, s= uch as the completion of an asynchronous result or availability of new or m= odified information. The service state that triggers the change is dependen= t upon the request

Reference:
OData Version 4.01 Part 1: Protocol= =E2=80=93
http://do= cs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_Pre= ferencecallbackodatacallback

Notes: [optional]
<None>[was The callback preference was named odata.callback in OData version 4.= 0.]

####
Preference:
[odata.]continue-on-error =C2=A0[was con= tinue-on-error]
=C2=A0
Value:
<none>

Optional Para= meters:
<none>

Description:
Requests that the service = attempt to continue processing a request that encounters non-fatal errors, = for example in a multi-part request. The response SHOULD indicate what port= ions of the request were and were not able to be successfully handled.
=
Reference:
OData Version 4.01 Part 1: Protocol =E2=80=93
http://docs.oasis-open.org= /odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_Preferencecontinueon= errorodatacontin

Notes: [optional]
<None>
[was The c= ontinue-on-error preference was named odata.continue-on-error in OData vers= ion 4.0.]

####
Preference:
[odata.]include-annotations [was i= nclude-annotations]
=C2=A0
Value:
Comma-separated list of terms = to include or, when prefixed with a minus sign (-), exclude from the respon= se. Terms MUST be namespace-qualified and MAY specify just a namespace to i= nclude or exclude all terms within that namespace. The special value "= *" matches all annotations.

Optional Parameters:
<none&= gt;

Description:
Specifies the set of annotations the client req= uests to be included, where applicable, or excluded in the response.
<= br>Reference:
OData Version 4.01 Part 1: Protocol =E2=80=93
http://docs.oasis-open.org/= odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_Preferenceincludeanno= tationsodatainc

Notes: [optional]
<None>
[was =C2=A0= The include-annotations preference was named odata.include-annotations in O= Data version 4.0.]

####
Preference:
[odata.]maxpagesize =C2= =A0[was maxpagesize]
=C2=A0
Value:
a positive integer that repre= sents the maximum number of items each collection in a response SHOULD cont= ain

Optional Parameters:
<none>

Description:
R= equests that each collection within the response contain no more than the n= umber of items specified as the positive integer value of this preference.<= br>
Reference:
OData Version 4.01 Part 1: Protocol =E2=80=93
http://docs.oasis-open= .org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_Preferencemaxpag= esizeodatamaxpagesiz

Notes: [optional]
<None>
[was= The maxpagesize preference was named odata.maxpagesize in OData version 4.= 0.]

####
Preference:
omit-values =C2=A0[was Omit-values]
<= br>Value:
One of
=C2=A0 =C2=A0nulls - =C2=A0properties containing n= ull values may be omitted from the response
=C2=A0 =C2=A0defaults - pro= perties containing the property default value may be omitted from the respo= nse

Optional Parameters:
<none>

Description:
S= pecifies whether a server can omit properties with a null value or properti= es set to their default value from a response

Reference:
OData V= ersion 4.01 Part 1: Protocol =E2=80=93
http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-prot= ocol.html#sec_Preferenceomitvalues

Notes: [optional]
<none= >

####
Preference:
[odata.]track-changes =C2=A0[was track-= changes]
=C2=A0
Value:
<none>

Optional Parameters:=
<none>

Description:
Requests that the service initiat= e change tracking on the result of this request, according to the underlyin= g protocol.

Reference:
OData Version 4.01 Part 1: Protocol =E2= =80=93
http://d= ocs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_Pr= eferencetrackchangesodatatrackchan

Notes: [optional]
<none= >
[was The track-changes preference was named odata.track-changes in= OData version 4.0.]

--

/chet=C2=A0
----------------
Chet Ensign
Chief Technical Community Steward
OASIS: Advancing open stan= dards for the information society
http://www.oasis-open.org

M= obile: +1 201-341-1393=C2=A0
--0000000000002f58eb0590cff11b--