From 447e6899a04bb54b9728cc0314943451fad915cc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Heiko=20Thei=C3=9Fen?= Date: Fri, 10 Nov 2023 16:07:23 +0100 Subject: [PATCH 1/2] More backtick errors (#214) --- docs/odata-csdl-json/odata-csdl-json.html | 10 +++--- docs/odata-csdl-json/odata-csdl-json.md | 10 +++--- docs/odata-csdl-xml/odata-csdl-xml.html | 12 +++---- docs/odata-csdl-xml/odata-csdl-xml.md | 12 +++---- docs/odata-json-format/odata-json-format.html | 6 ++-- docs/odata-json-format/odata-json-format.md | 8 ++--- docs/odata-protocol/odata-protocol.html | 30 ++++++++--------- docs/odata-protocol/odata-protocol.md | 32 +++++++++---------- .../odata-temporal-ext.html | 2 +- docs/odata-temporal-ext/odata-temporal-ext.md | 4 +-- .../odata-url-conventions.html | 10 +++--- .../odata-url-conventions.md | 12 +++---- odata-csdl/13 Entity Container.md | 2 +- odata-csdl/14 Vocabulary and Annotation.md | 8 ++--- odata-csdl/4 CSDL Document.md | 2 +- odata-csdl/5 Schema.md | 2 +- odata-json-format/4 Common Characteristics.md | 8 ++--- odata-protocol/10 Context URL.md | 8 ++--- odata-protocol/11 Data Service Requests.md | 8 ++--- odata-protocol/12 Conformance.md | 2 +- odata-protocol/8 Header Fields.md | 14 ++++---- odata-temporal-ext/3 Vocabulary.md | 4 +-- odata-url-conventions/4 Resource Path.md | 6 ++-- odata-url-conventions/5 Query Options.md | 6 ++-- 24 files changed, 109 insertions(+), 109 deletions(-) diff --git a/docs/odata-csdl-json/odata-csdl-json.html b/docs/odata-csdl-json/odata-csdl-json.html index a7b177eda..f14e05fab 100644 --- a/docs/odata-csdl-json/odata-csdl-json.html +++ b/docs/odata-csdl-json/odata-csdl-json.html @@ -1078,7 +1078,7 @@

Media entity types MAY specify a list of acceptable media types using an annotation with term Core.AcceptableMediaTypes, see OData-VocCore.

$HasStream

-

The value of $HasStream is one of the Boolean literals true or false. Absence of the member means false.

+

The value of $HasStream is one of the Boolean literals true or false. Absence of the member means false.

6.5 Key

An entity is uniquely identified within an entity set by its key. A key MAY be specified if the entity type does not specify a base type that already has a key declared.

@@ -2666,7 +2666,7 @@

1 ]

14.4.1.4 Model Element Path

-

The model element path expression provides a value for terms or term properties that specify the built-in type Edm.ModelElementPath. Its argument is a model path.

+

The model element path expression provides a value for terms or term properties that specify the built-in type Edm.ModelElementPath. Its argument is a model path.

The value of the model element path expression is the path itself, not the instance(s) identified by the path.

Model element path expressions are represented as a string containing a path.

@@ -2676,7 +2676,7 @@ 

"@org.example.MyFavoriteModelElement": "/self.someAction"

14.4.1.5 Navigation Property Path

-

The navigation property path expression provides a value for terms or term properties that specify the built-in types Edm.NavigationPropertyPath, Edm.AnyPropertyPath, or Edm.ModelElementPath. Its argument is a model path with the following restriction:

+

The navigation property path expression provides a value for terms or term properties that specify the built-in types Edm.NavigationPropertyPath, Edm.AnyPropertyPath, or Edm.ModelElementPath. Its argument is a model path with the following restriction:

@@ -2696,7 +2696,7 @@

}

14.4.1.6 Property Path

-

The property path expression provides a value for terms or term properties that specify one of the built-in types Edm.PropertyPath, Edm.AnyPropertyPath, or Edm.ModelElementPath. Its argument is a model path with the following restriction:

+

The property path expression provides a value for terms or term properties that specify one of the built-in types Edm.PropertyPath, Edm.AnyPropertyPath, or Edm.ModelElementPath. Its argument is a model path with the following restriction:

@@ -3047,7 +3047,7 @@

}

14.4.4.4 Function odata.uriEncode

-

The odata.uriEncode client-side function takes one argument of primitive type and returns the URL-encoded OData literal that can be used as a key value in OData URLs or in the query part of OData URLs.

+

The odata.uriEncode client-side function takes one argument of primitive type and returns the URL-encoded OData literal that can be used as a key value in OData URLs or in the query part of OData URLs.

Note: string literals are surrounded by single quotes as required by the paren-style key syntax.

Example 78:

diff --git a/docs/odata-csdl-json/odata-csdl-json.md b/docs/odata-csdl-json/odata-csdl-json.md index 6d83f0998..c86850343 100644 --- a/docs/odata-csdl-json/odata-csdl-json.md +++ b/docs/odata-csdl-json/odata-csdl-json.md @@ -1497,7 +1497,7 @@ see [OData-VocCore](#ODataVocCore). ::: {.varjson .rep} ### `$HasStream` -The value of `$HasStream `is one of the Boolean literals `true` or +The value of `$HasStream` is one of the Boolean literals `true` or `false`. Absence of the member means `false`. ::: @@ -4502,7 +4502,7 @@ Example 68: The model element path expression provides a value for terms or term properties that specify the [built-in -type](#BuiltInTypesfordefiningVocabularyTerms)` Edm.ModelElementPath`. Its +type](#BuiltInTypesfordefiningVocabularyTerms) `Edm.ModelElementPath`. Its argument is a [model path](#PathExpressions). The value of the model element path expression is the path itself, not @@ -4527,7 +4527,7 @@ Example 69: The navigation property path expression provides a value for terms or term properties that specify the [built-in types](#BuiltInTypesfordefiningVocabularyTerms) -`Edm.NavigationPropertyPath, Edm.AnyPropertyPath, or Edm.ModelElementPath`. +`Edm.NavigationPropertyPath`, `Edm.AnyPropertyPath`, or `Edm.ModelElementPath`. Its argument is a [model path](#PathExpressions) with the following restriction: - A non-null path MUST resolve to a model @@ -4563,7 +4563,7 @@ Example 70: The property path expression provides a value for terms or term properties that specify one of the [built-in types](#BuiltInTypesfordefiningVocabularyTerms) -`Edm.PropertyPath, Edm.AnyPropertyPath, or Edm.ModelElementPath`. Its +`Edm.PropertyPath`, `Edm.AnyPropertyPath`, or `Edm.ModelElementPath`. Its argument is a [model path](#PathExpressions) with the following restriction: - A non-null path MUST resolve to a model @@ -5047,7 +5047,7 @@ Example 77: all non-empty `FirstName` values not containing the letters #### 14.4.4.4 Function `odata.uriEncode` -The `odata.uriEncode `client-side function takes one argument of +The `odata.uriEncode` client-side function takes one argument of primitive type and returns the URL-encoded OData literal that can be used as a key value in OData URLs or in the query part of OData URLs. diff --git a/docs/odata-csdl-xml/odata-csdl-xml.html b/docs/odata-csdl-xml/odata-csdl-xml.html index 497847b76..c359dead1 100644 --- a/docs/odata-csdl-xml/odata-csdl-xml.html +++ b/docs/odata-csdl-xml/odata-csdl-xml.html @@ -773,7 +773,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.

@@ -1743,7 +1743,7 @@

</EntitySet>
-

Example 37: binding Supplier on Products contained within Categories – binding applies to all suppliers of all products of all categories

+

Example 37: binding Supplier on Products contained within Categories – binding applies to all suppliers of all products of all categories

<EntitySet Name="Categories" EntityType="self.Category">
   <NavigationPropertyBinding Path="Products/Supplier"
                              Target="Suppliers" />
@@ -2532,7 +2532,7 @@ 
</Annotation>

14.4.1.4 Model Element Path

-

The model element path expression provides a value for terms or term properties that specify the built-in type Edm.ModelElementPath. Its argument is a model path.

+

The model element path expression provides a value for terms or term properties that specify the built-in type Edm.ModelElementPath. Its argument is a model path.

The value of the model element path expression is the path itself, not the instance(s) identified by the path.

Expression edm:ModelElementPath

@@ -2548,7 +2548,7 @@

</Annotation>

14.4.1.5 Navigation Property Path

-

The navigation property path expression provides a value for terms or term properties that specify the built-in types Edm.NavigationPropertyPath, Edm.AnyPropertyPath, or Edm.ModelElementPath. Its argument is a model path with the following restriction:

+

The navigation property path expression provides a value for terms or term properties that specify the built-in types Edm.NavigationPropertyPath, Edm.AnyPropertyPath, or Edm.ModelElementPath. Its argument is a model path with the following restriction:

@@ -2573,7 +2573,7 @@

</Annotation>

14.4.1.6 Property Path

-

The property path expression provides a value for terms or term properties that specify one of the built-in types Edm.PropertyPath, Edm.AnyPropertyPath, or Edm.ModelElementPath. Its argument is a model path with the following restriction:

+

The property path expression provides a value for terms or term properties that specify one of the built-in types Edm.PropertyPath, Edm.AnyPropertyPath, or Edm.ModelElementPath. Its argument is a model path with the following restriction:

@@ -2825,7 +2825,7 @@

</Apply>

14.4.4.4 Function odata.uriEncode

-

The odata.uriEncode client-side function takes one argument of primitive type and returns the URL-encoded OData literal that can be used as a key value in OData URLs or in the query part of OData URLs.

+

The odata.uriEncode client-side function takes one argument of primitive type and returns the URL-encoded OData literal that can be used as a key value in OData URLs or in the query part of OData URLs.

Note: string literals are surrounded by single quotes as required by the paren-style key syntax.

Example 78:

diff --git a/docs/odata-csdl-xml/odata-csdl-xml.md b/docs/odata-csdl-xml/odata-csdl-xml.md index be85d2dfc..fa239840d 100644 --- a/docs/odata-csdl-xml/odata-csdl-xml.md +++ b/docs/odata-csdl-xml/odata-csdl-xml.md @@ -852,7 +852,7 @@ 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`. +made with an `OData-MaxVersion` header with a value of `4.0`. ### Element `edmx:DataServices` @@ -3150,7 +3150,7 @@ Example 36: for an entity set in any container in scope ::: {.varxml .example} Example 37: binding `Supplier` on `Products` contained within -`Categories – binding applies to all suppliers of all products of all categories` +`Categories` – binding applies to all suppliers of all products of all categories ```xml 14.4.4.4 Function `odata.uriEncode` -The `odata.uriEncode `client-side function takes one argument of +The `odata.uriEncode` client-side function takes one argument of primitive type and returns the URL-encoded OData literal that can be used as a key value in OData URLs or in the query part of OData URLs. diff --git a/docs/odata-json-format/odata-json-format.html b/docs/odata-json-format/odata-json-format.html index bc33d3f42..a65181d62 100644 --- a/docs/odata-json-format/odata-json-format.html +++ b/docs/odata-json-format/odata-json-format.html @@ -514,7 +514,7 @@

type control information unless their type is Double. -
  • The special floating-point values -INF, INF, and NaN are serialized as strings and MUST have a type control information to specify the numeric type of the property.
    • +
  • The special floating-point values -INF, INF, and NaN are serialized as strings and MUST have a type control information to specify the numeric type of the property.
  • 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 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.

    • The type control information can be absent in properties nested in an instance of type Edm.Untyped. In particular, individual primitive values within a collection cannot have type control information.

    @@ -550,7 +550,7 @@

    4.5.8 Control Information: id (odata.id)

    The id control information contains the entity-id, see OData-Protocol. By convention the entity-id is identical to the canonical URL of the entity, as defined in OData-URL.

    -

    The id control information MUST appear in responses if metadata=full is requested, or if metadata=minimal is requested and any of a non-transient entity's key fields are omitted from the response or the entity-id is not identical to the canonical URL of the entity after

    +

    The id control information MUST appear in responses if metadata=full is requested, or if metadata=minimal is requested and any of a non-transient entity’s key fields are omitted from the response or the entity-id is not identical to the canonical URL of the entity after

  • SupportedActions is a collection of qualified names of temporal actions that may be bound to the annotated entity set. These can be the standard actions defined in this specification, or service-specific actions.
    • diff --git a/docs/odata-temporal-ext/odata-temporal-ext.md b/docs/odata-temporal-ext/odata-temporal-ext.md index 885e29c74..d95622a5b 100644 --- a/docs/odata-temporal-ext/odata-temporal-ext.md +++ b/docs/odata-temporal-ext/odata-temporal-ext.md @@ -1302,8 +1302,8 @@ structured type with the following properties: - If the period end property does not specify a default value, a default value of "ad infinitum" is assumed. - Records of type `TimelineVisible` MAY specify the property `ObjectKey`. - - `ObjectKey` is the “sub-key” or “alternate key” that identifies time slices for a single temporal object. It is only necessary if the annotated entity set can contain time slices - for more than one temporal object. `The object key is `a collection of + - `ObjectKey` is the "sub-key" or "alternate key" that identifies time slices for a single temporal object. It is only necessary if the annotated entity set can contain time slices + for more than one temporal object. The object key is a collection of property paths whose value combination uniquely identifies a temporal object. - `SupportedActions` is a collection of diff --git a/docs/odata-url-conventions/odata-url-conventions.html b/docs/odata-url-conventions/odata-url-conventions.html index 1e6b5a6fc..ef4c7a179 100644 --- a/docs/odata-url-conventions/odata-url-conventions.html +++ b/docs/odata-url-conventions/odata-url-conventions.html @@ -702,7 +702,7 @@

    Properties of type Edm.Stream already return the raw value of the media stream and do not support appending the /$value segment.

    4.8 Addressing the Count of a Collection

    To address the raw value of the number of items in a collection, clients append /$count to the resource path of the URL identifying the entity set or collection.

    -

    The /$count path suffix identifies the integer count of records in the collection and SHOULD NOT be combined with the system query options $top, $skip, $orderby, $expand, and $format. The count MUST NOT be affected by $top, $skip, $orderby, or $expand.

    +

    The /$count path suffix identifies the integer count of records in the collection and SHOULD NOT be combined with the system query options $top, $skip, $orderby, $expand, and $format. The count MUST NOT be affected by $top, $skip, $orderby, or $expand.

    The count is calculated after applying any /$filter path segments, or $filter or $search system query options to the collection.

    Example 30: the number of related entities

    @@ -726,7 +726,7 @@

    4.9 Addressing a Member within an Entity Collection

    Collections of entities are modeled as entity sets, collection-valued navigation properties, or operation results.

    -

    For entity sets, results of operations associated with an entity set through an EntitySet or EntitySetPath declaration, or collection-valued navigation properties with a NavigationPropertyBinding or ContainsTarget=true specification, members of the collection can be addressed by convention by appending the parenthesized key to the URL specifying the collection of entities, or by using the key-as-segment convention if supported by the service.

    +

    For entity sets, results of operations associated with an entity set through an EntitySet or EntitySetPath declaration, or collection-valued navigation properties with a NavigationPropertyBinding or ContainsTarget=true specification, members of the collection can be addressed by convention by appending the parenthesized key to the URL specifying the collection of entities, or by using the key-as-segment convention if supported by the service.

    For collection-valued navigation properties with navigation property bindings that end in a type-cast segment, a type-cast segment MUST be appended to the collection URL before appending the key segment.

    Note: entity sets or collection-valued navigation properties annotated with term Capabilities.IndexableByKey defined in OData-VocCap and a value of false do not support addressing their members by key.

    4.10 Addressing a Member of an Ordered Collection

    @@ -852,7 +852,7 @@

    5 Query Options

    The query options part of an OData URL specifies three types of information: system query options, custom query options, and parameter aliases. All OData services MUST follow the query string parsing and construction rules defined in this section and its subsections.

    5.1 System Query Options

    -

    System query options are query string parameters that control the amount and order of the data returned for the resource identified by the URL. The names of all system query options are optionally prefixed with a dollar ($) character. 4.01 Services MUST support case-insensitive system query option names specified with or without the $ prefix. Clients that want to work with 4.0 services MUST use lower case names and specify the $ prefix.

    +

    System query options are query string parameters that control the amount and order of the data returned for the resource identified by the URL. The names of all system query options are optionally prefixed with a dollar ($) character. 4.01 Services MUST support case-insensitive system query option names specified with or without the $ prefix. Clients that want to work with 4.0 services MUST use lower case names and specify the $ prefix.

    For GET, PATCH, and PUT requests the following rules apply:

    • Resource paths identifying a single entity, a complex type instance, a collection of entities, or a collection of complex type instances allow $compute, $expand and $select.
      • @@ -1864,14 +1864,14 @@

      5.1.5 System Query Option $orderby

      The $orderby system query option allows clients to request resources in a particular order.

      The semantics of $orderby are covered in the OData-Protocol document.

      The OData-ABNF orderby syntax rule defines the formal grammar of the $orderby query option.

      5.1.6 System Query Options $top and $skip

      The $top system query option requests the number of items in the queried collection to be included in the result. The $skip query option requests the number of items in the queried collection that are to be skipped and not included in the result. A client can request a particular page of items by combining $top and $skip.

      -

      The semantics of $top and $skip are covered in the OData-Protocol document. The OData-ABNF top and skip syntax rules define the formal grammar of the $top and $skip query options respectively.

      +

      The semantics of $top and $skip are covered in the OData-Protocol document. The OData-ABNF top and skip syntax rules define the formal grammar of the $top and $skip query options respectively.

      5.1.7 System Query Option $count

      The $count system query option allows clients to request a count of the matching resources included with the resources in the response. The $count query option has a Boolean value of true or false.

      The semantics of $count is covered in the OData-Protocol document.

      diff --git a/docs/odata-url-conventions/odata-url-conventions.md b/docs/odata-url-conventions/odata-url-conventions.md index ff5a8cb5f..f8e8d399e 100644 --- a/docs/odata-url-conventions/odata-url-conventions.md +++ b/docs/odata-url-conventions/odata-url-conventions.md @@ -997,7 +997,7 @@ To address the raw value of the number of items in a collection, clients append `/$count` to the resource path of the URL identifying the entity set or collection. -The `/$count `path suffix identifies the integer count of records in the +The `/$count` path suffix identifies the integer count of records in the collection and SHOULD NOT be combined with the system query options [`$top`](#SystemQueryOptionstopandskip), [`$skip`](#SystemQueryOptionstopandskip), @@ -1055,9 +1055,9 @@ Collections of entities are modeled as entity sets, collection-valued navigation properties, or operation results. For entity sets, results of operations associated with an entity set -through an `EntitySet `or `EntitySetPath` declaration, or +through an `EntitySet` or `EntitySetPath` declaration, or collection-valued navigation properties with a -`NavigationPropertyBinding `or `ContainsTarget=true `specification, +`NavigationPropertyBinding` or `ContainsTarget=true` specification, members of the collection can be addressed by convention by appending the parenthesized key to the URL specifying the collection of entities, or by using the [key-as-segment convention](#KeyasSegmentConvention) if @@ -1413,7 +1413,7 @@ System query options are query string parameters that control the amount and order of the data returned for the resource identified by the URL. The names of all system query options are optionally prefixed with a dollar (`$`) character. 4.01 Services MUST support case-insensitive -system query option names specified with or without the `$ `prefix. +system query option names specified with or without the `$` prefix. Clients that want to work with 4.0 services MUST use lower case names and specify the `$` prefix. @@ -3634,7 +3634,7 @@ http://host/service/Products?$select=ID,Model.ActionName,Model2.* ``` ::: -When multiple select item exist in a `select clause`, then the total set +When multiple select item exist in a `$select` clause, then the total set of properties, open properties, navigation properties, actions and functions to be returned is equal to the union of the set of those identified by each select item. @@ -3661,7 +3661,7 @@ particular page of items by combining `$top` and `$skip`. The semantics of `$top` and `$skip` are covered in the [OData-Protocol](#ODataProtocol) document. The [OData-ABNF](#ODataABNF) `top` and `skip` syntax rules define the formal grammar of the `$top` and -`$skip `query options respectively. +`$skip` query options respectively. ### 5.1.7 System Query Option `$count` diff --git a/odata-csdl/13 Entity Container.md b/odata-csdl/13 Entity Container.md index 956f807e1..7a826a547 100644 --- a/odata-csdl/13 Entity Container.md +++ b/odata-csdl/13 Entity Container.md @@ -553,7 +553,7 @@ Example ##ex: for an entity set in any container in scope ::: {.varxml .example} Example ##ex: binding `Supplier` on `Products` contained within -`Categories – binding applies to all suppliers of all products of all categories` +`Categories` – binding applies to all suppliers of all products of all categories ```xml Date: Sat, 11 Nov 2023 12:14:43 +0100 Subject: [PATCH 2/2] Yet more backtick errors (#215) --- docs/odata-csdl-json/odata-csdl-json.html | 4 ++-- docs/odata-csdl-json/odata-csdl-json.md | 6 ++++-- docs/odata-protocol/odata-protocol.html | 18 +++++++++--------- docs/odata-protocol/odata-protocol.md | 19 ++++++++++--------- .../odata-temporal-ext.html | 2 +- docs/odata-temporal-ext/odata-temporal-ext.md | 2 +- .../odata-url-conventions.html | 8 ++++---- .../odata-url-conventions.md | 8 ++++---- odata-csdl/14 Vocabulary and Annotation.md | 2 +- odata-csdl/15 Identifier and Path Values.md | 2 +- odata-protocol/10 Context URL.md | 12 ++++++------ odata-protocol/11.5 Operations.md | 2 +- odata-protocol/11.7 Batch Requests.md | 4 ++-- odata-temporal-ext/4 Temporal Requests.md | 2 +- odata-url-conventions/4 Resource Path.md | 6 +++--- odata-url-conventions/5 Query Options.md | 2 +- 16 files changed, 51 insertions(+), 48 deletions(-) diff --git a/docs/odata-csdl-json/odata-csdl-json.html b/docs/odata-csdl-json/odata-csdl-json.html index f14e05fab..4eb79932b 100644 --- a/docs/odata-csdl-json/odata-csdl-json.html +++ b/docs/odata-csdl-json/odata-csdl-json.html @@ -2857,7 +2857,7 @@

      < "S" ] ] -} ```

    +}

    14.4.3 Arithmetic Operators

    Annotations MAY use the following arithmetic expressions which evaluate to a numeric value. These expressions MAY be combined, and they MAY be used anywhere instead of a numeric expression of the appropriate type. The semantics and evaluation rules for each arithmetic expression is identical to the corresponding arithmetic operator defined in OData-URL.

    @@ -3563,7 +3563,7 @@

    } } } -} ``` +}

    17 Conformance

    diff --git a/docs/odata-csdl-json/odata-csdl-json.md b/docs/odata-csdl-json/odata-csdl-json.md index c86850343..40502e256 100644 --- a/docs/odata-csdl-json/odata-csdl-json.md +++ b/docs/odata-csdl-json/odata-csdl-json.md @@ -4778,7 +4778,8 @@ Example 73: "S" ] ] -} ``` +} +``` ::: @@ -5814,7 +5815,8 @@ Example 91: } } } -} ``` +} +``` ::: diff --git a/docs/odata-protocol/odata-protocol.html b/docs/odata-protocol/odata-protocol.html index b9442c6c4..d560641ad 100644 --- a/docs/odata-protocol/odata-protocol.html +++ b/docs/odata-protocol/odata-protocol.html @@ -991,8 +991,8 @@

    10.4 Singleton<

    If a response or response part is a singleton, its name is the context URL fragment.

    Example 15: resource URL and corresponding context URL

    -
    http://host/service/MainSupplier`
-http://host/service/$metadata#`MainSupplier
    +
    http://host/service/MainSupplier
+http://host/service/$metadata#MainSupplier

    10.5 Collection of Derived Entities

    Context URL template:

    @@ -1009,7 +1009,7 @@

    10.6 D

    If a response or response part is a single entity of a type derived from the declared type of an entity set, a type-cast segment is appended to the entity set name.

    Example 17: resource URL and corresponding context URL

    -
    http://host/service/Customers(2)/Model.VipCustomer`
+
    http://host/service/Customers(2)/Model.VipCustomer
 http://host/service/$metadata#Customers/Model.VipCustomer/$entity

    10.7 Collection of Projected Entities

    @@ -1024,7 +1024,7 @@

    $select.

    Example 18: resource URL and corresponding context URL

    -
    http://host/service/Customers?$`select`=Address,Orders
+
    http://host/service/Customers?$select=Address,Orders
 http://host/service/$metadata#Customers(Address,Orders)

    10.8 Projected Entity

    @@ -1135,7 +1135,7 @@

    Context URL templates:

    {context-url}#{entity-set}{/type-name}{select-list}
 {context-url}#{entity-set}{/type-name}{select-list}/$entity
-{context-url}#{entity}/{property-path}`{select-list}
+{context-url}#{entity}/{property-path}{select-list}
 {context-url}#Collection({type-name}){select-list}
 {context-url}#{type-name}{select-list}

    If the response from an action or function is a collection of entities or a single entity that is a member of an entity set, the context URL identifies the entity set. If the response from an action or function is a property of a single entity, the context URL identifies the entity and property. Otherwise, the context URL identifies the type returned by the operation. The context URL will correspond to one of the former examples.

    @@ -1154,7 +1154,7 @@

    Example 30: resource URL and corresponding context URL

    -
    http://host/service/Customers`?$deltatoken=1234
+
    http://host/service/Customers?$deltatoken=1234
 http://host/service/$metadata#Customers/$delta
    
 
 
    The context URL of an update request body for a collection of entities is simply the fragment #$delta.
    
@@ -2187,7 +2187,7 @@ 
    
 
    Example 98: invoke the SampleEntities.CreateOrder action using Customers('ALFKI') as the customer (or binding parameter). The values 2 for the quantity parameter and BLACKFRIDAY for the discountCode parameter are passed in the body of the request. Invoke the action only if the customer’s ETag still matches.
    
 
    POST http://host/service/Customers('ALFKI')/SampleEntities.CreateOrder
-If-Match: W/"MjAxOS0wMy0yMVQxMzowNVo="`
+If-Match: W/"MjAxOS0wMy0yMVQxMzowNVo="
 Content-Type: application/json
 
 {
@@ -2222,7 +2222,7 @@ 
    multipart batch format MUST contain a Content-Type header specifying a content type of multipart/mixed and a boundary parameter as defined in RFC2046.
    
 
    
 
    Example 99: multipart batch request
    
-
    POST /service/$batch HTTP/1.1`
+
    POST /service/$batch HTTP/1.1
 Host: odata.org
 OData-Version: 4.0
 Content-Type: multipart/mixed; boundary=batch_36522ad7-fc75-4b56-8c71-56071383e77b
@@ -2274,7 +2274,7 @@ 
    
 
    
 
    Example 101:
    
-
    GET https://host:1234/path/service/People(1) HTTP/1.1 ```
    
+
    GET https://host:1234/path/service/People(1) HTTP/1.1