From c7b586edb13797f573e2c312fa9ef77e5434574b Mon Sep 17 00:00:00 2001 From: D024504 Date: Thu, 26 Oct 2023 08:28:19 +0200 Subject: [PATCH] Punctuation on the wrong side of the backtick --- docs/odata-csdl-json/odata-csdl-json.html | 2 +- docs/odata-csdl-json/odata-csdl-json.md | 2 +- docs/odata-csdl-xml/odata-csdl-xml.html | 4 ++-- docs/odata-csdl-xml/odata-csdl-xml.md | 6 +++--- docs/odata-json-format/odata-json-format.html | 4 ++-- docs/odata-json-format/odata-json-format.md | 4 ++-- docs/odata-protocol/odata-protocol.html | 14 +++++++------- docs/odata-protocol/odata-protocol.md | 14 +++++++------- .../odata-url-conventions.html | 6 +++--- .../odata-url-conventions/odata-url-conventions.md | 6 +++--- odata-csdl/14 Vocabulary and Annotation.md | 2 +- odata-csdl/4 CSDL Document.md | 4 ++-- odata-json-format/15 Delta Payload.md | 2 +- odata-json-format/4 Common Characteristics.md | 2 +- odata-protocol/11 Data Service Requests.md | 6 +++--- odata-protocol/11.4 Data Modification.md | 6 +++--- odata-protocol/11.7 Batch Requests.md | 2 +- odata-url-conventions/5 Query Options.md | 6 +++--- 18 files changed, 46 insertions(+), 46 deletions(-) diff --git a/docs/odata-csdl-json/odata-csdl-json.html b/docs/odata-csdl-json/odata-csdl-json.html index fd9b8ee35..d73e47da3 100644 --- a/docs/odata-csdl-json/odata-csdl-json.html +++ b/docs/odata-csdl-json/odata-csdl-json.html @@ -3011,7 +3011,7 @@

14.4.4.2 Function odata.fillUriTemplate

-

The odata.fillUriTemplate client-side function takes two or more expressions as arguments and returns a value of type Edm.String.

+

The odata.fillUriTemplate client-side function takes two or more expressions as arguments and returns a value of type Edm.String.

The first argument MUST be of type Edm.String and specifies a URI template according to RFC6570, the other arguments MUST be labeled element expressions. Each labeled element expression specifies the template parameter name as its name and evaluates to the template parameter value.

RFC6570 defines three kinds of template parameters: simple values, lists of values, and key-value maps.

Simple values are represented as labeled element expressions that evaluate to a single primitive value. The literal representation of this value according to OData-ABNF is used to fill the corresponding template parameter.

diff --git a/docs/odata-csdl-json/odata-csdl-json.md b/docs/odata-csdl-json/odata-csdl-json.md index ca66b44a0..c3c0540a2 100644 --- a/docs/odata-csdl-json/odata-csdl-json.md +++ b/docs/odata-csdl-json/odata-csdl-json.md @@ -4972,7 +4972,7 @@ the member name of the enumeration value. #### 14.4.4.2 Function `odata.fillUriTemplate` The `odata.fillUriTemplate` client-side function takes two or more -expressions as arguments and returns a value of type `Edm.String.` +expressions as arguments and returns a value of type `Edm.String`. The first argument MUST be of type `Edm.String` and specifies a URI template according to [RFC6570](#rfc6570), the other arguments MUST be diff --git a/docs/odata-csdl-xml/odata-csdl-xml.html b/docs/odata-csdl-xml/odata-csdl-xml.html index 45c523bea..0d1b52af9 100644 --- a/docs/odata-csdl-xml/odata-csdl-xml.html +++ b/docs/odata-csdl-xml/odata-csdl-xml.html @@ -774,7 +774,7 @@

The edmx:Edmx element is the root element of a CSDL XML document. It MUST contain the Version attribute and it MUST contain exactly one edmx:DataServices element.

It MAY contain edmx:Reference elements to reference other CSDL documents.

Attribute Version

-

The Version attribute specifies the OData protocol version of the service. For OData 4.0 responses the value of this attribute MUST be 4.0. For OData 4.01 responses the value of this attribute MUST be 4.01. Services MUST return an OData 4.0 response if the request was made with an OData-MaxVersion header with a value of 4.0.

+

The Version attribute specifies the OData protocol version of the service. For OData 4.0 responses the value of this attribute MUST be 4.0. For OData 4.01 responses the value of this attribute MUST be 4.01. Services MUST return an OData 4.0 response if the request was made with an OData-MaxVersion header with a value of 4.0.

Element edmx:DataServices

The edmx:DataServices element MUST contain one or more edm:Schema elements which define the schemas exposed by the OData service.

@@ -2801,7 +2801,7 @@

14.4.4.2 Function odata.fillUriTemplate

-

The odata.fillUriTemplate client-side function takes two or more expressions as arguments and returns a value of type Edm.String.

+

The odata.fillUriTemplate client-side function takes two or more expressions as arguments and returns a value of type Edm.String.

The first argument MUST be of type Edm.String and specifies a URI template according to RFC6570, the other arguments MUST be labeled element expressions. Each labeled element expression specifies the template parameter name as its name and evaluates to the template parameter value.

RFC6570 defines three kinds of template parameters: simple values, lists of values, and key-value maps.

Simple values are represented as labeled element expressions that evaluate to a single primitive value. The literal representation of this value according to OData-ABNF is used to fill the corresponding template parameter.

diff --git a/docs/odata-csdl-xml/odata-csdl-xml.md b/docs/odata-csdl-xml/odata-csdl-xml.md index 5f2bcead3..54781c677 100644 --- a/docs/odata-csdl-xml/odata-csdl-xml.md +++ b/docs/odata-csdl-xml/odata-csdl-xml.md @@ -852,8 +852,8 @@ other CSDL documents. The `Version` attribute specifies the OData protocol version of the service. For OData 4.0 responses the value of this attribute MUST be -`4.0.` For OData 4.01 responses the value of this attribute MUST be -`4.01.` Services MUST return an OData 4.0 response if the request was +`4.0`. For OData 4.01 responses the value of this attribute MUST be +`4.01`. Services MUST return an OData 4.0 response if the request was made with an `OData-MaxVersion `header with a value of `4.0`. ### Element `edmx:DataServices` @@ -4802,7 +4802,7 @@ the member name of the enumeration value. #### 14.4.4.2 Function `odata.fillUriTemplate` The `odata.fillUriTemplate` client-side function takes two or more -expressions as arguments and returns a value of type `Edm.String.` +expressions as arguments and returns a value of type `Edm.String`. The first argument MUST be of type `Edm.String` and specifies a URI template according to [RFC6570](#rfc6570), the other arguments MUST be diff --git a/docs/odata-json-format/odata-json-format.html b/docs/odata-json-format/odata-json-format.html index f78c08bfa..372c60dfe 100644 --- a/docs/odata-json-format/odata-json-format.html +++ b/docs/odata-json-format/odata-json-format.html @@ -416,7 +416,7 @@

4.1 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.

+

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 metadata parameter to specify the amount of metadata included in the response.

Requests and responses MUST include the IEEE754Compatible parameter if Edm.Int64 and Edm.Decimal numbers are represented as strings.

Requests and responses MAY add the streaming parameter with a value of true or false, see section "Payload Ordering Constraints".

@@ -1256,7 +1256,7 @@

15.3 D

In OData 4.01 payloads the deleted-entity object MUST include the following properties, regardless of the specified metadata value:

For full metadata the context control information MUST be included. It also MUST be included if the entity set of the deleted entity cannot be determined from the surrounding context.

The deleted-entity object MAY include additional properties of the entity, as well as annotations, and MAY include related entities, related deleted entities, or a delta or full representation of a related collection of entities, to represent related entities that have been modified or deleted.

diff --git a/docs/odata-json-format/odata-json-format.md b/docs/odata-json-format/odata-json-format.md index 7c4aad95d..539712cc3 100644 --- a/docs/odata-json-format/odata-json-format.md +++ b/docs/odata-json-format/odata-json-format.md @@ -551,7 +551,7 @@ 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 +Allowed values are `UTF-8`, `UTF-16`, and `UTF-32`. If no `charset` parameter is present, `UTF-8` MUST be assumed. @@ -2383,7 +2383,7 @@ following properties, regardless of the specified from the response _or_ the entity-id is not identical to the canonical URL of the entity. For [ordered payloads](#PayloadOrderingConstraints), the control information - `id,` if present, MUST immediately follow the control + `id`, if present, MUST immediately follow the control information [`removed`](#ControlInformationremovedodataremoved). diff --git a/docs/odata-protocol/odata-protocol.html b/docs/odata-protocol/odata-protocol.html index 9f32d72fb..0a5a90a4f 100644 --- a/docs/odata-protocol/odata-protocol.html +++ b/docs/odata-protocol/odata-protocol.html @@ -1480,7 +1480,7 @@

11.2.6.1.3 Parameter Aliases
-

Parameter aliases can be used in place of literal values in entity keys, function parameters, or within a $compute, $filter or $orderby expression. Parameters aliases are names beginning with an at sign (@).

+

Parameter aliases can be used in place of literal values in entity keys, function parameters, or within a $compute, $filter or $orderby expression. Parameters aliases are names beginning with an at sign (@).

Actual parameter values are specified as query options in the query part of the request URL. The query option name is the name of the parameter alias, and the query option value is the value to be used for the specified parameter alias.

Example 48: returns all employees whose Region property matches the string parameter value "WA"

@@ -1673,7 +1673,7 @@

GET http://host/service/Orders?$format=json

is equivalent to a request with the Accept header set to application/json; it requests the set of Order entities represented using the JSON media type with minimal metadata, as defined in OData-JSON.

-

In metadata document requests, the values application/xml and application/json, along with their subtypes and parameterized variants, as well as the format-specific abbreviations xml and json, are reserved for this specification.

+

In metadata document requests, the values application/xml and application/json, along with their subtypes and parameterized variants, as well as the format-specific abbreviations xml and json, are reserved for this specification.

11.2.12 System Query Option $schemaversion

The $schemaversion system query option MAY be included in any request. For a metadata document request the value of the $schemaversion system query option addresses a specific schema version. For all other request types the value specifies the version of the schema against which the request is made. The syntax of the $schemaversion system query option is defined in OData-ABNF.

The value of the $schemaversion system query option MUST be a version of the schema as returned in the Core.SchemaVersion annotation, defined in OData-VocCore, of a previous request to the metadata document, or * in order to specify the current version of the metadata.

@@ -1683,7 +1683,7 @@

404 Not Found. The response body SHOULD provide additional information.

11.3 Requesting Changes

-

Services advertise their change-tracking capabilities by annotating entity sets with the Capabilities.ChangeTracking term defined in OData-VocCap.

+

Services advertise their change-tracking capabilities by annotating entity sets with the Capabilities.ChangeTracking term defined in OData-VocCap.

Any GET request to retrieve one or more entities MAY allow change-tracking.

Clients request that the service track changes to a result by specifying the track-changes preference on a request. If supported for the request, the service includes a Preference-Applied header in the response containing the track-changes preference and includes a delta link in a result for a single entity, and on the last page of results for a collection of entities in place of the next link.

@@ -1810,16 +1810,16 @@