Skip to content

Commit

Permalink
Example title fine-tuned in Syntax spec
Browse files Browse the repository at this point in the history
  • Loading branch information
François Daoust committed Nov 17, 2012
1 parent 80c3343 commit dc1f63f
Showing 1 changed file with 6 additions and 7 deletions.
13 changes: 6 additions & 7 deletions spec/latest/json-ld-syntax/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -585,13 +585,13 @@ <h2>The Context</h2>
<!--
[
{
"@context": "http://example.org/contexts/person.jsonld",
****"@context": "http://example.org/contexts/person.jsonld",****
"name": "Manu Sporny",
"homepage": "http://manu.sporny.org/",
"depiction": "http://twitter.com/account/profile_image/manusporny"
},
{
"@context": "http://example.org/contexts/place.jsonld",
****"@context": "http://example.org/contexts/place.jsonld",****
"name": "The Empire State Building",
"description": "The Empire State Building is a 102-story landmark in New York City.",
"geo": {
Expand All @@ -603,9 +603,7 @@ <h2>The Context</h2>
-->
</pre>

<p>A <tref>node definition</tref> may specify multiple contexts, using an
<tref>array</tref>, processed in order.
This is useful when an author would like to use an existing context
<p>This is useful when an author would like to use an existing context
and add application-specific terms to the existing context. Duplicate context
<tref title="term">terms</tref> are overridden using a last-defined-overrides
mechanism.</p>
Expand Down Expand Up @@ -642,7 +640,8 @@ <h2>The Context</h2>
the <tref>term</tref> is effectively removed from the list of
<tref title="term">terms</tref> defined in the <tref>active context</tref>.</p>

<p>The set of contexts defined within a specific <tref>node definition</tref> are
<p>A <tref>node definition</tref> may specify multiple contexts, using an
<tref>array</tref>, processed in order. The set of contexts defined within a specific <tref>node definition</tref> are
referred to as <tdef title="local context">local contexts</tdef>. Setting the context to <code>null</code>
effectively resets the <tref>active context</tref> to an empty context. The
<tdef>active context</tdef> refers to the accumulation of <tref title="local context">local contexts</tref>
Expand Down Expand Up @@ -2281,7 +2280,7 @@ <h2>Named Graphs</h2>
is not desirable to the application. For example:</p>

<pre class="example" data-transform="updateExample"
title="Multiple node definitions with a single context using @graph">
title="Using @graph to explicitly express the default graph">
<!--
{
"@context": ...,
Expand Down

0 comments on commit dc1f63f

Please sign in to comment.