George's proposal

docs/odata-protocol/odata-protocol.html

@@ -590,7 +590,7 @@ <h2 id="42-read-urls-and-edit-urls"><a name="ReadURLsandEditURLs" href="#ReadURL
 <p>The edit URL of a property is the edit URL of the entity with appended segment(s) containing the path to the property.</p>
 <p>Services are strongly encouraged to use the canonical URL for an entity as defined in <strong>OData-URL</strong> for both the read URL and the edit URL of an entity, with a cast segment to the type of the entity appended to the canonical URL if the type of the entity is derived from the declared type of the entity set. However, clients cannot assume this convention and must use the links specified in the payload according to the appropriate format as the two URLs may be different from one another, or one or both of them may differ from convention.</p>
 <h2 id="43-transient-entities"><a name="TransientEntities" href="#TransientEntities">4.3 Transient Entities</a></h2>
-<p>Transient entities are instances of an entity type that are “calculated on the fly” and only exist within a single payload. They cannot be reread or updated and consequently possess neither a stable entity-id nor a read URL or an update URL.</p>
+<p>Transient entities are derived from instances of an entity type that are “calculated on the fly” and only exist within a single payload. They cannot be updated and consequently possess neither a stable entity-id nor an update URL. A transient entity may have a read URL, which may be used to re-derive the transient entity from the current state of the underlying entity.</p>
 <h2 id="44-default-namespaces"><a name="DefaultNamespaces" href="#DefaultNamespaces">4.4 Default Namespaces</a></h2>
 <p>References to actions, functions, and types within a URL typically requires prefixing the name of the action, function, or type with the namespace or alias in which it is defined. This namespace qualification enables differentiating between similarly named elements across schema, or between properties and bound functions, actions, or types with the same name.</p>
 <p>Services MAY define one or more default namespaces through the <a href="https://github.com/oasis-tcs/odata-vocabularies/blob/master/vocabularies/Org.OData.Core.V1.md#DefaultNamespace"><code>Core.DefaultNamespace</code></a> term defined in <a href="#ODataVocCore">OData-VocCore</a>. Functions, actions and types in a default namespace can be referenced in URLs with or without namespace or alias qualification.</p>

docs/odata-protocol/odata-protocol.md

@@ -605,10 +605,12 @@ one or both of them may differ from convention.
 
 ## <a name="TransientEntities" href="#TransientEntities">4.3 Transient Entities</a>
 
-Transient entities are instances of an entity type that are "calculated
+Transient entities are derived from instances of an entity type that are "calculated
 on the fly" and only exist within a single payload. They cannot be
-reread or updated and consequently possess neither a stable entity-id
-nor a read URL or an update URL.
+updated and consequently possess neither a stable entity-id
+nor an update URL.
+A transient entity may have a read URL, which may be used to re-derive
+the transient entity from the current state of the underlying entity.
 
 ## <a name="DefaultNamespaces" href="#DefaultNamespaces">4.4 Default Namespaces</a>
 

odata-protocol/1 Introduction.md

@@ -287,10 +287,12 @@ one or both of them may differ from convention.
 
 ## ##subsec Transient Entities
 
-Transient entities are instances of an entity type that are "calculated
+Transient entities are derived from instances of an entity type that are "calculated
 on the fly" and only exist within a single payload. They cannot be
-reread or updated and consequently possess neither a stable entity-id
-nor a read URL or an update URL.
+updated and consequently possess neither a stable entity-id
+nor an update URL.
+A transient entity may have a read URL, which may be used to re-derive
+the transient entity from the current state of the underlying entity.
 
 ## ##subsec Default Namespaces