Revert "TC 2024-10-23"

This reverts commit 8a58657.

docs/odata-protocol/odata-protocol.html

@@ -1424,7 +1424,7 @@ <h2 id="108-projected-entity"><a id="ProjectedEntity" href="#ProjectedEntity">10
 <pre><code>{context-url}#{entity-set}{/type-name}{select-list}/$entity
 {context-url}#{singleton}{select-list}
 {context-url}#{type-name}{select-list}</code></pre>
-<p>If a single entity contains a subset of properties, the parenthesized comma-separated list of the selected defined or dynamic properties, instance annotations, navigation properties, functions, and actions is appended to the <code>{entity-set}</code> after an optional type-cast segment and prior to appending <code>/$entity</code>. If the entity is not bound to an entity set, the <code>{select-list}</code> is instead appended to the <code>{type-name}</code> of the returned entity.</p>
+<p>If a single entity contains a subset of properties, the parenthesized comma-separated list of the selected defined or dynamic properties, instance annotations, navigation properties, functions, and actions is appended to the <code>{entity-set}</code> after an optional type-cast segment and prior to appending <code>/$entity</code>. If the response is not a subset of a single entity set, the <code>{select-list}</code> is instead appended to the <code>{type-name}</code> of the returned entity.</p>
 <p>Regardless of how contained structural properties are represented in the request URL (as paths or as select options) they are represented in the context URL using path syntax, as defined in OData 4.0.</p>
 <p>The shortcut <code>*</code> represents the list of all structural properties. Properties defined on types derived from the type of the entity set (or type specified in the type-cast segment if specified) are prefixed with the qualified name of the derived type as defined in <a href="#ODataABNF">OData-ABNF</a>. Note that expanded properties are automatically included in the response.</p>
 <p>The list also contains explicitly selected or expanded instance annotations. It is possible to select or expand only instance annotations, in which case only those selected or expanded annotations appear in the result. Note that annotations specified only in the <a href="#Preferenceincludeannotationsodataincludeannotations"><code>include-annotations</code></a> preference do not appear in the context URL and do not affect the selected/expanded properties.</p>

docs/odata-protocol/odata-protocol.md

@@ -2226,8 +2226,8 @@ If a single entity contains a subset of properties, the parenthesized
 comma-separated list of the selected defined or dynamic properties,
 instance annotations, navigation properties, functions, and actions is
 appended to the `{entity-set}` after an optional type-cast segment and
-prior to appending `/$entity`. If the entity is not bound to an
-entity set, the `{select-list}` is instead appended to the
+prior to appending `/$entity`. If the response is not a subset of a
+single entity set, the `{select-list}` is instead appended to the
 `{type-name}` of the returned entity.
 
 Regardless of how contained structural properties are represented in the

odata-protocol/10 Context URL.md

@@ -249,8 +249,8 @@ If a single entity contains a subset of properties, the parenthesized
 comma-separated list of the selected defined or dynamic properties,
 instance annotations, navigation properties, functions, and actions is
 appended to the `{entity-set}` after an optional type-cast segment and
-prior to appending `/$entity`. If the entity is not bound to an
-entity set, the `{select-list}` is instead appended to the
+prior to appending `/$entity`. If the response is not a subset of a
+single entity set, the `{select-list}` is instead appended to the
 `{type-name}` of the returned entity.
 
 Regardless of how contained structural properties are represented in the