-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
c4731ef
commit f58125b
Showing
5 changed files
with
5 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2555,7 +2555,7 @@ <h4 id="14411-path-syntax"><a name="PathSyntax" href="#PathSyntax">14.4.1.1 Path | |
</div> | ||
<p>A model path MAY contain path segments starting with a navigation property, then followed by an at (<code>@</code>) character, then followed by the <a href="#QualifiedName">qualified name</a> of a term in scope, and optionally followed by a hash (<code>#</code>) character and a <a href="#SimpleIdentifier">simple identifier</a> which is interpreted as a <a href="#Qualifier">qualifier</a> for the term. If the navigation property has not been annotated with that term (and if present, with that qualifier), the path segment evaluates to the null value. This allows addressing annotations on the navigation property itself; annotations on the entity type specified by the navigation property are addressed via a <a href="#TermCast">term-cast segment</a>.</p> | ||
<div class="example"> | ||
<p>Example 64: model path addressing an annotation on a navigation property vs. term cast addressing an annotation on the resource addressed by the navigation property</p> | ||
<p>Example 64: model path segment addressing an annotation on a navigation property vs. term cast addressing an annotation on the resource addressed by the navigation property</p> | ||
<pre><code>.../[email protected]</code></pre> | ||
<pre><code>.../Items/@Core.Description</code></pre> | ||
</div> | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4271,7 +4271,7 @@ type specified by the navigation property are addressed via a [term-cast | |
segment](#TermCast). | ||
|
||
::: example | ||
Example 64: model path addressing an annotation on a navigation property | ||
Example 64: model path segment addressing an annotation on a navigation property | ||
vs. term cast addressing an annotation on the resource addressed by the navigation property | ||
``` | ||
.../[email protected] | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2436,7 +2436,7 @@ <h4 id="14411-path-syntax"><a name="PathSyntax" href="#PathSyntax">14.4.1.1 Path | |
</div> | ||
<p>A model path MAY contain path segments starting with a navigation property, then followed by an at (<code>@</code>) character, then followed by the <a href="#QualifiedName">qualified name</a> of a term in scope, and optionally followed by a hash (<code>#</code>) character and a <a href="#SimpleIdentifier">simple identifier</a> which is interpreted as a <a href="#Qualifier">qualifier</a> for the term. If the navigation property has not been annotated with that term (and if present, with that qualifier), the path segment evaluates to the null value. This allows addressing annotations on the navigation property itself; annotations on the entity type specified by the navigation property are addressed via a <a href="#TermCast">term-cast segment</a>.</p> | ||
<div class="example"> | ||
<p>Example 64: model path addressing an annotation on a navigation property vs. term cast addressing an annotation on the resource addressed by the navigation property</p> | ||
<p>Example 64: model path segment addressing an annotation on a navigation property vs. term cast addressing an annotation on the resource addressed by the navigation property</p> | ||
<pre><code>.../[email protected]</code></pre> | ||
<pre><code>.../Items/@Core.Description</code></pre> | ||
</div> | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4191,7 +4191,7 @@ type specified by the navigation property are addressed via a [term-cast | |
segment](#TermCast). | ||
|
||
::: example | ||
Example 64: model path addressing an annotation on a navigation property | ||
Example 64: model path segment addressing an annotation on a navigation property | ||
vs. term cast addressing an annotation on the resource addressed by the navigation property | ||
``` | ||
.../[email protected] | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1351,7 +1351,7 @@ type specified by the navigation property are addressed via a [term-cast | |
segment](#TermCast). | ||
|
||
::: example | ||
Example ##ex: model path addressing an annotation on a navigation property | ||
Example ##ex: model path segment addressing an annotation on a navigation property | ||
vs. term cast addressing an annotation on the resource addressed by the navigation property | ||
``` | ||
.../[email protected] | ||
|