Minor changes to clarify that @type coercion applies to strings.
--- a/spec/latest/json-ld/index.html Tue Aug 13 17:19:38 2013 -0400
+++ b/spec/latest/json-ld/index.html Tue Aug 13 17:32:54 2013 -0400
@@ -568,11 +568,11 @@
"name": "http://schema.org/name", **** ← This means that 'name' is shorthand for 'http://schema.org/name' ****
"image": {
"@id": "http://schema.org/image", **** ← This means that 'image' is shorthand for 'http://schema.org/image' ****
- "@type": "@id" **** ← This means that the value associated with 'image' should be interpreted as an identifier that is an IRI ****
+ "@type": "@id" **** ← This means that a string value associated with 'image' should be interpreted as an identifier that is an IRI ****
},
"homepage": {
"@id": "http://schema.org/url", **** ← This means that 'homepage' is shorthand for 'http://schema.org/url' ****
- "@type": "@id" **** ← This means that the value associated with 'homepage' should be interpreted as an identifier that is an IRI ****
+ "@type": "@id" **** ← This means that a string value associated with 'homepage' should be interpreted as an identifier that is an IRI ****
}
}****
}
@@ -585,7 +585,8 @@
<p>When a <tref>JSON object</tref> is associated with a term, it is called
an <tdef>expanded term definition</tdef>. The example above specifies that
- the values of <code>image</code> and <code>homepage</code> terms are
+ the values of <code>image</code> and <code>homepage</code>, if they are
+ strings, are to be interpreted as
<tref title="IRI">IRIs</tref>. <tref title="expanded term definition">Expanded term definitions</tref>
also allow terms to be used for <a href="#data-indexing">index maps</a>
and to specify whether <tref title="array">array</tref> values are to be
@@ -615,8 +616,9 @@
</pre>
<p>The referenced context not only specifies how the terms map to
- <tref title="IRI">IRIs</tref> in the Schema.org vocabulary but also specifies that
- the values of the <code>homepage</code> and <code>image</code> property
+ <tref title="IRI">IRIs</tref> in the Schema.org vocabulary but also
+ specifies that string values associated with
+ the <code>homepage</code> and <code>image</code> property
can be interpreted as an <tref>IRI</tref> (<code>"@type": "@id"</code>,
see <a class="sectionRef" href="#iris"></a> for more details). This information allows developers
to re-use each other's data without having to agree to how their data will interoperate