From bb19fa303df3a06a68ebc0d4fd9c35819f8b9c89 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Heiko=20Thei=C3=9Fen?= Date: Wed, 28 Aug 2024 10:16:56 +0200 Subject: [PATCH] =?UTF-8?q?Avoid=20use=20of=20=E2=80=B2=20in=20Markdown=20?= =?UTF-8?q?files?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/odata-protocol/odata-protocol.html | 6 +++--- docs/odata-protocol/odata-protocol.md | 12 ++++++------ .../odata-url-conventions/odata-url-conventions.html | 2 +- docs/odata-url-conventions/odata-url-conventions.md | 2 +- odata-protocol/11.5 Operations.md | 4 ++-- odata-protocol/11.7 Batch Requests.md | 8 ++++---- odata-url-conventions/5 Query Options.md | 2 +- 7 files changed, 18 insertions(+), 18 deletions(-) diff --git a/docs/odata-protocol/odata-protocol.html b/docs/odata-protocol/odata-protocol.html index b904957a..456f479b 100644 --- a/docs/odata-protocol/odata-protocol.html +++ b/docs/odata-protocol/odata-protocol.html @@ -2807,7 +2807,7 @@

format.

-

Example 91: given a GET request to http://host/service/Customers(′ALFKI′), the service might respond with a Customer that includes the SampleEntities.MostRecentOrder function bound to the entity

+

Example 91: given a GET request to http://host/service/Customers('ALFKI'), the service might respond with a Customer that includes the SampleEntities.MostRecentOrder function bound to the entity

{
   "@context": …,
   "CustomerID": "ALFKI",
@@ -2919,7 +2919,7 @@ 
204 No Content on success.

 
To request processing of the action only if the binding parameter value, an entity or collection of entities, is unmodified, the client includes the If-Match header with the latest known ETag value for the entity or collection of entities. The ETag value for a collection as a whole is transported in the ETag header of a collection response.

 

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

+
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="
 Content-Type: application/json
@@ -3197,7 +3197,7 @@ 
example 102). This gives the effective second request URL http://host/service/Customers(′ALFKI′)/Orders as base URI for the second Location URL, which therefore resolves to http://host/service/Customers(′ALFKI′)/Orders(1).

+
The second Location URL Orders(1) is relative with its base URI being the second request URL $1/Orders. To get an absolute base URI, the client must replace the $1 with the first Location URL Customers('ALFKI') and resolve the resulting URL Customers('ALFKI')/Orders(1) relative to its base URI, which is http://host/service/Customers (determined from the first request URL /service/Customers and the Host: host header as in example 102). This gives the effective second request URL http://host/service/Customers('ALFKI')/Orders as base URI for the second Location URL, which therefore resolves to http://host/service/Customers('ALFKI')/Orders(1).

 

 
 

diff --git a/docs/odata-protocol/odata-protocol.md b/docs/odata-protocol/odata-protocol.md
index 9dc3a0d9..8ac825c9 100644
--- a/docs/odata-protocol/odata-protocol.md
+++ b/docs/odata-protocol/odata-protocol.md
@@ -5372,7 +5372,7 @@ or function depends on the [format](#Formats).
 
 ::: example
 Example 91: given a `GET` request to
-`http://host/service/Customers(′ALFKI′)`, the service might respond with
+`http://host/service/Customers('ALFKI')`, the service might respond with
 a Customer that includes the `SampleEntities.MostRecentOrder` function
 bound to the entity
 ```json
@@ -5714,7 +5714,7 @@ collection response.
 
 ::: example
 Example 98: invoke the `SampleEntities.CreateOrder` action using
-`Customers(′ALFKI′)` as the customer (or binding parameter). The values
+`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.
@@ -6225,13 +6225,13 @@ Location: Orders(1)
 ```
 The second `Location` URL `Orders(1)` is relative with its base URI being the second
 request URL `$1/Orders`. To get an absolute base URI, the client must replace the
-`$1` with the first `Location` URL `Customers(′ALFKI′)` and resolve the
-resulting URL `Customers(′ALFKI′)/Orders(1)` relative to its base URI, which is
+`$1` with the first `Location` URL `Customers('ALFKI')` and resolve the
+resulting URL `Customers('ALFKI')/Orders(1)` relative to its base URI, which is
 `http://host/service/Customers` (determined from the
 first request URL `/service/Customers` and the `Host: host` header
 as in [example 102](#batchhost)). This gives the effective second request URL
-`http://host/service/Customers(′ALFKI′)/Orders` as base URI for the second `Location`
-URL, which therefore resolves to `http://host/service/Customers(′ALFKI′)/Orders(1)`.
+`http://host/service/Customers('ALFKI')/Orders` as base URI for the second `Location`
+URL, which therefore resolves to `http://host/service/Customers('ALFKI')/Orders(1)`.
 :::
 
 #### 11.7.7.3 Referencing an ETag
diff --git a/docs/odata-url-conventions/odata-url-conventions.html b/docs/odata-url-conventions/odata-url-conventions.html
index a47f31b8..873a9cc5 100644
--- a/docs/odata-url-conventions/odata-url-conventions.html
+++ b/docs/odata-url-conventions/odata-url-conventions.html
@@ -2420,7 +2420,7 @@ 
.

+
To support type-ahead use cases, incomplete search expressions can be sent as OData string literals enclosed in single-quotes, and single-quotes within the search expression doubled. Such an expression can also be used to search for double quotes: ?$search='"'.

 
The OData-ABNF searchExpr syntax rule defines the formal grammar of the search expression.

 

 
diff --git a/docs/odata-url-conventions/odata-url-conventions.md b/docs/odata-url-conventions/odata-url-conventions.md
index 17ed4b45..948e6b87 100644
--- a/docs/odata-url-conventions/odata-url-conventions.md
+++ b/docs/odata-url-conventions/odata-url-conventions.md
@@ -4042,7 +4042,7 @@ expressions evaluate to `true`, otherwise `false`.
 To support type-ahead use cases, incomplete search expressions can be
 sent as OData string literals enclosed in single-quotes, and
 single-quotes within the search expression doubled.
-Such an expression can also be used to search for double quotes: `?$search=′"′`.
+Such an expression can also be used to search for double quotes: `?$search='"'`.
 
 The [OData-ABNF](#ODataABNF) `searchExpr` syntax rule defines the formal
 grammar of the search expression.
diff --git a/odata-protocol/11.5 Operations.md b/odata-protocol/11.5 Operations.md
index 72d9774b..bdbe5b77 100644
--- a/odata-protocol/11.5 Operations.md	
+++ b/odata-protocol/11.5 Operations.md	
@@ -103,7 +103,7 @@ or function depends on the [format](#Formats).
 
 ::: example
 Example ##ex: given a `GET` request to
-`http://host/service/Customers(′ALFKI′)`, the service might respond with
+`http://host/service/Customers('ALFKI')`, the service might respond with
 a Customer that includes the `SampleEntities.MostRecentOrder` function
 bound to the entity
 ```json
@@ -445,7 +445,7 @@ collection response.
 
 ::: example
 Example ##ex: invoke the `SampleEntities.CreateOrder` action using
-`Customers(′ALFKI′)` as the customer (or binding parameter). The values
+`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.
diff --git a/odata-protocol/11.7 Batch Requests.md b/odata-protocol/11.7 Batch Requests.md
index 7b2d3897..9675b2f8 100644
--- a/odata-protocol/11.7 Batch Requests.md	
+++ b/odata-protocol/11.7 Batch Requests.md	
@@ -404,13 +404,13 @@ Location: Orders(1)
 ```
 The second `Location` URL `Orders(1)` is relative with its base URI being the second
 request URL `$1/Orders`. To get an absolute base URI, the client must replace the
-`$1` with the first `Location` URL `Customers(′ALFKI′)` and resolve the
-resulting URL `Customers(′ALFKI′)/Orders(1)` relative to its base URI, which is
+`$1` with the first `Location` URL `Customers('ALFKI')` and resolve the
+resulting URL `Customers('ALFKI')/Orders(1)` relative to its base URI, which is
 `http://host/service/Customers` (determined from the
 first request URL `/service/Customers` and the `Host: host` header
 as in [example ##batchhost]). This gives the effective second request URL
-`http://host/service/Customers(′ALFKI′)/Orders` as base URI for the second `Location`
-URL, which therefore resolves to `http://host/service/Customers(′ALFKI′)/Orders(1)`.
+`http://host/service/Customers('ALFKI')/Orders` as base URI for the second `Location`
+URL, which therefore resolves to `http://host/service/Customers('ALFKI')/Orders(1)`.
 :::
 
 #### ##subsubsubsec Referencing an ETag
diff --git a/odata-url-conventions/5 Query Options.md b/odata-url-conventions/5 Query Options.md
index 2be14399..66e3b5e5 100644
--- a/odata-url-conventions/5 Query Options.md	
+++ b/odata-url-conventions/5 Query Options.md	
@@ -2469,7 +2469,7 @@ expressions evaluate to `true`, otherwise `false`.
 To support type-ahead use cases, incomplete search expressions can be
 sent as OData string literals enclosed in single-quotes, and
 single-quotes within the search expression doubled.
-Such an expression can also be used to search for double quotes: `?$search=′"′`.
+Such an expression can also be used to search for double quotes: `?$search='"'`.
 
 The [OData-ABNF](#ODataABNF) `searchExpr` syntax rule defines the formal
 grammar of the search expression.