json-ld: changeset 767:b53e28df4bfd

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/spec/WD/json-ld-api/20120712/diff-20120626.html	Tue Jun 26 23:49:05 2012 -0400
@@ -0,0 +1,17001 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.1//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd">
+<html dir="ltr" xmlns="http://www.w3.org/1999/xhtml" typeof="bibo:Document">
+<head>
+<title>JSON-LD API 1.0</title>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+
+<!-- 
+  === NOTA BENE ===
+  For the three scripts below, if your spec resides on dev.w3 you can check them
+  out in the same tree and use relative links so that they'll work offline,
+   -->
+
+
+
+<style type="text/css">
+.diff { font-weight:bold; color:#0a3; }
+</style>
+<style type="text/css">/*****************************************************************
+ * ReSpec 3 CSS
+ * Robin Berjon - http://berjon.com/
+ *****************************************************************/
+
+/* --- INLINES --- */
+em.rfc2119 { 
+    text-transform:     lowercase;
+    font-variant:       small-caps;
+    font-style:         normal;
+    color:              #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+    border: none;
+}
+
+dfn {
+    font-weight:    bold;
+}
+
+a.internalDFN {
+    color:  inherit;
+    border-bottom:  1px solid #99c;
+    text-decoration:    none;
+}
+
+a.externalDFN {
+    color:  inherit;
+    border-bottom:  1px dotted #ccc;
+    text-decoration:    none;
+}
+
+a.bibref {
+    text-decoration:    none;
+}
+
+cite .bibref {
+    font-style: normal;
+}
+
+code {
+    color:  #ff4500;
+}
+
+
+/* --- --- */
+ol.algorithm { counter-reset:numsection; list-style-type: none; }
+ol.algorithm li { margin: 0.5em 0; }
+ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }
+
+
+/* --- WEB IDL --- */
+pre.idl {
+    border-top: 1px solid #90b8de;
+    border-bottom: 1px solid #90b8de;
+    padding:    1em;
+    line-height:    120%;
+}
+
+pre.idl::before {
+    content:    "WebIDL";
+    display:    block;
+    width:      150px;
+    background: #90b8de;
+    color:  #fff;
+    font-family:    initial;
+    padding:    3px;
+    font-weight:    bold;
+    margin: -1em 0 1em -1em;
+}
+
+.idlType {
+    color:  #ff4500;
+    font-weight:    bold;
+    text-decoration:    none;
+}
+
+/*.idlModule*/
+/*.idlModuleID*/
+/*.idlInterface*/
+.idlInterfaceID, .idlDictionaryID, .idlCallbackID, .idlEnumID {
+    font-weight:    bold;
+    color:  #005a9c;
+}
+
+.idlSuperclass {
+    font-style: italic;
+    color:  #005a9c;
+}
+
+/*.idlAttribute*/
+.idlAttrType, .idlFieldType, .idlMemberType {
+    color:  #005a9c;
+}
+.idlAttrName, .idlFieldName, .idlMemberName {
+    color:  #ff4500;
+}
+.idlAttrName a, .idlFieldName a, .idlMemberName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlMethod*/
+.idlMethType, .idlCallbackType {
+    color:  #005a9c;
+}
+.idlMethName {
+    color:  #ff4500;
+}
+.idlMethName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlParam*/
+.idlParamType {
+    color:  #005a9c;
+}
+.idlParamName {
+    font-style: italic;
+}
+
+.extAttr {
+    color:  #666;
+}
+
+/*.idlConst*/
+.idlConstType {
+    color:  #005a9c;
+}
+.idlConstName {
+    color:  #ff4500;
+}
+.idlConstName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlException*/
+.idlExceptionID {
+    font-weight:    bold;
+    color:  #c00;
+}
+
+.idlTypedefID, .idlTypedefType {
+    color:  #005a9c;
+}
+
+.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
+    color:  #c00;
+    font-weight:    normal;
+}
+
+.excName a {
+    font-family:    monospace;
+}
+
+.idlRaises a.idlType, .excName a.idlType {
+    border-bottom:  1px dotted #c00;
+}
+
+.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
+    width:  45px;
+    text-align: center;
+}
+.excGetSetTrue, .prmNullTrue, .prmOptTrue { color:  #0c0; }
+.excGetSetFalse, .prmNullFalse, .prmOptFalse { color:  #c00; }
+
+.idlImplements a {
+    font-weight:    bold;
+}
+
+dl.attributes, dl.methods, dl.constants, dl.fields, dl.dictionary-members {
+    margin-left:    2em;
+}
+
+.attributes dt, .methods dt, .constants dt, .fields dt, .dictionary-members dt {
+    font-weight:    normal;
+}
+
+.attributes dt code, .methods dt code, .constants dt code, .fields dt code, .dictionary-members dt code {
+    font-weight:    bold;
+    color:  #000;
+    font-family:    monospace;
+}
+
+.attributes dt code, .fields dt code, .dictionary-members dt code {
+    background:  #ffffd2;
+}
+
+.attributes dt .idlAttrType code, .fields dt .idlFieldType code, .dictionary-members dt .idlMemberType code {
+    color:  #005a9c;
+    background:  transparent;
+    font-family:    inherit;
+    font-weight:    normal;
+    font-style: italic;
+}
+
+.methods dt code {
+    background:  #d9e6f8;
+}
+
+.constants dt code {
+    background:  #ddffd2;
+}
+
+.attributes dd, .methods dd, .constants dd, .fields dd, .dictionary-members dd {
+    margin-bottom:  1em;
+}
+
+table.parameters, table.exceptions {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    margin: 0.5em 0;
+    width:  100%;
+}
+table.parameters { border-bottom:  1px solid #90b8de; }
+table.exceptions { border-bottom:  1px solid #deb890; }
+
+.parameters th, .exceptions th {
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+    font-family:    initial;
+    font-weight:    normal;
+    text-shadow:    #666 1px 1px 0;
+}
+.parameters th { background: #90b8de; }
+.exceptions th { background: #deb890; }
+
+.parameters td, .exceptions td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+    vertical-align: top;
+}
+
+.parameters tr:first-child td, .exceptions tr:first-child td {
+    border-top: none;
+}
+
+.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
+    width:  100px;
+}
+
+.parameters td.prmType {
+    width:  120px;
+}
+
+table.exceptions table {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    width:  100%;
+}
+
+/* --- TOC --- */
+.toc a, .tof a {
+    text-decoration:    none;
+}
+
+a .secno, a .figno {
+    color:  #000;
+}
+
+ul.tof, ol.tof {
+    list-style: none outside none;
+}
+
+.caption {
+    margin-top: 0.5em;
+    font-style:   italic;
+}
+
+/* --- TABLE --- */
+table.simple {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    border-bottom:  3px solid #005a9c;
+}
+
+.simple th {
+    background: #005a9c;
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+}
+
+.simple th[scope="row"] {
+    background: inherit;
+    color:  inherit;
+    border-top: 1px solid #ddd;
+}
+
+.simple td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+    background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+    margin-top: 0;
+}
+
+.section dd > p:last-child {
+    margin-bottom: 0;
+}
+
+.section dd {
+    margin-bottom:  1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+    margin-bottom:  0;
+}
+</style><style type="text/css">/* --- EXAMPLES --- */
+div.example-title {
+    min-width: 7.5em;
+    color: #b9ab2d;
+}
+div.example-title span {
+    text-transform: uppercase;   
+}
+div.example, div.illegal-example {
+    padding: 0.5em;
+    margin: 1em 0;
+    position: relative;
+    clear: both;
+}
+div.illegal-example { color: red }
+div.illegal-example p { color: black }
+div.example {
+    padding: .5em;
+    border-left-width: .5em;
+    border-left-style: solid;
+    border-color: #e0cb52;
+    background: #fcfaee;    
+}
+</style><style type="text/css">/* --- ISSUES/NOTES --- */
+div.issue-title, div.note-title {
+    padding-right:  1em;
+    min-width: 7.5em;
+    color: #b9ab2d;
+}
+div.issue-title { color: #e05252; }
+div.note-title { color: #52e052; }
+div.issue-title span, div.note-title span {
+    text-transform: uppercase;
+}
+div.note, div.issue {
+    margin-top: 1em;
+    margin-bottom: 1em;
+}
+.note > p:first-child, .issue > p:first-child { margin-top: 0 }
+.issue, .note {
+    padding: .5em;
+    border-left-width: .5em;
+    border-left-style: solid;
+}
+div.issue, div.note {
+    padding: 0.5em;
+    margin: 1em 0;
+    position: relative;
+    clear: both;
+}
+span.note, span.issue { padding: .1em .5em .15em; }
+
+.issue {
+    border-color: #e05252;
+    background: #fbe9e9;
+}
+.note {
+    border-color: #52e052;
+    background: #e9fbe9;
+}
+
+
+</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD" /><script type="text/javascript" src="http://s3.amazonaws.com/green-turtle/RDFa.0.15.0.js"></script><meta name="green-turtle-rdfa-message" content="{ &quot;type&quot;: &quot;status&quot;, &quot;loaded&quot;: true, &quot;count&quot;: 45 }" /><style type='text/css'>
+.diff-old-a {
+  font-size: smaller;
+  color: red;
+}
+
+.diff-new { background-color: yellow; }
+.diff-chg { background-color: lime; }
+.diff-new:before,
+.diff-new:after
+    { content: "\2191" }
+.diff-chg:before, .diff-chg:after
+    { content: "\2195" }
+.diff-old { text-decoration: line-through; background-color: #FBB; }
+.diff-old:before,
+.diff-old:after
+    { content: "\2193" }
+:focus { border: thin red solid}
+</style>
+</head>
+
+
+<body>
+<div class="head">
+<p>
+<a href="http://www.w3.org/">
+<img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C" />
+</a>
+</p>
+<h1 class="title" id="title">
+JSON-LD
+API
+1.0
+</h1>
+<h2 id="subtitle">
+An
+Application
+Programming
+Interface
+for
+the
+JSON-LD
+Syntax
+</h2>
+<del class="diff-old">Final
+Community
+Group
+Specification
+26
+June
+</del>
+<h2 id="w3c-working-draft-12-july-2012">
+<acronym title="World Wide Web Consortium">
+<ins class="diff-chg">W3C
+</ins></acronym><ins class="diff-chg">
+Working
+Draft
+12
+July
+</ins>
+2012
+</h2>
+<dl>
+<dt>
+<ins class="diff-new">This
+version:
+</ins></dt><dd><a href="http://www.w3.org/TR/2012/WD-json-ld-api-20120712/"><ins class="diff-new">
+http://www.w3.org/TR/2012/WD-json-ld-api-20120712/
+</ins></a></dd><dt><ins class="diff-new">
+Latest
+published
+version:
+</ins></dt><dd><a href="http://www.w3.org/TR/json-ld-api/"><ins class="diff-new">
+http://www.w3.org/TR/json-ld-api/
+</ins></a></dd><dt>
+Latest
+editor's
+draft:
+</dt>
+<dd>
+<del class="diff-old">http://json-ld.org/spec/latest/json-ld-api/
+</del>
+<a href="http://dvcs.w3.org/hg/json-ld/raw-file/default/spec/latest/json-ld-api/index.html">
+<ins class="diff-chg">http://dvcs.w3.org/hg/json-ld/raw-file/default/spec/latest/json-ld-api/index.html
+</ins>
+</a>
+</dd>
+<dt>
+Editors:
+</dt>
+<dd rel="bibo:editor" inlist="">
+<span typeof="foaf:Person">
+<a rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="http://manu.sporny.org/">
+Manu
+Sporny
+</a>,
+<a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">
+Digital
+Bazaar
+</a>
+</span>
+</dd>
+<dd rel="bibo:editor" inlist="">
+<span typeof="foaf:Person">
+<a rel="foaf:homepage" property="foaf:name" content="Gregg Kellogg" href="http://greggkellogg.net/">
+Gregg
+Kellogg
+</a>,
+<a rel="foaf:workplaceHomepage" href="http://kellogg-assoc.com/">
+Kellogg
+Associates
+</a>
+</span>
+</dd>
+<dd rel="bibo:editor" inlist="">
+<span typeof="foaf:Person">
+<a rel="foaf:homepage" property="foaf:name" content="Dave Longley" href="http://digitalbazaar.com/">
+Dave
+Longley
+</a>,
+<a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">
+Digital
+Bazaar
+</a>
+</span>
+</dd>
+<dd rel="bibo:editor" inlist="">
+<span typeof="foaf:Person">
+<a rel="foaf:homepage" property="foaf:name" content="Markus Lanthaler" href="http://www.markus-lanthaler.com/">
+Markus
+Lanthaler
+</a>,
+<a rel="foaf:workplaceHomepage" href="http://www.tugraz.at/">
+Graz
+University
+of
+Technology
+</a>
+</span>
+</dd>
+<dt>
+Authors:
+</dt>
+<dd rel="dcterms:contributor">
+<span typeof="foaf:Person">
+<a rel="foaf:homepage" property="foaf:name" content="Dave Longley" href="http://digitalbazaar.com/">
+Dave
+Longley
+</a>,
+<a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">
+Digital
+Bazaar
+</a>
+</span>
+</dd>
+<dd rel="dcterms:contributor">
+<span typeof="foaf:Person">
+<a rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="http://digitalbazaar.com/">
+Manu
+Sporny
+</a>,
+<a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">
+Digital
+Bazaar
+</a>
+</span>
+</dd>
+<dd rel="dcterms:contributor">
+<span typeof="foaf:Person">
+<a rel="foaf:homepage" property="foaf:name" content="Gregg Kellogg" href="http://greggkellogg.net/">
+Gregg
+Kellogg
+</a>,
+<a rel="foaf:workplaceHomepage" href="http://kellogg-assoc.com/">
+Kellogg
+Associates
+</a>
+</span>
+</dd>
+<dd rel="dcterms:contributor">
+<span typeof="foaf:Person">
+<a rel="foaf:homepage" property="foaf:name" content="Markus Lanthaler" href="http://www.markus-lanthaler.com/">
+Markus
+Lanthaler
+</a>,
+<a rel="foaf:workplaceHomepage" href="http://www.tugraz.at/">
+Graz
+University
+of
+Technology
+</a>
+</span>
+</dd>
+</dl>
+<p>
+This
+document
+is
+also
+available
+in
+this
+non-normative
+format:
+<a href="diff-20120626.html">
+diff
+to
+previous
+version
+</a>
+</p>
+<p class="copyright">
+<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">
+Copyright
+</a>
+©
+2010-2012
+<del class="diff-old">the
+Contributors
+to
+the
+JSON-LD
+API
+1.0
+Specification,
+published
+by
+the
+JSON
+for
+Linking
+Data
+Community
+Group
+</del>
+<a href="http://www.w3.org/">
+<acronym title="World Wide Web Consortium">
+<ins class="diff-chg">W3C
+</ins></acronym>
+</a>
+<del class="diff-old">under
+the
+</del>
+<sup>
+<ins class="diff-chg">®
+</ins></sup><ins class="diff-chg">
+(
+</ins><a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology"><ins class="diff-chg">
+MIT
+</ins></acronym></a>,<a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics"><ins class="diff-chg">
+ERCIM
+</ins></acronym></a>,<a href="http://www.keio.ac.jp/"><ins class="diff-chg">
+Keio
+</ins></a><ins class="diff-chg">
+),
+All
+Rights
+Reserved.
+</ins><acronym title="World Wide Web Consortium">
+W3C
+<del class="diff-old">Community
+Final
+Specification
+Agreement
+(FSA)
+.
+A
+human-readable
+summary
+</del>
+</acronym>
+<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">
+<ins class="diff-chg">liability
+</ins></a>,<a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks"><ins class="diff-chg">
+trademark
+</ins>
+</a>
+<del class="diff-old">is
+available.
+</del>
+<ins class="diff-chg">and
+</ins><a href="http://www.w3.org/Consortium/Legal/copyright-documents"><ins class="diff-chg">
+document
+use
+</ins></a><ins class="diff-chg">
+rules
+apply.
+</ins>
+</p>
+<hr />
+</div>
+<div id="abstract" class="introductory section">
+<h2>
+Abstract
+</h2>
+<p>
+JSON
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RFC4627">
+RFC4627
+</a>
+</cite>
+]
+has
+proven
+to
+be
+a
+highly
+useful
+object
+serialization
+and
+messaging
+format.
+JSON-LD
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-JSON-LD">
+JSON-LD
+</a>
+</cite>
+]
+harmonizes
+the
+representation
+of
+Linked
+Data
+in
+JSON
+by
+outlining
+a
+common
+JSON
+representation
+format
+for
+expressing
+directed
+graphs;
+mixing
+both
+Linked
+Data
+and
+non-Linked
+Data
+in
+a
+single
+document.
+This
+document
+outlines
+an
+Application
+Programming
+Interface
+and
+a
+set
+of
+algorithms
+for
+programmatically
+transforming
+JSON-LD
+documents
+in
+order
+to
+make
+them
+easier
+to
+work
+with
+in
+programming
+environments
+like
+JavaScript,
+Python,
+and
+Ruby.
+</p>
+</div>
+<div id="sotd" class="introductory section">
+<h2>
+Status
+of
+This
+Document
+</h2>
+<p>
+<em>
+This
+<del class="diff-old">specification
+was
+published
+by
+</del>
+<ins class="diff-chg">section
+describes
+</ins>
+the
+<del class="diff-old">JSON
+for
+Linking
+Data
+Community
+Group
+.
+It
+is
+not
+a
+W3C
+Standard
+nor
+is
+it
+on
+</del>
+<ins class="diff-chg">status
+of
+this
+document
+at
+</ins>
+the
+<ins class="diff-new">time
+of
+its
+publication.
+Other
+documents
+may
+supersede
+this
+document.
+A
+list
+of
+current
+</ins><acronym title="World Wide Web Consortium">
+W3C
+<del class="diff-old">Standards
+Track.
+Please
+note
+that
+under
+</del>
+</acronym>
+<ins class="diff-chg">publications
+and
+</ins>
+the
+<ins class="diff-chg">latest
+revision
+of
+this
+technical
+report
+can
+be
+found
+in
+the
+</ins><a href="http://www.w3.org/TR/"><acronym title="World Wide Web Consortium">
+W3C
+<del class="diff-old">Community
+Final
+Specification
+Agreement
+(FSA)
+</del>
+</acronym>
+<ins class="diff-chg">technical
+reports
+index
+</ins>
+</a>
+<del class="diff-old">other
+conditions
+apply.
+Learn
+more
+about
+W3C
+Community
+and
+Business
+Groups
+.
+</del>
+<ins class="diff-chg">at
+http://www.w3.org/TR/.
+</ins></em>
+</p>
+<p>
+This
+document
+has
+been
+under
+development
+for
+over
+18
+months
+in
+the
+JSON
+for
+Linking
+Data
+Community
+Group.
+The
+document
+has
+recently
+been
+<del class="diff-old">approved
+for
+transfer
+into
+</del>
+<ins class="diff-chg">transferred
+to
+</ins>
+the
+RDF
+Working
+Group
+for
+<del class="diff-old">review
+with
+the
+intent
+to
+publish
+the
+document
+</del>
+<ins class="diff-chg">review,
+improvement,
+and
+publication
+</ins>
+along
+the
+<del class="diff-old">W3C
+</del>
+Recommendation
+track.
+<del class="diff-old">This
+</del>
+<ins class="diff-chg">While
+this
+is
+a
+First
+Public
+Working
+Draft
+publication,
+the
+</ins>
+specification
+has
+undergone
+significant
+development,
+review,
+and
+changes
+during
+the
+course
+of
+the
+last
+18
+months
+and
+is
+<del class="diff-old">being
+published
+as
+a
+Final
+Community
+Group
+Specification
+so
+that
+it
+may
+gain
+wider
+review
+and
+feedback.
+</del>
+<ins class="diff-chg">more
+mature
+than
+the
+First
+Public
+Working
+Draft
+status
+implies.
+</ins>
+</p>
+<p>
+There
+are
+currently
+<a href="http://json-ld.org/#impl">
+five
+interoperable
+implementations
+</a>
+of
+this
+specification.
+There
+is
+a
+<a href="https://github.com/json-ld/json-ld.org/tree/master/test-suite">
+fairly
+complete
+test
+suite
+</a>
+and
+a
+<a href="http://json-ld.org/playground/">
+live
+JSON-LD
+editor
+</a>
+that
+is
+capable
+of
+demonstrating
+the
+features
+described
+in
+this
+document.
+While
+development
+on
+implementations,
+the
+test
+suite
+and
+the
+live
+editor
+will
+continue,
+they
+are
+believed
+to
+be
+mature
+enough
+to
+be
+integrated
+into
+a
+non-production
+system
+at
+this
+point
+in
+time
+with
+the
+expectation
+that
+they
+could
+be
+used
+in
+a
+production
+system
+within
+the
+next
+year.
+</p>
+<div class="issue">
+<div class="issue-title">
+<span>
+Issue
+1
+</span>
+</div>
+<p class="">
+It
+is
+important
+for
+readers
+to
+understand
+that
+the
+scope
+of
+this
+document
+is
+currently
+under
+debate
+and
+new
+features
+may
+be
+added
+to
+the
+specification.
+Existing
+features
+may
+be
+modified
+heavily
+or
+removed
+entirely
+from
+the
+specification
+upon
+further
+review
+and
+feedback
+from
+the
+broader
+community.
+This
+is
+a
+work
+in
+progress
+and
+publication
+as
+a
+First
+Public
+Working
+Draft
+does
+not
+require
+that
+all
+Working
+Group
+members
+agree
+on
+the
+content
+of
+the
+document.
+</p>
+</div>
+<p>
+<ins class="diff-new">This
+document
+was
+published
+by
+the
+</ins><a href="http://www.w3.org/2011/rdf-wg/"><ins class="diff-new">
+RDF
+Working
+Group
+</ins></a><ins class="diff-new">
+as
+a
+First
+Public
+Working
+Draft.
+This
+document
+is
+intended
+to
+become
+a
+</ins><acronym title="World Wide Web Consortium"><ins class="diff-new">
+W3C
+</ins></acronym><ins class="diff-new">
+Recommendation.
+If
+you
+wish
+to
+make
+comments
+regarding
+this
+document,
+please
+send
+them
+to
+</ins><a href="mailto:public-rdf-comments@w3.org"><ins class="diff-new">
+public-rdf-comments@w3.org
+</ins></a><ins class="diff-new">
+(
+</ins><a href="mailto:public-rdf-comments-request@w3.org?subject=subscribe"><ins class="diff-new">
+subscribe
+</ins></a>,<a href="http://lists.w3.org/Archives/Public/public-rdf-comments/"><ins class="diff-new">
+archives
+</ins></a><ins class="diff-new">
+).
+All
+feedback
+is
+welcome.
+</ins></p><p><ins class="diff-new">
+Publication
+as
+a
+Working
+Draft
+does
+not
+imply
+endorsement
+by
+the
+</ins><acronym title="World Wide Web Consortium"><ins class="diff-new">
+W3C
+</ins></acronym><ins class="diff-new">
+Membership.
+This
+is
+a
+draft
+document
+and
+may
+be
+updated,
+replaced
+or
+obsoleted
+by
+other
+documents
+at
+any
+time.
+It
+is
+inappropriate
+to
+cite
+this
+document
+as
+other
+than
+work
+in
+progress.
+</ins></p><p><ins class="diff-new">
+This
+document
+was
+produced
+by
+a
+group
+operating
+under
+the
+</ins><a href="http://www.w3.org/Consortium/Patent-Policy-20040205/"><ins class="diff-new">
+5
+February
+2004
+</ins><acronym title="World Wide Web Consortium"><ins class="diff-new">
+W3C
+</ins></acronym><ins class="diff-new">
+Patent
+Policy
+</ins></a>.<acronym title="World Wide Web Consortium"><ins class="diff-new">
+W3C
+</ins></acronym><ins class="diff-new">
+maintains
+a
+</ins><a href="http://www.w3.org/2004/01/pp-impl/46168/status" rel="disclosure"><ins class="diff-new">
+public
+list
+of
+any
+patent
+disclosures
+</ins></a><ins class="diff-new">
+made
+in
+connection
+with
+the
+deliverables
+of
+the
+group;
+that
+page
+also
+includes
+instructions
+for
+disclosing
+a
+patent.
+An
+individual
+who
+has
+actual
+knowledge
+of
+a
+patent
+which
+the
+individual
+believes
+contains
+</ins><a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential"><ins class="diff-new">
+Essential
+Claim(s)
+</ins></a><ins class="diff-new">
+must
+disclose
+the
+information
+in
+accordance
+with
+</ins><a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure"><ins class="diff-new">
+section
+6
+of
+the
+</ins><acronym title="World Wide Web Consortium"><ins class="diff-new">
+W3C
+</ins></acronym><ins class="diff-new">
+Patent
+Policy
+</ins></a>.</p>
+</div>
+<div id="toc" class="section">
+<h2 class="introductory">
+Table
+of
+Contents
+</h2>
+<ul class="toc">
+<li class="tocline">
+<a href="#preface" class="tocxref">
+<span class="secno">
+1.
+</span>
+Preface
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#contributing" class="tocxref">
+<span class="secno">
+1.1
+</span>
+Contributing
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#introduction" class="tocxref">
+<span class="secno">
+2.
+</span>
+Introduction
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#expansion" class="tocxref">
+<span class="secno">
+2.1
+</span>
+Expansion
+</a>
+</li>
+<li class="tocline">
+<a href="#compaction" class="tocxref">
+<span class="secno">
+2.2
+</span>
+Compaction
+</a>
+</li>
+<li class="tocline">
+<a href="#conversion-to-and-from-rdf" class="tocxref">
+<span class="secno">
+2.3
+</span>
+Conversion
+to
+and
+from
+RDF
+</a>
+</li>
+<li class="tocline">
+<a href="#framing-and-normalization" class="tocxref">
+<span class="secno">
+2.4
+</span>
+Framing
+and
+Normalization
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#the-application-programming-interface" class="tocxref">
+<span class="secno">
+3.
+</span>
+The
+Application
+Programming
+Interface
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#general-terminology" class="tocxref">
+<span class="secno">
+3.1
+</span>
+General
+Terminology
+</a>
+</li>
+<li class="tocline">
+<a href="#jsonldprocessor" class="tocxref">
+<span class="secno">
+3.2
+</span>
+JsonLdProcessor
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#methods" class="tocxref">
+<span class="secno">
+3.2.1
+</span>
+Methods
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#callbacks" class="tocxref">
+<span class="secno">
+3.3
+</span>
+Callbacks
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#jsonldcallback" class="tocxref">
+<span class="secno">
+3.3.1
+</span>
+JsonLdCallback
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#methods-1" class="tocxref">
+<span class="secno">
+3.3.1.1
+</span>
+Methods
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#quadcallback" class="tocxref">
+<span class="secno">
+3.3.2
+</span>
+QuadCallback
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#methods-2" class="tocxref">
+<span class="secno">
+3.3.2.1
+</span>
+Methods
+</a>
+</li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#data-structures" class="tocxref">
+<span class="secno">
+3.4
+</span>
+Data
+Structures
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#url" class="tocxref">
+<span class="secno">
+3.4.1
+</span>
+URL
+</a>
+</li>
+<li class="tocline">
+<a href="#jsonldoptions" class="tocxref">
+<span class="secno">
+3.4.2
+</span>
+JsonLdOptions
+</a>
+</li>
+<li class="tocline">
+<a href="#quad" class="tocxref">
+<span class="secno">
+3.4.3
+</span>
+Quad
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#attributes" class="tocxref">
+<span class="secno">
+3.4.3.1
+</span>
+Attributes
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#node" class="tocxref">
+<span class="secno">
+3.4.4
+</span>
+Node
+</a>
+</li>
+<li class="tocline">
+<a href="#iri" class="tocxref">
+<span class="secno">
+3.4.5
+</span>
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#attributes-1" class="tocxref">
+<span class="secno">
+3.4.5.1
+</span>
+Attributes
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#blank-node" class="tocxref">
+<span class="secno">
+3.4.6
+</span>
+<span title="blank_node">
+Blank
+Node
+</span>
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#attributes-2" class="tocxref">
+<span class="secno">
+3.4.6.1
+</span>
+Attributes
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#literal" class="tocxref">
+<span class="secno">
+3.4.7
+</span>
+Literal
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#attributes-3" class="tocxref">
+<span class="secno">
+3.4.7.1
+</span>
+Attributes
+</a>
+</li>
+</ul>
+</li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#algorithms" class="tocxref">
+<span class="secno">
+4.
+</span>
+Algorithms
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#algorithm-terms" class="tocxref">
+<span class="secno">
+4.1
+</span>
+Algorithm
+Terms
+</a>
+</li>
+<li class="tocline">
+<a href="#context-processing" class="tocxref">
+<span class="secno">
+4.2
+</span>
+Context
+Processing
+</a>
+</li>
+<li class="tocline">
+<a href="#iri-expansion" class="tocxref">
+<span class="secno">
+4.3
+</span>
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Expansion
+</a>
+</li>
+<li class="tocline">
+<a href="#iri-compaction" class="tocxref">
+<span class="secno">
+4.4
+</span>
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Compaction
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#iri-compaction-algorithm" class="tocxref">
+<span class="secno">
+4.4.1
+</span>
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Compaction
+Algorithm
+</a>
+</li>
+<li class="tocline">
+<a href="#term-rank-algorithm" class="tocxref">
+<span class="secno">
+4.4.2
+</span>
+Term
+Rank
+Algorithm
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#value-expansion" class="tocxref">
+<span class="secno">
+4.5
+</span>
+Value
+Expansion
+</a>
+</li>
+<li class="tocline">
+<a href="#value-compaction" class="tocxref">
+<span class="secno">
+4.6
+</span>
+Value
+Compaction
+</a>
+</li>
+<li class="tocline">
+<a href="#expansion-1" class="tocxref">
+<span class="secno">
+4.7
+</span>
+Expansion
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#expansion-algorithm" class="tocxref">
+<span class="secno">
+4.7.1
+</span>
+Expansion
+Algorithm
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#compaction-1" class="tocxref">
+<span class="secno">
+4.8
+</span>
+Compaction
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#compaction-algorithm" class="tocxref">
+<span class="secno">
+4.8.1
+</span>
+Compaction
+Algorithm
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#rdf-conversion" class="tocxref">
+<span class="secno">
+4.9
+</span>
+RDF
+Conversion
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#overview" class="tocxref">
+<span class="secno">
+4.9.1
+</span>
+Overview
+</a>
+</li>
+<li class="tocline">
+<a href="#parsing-examples" class="tocxref">
+<span class="secno">
+4.9.2
+</span>
+Parsing
+Examples
+</a>
+</li>
+<li class="tocline">
+<a href="#convert-to-rdf-algorithm" class="tocxref">
+<span class="secno">
+4.9.3
+</span>
+Convert
+to
+RDF
+Algorithm
+</a>
+</li>
+<li class="tocline">
+<a href="#list-conversion" class="tocxref">
+<span class="secno">
+4.9.4
+</span>
+List
+Conversion
+</a>
+</li>
+<li class="tocline">
+<a href="#convert-from-rdf-algorithm" class="tocxref">
+<span class="secno">
+4.9.5
+</span>
+Convert
+from
+RDF
+Algorithm
+</a>
+</li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#data-round-tripping" class="tocxref">
+<span class="secno">
+5.
+</span>
+Data
+Round
+Tripping
+</a>
+</li>
+<li class="tocline">
+<a href="#appendix-a" class="tocxref">
+<span class="secno">
+A.
+</span>
+Initial
+Context
+</a>
+</li>
+<li class="tocline">
+<a href="#acknowledgements" class="tocxref">
+<span class="secno">
+B.
+</span>
+Acknowledgements
+</a>
+</li>
+<li class="tocline">
+<a href="#references" class="tocxref">
+<span class="secno">
+C.
+</span>
+References
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#normative-references" class="tocxref">
+<span class="secno">
+C.1
+</span>
+Normative
+references
+</a>
+</li>
+<li class="tocline">
+<a href="#informative-references" class="tocxref">
+<span class="secno">
+C.2
+</span>
+Informative
+references
+</a>
+</li>
+</ul>
+</li>
+</ul>
+</div>
+<div id="preface" class="section">
+<h2>
+<span class="secno">
+1.
+</span>
+Preface
+</h2>
+<p>
+This
+document
+is
+a
+detailed
+specification
+for
+an
+Application
+Programming
+Interface
+for
+the
+JSON-LD
+Syntax.
+The
+document
+is
+primarily
+intended
+for
+the
+following
+audiences:
+</p>
+<ul>
+<li>
+Web
+authors
+and
+developers
+that
+want
+a
+very
+detailed
+view
+of
+how
+a
+JSON-LD
+processor
+and
+the
+API
+operates.
+</li>
+<li>
+Software
+developers
+that
+want
+to
+implement
+processors
+and
+APIs
+for
+JSON-LD.
+</li>
+</ul>
+<p>
+To
+understand
+the
+basics
+in
+this
+specification
+you
+must
+first
+be
+familiar
+with
+JSON,
+which
+is
+detailed
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RFC4627">
+RFC4627
+</a>
+</cite>
+].
+You
+must
+also
+understand
+the
+JSON-LD
+Syntax
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-JSON-LD">
+JSON-LD
+</a>
+</cite>
+],
+which
+is
+the
+base
+syntax
+used
+by
+all
+of
+the
+algorithms
+in
+this
+document.
+To
+understand
+the
+API
+and
+how
+it
+is
+intended
+to
+operate
+in
+a
+programming
+environment,
+it
+is
+useful
+to
+have
+working
+knowledge
+of
+the
+JavaScript
+programming
+language
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-ECMA-262">
+ECMA-262
+</a>
+</cite>
+]
+and
+WebIDL
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-WEBIDL">
+WEBIDL
+</a>
+</cite>
+].
+To
+understand
+how
+JSON-LD
+maps
+to
+RDF,
+it
+is
+helpful
+to
+be
+familiar
+with
+the
+basic
+RDF
+concepts
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">
+RDF-CONCEPTS
+</a>
+</cite>
+].
+</p>
+<div id="contributing" class="section">
+<h3>
+<span class="secno">
+1.1
+</span>
+Contributing
+</h3>
+<p>
+There
+are
+a
+number
+of
+ways
+that
+one
+may
+participate
+in
+the
+development
+of
+this
+specification:
+</p>
+<ul>
+<li>
+If
+you
+want
+to
+make
+sure
+that
+your
+feedback
+is
+formally
+addressed
+by
+the
+RDF
+Working
+Group,
+you
+should
+send
+it
+to
+public-rdf-comments:
+<a href="http://lists.w3.org/Archives/Public/public-rdf-comments/">
+public-rdf-comments@w3.org
+</a>
+</li>
+<li>
+Ad-hoc
+technical
+discussion
+primarily
+occurs
+on
+the
+public
+community
+mailing
+list:
+<a href="http://lists.w3.org/Archives/Public/public-linked-json/">
+public-linked-json@w3.org
+</a>
+</li>
+<li>
+<a href="http://json-ld.org/minutes/">
+Public
+JSON-LD
+Community
+Group
+teleconferences
+</a>
+are
+held
+on
+Tuesdays
+at
+1500UTC
+every
+week.
+</li>
+<li>
+RDF
+Working
+Group
+teleconferences
+are
+held
+on
+Wednesdays
+at
+1500UTC
+every
+week.
+Participation
+is
+limited
+to
+RDF
+Working
+Group
+members.
+</li>
+<li>
+Specification
+bugs
+and
+issues
+should
+be
+reported
+in
+the
+<a href="https://github.com/json-ld/json-ld.org/issues">
+issue
+tracker
+</a>
+if
+you
+do
+not
+want
+to
+send
+an
+e-mail
+to
+the
+public-rdf-comments
+mailing
+list.
+</li>
+<li>
+<a href="https://github.com/json-ld/json-ld.org/tree/master/spec">
+Source
+code
+</a>
+for
+the
+specification
+can
+be
+found
+on
+Github.
+</li>
+<li>
+The
+<a href="http://webchat.freenode.net/?channels=json-ld">
+#json-ld
+</a>
+IRC
+channel
+is
+available
+for
+real-time
+discussion
+on
+irc.freenode.net.
+</li>
+</ul>
+</div>
+</div>
+<div id="introduction" class="section">
+<h2>
+<span class="secno">
+2.
+</span>
+Introduction
+</h2>
+<p>
+The
+JSON-LD
+Syntax
+specification
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-JSON-LD">
+JSON-LD
+</a>
+</cite>
+]
+outlines
+a
+language
+that
+may
+be
+used
+to
+express
+Linked
+Data
+in
+JSON.
+Often,
+it
+is
+useful
+to
+be
+able
+to
+transform
+JSON-LD
+documents
+so
+that
+they
+may
+be
+easily
+processed
+in
+a
+programming
+environment
+like
+JavaScript,
+Python
+or
+Ruby.
+</p>
+<p>
+There
+are
+three
+major
+types
+of
+transformation
+that
+are
+discussed
+in
+this
+document;
+compaction,
+expansion,
+and
+RDF
+conversion.
+</p>
+<div id="expansion" class="section">
+<h3>
+<span class="secno">
+2.1
+</span>
+Expansion
+</h3>
+<p>
+Software
+algorithms
+are
+easiest
+to
+write
+when
+the
+data
+that
+they
+are
+processing
+have
+a
+regular
+form.
+Since
+information
+can
+be
+represented
+by
+JSON-LD
+in
+a
+variety
+of
+different
+ways,
+transforming
+all
+of
+these
+methods
+into
+a
+uniform
+structure
+allows
+the
+developer
+to
+simplify
+their
+processing
+code.
+For
+example,
+note
+that
+the
+following
+input
+uses
+only
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s
+and
+is
+fairly
+compact:
+</p>
+  <div class="example"><div class="example-title"><span>Example 1</span></div><pre class="example">var input1 = {
+  &quot;@context&quot;: &quot;http://json-ld.org/contexts/person.jsonld&quot;
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;
+}
+</pre>
+</div>
+<p>
+The
+next
+input
+example
+uses
+one
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+to
+express
+a
+property,
+but
+leaves
+the
+rest
+of
+the
+information
+untouched.
+</p>
+  <div class="example"><div class="example-title"><span>Example 2</span></div><pre class="example">var input2 = {
+  &quot;@context&quot;: &quot;http://json-ld.org/contexts/person.jsonld&quot;
+  &quot;<span class="diff">http://xmlns.com/foaf/0.1/name</span>&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;
+}
+</pre>
+</div>
+<p>
+While
+both
+inputs
+are
+valid
+JSON-LD,
+writing
+a
+program
+to
+handle
+every
+permutation
+of
+possible
+inputs
+can
+be
+difficult,
+especially
+when
+the
+incoming
+context
+could
+change
+as
+well.
+To
+ensure
+that
+the
+data
+can
+be
+given
+a
+more
+uniform
+structure,
+JSON-LD
+introduces
+the
+notion
+of
+expansion.
+<dfn title="expansion" id="dfn-expansion">
+Expansion
+</dfn>
+performs
+two
+important
+operations.
+The
+first
+is
+to
+expand
+all
+values
+that
+are
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+s
+to
+their
+fully
+expanded
+form.
+The
+second
+is
+to
+express
+all
+values
+in
+<dfn title="expanded_form" id="dfn-expanded_form">
+expanded
+form
+</dfn>.
+To
+transform
+both
+inputs
+above
+to
+the
+same
+representation,
+the
+developer
+could
+do
+the
+following:
+</p>
+  <div class="example"><div class="example-title"><span>Example 3</span></div><pre class="example">function expansionCallback(output) {
+   console.log(output);
+}
+// the second parameter is 'null' because the developer does not wish to
+// inject another context value
+jsonld.expand(input1, null, expansionCallback);
+jsonld.expand(input2,
+null,
+expansionCallback);
+</pre>
+</div>
+<p>
+The
+output
+for
+both
+calls
+above
+will
+be:
+</p>
+  <div class="example"><div class="example-title"><span>Example 4</span></div><pre class="example">[{
+  &quot;http://xmlns.com/foaf/0.1/name&quot;: [{
+    &quot;@value&quot;: &quot;Manu Sporny&quot;
+  }],
+  &quot;http://xmlns.com/foaf/0.1/homepage&quot;: [{
+    &quot;@id&quot;: &quot;http://manu.sporny.org/&quot;
+  }]
+}]
+</pre>
+</div>
+<p>
+Note
+that
+in
+the
+example
+above;
+all
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+definitions
+have
+been
+removed,
+all
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+and
+prefixes
+have
+been
+expanded
+to
+full
+IRIs,
+and
+all
+<a class="tref internalDFN" title="literal" href="#dfn-literal">
+literal
+</a>
+s
+are
+expressed
+in
+<a class="tref internalDFN" title="expanded_form" href="#dfn-expanded_form">
+expanded
+form
+</a>.
+While
+the
+output
+is
+more
+difficult
+for
+a
+human
+to
+read,
+it
+is
+easier
+for
+a
+software
+program
+to
+process
+because
+of
+its
+very
+regular
+structure.
+</p>
+</div>
+<div id="compaction" class="section">
+<h3>
+<span class="secno">
+2.2
+</span>
+Compaction
+</h3>
+<p>
+While
+expansion
+expands
+a
+given
+input
+as
+much
+as
+possible,
+compaction
+performs
+the
+opposite
+operation
+-
+expressing
+a
+given
+input
+as
+succinctly
+as
+possible.
+While
+expansion
+is
+meant
+to
+produce
+something
+that
+is
+easy
+to
+process
+by
+software
+programs,
+compaction
+is
+meant
+to
+produce
+something
+that
+is
+easy
+to
+ready
+by
+software
+developers.
+Compaction
+uses
+a
+developer-supplied
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+to
+compresses
+all
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+s
+to
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s
+or
+<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
+prefix
+</a>
+es,
+and
+compacts
+all
+<a class="tref internalDFN" title="literal" href="#dfn-literal">
+literal
+</a>
+s
+expressed
+in
+<a class="tref internalDFN" title="expanded_form" href="#dfn-expanded_form">
+expanded
+form
+</a>
+as
+much
+as
+possible.
+</p>
+<p>
+The
+following
+example
+expresses
+input
+that
+has
+already
+been
+fully
+expanded:
+</p>
+  <div class="example"><div class="example-title"><span>Example 5</span></div><pre class="example">var expandedInput = [{
+  &quot;http://xmlns.com/foaf/0.1/name&quot;: [{
+    &quot;@value&quot;: &quot;Manu Sporny&quot;
+  }],
+  &quot;http://xmlns.com/foaf/0.1/homepage&quot;: [{
+    &quot;@id&quot;: &quot;http://manu.sporny.org/&quot;
+  }]
+}]
+</pre>
+</div>
+<p>
+A
+developer
+that
+wants
+to
+transform
+the
+data
+above
+into
+a
+more
+human-readable
+form,
+could
+do
+the
+following
+using
+the
+JSON-LD
+API:
+</p>
+  <div class="example"><div class="example-title"><span>Example 6</span></div><pre class="example">function compactionCallback(output) {
+   console.log(output);
+}
+jsonld.compact(expandedInput,
+&quot;http://json-ld.org/contexts/person.jsonld&quot;,
+compactionCallback);
+</pre>
+</div>
+<p>
+The
+following
+would
+be
+the
+result
+of
+the
+call
+above:
+</p>
+  <div class="example"><div class="example-title"><span>Example 7</span></div><pre class="example">{
+  &quot;@context&quot;: &quot;http://json-ld.org/contexts/person.jsonld&quot;
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;
+}
+</pre>
+</div>
+<p>
+Note
+that
+all
+of
+the
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s
+have
+been
+compressed
+and
+the
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+has
+been
+injected
+into
+the
+output.
+While
+compacted
+output
+is
+most
+useful
+to
+humans,
+it
+can
+also
+be
+carefully
+used
+to
+generate
+structures
+that
+are
+easy
+to
+use
+for
+developers
+to
+program
+against
+as
+well.
+</p>
+</div>
+<div id="conversion-to-and-from-rdf" class="section">
+<h3>
+<span class="secno">
+2.3
+</span>
+Conversion
+to
+and
+from
+RDF
+</h3>
+<p>
+JSON-LD
+can
+be
+used
+to
+losslessly
+express
+the
+RDF
+data
+model
+as
+described
+in
+the
+RDF
+Concepts
+document
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">
+RDF-CONCEPTS
+</a>
+</cite>
+].
+This
+ensures
+that
+data
+can
+be
+round-tripped
+from
+any
+RDF
+syntax,
+like
+N-Triples
+or
+TURTLE,
+without
+any
+loss
+in
+the
+fidelity
+of
+the
+data.
+Assume
+the
+following
+RDF
+input
+in
+N-Triples
+format:
+</p>
+  <div class="example"><div class="example-title"><span>Example 8</span></div><pre class="example">var data = &quot;
+&lt;http://manu.sporny.org/about/#manu&gt; &lt;http://xmlns.com/foaf/0.1/name&gt; \&quot;Manu Sporny\&quot; .\n
+&lt;http://manu.sporny.org/about/#manu&gt;
+&lt;http://xmlns.com/foaf/0.1/homepage&gt;
+&lt;http://manu.sporny.org/&gt;
+.&quot;;
+</pre>
+</div>
+<p>
+A
+developer
+can
+use
+the
+JSON-LD
+API
+to
+transform
+the
+markup
+above
+into
+a
+JSON-LD
+document:
+</p>
+  <div class="example"><div class="example-title"><span>Example 9</span></div><pre class="example">function conversionCallback(result)
+{
+  console.log(&quot;JSON-LD Document: &quot;, result);
+};
+jsonld.fromRDF(data,
+conversionCallback,
+{&quot;format&quot;:
+&quot;ntriples&quot;});
+</pre>
+</div>
+<p>
+The
+following
+expanded
+output
+would
+be
+the
+result
+of
+the
+call
+above:
+</p>
+  <div class="example"><div class="example-title"><span>Example 10</span></div><pre class="example">[{
+  &quot;@id&quot;: &quot;http://manu.sporny.org/about/#manu&quot;,
+  &quot;http://xmlns.com/foaf/0.1/name&quot;: [{
+    &quot;@value&quot;: &quot;Manu Sporny&quot;
+  }],
+  &quot;http://xmlns.com/foaf/0.1/homepage&quot;: [{
+    &quot;@id&quot;: &quot;http://manu.sporny.org/&quot;
+  }]
+}]
+</pre>
+</div>
+<p>
+Note
+that
+the
+output
+above,
+could
+easily
+be
+compacted
+to
+produce
+the
+following
+using
+the
+technique
+outlined
+in
+the
+previous
+section:
+</p>
+  <div class="example"><div class="example-title"><span>Example 11</span></div><pre class="example">{
+  &quot;@context&quot;: &quot;http://json-ld.org/contexts/person.jsonld&quot;,
+  &quot;@id&quot;: &quot;http://manu.sporny.org/about/#manu&quot;,
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;
+}
+</pre>
+</div>
+<p>
+Transforming
+the
+object
+above
+back
+to
+RDF
+is
+as
+simple
+as
+calling
+the
+<code>
+toRDF()
+</code>
+method:
+</p>
+  <div class="example"><div class="example-title"><span>Example 12</span></div><pre class="example">var jsonldDocument = ...; // assign the JSON-LD document here
+function rdfCallback(quads)
+{
+  console.log(&quot;RDF Data: &quot;, quads);
+};
+jsonld.toRDF(jsonldDocument,
+rdfCallback);
+</pre>
+</div>
+</div>
+<div id="framing-and-normalization" class="section">
+<h3>
+<span class="secno">
+2.4
+</span>
+Framing
+and
+Normalization
+</h3>
+<div class="issue">
+<div class="issue-title">
+<span>
+Issue
+2
+</span>
+</div>
+<p class="">
+There
+are
+currently
+two
+other
+API
+methods
+that
+are
+in
+active
+development
+and
+were
+not
+ready
+for
+publication
+at
+the
+time
+this
+document
+was
+published.
+Framing
+allows
+a
+developer
+to
+force
+a
+different
+layout
+for
+the
+data
+and
+effectively
+perform
+query-by-example
+on
+JSON-LD
+documents
+-
+this
+is
+most
+useful
+when
+a
+JSON-LD-based
+REST
+API
+does
+not
+know
+the
+exact
+form
+of
+the
+data
+it
+is
+getting
+in,
+but
+still
+wants
+to
+operate
+upon
+it
+if
+some
+bare
+essentials
+are
+found
+in
+the
+data.
+JSON-LD
+normalization
+allows
+JSON-LD
+documents
+to
+be
+deterministically
+serialized
+such
+that
+they
+can
+be
+digitally
+signed
+or
+be
+used
+to
+find
+the
+differences
+between
+two
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>
+s.
+It
+is
+expected
+that
+framing
+will
+be
+a
+part
+of
+the
+final
+API.
+It
+is
+expected
+that
+normalization
+will
+be
+an
+optional
+feature
+that
+JSON-LD
+processors
+may
+implement.
+</p>
+</div>
+</div>
+</div>
+<div id="the-application-programming-interface" class="section">
+<h2>
+<span class="secno">
+3.
+</span>
+The
+Application
+Programming
+Interface
+</h2>
+<p>
+This
+API
+provides
+a
+clean
+mechanism
+that
+enables
+developers
+to
+convert
+JSON-LD
+data
+into
+a
+a
+variety
+of
+output
+formats
+that
+are
+easier
+to
+work
+with
+in
+various
+programming
+languages.
+If
+a
+JSON-LD
+API
+is
+provided
+in
+a
+programming
+environment,
+the
+entirety
+of
+the
+following
+API
+<em class="rfc2119" title="must">
+must
+</em>
+be
+implemented.
+</p>
+<div id="general-terminology" class="section">
+<h3>
+<span class="secno">
+3.1
+</span>
+General
+Terminology
+</h3>
+<div class="issue">
+<div class="issue-title">
+<span>
+Issue
+3
+</span>
+</div>
+<p class="">
+The
+intent
+of
+the
+Working
+Group
+and
+the
+Editors
+of
+this
+specification
+is
+to
+eventually
+align
+terminology
+used
+in
+this
+document
+with
+the
+terminology
+used
+in
+the
+RDF
+Concepts
+document
+to
+the
+extent
+to
+which
+it
+makes
+sense
+to
+do
+so.
+In
+general,
+if
+there
+is
+an
+analogue
+to
+terminology
+used
+in
+this
+document
+in
+the
+RDF
+Concepts
+document,
+the
+preference
+is
+to
+use
+the
+terminology
+in
+the
+RDF
+Concepts
+document.
+</p>
+</div>
+<p>
+The
+following
+is
+an
+explanation
+of
+the
+general
+terminology
+used
+in
+this
+document:
+</p>
+<dl>
+<dt>
+<dfn title="json_object" id="dfn-json_object">
+JSON
+object
+</dfn>
+</dt>
+<dd>
+An
+object
+structure
+is
+represented
+as
+a
+pair
+of
+curly
+brackets
+surrounding
+zero
+or
+more
+name-value
+pairs.
+A
+name
+is
+a
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>.
+A
+single
+colon
+comes
+after
+each
+name,
+separating
+the
+name
+from
+the
+value.
+A
+single
+comma
+separates
+a
+value
+from
+a
+following
+name.
+The
+names
+within
+an
+object
+<em class="rfc2119" title="should">
+should
+</em>
+be
+unique.
+</dd>
+<dt>
+<dfn title="array" id="dfn-array">
+array
+</dfn>
+</dt>
+<dd>
+An
+array
+is
+represented
+as
+square
+brackets
+surrounding
+zero
+or
+more
+values
+that
+are
+separated
+by
+commas.
+</dd>
+<dt>
+<dfn title="string" id="dfn-string">
+string
+</dfn>
+</dt>
+<dd>
+A
+string
+is
+a
+sequence
+of
+zero
+or
+more
+Unicode
+(UTF-8)
+characters,
+wrapped
+in
+double
+quotes,
+using
+backslash
+escapes
+(if
+necessary).
+A
+character
+is
+represented
+as
+a
+single
+character
+string.
+</dd>
+<dt>
+<dfn title="number" id="dfn-number">
+number
+</dfn>
+</dt>
+<dd>
+A
+number
+is
+similar
+to
+that
+used
+in
+most
+programming
+languages,
+except
+that
+the
+octal
+and
+hexadecimal
+formats
+are
+not
+used
+and
+that
+leading
+zeros
+are
+not
+allowed.
+</dd>
+<dt>
+<dfn title="true" id="dfn-true">
+true
+</dfn>
+and
+<dfn title="false" id="dfn-false">
+false
+</dfn>
+</dt>
+<dd>
+Values
+that
+are
+used
+to
+express
+one
+of
+two
+possible
+boolean
+states.
+</dd>
+<dt>
+<dfn title="null" id="dfn-null">
+null
+</dfn>
+</dt>
+<dd>
+Unless
+otherwise
+specified,
+a
+JSON-LD
+processor
+<em class="rfc2119" title="must">
+must
+</em>
+act
+as
+if
+a
+key-value
+pair
+in
+the
+body
+of
+a
+JSON-LD
+document
+was
+never
+declared
+when
+the
+value
+equals
+<em>
+null
+</em>.
+If
+<code>
+@value
+</code>,
+<code>
+@list
+</code>,
+or
+<code>
+@set
+</code>
+is
+set
+to
+<em>
+null
+</em>
+in
+expanded
+form,
+then
+the
+entire
+JSON
+object
+is
+ignored.
+If
+<code>
+@context
+</code>
+is
+set
+to
+<em>
+null
+</em>,
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+is
+reset
+and
+when
+used
+within
+a
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>,
+it
+removes
+any
+definition
+associated
+with
+the
+key,
+unless
+otherwise
+specified.
+</dd>
+<dt>
+<dfn title="subject_definition" id="dfn-subject_definition">
+subject
+definition
+</dfn>
+</dt>
+<dd>
+A
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+used
+to
+represent
+a
+<a class="tref internalDFN" title="subject" href="#dfn-subject">
+subject
+</a>
+and
+one
+or
+more
+properties
+of
+that
+subject.
+A
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+is
+a
+subject
+definition
+if
+it
+does
+not
+contain
+they
+keys
+<code>
+@value
+</code>,
+<code>
+@list
+</code>
+or
+<code>
+@set
+</code>
+and
+it
+has
+one
+or
+more
+keys
+other
+than
+<code>
+@id
+</code>.
+</dd>
+<dt>
+<dfn title="subject_reference" id="dfn-subject_reference">
+subject
+reference
+</dfn>
+</dt>
+<dd>
+A
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+used
+to
+reference
+a
+subject
+having
+only
+the
+<code>
+@id
+</code>
+key.
+</dd>
+<dt>
+<dfn title="linked_data" id="dfn-linked_data">
+Linked
+Data
+</dfn>
+</dt>
+<dd>
+A
+set
+of
+documents,
+each
+containing
+a
+representation
+of
+a
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>.
+</dd>
+<dt>
+<dfn title="linked_data_graph" id="dfn-linked_data_graph">
+linked
+data
+graph
+</dfn>
+or
+<dfn title="dataset" id="dfn-dataset">
+dataset
+</dfn>
+</dt>
+<dd>
+An
+unordered
+labeled
+directed
+graph,
+where
+<a class="tref internalDFN" title="node" href="#dfn-node">
+node
+</a>
+s
+are
+<a class="tref internalDFN" title="subject" href="#dfn-subject">
+subject
+</a>
+s
+or
+<a class="tref internalDFN" title="object" href="#dfn-object">
+object
+</a>
+s,
+and
+edges
+are
+properties.
+</dd>
+<dt>
+<dfn title="node" id="dfn-node">
+node
+</dfn>
+</dt>
+<dd>
+A
+piece
+of
+information
+that
+is
+represented
+in
+a
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>.
+</dd>
+<dt>
+<dfn title="named_graph" id="dfn-named_graph">
+named
+graph
+</dfn>
+</dt>
+<dd>
+A
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>
+that
+has
+one
+or
+more
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+that
+are
+used
+to
+refer
+to
+it.
+</dd>
+<dt>
+<dfn title="graph_name" id="dfn-graph_name">
+graph
+name
+</dfn>
+</dt>
+<dd>
+An
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+that
+is
+a
+reference
+to
+a
+<a class="tref internalDFN" title="named_graph" href="#dfn-named_graph">
+named
+graph
+</a>.
+</dd>
+<dt>
+<dfn title="default_graph" id="dfn-default_graph">
+default
+graph
+</dfn>
+</dt>
+<dd>
+When
+executing
+an
+algorithm,
+the
+graph
+where
+data
+should
+be
+placed
+if
+a
+<a class="tref internalDFN" title="named_graph" href="#dfn-named_graph">
+named
+graph
+</a>
+is
+not
+specified.
+</dd>
+<dt>
+<dfn title="subject" id="dfn-subject">
+subject
+</dfn>
+</dt>
+<dd>
+Any
+node
+in
+a
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>
+with
+at
+least
+one
+outgoing
+edge.
+</dd>
+<dt>
+<dfn title="iri" id="dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</dfn>
+</dt>
+<dd>
+An
+Internationalized
+Resource
+Identifier
+as
+described
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RFC3987">
+RFC3987
+</a>
+</cite>
+]).
+</dd>
+<dt>
+<dfn title="object" id="dfn-object">
+object
+</dfn>
+</dt>
+<dd>
+A
+node
+in
+a
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>
+with
+at
+least
+one
+incoming
+edge.
+</dd>
+<dt>
+<dfn title="property" id="dfn-property">
+property
+</dfn>
+</dt>
+<dd>
+An
+edge
+of
+the
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>.
+</dd>
+<dt>
+<dfn title="literal" id="dfn-literal">
+literal
+</dfn>
+</dt>
+<dd>
+An
+<a class="tref internalDFN" title="object" href="#dfn-object">
+object
+</a>
+with
+a
+label
+that
+is
+not
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+</dd>
+<dt>
+<dfn title="quad" id="dfn-quad">
+quad
+</dfn>
+</dt>
+<dd>
+A
+piece
+of
+information
+that
+contains
+four
+items;
+a
+<a class="tref internalDFN" title="subject" href="#dfn-subject">
+subject
+</a>,
+a
+<a class="tref internalDFN" title="property" href="#dfn-property">
+property
+</a>,
+a
+<a class="tref internalDFN" title="object" href="#dfn-object">
+object
+</a>,
+and
+a
+<a class="tref internalDFN" title="graph_name" href="#dfn-graph_name">
+graph
+name
+</a>.
+</dd>
+<dt>
+<dfn title="context" id="dfn-context">
+context
+</dfn>
+</dt>
+<dd>
+A
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+that
+contains
+rules
+for
+interpreting
+a
+JSON-LD
+document.
+</dd>
+<dt>
+<dfn title="keyword" id="dfn-keyword">
+keyword
+</dfn>
+</dt>
+<dd>
+A
+JSON
+key
+that
+is
+specific
+to
+JSON-LD,
+specified
+in
+the
+JSON-LD
+Syntax
+specification
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-JSON-LD">
+JSON-LD
+</a>
+</cite>
+]
+in
+the
+section
+titled
+<a href="http://sites.local/json-ld.org/spec/latest/json-ld-syntax/#syntax-tokens-and-keywords">
+Syntax
+Tokens
+and
+Keywords
+</a>.
+</dd>
+</dl>
+</div>
+<div id="jsonldprocessor" class="section">
+<h3>
+<span class="secno">
+3.2
+</span>
+JsonLdProcessor
+</h3>
+<p>
+The
+JSON-LD
+Processor
+interface
+is
+the
+high-level
+programming
+structure
+that
+developers
+use
+to
+access
+the
+JSON-LD
+transformation
+methods.
+</p>
+    <pre class="idl"><span class="idlInterface" id="idl-def-JsonLdProcessor">[<span class="extAttr">NoInterfaceObject</span>]
+interface <span class="idlInterfaceID">JsonLdProcessor</span> {
+<span class="idlMethod">    <span class="idlMethType"><a>void</a></span> <span class="idlMethName"><a href="#widl-JsonLdProcessor-expand-void-object-or-object---or-URL-input-object-or-URL-context-JsonLdCallback-callback-JsonLdOptions-options">expand</a></span> (<span class="idlParam"><span class="idlParamType"><a>object or object[] or URL</a></span> <span class="idlParamName">input</span></span>, <span class="idlParam"><span class="idlParamType"><a>object or URL</a>?</span> <span class="idlParamName">context</span></span>, <span class="idlParam"><span class="idlParamType"><a href="#idl-def-JsonLdCallback" class="idlType"><code>JsonLdCallback</code></a></span> <span class="idlParamName">callback</span></span>, <span class="idlParam">optional <span class="idlParamType"><a href="#idl-def-JsonLdOptions" class="idlType"><code>JsonLdOptions</code></a></span> <span class="idlParamName">options</span></span>);</span>
+<span class="idlMethod">    <span class="idlMethType"><a>void</a></span> <span class="idlMethName"><a href="#widl-JsonLdProcessor-compact-void-object-or-object---or-URL-input-object-or-URL-context-JsonLdCallback-callback-JsonLdOptions-options">compact</a></span> (<span class="idlParam"><span class="idlParamType"><a>object or object[] or URL</a></span> <span class="idlParamName">input</span></span>, <span class="idlParam"><span class="idlParamType"><a>object or URL</a></span> <span class="idlParamName">context</span></span>, <span class="idlParam"><span class="idlParamType"><a href="#idl-def-JsonLdCallback" class="idlType"><code>JsonLdCallback</code></a></span> <span class="idlParamName">callback</span></span>, <span class="idlParam">optional <span class="idlParamType"><a href="#idl-def-JsonLdOptions" class="idlType"><code>JsonLdOptions</code></a></span> <span class="idlParamName">options</span></span>);</span>
+<span class="idlMethod">    <span class="idlMethType"><a>void</a></span> <span class="idlMethName"><a href="#widl-JsonLdProcessor-fromRDF-void-QuadArray-input-JsonLdCallback-callback-JsonLdOptions-options">fromRDF</a></span> (<span class="idlParam"><span class="idlParamType"><a href="#idl-def-Quad" class="idlType"><code>Quad</code></a>[]</span> <span class="idlParamName">input</span></span>, <span class="idlParam"><span class="idlParamType"><a href="#idl-def-JsonLdCallback" class="idlType"><code>JsonLdCallback</code></a></span> <span class="idlParamName">callback</span></span>, <span class="idlParam">optional <span class="idlParamType"><a href="#idl-def-JsonLdOptions" class="idlType"><code>JsonLdOptions</code></a></span> <span class="idlParamName">options</span></span>);</span>
+<span class="idlMethod">    <span class="idlMethType"><a>void</a></span> <span class="idlMethName"><a href="#widl-JsonLdProcessor-toRDF-void-object-or-object---or-URL-input-QuadCallback-callback-JsonLdOptions-options">toRDF</a></span> (<span class="idlParam"><span class="idlParamType"><a>object or object[] or URL</a></span> <span class="idlParamName">input</span></span>, <span class="idlParam"><span class="idlParamType"><a href="#idl-def-QuadCallback" class="idlType"><code>QuadCallback</code></a></span> <span class="idlParamName">callback</span></span>, <span class="idlParam">optional <span class="idlParamType"><a href="#idl-def-JsonLdOptions" class="idlType"><code>JsonLdOptions</code></a></span> <span class="idlParamName">options</span></span>);</span>
+};</span>
+</pre>
+<div id="methods" class="section">
+<h2>
+<span class="secno">
+3.2.1
+</span>
+Methods
+</h2>
+<dl class="methods">
+<dt id="widl-JsonLdProcessor-compact-void-object-or-object---or-URL-input-object-or-URL-context-JsonLdCallback-callback-JsonLdOptions-options">
+<code>
+compact
+</code>
+</dt>
+<dd>
+<a href="#compaction">
+Compacts
+</a>
+the
+given
+<code>
+input
+</code>
+using
+the
+<code>
+context
+</code>
+according
+to
+the
+steps
+in
+the
+<a href="#compaction-algorithm">
+Compaction
+Algorithm
+</a>.
+The
+<code>
+input
+</code>
+<em class="rfc2119" title="must">
+must
+</em>
+be
+copied,
+compacted
+and
+returned
+if
+there
+are
+no
+errors.
+If
+the
+compaction
+fails,
+an
+appropriate
+exception
+<em class="rfc2119" title="must">
+must
+</em>
+be
+thrown.
+<table class="parameters">
+<tr>
+<th>
+Parameter
+</th>
+<th>
+Type
+</th>
+<th>
+Nullable
+</th>
+<th>
+Optional
+</th>
+<th>
+Description
+</th>
+</tr>
+<tr>
+<td class="prmName">
+input
+</td>
+<td class="prmType">
+<code>
+<a>
+object
+or
+object[]
+or
+URL
+</a>
+</code>
+</td>
+<td class="prmNullFalse">
+✘
+</td>
+<td class="prmOptFalse">
+✘
+</td>
+<td class="prmDesc">
+The
+JSON-LD
+object
+or
+array
+of
+JSON-LD
+objects
+to
+perform
+the
+compaction
+upon
+or
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+referencing
+the
+JSON-LD
+document
+to
+compact.
+</td>
+</tr>
+<tr>
+<td class="prmName">
+context
+</td>
+<td class="prmType">
+<code>
+<a>
+object
+or
+URL
+</a>
+</code>
+</td>
+<td class="prmNullFalse">
+✘
+</td>
+<td class="prmOptFalse">
+✘
+</td>
+<td class="prmDesc">
+The
+context
+to
+use
+when
+compacting
+the
+<code>
+input
+</code>
+;
+either
+in
+the
+form
+of
+an
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+or
+as
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+</td>
+</tr>
+<tr>
+<td class="prmName">
+callback
+</td>
+<td class="prmType">
+<code>
+<a href="#idl-def-JsonLdCallback" class="idlType">
+<code>
+JsonLdCallback
+</code>
+</a>
+</code>
+</td>
+<td class="prmNullFalse">
+✘
+</td>
+<td class="prmOptFalse">
+✘
+</td>
+<td class="prmDesc">
+A
+callback
+that
+is
+called
+when
+processing
+is
+complete
+on
+the
+given
+<code>
+input
+</code>.
+</td>
+</tr>
+<tr>
+<td class="prmName">
+options
+</td>
+<td class="prmType">
+<code>
+<a href="#idl-def-JsonLdOptions" class="idlType">
+<code>
+JsonLdOptions
+</code>
+</a>
+</code>
+</td>
+<td class="prmNullFalse">
+✘
+</td>
+<td class="prmOptTrue">
+✔
+</td>
+<td class="prmDesc">
+A
+set
+of
+options
+that
+<em class="rfc2119" title="may">
+may
+</em>
+affect
+the
+expansion
+algorithm
+such
+as,
+e.g.,
+the
+input
+document's
+base
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+This
+also
+includes
+<code>
+optimize
+</code>,
+which
+if
+set
+will
+cause
+processor-specific
+optimization.
+</td>
+</tr>
+</table>
+<div>
+<em>
+Return
+type:
+</em>
+<code>
+<a>
+void
+</a>
+</code>
+</div>
+</dd>
+<dt id="widl-JsonLdProcessor-expand-void-object-or-object---or-URL-input-object-or-URL-context-JsonLdCallback-callback-JsonLdOptions-options">
+<code>
+expand
+</code>
+</dt>
+<dd>
+<a href="#expansion">
+Expands
+</a>
+the
+given
+<code>
+input
+</code>
+according
+to
+the
+steps
+in
+the
+<a href="#expansion-algorithm">
+Expansion
+Algorithm
+</a>.
+The
+<code>
+input
+</code>
+<em class="rfc2119" title="must">
+must
+</em>
+be
+copied,
+expanded
+and
+returned
+if
+there
+are
+no
+errors.
+If
+the
+expansion
+fails,
+an
+appropriate
+exception
+<em class="rfc2119" title="must">
+must
+</em>
+be
+thrown.
+<table class="parameters">
+<tr>
+<th>
+Parameter
+</th>
+<th>
+Type
+</th>
+<th>
+Nullable
+</th>
+<th>
+Optional
+</th>
+<th>
+Description
+</th>
+</tr>
+<tr>
+<td class="prmName">
+input
+</td>
+<td class="prmType">
+<code>
+<a>
+object
+or
+object[]
+or
+URL
+</a>
+</code>
+</td>
+<td class="prmNullFalse">
+✘
+</td>
+<td class="prmOptFalse">
+✘
+</td>
+<td class="prmDesc">
+The
+JSON-LD
+object
+or
+array
+of
+JSON-LD
+objects
+to
+perform
+the
+expansion
+upon
+or
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+referencing
+the
+JSON-LD
+document
+to
+expand.
+</td>
+</tr>
+<tr>
+<td class="prmName">
+context
+</td>
+<td class="prmType">
+<code>
+<a>
+object
+or
+URL
+</a>
+</code>
+</td>
+<td class="prmNullTrue">
+✔
+</td>
+<td class="prmOptFalse">
+✘
+</td>
+<td class="prmDesc">
+An
+optional
+external
+context
+to
+use
+additionally
+to
+the
+context
+embedded
+in
+<code>
+input
+</code>
+when
+expanding
+the
+<code>
+input
+</code>.
+</td>
+</tr>
+<tr>
+<td class="prmName">
+callback
+</td>
+<td class="prmType">
+<code>
+<a href="#idl-def-JsonLdCallback" class="idlType">
+<code>
+JsonLdCallback
+</code>
+</a>
+</code>
+</td>
+<td class="prmNullFalse">
+✘
+</td>
+<td class="prmOptFalse">
+✘
+</td>
+<td class="prmDesc">
+A
+callback
+that
+is
+called
+when
+processing
+is
+complete
+on
+the
+given
+<code>
+input
+</code>.
+</td>
+</tr>
+<tr>
+<td class="prmName">
+options
+</td>
+<td class="prmType">
+<code>
+<a href="#idl-def-JsonLdOptions" class="idlType">
+<code>
+JsonLdOptions
+</code>
+</a>
+</code>
+</td>
+<td class="prmNullFalse">
+✘
+</td>
+<td class="prmOptTrue">
+✔
+</td>
+<td class="prmDesc">
+A
+set
+of
+options
+that
+<em class="rfc2119" title="may">
+may
+</em>
+affect
+the
+expansion
+algorithm
+such
+as,
+e.g.,
+the
+input
+document's
+base
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+</td>
+</tr>
+</table>
+<div>
+<em>
+Return
+type:
+</em>
+<code>
+<a>
+void
+</a>
+</code>
+</div>
+</dd>
+<dt id="widl-JsonLdProcessor-fromRDF-void-QuadArray-input-JsonLdCallback-callback-JsonLdOptions-options">
+<code>
+fromRDF
+</code>
+</dt>
+<dd>
+Creates
+a
+JSON-LD
+document
+given
+an
+set
+of
+<a class="datatype idlType" title="quad" href="#idl-def-quad">
+<code>
+Quads
+</code>
+</a>.
+<table class="parameters">
+<tr>
+<th>
+Parameter
+</th>
+<th>
+Type
+</th>
+<th>
+Nullable
+</th>
+<th>
+Optional
+</th>
+<th>
+Description
+</th>
+</tr>
+<tr>
+<td class="prmName">
+input
+</td>
+<td class="prmType">
+<code>
+<a href="#idl-def-Quad" class="idlType">
+<code>
+Quad
+</code>
+</a>
+[]
+</code>
+</td>
+<td class="prmNullFalse">
+✘
+</td>
+<td class="prmOptFalse">
+✘
+</td>
+<td class="prmDesc">
+A
+<a class="tref internalDFN" title="dataset" href="#dfn-dataset">
+dataset
+</a>
+represented
+as
+an
+array
+of
+<a class="datatype idlType" title="quad" href="#idl-def-quad">
+<code>
+Quads
+</code>
+</a>.
+</td>
+</tr>
+<tr>
+<td class="prmName">
+callback
+</td>
+<td class="prmType">
+<code>
+<a href="#idl-def-JsonLdCallback" class="idlType">
+<code>
+JsonLdCallback
+</code>
+</a>
+</code>
+</td>
+<td class="prmNullFalse">
+✘
+</td>
+<td class="prmOptFalse">
+✘
+</td>
+<td class="prmDesc">
+A
+callback
+that
+is
+called
+when
+processing
+is
+complete
+on
+the
+given
+<code>
+input
+</code>.
+</td>
+</tr>
+<tr>
+<td class="prmName">
+options
+</td>
+<td class="prmType">
+<code>
+<a href="#idl-def-JsonLdOptions" class="idlType">
+<code>
+JsonLdOptions
+</code>
+</a>
+</code>
+</td>
+<td class="prmNullFalse">
+✘
+</td>
+<td class="prmOptTrue">
+✔
+</td>
+<td class="prmDesc">
+A
+set
+of
+options
+that
+will
+affect
+the
+algorithm.
+This
+includes
+<code>
+notType
+</code>,
+which
+if
+set
+to
+<a class="tref internalDFN" title="true" href="#dfn-true">
+true
+</a>
+causes
+the
+resulting
+document
+to
+use
+<code>
+rdf:type
+</code>
+as
+a
+property,
+instead
+of
+<code>
+@type
+</code>.
+</td>
+</tr>
+</table>
+<div>
+<em>
+Return
+type:
+</em>
+<code>
+<a>
+void
+</a>
+</code>
+</div>
+</dd>
+<dt id="widl-JsonLdProcessor-toRDF-void-object-or-object---or-URL-input-QuadCallback-callback-JsonLdOptions-options">
+<code>
+toRDF
+</code>
+</dt>
+<dd>
+Processes
+the
+<code>
+input
+</code>
+according
+to
+the
+<a href="#convert-to-rdf-algorithm">
+Convert
+to
+RDF
+Algorithm
+</a>,
+calling
+the
+provided
+<code>
+callback
+</code>
+for
+each
+<a class="datatype idlType" title="Quad" href="#idl-def-Quad">
+<code>
+Quad
+</code>
+</a>
+generated.
+<table class="parameters">
+<tr>
+<th>
+Parameter
+</th>
+<th>
+Type
+</th>
+<th>
+Nullable
+</th>
+<th>
+Optional
+</th>
+<th>
+Description
+</th>
+</tr>
+<tr>
+<td class="prmName">
+input
+</td>
+<td class="prmType">
+<code>
+<a>
+object
+or
+object[]
+or
+URL
+</a>
+</code>
+</td>
+<td class="prmNullFalse">
+✘
+</td>
+<td class="prmOptFalse">
+✘
+</td>
+<td class="prmDesc">
+The
+JSON-LD
+object
+or
+array
+of
+JSON-LD
+objects
+to
+convert
+to
+RDF
+or
+a
+<a href="#idl-def-URL" class="idlType">
+<code>
+URL
+</code>
+</a>
+referencing
+the
+JSON-LD
+document
+to
+convert
+to
+RDF.
+</td>
+</tr>
+<tr>
+<td class="prmName">
+callback
+</td>
+<td class="prmType">
+<code>
+<a href="#idl-def-QuadCallback" class="idlType">
+<code>
+QuadCallback
+</code>
+</a>
+</code>
+</td>
+<td class="prmNullFalse">
+✘
+</td>
+<td class="prmOptFalse">
+✘
+</td>
+<td class="prmDesc">
+A
+callback
+that
+is
+called
+when
+a
+<a class="datatype idlType" title="Quad" href="#idl-def-Quad">
+<code>
+Quad
+</code>
+</a>
+is
+created
+from
+processing
+the
+given
+<code>
+input
+</code>.
+</td>
+</tr>
+<tr>
+<td class="prmName">
+options
+</td>
+<td class="prmType">
+<code>
+<a href="#idl-def-JsonLdOptions" class="idlType">
+<code>
+JsonLdOptions
+</code>
+</a>
+</code>
+</td>
+<td class="prmNullFalse">
+✘
+</td>
+<td class="prmOptTrue">
+✔
+</td>
+<td class="prmDesc">
+A
+set
+of
+options
+that
+<em class="rfc2119" title="may">
+may
+</em>
+affect
+the
+conversion
+to
+RDF
+such
+as,
+e.g.,
+the
+input
+document's
+base
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+</td>
+</tr>
+</table>
+<div>
+<em>
+Return
+type:
+</em>
+<code>
+<a>
+void
+</a>
+</code>
+</div>
+</dd>
+</dl>
+</div>
+</div>
+<div id="callbacks" class="section">
+<h3>
+<span class="secno">
+3.3
+</span>
+Callbacks
+</h3>
+<div id="jsonldcallback" class="section">
+<h4>
+<span class="secno">
+3.3.1
+</span>
+JsonLdCallback
+</h4>
+<p>
+The
+<a href="#idl-def-JsonLdCallback" class="idlType">
+<code>
+JsonLdCallback
+</code>
+</a>
+is
+used
+to
+return
+a
+processed
+JSON-LD
+representation
+as
+the
+result
+of
+processing
+an
+API
+method.
+</p>
+    <pre class="idl"><span class="idlInterface" id="idl-def-JsonLdCallback">[<span class="extAttr">NoInterfaceObject Callback</span>]
+interface <span class="idlInterfaceID">JsonLdCallback</span> {
+<span class="idlMethod">    <span class="idlMethType"><a>void</a></span> <span class="idlMethName"><a href="#widl-JsonLdCallback-jsonLd-void-object-or-objectArray-jsonld">jsonLd</a></span> (<span class="idlParam"><span class="idlParamType"><a>object or object</a>[]</span> <span class="idlParamName">jsonld</span></span>);</span>
+};</span>
+</pre>
+<div id="methods-1" class="section">
+<h2>
+<span class="secno">
+3.3.1.1
+</span>
+Methods
+</h2>
+<dl class="methods">
+<dt id="widl-JsonLdCallback-jsonLd-void-object-or-objectArray-jsonld">
+<code>
+jsonLd
+</code>
+</dt>
+<dd>
+This
+callback
+is
+invoked
+when
+processing
+is
+complete.
+<table class="parameters">
+<tr>
+<th>
+Parameter
+</th>
+<th>
+Type
+</th>
+<th>
+Nullable
+</th>
+<th>
+Optional
+</th>
+<th>
+Description
+</th>
+</tr>
+<tr>
+<td class="prmName">
+jsonld
+</td>
+<td class="prmType">
+<code>
+<a>
+object
+or
+object
+</a>
+[]
+</code>
+</td>
+<td class="prmNullFalse">
+✘
+</td>
+<td class="prmOptFalse">
+✘
+</td>
+<td class="prmDesc">
+The
+processed
+JSON-LD
+document.
+</td>
+</tr>
+</table>
+<div>
+<em>
+Return
+type:
+</em>
+<code>
+<a>
+void
+</a>
+</code>
+</div>
+</dd>
+</dl>
+</div>
+</div>
+<div id="quadcallback" class="section">
+<h4>
+<span class="secno">
+3.3.2
+</span>
+QuadCallback
+</h4>
+<p>
+The
+<a href="#idl-def-QuadCallback" class="idlType">
+<code>
+QuadCallback
+</code>
+</a>
+is
+called
+whenever
+the
+processor
+generates
+a
+quad
+during
+the
+<code>
+quad()
+</code>
+call.
+</p>
+    <pre class="idl"><span class="idlInterface" id="idl-def-QuadCallback">[<span class="extAttr">NoInterfaceObject Callback</span>]
+interface <span class="idlInterfaceID">QuadCallback</span> {
+<span class="idlMethod">    <span class="idlMethType"><a>void</a></span> <span class="idlMethName"><a href="#widl-QuadCallback-quad-void-Quad-quad">quad</a></span> (<span class="idlParam"><span class="idlParamType"><a href="#idl-def-Quad" class="idlType"><code>Quad</code></a></span> <span class="idlParamName">quad</span></span>);</span>
+};</span>
+</pre>
+<div id="methods-2" class="section">
+<h2>
+<span class="secno">
+3.3.2.1
+</span>
+Methods
+</h2>
+<dl class="methods">
+<dt id="widl-QuadCallback-quad-void-Quad-quad">
+<code>
+quad
+</code>
+</dt>
+<dd>
+This
+callback
+is
+invoked
+whenever
+a
+quad
+is
+generated
+by
+the
+processor.
+<table class="parameters">
+<tr>
+<th>
+Parameter
+</th>
+<th>
+Type
+</th>
+<th>
+Nullable
+</th>
+<th>
+Optional
+</th>
+<th>
+Description
+</th>
+</tr>
+<tr>
+<td class="prmName">
+quad
+</td>
+<td class="prmType">
+<code>
+<a href="#idl-def-Quad" class="idlType">
+<code>
+Quad
+</code>
+</a>
+</code>
+</td>
+<td class="prmNullFalse">
+✘
+</td>
+<td class="prmOptFalse">
+✘
+</td>
+<td class="prmDesc">
+The
+quad.
+</td>
+</tr>
+</table>
+<div>
+<em>
+Return
+type:
+</em>
+<code>
+<a>
+void
+</a>
+</code>
+</div>
+</dd>
+</dl>
+</div>
+</div>
+</div>
+<div id="data-structures" class="section">
+<h3>
+<span class="secno">
+3.4
+</span>
+Data
+Structures
+</h3>
+<p>
+This
+section
+describes
+datatype
+definitions
+used
+within
+the
+JSON-LD
+API.
+</p>
+<div id="url" class="section">
+<h4>
+<span class="secno">
+3.4.1
+</span>
+URL
+</h4>
+<p>
+The
+<a href="#idl-def-URL" class="idlType">
+<code>
+URL
+</code>
+</a>
+datatype
+is
+a
+string
+representation
+of
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+</p>
+<pre class="idl">
+<span class="idlTypedef" id="idl-def-URL">
+typedef
+<span class="idlTypedefType">
+<a>
+DOMString
+</a>
+</span>
+<span class="idlTypedefID">
+URL
+</span>
+;
+</span>
+</pre>
+<div class="idlTypedefDesc">
+This
+datatype
+indicates
+that
+the
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+is
+interpreted
+as
+a
+Universal
+Resource
+Locator
+identifying
+a
+document,
+which
+when
+parsed
+as
+JSON
+yields
+either
+a
+<code>
+JSON
+object
+</code>
+or
+<code>
+array
+</code>.
+</div>
+</div>
+<div id="jsonldoptions" class="section">
+<h4>
+<span class="secno">
+3.4.2
+</span>
+JsonLdOptions
+</h4>
+<p>
+The
+<a href="#idl-def-JsonLdOptions" class="idlType">
+<code>
+JsonLdOptions
+</code>
+</a>
+type
+is
+used
+to
+convert
+a
+set
+of
+options
+to
+an
+interface
+method.
+</p>
+<pre class="idl">
+<span class="idlTypedef" id="idl-def-JsonLdOptions">
+typedef
+<span class="idlTypedefType">
+<a>
+object
+</a>
+</span>
+<span class="idlTypedefID">
+JsonLdOptions
+</span>
+;
+</span>
+</pre>
+<div class="idlTypedefDesc">
+<dt>
+<a href="#idl-def-URL" class="idlType">
+<code>
+URL
+</code>
+</a>
+base
+</dt>
+<dd>
+The
+Base
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+to
+use
+when
+expanding
+the
+document.
+This
+overrides
+the
+value
+of
+<em>
+input
+</em>
+if
+it
+is
+a
+<a href="#idl-def-URL" class="idlType">
+<code>
+URL
+</code>
+</a>
+or
+if
+it
+is
+a
+<code>
+object
+</code>
+or
+<code>
+object[]
+</code>.
+</dd>
+<dt>
+boolean
+optimize
+</dt>
+<dd>
+If
+set
+to
+<code>
+true
+</code>,
+the
+JSON-LD
+processor
+is
+allowed
+to
+optimize
+the
+output
+of
+the
+<a href="#compaction-algorithm">
+Compaction
+Algorithm
+</a>
+to
+produce
+even
+compacter
+representations.
+The
+algorithm
+for
+compaction
+optimization
+is
+beyond
+the
+scope
+of
+this
+specification
+and
+thus
+not
+defined.
+Consequently,
+different
+implementations
+<em class="rfc2119" title="may">
+may
+</em>
+implement
+different
+optimization
+algorithms.
+</dd>
+<dt>
+boolean
+noType
+</dt>
+<dd>
+If
+set
+to
+<code>
+true
+</code>,
+the
+JSON-LD
+processor
+will
+not
+use
+the
+<code>
+@type
+</code>
+property
+when
+generating
+the
+output,
+and
+will
+use
+the
+expanded
+<code>
+rdf:type
+</code>
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+as
+the
+property
+instead
+of
+<code>
+@type
+</code>.
+</dd>
+</div>
+</div>
+<p>
+The
+following
+data
+structures
+are
+used
+for
+representing
+data
+about
+RDF
+quads.
+They
+are
+used
+for
+normalization,
+<a>
+fromRDF
+</a>,
+and
+from
+<a>
+toRDF
+</a>
+interfaces.
+</p>
+<div id="quad" class="section">
+<h4>
+<span class="secno">
+3.4.3
+</span>
+Quad
+</h4>
+<p>
+The
+<a href="#idl-def-Quad" class="idlType">
+<code>
+Quad
+</code>
+</a>
+interface
+represents
+an
+RDF
+Quad.
+See
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">
+RDF-CONCEPTS
+</a>
+</cite>
+]
+definition
+for
+<cite>
+<a href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-triple">
+RDF
+triple
+</a>
+</cite>,
+which
+most
+closely
+aligns
+to
+<a href="#idl-def-Quad" class="idlType">
+<code>
+Quad
+</code>
+</a>.
+</p>
+    <pre class="idl"><span class="idlInterface" id="idl-def-Quad">[<span class="extAttr">NoInterfaceObject</span>]
+interface <span class="idlInterfaceID">Quad</span> {
+<span class="idlAttribute">    readonly attribute <span class="idlAttrType"><a href="#idl-def-Node" class="idlType"><code>Node</code></a></span>  <span class="idlAttrName"><a href="#widl-Quad-subject">subject</a></span>;</span>
+<span class="idlAttribute">    readonly attribute <span class="idlAttrType"><a href="#idl-def-Node" class="idlType"><code>Node</code></a></span>  <span class="idlAttrName"><a href="#widl-Quad-predicate">predicate</a></span>;</span>
+<span class="idlAttribute">    readonly attribute <span class="idlAttrType"><a href="#idl-def-Node" class="idlType"><code>Node</code></a></span>  <span class="idlAttrName"><a href="#widl-Quad-object">object</a></span>;</span>
+<span class="idlAttribute">    readonly attribute <span class="idlAttrType"><a href="#idl-def-Node" class="idlType"><code>Node</code></a>?</span> <span class="idlAttrName"><a href="#widl-Quad-graphName">graphName</a></span>;</span>
+};</span>
+</pre>
+<div id="attributes" class="section">
+<h2>
+<span class="secno">
+3.4.3.1
+</span>
+Attributes
+</h2>
+<dl class="attributes">
+<dt id="widl-Quad-graphName">
+<code>
+graphName
+</code>
+of
+type
+<span class="idlAttrType">
+<a href="#idl-def-Node" class="idlType">
+<code>
+Node
+</code>
+</a>
+</span>,
+readonly,
+nullable
+</dt>
+<dd>
+If
+present,
+the
+name
+associated
+with
+the
+<a href="#idl-def-Quad" class="idlType">
+<code>
+Quad
+</code>
+</a>
+identifying
+it
+as
+a
+member
+of
+a
+<a class="tref internalDFN" title="named_graph" href="#dfn-named_graph">
+named
+graph
+</a>.
+If
+it
+is
+missing,
+the
+quad
+is
+a
+member
+of
+the
+<a class="tref internalDFN" title="default_graph" href="#dfn-default_graph">
+default
+graph
+</a>.
+<div class="issue">
+<div class="issue-title">
+<span>
+Issue
+4
+</span>
+</div>
+<div class="">
+This
+element
+is
+at
+risk,
+and
+may
+be
+removed.
+</div>
+</div>
+</dd>
+<dt id="widl-Quad-object">
+<code>
+object
+</code>
+of
+type
+<span class="idlAttrType">
+<a href="#idl-def-Node" class="idlType">
+<code>
+Node
+</code>
+</a>
+</span>,
+readonly
+</dt>
+<dd>
+The
+<a class="tref internalDFN" title="object" href="#dfn-object">
+object
+</a>
+associated
+with
+the
+<a href="#idl-def-Quad" class="idlType">
+<code>
+Quad
+</code>
+</a>.
+</dd>
+<dt id="widl-Quad-predicate">
+<code>
+predicate
+</code>
+of
+type
+<span class="idlAttrType">
+<a href="#idl-def-Node" class="idlType">
+<code>
+Node
+</code>
+</a>
+</span>,
+readonly
+</dt>
+<dd>
+The
+predicate
+associated
+with
+the
+<a href="#idl-def-Quad" class="idlType">
+<code>
+Quad
+</code>
+</a>.
+Within
+JSON-LD,
+an
+<dfn title="rdf_predicate" id="dfn-rdf_predicate">
+RDF
+predicate
+</dfn>
+is
+refered
+to
+as
+a
+<a class="tref internalDFN" title="property" href="#dfn-property">
+property
+</a>
+</dd>
+<dt id="widl-Quad-subject">
+<code>
+subject
+</code>
+of
+type
+<span class="idlAttrType">
+<a href="#idl-def-Node" class="idlType">
+<code>
+Node
+</code>
+</a>
+</span>,
+readonly
+</dt>
+<dd>
+The
+<a class="tref internalDFN" title="subject" href="#dfn-subject">
+subject
+</a>
+associated
+with
+the
+<a href="#idl-def-Quad" class="idlType">
+<code>
+Quad
+</code>
+</a>.
+</dd>
+</dl>
+</div>
+</div>
+<div id="node" class="section">
+<h4>
+<span class="secno">
+3.4.4
+</span>
+Node
+</h4>
+<p>
+<a class="datatype idlType" title="Node" href="#idl-def-Node">
+<code>
+Node
+</code>
+</a>
+is
+the
+base
+class
+of
+<a class="datatype idlType" title="IRI" href="#idl-def-IRI">
+<code>
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</code>
+</a>,
+<a class="datatype idlType" title="BlankNode" href="#idl-def-BlankNode">
+<code>
+BlankNode
+</code>
+</a>,
+and
+<a class="datatype idlType" title="Literal" href="#idl-def-Literal">
+<code>
+Literal
+</code>
+</a>.
+It
+is
+the
+IDL
+representation
+of
+a
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>
+<a class="tref internalDFN" title="node" href="#dfn-node">
+node
+</a>.
+</p>
+    <pre class="idl"><span class="idlInterface" id="idl-def-Node">[<span class="extAttr">NoInterfaceObject</span>]
+interface <span class="idlInterfaceID">Node</span> {
+};</span>
+</pre>
+</div>
+<div id="iri" class="section">
+<h4>
+<span class="secno">
+3.4.5
+</span>
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</h4>
+<p>
+A
+<a class="tref internalDFN" title="node" href="#dfn-node">
+node
+</a>
+that
+is
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+</p>
+    <pre class="idl"><span class="idlInterface" id="idl-def-IRI">[<span class="extAttr">NoInterfaceObject</span>]
+interface <span class="idlInterfaceID">IRI</span> : <span class="idlSuperclass"><a href="#idl-def-Node" class="idlType"><code>Node</code></a></span> {
+<span class="idlAttribute">    readonly attribute <span class="idlAttrType"><a>DOMString</a></span> <span class="idlAttrName"><a href="#widl-IRI-value">value</a></span>;</span>
+};</span>
+</pre>
+<div id="attributes-1" class="section">
+<h2>
+<span class="secno">
+3.4.5.1
+</span>
+Attributes
+</h2>
+<dl class="attributes">
+<dt id="widl-IRI-value">
+<code>
+value
+</code>
+of
+type
+<span class="idlAttrType">
+<a>
+DOMString
+</a>
+</span>,
+readonly
+</dt>
+<dd>
+The
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+identifier
+of
+the
+<a class="tref internalDFN" title="node" href="#dfn-node">
+node
+</a>
+as
+a
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-UNICODE">
+UNICODE
+</a>
+</cite>
+]
+string.
+</dd>
+</dl>
+</div>
+</div>
+<div id="blank-node" class="section">
+<h4>
+<span class="secno">
+3.4.6
+</span>
+<dfn title="blank_node" id="dfn-blank_node">
+Blank
+Node
+</dfn>
+</h4>
+<p>
+A
+<a class="tref internalDFN" title="node" href="#dfn-node">
+node
+</a>
+in
+the
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>
+that
+does
+not
+contain
+a
+de-reference-able
+identifier
+because
+it
+is
+either
+ephemeral
+in
+nature
+or
+does
+not
+contain
+information
+that
+needs
+to
+be
+linked
+to
+from
+outside
+of
+the
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>.
+A
+blank
+node
+is
+assigned
+an
+identifier
+starting
+with
+the
+prefix
+<code>
+_:
+</code>
+and
+an
+implementation
+dependent,
+auto-generated
+suffix
+that
+is
+unique
+to
+all
+information
+associated
+with
+the
+particular
+blank
+node.
+</p>
+    <pre class="idl"><span class="idlInterface" id="idl-def-BlankNode">[<span class="extAttr">NoInterfaceObject</span>]
+interface <span class="idlInterfaceID">BlankNode</span> : <span class="idlSuperclass"><a href="#idl-def-Node" class="idlType"><code>Node</code></a></span> {
+<span class="idlAttribute">    readonly attribute <span class="idlAttrType"><a>DOMString</a></span> <span class="idlAttrName"><a href="#widl-BlankNode-identifier">identifier</a></span>;</span>
+};</span>
+</pre>
+<div id="attributes-2" class="section">
+<h2>
+<span class="secno">
+3.4.6.1
+</span>
+Attributes
+</h2>
+<dl class="attributes">
+<dt id="widl-BlankNode-identifier">
+<code>
+identifier
+</code>
+of
+type
+<span class="idlAttrType">
+<a>
+DOMString
+</a>
+</span>,
+readonly
+</dt>
+<dd>
+The
+temporary
+identifier
+of
+the
+<a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">
+blank
+node
+</a>.
+The
+<code>
+identifier
+</code>
+<em class="rfc2119" title="must not">
+must
+not
+</em>
+be
+relied
+upon
+in
+any
+way
+between
+two
+separate
+processing
+runs
+of
+the
+same
+document
+or
+with
+a
+different
+document.
+</dd>
+</dl>
+</div>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+Developers
+and
+authors
+must
+not
+assume
+that
+the
+value
+of
+a
+<a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">
+blank
+node
+</a>
+will
+remain
+the
+same
+between
+two
+processing
+runs.
+<a href="#idl-def-BlankNode" class="idlType">
+<code>
+BlankNode
+</code>
+</a>
+values
+are
+only
+valid
+for
+the
+most
+recent
+processing
+run
+on
+the
+document.
+<a href="#idl-def-BlankNode" class="idlType">
+<code>
+BlankNode
+</code>
+</a>
+values
+will
+often
+be
+generated
+differently
+by
+different
+processors.
+</p>
+</div>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+Implementers
+<em class="rfc2119" title="must">
+must
+</em>
+ensure
+that
+<a href="#idl-def-BlankNode" class="idlType">
+<code>
+BlankNode
+</code>
+</a>
+values
+are
+unique
+within
+the
+current
+environment,
+two
+<a class="datatype idlType" title="blanknode" href="#idl-def-blanknode">
+<code>
+BlankNodes
+</code>
+</a>
+are
+considered
+equal
+if,
+and
+only
+if,
+their
+values
+are
+strictly
+equal.
+</p>
+</div>
+</div>
+<div id="literal" class="section">
+<h4>
+<span class="secno">
+3.4.7
+</span>
+Literal
+</h4>
+<p>
+Literals
+represent
+values
+such
+as
+numbers,
+dates
+and
+strings
+in
+RDF
+data.
+A
+<a class="datatype idlType" title="Literal" href="#idl-def-Literal">
+<code>
+Literal
+</code>
+</a>
+is
+comprised
+of
+three
+attributes:
+</p>
+<ul>
+<li>
+a
+lexical
+form
+of
+the
+<code>
+value
+</code>
+</li>
+<li>
+an
+optional
+<code>
+language
+</code>
+tag
+</li>
+<li>
+a
+<code>
+datatype
+</code>
+specified
+by
+an
+<a class="datatype idlType" title="IRI" href="#idl-def-IRI">
+<code>
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</code>
+</a>
+</li>
+</ul>
+<p>
+Literals
+representing
+plain
+text
+in
+a
+natural
+language
+may
+have
+a
+<code>
+language
+</code>
+tag
+specified
+by
+a
+string
+token,
+as
+specified
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-BCP47">
+BCP47
+</a>
+</cite>
+],
+normalized
+to
+lowercase
+(e.g.,
+<code>
+'en'
+</code>,
+<code>
+'fr'
+</code>,
+<code>
+'en-gb'
+</code>
+).
+They
+also
+have
+a
+datatype
+attribute
+such
+as
+<code>
+xsd:string
+</code>.
+If
+unspecified,
+the
+<code>
+datatype
+</code>
+defaults
+to
+<code>
+xsd:string
+</code>.
+</p>
+<p>
+Literals
+representing
+values
+with
+a
+specific
+datatype,
+such
+as
+the
+integer
+72,
+may
+have
+a
+<code>
+datatype
+</code>
+attribute
+specified
+in
+the
+form
+of
+a
+<a href="#idl-def-IRI" class="idlType">
+<code>
+IRI
+</code>
+</a>
+(e.g.,
+<code>
+xsd:integer
+</code>
+).
+</p>
+<p>
+See[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">
+RDF-CONCEPTS
+</a>
+</cite>
+]
+definition
+for
+<cite>
+<a href="http://www.w3.org/TR/rdf11-concepts/#dfn-literal">
+literal
+</a>
+</cite>.
+</p>
+      <pre class="idl"><span class="idlInterface" id="idl-def-Literal">[<span class="extAttr">NoInterfaceObject</span>]
+interface <span class="idlInterfaceID">Literal</span> : <span class="idlSuperclass"><a href="#idl-def-Node" class="idlType"><code>Node</code></a></span> {
+<span class="idlAttribute">    readonly attribute <span class="idlAttrType"><a>DOMString</a></span>  <span class="idlAttrName"><a href="#widl-Literal-value">value</a></span>;</span>
+<span class="idlAttribute">    readonly attribute <span class="idlAttrType"><a>DOMString</a>?</span> <span class="idlAttrName"><a href="#widl-Literal-language">language</a></span>;</span>
+<span class="idlAttribute">    readonly attribute <span class="idlAttrType"><a href="#idl-def-IRI" class="idlType"><code>IRI</code></a>?</span>       <span class="idlAttrName"><a href="#widl-Literal-datatype">datatype</a></span>;</span>
+};</span>
+</pre>
+<div id="attributes-3" class="section">
+<h2>
+<span class="secno">
+3.4.7.1
+</span>
+Attributes
+</h2>
+<dl class="attributes">
+<dt id="widl-Literal-datatype">
+<code>
+datatype
+</code>
+of
+type
+<span class="idlAttrType">
+<a href="#idl-def-IRI" class="idlType">
+<code>
+IRI
+</code>
+</a>
+</span>,
+readonly,
+nullable
+</dt>
+<dd>
+An
+optional
+datatype
+identified
+by
+a
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>.
+</dd>
+<dt id="widl-Literal-language">
+<code>
+language
+</code>
+of
+type
+<span class="idlAttrType">
+<a>
+DOMString
+</a>
+</span>,
+readonly,
+nullable
+</dt>
+<dd>
+An
+optional
+language
+tag
+as
+defined
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-BCP47">
+BCP47
+</a>
+</cite>
+],
+normalized
+to
+lowercase.
+</dd>
+<dt id="widl-Literal-value">
+<code>
+value
+</code>
+of
+type
+<span class="idlAttrType">
+<a>
+DOMString
+</a>
+</span>,
+readonly
+</dt>
+<dd>
+The
+lexical
+form
+of
+the
+Literal's
+value.
+</dd>
+</dl>
+</div>
+</div>
+</div>
+</div>
+<div id="algorithms" class="section">
+<h2>
+<span class="secno">
+4.
+</span>
+Algorithms
+</h2>
+<p>
+All
+algorithms
+described
+in
+this
+section
+are
+intended
+to
+operate
+on
+language-native
+data
+structures.
+That
+is,
+the
+serialization
+to
+a
+text-based
+JSON
+document
+isn't
+required
+as
+input
+or
+output
+to
+any
+of
+these
+algorithms
+and
+language-native
+data
+structures
+<em class="rfc2119" title="must">
+must
+</em>
+be
+used
+where
+applicable.
+</p>
+<div id="algorithm-terms" class="section">
+<h3>
+<span class="secno">
+4.1
+</span>
+Algorithm
+Terms
+</h3>
+<dl>
+<dt>
+<dfn title="initial_context" id="dfn-initial_context">
+initial
+context
+</dfn>
+</dt>
+<dd>
+a
+context
+that
+is
+specified
+to
+the
+algorithm
+before
+processing
+begins.
+The
+contents
+of
+the
+initial
+context
+is
+defined
+in
+<a href="#appendix-a">
+Appendix
+A
+</a>.
+</dd>
+<dt>
+<dfn title="active_subject" id="dfn-active_subject">
+active
+subject
+</dfn>
+</dt>
+<dd>
+the
+currently
+active
+subject
+that
+the
+processor
+should
+use
+when
+processing.
+</dd>
+<dt>
+<dfn title="active_property" id="dfn-active_property">
+active
+property
+</dfn>
+</dt>
+<dd>
+the
+currently
+active
+property
+that
+the
+processor
+should
+use
+when
+processing.
+The
+active
+property
+is
+represented
+in
+the
+original
+lexical
+form,
+which
+is
+used
+for
+finding
+coercion
+mappings
+in
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>.
+</dd>
+<dt>
+<dfn title="active_object" id="dfn-active_object">
+active
+object
+</dfn>
+</dt>
+<dd>
+the
+currently
+active
+object
+that
+the
+processor
+should
+use
+when
+processing.
+</dd>
+<dt>
+<dfn title="active_context" id="dfn-active_context">
+active
+context
+</dfn>
+</dt>
+<dd>
+a
+context
+that
+is
+used
+to
+resolve
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s
+while
+the
+processing
+algorithm
+is
+running.
+The
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+is
+the
+context
+contained
+within
+the
+<a class="tref internalDFN" title="processor_state" href="#dfn-processor_state">
+processor
+state
+</a>.
+</dd>
+<dt>
+<dfn title="compact_iri" id="dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</dfn>
+</dt>
+<dd>
+a
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+is
+has
+the
+form
+of
+<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
+prefix
+</a>
+and
+<em>
+suffix
+</em>
+and
+is
+used
+as
+a
+way
+of
+expressing
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+without
+needing
+to
+define
+separate
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+definitions
+for
+each
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+contained
+within
+a
+common
+vocabulary
+identified
+by
+<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
+prefix
+</a>.
+</dd>
+<dt>
+<dfn title="local_context" id="dfn-local_context">
+local
+context
+</dfn>
+</dt>
+<dd>
+a
+context
+that
+is
+specified
+within
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>,
+specified
+via
+the
+<code>
+@context
+</code>
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>.
+</dd>
+<dt>
+<dfn title="processor_state" id="dfn-processor_state">
+processor
+state
+</dfn>
+</dt>
+<dd>
+the
+<a class="tref internalDFN" title="processor_state" href="#dfn-processor_state">
+processor
+state
+</a>,
+which
+includes
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>,
+<a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">
+active
+subject
+</a>,
+and
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>.
+The
+<a class="tref internalDFN" title="processor_state" href="#dfn-processor_state">
+processor
+state
+</a>
+is
+managed
+as
+a
+stack
+with
+elements
+from
+the
+previous
+<a class="tref internalDFN" title="processor_state" href="#dfn-processor_state">
+processor
+state
+</a>
+copied
+into
+a
+new
+<a class="tref internalDFN" title="processor_state" href="#dfn-processor_state">
+processor
+state
+</a>
+when
+entering
+a
+new
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>.
+</dd>
+<dt>
+<dfn title="json-ld_input" id="dfn-json-ld_input">
+JSON-LD
+input
+</dfn>
+</dt>
+<dd>
+The
+JSON-LD
+data
+structure
+that
+is
+provided
+as
+input
+to
+the
+algorithm.
+</dd>
+<dt>
+<dfn title="json-ld_output" id="dfn-json-ld_output">
+JSON-LD
+output
+</dfn>
+</dt>
+<dd>
+The
+JSON-LD
+data
+structure
+that
+is
+produced
+as
+output
+by
+the
+algorithm.
+</dd>
+<dt>
+<dfn title="term" id="dfn-term">
+term
+</dfn>
+</dt>
+<dd>
+A
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+is
+a
+short
+word
+defined
+in
+a
+context
+that
+<em class="rfc2119" title="may">
+may
+</em>
+be
+expanded
+to
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+</dd>
+<dt>
+<dfn title="prefix" id="dfn-prefix">
+prefix
+</dfn>
+</dt>
+<dd>
+A
+<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
+prefix
+</a>
+is
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+that
+expands
+to
+a
+vocabulary
+base
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>.
+It
+is
+typically
+used
+along
+with
+a
+<em>
+suffix
+</em>
+to
+form
+a
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+to
+create
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+within
+a
+vocabulary.
+</dd>
+<dt>
+<dfn title="language-tagged_literal" id="dfn-language-tagged_literal">
+language-tagged
+literal
+</dfn>
+</dt>
+<dd>
+A
+<a class="tref internalDFN" title="language-tagged_literal" href="#dfn-language-tagged_literal">
+language-tagged
+literal
+</a>
+is
+a
+<a class="tref internalDFN" title="literal" href="#dfn-literal">
+literal
+</a>
+without
+a
+datatype,
+including
+a
+language.
+See
+<cite>
+<a href="http://www.w3.org/TR/rdf11-concepts/#dfn-language-tagged-literal">
+languaged-tagged
+literal
+</a>
+</cite>
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">
+RDF-CONCEPTS
+</a>
+</cite>
+].
+</dd>
+<dt>
+<dfn title="typed_literal" id="dfn-typed_literal">
+typed
+literal
+</dfn>
+</dt>
+<dd>
+A
+<a class="tref internalDFN" title="typed_literal" href="#dfn-typed_literal">
+typed
+literal
+</a>
+is
+a
+<a class="tref internalDFN" title="literal" href="#dfn-literal">
+literal
+</a>
+with
+an
+associated
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+which
+indicates
+the
+literal's
+datatype.
+See
+<cite>
+<a href="http://www.w3.org/TR/rdf11-concepts/#dfn-typed-literal">
+languaged-tagged
+literal
+</a>
+</cite>
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">
+RDF-CONCEPTS
+</a>
+</cite>
+].
+</dd>
+</dl>
+</div>
+<div id="context-processing" class="section">
+<h3 id="context">
+<span class="secno">
+4.2
+</span>
+Context
+Processing
+</h3>
+<p>
+Processing
+of
+JSON-LD
+data
+structure
+is
+managed
+recursively.
+During
+processing,
+each
+rule
+is
+applied
+using
+information
+provided
+by
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>.
+Processing
+begins
+by
+pushing
+a
+new
+<a class="tref internalDFN" title="processor_state" href="#dfn-processor_state">
+processor
+state
+</a>
+onto
+the
+<a class="tref internalDFN" title="processor_state" href="#dfn-processor_state">
+processor
+state
+</a>
+stack
+and
+initializing
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+with
+the
+<a class="tref internalDFN" title="initial_context" href="#dfn-initial_context">
+initial
+context
+</a>.
+If
+a
+<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
+local
+context
+</a>
+is
+encountered,
+information
+from
+the
+<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
+local
+context
+</a>
+is
+merged
+into
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>.
+</p>
+<p>
+The
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+is
+used
+for
+expanding
+properties
+and
+values
+of
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+(or
+elements
+of
+an
+array)
+using
+a
+<dfn title="term_mapping" id="dfn-term_mapping">
+term
+mapping
+</dfn>.
+It
+is
+also
+used
+to
+maintain
+<dfn title="coercion_mapping" id="dfn-coercion_mapping">
+coercion
+mapping
+</dfn>
+s
+from
+terms
+to
+datatypes,
+<dfn title="language_mapping" id="dfn-language_mapping">
+language
+mapping
+</dfn>
+s
+from
+terms
+to
+language
+codes,
+and
+<dfn title="list_mapping" id="dfn-list_mapping">
+list
+mapping
+</dfn>
+s
+and
+<dfn title="set_mapping" id="dfn-set_mapping">
+set
+mapping
+</dfn>
+s
+for
+terms.
+Processors
+<em class="rfc2119" title="must">
+must
+</em>
+use
+the
+lexical
+form
+of
+the
+property
+when
+creating
+a
+mapping,
+as
+lookup
+is
+performed
+on
+lexical
+forms,
+not
+expanded
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+representations.
+</p>
+<p>
+A
+<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
+local
+context
+</a>
+is
+identified
+within
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+having
+a
+<code>
+@context
+</code>
+property
+with
+a
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>,
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>
+or
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+value.
+When
+processing
+a
+<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
+local
+context
+</a>,
+special
+processing
+rules
+apply:
+</p>
+<ol class="algorithm">
+<li>
+Create
+a
+new,
+empty
+<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
+local
+context
+</a>.
+</li>
+<li>
+Let
+<em>
+context
+</em>
+be
+the
+value
+of
+<code>
+@context
+</code>
+<ol class="algorithm">
+<li id="process-context">
+If
+<em>
+context
+</em>
+equals
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>,
+reset
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+to
+the
+<a class="tref internalDFN" title="initial_context" href="#dfn-initial_context">
+initial
+context
+</a>.
+</li>
+<li>
+If
+<em>
+context
+</em>
+is
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>,
+process
+each
+element
+as
+<em>
+context
+</em>
+in
+order
+by
+starting
+at
+<a href="#process-context">
+Step
+2.1
+</a>.
+</li>
+<li>
+If
+<em>
+context
+</em>
+is
+a
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>,
+it
+<em class="rfc2119" title="must">
+must
+</em>
+have
+a
+lexical
+form
+of
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+<ol class="algorithm">
+<li>
+Dereference
+<em>
+context
+</em>.
+</li>
+<li>
+If
+the
+resulting
+document
+is
+a
+JSON
+document,
+extract
+the
+top-level
+<code>
+@context
+</code>
+element
+using
+the
+JSON
+Pointer
+&quot;/@context&quot;
+as
+described
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-JSON-POINTER">
+JSON-POINTER
+</a>
+</cite>
+].
+Set
+<em>
+context
+</em>
+to
+the
+extracted
+content
+and
+process
+it
+by
+starting
+at
+<a href="#process-context">
+Step
+2.1
+</a>.
+</li>
+</ol>
+</li>
+<li>
+If
+<em>
+context
+</em>
+is
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>,
+perform
+the
+following
+steps:
+<ol class="algorithm">
+<li>
+If
+<em>
+context
+</em>
+has
+a
+<code>
+@language
+</code>
+property,
+it
+<em class="rfc2119" title="must">
+must
+</em>
+have
+a
+value
+of
+a
+simple
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>
+or
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>.
+Add
+the
+language
+to
+the
+<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
+local
+context
+</a>.
+</li>
+<li id="object-context">
+Otherwise,
+for
+each
+property
+in
+<em>
+context
+</em>
+perform
+the
+following
+steps:
+<ol class="algorithm">
+<li>
+If
+the
+property's
+value
+is
+a
+simple
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>,
+determine
+the
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+mapping
+value
+by
+performing
+<a href="#iri-expansion">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Expansion
+</a>
+on
+the
+associated
+value.
+If
+the
+result
+of
+the
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+mapping
+is
+an
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+merge
+the
+property
+into
+the
+<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
+local
+context
+</a>
+<a class="tref internalDFN" title="term_mapping" href="#dfn-term_mapping">
+term
+mapping
+</a>,
+unless
+the
+property
+is
+a
+JSON-LD
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>,
+in
+which
+case
+throw
+an
+exception.
+</li>
+<li>
+Otherwise,
+if
+the
+property's
+value
+is
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>
+remove
+mapping,
+coercion,
+container
+and
+language
+information
+associated
+with
+property
+from
+the
+<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
+local
+context
+</a>.
+</li>
+<li>
+Otherwise,
+the
+<em>
+property
+</em>
+'s
+<em>
+value
+</em>
+<em class="rfc2119" title="must">
+must
+</em>
+be
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>.
+<ol class="algorithm">
+<li>
+If
+the
+<em>
+property
+</em>
+is
+a
+JSON-LD
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>
+and
+the
+value
+has
+<code>
+@id
+</code>,
+<code>
+@language
+</code>
+or
+<code>
+@type
+</code>
+properties,
+throw
+an
+exception.
+<div class="issue">
+<div class="issue-title">
+<span>
+Issue
+5
+</span>
+</div>
+<div class="">
+Undecided
+if
+<code>
+@type
+</code>
+or
+<code>
+@graph
+</code>
+can
+take
+a
+<code>
+@container
+</code>
+with
+<code>
+@set
+</code>.
+</div>
+</div>
+</li>
+<li>
+If
+the
+<em>
+property
+</em>
+has
+the
+form
+of
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>,
+its
+<em>
+value
+</em>
+<em class="rfc2119" title="must">
+must
+</em>
+have
+an
+<code>
+@id
+</code>
+property
+with
+a
+string
+value
+which
+<em class="rfc2119" title="must">
+must
+</em>
+have
+the
+form
+of
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>,
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+or
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+Determine
+the
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+mapping
+by
+performing
+<a href="#iri-expansion">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Expansion
+</a>
+on
+the
+associated
+value.
+If
+the
+result
+of
+the
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+mapping
+is
+an
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+merge
+the
+<em>
+property
+</em>
+into
+the
+<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
+local
+context
+</a>
+<a class="tref internalDFN" title="term_mapping" href="#dfn-term_mapping">
+term
+mapping
+</a>.
+</li>
+<li>
+If
+the
+<em>
+property
+</em>
+has
+the
+form
+of
+of
+a
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+or
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+the
+<em>
+value
+</em>
+<em class="rfc2119" title="may">
+may
+</em>
+have
+a
+<code>
+@id
+</code>
+property
+with
+a
+string
+value
+which
+<em class="rfc2119" title="must">
+must
+</em>
+have
+the
+form
+of
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>,
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+or
+absolute
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+Determine
+the
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+mapping
+by
+performing
+<a href="#iri-expansion">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Expansion
+</a>
+on
+the
+associated
+value.
+If
+the
+result
+of
+the
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+mapping
+is
+an
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+merge
+the
+<em>
+property
+</em>
+into
+the
+<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
+local
+context
+</a>
+<a class="tref internalDFN" title="term_mapping" href="#dfn-term_mapping">
+term
+mapping
+</a>.
+</li>
+<li>
+If
+the
+<em>
+value
+</em>
+has
+a
+<code>
+@type
+</code>
+property,
+its
+value
+<em class="rfc2119" title="must">
+must
+</em>
+have
+the
+form
+of
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>,
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+or
+the
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>
+<code>
+@id
+</code>.
+Determine
+the
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+by
+performing
+<a href="#iri-expansion">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Expansion
+</a>
+on
+the
+associated
+value.
+If
+the
+result
+of
+the
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+mapping
+is
+an
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+or
+<code>
+@id
+</code>,
+merge
+into
+the
+<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
+local
+context
+</a>
+<a class="tref internalDFN" title="coercion_mapping" href="#dfn-coercion_mapping">
+coercion
+mapping
+</a>
+using
+the
+lexical
+value
+of
+the
+<em>
+property
+</em>.
+</li>
+<li>
+If
+the
+<em>
+value
+</em>
+has
+a
+<code>
+@container
+</code>
+property,
+its
+value
+<em class="rfc2119" title="must">
+must
+</em>
+be
+<code>
+@list
+</code>
+or
+<code>
+@set
+</code>.
+Merge
+the
+<a class="tref internalDFN" title="list_mapping" href="#dfn-list_mapping">
+list
+mapping
+</a>
+or
+<a class="tref internalDFN" title="set_mapping" href="#dfn-set_mapping">
+set
+mapping
+</a>
+into
+the
+<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
+local
+context
+</a>
+using
+the
+lexical
+value
+of
+the
+<em>
+property
+</em>.
+</li>
+<li>
+If
+the
+<em>
+value
+</em>
+has
+a
+<code>
+@language
+</code>
+property
+but
+no
+<code>
+@type
+</code>
+property,
+the
+value
+of
+the
+<code>
+@language
+</code>
+property
+<em class="rfc2119" title="must">
+must
+</em>
+be
+a
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>
+or
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>.
+Merge
+the
+<a class="tref internalDFN" title="language_mapping" href="#dfn-language_mapping">
+language
+mapping
+</a>
+into
+the
+<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
+local
+context
+</a>
+using
+the
+lexical
+value
+of
+the
+<em>
+property
+</em>.
+</li>
+</ol>
+</li>
+<li>
+Merge
+the
+<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
+local
+context
+</a>
+into
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>.
+</li>
+<li>
+Repeat
+<a href="#object-context">
+Step
+2.4.2
+</a>
+until
+no
+entries
+are
+added
+to
+the
+<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
+local
+context
+</a>.
+</li>
+</ol>
+</li>
+</ol>
+</li>
+</ol>
+</li>
+</ol>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+It
+can
+be
+difficult
+to
+distinguish
+between
+a
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+and
+an
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+as
+a
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+may
+seem
+to
+be
+a
+valid
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+<em>
+scheme
+</em>.
+When
+performing
+repeated
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+expansion,
+a
+term
+used
+as
+a
+prefix
+may
+not
+have
+a
+valid
+mapping
+due
+to
+dependencies
+in
+resolving
+term
+definitions.
+By
+continuing
+<a href="#object-context">
+Step
+2.3.2
+</a>
+until
+no
+changes
+are
+made,
+mappings
+to
+IRIs
+created
+using
+an
+undefined
+term
+prefix
+will
+eventually
+resolve
+to
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+s.
+</p>
+</div>
+<div class="issue">
+<div class="issue-title">
+<span>
+Issue
+6
+</span>
+</div>
+<p class="">
+<a href="https://github.com/json-ld/json-ld.org/issues/43">
+Issue
+43
+</a>
+concerns
+performing
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+expansion
+in
+the
+key
+position
+of
+a
+context
+definition.
+</p>
+</div>
+</div>
+<div id="iri-expansion" class="section">
+<h3>
+<span class="secno">
+4.3
+</span>
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Expansion
+</h3>
+<p>
+Keys
+and
+some
+values
+are
+evaluated
+to
+produce
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+This
+section
+defines
+an
+algorithm
+for
+transforming
+a
+value
+representing
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+into
+an
+actual
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>.
+</p>
+<p>
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+s
+may
+be
+represented
+as
+an
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+or
+a
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+</p>
+<p>
+An
+<dfn title="absolute_iri" id="dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</dfn>
+is
+defined
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RFC3987">
+RFC3987
+</a>
+</cite>
+]
+containing
+a
+<em>
+scheme
+</em>
+along
+with
+<em>
+path
+</em>
+and
+optional
+<em>
+query
+</em>
+and
+fragment
+segments.
+A
+<dfn title="relative_iri" id="dfn-relative_iri">
+relative
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</dfn>
+is
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+that
+is
+relative
+some
+other
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+;
+in
+the
+case
+of
+JSON-LD
+this
+is
+the
+base
+location
+of
+the
+document.
+</p>
+<p>
+The
+algorithm
+for
+generating
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+is:
+</p>
+<ol class="algorithm">
+<li>
+If
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+contains
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+mapping
+for
+the
+value
+using
+a
+case-sensitive
+comparison,
+use
+the
+mapped
+value
+as
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>.
+</li>
+<li>
+Otherwise,
+split
+the
+value
+into
+a
+<em>
+prefix
+</em>
+and
+<em>
+suffix
+</em>
+from
+the
+first
+occurrence
+of
+':'.
+</li>
+<li>
+If
+the
+prefix
+is
+a
+'_'
+(underscore),
+the
+value
+represents
+a
+named
+<a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">
+blank
+node
+</a>.
+</li>
+<li>
+If
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+contains
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+mapping
+for
+<em>
+prefix
+</em>
+using
+a
+case-sensitive
+comparison,
+and
+<em>
+suffix
+</em>
+does
+not
+does
+not
+begin
+with
+'//'
+(i.e.,
+it
+does
+not
+match
+a
+<em>
+hier-part
+</em>
+including
+<em>
+authority
+</em>
+(as
+defined
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RFC3986">
+RFC3986
+</a>
+</cite>
+]),
+generate
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+by
+prepending
+the
+mapped
+prefix
+to
+the
+(possibly
+empty)
+suffix
+using
+textual
+concatenation.
+Note
+that
+an
+empty
+suffix
+and
+no
+suffix
+(meaning
+the
+value
+contains
+no
+':'
+string
+at
+all)
+are
+treated
+equivalently.
+</li>
+<li>
+Otherwise,
+use
+the
+value
+directly
+as
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>.
+</li>
+</ol>
+<p>
+</p>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+Previous
+versions
+of
+this
+specification
+used
+<code>
+@base
+</code>
+and
+<code>
+@vocab
+</code>
+to
+define
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+prefixes
+used
+to
+resolve
+<a class="tref internalDFN" title="relative_iri" href="#dfn-relative_iri">
+relative
+IRIs
+</a>.
+It
+was
+determined
+that
+this
+added
+too
+much
+complexity,
+but
+the
+issue
+can
+be
+re-examined
+in
+the
+future
+based
+on
+community
+input.
+</p>
+</div>
+</div>
+<div id="iri-compaction" class="section">
+<h3>
+<span class="secno">
+4.4
+</span>
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Compaction
+</h3>
+<p>
+Some
+keys
+and
+values
+are
+expressed
+using
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+s.
+This
+section
+defines
+an
+algorithm
+for
+transforming
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+(
+<em>
+iri
+</em>
+)
+to
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+or
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+using
+the
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s
+specified
+in
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+using
+an
+optional
+<em>
+value
+</em>.
+</p>
+<div id="iri-compaction-algorithm" class="section">
+<h4>
+<span class="secno">
+4.4.1
+</span>
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Compaction
+Algorithm
+</h4>
+<p>
+The
+algorithm
+for
+generating
+a
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+is:
+</p>
+<ol class="algorithm">
+<li>
+Create
+an
+empty
+list
+of
+terms
+<em>
+terms
+</em>
+that
+will
+be
+populated
+with
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s
+that
+are
+ranked
+according
+to
+how
+closely
+they
+match
+<em>
+value
+</em>.
+Initialize
+<em>
+highest
+rank
+</em>
+to
+<code>
+0
+</code>,
+and
+set
+a
+flag
+<em>
+list
+container
+</em>
+to
+<code>
+false
+</code>.
+</li>
+<li>
+For
+each
+<em>
+term
+</em>
+in
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>:
+<ol class="algorithm">
+<li>
+If
+the
+<em>
+term
+</em>
+'s
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+is
+not
+a
+complete
+match
+against
+<em>
+iri
+</em>,
+continue
+to
+the
+next
+<em>
+term
+</em>.
+</li>
+<li>
+If
+<em>
+value
+</em>
+is
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+containing
+only
+the
+property
+<code>
+@list
+</code>:
+<ol class="algorithm">
+<li>
+If
+<em>
+term
+</em>
+has
+a
+<code>
+@container
+</code>
+set
+to
+<code>
+@set
+</code>,
+continue
+to
+the
+next
+<em>
+term
+</em>.
+</li>
+<li>
+If
+<em>
+list
+container
+</em>
+is
+<code>
+true
+</code>
+and
+<em>
+term
+</em>
+does
+not
+have
+a
+<code>
+container
+</code>
+set
+to
+<code>
+@list
+</code>,
+continue
+to
+the
+next
+<em>
+term
+</em>.
+</li>
+</ol>
+</li>
+<li>
+Otherwise,
+if
+<em>
+term
+</em>
+has
+a
+<code>
+container
+</code>
+set
+to
+<code>
+@list
+</code>,
+continue
+to
+the
+next
+<em>
+term
+</em>.
+</li>
+<li>
+Set
+<em>
+rank
+</em>
+to
+the
+<a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">
+term
+rank
+</a>
+of
+<em>
+value
+</em>
+by
+passing
+passing
+<em>
+term
+</em>,
+<em>
+value
+</em>,
+and
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+to
+the
+<a href="#term-rank-algorithm">
+Term
+Rank
+Algorithm
+</a>.
+</li>
+<li>
+If
+<em>
+rank
+</em>
+is
+greater
+than
+<code>
+0
+</code>:
+<ol class="algorithm">
+<li>
+If
+<em>
+term
+</em>
+has
+a
+<code>
+container
+</code>
+set
+to
+<code>
+@set
+</code>,
+then
+add
+<code>
+1
+</code>
+to
+<em>
+rank
+</em>.
+</li>
+<li>
+If
+<em>
+value
+</em>
+is
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+containing
+only
+the
+property
+<code>
+@list
+</code>
+and
+<em>
+list
+container
+</em>
+is
+<code>
+false
+</code>
+and
+<em>
+term
+</em>
+has
+a
+<code>
+container
+</code>
+set
+to
+<code>
+@list
+</code>,
+then
+set
+<em>
+list
+container
+</em>
+to
+<code>
+true
+</code>,
+clear
+<em>
+terms
+</em>,
+set
+<em>
+highest
+rank
+</em>
+to
+<em>
+rank
+</em>,
+and
+add
+<em>
+term
+</em>
+to
+<em>
+terms
+</em>.
+</li>
+<li>
+Otherwise,
+if
+<em>
+rank
+</em>
+is
+greater
+than
+or
+equal
+to
+<em>
+highest
+rank
+</em>:
+<ol class="algorithm">
+<li>
+If
+<em>
+rank
+</em>
+is
+greater
+than
+<em>
+highest
+rank
+</em>,
+clear
+<em>
+terms
+</em>
+and
+set
+<em>
+highest
+rank
+</em>
+to
+<em>
+rank
+</em>.
+</li>
+<li>
+Add
+<em>
+term
+</em>
+to
+<em>
+terms
+</em>.
+</li>
+</ol>
+</li>
+</ol>
+</li>
+</ol>
+</li>
+<li>
+If
+<em>
+terms
+</em>
+is
+empty,
+add
+a
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+representation
+of
+<em>
+iri
+</em>
+for
+each
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+in
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+which
+maps
+to
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+which
+is
+a
+prefix
+for
+<em>
+iri
+</em>
+where
+the
+resulting
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+is
+not
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+in
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>.
+The
+resulting
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+is
+the
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+associated
+with
+the
+partially
+matched
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+in
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+concatenated
+with
+a
+colon
+(:)
+character
+and
+the
+unmatched
+part
+of
+<em>
+iri
+</em>.
+</li>
+<li>
+If
+<em>
+terms
+</em>
+is
+empty,
+return
+<em>
+iri
+</em>.
+</li>
+<li>
+Otherwise,
+return
+the
+shortest
+and
+lexicographically
+least
+value
+in
+<em>
+terms
+</em>.
+</li>
+</ol>
+<p>
+</p>
+</div>
+<div id="term-rank-algorithm" class="section">
+<h4>
+<span class="secno">
+4.4.2
+</span>
+Term
+Rank
+Algorithm
+</h4>
+<p>
+When
+selecting
+among
+multiple
+possible
+terms
+for
+a
+given
+property,
+it
+may
+be
+that
+multiple
+<a class="tref internalDFN" title="term" href="#dfn-term">
+terms
+</a>
+are
+defined
+with
+the
+same
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+but
+differ
+in
+<code>
+@type
+</code>,
+<code>
+@container
+</code>
+or
+<code>
+@language
+</code>.
+The
+purpose
+of
+this
+algorithm
+is
+to
+take
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+and
+a
+value
+and
+give
+it
+a
+<dfn title="term_rank" id="dfn-term_rank">
+term
+rank
+</dfn>.
+The
+selection
+can
+then
+be
+based,
+partly,
+on
+the
+term
+having
+the
+highest
+<a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">
+term
+rank
+</a>.
+</p>
+<p>
+Given
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+<em>
+term
+</em>,
+<em>
+value
+</em>,
+and
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+determine
+the
+<a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">
+term
+rank
+</a>
+using
+the
+following
+steps:
+</p>
+<ol class="algorithm">
+<li>
+If
+<em>
+value
+</em>
+is
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>,
+<a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">
+term
+rank
+</a>
+is
+<code>
+3
+</code>.
+</li>
+<li>
+Otherwise,
+if
+<em>
+value
+</em>
+is
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+containing
+only
+the
+property
+<code>
+@list
+</code>:
+<ol class="algorithm">
+<li>
+If
+the
+<code>
+@list
+</code>
+property
+is
+an
+empty
+array,
+if
+<em>
+term
+</em>
+has
+<code>
+@container
+</code>
+set
+to
+<code>
+@list
+</code>,
+<a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">
+term
+rank
+</a>
+is
+<code>
+1
+</code>,
+otherwise
+<code>
+0
+</code>.
+</li>
+<li>
+Otherwise,
+return
+the
+sum
+of
+the
+<a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">
+term
+rank
+</a>
+s
+for
+every
+entry
+in
+the
+list.
+</li>
+</ol>
+</li>
+<li>
+Otherwise,
+<em>
+value
+</em>
+<em class="rfc2119" title="must">
+must
+</em>
+be
+a
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>,
+<a class="tref internalDFN" title="subject_reference" href="#dfn-subject_reference">
+subject
+reference
+</a>,
+or
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+having
+a
+<code>
+@value
+</code>.
+<ol class="algorithm">
+<li>
+If
+<em>
+value
+</em>
+has
+a
+<code>
+@value
+</code>
+property:
+<ol class="algorithm">
+<li>
+If
+<em>
+value
+</em>
+has
+a
+<code>
+@type
+</code>
+property
+matching
+a
+<code>
+@type
+</code>
+coercion
+for
+<em>
+term
+</em>,
+<a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">
+term
+rank
+</a>
+is
+<code>
+3
+</code>,
+otherwise
+if
+<em>
+term
+</em>
+has
+no
+<code>
+@type
+</code>
+coercion
+and
+no
+<code>
+@language
+</code>,
+<a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">
+term
+rank
+</a>
+is
+<code>
+1
+</code>,
+otherwise
+<code>
+0
+</code>.
+</li>
+<li>
+Otherwise,
+if
+<code>
+@value
+</code>
+is
+not
+a
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>,
+if
+<em>
+term
+</em>
+has
+no
+<code>
+@type
+</code>
+or
+<code>
+@language
+</code>
+it
+is
+<code>
+2
+</code>,
+otherwise
+<code>
+1
+</code>.
+</li>
+<li>
+Otherwise,
+if
+<em>
+value
+</em>
+has
+no
+<code>
+@language
+</code>
+property,
+if
+<em>
+term
+</em>
+has
+<code>
+@language
+</code>
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>,
+or
+<em>
+term
+</em>
+has
+no
+<code>
+@type
+</code>
+or
+<code>
+@language
+</code>
+and
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+has
+no
+<code>
+@language
+</code>,
+<a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">
+term
+rank
+</a>
+is
+<code>
+3
+</code>,
+otherwise
+<code>
+0
+</code>.
+</li>
+<li>
+Otherwise,
+if
+<em>
+value
+</em>
+has
+a
+<code>
+@language
+</code>
+property
+matching
+a
+<code>
+@language
+</code>
+definition
+for
+<em>
+term
+</em>
+(or
+<em>
+term
+</em>
+has
+no
+<code>
+@type
+</code>
+or
+<code>
+@language
+</code>
+definition
+and
+<code>
+@language
+</code>
+in
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+matches
+the
+<em>
+value
+</em>
+<code>
+@language
+</code>
+),
+<a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">
+term
+rank
+</a>
+is
+<code>
+3
+</code>,
+otherwise
+if
+<em>
+term
+</em>
+has
+no
+<code>
+@type
+</code>
+coercion
+and
+no
+<code>
+@language
+</code>,
+<a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">
+term
+rank
+</a>
+is
+<code>
+1
+</code>,
+otherwise
+<code>
+0
+</code>.
+</li>
+</ol>
+</li>
+<li>
+Otherwise,
+if
+<em>
+term
+</em>
+has
+<code>
+@type
+</code>
+coerced
+to
+<code>
+@id
+</code>,
+<a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">
+term
+rank
+</a>
+is
+<code>
+3
+</code>,
+otherwise
+if
+<em>
+term
+</em>
+has
+no
+<code>
+@type
+</code>
+coercion
+and
+no
+<code>
+@language
+</code>,
+<a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">
+term
+rank
+</a>
+is
+<code>
+1
+</code>,
+otherwise
+<code>
+0
+</code>.
+</li>
+</ol>
+</li>
+<li>
+Return
+<a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">
+term
+rank
+</a>.
+</li>
+</ol>
+</div>
+</div>
+<div id="value-expansion" class="section">
+<h3>
+<span class="secno">
+4.5
+</span>
+Value
+Expansion
+</h3>
+<p>
+Some
+values
+in
+JSON-LD
+can
+be
+expressed
+in
+a
+compact
+form.
+These
+values
+are
+required
+to
+be
+expanded
+at
+times
+when
+processing
+JSON-LD
+documents.
+</p>
+<p>
+The
+algorithm
+for
+expanding
+a
+<em>
+value
+</em>
+takes
+an
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+and
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>.
+It
+is
+implemented
+as
+follows:
+</p>
+<ol class="algorithm">
+<li>
+If
+<em>
+value
+</em>
+is
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>,
+the
+<em>
+value
+</em>
+is
+already
+expanded.
+</li>
+<li>
+If
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+is
+<code>
+@graph
+</code>
+or
+the
+target
+of
+an
+<code>
+@id
+</code>
+coercion,
+expand
+the
+value
+into
+an
+object
+with
+a
+key-value
+pair
+where
+the
+key
+is
+<code>
+@id
+</code>
+and
+the
+value
+is
+the
+expanded
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+according
+to
+the
+<a href="#iri-expansion">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Expansion
+</a>
+rules.
+</li>
+<li>
+Otherwise,
+if
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+is
+not
+a
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>,
+then
+expand
+<em>
+value
+</em>
+into
+an
+object:
+<ol class="algorithm">
+<li>
+Set
+the
+first
+key-value
+pair
+to
+<code>
+@value
+</code>
+and
+the
+unexpanded
+<em>
+value
+</em>.
+</li>
+<li>
+If
+the
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+is
+the
+target
+of
+typed
+literal
+coercion,
+set
+the
+second
+key-value
+pair
+to
+<code>
+@type
+</code>
+and
+the
+associated
+coercion
+datatype
+expanded
+according
+to
+the
+<a href="#iri-expansion">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Expansion
+</a>
+rules.
+</li>
+<li>
+Otherwise,
+if
+the
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+is
+the
+target
+of
+language
+tagging,
+set
+the
+second
+key-value
+pair
+to
+<code>
+@language
+</code>
+and
+value
+of
+the
+language
+tagging
+from
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>.
+</li>
+</ol>
+</li>
+<li>
+Otherwise,
+<em>
+value
+</em>
+is
+already
+expanded.
+</li>
+</ol>
+</div>
+<div id="value-compaction" class="section">
+<h3>
+<span class="secno">
+4.6
+</span>
+Value
+Compaction
+</h3>
+<p>
+Some
+values,
+such
+as
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+IRIs
+</a>
+and
+<a class="tref internalDFN" title="typed_literal" href="#dfn-typed_literal">
+typed
+literals
+</a>,
+may
+be
+expressed
+in
+an
+expanded
+form
+in
+JSON-LD.
+These
+values
+are
+required
+to
+be
+compacted
+at
+times
+when
+processing
+JSON-LD
+documents.
+</p>
+<p>
+The
+algorithm
+for
+compacting
+an
+expanded
+value
+<em>
+value
+</em>
+takes
+an
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+and
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>.
+It
+is
+implemented
+as
+follows:
+</p>
+<ol class="algorithm">
+<li>
+If
+<em>
+value
+</em>
+only
+has
+one
+property
+and
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+has
+no
+default
+language,
+then
+the
+compacted
+value
+is
+the
+value
+of
+<code>
+@value
+</code>.
+</li>
+<li>
+Otherwise,
+if
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+is
+<code>
+@graph
+</code>,
+the
+compacted
+value
+is
+the
+value
+associated
+with
+the
+<code>
+@id
+</code>
+key,
+processed
+according
+to
+the
+<a href="#iri-compaction">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Compaction
+</a>
+steps.
+</li>
+<li>
+Otherwise,
+if
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+contains
+a
+coercion
+target
+for
+the
+key
+that
+matches
+the
+expression
+of
+the
+value,
+compact
+the
+value
+using
+the
+following
+steps:
+<ol class="algorithm">
+<li>
+If
+the
+coercion
+target
+is
+an
+<code>
+@id
+</code>,
+the
+compacted
+value
+is
+the
+value
+associated
+with
+the
+<code>
+@id
+</code>
+key,
+processed
+according
+to
+the
+<a href="#iri-compaction">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Compaction
+</a>
+steps.
+</li>
+<li>
+If
+the
+coercion
+target
+is
+a
+<a class="tref internalDFN" title="typed_literal" href="#dfn-typed_literal">
+typed
+literal
+</a>,
+the
+compacted
+value
+is
+the
+value
+associated
+with
+the
+<code>
+@value
+</code>
+key.
+</li>
+</ol>
+</li>
+<li>
+Otherwise,
+if
+<em>
+value
+</em>
+contains
+an
+<code>
+@id
+</code>
+key,
+the
+compacted
+value
+is
+<em>
+value
+</em>
+with
+the
+value
+of
+<code>
+@id
+</code>
+processed
+according
+to
+the
+<a href="#iri-compaction">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Compaction
+</a>
+steps.
+</li>
+<li>
+Otherwise,
+if
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+contains
+a
+<code>
+@language
+</code>,
+which
+matches
+the
+<code>
+@language
+</code>
+of
+the
+value,
+or
+the
+value
+has
+only
+a
+<code>
+@value
+</code>
+key,
+the
+compacted
+value
+is
+the
+value
+associated
+with
+the
+<code>
+@value
+</code>
+key.
+</li>
+<li>
+Otherwise,
+if
+the
+value
+contains
+a
+<code>
+@type
+</code>
+key,
+the
+compacted
+value
+is
+<em>
+value
+</em>
+with
+the
+<code>
+@type
+</code>
+value
+processed
+according
+to
+the
+<a href="#iri-compaction">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Compaction
+</a>
+steps.
+</li>
+<li>
+Otherwise,
+the
+value
+is
+not
+modified.
+</li>
+</ol>
+</div>
+<div id="expansion-1" class="section">
+<h3>
+<span class="secno">
+4.7
+</span>
+Expansion
+</h3>
+<p>
+Expansion
+is
+the
+process
+of
+taking
+a
+JSON-LD
+document
+and
+applying
+a
+context
+such
+that
+all
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>,
+datatypes,
+and
+literal
+values
+are
+expanded
+so
+that
+the
+context
+is
+no
+longer
+necessary.
+JSON-LD
+document
+expansion
+is
+typically
+used
+as
+a
+part
+of
+other
+JSON-LD
+API
+methods.
+</p>
+<p>
+For
+example,
+assume
+the
+following
+JSON-LD
+input
+document:
+</p>
+<div class="example"><div class="example-title"><span>Example 13</span></div><pre class="example">{
+   &quot;@context&quot;:
+   {
+      &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+      &quot;homepage&quot;: {
+        &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+        &quot;@type&quot;, &quot;@id&quot;
+      }
+   },
+   &quot;name&quot;: &quot;Manu Sporny&quot;,
+   &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;
+}
+</pre>
+</div>
+<p>
+Running
+the
+JSON-LD
+Expansion
+algorithm
+against
+the
+JSON-LD
+input
+document
+provided
+above
+would
+result
+in
+the
+following
+output:
+</p>
+<div class="example"><div class="example-title"><span>Example 14</span></div><pre class="example">{
+   &quot;http://xmlns.com/foaf/0.1/name&quot;: &quot;Manu Sporny&quot;,
+   &quot;http://xmlns.com/foaf/0.1/homepage&quot;: {
+      &quot;@id&quot;: &quot;http://manu.sporny.org/&quot;
+   }
+}
+</pre>
+</div>
+<div id="expansion-algorithm" class="section">
+<h4>
+<span class="secno">
+4.7.1
+</span>
+Expansion
+Algorithm
+</h4>
+<p>
+The
+algorithm
+takes
+three
+input
+variables:
+an
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>,
+an
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>,
+and
+an
+<em>
+element
+</em>
+to
+be
+expanded.
+To
+begin,
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+is
+set
+to
+the
+result
+of
+performing,
+<a href="#context-processing">
+Context
+Processing
+</a>
+on
+the
+passed
+<em>
+context
+</em>,
+or
+to
+the
+<a class="tref internalDFN" title="initial_context" href="#dfn-initial_context">
+initial
+context
+</a>
+if
+<em>
+context
+</em>
+is
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>,
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+is
+set
+to
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>,
+and
+<em>
+element
+</em>
+is
+set
+to
+the
+<a class="tref internalDFN" title="json-ld_input" href="#dfn-json-ld_input">
+JSON-LD
+input
+</a>.
+</p>
+<ol class="algorithm">
+<li>
+If
+<em>
+element
+</em>
+is
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>,
+process
+each
+entry
+in
+<em>
+element
+</em>
+recursively
+using
+this
+algorithm,
+passing
+copies
+of
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+and
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>.
+If
+has
+a
+<code>
+@container
+</code>
+set
+to
+<code>
+@list
+</code>
+and
+any
+entry
+in
+<em>
+element
+</em>
+is
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>,
+or
+is
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+containing
+a
+<code>
+@list
+</code>
+property,
+throw
+an
+exception,
+as
+lists
+of
+lists
+are
+not
+allowed.
+If
+the
+expanded
+entry
+is
+null,
+drop
+it.
+If
+it's
+an
+array,
+merge
+its
+entries
+with
+<em>
+element
+</em>
+'s
+entries.
+</li>
+<li>
+Otherwise,
+if
+<em>
+element
+</em>
+is
+an
+object
+<ol class="algorithm">
+<li>
+If
+<em>
+element
+</em>
+has
+a
+<code>
+@context
+</code>
+property,
+update
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+according
+to
+the
+steps
+outlined
+in
+<a href="#context-processing">
+Context
+Processing
+</a>
+and
+remove
+the
+<code>
+@context
+</code>
+property.
+</li>
+<li>
+Then,
+proceed
+and
+process
+each
+<em>
+property
+</em>
+and
+<em>
+value
+</em>
+in
+<em>
+element
+</em>
+as
+follows:
+<ol class="algorithm">
+<li>
+Remove
+<em>
+property
+</em>
+from
+<em>
+element
+</em>,
+expand
+<em>
+property
+</em>
+according
+to
+the
+steps
+outlined
+in
+<a href="#iri-expansion">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Expansion
+</a>.
+Set
+the
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+to
+the
+original
+un-expanded
+<em>
+property
+</em>
+if
+<em>
+property
+</em>
+is
+not
+a
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>.
+</li>
+<li>
+If
+<em>
+property
+</em>
+does
+not
+expand
+to
+a
+keyword
+or
+an
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+(i.e.,
+it
+doesn't
+contain
+a
+colon),
+continue
+with
+the
+next
+property
+from
+<em>
+element
+</em>.
+</li>
+<li>
+If
+<em>
+value
+</em>
+is
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>
+and
+<em>
+property
+</em>
+is
+not
+<code>
+@value
+</code>,
+continue
+with
+the
+next
+property
+from
+<em>
+element
+</em>.
+</li>
+<li>
+If
+the
+<em>
+property
+</em>
+is
+<code>
+@id
+</code>
+the
+<em>
+value
+</em>
+<em class="rfc2119" title="must">
+must
+</em>
+be
+a
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>.
+Expand
+the
+<em>
+value
+</em>
+according
+to
+<a href="#iri-expansion">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Expansion
+</a>.
+</li>
+<li>
+Otherwise,
+if
+the
+<em>
+property
+</em>
+is
+<code>
+@type
+</code>:
+<ol class="algorithm">
+<li>
+If
+<em>
+value
+</em>
+is
+a
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>,
+expand
+according
+to
+<a href="#iri-expansion">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Expansion
+</a>.
+</li>
+<li>
+Otherwise,
+if
+<em>
+value
+</em>
+is
+a
+<a class="tref internalDFN" title="subject_reference" href="#dfn-subject_reference">
+subject
+reference
+</a>,
+the
+expanded
+value
+is
+the
+result
+of
+performing
+<a href="#iri-expansion">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Expansion
+</a>
+on
+the
+value
+of
+<code>
+@id
+</code>.
+</li>
+<li>
+Otherwise,
+if
+<em>
+value
+</em>
+is
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+Object
+</a>,
+it
+must
+be
+empty
+(used
+for
+<cite>
+<a href="../json-ld-framing/#framing">
+Framing
+</a>
+</cite>
+).
+</li>
+<li>
+Otherwise,
+if
+<em>
+value
+</em>
+is
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>,
+all
+elements
+must
+be
+either
+a
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>
+or
+<a class="tref internalDFN" title="subject_reference" href="#dfn-subject_reference">
+subject
+reference
+</a>.
+Expand
+<em>
+value
+</em>
+for
+each
+of
+its
+entries
+using
+the
+previous
+three
+steps.
+</li>
+</ol>
+</li>
+<li>
+Otherwise,
+if
+the
+<em>
+property
+</em>
+is
+<code>
+@value
+</code>
+or
+<code>
+@language
+</code>
+the
+<em>
+value
+</em>
+<em class="rfc2119" title="must not">
+must
+not
+</em>
+be
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+or
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>.
+</li>
+<li>
+Otherwise,
+if
+the
+<em>
+property
+</em>
+is
+<code>
+@list
+</code>
+or
+<code>
+@set
+</code>
+expand
+<em>
+value
+</em>
+recursively
+using
+this
+algorithm,
+passing
+copies
+of
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+and
+<em>
+active
+property
+</em>.
+If
+the
+expanded
+<em>
+value
+</em>
+is
+not
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>,
+convert
+it
+to
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>.
+If
+<em>
+property
+</em>
+is
+<code>
+@list
+</code>
+and
+any
+entry
+in
+<em>
+value
+</em>
+is
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+containing
+an
+<code>
+@list
+</code>
+property,
+throw
+an
+exception,
+as
+lists
+of
+lists
+are
+not
+supported.
+</li>
+<li>
+Otherwise,
+expand
+<em>
+value
+</em>
+recursively
+using
+this
+algorithm,
+passing
+copies
+of
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+and
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>.
+</li>
+<li>
+If
+<em>
+property
+</em>
+is
+not
+a
+keyword
+and
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+has
+a
+<code>
+@container
+</code>
+<code>
+@list
+</code>
+and
+the
+expanded
+<em>
+value
+</em>
+is
+not
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>,
+convert
+<em>
+value
+</em>
+to
+an
+<a class="tref internalDFN" title="object" href="#dfn-object">
+object
+</a>
+with
+an
+<code>
+@list
+</code>
+property
+whose
+value
+is
+set
+to
+<em>
+value
+</em>
+(unless
+<em>
+value
+</em>
+is
+already
+in
+that
+form).
+</li>
+<li>
+Convert
+<em>
+value
+</em>
+to
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>
+form
+unless
+<em>
+value
+</em>
+is
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>
+or
+<em>
+property
+</em>
+is
+<code>
+@id
+</code>,
+<code>
+@type
+</code>,
+<code>
+@value
+</code>,
+or
+<code>
+@language
+</code>.
+</li>
+<li>
+If
+<em>
+value
+</em>
+is
+not
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>,
+either
+merge
+<em>
+value
+</em>
+into
+an
+existing
+<em>
+property
+</em>
+property
+of
+<em>
+element
+</em>
+or
+create
+a
+new
+<em>
+property
+</em>
+property
+with
+<em>
+value
+</em>
+as
+value.
+</li>
+</ol>
+</li>
+<li>
+If
+the
+processed
+<em>
+element
+</em>
+has
+an
+<code>
+@value
+</code>
+property
+<ol class="algorithm">
+<li>
+<em>
+element
+</em>
+<em class="rfc2119" title="must not">
+must
+not
+</em>
+have
+more
+than
+one
+other
+property,
+which
+can
+either
+be
+<code>
+@language
+</code>
+or
+<code>
+@type
+</code>
+with
+a
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>
+value.
+</li>
+<li>
+if
+the
+value
+of
+<code>
+@value
+</code>
+equals
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>,
+replace
+<em>
+element
+</em>
+with
+the
+value
+of
+<code>
+@value
+</code>.
+</li>
+</ol>
+</li>
+<li>
+Otherwise,
+if
+<em>
+element
+</em>
+has
+an
+<code>
+@type
+</code>
+property
+and
+its
+value
+is
+not
+in
+the
+form
+of
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>,
+convert
+it
+to
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>.
+</li>
+<li>
+If
+<em>
+element
+</em>
+has
+an
+<code>
+@set
+</code>
+or
+<code>
+@list
+</code>
+property,
+it
+<em class="rfc2119" title="must">
+must
+</em>
+be
+the
+only
+property.
+Set
+<em>
+element
+</em>
+to
+the
+value
+of
+<code>
+@set
+</code>
+;
+leave
+<code>
+@list
+</code>
+untouched.
+</li>
+<li>
+If
+<em>
+element
+</em>
+has
+just
+a
+<code>
+@language
+</code>
+property,
+set
+<em>
+element
+</em>
+to
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>.
+</li>
+</ol>
+</li>
+<li>
+Otherwise,
+expand
+<em>
+element
+</em>
+according
+to
+the
+<a href="#value-expansion">
+Value
+Expansion
+</a>
+rules,
+passing
+copies
+of
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+and
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>.
+</li>
+</ol>
+<p>
+If,
+after
+the
+algorithm
+outlined
+above
+is
+run,
+the
+resulting
+<em>
+element
+</em>
+is
+an
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+with
+just
+a
+<code>
+@graph
+</code>
+property,
+<em>
+element
+</em>
+is
+set
+to
+the
+value
+of
+<code>
+@graph
+</code>
+'s
+value.
+Finally,
+if
+<em>
+element
+</em>
+is
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>,
+it
+is
+wrapped
+into
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>.
+</p>
+</div>
+</div>
+<div id="compaction-1" class="section">
+<h3>
+<span class="secno">
+4.8
+</span>
+Compaction
+</h3>
+<p>
+Compaction
+is
+the
+process
+of
+taking
+a
+JSON-LD
+document
+and
+applying
+a
+context
+such
+that
+the
+most
+compact
+form
+of
+the
+document
+is
+generated.
+JSON
+is
+typically
+expressed
+in
+a
+very
+compact,
+key-value
+format.
+That
+is,
+full
+IRIs
+are
+rarely
+used
+as
+keys.
+At
+times,
+a
+JSON-LD
+document
+may
+be
+received
+that
+is
+not
+in
+its
+most
+compact
+form.
+JSON-LD,
+via
+the
+API,
+provides
+a
+way
+to
+compact
+a
+JSON-LD
+document.
+</p>
+<p>
+For
+example,
+assume
+the
+following
+JSON-LD
+input
+document:
+</p>
+<div class="example"><div class="example-title"><span>Example 15</span></div><pre class="example">{
+  &quot;http://xmlns.com/foaf/0.1/name&quot;: &quot;Manu Sporny&quot;,
+  &quot;http://xmlns.com/foaf/0.1/homepage&quot;: {
+    &quot;@id&quot;: &quot;http://manu.sporny.org/&quot;
+  }
+}
+</pre>
+</div>
+<p>
+Additionally,
+assume
+the
+following
+developer-supplied
+JSON-LD
+context:
+</p>
+<div class="example"><div class="example-title"><span>Example 16</span></div><pre class="example">{
+  &quot;@context&quot;: {
+    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+    &quot;homepage&quot;: {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    }
+  }
+}
+</pre>
+</div>
+<p>
+Running
+the
+JSON-LD
+Compaction
+algorithm
+given
+the
+context
+supplied
+above
+against
+the
+JSON-LD
+input
+document
+provided
+above
+would
+result
+in
+the
+following
+output:
+</p>
+<div class="example"><div class="example-title"><span>Example 17</span></div><pre class="example">{
+  &quot;@context&quot;: {
+    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+    &quot;homepage&quot;: {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    }
+  },
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;
+}
+</pre>
+</div>
+<p>
+The
+compaction
+algorithm
+also
+enables
+the
+developer
+to
+map
+any
+expanded
+format
+into
+an
+application-specific
+compacted
+format.
+While
+the
+context
+provided
+above
+mapped
+<code>
+http://xmlns.com/foaf/0.1/name
+</code>
+to
+<strong>
+name
+</strong>,
+it
+could
+have
+also
+mapped
+it
+to
+any
+arbitrary
+string
+provided
+by
+the
+developer.
+</p>
+<div id="compaction-algorithm" class="section">
+<h4>
+<span class="secno">
+4.8.1
+</span>
+Compaction
+Algorithm
+</h4>
+<p>
+The
+algorithm
+takes
+three
+input
+variables:
+an
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>,
+an
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>,
+and
+an
+<em>
+element
+</em>
+to
+be
+compacted.
+To
+begin,
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+is
+set
+to
+the
+result
+of
+performing
+<a href="#context-processing">
+Context
+Processing
+</a>
+on
+the
+passed
+<em>
+context
+</em>,
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+is
+set
+to
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>,
+and
+<em>
+element
+</em>
+is
+set
+to
+the
+result
+of
+performing
+the
+<a href="#expansion-algorithm">
+Expansion
+Algorithm
+</a>
+on
+the
+<a class="tref internalDFN" title="json-ld_input" href="#dfn-json-ld_input">
+JSON-LD
+input
+</a>.
+This
+removes
+any
+existing
+context
+to
+allow
+the
+given
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+to
+be
+cleanly
+applied.
+</p>
+<ol class="algorithm">
+<li>
+If
+<em>
+element
+</em>
+is
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>,
+process
+each
+entry
+in
+<em>
+element
+</em>
+recursively
+using
+this
+algorithm,
+passing
+a
+copy
+of
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+and
+the
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>.
+If
+<em>
+element
+</em>
+has
+a
+single
+item,
+the
+compacted
+value
+is
+that
+item;
+otherwise
+the
+compacted
+value
+is
+<em>
+element
+</em>.
+</li>
+<li>
+Otherwise,
+if
+<em>
+element
+</em>
+is
+an
+object:
+<ol class="algorithm">
+<li>
+If
+<em>
+element
+</em>
+has
+an
+<code>
+@value
+</code>
+property
+or
+element
+is
+a
+<a class="tref internalDFN" title="subject_reference" href="#dfn-subject_reference">
+subject
+reference
+</a>,
+return
+the
+result
+of
+performing
+<a href="#value-compaction">
+Value
+Compaction
+</a>
+on
+<em>
+element
+</em>
+using
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>.
+</li>
+<li>
+Otherwise,
+if
+the
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+has
+a
+<code>
+@container
+</code>
+mapping
+to
+<code>
+@list
+</code>
+and
+<em>
+element
+</em>
+has
+a
+corresponding
+<code>
+@list
+</code>
+property,
+recursively
+compact
+that
+property's
+value
+passing
+a
+copy
+of
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+and
+the
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+ensuring
+that
+the
+result
+is
+an
+array
+and
+removing
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>
+values.
+Return
+either
+the
+result
+as
+an
+array,
+as
+an
+object
+with
+a
+key
+of
+<code>
+@list
+</code>
+(or
+appropriate
+alias
+from
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+).
+</li>
+<li>
+Otherwise,
+construct
+<em>
+output
+</em>
+as
+a
+new
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+used
+for
+returning
+the
+result
+of
+compacting
+<em>
+element
+</em>.
+For
+each
+<em>
+property
+</em>
+and
+<em>
+value
+</em>
+in
+<em>
+element:
+</em>
+<ol class="algorithm">
+<li>
+If
+<em>
+property
+</em>
+is
+<code>
+@id
+</code>
+or
+<code>
+@type
+</code>
+<ol class="algorithm">
+<li>
+Set
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+to
+the
+result
+of
+performing
+<a href="#iri-compaction">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Compaction
+</a>
+on
+<em>
+property
+</em>.
+</li>
+<li>
+If
+<em>
+value
+</em>
+is
+a
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>,
+the
+compacted
+<em>
+value
+</em>
+is
+the
+result
+of
+performing
+<a href="#iri-compaction">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Compaction
+</a>
+on
+<em>
+value
+</em>.
+</li>
+<li>
+Otherwise,
+<em>
+value
+</em>
+<em class="rfc2119" title="must">
+must
+</em>
+be
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>.
+Perform
+<a href="#iri-compaction">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Compaction
+</a>
+on
+every
+entry
+of
+<em>
+value
+</em>.
+If
+<em>
+value
+</em>
+contains
+just
+one
+entry,
+<em>
+value
+</em>
+is
+set
+to
+that
+entry.
+</li>
+<li>
+Add
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+and
+the
+expanded
+<em>
+value
+</em>
+to
+<em>
+output
+</em>.
+</li>
+</ol>
+</li>
+<li>
+Otherwise,
+<em>
+value
+</em>
+<em class="rfc2119" title="must">
+must
+</em>
+be
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>.
+</li>
+<li>
+If
+<em>
+value
+</em>
+is
+empty:
+<ol class="algorithm">
+<li>
+Set
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+to
+the
+result
+of
+performing
+<a href="#iri-compaction">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Compaction
+</a>
+on
+<em>
+property
+</em>.
+</li>
+<li>
+Create
+an
+entry
+in
+<em>
+output
+</em>
+for
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+and
+<em>
+value
+</em>.
+</li>
+</ol>
+</li>
+<li>
+For
+each
+<em>
+item
+</em>
+in
+<em>
+value
+</em>:
+<ol class="algorithm">
+<li>
+Set
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+to
+the
+result
+of
+performing
+<a href="#iri-compaction">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Compaction
+</a>
+for
+<em>
+property
+</em>
+and
+<em>
+item
+</em>
+using
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>.
+</li>
+<li>
+Compact
+<em>
+item
+</em>
+by
+recursively
+performing
+this
+algorithm
+passing
+a
+copy
+of
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+and
+the
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>.
+</li>
+<li>
+If
+an
+entry
+already
+exists
+in
+<em>
+output
+</em>
+for
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>,
+convert
+it
+to
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>
+if
+necessary,
+and
+append
+the
+compacted
+<em>
+value
+</em>.
+</li>
+<li>
+Otherwise,
+if
+the
+compacted
+<em>
+value
+</em>
+is
+not
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>
+and
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+has
+a
+<code>
+@container
+</code>
+mapping
+to
+<code>
+@set
+</code>,
+create
+an
+entry
+in
+<em>
+output
+</em>
+for
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+and
+<em>
+value
+</em>
+as
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>.
+</li>
+<li>
+Otherwise,
+create
+an
+entry
+in
+<em>
+output
+</em>
+for
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+and
+<em>
+value
+</em>.
+</li>
+</ol>
+</li>
+</ol>
+</li>
+</ol>
+</li>
+<li>
+Otherwise,
+return
+<em>
+element
+</em>
+as
+the
+compacted
+<em>
+element
+</em>.
+<div class="issue">
+<div class="issue-title">
+<span>
+Issue
+7
+</span>
+</div>
+<div class="">
+Perhaps
+this
+should
+also
+call
+<a href="#value-compaction">
+Value
+Compaction
+</a>
+on
+native
+types
+and
+strings,
+which
+could
+consolidate
+potential
+transformation
+in
+one
+place.
+</div>
+</div>
+</li>
+</ol>
+<p>
+If,
+after
+the
+algorithm
+outlined
+above
+is
+run,
+the
+resulting
+<em>
+element
+</em>
+is
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>,
+put
+<em>
+element
+</em>
+into
+the
+<code>
+@graph
+</code>
+property
+of
+a
+new
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+and
+then
+set
+<em>
+element
+</em>
+to
+that
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>.
+Finally,
+add
+a
+<code>
+@context
+</code>
+property
+to
+<em>
+element
+</em>
+and
+set
+it
+to
+the
+initially
+passed
+<em>
+context
+</em>.
+</p>
+</div>
+</div>
+<div id="rdf-conversion" class="section">
+<h3>
+<span class="secno">
+4.9
+</span>
+RDF
+Conversion
+</h3>
+<p>
+A
+JSON-LD
+document
+<em class="rfc2119" title="may">
+may
+</em>
+be
+converted
+between
+other
+RDF-compatible
+document
+formats
+using
+the
+algorithms
+specified
+in
+this
+section.
+</p>
+<p>
+The
+JSON-LD
+Processing
+Model
+describes
+processing
+rules
+for
+extracting
+RDF
+from
+a
+JSON-LD
+document,
+and
+for
+transforming
+an
+array
+of
+<a href="#idl-def-Quad" class="idlType">
+<code>
+Quad
+</code>
+</a>
+retrieved
+by
+processing
+another
+serialization
+format
+into
+JSON-LD.
+Note
+that
+many
+uses
+of
+JSON-LD
+may
+not
+require
+generation
+of
+RDF.
+</p>
+<p>
+The
+processing
+algorithms
+described
+in
+this
+section
+are
+provided
+in
+order
+to
+demonstrate
+how
+one
+might
+implement
+a
+JSON-LD
+to
+RDF
+processor.
+Conformant
+implementations
+are
+only
+required
+to
+produce
+the
+same
+type
+and
+number
+of
+quads
+during
+the
+output
+process
+and
+are
+not
+required
+to
+implement
+the
+algorithm
+exactly
+as
+described.
+</p>
+<div class="informative section" id="overview">
+<h4>
+<span class="secno">
+4.9.1
+</span>
+Overview
+</h4>
+<p>
+<em>
+This
+section
+is
+non-normative.
+</em>
+</p>
+<p>
+JSON-LD
+is
+intended
+to
+have
+an
+easy
+to
+parse
+grammar
+that
+closely
+models
+existing
+practice
+in
+using
+JSON
+for
+describing
+object
+representations.
+This
+allows
+the
+use
+of
+existing
+libraries
+for
+parsing
+JSON.
+</p>
+<p>
+As
+with
+other
+grammars
+used
+for
+describing
+<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
+Linked
+Data
+</a>,
+a
+key
+concept
+is
+that
+of
+a
+<a class="tref internalDFN" title="node" href="#dfn-node">
+node
+</a>
+in
+a
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>.
+Nodes
+may
+be
+of
+three
+basic
+types.
+The
+first
+is
+the
+<a class="datatype idlType" title="IRI" href="#idl-def-IRI">
+<code>
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</code>
+</a>,
+which
+is
+used
+to
+refer
+to
+<a class="tref internalDFN" title="node" href="#dfn-node">
+node
+</a>
+s
+in
+other
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>
+s.
+The
+second
+is
+the
+<a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">
+blank
+node
+</a>,
+which
+are
+nodes
+for
+which
+an
+external
+name
+does
+not
+exist,
+or
+is
+not
+known.
+The
+third
+is
+a
+<a class="tref internalDFN" title="literal" href="#dfn-literal">
+Literal
+</a>,
+which
+express
+values
+such
+as
+strings,
+dates
+and
+other
+information
+having
+a
+lexical
+form,
+possibly
+including
+an
+explicit
+language
+or
+datatype.
+</p>
+<p>
+Data
+described
+with
+JSON-LD
+may
+be
+considered
+to
+be
+a
+graph
+made
+up
+of
+<a class="tref internalDFN" title="subject" href="#dfn-subject">
+subject
+</a>
+and
+<a class="tref internalDFN" title="object" href="#dfn-object">
+object
+</a>
+<a class="tref internalDFN" title="node" href="#dfn-node">
+nodes
+</a>
+related
+via
+a
+<a class="tref internalDFN" title="property" href="#dfn-property">
+property
+</a>
+<a class="tref internalDFN" title="node" href="#dfn-node">
+node
+</a>.
+Specific
+implementations
+may
+also
+choose
+to
+operate
+on
+the
+document
+as
+a
+normal
+JSON
+description
+of
+objects
+having
+attributes.
+Both
+approaches
+are
+valid
+ways
+to
+interact
+with
+JSON-LD
+documents.
+</p>
+</div>
+<div class="informative section" id="parsing-examples">
+<h4>
+<span class="secno">
+4.9.2
+</span>
+Parsing
+Examples
+</h4>
+<p>
+<em>
+This
+section
+is
+non-normative.
+</em>
+</p>
+<p>
+The
+following
+examples
+show
+simple
+transformations
+of
+JSON-LD
+documents
+to
+Turtle
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-TURTLE-TR">
+TURTLE-TR
+</a>
+</cite>
+].
+</p>
+<p>
+The
+first
+example
+uses
+a
+simple
+document
+containing
+a
+simple
+FOAF
+profile:
+</p>
+<div class="example"><div class="example-title"><span>Example 18</span></div><pre class="example">{
+  &quot;@context&quot;: {&quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;},
+  &quot;@id&quot;: &quot;http://greggkellogg.net/foaf#me&quot;,
+  &quot;@type&quot;: &quot;foaf:Person&quot;,
+  &quot;foaf:name&quot;: &quot;Gregg Kellogg&quot;,
+  &quot;foaf:knows&quot;: {
+    &quot;@type&quot;: &quot;foaf:Person&quot;,
+    &quot;foaf:name&quot;: &quot;Manu Sporny&quot;
+  }
+}
+</pre>
+</div>
+<p>
+This
+translates
+fairly
+directly
+to
+a
+similar
+Turtle
+document:
+</p>
+<div class="example"><div class="example-title"><span>Example 19</span></div><pre class="example">@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt;.
+&lt;http://greggkellogg.net/foaf#me&gt; a foaf:Person;
+  foaf:name &quot;Gregg Kellogg&quot;;
+foaf:knows
+[
+a
+foaf:Person;
+foaf:name
+&quot;Manu
+Sporny&quot;].
+</pre>
+</div>
+<p>
+The
+actual
+parsing
+steps
+first
+require
+that
+the
+JSON-LD
+document
+be
+expanded,
+to
+eliminate
+the
+<code>
+@context
+</code>:
+</p>
+<div class="example"><div class="example-title"><span>Example 20</span></div><pre class="example">[{
+  &quot;@id&quot;: &quot;http://greggkellogg.net/foaf#me&quot;,
+  &quot;@type&quot;: [&quot;http://xmlns.com/foaf/0.1/Person&quot;],
+  &quot;http://xmlns.com/foaf/0.1/name&quot;: [{&quot;@value&quot;: &quot;Gregg Kellogg&quot;}],
+  &quot;http://xmlns.com/foaf/0.1/knows&quot;: [{
+    &quot;@type&quot;: [&quot;http://xmlns.com/foaf/0.1/Person&quot;],
+    &quot;http://xmlns.com/foaf/0.1/name&quot;: [{&quot;@value&quot;: &quot;Manu Sporny&quot;}]
+  }]
+}]
+</pre>
+</div>
+<p>
+The
+process
+of
+translating
+this
+to
+RDF
+then
+operates
+over
+each
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>
+to
+find
+a
+subject,
+each
+<a class="tref internalDFN" title="property" href="#dfn-property">
+property
+</a>
+to
+find
+an
+RDF
+<em>
+predicate
+</em>,
+and
+each
+value
+of
+that
+property
+to
+find
+an
+<a class="tref internalDFN" title="object" href="#dfn-object">
+object
+</a>.
+In
+this
+case,
+each
+property
+has
+just
+a
+single
+object:
+<code>
+foaf:name
+</code>
+identifies
+a
+<a class="tref internalDFN" title="literal" href="#dfn-literal">
+literal
+</a>,
+and
+<code>
+foaf:knows
+</code>
+identifies
+a
+second
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>
+similar
+to
+Turtle's
+<code>
+blankNodePropertyList
+</code>.
+</p>
+<p>
+After
+expansion,
+JSON-LD
+<a class="tref internalDFN" title="number" href="#dfn-number">
+numbers
+</a>,
+<a class="tref internalDFN" title="true" href="#dfn-true">
+booleans
+</a>,
+typed-
+and
+language-tagged-
+<a class="tref internalDFN" title="literal" href="#dfn-literal">
+literals
+</a>,
+and
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+IRIs
+</a>
+become
+explicit,
+and
+can
+be
+directly
+transformed
+into
+their
+RDF
+representations.
+</p>
+<div class="example"><div class="example-title"><span>Example 21</span></div><pre class="example">[{
+  &quot;@id&quot;: &quot;http://greggkellogg.net/foaf#me&quot;,
+  &quot;@type&quot;: [&quot;http://xmlns.com/foaf/0.1/Person&quot;],
+  &quot;http://xmlns.com/foaf/0.1/name&quot;: [{&quot;@value&quot;: &quot;Gregg Kellogg&quot;}],
+  <span class="diff">&quot;http://xmlns.com/foaf/0.1/currentProject&quot;: [{&quot;@id&quot;: &quot;http://json-ld.org/&quot;}],
+  &quot;http://xmlns.com/foaf/0.1/birthday&quot;: [{
+    &quot;@value&quot;: &quot;1957-02-27&quot;,
+    &quot;@type&quot;: &quot;http://www.w3.org/2001/XMLSchema#date&quot;
+  }],</span>
+  &quot;http://xmlns.com/foaf/0.1/knows&quot;: [{
+    &quot;@type&quot;: [&quot;http://xmlns.com/foaf/0.1/Person&quot;],
+    &quot;http://xmlns.com/foaf/0.1/name&quot;: [{&quot;@value&quot;: &quot;Manu Sporny&quot;}]
+  }]
+}]
+</pre>
+</div>
+<p>
+Translates
+to:
+</p>
+<div class="example"><div class="example-title"><span>Example 22</span></div><pre class="example">@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt;.
+@prefix xsd: &lt;http://www.w3.org/2001/XMLSchema#&gt;.
+&lt;http://greggkellogg.net/foaf#me&gt; a foaf:Person;
+  foaf:name &quot;Gregg Kellogg&quot;;
+  <span class="diff">foaf:currentProject &lt;http://json-ld.org/&gt;;
+  foaf:birthday &quot;1957-02-27&quot;^^xsd:date;</span>
+foaf:knows
+[
+a
+foaf:Person;
+foaf:name
+&quot;Manu
+Sporny&quot;].
+</pre>
+</div>
+</div>
+<div id="convert-to-rdf-algorithm" class="section">
+<h4>
+<span class="secno">
+4.9.3
+</span>
+Convert
+to
+RDF
+Algorithm
+</h4>
+<p>
+The
+algorithm
+below
+is
+designed
+for
+in-memory
+implementations
+with
+random
+access
+to
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+elements.
+</p>
+<p>
+A
+conforming
+JSON-LD
+processor
+implementing
+RDF
+conversion
+<em class="rfc2119" title="must">
+must
+</em>
+implement
+a
+processing
+algorithm
+that
+results
+in
+the
+same
+set
+of
+RDF
+<a class="tref internalDFN" title="quad" href="#dfn-quad">
+Quads
+</a>
+that
+the
+following
+algorithm
+generates:
+</p>
+<p>
+The
+algorithm
+takes
+five
+input
+variables:
+a
+<em>
+element
+</em>
+to
+be
+converted,
+an
+<a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">
+active
+subject
+</a>,
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+and
+<a class="tref internalDFN" title="graph_name" href="#dfn-graph_name">
+graph
+name
+</a>.
+To
+begin,
+the
+<a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">
+active
+subject
+</a>,
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+and
+<a class="tref internalDFN" title="graph_name" href="#dfn-graph_name">
+graph
+name
+</a>
+are
+set
+to
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>,
+and
+<em>
+element
+</em>
+is
+set
+to
+the
+result
+of
+performing
+the
+<a href="#expansion-algorithm">
+Expansion
+Algorithm
+</a>
+on
+the
+<a class="tref internalDFN" title="json-ld_input" href="#dfn-json-ld_input">
+JSON-LD
+input
+</a>.
+This
+removes
+any
+existing
+context
+to
+allow
+the
+given
+context
+to
+be
+cleanly
+applied.
+</p>
+<ol class="algorithm">
+<li id="processing-step-associative">
+If
+<em>
+element
+</em>
+is
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>,
+perform
+the
+following
+steps:
+<ol class="algorithm">
+<li>
+Set
+<a class="tref internalDFN" title="active_object" href="#dfn-active_object">
+active
+object
+</a>
+to
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>.
+</li>
+<li>
+If
+<em>
+element
+</em>
+has
+a
+<code>
+@value
+</code>
+property:
+<ol class="algorithm">
+<li>
+If
+the
+value
+of
+<code>
+@value
+</code>
+is
+a
+<a class="tref internalDFN" title="number" href="#dfn-number">
+number
+</a>,
+set
+the
+<a class="tref internalDFN" title="active_object" href="#dfn-active_object">
+active
+object
+</a>
+to
+a
+<a class="tref internalDFN" title="typed_literal" href="#dfn-typed_literal">
+typed
+literal
+</a>
+using
+a
+string
+representation
+of
+the
+value
+as
+defined
+in
+the
+section
+<a href="#data-round-tripping">
+Data
+Round
+Tripping
+</a>.
+Set
+datatype
+to
+the
+value
+of
+the
+<code>
+@type
+</code>
+property
+if
+it
+exists,
+otherwise
+either
+<code>
+xsd:integer
+</code>
+or
+<code>
+xsd:double
+</code>,
+depending
+on
+if
+the
+value
+contains
+a
+fractional
+and/or
+an
+exponential
+component.
+</li>
+<li>
+Otherwise,
+if
+the
+value
+of
+<code>
+@value
+</code>
+is
+<strong>
+true
+</strong>
+or
+<strong>
+false
+</strong>,
+set
+the
+<a class="tref internalDFN" title="active_object" href="#dfn-active_object">
+active
+object
+</a>
+to
+a
+<a class="tref internalDFN" title="typed_literal" href="#dfn-typed_literal">
+typed
+literal
+</a>
+created
+from
+the
+string
+representation
+of
+the
+value.
+Set
+datatype
+to
+the
+value
+of
+the
+<code>
+@type
+</code>
+property
+if
+it
+exists,
+otherwise
+<code>
+xsd:boolean
+</code>.
+</li>
+<li>
+Otherwise,
+if
+<em>
+element
+</em>
+contains
+a
+<code>
+@type
+</code>
+property,
+set
+the
+<a class="tref internalDFN" title="active_object" href="#dfn-active_object">
+active
+object
+</a>
+to
+a
+<a class="tref internalDFN" title="typed_literal" href="#dfn-typed_literal">
+typed
+literal
+</a>.
+</li>
+<li>
+Otherwise,
+if
+<em>
+element
+</em>
+contains
+a
+<code>
+@language
+</code>
+property,
+set
+the
+<a class="tref internalDFN" title="active_object" href="#dfn-active_object">
+active
+object
+</a>
+to
+a
+<a class="tref internalDFN" title="language-tagged_literal" href="#dfn-language-tagged_literal">
+language-tagged
+literal
+</a>.
+</li>
+<li>
+Otherwise,
+set
+the
+<a class="tref internalDFN" title="active_object" href="#dfn-active_object">
+active
+object
+</a>
+to
+a
+<a class="tref internalDFN" title="typed_literal" href="#dfn-typed_literal">
+typed
+literal
+</a>
+using
+<code>
+xsd:string
+</code>
+as
+the
+datatype.
+</li>
+</ol>
+</li>
+<li>
+If
+<em>
+element
+</em>
+has
+a
+<code>
+@list
+</code>
+property
+the
+value
+<em class="rfc2119" title="must">
+must
+</em>
+be
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>.
+Process
+its
+value
+as
+a
+list
+as
+described
+in
+<a href="#list-conversion">
+List
+Conversion
+</a>
+using
+the
+return
+value
+as
+the
+<a class="tref internalDFN" title="active_object" href="#dfn-active_object">
+active
+object
+</a>
+</li>
+<li>
+If
+<a class="tref internalDFN" title="active_object" href="#dfn-active_object">
+active
+object
+</a>
+is
+not
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>:
+<ol class="algorithm">
+<li>
+If
+neither
+<a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">
+active
+subject
+</a>
+nor
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+are
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>,
+generate
+a
+<a href="#idl-def-Quad" class="idlType">
+<code>
+Quad
+</code>
+</a>
+representing
+<a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">
+active
+subject
+</a>,
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>,
+<a class="tref internalDFN" title="active_object" href="#dfn-active_object">
+active
+object
+</a>,
+and
+<a class="tref internalDFN" title="graph_name" href="#dfn-graph_name">
+graph
+name
+</a>.
+</li>
+<li>
+Return
+<a class="tref internalDFN" title="active_object" href="#dfn-active_object">
+active
+object
+</a>.
+</li>
+</ol>
+</li>
+<li id="processing-step-subject">
+If
+<em>
+element
+</em>
+has
+a
+<code>
+@id
+</code>
+property,
+the
+value
+<em class="rfc2119" title="must">
+must
+</em>
+be
+a
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>,
+set
+the
+<a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">
+active
+subject
+</a>
+to
+the
+previously
+expanded
+value
+(either
+a
+<a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">
+blank
+node
+</a>
+or
+an
+<a class="datatype idlType" title="IRI" href="#idl-def-IRI">
+<code>
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</code>
+</a>
+).
+</li>
+<li>
+Otherwise,
+if
+<em>
+element
+</em>
+does
+not
+have
+a
+<code>
+@id
+</code>
+property,
+set
+the
+<a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">
+active
+subject
+</a>
+to
+newly
+generated
+<a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">
+blank
+node
+</a>.
+</li>
+<li>
+Process
+each
+<em>
+property
+</em>
+and
+<em>
+value
+</em>
+in
+<em>
+element
+</em>,
+ordered
+by
+<em>
+property
+</em>,
+as
+follows:
+<ol class="algorithm">
+<li>
+If
+<em>
+property
+</em>
+is
+<code>
+@type
+</code>,
+set
+the
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+to
+<code>
+rdf:type
+</code>.
+</li>
+<li>
+Otherwise,
+if
+<em>
+property
+</em>
+is
+<code>
+@graph
+</code>,
+process
+<em>
+value
+</em>
+algorithm
+recursively,
+using
+<a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">
+active
+subject
+</a>
+as
+<a class="tref internalDFN" title="graph_name" href="#dfn-graph_name">
+graph
+name
+</a>
+and
+null
+values
+for
+<a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">
+active
+subject
+</a>
+and
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+and
+then
+proceed
+to
+next
+property.
+</li>
+<li>
+Otherwise,
+if
+<em>
+property
+</em>
+is
+a
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>,
+skip
+this
+step.
+</li>
+<li>
+Otherwise,
+set
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+to
+the
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+value
+of
+<em>
+property
+</em>.
+</li>
+<li>
+Process
+<em>
+value
+</em>
+recursively
+using
+this
+algorithm,
+passing
+copies
+of
+<a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">
+active
+subject
+</a>,
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+and
+<a class="tref internalDFN" title="graph_name" href="#dfn-graph_name">
+graph
+name
+</a>.
+</li>
+</ol>
+</li>
+<li>
+Set
+<a class="tref internalDFN" title="active_object" href="#dfn-active_object">
+active
+object
+</a>
+to
+<a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">
+active
+subject
+</a>.
+</li>
+</ol>
+</li>
+<li>
+Otherwise,
+if
+<em>
+element
+</em>
+is
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>,
+process
+each
+value
+in
+the
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>
+as
+follows,
+process
+<em>
+element
+</em>
+recursively
+using
+this
+algorithm,
+using
+copies
+of
+<a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">
+active
+subject
+</a>,
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>,
+and
+<a class="tref internalDFN" title="graph_name" href="#dfn-graph_name">
+graph
+name
+</a>.
+</li>
+<li>
+Otherwise,
+if
+<em>
+element
+</em>
+is
+a
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>,
+then
+the
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+must
+be
+<code>
+rdf:type
+</code>
+so
+set
+the
+<a class="tref internalDFN" title="active_object" href="#dfn-active_object">
+active
+object
+</a>
+to
+an
+<a class="datatype idlType" title="IRI" href="#idl-def-IRI">
+<code>
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</code>
+</a>.
+</li>
+<li>
+If
+any
+of
+these
+steps
+created
+an
+<a class="tref internalDFN" title="active_object" href="#dfn-active_object">
+active
+object
+</a>
+and
+neither
+<a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">
+active
+subject
+</a>
+nor
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+are
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>,
+generate
+a
+<a href="#idl-def-Quad" class="idlType">
+<code>
+Quad
+</code>
+</a>
+using
+<a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">
+active
+subject
+</a>,
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>,
+<a class="tref internalDFN" title="active_object" href="#dfn-active_object">
+active
+object
+</a>
+and
+<a class="tref internalDFN" title="graph_name" href="#dfn-graph_name">
+graph
+name
+</a>.
+</li>
+<li>
+Return
+<a class="tref internalDFN" title="active_object" href="#dfn-active_object">
+active
+object
+</a>.
+</li>
+</ol>
+</div>
+<div id="list-conversion" class="section">
+<h4>
+<span class="secno">
+4.9.4
+</span>
+List
+Conversion
+</h4>
+<p>
+List
+Conversion
+is
+the
+process
+of
+taking
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>
+of
+values
+and
+adding
+them
+to
+a
+newly
+created
+<cite>
+<a href="http://www.w3.org/TR/rdf-schema/#ch_collectionvocab">
+RDF
+Collection
+</a>
+</cite>
+(see
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RDF-SCHEMA">
+RDF-SCHEMA
+</a>
+</cite>
+])
+by
+linking
+each
+element
+of
+the
+list
+using
+<code>
+rdf:first
+</code>
+and
+<code>
+rdf:next
+</code>,
+terminating
+the
+list
+with
+<code>
+rdf:nil
+</code>
+using
+the
+following
+sequence:
+</p>
+<p>
+The
+algorithm
+is
+invoked
+with
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>
+<em>
+array
+</em>,
+the
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+and
+returns
+a
+value
+to
+be
+used
+as
+an
+<a class="tref internalDFN" title="active_object" href="#dfn-active_object">
+active
+object
+</a>
+in
+the
+calling
+location.
+</p>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<div class="">
+This
+algorithm
+does
+not
+support
+lists
+containing
+lists.
+</div>
+</div>
+<ol class="algorithm">
+<li>
+If
+<em>
+array
+</em>
+is
+empty
+return
+<code>
+rdf:nil
+</code>.
+</li>
+<li>
+Otherwise,
+generate
+a
+<a href="#idl-def-Quad" class="idlType">
+<code>
+Quad
+</code>
+</a>
+using
+using
+the
+<a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">
+active
+subject
+</a>,
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>
+and
+a
+newly
+generated
+<a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">
+blank
+node
+</a>
+identified
+as
+<em>
+first
+<a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">
+blank
+node
+</a>
+</em>.
+</li>
+<li>
+For
+each
+element
+in
+<em>
+array
+</em>
+other
+than
+the
+last
+element:
+<ol class="algorithm">
+<li>
+Create
+a
+processor
+state
+using
+<em>
+first
+blank
+node
+</em>
+as
+the
+<a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">
+active
+subject
+</a>,
+and
+<code>
+rdf:first
+</code>
+as
+the
+<a class="tref internalDFN" title="active_property" href="#dfn-active_property">
+active
+property
+</a>.
+<ol class="algorithm">
+<li>
+Process
+the
+value
+starting
+at
+<a href="#processing-step-associative">
+Step
+1
+</a>.
+</li>
+<li>
+Proceed
+using
+the
+previous
+<a class="tref internalDFN" title="processor_state" href="#dfn-processor_state">
+processor
+state
+</a>.
+</li>
+</ol>
+</li>
+<li>
+Unless
+this
+is
+the
+last
+element
+in
+<em>
+array
+</em>,
+generate
+a
+new
+<a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">
+blank
+node
+</a>
+identified
+as
+<em>
+rest
+blank
+node
+</em>,
+otherwise
+use
+<code>
+rdf:nil
+</code>.
+</li>
+<li>
+Generate
+a
+new
+<a href="#idl-def-Quad" class="idlType">
+<code>
+Quad
+</code>
+</a>
+using
+<em>
+first
+blank
+node
+</em>,
+<code>
+rdf:rest
+</code>
+and
+<em>
+rest
+blank
+node
+</em>.
+</li>
+<li>
+Set
+<em>
+first
+blank
+node
+</em>
+to
+<em>
+rest
+blank
+node
+</em>.
+</li>
+<li>
+Return
+<em>
+first
+blank
+node
+</em>.
+</li>
+</ol>
+</li>
+</ol>
+</div>
+<div id="convert-from-rdf-algorithm" class="section">
+<h4>
+<span class="secno">
+4.9.5
+</span>
+Convert
+from
+RDF
+Algorithm
+</h4>
+<p>
+In
+some
+cases,
+data
+exists
+natively
+in
+Triples
+or
+Quads
+form;
+for
+example,
+if
+the
+data
+was
+originally
+represented
+in
+an
+RDF
+graph
+or
+triple/quad
+store.
+This
+algorithm
+is
+designed
+to
+simply
+translate
+an
+array
+of
+<a class="datatype idlType" title="quad" href="#idl-def-quad">
+<code>
+Quads
+</code>
+</a>
+into
+a
+JSON-LD
+document.
+</p>
+<p>
+When
+expanding
+<a class="tref internalDFN" title="typed_literal" href="#dfn-typed_literal">
+typed
+literal
+</a>
+values
+having
+a
+datatype
+of
+<code>
+xsd:string
+</code>,
+the
+<code>
+@type
+</code>
+<em class="rfc2119" title="must not">
+must
+not
+</em>
+be
+set
+to
+<code>
+xsd:string
+</code>
+and
+the
+resulting
+value
+<em class="rfc2119" title="must">
+must
+</em>
+have
+only
+a
+<code>
+@value
+</code>
+property.
+</p>
+<p>
+The
+conversion
+algorithm
+takes
+a
+single
+parameter
+<em>
+input
+</em>
+in
+the
+form
+of
+an
+array
+of
+<a href="#idl-def-Quad" class="idlType">
+<code>
+Quad
+</code>
+</a>
+representations.
+</p>
+<ol class="algorithm">
+<li id="new_graph">
+Construct
+<em>
+defaultGraph
+</em>
+as
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+containing
+<em>
+subjects
+</em>
+and
+<em>
+listMap
+</em>,
+each
+an
+empty
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>.
+</li>
+<li>
+Construct
+<em>
+graphs
+</em>
+as
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+containing
+<em>
+defaultGraph
+</em>
+identified
+by
+an
+empty
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>.
+</li>
+<li>
+For
+each
+quad
+in
+<em>
+input
+</em>:
+<ol class="algorithm">
+<li>
+Set
+<em>
+graph
+</em>
+to
+the
+entry
+in
+<em>
+graphs
+</em>
+identified
+by
+<em>
+name
+</em>,
+initializing
+it
+to
+a
+new
+entry
+using
+the
+mechanism
+described
+in
+<a href="#new_graph">
+Step
+1
+</a>.
+</li>
+<li>
+If
+<em>
+property
+</em>
+is
+<code>
+rdf:first
+</code>,
+use
+the
+entry
+in
+<em>
+graph.listMap
+</em>
+indexed
+by
+<em>
+subject
+</em>,
+initializing
+it
+to
+a
+new
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+if
+nesessary.
+Represent
+<em>
+object
+</em>
+in
+expanded
+form,
+as
+described
+in
+<a href="#value-expansion">
+Value
+Expansion
+</a>.
+Add
+the
+resulting
+<em>
+object
+representation
+</em>
+to
+the
+entry
+indexed
+by
+<em>
+first
+</em>,
+and
+skip
+to
+the
+next
+quad.
+</li>
+<li>
+If
+<em>
+property
+</em>
+is
+<code>
+rdf:rest
+</code>:
+<ol class="algorithm">
+<li>
+If
+<em>
+object
+</em>
+is
+a
+<a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">
+blank
+node
+</a>,
+use
+the
+entry
+in
+<em>
+graph.listMap
+</em>
+indexed
+by
+<em>
+subject
+</em>,
+initializing
+it
+to
+a
+new
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+if
+necessary.
+Add
+the
+<em>
+nominalValue
+</em>
+of
+<em>
+object
+</em>
+to
+the
+entry
+indexed
+by
+<em>
+rest
+</em>.
+</li>
+<li>
+Skip
+to
+the
+next
+quad.
+</li>
+</ol>
+</li>
+<li>
+If
+<em>
+name
+</em>
+is
+not
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>,
+and
+<em>
+defaultGraph.subjects
+</em>
+does
+not
+contain
+an
+entry
+for
+<em>
+name
+</em>,
+create
+a
+new
+entry
+for
+<em>
+name
+</em>
+from
+a
+new
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+with
+key/value
+pair
+of
+<code>
+@id
+</code>
+and
+a
+string
+representation
+of
+<em>
+name
+</em>.
+</li>
+<li>
+Set
+<em>
+value
+</em>
+as
+the
+entry
+from
+<em>
+graph.subjects
+</em>
+for
+<em>
+subject
+</em>,
+initializing
+it
+to
+a
+new
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+with
+key/value
+pair
+of
+<code>
+@id
+</code>
+and
+a
+string
+representation
+of
+<em>
+subject
+</em>
+if
+necessary.
+</li>
+<li>
+If
+<em>
+property
+</em>
+is
+<code>
+rdf:type
+</code>
+and
+the
+<em>
+notType
+</em>
+option
+is
+present
+and
+not
+<a class="tref internalDFN" title="true" href="#dfn-true">
+true
+</a>:
+<ol class="algorithm">
+<li>
+Append
+the
+string
+representation
+of
+<em>
+object
+</em>
+to
+the
+array
+value
+for
+the
+key
+<code>
+@type
+</code>,
+creating
+an
+entry
+in
+<em>
+value
+</em>
+if
+necessary.
+</li>
+</ol>
+</li>
+<li>
+Otherwise,
+if
+<em>
+object
+</em>
+is
+<code>
+rdf:nil
+</code>:
+<ol class="algorithm">
+<li>
+Let
+<em>
+key
+</em>
+be
+the
+string
+representation
+of
+<em>
+property
+</em>.
+</li>
+<li>
+Append
+an
+empty
+<code>
+@list
+</code>
+representation
+to
+the
+array
+value
+for
+<em>
+key
+</em>,
+creating
+an
+entry
+in
+<em>
+value
+</em>
+if
+necessary.
+</li>
+</ol>
+</li>
+<li>
+Otherwise,
+<ol class="algorithm">
+<li>
+Let
+<em>
+key
+</em>
+be
+the
+string
+representation
+of
+<em>
+property
+</em>
+and
+let
+<em>
+object
+representation
+</em>
+be
+<em>
+object
+</em>
+represented
+in
+expanded
+form
+as
+described
+in
+<a href="#value-expansion">
+Value
+Expansion
+</a>.
+</li>
+<li>
+If
+<em>
+object
+</em>
+is
+a
+<a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">
+blank
+node
+</a>,
+use
+the
+entry
+in
+<em>
+graph.listMap
+</em>
+indexed
+by
+<em>
+object
+</em>,
+initializing
+it
+to
+a
+new
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+if
+nesessary.
+Add
+an
+entry
+for
+<em>
+head
+</em>
+with
+<em>
+object
+representation
+</em>.
+</li>
+<li>
+Append
+<em>
+object
+representation
+</em>
+to
+the
+array
+value
+for
+<em>
+key
+</em>,
+creating
+an
+entry
+in
+<em>
+value
+</em>
+if
+necessary.
+</li>
+</ol>
+</li>
+</ol>
+</li>
+<li>
+For
+each
+<em>
+name
+</em>
+and
+<em>
+graph
+</em>
+in
+<em>
+graphs
+</em>:
+<ol class="algorithm">
+<li>
+For
+each
+<em>
+subject
+</em>
+and
+<em>
+entry
+</em>
+in
+<em>
+graph
+</em>
+where
+<em>
+entry
+</em>
+has
+both
+<em>
+head
+</em>
+and
+<em>
+first
+</em>
+keys:
+<ol class="algorithm">
+<li>
+Set
+<em>
+value
+</em>
+to
+the
+value
+of
+<em>
+head
+</em>
+in
+<em>
+entry
+</em>.
+</li>
+<li>
+Remove
+the
+entry
+for
+<code>
+@id
+</code>
+in
+<em>
+value
+</em>.
+</li>
+<li>
+Add
+an
+entry
+to
+<em>
+value
+</em>
+for
+<code>
+@list
+</code>
+initialized
+to
+a
+new
+array
+containing
+the
+value
+of
+<em>
+first
+</em>
+from
+<em>
+entry
+</em>.
+</li>
+<li>
+While
+<em>
+entry
+</em>
+has
+a
+key
+for
+<em>
+rest
+</em>:
+<ol class="algorithm">
+<li>
+Set
+<em>
+entry
+</em>
+to
+the
+value
+of
+<em>
+graph.listMap
+</em>
+for
+<em>
+entry.rest
+</em>.
+</li>
+<li>
+Add
+the
+value
+for
+<em>
+entry.first
+</em>
+to
+the
+list
+array.
+</li>
+</ol>
+</li>
+</ol>
+</li>
+</ol>
+</li>
+<li>
+Create
+<em>
+array
+</em>
+as
+an
+empty
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>.
+</li>
+<li>
+For
+each
+<em>
+subject
+</em>
+and
+<em>
+entry
+</em>
+in
+<em>
+defaultGraph.subjects
+</em>
+ordered
+by
+<em>
+subject
+</em>:
+<ol class="algorithm">
+<li>
+Add
+<em>
+entry
+</em>
+to
+<em>
+array
+</em>.
+</li>
+<li>
+If
+<em>
+graphs
+</em>
+has
+an
+entry
+for
+<em>
+subject
+</em>,
+add
+a
+property
+<code>
+@graph
+</code>
+in
+<em>
+entry
+</em>
+containing
+the
+ordered
+entries
+from
+<em>
+graphs[subject].subjects
+</em>.
+</li>
+</ol>
+</li>
+<li>
+Return
+<em>
+array
+</em>
+as
+the
+result.
+</li>
+</ol>
+</div>
+</div>
+</div>
+<div id="data-round-tripping" class="section">
+<h2>
+<span class="secno">
+5.
+</span>
+Data
+Round
+Tripping
+</h2>
+<p>
+When
+coercing
+numbers
+to
+<strong>
+xsd:integer
+</strong>
+or
+<strong>
+xsd:double
+</strong>
+as
+it,
+e.g.,
+happens
+during
+<a href="#rdf-conversion">
+RDF
+Conversion
+</a>,
+implementers
+<em class="rfc2119" title="must">
+must
+</em>
+ensure
+that
+the
+result
+is
+a
+canonical
+lexical
+form
+in
+the
+form
+of
+a
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>.
+A
+<dfn title="canonical_lexical_form" id="dfn-canonical_lexical_form">
+canonical
+lexical
+form
+</dfn>
+is
+a
+set
+of
+literals
+from
+among
+the
+valid
+set
+of
+literals
+for
+a
+datatype
+such
+that
+there
+is
+a
+one-to-one
+mapping
+between
+the
+canonical
+lexical
+form
+and
+a
+value
+in
+the
+value
+space
+as
+defined
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">
+XMLSCHEMA11-2
+</a>
+</cite>
+]].
+In
+other
+words,
+every
+value
+<em class="rfc2119" title="must">
+must
+</em>
+be
+converted
+to
+a
+deterministic
+string
+representation.
+</p>
+<p>
+The
+canonical
+lexical
+form
+of
+an
+<em>
+integer
+</em>,
+i.e.,
+a
+number
+without
+fractions
+or
+a
+number
+coerced
+to
+<strong>
+xsd:integer
+</strong>,
+is
+a
+finite-length
+sequence
+of
+decimal
+digits
+(
+<code>
+0-9
+</code>
+)
+with
+an
+optional
+leading
+minus
+sign;
+leading
+zeroes
+are
+prohibited.
+To
+convert
+the
+number
+in
+JavaScript,
+implementers
+can
+use
+the
+following
+snippet
+of
+code:
+</p>
+<div class="example">
+<div class="example-title">
+<span>
+Example
+23
+</span>
+</div>
+<pre class="example">
+(value).toFixed(0).toString()
+</pre>
+</div>
+<p>
+The
+canonical
+lexical
+form
+of
+a
+<em>
+double
+</em>,
+i.e.,
+a
+number
+with
+fractions
+or
+a
+number
+coerced
+to
+<strong>
+xsd:double
+</strong>,
+consists
+of
+a
+mantissa
+followed
+by
+the
+character
+&quot;E&quot;,
+followed
+by
+an
+exponent.
+The
+mantissa
+<em class="rfc2119" title="must">
+must
+</em>
+be
+a
+decimal
+number.
+The
+exponent
+<em class="rfc2119" title="must">
+must
+</em>
+be
+an
+integer.
+Leading
+zeroes
+and
+a
+preceding
+plus
+sign
+(
+<code>
++
+</code>
+)
+are
+prohibited
+in
+the
+exponent.
+If
+the
+exponent
+is
+zero,
+it
+must
+be
+indicated
+by
+<code>
+E0
+</code>.
+For
+the
+mantissa,
+the
+preceding
+optional
+plus
+sign
+is
+prohibited
+and
+the
+decimal
+point
+is
+required.
+Leading
+and
+trailing
+zeroes
+are
+prohibited
+subject
+to
+the
+following:
+number
+representations
+must
+be
+normalized
+such
+that
+there
+is
+a
+single
+digit
+which
+is
+non-zero
+to
+the
+left
+of
+the
+decimal
+point
+and
+at
+least
+a
+single
+digit
+to
+the
+right
+of
+the
+decimal
+point
+unless
+the
+value
+being
+represented
+is
+zero.
+The
+canonical
+representation
+for
+zero
+is
+<code>
+0.0E0
+</code>.
+To
+convert
+the
+number
+in
+JavaScript,
+implementers
+can
+use
+the
+following
+snippet
+of
+code:
+</p>
+<div class="example">
+<div class="example-title">
+<span>
+Example
+24
+</span>
+</div>
+<pre class="example">
+(value).toExponential().replace(/e\+?/,'E')
+</pre>
+</div>
+<p>
+<strong>
+xsd:double
+</strong>
+'s
+value
+space
+is
+defined
+by
+the
+IEEE
+double-precision
+64-bit
+floating
+point
+type
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-IEEE-754-1985">
+IEEE-754-1985
+</a>
+</cite>
+].
+</p>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+When
+data
+such
+as
+decimals
+need
+to
+be
+normalized,
+JSON-LD
+authors
+should
+not
+use
+values
+that
+are
+going
+to
+undergo
+automatic
+conversion.
+This
+is
+due
+to
+the
+lossy
+nature
+of
+<strong>
+xsd:double
+</strong>
+values.
+Authors
+should
+instead
+use
+the
+expanded
+object
+form
+to
+set
+the
+canonical
+lexical
+form
+directly.
+</p>
+</div>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+When
+JSON-native
+datatypes,
+like
+<a class="tref internalDFN" title="number" href="#dfn-number">
+number
+</a>
+s,
+are
+type
+coerced,
+lossless
+data
+round-tripping
+can
+not
+be
+guaranted.
+Consider
+the
+following
+code
+example:
+</p>
+</div>
+<div class="example"><div class="example-title"><span>Example 25</span></div><pre class="example">var myObj1 = {
+               &quot;@context&quot;: {
+                 &quot;number&quot;: {
+                   &quot;@id&quot;: &quot;http://example.com/vocab#number&quot;,
+                   <span class="diff">&quot;@type&quot;: &quot;xsd:nonNegativeInteger&quot;</span>
+                 }
+               },
+               &quot;number&quot; : <span class="diff">42</span>
+             };
+// Convert the JSON-LD document to RDF; this converts 42 to a string
+var jsonldText = jsonld.toRDF(myObj1, myRdfTripleCollector);
+// Convert the RDF triples back to a JavaScript object
+var
+myObj2
+=
+jsonld.fromRDF(myRdfTripleCollector.getTriples());
+</pre>
+</div>
+<p>
+At
+this
+point,
+<code>
+myObj1
+</code>
+and
+<code>
+myObj2
+</code>
+will
+have
+different
+values
+for
+the
+&quot;number&quot;
+property.
+<code>
+myObj1
+</code>
+will
+have
+the
+number
+<code>
+42
+</code>,
+while
+<code>
+myObj2
+</code>
+have
+an
+object
+consisting
+of
+<code>
+@value
+</code>
+set
+to
+the
+string
+<code>
+&quot;42&quot;
+</code>
+and
+<code>
+@type
+</code>
+set
+to
+the
+expanded
+value
+of
+<em>
+xsd:nonNegativeInteger
+</em>.
+</p>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+Some
+JSON
+serializers,
+such
+as
+PHP's
+native
+implementation
+in
+some
+versions,
+backslash-escape
+the
+forward
+slash
+character.
+For
+example,
+the
+value
+<code>
+http://example.com/
+</code>
+would
+be
+serialized
+as
+<code>
+http:\/\/example.com\/
+</code>.
+This
+is
+problematic
+as
+other
+JSON
+parsers
+might
+not
+understand
+those
+escaping
+characters.
+There
+is
+no
+need
+to
+backslash-escape
+forward
+slashes
+in
+JSON-LD.
+To
+aid
+interoperability
+between
+JSON-LD
+processors,
+a
+JSON-LD
+serializer
+<em class="rfc2119" title="must not">
+must
+not
+</em>
+backslash-escape
+forward
+slashes.
+</p>
+</div>
+</div>
+<div class="appendix section" id="appendix-a">
+<h2>
+<span class="secno">
+A.
+</span>
+Initial
+Context
+</h2>
+<div class="issue">
+<div class="issue-title">
+<span>
+Issue
+8
+</span>
+</div>
+<p class="">
+It
+is
+<a href="https://github.com/json-ld/json-ld.org/issues/80">
+still
+being
+discussed
+</a>
+whether
+JSON-LD
+has
+the
+notion
+of
+an
+initial
+context
+or
+not.
+If
+JSON-LD
+has
+an
+initial
+context,
+it
+<em class="rfc2119" title="must">
+must
+</em>
+be
+specified
+external
+to
+the
+JSON-LD
+Syntax
+specification
+at
+a
+well-known
+location.
+</p>
+</div>
+</div>
+<div class="appendix section" id="acknowledgements">
+<h2>
+<span class="secno">
+B.
+</span>
+Acknowledgements
+</h2>
+<p>
+The
+editors
+would
+like
+to
+thank
+Mark
+Birbeck,
+who
+provided
+a
+great
+deal
+of
+the
+initial
+push
+behind
+the
+JSON-LD
+work
+via
+his
+work
+on
+RDFj,
+Dave
+Lehn
+and
+Mike
+Johnson
+who
+reviewed,
+provided
+feedback,
+and
+performed
+several
+implementations
+of
+the
+specification,
+and
+Ian
+Davis,
+who
+created
+RDF/JSON.
+Thanks
+also
+to
+Nathan
+Rixham,
+Bradley
+P.
+Allen,
+Kingsley
+Idehen,
+Glenn
+McDonald,
+Alexandre
+Passant,
+Danny
+Ayers,
+Ted
+Thibodeau
+Jr.,
+Olivier
+Grisel,
+Josh
+Mandel,
+Eric
+Prud'hommeaux,
+David
+Wood,
+Guus
+Schreiber,
+Pat
+Hayes,
+Sandro
+Hawke,
+and
+Richard
+Cyganiak
+for
+their
+input
+on
+the
+specification.
+</p>
+</div>
+<div id="references" class="appendix section">
+<h2>
+<span class="secno">
+C.
+</span>
+References
+</h2>
+<div id="normative-references" class="section">
+<h3>
+<span class="secno">
+C.1
+</span>
+Normative
+references
+</h3>
+<dl class="bibliography">
+<dt id="bib-BCP47">
+[BCP47]
+</dt>
+<dd>
+A.
+Phillips;
+M.
+Davis.
+<a href="http://tools.ietf.org/html/bcp47">
+<cite>
+Tags
+for
+Identifying
+Languages
+</cite>
+</a>
+September
+2009.
+IETF
+Best
+Current
+Practice.
+URL:
+<a href="http://tools.ietf.org/html/bcp47">
+http://tools.ietf.org/html/bcp47
+</a>
+</dd>
+<dt id="bib-IEEE-754-1985">
+[IEEE-754-1985]
+</dt>
+<dd>
+IEEE.
+<cite>
+IEEE
+Standard
+for
+Binary
+Floating-Point
+Arithmetic.
+</cite>
+See
+<a href="http://standards.ieee.org/reading/ieee/std_public/description/busarch/754-1985_desc.html">
+http://standards.ieee.org/reading/ieee/std_public/description/busarch/754-1985_desc.html
+</a>
+</dd>
+<dt id="bib-JSON-LD">
+[JSON-LD]
+</dt>
+<dd>
+<cite>
+<a href="http://json-ld.org/spec/ED/json-ld-syntax/20120522/">
+The
+JSON-LD
+Syntax
+</a>
+</cite>
+Manu
+Sporny,
+Gregg
+Kellogg,
+Markus
+Lanthaler
+Editors.
+World
+Wide
+Web
+Consortium
+(work
+in
+progress).
+22
+May
+2012.
+Editor's
+Draft.
+This
+edition
+of
+the
+JSON-LD
+Syntax
+specification
+is
+http://json-ld.org/spec/ED/json-ld-syntax/20120522/.
+The
+<a href="http://json-ld.org/spec/latest/json-ld-syntax/">
+latest
+edition
+of
+the
+JSON-LD
+Syntax
+</a>
+is
+available
+at
+http://json-ld.org/spec/latest/json-ld-syntax/
+</dd>
+<dt id="bib-JSON-POINTER">
+[JSON-POINTER]
+</dt>
+<dd>
+<cite>
+<a href="http://tools.ietf.org/html/draft-ietf-appsawg-json-pointer-02">
+JSON
+Pointer
+</a>
+</cite>
+P.
+Bryan,
+Ed.
+IETF
+Draft.
+URL:
+<a href="http://tools.ietf.org/html/draft-ietf-appsawg-json-pointer-02">
+http://tools.ietf.org/html/draft-ietf-appsawg-json-pointer-02
+</a>
+</dd>
+<dt id="bib-RDF-CONCEPTS">
+[RDF-CONCEPTS]
+</dt>
+<dd>
+<cite>
+<a href="http://www.w3.org/TR/2011/WD-rdf11-concepts-20110830/">
+RDF
+1.1
+Concepts
+and
+Abstract
+Syntax
+</a>
+</cite>
+Richard
+Cyganiak,
+David
+Wood,
+Editors.
+World
+Wide
+Web
+Consortium
+(work
+in
+progress).
+30
+May
+2012.
+Editor's
+Draft.
+This
+edition
+of
+the
+JSON-LD
+Syntax
+specification
+is
+http://www.w3.org/TR/2011/WD-rdf11-concepts-20110830/.
+The
+<a href="http://www.w3.org/TR/rdf11-concepts/">
+latest
+edition
+of
+the
+JSON-LD
+Syntax
+</a>
+is
+available
+at
+http://www.w3.org/TR/rdf11-concepts/
+</dd>
+<dt id="bib-RDF-SCHEMA">
+[RDF-SCHEMA]
+</dt>
+<dd>
+Dan
+Brickley;
+Ramanathan
+V.
+Guha.
+<a href="http://www.w3.org/TR/2004/REC-rdf-schema-20040210">
+<cite>
+RDF
+Vocabulary
+Description
+Language
+1.0:
+RDF
+Schema.
+</cite>
+</a>
+10
+February
+2004.
+W3C
+Recommendation.
+URL:
+<a href="http://www.w3.org/TR/2004/REC-rdf-schema-20040210">
+http://www.w3.org/TR/2004/REC-rdf-schema-20040210
+</a>
+</dd>
+<dt id="bib-RFC3986">
+[RFC3986]
+</dt>
+<dd>
+T.
+Berners-Lee;
+R.
+Fielding;
+L.
+Masinter.
+<a href="http://www.ietf.org/rfc/rfc3986.txt">
+<cite>
+Uniform
+Resource
+Identifier
+(URI):
+Generic
+Syntax.
+</cite>
+</a>
+January
+2005.
+Internet
+RFC
+3986.
+URL:
+<a href="http://www.ietf.org/rfc/rfc3986.txt">
+http://www.ietf.org/rfc/rfc3986.txt
+</a>
+</dd>
+<dt id="bib-RFC3987">
+[RFC3987]
+</dt>
+<dd>
+M.
+Dürst;
+M.
+Suignard.
+<a href="http://www.ietf.org/rfc/rfc3987.txt">
+<cite>
+Internationalized
+Resource
+Identifiers
+(IRIs).
+</cite>
+</a>
+January
+2005.
+Internet
+RFC
+3987.
+URL:
+<a href="http://www.ietf.org/rfc/rfc3987.txt">
+http://www.ietf.org/rfc/rfc3987.txt
+</a>
+</dd>
+<dt id="bib-RFC4627">
+[RFC4627]
+</dt>
+<dd>
+D.
+Crockford.
+<a href="http://www.ietf.org/rfc/rfc4627.txt">
+<cite>
+The
+application/json
+Media
+Type
+for
+JavaScript
+Object
+Notation
+(JSON)
+</cite>
+</a>
+July
+2006.
+Internet
+RFC
+4627.
+URL:
+<a href="http://www.ietf.org/rfc/rfc4627.txt">
+http://www.ietf.org/rfc/rfc4627.txt
+</a>
+</dd>
+<dt id="bib-WEBIDL">
+[WEBIDL]
+</dt>
+<dd>
+<cite>
+<a href="http://www.w3.org/TR/2012/CR-WebIDL-20120419/">
+Web
+IDL
+</a>
+</cite>
+Cameron
+McCormack,
+Editor.
+World
+Wide
+Web
+Consortium.
+19
+April
+2012.
+Candidate
+Recommendataion.
+This
+edition
+of
+Web
+IDL
+is
+http://www.w3.org/TR/2012/CR-WebIDL-20120419/.
+The
+<a href="http://dev.w3.org/2006/webapi/WebIDL/">
+latest
+edition
+of
+Web
+IDL
+</a>
+is
+available
+at
+http://dev.w3.org/2006/webapi/WebIDL/
+</dd>
+<dt id="bib-XMLSCHEMA11-2">
+[XMLSCHEMA11-2]
+</dt>
+<dd>
+Henry
+S.
+Thompson;
+et
+al.
+<a href="http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/">
+<cite>
+W3C
+XML
+Schema
+Definition
+Language
+(XSD)
+1.1
+Part
+2:
+Datatypes.
+</cite>
+</a>
+5
+April
+2012.
+W3C
+Recommendation
+URL:
+<a href="http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/">
+http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/
+</a>
+</dd>
+</dl>
+</div>
+<div id="informative-references" class="section">
+<h3>
+<span class="secno">
+C.2
+</span>
+Informative
+references
+</h3>
+<dl class="bibliography">
+<dt id="bib-ECMA-262">
+[ECMA-262]
+</dt>
+<dd>
+<a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">
+<cite>
+ECMAScript
+Language
+Specification.
+</cite>
+</a>
+December
+1999.
+URL:
+<a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">
+http://www.ecma-international.org/publications/standards/Ecma-262.htm
+</a>
+</dd>
+<dt id="bib-TURTLE-TR">
+[TURTLE-TR]
+</dt>
+<dd>
+Eric
+Prud'hommeaux,
+Gavin
+Carothers.
+<cite>
+<a href="http://www.w3.org/TR/2011/WD-turtle-20110809/">
+Turtle:
+Terse
+RDF
+Triple
+Language.
+</a>
+</cite>
+09
+August
+2011.
+W3C
+Working
+Draft.
+URL:
+<a href="http://www.w3.org/TR/2011/WD-turtle-20110809/">
+http://www.w3.org/TR/2011/WD-turtle-20110809/
+</a>
+</dd>
+<dt id="bib-UNICODE">
+[UNICODE]
+</dt>
+<dd>
+The
+Unicode
+Consortium.
+<a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html">
+<cite>
+The
+Unicode
+Standard.
+</cite>
+</a>
+2003.
+Defined
+by:
+The
+Unicode
+Standard,
+Version
+4.0
+(Boston,
+MA,
+Addison-Wesley,
+ISBN
+0-321-18578-1),
+as
+updated
+from
+time
+to
+time
+by
+the
+publication
+of
+new
+versions
+URL:
+<a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html">
+http://www.unicode.org/unicode/standard/versions/enumeratedversions.html
+</a>
+</dd>
+</dl>
+</div>
+</div>
+</body>
+</html>

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/spec/WD/json-ld-api/20120712/index.html	Tue Jun 26 23:49:05 2012 -0400
@@ -0,0 +1,2436 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.1//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd">
+<html dir="ltr" xmlns="http://www.w3.org/1999/xhtml" typeof="bibo:Document">
+<head>
+<title>JSON-LD API 1.0</title>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+
+<!-- 
+  === NOTA BENE ===
+  For the three scripts below, if your spec resides on dev.w3 you can check them
+  out in the same tree and use relative links so that they'll work offline,
+   -->
+
+
+
+<style type="text/css">
+.diff { font-weight:bold; color:#0a3; }
+</style>
+<style type="text/css">/*****************************************************************
+ * ReSpec 3 CSS
+ * Robin Berjon - http://berjon.com/
+ *****************************************************************/
+
+/* --- INLINES --- */
+em.rfc2119 { 
+    text-transform:     lowercase;
+    font-variant:       small-caps;
+    font-style:         normal;
+    color:              #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+    border: none;
+}
+
+dfn {
+    font-weight:    bold;
+}
+
+a.internalDFN {
+    color:  inherit;
+    border-bottom:  1px solid #99c;
+    text-decoration:    none;
+}
+
+a.externalDFN {
+    color:  inherit;
+    border-bottom:  1px dotted #ccc;
+    text-decoration:    none;
+}
+
+a.bibref {
+    text-decoration:    none;
+}
+
+cite .bibref {
+    font-style: normal;
+}
+
+code {
+    color:  #ff4500;
+}
+
+
+/* --- --- */
+ol.algorithm { counter-reset:numsection; list-style-type: none; }
+ol.algorithm li { margin: 0.5em 0; }
+ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }
+
+
+/* --- WEB IDL --- */
+pre.idl {
+    border-top: 1px solid #90b8de;
+    border-bottom: 1px solid #90b8de;
+    padding:    1em;
+    line-height:    120%;
+}
+
+pre.idl::before {
+    content:    "WebIDL";
+    display:    block;
+    width:      150px;
+    background: #90b8de;
+    color:  #fff;
+    font-family:    initial;
+    padding:    3px;
+    font-weight:    bold;
+    margin: -1em 0 1em -1em;
+}
+
+.idlType {
+    color:  #ff4500;
+    font-weight:    bold;
+    text-decoration:    none;
+}
+
+/*.idlModule*/
+/*.idlModuleID*/
+/*.idlInterface*/
+.idlInterfaceID, .idlDictionaryID, .idlCallbackID, .idlEnumID {
+    font-weight:    bold;
+    color:  #005a9c;
+}
+
+.idlSuperclass {
+    font-style: italic;
+    color:  #005a9c;
+}
+
+/*.idlAttribute*/
+.idlAttrType, .idlFieldType, .idlMemberType {
+    color:  #005a9c;
+}
+.idlAttrName, .idlFieldName, .idlMemberName {
+    color:  #ff4500;
+}
+.idlAttrName a, .idlFieldName a, .idlMemberName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlMethod*/
+.idlMethType, .idlCallbackType {
+    color:  #005a9c;
+}
+.idlMethName {
+    color:  #ff4500;
+}
+.idlMethName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlParam*/
+.idlParamType {
+    color:  #005a9c;
+}
+.idlParamName {
+    font-style: italic;
+}
+
+.extAttr {
+    color:  #666;
+}
+
+/*.idlConst*/
+.idlConstType {
+    color:  #005a9c;
+}
+.idlConstName {
+    color:  #ff4500;
+}
+.idlConstName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlException*/
+.idlExceptionID {
+    font-weight:    bold;
+    color:  #c00;
+}
+
+.idlTypedefID, .idlTypedefType {
+    color:  #005a9c;
+}
+
+.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
+    color:  #c00;
+    font-weight:    normal;
+}
+
+.excName a {
+    font-family:    monospace;
+}
+
+.idlRaises a.idlType, .excName a.idlType {
+    border-bottom:  1px dotted #c00;
+}
+
+.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
+    width:  45px;
+    text-align: center;
+}
+.excGetSetTrue, .prmNullTrue, .prmOptTrue { color:  #0c0; }
+.excGetSetFalse, .prmNullFalse, .prmOptFalse { color:  #c00; }
+
+.idlImplements a {
+    font-weight:    bold;
+}
+
+dl.attributes, dl.methods, dl.constants, dl.fields, dl.dictionary-members {
+    margin-left:    2em;
+}
+
+.attributes dt, .methods dt, .constants dt, .fields dt, .dictionary-members dt {
+    font-weight:    normal;
+}
+
+.attributes dt code, .methods dt code, .constants dt code, .fields dt code, .dictionary-members dt code {
+    font-weight:    bold;
+    color:  #000;
+    font-family:    monospace;
+}
+
+.attributes dt code, .fields dt code, .dictionary-members dt code {
+    background:  #ffffd2;
+}
+
+.attributes dt .idlAttrType code, .fields dt .idlFieldType code, .dictionary-members dt .idlMemberType code {
+    color:  #005a9c;
+    background:  transparent;
+    font-family:    inherit;
+    font-weight:    normal;
+    font-style: italic;
+}
+
+.methods dt code {
+    background:  #d9e6f8;
+}
+
+.constants dt code {
+    background:  #ddffd2;
+}
+
+.attributes dd, .methods dd, .constants dd, .fields dd, .dictionary-members dd {
+    margin-bottom:  1em;
+}
+
+table.parameters, table.exceptions {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    margin: 0.5em 0;
+    width:  100%;
+}
+table.parameters { border-bottom:  1px solid #90b8de; }
+table.exceptions { border-bottom:  1px solid #deb890; }
+
+.parameters th, .exceptions th {
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+    font-family:    initial;
+    font-weight:    normal;
+    text-shadow:    #666 1px 1px 0;
+}
+.parameters th { background: #90b8de; }
+.exceptions th { background: #deb890; }
+
+.parameters td, .exceptions td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+    vertical-align: top;
+}
+
+.parameters tr:first-child td, .exceptions tr:first-child td {
+    border-top: none;
+}
+
+.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
+    width:  100px;
+}
+
+.parameters td.prmType {
+    width:  120px;
+}
+
+table.exceptions table {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    width:  100%;
+}
+
+/* --- TOC --- */
+.toc a, .tof a {
+    text-decoration:    none;
+}
+
+a .secno, a .figno {
+    color:  #000;
+}
+
+ul.tof, ol.tof {
+    list-style: none outside none;
+}
+
+.caption {
+    margin-top: 0.5em;
+    font-style:   italic;
+}
+
+/* --- TABLE --- */
+table.simple {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    border-bottom:  3px solid #005a9c;
+}
+
+.simple th {
+    background: #005a9c;
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+}
+
+.simple th[scope="row"] {
+    background: inherit;
+    color:  inherit;
+    border-top: 1px solid #ddd;
+}
+
+.simple td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+    background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+    margin-top: 0;
+}
+
+.section dd > p:last-child {
+    margin-bottom: 0;
+}
+
+.section dd {
+    margin-bottom:  1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+    margin-bottom:  0;
+}
+</style><style type="text/css">/* --- EXAMPLES --- */
+div.example-title {
+    min-width: 7.5em;
+    color: #b9ab2d;
+}
+div.example-title span {
+    text-transform: uppercase;   
+}
+div.example, div.illegal-example {
+    padding: 0.5em;
+    margin: 1em 0;
+    position: relative;
+    clear: both;
+}
+div.illegal-example { color: red }
+div.illegal-example p { color: black }
+div.example {
+    padding: .5em;
+    border-left-width: .5em;
+    border-left-style: solid;
+    border-color: #e0cb52;
+    background: #fcfaee;    
+}
+</style><style type="text/css">/* --- ISSUES/NOTES --- */
+div.issue-title, div.note-title {
+    padding-right:  1em;
+    min-width: 7.5em;
+    color: #b9ab2d;
+}
+div.issue-title { color: #e05252; }
+div.note-title { color: #52e052; }
+div.issue-title span, div.note-title span {
+    text-transform: uppercase;
+}
+div.note, div.issue {
+    margin-top: 1em;
+    margin-bottom: 1em;
+}
+.note > p:first-child, .issue > p:first-child { margin-top: 0 }
+.issue, .note {
+    padding: .5em;
+    border-left-width: .5em;
+    border-left-style: solid;
+}
+div.issue, div.note {
+    padding: 0.5em;
+    margin: 1em 0;
+    position: relative;
+    clear: both;
+}
+span.note, span.issue { padding: .1em .5em .15em; }
+
+.issue {
+    border-color: #e05252;
+    background: #fbe9e9;
+}
+.note {
+    border-color: #52e052;
+    background: #e9fbe9;
+}
+
+
+</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD" /><script type="text/javascript" src="http://s3.amazonaws.com/green-turtle/RDFa.0.15.0.js"></script><meta name="green-turtle-rdfa-message" content="{ &quot;type&quot;: &quot;status&quot;, &quot;loaded&quot;: true, &quot;count&quot;: 45 }" /></head>
+
+<body><div class="head">
+  <p>
+    
+      <a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C" /></a>
+    
+  </p>
+  <h1 class="title" id="title">JSON-LD API 1.0</h1>
+  
+    <h2 id="subtitle">An Application Programming Interface for the JSON-LD Syntax</h2>
+  
+  <h2 id="w3c-working-draft-12-july-2012"><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 12 July 2012</h2>
+  <dl>
+    
+      <dt>This version:</dt>
+      <dd><a href="http://www.w3.org/TR/2012/WD-json-ld-api-20120712/">http://www.w3.org/TR/2012/WD-json-ld-api-20120712/</a></dd>
+      <dt>Latest published version:</dt>
+      <dd><a href="http://www.w3.org/TR/json-ld-api/">http://www.w3.org/TR/json-ld-api/</a></dd>
+    
+    
+      <dt>Latest editor's draft:</dt>
+      <dd><a href="http://dvcs.w3.org/hg/json-ld/raw-file/default/spec/latest/json-ld-api/index.html">http://dvcs.w3.org/hg/json-ld/raw-file/default/spec/latest/json-ld-api/index.html</a></dd>
+    
+    
+    
+    
+    
+    
+    <dt>Editors:</dt>
+    <dd rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="http://manu.sporny.org/">Manu Sporny</a>, <a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">Digital Bazaar</a></span>
+</dd>
+<dd rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Gregg Kellogg" href="http://greggkellogg.net/">Gregg Kellogg</a>, <a rel="foaf:workplaceHomepage" href="http://kellogg-assoc.com/">Kellogg Associates</a></span>
+</dd>
+<dd rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Dave Longley" href="http://digitalbazaar.com/">Dave Longley</a>, <a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">Digital Bazaar</a></span>
+</dd>
+<dd rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Markus Lanthaler" href="http://www.markus-lanthaler.com/">Markus Lanthaler</a>, <a rel="foaf:workplaceHomepage" href="http://www.tugraz.at/">Graz University of Technology</a></span>
+</dd>
+
+    
+      <dt>Authors:</dt>
+      <dd rel="dcterms:contributor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Dave Longley" href="http://digitalbazaar.com/">Dave Longley</a>, <a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">Digital Bazaar</a></span>
+</dd>
+<dd rel="dcterms:contributor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="http://digitalbazaar.com/">Manu Sporny</a>, <a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">Digital Bazaar</a></span>
+</dd>
+<dd rel="dcterms:contributor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Gregg Kellogg" href="http://greggkellogg.net/">Gregg Kellogg</a>, <a rel="foaf:workplaceHomepage" href="http://kellogg-assoc.com/">Kellogg Associates</a></span>
+</dd>
+<dd rel="dcterms:contributor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Markus Lanthaler" href="http://www.markus-lanthaler.com/">Markus Lanthaler</a>, <a rel="foaf:workplaceHomepage" href="http://www.tugraz.at/">Graz University of Technology</a></span>
+</dd>
+
+    
+  </dl>
+  
+  
+    <p>
+      
+        This document is also available in this non-normative format: 
+      
+      <a href="diff-20120626.html">diff to previous version</a>
+    </p>
+  
+  
+  
+    
+      <p class="copyright">
+        <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 
+        2010-2012
+        
+        <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> 
+        (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>,
+        <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
+        <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved.
+        <acronym title="World Wide Web Consortium">W3C</acronym> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
+        <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
+        <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
+      </p>
+    
+  
+  <hr />
+</div>
+<div id="abstract" class="introductory section"><h2>Abstract</h2>
+<p>
+JSON [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC4627">RFC4627</a></cite>] has proven to be a highly useful object serialization and
+messaging format. JSON-LD [<cite><a class="bibref" rel="biblioentry" href="#bib-JSON-LD">JSON-LD</a></cite>] harmonizes the representation of
+Linked Data in JSON by outlining a common JSON representation format for
+expressing directed graphs; mixing both Linked Data and non-Linked Data in
+a single document. This document outlines an Application Programming
+Interface and a set of algorithms for programmatically transforming
+JSON-LD documents in order to make them easier to work with in programming
+environments like JavaScript, Python, and Ruby.
+</p>
+</div><div id="sotd" class="introductory section"><h2>Status of This Document</h2>
+  
+    
+      
+        <p>
+          <em>This section describes the status of this document at the time of its publication. Other
+          documents may supersede this document. A list of current <acronym title="World Wide Web Consortium">W3C</acronym> publications and the latest revision
+          of this technical report can be found in the <a href="http://www.w3.org/TR/"><acronym title="World Wide Web Consortium">W3C</acronym> technical reports
+          index</a> at http://www.w3.org/TR/.</em>
+        </p>
+        
+<p>This document has been under development for over 18 months in the
+JSON for Linking Data Community Group. The document has recently been
+transferred to the RDF Working Group for review, improvement, and publication 
+along the Recommendation track. While this is a First Public Working Draft
+publication, the specification has undergone significant development, review, 
+and changes during the course of the last 18 months and is more mature than
+the First Public Working Draft status implies.
+</p>
+<p>
+There are currently
+<a href="http://json-ld.org/#impl">five interoperable implementations</a>
+of this specification. There is
+a <a href="https://github.com/json-ld/json-ld.org/tree/master/test-suite">fairly complete test suite</a>
+and a
+<a href="http://json-ld.org/playground/">live JSON-LD editor</a>
+that is capable of demonstrating the features described in
+this document. While development on implementations, the test suite
+and the live editor will continue, they are believed to be mature enough
+to be integrated into a non-production system at this point in time with
+the expectation that they could be used in a production system within the
+next year.
+</p>
+<div class="issue"><div class="issue-title"><span>Issue 1</span></div><p class="">
+It is important for readers to understand that the scope of this document is
+currently under debate and new features may be added to the specification.
+Existing features may be modified heavily or removed entirely from the
+specification upon further review and feedback from the broader community.
+This is a work in progress and publication as a First Public Working Draft
+does not require that all Working Group members agree on the content of the
+document.
+</p></div>
+
+        <p>
+          This document was published by the <a href="http://www.w3.org/2011/rdf-wg/">RDF Working Group</a> as a First Public Working Draft.
+          
+            This document is intended to become a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation.
+          
+          If you wish to make comments regarding this document, please send them to 
+          <a href="mailto:public-rdf-comments@w3.org">public-rdf-comments@w3.org</a> 
+          (<a href="mailto:public-rdf-comments-request@w3.org?subject=subscribe">subscribe</a>,
+          <a href="http://lists.w3.org/Archives/Public/public-rdf-comments/">archives</a>).
+          
+          
+          All feedback is welcome.
+        </p>
+        
+          <p>
+            Publication as a Working Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership.
+            This is a draft document and may be updated, replaced or obsoleted by other documents at 
+            any time. It is inappropriate to cite this document as other than work in progress.
+          </p>
+        
+        
+        <p>
+          
+            This document was produced by a group operating under the 
+            <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.
+          
+          
+          
+            
+              <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="http://www.w3.org/2004/01/pp-impl/46168/status" rel="disclosure">public list of any patent disclosures</a> 
+            
+            made in connection with the deliverables of the group; that page also includes instructions for 
+            disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains
+            <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the
+            information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
+            6 of the <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.
+          
+          
+        </p>
+        
+      
+    
+  
+</div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#preface" class="tocxref"><span class="secno">1. </span>Preface</a><ul class="toc"><li class="tocline"><a href="#contributing" class="tocxref"><span class="secno">1.1 </span>Contributing</a></li></ul></li><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">2. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#expansion" class="tocxref"><span class="secno">2.1 </span>Expansion</a></li><li class="tocline"><a href="#compaction" class="tocxref"><span class="secno">2.2 </span>Compaction</a></li><li class="tocline"><a href="#conversion-to-and-from-rdf" class="tocxref"><span class="secno">2.3 </span>Conversion to and from RDF</a></li><li class="tocline"><a href="#framing-and-normalization" class="tocxref"><span class="secno">2.4 </span>Framing and Normalization</a></li></ul></li><li class="tocline"><a href="#the-application-programming-interface" class="tocxref"><span class="secno">3. </span>The Application Programming Interface</a><ul class="toc"><li class="tocline"><a href="#general-terminology" class="tocxref"><span class="secno">3.1 </span>General Terminology</a></li><li class="tocline"><a href="#jsonldprocessor" class="tocxref"><span class="secno">3.2 </span>JsonLdProcessor</a><ul class="toc"><li class="tocline"><a href="#methods" class="tocxref"><span class="secno">3.2.1 </span>Methods</a></li></ul></li><li class="tocline"><a href="#callbacks" class="tocxref"><span class="secno">3.3 </span>Callbacks</a><ul class="toc"><li class="tocline"><a href="#jsonldcallback" class="tocxref"><span class="secno">3.3.1 </span>JsonLdCallback</a><ul class="toc"><li class="tocline"><a href="#methods-1" class="tocxref"><span class="secno">3.3.1.1 </span>Methods</a></li></ul></li><li class="tocline"><a href="#quadcallback" class="tocxref"><span class="secno">3.3.2 </span>QuadCallback</a><ul class="toc"><li class="tocline"><a href="#methods-2" class="tocxref"><span class="secno">3.3.2.1 </span>Methods</a></li></ul></li></ul></li><li class="tocline"><a href="#data-structures" class="tocxref"><span class="secno">3.4 </span>Data Structures</a><ul class="toc"><li class="tocline"><a href="#url" class="tocxref"><span class="secno">3.4.1 </span>URL</a></li><li class="tocline"><a href="#jsonldoptions" class="tocxref"><span class="secno">3.4.2 </span>JsonLdOptions</a></li><li class="tocline"><a href="#quad" class="tocxref"><span class="secno">3.4.3 </span>Quad</a><ul class="toc"><li class="tocline"><a href="#attributes" class="tocxref"><span class="secno">3.4.3.1 </span>Attributes</a></li></ul></li><li class="tocline"><a href="#node" class="tocxref"><span class="secno">3.4.4 </span>Node</a></li><li class="tocline"><a href="#iri" class="tocxref"><span class="secno">3.4.5 </span><abbr title="Internationalized Resource Identifier">IRI</abbr></a><ul class="toc"><li class="tocline"><a href="#attributes-1" class="tocxref"><span class="secno">3.4.5.1 </span>Attributes</a></li></ul></li><li class="tocline"><a href="#blank-node" class="tocxref"><span class="secno">3.4.6 </span><span title="blank_node">Blank Node</span></a><ul class="toc"><li class="tocline"><a href="#attributes-2" class="tocxref"><span class="secno">3.4.6.1 </span>Attributes</a></li></ul></li><li class="tocline"><a href="#literal" class="tocxref"><span class="secno">3.4.7 </span>Literal</a><ul class="toc"><li class="tocline"><a href="#attributes-3" class="tocxref"><span class="secno">3.4.7.1 </span>Attributes</a></li></ul></li></ul></li></ul></li><li class="tocline"><a href="#algorithms" class="tocxref"><span class="secno">4. </span>Algorithms</a><ul class="toc"><li class="tocline"><a href="#algorithm-terms" class="tocxref"><span class="secno">4.1 </span>Algorithm Terms</a></li><li class="tocline"><a href="#context-processing" class="tocxref"><span class="secno">4.2 </span>Context Processing</a></li><li class="tocline"><a href="#iri-expansion" class="tocxref"><span class="secno">4.3 </span><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion</a></li><li class="tocline"><a href="#iri-compaction" class="tocxref"><span class="secno">4.4 </span><abbr title="Internationalized Resource Identifier">IRI</abbr> Compaction</a><ul class="toc"><li class="tocline"><a href="#iri-compaction-algorithm" class="tocxref"><span class="secno">4.4.1 </span><abbr title="Internationalized Resource Identifier">IRI</abbr> Compaction Algorithm</a></li><li class="tocline"><a href="#term-rank-algorithm" class="tocxref"><span class="secno">4.4.2 </span>Term Rank Algorithm</a></li></ul></li><li class="tocline"><a href="#value-expansion" class="tocxref"><span class="secno">4.5 </span>Value Expansion</a></li><li class="tocline"><a href="#value-compaction" class="tocxref"><span class="secno">4.6 </span>Value Compaction</a></li><li class="tocline"><a href="#expansion-1" class="tocxref"><span class="secno">4.7 </span>Expansion</a><ul class="toc"><li class="tocline"><a href="#expansion-algorithm" class="tocxref"><span class="secno">4.7.1 </span>Expansion Algorithm</a></li></ul></li><li class="tocline"><a href="#compaction-1" class="tocxref"><span class="secno">4.8 </span>Compaction</a><ul class="toc"><li class="tocline"><a href="#compaction-algorithm" class="tocxref"><span class="secno">4.8.1 </span>Compaction Algorithm</a></li></ul></li><li class="tocline"><a href="#rdf-conversion" class="tocxref"><span class="secno">4.9 </span>RDF Conversion</a><ul class="toc"><li class="tocline"><a href="#overview" class="tocxref"><span class="secno">4.9.1 </span>Overview</a></li><li class="tocline"><a href="#parsing-examples" class="tocxref"><span class="secno">4.9.2 </span>Parsing Examples</a></li><li class="tocline"><a href="#convert-to-rdf-algorithm" class="tocxref"><span class="secno">4.9.3 </span>Convert to RDF Algorithm</a></li><li class="tocline"><a href="#list-conversion" class="tocxref"><span class="secno">4.9.4 </span>List Conversion</a></li><li class="tocline"><a href="#convert-from-rdf-algorithm" class="tocxref"><span class="secno">4.9.5 </span>Convert from RDF Algorithm</a></li></ul></li></ul></li><li class="tocline"><a href="#data-round-tripping" class="tocxref"><span class="secno">5. </span>Data Round Tripping</a></li><li class="tocline"><a href="#appendix-a" class="tocxref"><span class="secno">A. </span>Initial Context</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">B. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></div>
+
+
+
+<div id="preface" class="section">
+
+<!-- OddPage -->
+<h2><span class="secno">1. </span>Preface</h2>
+
+<p>
+This document is a detailed specification for an Application Programming
+Interface for the JSON-LD Syntax. The document is primarily intended for
+the following audiences:
+</p>
+
+<ul>
+  <li>Web authors and developers that want a very detailed view of how
+  a JSON-LD processor and the API operates.</li>
+  <li>Software developers that want to implement processors and APIs for
+  JSON-LD.</li>
+</ul>
+
+<p>
+To understand the basics in this specification you must first be familiar with
+JSON, which is detailed in [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC4627">RFC4627</a></cite>]. You must also understand the
+JSON-LD Syntax [<cite><a class="bibref" rel="biblioentry" href="#bib-JSON-LD">JSON-LD</a></cite>], which is the base syntax used by all of the
+algorithms in this document. To understand the API and how it is
+intended to operate in a programming environment, it is useful to have working
+knowledge of the JavaScript programming language [<cite><a class="bibref" rel="biblioentry" href="#bib-ECMA-262">ECMA-262</a></cite>] and
+WebIDL [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBIDL">WEBIDL</a></cite>]. To understand how JSON-LD maps to RDF, it is helpful to be
+familiar with the basic RDF concepts [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>].</p>
+
+<div id="contributing" class="section">
+  <h3><span class="secno">1.1 </span>Contributing</h3>
+
+  <p>There are a number of ways that one may participate in the development of
+    this specification:</p>
+
+  <ul>
+    <li>If you want to make sure that your feedback is formally addressed by
+      the RDF Working Group, you should send it to public-rdf-comments:
+      <a href="http://lists.w3.org/Archives/Public/public-rdf-comments/">public-rdf-comments@w3.org</a></li>
+
+    <li>Ad-hoc technical discussion primarily occurs on the public community mailing list:
+      <a href="http://lists.w3.org/Archives/Public/public-linked-json/">public-linked-json@w3.org</a></li>
+
+    <li><a href="http://json-ld.org/minutes/">Public JSON-LD Community Group teleconferences</a>
+    are held on Tuesdays at 1500UTC every week.</li>
+
+    <li>RDF Working Group teleconferences are held on Wednesdays at 1500UTC
+    every week. Participation is limited to RDF Working Group members.</li>
+
+    <li>Specification bugs and issues should be reported in the
+      <a href="https://github.com/json-ld/json-ld.org/issues">issue tracker</a>
+      if you do not want to send an e-mail to the public-rdf-comments mailing
+      list.</li>
+
+    <li><a href="https://github.com/json-ld/json-ld.org/tree/master/spec">Source code</a>
+      for the specification can be found on Github.</li>
+
+    <li>The <a href="http://webchat.freenode.net/?channels=json-ld">#json-ld</a>
+      IRC channel is available for real-time discussion on irc.freenode.net.</li>
+  </ul>
+
+</div>
+
+</div>
+
+<div id="introduction" class="section">
+
+<!-- OddPage -->
+<h2><span class="secno">2. </span>Introduction</h2>
+
+<p>
+The JSON-LD Syntax specification [<cite><a class="bibref" rel="biblioentry" href="#bib-JSON-LD">JSON-LD</a></cite>] outlines a language that may be
+used to express Linked Data in JSON. Often, it is useful to be able to
+transform JSON-LD documents so that they may be easily processed in
+a programming environment like JavaScript, Python or Ruby.
+</p>
+
+<p>
+There are three major types of transformation that are discussed in this
+document; compaction, expansion, and RDF conversion.
+</p>
+
+<div id="expansion" class="section">
+  <h3><span class="secno">2.1 </span>Expansion</h3>
+  <p>
+Software algorithms are easiest to write when the data that they are processing
+have a regular form. Since information can be represented by JSON-LD in a
+variety of different ways, transforming all of these methods into a uniform
+structure allows the developer to simplify their processing code. For example,
+note that the following input uses only <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s and is fairly
+compact:
+  </p>
+
+  <div class="example"><div class="example-title"><span>Example 1</span></div><pre class="example">var input1 = {
+  &quot;@context&quot;: &quot;http://json-ld.org/contexts/person.jsonld&quot;
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;
+}</pre></div>
+
+  <p>
+The next input example uses one <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> to express a property, but
+leaves the rest of the information untouched.
+  </p>
+
+  <div class="example"><div class="example-title"><span>Example 2</span></div><pre class="example">var input2 = {
+  &quot;@context&quot;: &quot;http://json-ld.org/contexts/person.jsonld&quot;
+  &quot;<span class="diff">http://xmlns.com/foaf/0.1/name</span>&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;
+}</pre></div>
+
+  <p>
+While both inputs are valid JSON-LD, writing a program to handle every
+permutation of possible inputs can be difficult, especially when the incoming
+context could change as well. To ensure that the data can be given a more
+uniform structure, JSON-LD introduces the notion of expansion.
+<dfn title="expansion" id="dfn-expansion">Expansion</dfn> performs two important operations. The first is to
+expand all values that are <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>s to their fully expanded form.
+The second is to express all values in <dfn title="expanded_form" id="dfn-expanded_form">expanded form</dfn>. To
+transform both inputs above to the same representation, the developer could
+do the following:
+  </p>
+
+  <div class="example"><div class="example-title"><span>Example 3</span></div><pre class="example">function expansionCallback(output) {
+   console.log(output);
+}
+
+// the second parameter is 'null' because the developer does not wish to
+// inject another context value
+jsonld.expand(input1, null, expansionCallback);
+jsonld.expand(input2, null, expansionCallback);</pre></div>
+
+  <p>
+The output for both calls above will be:
+  </p>
+
+  <div class="example"><div class="example-title"><span>Example 4</span></div><pre class="example">[{
+  &quot;http://xmlns.com/foaf/0.1/name&quot;: [{
+    &quot;@value&quot;: &quot;Manu Sporny&quot;
+  }],
+  &quot;http://xmlns.com/foaf/0.1/homepage&quot;: [{
+    &quot;@id&quot;: &quot;http://manu.sporny.org/&quot;
+  }]
+}]</pre></div>
+
+  <p>
+Note that in the example above; all <a class="tref internalDFN" title="context" href="#dfn-context">context</a> definitions have
+been removed, all <a class="tref internalDFN" title="term" href="#dfn-term">term</a> and prefixes have been expanded to full
+IRIs, and all <a class="tref internalDFN" title="literal" href="#dfn-literal">literal</a>s are expressed in <a class="tref internalDFN" title="expanded_form" href="#dfn-expanded_form">expanded form</a>.
+While the output is more difficult for a human to read, it is easier for a
+software program to process because of its very regular structure.
+  </p>
+</div>
+
+<div id="compaction" class="section">
+  <h3><span class="secno">2.2 </span>Compaction</h3>
+  <p>
+While expansion expands a given input as much as possible, compaction performs
+the opposite operation - expressing a given input as succinctly as possible.
+While expansion is meant to produce something that is easy to process by
+software programs, compaction is meant to produce something that is easy to
+ready by software developers. Compaction uses a developer-supplied
+<a class="tref internalDFN" title="context" href="#dfn-context">context</a> to compresses all <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>s to <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s
+or <a class="tref internalDFN" title="prefix" href="#dfn-prefix">prefix</a>es, and compacts all <a class="tref internalDFN" title="literal" href="#dfn-literal">literal</a>s expressed
+in <a class="tref internalDFN" title="expanded_form" href="#dfn-expanded_form">expanded form</a> as much as possible.
+  </p>
+
+  <p>
+The following example expresses input that has already been fully expanded:
+  </p>
+
+  <div class="example"><div class="example-title"><span>Example 5</span></div><pre class="example">var expandedInput = [{
+  &quot;http://xmlns.com/foaf/0.1/name&quot;: [{
+    &quot;@value&quot;: &quot;Manu Sporny&quot;
+  }],
+  &quot;http://xmlns.com/foaf/0.1/homepage&quot;: [{
+    &quot;@id&quot;: &quot;http://manu.sporny.org/&quot;
+  }]
+}]</pre></div>
+
+  <p>
+A developer that wants to transform the data above into a more human-readable
+form, could do the following using the JSON-LD API:
+  </p>
+
+  <div class="example"><div class="example-title"><span>Example 6</span></div><pre class="example">function compactionCallback(output) {
+   console.log(output);
+}
+
+jsonld.compact(expandedInput, &quot;http://json-ld.org/contexts/person.jsonld&quot;, compactionCallback);</pre></div>
+
+  <p>
+The following would be the result of the call above:
+  </p>
+
+  <div class="example"><div class="example-title"><span>Example 7</span></div><pre class="example">{
+  &quot;@context&quot;: &quot;http://json-ld.org/contexts/person.jsonld&quot;
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;
+}</pre></div>
+
+  <p>
+Note that all of the <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s have been compressed and
+the <a class="tref internalDFN" title="context" href="#dfn-context">context</a> has been injected into the output. While compacted
+output is most useful to humans, it can also be carefully used to generate
+structures that are easy to use for developers to program against as well.
+  </p>
+
+</div>
+
+<div id="conversion-to-and-from-rdf" class="section">
+  <h3><span class="secno">2.3 </span>Conversion to and from RDF</h3>
+  <p>
+JSON-LD can be used to losslessly express the RDF data model as described in
+the RDF Concepts document  [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>]. This ensures that
+data can be round-tripped from any RDF syntax, like N-Triples or TURTLE,
+without any loss in the fidelity of the data. Assume the following RDF input
+in N-Triples format:
+  </p>
+
+  <div class="example"><div class="example-title"><span>Example 8</span></div><pre class="example">var data = &quot;
+&lt;http://manu.sporny.org/about/#manu&gt; &lt;http://xmlns.com/foaf/0.1/name&gt; \&quot;Manu Sporny\&quot; .\n
+&lt;http://manu.sporny.org/about/#manu&gt; &lt;http://xmlns.com/foaf/0.1/homepage&gt; &lt;http://manu.sporny.org/&gt; .&quot;;</pre></div>
+
+  <p>
+A developer can use the JSON-LD API to transform the markup above into a
+JSON-LD document:
+  </p>
+
+  <div class="example"><div class="example-title"><span>Example 9</span></div><pre class="example">function conversionCallback(result)
+{
+  console.log(&quot;JSON-LD Document: &quot;, result);
+};
+
+jsonld.fromRDF(data, conversionCallback, {&quot;format&quot;: &quot;ntriples&quot;});</pre></div>
+
+  <p>
+The following expanded output would be the result of the call above:
+  </p>
+
+  <div class="example"><div class="example-title"><span>Example 10</span></div><pre class="example">[{
+  &quot;@id&quot;: &quot;http://manu.sporny.org/about/#manu&quot;,
+  &quot;http://xmlns.com/foaf/0.1/name&quot;: [{
+    &quot;@value&quot;: &quot;Manu Sporny&quot;
+  }],
+  &quot;http://xmlns.com/foaf/0.1/homepage&quot;: [{
+    &quot;@id&quot;: &quot;http://manu.sporny.org/&quot;
+  }]
+}]</pre></div>
+
+  <p>
+Note that the output above, could easily be compacted to produce the following
+using the technique outlined in the previous section:
+  </p>
+
+  <div class="example"><div class="example-title"><span>Example 11</span></div><pre class="example">{
+  &quot;@context&quot;: &quot;http://json-ld.org/contexts/person.jsonld&quot;,
+  &quot;@id&quot;: &quot;http://manu.sporny.org/about/#manu&quot;,
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;
+}</pre></div>
+
+  <p>
+Transforming the object above back to RDF is as simple as calling the
+<code>toRDF()</code> method:
+  </p>
+
+  <div class="example"><div class="example-title"><span>Example 12</span></div><pre class="example">var jsonldDocument = ...; // assign the JSON-LD document here
+
+function rdfCallback(quads)
+{
+  console.log(&quot;RDF Data: &quot;, quads);
+};
+
+jsonld.toRDF(jsonldDocument, rdfCallback);</pre></div>
+
+</div>
+
+<div id="framing-and-normalization" class="section">
+  <h3><span class="secno">2.4 </span>Framing and Normalization</h3>
+  <div class="issue"><div class="issue-title"><span>Issue 2</span></div><p class="">
+There are currently two other API methods that are in active development and
+were not ready for publication at the time this document was published.
+Framing allows a developer to force a different layout for the data and
+effectively perform query-by-example on JSON-LD documents - this is most
+useful when a JSON-LD-based REST API does not know the exact form of the data
+it is getting in, but still wants to operate upon it if some bare essentials
+are found in the data. JSON-LD normalization allows JSON-LD documents to be
+deterministically serialized such that they can be digitally signed or be
+used to find the differences between two <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a>s.
+It is expected that framing will be a part of the final API. It is expected
+that normalization will be an optional feature that JSON-LD processors may
+implement.
+  </p></div>
+</div>
+
+</div>
+
+<div id="the-application-programming-interface" class="section">
+  
+<!-- OddPage -->
+<h2><span class="secno">3. </span>The Application Programming Interface</h2>
+
+  <p>This API provides a clean mechanism that enables developers to convert
+  JSON-LD data into a a variety of output formats that are easier to work
+  with in various programming languages. If a JSON-LD API is provided in
+  a programming environment, the entirety of the following API <em class="rfc2119" title="must">must</em> be
+  implemented.
+  </p>
+
+<div id="general-terminology" class="section">
+  <h3><span class="secno">3.1 </span>General Terminology</h3>
+
+  <div class="issue"><div class="issue-title"><span>Issue 3</span></div><p class="">
+The intent of the Working Group and the Editors of this specification is to
+eventually align terminology used in this document with the terminology used
+in the RDF Concepts document to the extent to which it makes sense to do so.
+In general, if there is an analogue to terminology used in this document in
+the RDF Concepts document, the preference is to use the terminology in the
+RDF Concepts document.
+  </p></div>
+
+  <p>
+The following is an explanation of the general terminology used in this
+document:
+  </p>
+
+  <dl>
+      <dt><dfn title="json_object" id="dfn-json_object">JSON object</dfn></dt><dd>
+      An object structure is represented as a pair of curly brackets surrounding zero or
+      more name-value pairs. A name is a <a class="tref internalDFN" title="string" href="#dfn-string">string</a>. A single colon comes after
+      each name, separating the name from the value. A single comma separates a value
+      from a following name. The names within an object <em class="rfc2119" title="should">should</em> be unique.
+    </dd>
+    <dt><dfn title="array" id="dfn-array">array</dfn></dt>
+    <dd>
+      An array is represented as square brackets surrounding zero or more
+      values that are separated by commas.
+    </dd>
+    <dt><dfn title="string" id="dfn-string">string</dfn></dt><dd>
+      A string is a sequence of zero or more Unicode (UTF-8) characters,
+      wrapped in double quotes, using backslash escapes (if necessary). A
+      character is represented as a single character string.
+    </dd>
+    <dt><dfn title="number" id="dfn-number">number</dfn></dt>
+    <dd>
+      A number is similar to that used in most programming languages, except
+      that the octal and hexadecimal formats are not used and that leading
+      zeros are not allowed.</dd>
+    <dt><dfn title="true" id="dfn-true">true</dfn> and <dfn title="false" id="dfn-false">false</dfn></dt><dd>
+      Values that are used to express one of two possible boolean states.
+    </dd>
+    <dt><dfn title="null" id="dfn-null">null</dfn></dt><dd>
+      Unless otherwise specified, a JSON-LD processor <em class="rfc2119" title="must">must</em> act as if a
+      key-value pair in the body of a JSON-LD document was never declared when
+      the value equals <em>null</em>. If <code>@value</code>,
+      <code>@list</code>, or <code>@set</code> is set to <em>null</em> in
+      expanded form, then the entire JSON object is ignored. If
+      <code>@context</code> is set to <em>null</em>, the
+      <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> is reset and when used
+      within a <a class="tref internalDFN" title="context" href="#dfn-context">context</a>, it removes any definition associated
+      with the key, unless otherwise specified.
+    </dd>
+    <dt><dfn title="subject_definition" id="dfn-subject_definition">subject definition</dfn></dt><dd>
+      A <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> used to represent a <a class="tref internalDFN" title="subject" href="#dfn-subject">subject</a> and
+      one or more properties of that subject. A <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> is a
+      subject definition if it does not contain they keys <code>@value</code>,
+      <code>@list</code> or <code>@set</code> and it has one or more keys
+      other than <code>@id</code>.</dd>
+    <dt><dfn title="subject_reference" id="dfn-subject_reference">subject reference</dfn></dt><dd>
+      A <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> used to reference a subject having only the
+      <code>@id</code> key.</dd>
+    <dt><dfn title="linked_data" id="dfn-linked_data">Linked Data</dfn></dt>
+    <dd>A set of documents, each containing a representation of a
+    <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a>.</dd>
+    <dt><dfn title="linked_data_graph" id="dfn-linked_data_graph">linked data graph</dfn> or <dfn title="dataset" id="dfn-dataset">dataset</dfn></dt>
+    <dd>An unordered labeled directed graph, where <a class="tref internalDFN" title="node" href="#dfn-node">node</a>s are
+    <a class="tref internalDFN" title="subject" href="#dfn-subject">subject</a>s or <a class="tref internalDFN" title="object" href="#dfn-object">object</a>s, and edges are
+    properties.</dd>
+    <dt><dfn title="node" id="dfn-node">node</dfn></dt>
+    <dd>A piece of information that is represented in a
+    <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a>.</dd>
+    <dt><dfn title="named_graph" id="dfn-named_graph">named graph</dfn></dt>
+    <dd>A <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a> that has one or more
+    <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> that are used to refer to it.</dd>
+    <dt><dfn title="graph_name" id="dfn-graph_name">graph name</dfn></dt>
+    <dd>An <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> that is a reference to a
+    <a class="tref internalDFN" title="named_graph" href="#dfn-named_graph">named graph</a>.</dd>
+    <dt><dfn title="default_graph" id="dfn-default_graph">default graph</dfn></dt>
+    <dd>When executing an algorithm, the graph where data should be placed
+    if a <a class="tref internalDFN" title="named_graph" href="#dfn-named_graph">named graph</a> is not specified.</dd>
+    <dt><dfn title="subject" id="dfn-subject">subject</dfn></dt>
+    <dd>Any node in a <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a> with at least one
+    outgoing edge.</dd>
+    <dt><dfn title="iri" id="dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></dfn></dt>
+    <dd>An Internationalized Resource Identifier as described
+    in [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3987">RFC3987</a></cite>]).</dd>
+    <dt><dfn title="object" id="dfn-object">object</dfn></dt>
+    <dd>A node in a <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a> with at least one
+    incoming edge.</dd>
+    <dt><dfn title="property" id="dfn-property">property</dfn></dt>
+    <dd>An edge of the <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a>.</dd>
+    <dt><dfn title="literal" id="dfn-literal">literal</dfn></dt>
+    <dd>An <a class="tref internalDFN" title="object" href="#dfn-object">object</a> with a label that is not an
+    <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.</dd>
+    <dt><dfn title="quad" id="dfn-quad">quad</dfn></dt>
+    <dd>A piece of information that contains four items; a
+    <a class="tref internalDFN" title="subject" href="#dfn-subject">subject</a>, a <a class="tref internalDFN" title="property" href="#dfn-property">property</a>, a <a class="tref internalDFN" title="object" href="#dfn-object">object</a>,
+    and a <a class="tref internalDFN" title="graph_name" href="#dfn-graph_name">graph name</a>.</dd>
+    <dt><dfn title="context" id="dfn-context">context</dfn></dt>
+    <dd>A <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> that contains rules for interpreting a
+    JSON-LD document.</dd>
+    <dt><dfn title="keyword" id="dfn-keyword">keyword</dfn></dt>
+    <dd>A JSON key that is specific to JSON-LD, specified in the JSON-LD
+    Syntax specification [<cite><a class="bibref" rel="biblioentry" href="#bib-JSON-LD">JSON-LD</a></cite>] in the section titled
+    <a href="http://sites.local/json-ld.org/spec/latest/json-ld-syntax/#syntax-tokens-and-keywords">Syntax Tokens and Keywords</a>.</dd>
+   </dl>
+ </div>
+
+  <div id="jsonldprocessor" class="section">
+    <h3><span class="secno">3.2 </span>JsonLdProcessor</h3>
+
+    <p>
+The JSON-LD Processor interface is the high-level programming structure that
+developers use to access the JSON-LD transformation methods.
+    </p>
+
+    <pre class="idl"><span class="idlInterface" id="idl-def-JsonLdProcessor">[<span class="extAttr">NoInterfaceObject</span>]
+interface <span class="idlInterfaceID">JsonLdProcessor</span> {
+<span class="idlMethod">    <span class="idlMethType"><a>void</a></span> <span class="idlMethName"><a href="#widl-JsonLdProcessor-expand-void-object-or-object---or-URL-input-object-or-URL-context-JsonLdCallback-callback-JsonLdOptions-options">expand</a></span> (<span class="idlParam"><span class="idlParamType"><a>object or object[] or URL</a></span> <span class="idlParamName">input</span></span>, <span class="idlParam"><span class="idlParamType"><a>object or URL</a>?</span> <span class="idlParamName">context</span></span>, <span class="idlParam"><span class="idlParamType"><a href="#idl-def-JsonLdCallback" class="idlType"><code>JsonLdCallback</code></a></span> <span class="idlParamName">callback</span></span>, <span class="idlParam">optional <span class="idlParamType"><a href="#idl-def-JsonLdOptions" class="idlType"><code>JsonLdOptions</code></a></span> <span class="idlParamName">options</span></span>);</span>
+<span class="idlMethod">    <span class="idlMethType"><a>void</a></span> <span class="idlMethName"><a href="#widl-JsonLdProcessor-compact-void-object-or-object---or-URL-input-object-or-URL-context-JsonLdCallback-callback-JsonLdOptions-options">compact</a></span> (<span class="idlParam"><span class="idlParamType"><a>object or object[] or URL</a></span> <span class="idlParamName">input</span></span>, <span class="idlParam"><span class="idlParamType"><a>object or URL</a></span> <span class="idlParamName">context</span></span>, <span class="idlParam"><span class="idlParamType"><a href="#idl-def-JsonLdCallback" class="idlType"><code>JsonLdCallback</code></a></span> <span class="idlParamName">callback</span></span>, <span class="idlParam">optional <span class="idlParamType"><a href="#idl-def-JsonLdOptions" class="idlType"><code>JsonLdOptions</code></a></span> <span class="idlParamName">options</span></span>);</span>
+<span class="idlMethod">    <span class="idlMethType"><a>void</a></span> <span class="idlMethName"><a href="#widl-JsonLdProcessor-fromRDF-void-QuadArray-input-JsonLdCallback-callback-JsonLdOptions-options">fromRDF</a></span> (<span class="idlParam"><span class="idlParamType"><a href="#idl-def-Quad" class="idlType"><code>Quad</code></a>[]</span> <span class="idlParamName">input</span></span>, <span class="idlParam"><span class="idlParamType"><a href="#idl-def-JsonLdCallback" class="idlType"><code>JsonLdCallback</code></a></span> <span class="idlParamName">callback</span></span>, <span class="idlParam">optional <span class="idlParamType"><a href="#idl-def-JsonLdOptions" class="idlType"><code>JsonLdOptions</code></a></span> <span class="idlParamName">options</span></span>);</span>
+<span class="idlMethod">    <span class="idlMethType"><a>void</a></span> <span class="idlMethName"><a href="#widl-JsonLdProcessor-toRDF-void-object-or-object---or-URL-input-QuadCallback-callback-JsonLdOptions-options">toRDF</a></span> (<span class="idlParam"><span class="idlParamType"><a>object or object[] or URL</a></span> <span class="idlParamName">input</span></span>, <span class="idlParam"><span class="idlParamType"><a href="#idl-def-QuadCallback" class="idlType"><code>QuadCallback</code></a></span> <span class="idlParamName">callback</span></span>, <span class="idlParam">optional <span class="idlParamType"><a href="#idl-def-JsonLdOptions" class="idlType"><code>JsonLdOptions</code></a></span> <span class="idlParamName">options</span></span>);</span>
+};</span>
+</pre><div id="methods" class="section"><h2><span class="secno">3.2.1 </span>Methods</h2><dl class="methods"><dt id="widl-JsonLdProcessor-compact-void-object-or-object---or-URL-input-object-or-URL-context-JsonLdCallback-callback-JsonLdOptions-options"><code>compact</code></dt><dd>
+        <a href="#compaction">Compacts</a> the given <code>input</code> using the
+        <code>context</code> according to the steps in the
+        <a href="#compaction-algorithm">Compaction Algorithm</a>. The
+        <code>input</code> <em class="rfc2119" title="must">must</em> be copied, compacted and returned if there are
+        no errors. If the compaction fails, an appropriate exception <em class="rfc2119" title="must">must</em> be
+        thrown.
+
+        
+
+        
+
+        
+      <table class="parameters"><tr><th>Parameter</th><th>Type</th><th>Nullable</th><th>Optional</th><th>Description</th></tr><tr><td class="prmName">input</td><td class="prmType"><code><a>object or object[] or URL</a></code></td><td class="prmNullFalse">✘</td><td class="prmOptFalse">✘</td><td class="prmDesc">The JSON-LD object or array of JSON-LD objects to perform the compaction upon or an
+            <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> referencing the JSON-LD document to compact.</td></tr><tr><td class="prmName">context</td><td class="prmType"><code><a>object or URL</a></code></td><td class="prmNullFalse">✘</td><td class="prmOptFalse">✘</td><td class="prmDesc">The context to use when compacting the <code>input</code>; either in the
+            form of an <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> or as <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.</td></tr><tr><td class="prmName">callback</td><td class="prmType"><code><a href="#idl-def-JsonLdCallback" class="idlType"><code>JsonLdCallback</code></a></code></td><td class="prmNullFalse">✘</td><td class="prmOptFalse">✘</td><td class="prmDesc">A callback that is called when processing is complete on
+            the given <code>input</code>.</td></tr><tr><td class="prmName">options</td><td class="prmType"><code><a href="#idl-def-JsonLdOptions" class="idlType"><code>JsonLdOptions</code></a></code></td><td class="prmNullFalse">✘</td><td class="prmOptTrue">✔</td><td class="prmDesc">A set of options that <em class="rfc2119" title="may">may</em> affect the expansion algorithm such as, e.g., the
+            input document's base <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>. This also includes <code>optimize</code>,
+            which if set will cause processor-specific optimization.</td></tr></table><div><em>Return type: </em><code><a>void</a></code></div></dd><dt id="widl-JsonLdProcessor-expand-void-object-or-object---or-URL-input-object-or-URL-context-JsonLdCallback-callback-JsonLdOptions-options"><code>expand</code></dt><dd>
+        <a href="#expansion">Expands</a> the given <code>input</code> according to
+        the steps in the <a href="#expansion-algorithm">Expansion Algorithm</a>. The
+        <code>input</code> <em class="rfc2119" title="must">must</em> be copied, expanded and returned if there are
+        no errors. If the expansion fails, an appropriate exception <em class="rfc2119" title="must">must</em> be thrown.
+
+        
+
+        
+
+        
+      <table class="parameters"><tr><th>Parameter</th><th>Type</th><th>Nullable</th><th>Optional</th><th>Description</th></tr><tr><td class="prmName">input</td><td class="prmType"><code><a>object or object[] or URL</a></code></td><td class="prmNullFalse">✘</td><td class="prmOptFalse">✘</td><td class="prmDesc">The JSON-LD object or array of JSON-LD objects to perform the expansion upon or an
+            <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> referencing the JSON-LD document to expand.</td></tr><tr><td class="prmName">context</td><td class="prmType"><code><a>object or URL</a></code></td><td class="prmNullTrue">✔</td><td class="prmOptFalse">✘</td><td class="prmDesc">An optional external context to use additionally to the context embedded in
+            <code>input</code> when expanding the <code>input</code>.</td></tr><tr><td class="prmName">callback</td><td class="prmType"><code><a href="#idl-def-JsonLdCallback" class="idlType"><code>JsonLdCallback</code></a></code></td><td class="prmNullFalse">✘</td><td class="prmOptFalse">✘</td><td class="prmDesc">A callback that is called when processing is complete on
+            the given <code>input</code>.</td></tr><tr><td class="prmName">options</td><td class="prmType"><code><a href="#idl-def-JsonLdOptions" class="idlType"><code>JsonLdOptions</code></a></code></td><td class="prmNullFalse">✘</td><td class="prmOptTrue">✔</td><td class="prmDesc">A set of options that <em class="rfc2119" title="may">may</em> affect the expansion algorithm such as, e.g., the
+            input document's base <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.</td></tr></table><div><em>Return type: </em><code><a>void</a></code></div></dd><dt id="widl-JsonLdProcessor-fromRDF-void-QuadArray-input-JsonLdCallback-callback-JsonLdOptions-options"><code>fromRDF</code></dt><dd>Creates a JSON-LD document given an set of <a class="datatype idlType" title="quad" href="#idl-def-quad"><code>Quads</code></a>.
+        
+      <table class="parameters"><tr><th>Parameter</th><th>Type</th><th>Nullable</th><th>Optional</th><th>Description</th></tr><tr><td class="prmName">input</td><td class="prmType"><code><a href="#idl-def-Quad" class="idlType"><code>Quad</code></a>[]</code></td><td class="prmNullFalse">✘</td><td class="prmOptFalse">✘</td><td class="prmDesc">A <a class="tref internalDFN" title="dataset" href="#dfn-dataset">dataset</a> represented as an array of <a class="datatype idlType" title="quad" href="#idl-def-quad"><code>Quads</code></a>.</td></tr><tr><td class="prmName">callback</td><td class="prmType"><code><a href="#idl-def-JsonLdCallback" class="idlType"><code>JsonLdCallback</code></a></code></td><td class="prmNullFalse">✘</td><td class="prmOptFalse">✘</td><td class="prmDesc">A callback that is called when processing is complete on
+            the given <code>input</code>.</td></tr><tr><td class="prmName">options</td><td class="prmType"><code><a href="#idl-def-JsonLdOptions" class="idlType"><code>JsonLdOptions</code></a></code></td><td class="prmNullFalse">✘</td><td class="prmOptTrue">✔</td><td class="prmDesc">A set of options that will affect the algorithm. This includes <code>notType</code>,
+            which if set to <a class="tref internalDFN" title="true" href="#dfn-true">true</a> causes the resulting document to use <code>rdf:type</code>
+            as a property, instead of <code>@type</code>.</td></tr></table><div><em>Return type: </em><code><a>void</a></code></div></dd><dt id="widl-JsonLdProcessor-toRDF-void-object-or-object---or-URL-input-QuadCallback-callback-JsonLdOptions-options"><code>toRDF</code></dt><dd>
+        Processes the <code>input</code> according to the
+        <a href="#convert-to-rdf-algorithm">Convert to RDF Algorithm</a>, calling
+        the provided <code>callback</code> for each <a class="datatype idlType" title="Quad" href="#idl-def-Quad"><code>Quad</code></a> generated.
+        
+
+        
+
+        
+
+      <table class="parameters"><tr><th>Parameter</th><th>Type</th><th>Nullable</th><th>Optional</th><th>Description</th></tr><tr><td class="prmName">input</td><td class="prmType"><code><a>object or object[] or URL</a></code></td><td class="prmNullFalse">✘</td><td class="prmOptFalse">✘</td><td class="prmDesc">The JSON-LD object or array of JSON-LD objects to convert to RDF or a <a href="#idl-def-URL" class="idlType"><code>URL</code></a>
+            referencing the JSON-LD document to convert to RDF.</td></tr><tr><td class="prmName">callback</td><td class="prmType"><code><a href="#idl-def-QuadCallback" class="idlType"><code>QuadCallback</code></a></code></td><td class="prmNullFalse">✘</td><td class="prmOptFalse">✘</td><td class="prmDesc">A callback that is called when a <a class="datatype idlType" title="Quad" href="#idl-def-Quad"><code>Quad</code></a> is created from processing
+            the given <code>input</code>.
+          </td></tr><tr><td class="prmName">options</td><td class="prmType"><code><a href="#idl-def-JsonLdOptions" class="idlType"><code>JsonLdOptions</code></a></code></td><td class="prmNullFalse">✘</td><td class="prmOptTrue">✔</td><td class="prmDesc">A set of options that <em class="rfc2119" title="may">may</em> affect the conversion to RDF such as, e.g.,
+            the input document's base <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.</td></tr></table><div><em>Return type: </em><code><a>void</a></code></div></dd></dl></div>
+
+  </div>
+
+  <div id="callbacks" class="section">
+    <h3><span class="secno">3.3 </span>Callbacks</h3>
+  <div id="jsonldcallback" class="section">
+    <h4><span class="secno">3.3.1 </span>JsonLdCallback</h4>
+    <p>The <a href="#idl-def-JsonLdCallback" class="idlType"><code>JsonLdCallback</code></a> is used to return a processed JSON-LD representation
+      as the result of processing an API method.</p>
+
+    <pre class="idl"><span class="idlInterface" id="idl-def-JsonLdCallback">[<span class="extAttr">NoInterfaceObject Callback</span>]
+interface <span class="idlInterfaceID">JsonLdCallback</span> {
+<span class="idlMethod">    <span class="idlMethType"><a>void</a></span> <span class="idlMethName"><a href="#widl-JsonLdCallback-jsonLd-void-object-or-objectArray-jsonld">jsonLd</a></span> (<span class="idlParam"><span class="idlParamType"><a>object or object</a>[]</span> <span class="idlParamName">jsonld</span></span>);</span>
+};</span>
+</pre><div id="methods-1" class="section"><h2><span class="secno">3.3.1.1 </span>Methods</h2><dl class="methods"><dt id="widl-JsonLdCallback-jsonLd-void-object-or-objectArray-jsonld"><code>jsonLd</code></dt><dd>This callback is invoked when processing is complete.
+      
+      <table class="parameters"><tr><th>Parameter</th><th>Type</th><th>Nullable</th><th>Optional</th><th>Description</th></tr><tr><td class="prmName">jsonld</td><td class="prmType"><code><a>object or object</a>[]</code></td><td class="prmNullFalse">✘</td><td class="prmOptFalse">✘</td><td class="prmDesc">The processed JSON-LD document.</td></tr></table><div><em>Return type: </em><code><a>void</a></code></div></dd></dl></div>
+  </div>
+  <div id="quadcallback" class="section">
+    <h4><span class="secno">3.3.2 </span>QuadCallback</h4>
+    <p>The <a href="#idl-def-QuadCallback" class="idlType"><code>QuadCallback</code></a> is called whenever the processor generates a
+    quad during the <code>quad()</code> call.</p>
+
+    <pre class="idl"><span class="idlInterface" id="idl-def-QuadCallback">[<span class="extAttr">NoInterfaceObject Callback</span>]
+interface <span class="idlInterfaceID">QuadCallback</span> {
+<span class="idlMethod">    <span class="idlMethType"><a>void</a></span> <span class="idlMethName"><a href="#widl-QuadCallback-quad-void-Quad-quad">quad</a></span> (<span class="idlParam"><span class="idlParamType"><a href="#idl-def-Quad" class="idlType"><code>Quad</code></a></span> <span class="idlParamName">quad</span></span>);</span>
+};</span>
+</pre><div id="methods-2" class="section"><h2><span class="secno">3.3.2.1 </span>Methods</h2><dl class="methods"><dt id="widl-QuadCallback-quad-void-Quad-quad"><code>quad</code></dt><dd>This callback is invoked whenever a quad is generated by the processor.
+      
+      <table class="parameters"><tr><th>Parameter</th><th>Type</th><th>Nullable</th><th>Optional</th><th>Description</th></tr><tr><td class="prmName">quad</td><td class="prmType"><code><a href="#idl-def-Quad" class="idlType"><code>Quad</code></a></code></td><td class="prmNullFalse">✘</td><td class="prmOptFalse">✘</td><td class="prmDesc">The quad.</td></tr></table><div><em>Return type: </em><code><a>void</a></code></div></dd></dl></div>
+  </div>
+  </div>
+
+  <div id="data-structures" class="section">
+    <h3><span class="secno">3.4 </span>Data Structures</h3>
+    <p>This section describes datatype definitions used within the JSON-LD API.</p>
+
+    <div id="url" class="section">
+    <h4><span class="secno">3.4.1 </span>URL</h4>
+    <p>The <a href="#idl-def-URL" class="idlType"><code>URL</code></a> datatype is a string representation of an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.</p>
+    <pre class="idl"><span class="idlTypedef" id="idl-def-URL">typedef <span class="idlTypedefType"><a>DOMString</a></span> <span class="idlTypedefID">URL</span>;</span></pre><div class="idlTypedefDesc">
+      This datatype indicates that the <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> is interpreted as a Universal Resource
+      Locator
+      identifying a document, which when parsed as JSON yields either a <code>JSON object</code>
+      or <code>array</code>.
+    </div>
+    </div>
+
+    <div id="jsonldoptions" class="section">
+    <h4><span class="secno">3.4.2 </span>JsonLdOptions</h4>
+    <p>The <a href="#idl-def-JsonLdOptions" class="idlType"><code>JsonLdOptions</code></a> type is used to convert a set of options to an interface method.</p>
+    <pre class="idl"><span class="idlTypedef" id="idl-def-JsonLdOptions">typedef <span class="idlTypedefType"><a>object</a></span> <span class="idlTypedefID">JsonLdOptions</span>;</span></pre><div class="idlTypedefDesc">
+      <dt><a href="#idl-def-URL" class="idlType"><code>URL</code></a> base</dt>
+      <dd>The Base <abbr title="Internationalized Resource Identifier">IRI</abbr> to use when expanding the document. This overrides the value of
+        <em>input</em> if it is a <a href="#idl-def-URL" class="idlType"><code>URL</code></a> or if it is a <code>object</code> or <code>object[]</code>.</dd>
+      <dt>boolean optimize</dt>
+      <dd>If set to <code>true</code>, the JSON-LD processor is allowed to
+        optimize the output of the <a href="#compaction-algorithm">Compaction Algorithm</a>
+        to produce even compacter representations. The algorithm for compaction
+        optimization is beyond the scope of this specification and thus
+        not defined. Consequently, different implementations <em class="rfc2119" title="may">may</em> implement
+        different optimization algorithms.</dd>
+      <dt>boolean noType</dt>
+      <dd>If set to <code>true</code>, the JSON-LD processor will not use the
+        <code>@type</code> property when generating the output, and will use the
+        expanded <code>rdf:type</code> <abbr title="Internationalized Resource Identifier">IRI</abbr> as the property instead of <code>@type</code>.</dd>
+    </div>
+    </div>
+
+    <p>The following data structures are used for representing data about
+      RDF quads. They are used for normalization, <a>fromRDF</a>,
+      and from <a>toRDF</a> interfaces.
+    </p>
+
+    <div id="quad" class="section">
+    <h4><span class="secno">3.4.3 </span>Quad</h4>
+    <p>The <a href="#idl-def-Quad" class="idlType"><code>Quad</code></a> interface represents an RDF Quad.
+      See [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>] definition for
+      <cite><a href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-triple">RDF triple</a></cite>,
+      which most closely aligns to <a href="#idl-def-Quad" class="idlType"><code>Quad</code></a>.
+    </p>
+    <pre class="idl"><span class="idlInterface" id="idl-def-Quad">[<span class="extAttr">NoInterfaceObject</span>]
+interface <span class="idlInterfaceID">Quad</span> {
+<span class="idlAttribute">    readonly attribute <span class="idlAttrType"><a href="#idl-def-Node" class="idlType"><code>Node</code></a></span>  <span class="idlAttrName"><a href="#widl-Quad-subject">subject</a></span>;</span>
+<span class="idlAttribute">    readonly attribute <span class="idlAttrType"><a href="#idl-def-Node" class="idlType"><code>Node</code></a></span>  <span class="idlAttrName"><a href="#widl-Quad-predicate">predicate</a></span>;</span>
+<span class="idlAttribute">    readonly attribute <span class="idlAttrType"><a href="#idl-def-Node" class="idlType"><code>Node</code></a></span>  <span class="idlAttrName"><a href="#widl-Quad-object">object</a></span>;</span>
+<span class="idlAttribute">    readonly attribute <span class="idlAttrType"><a href="#idl-def-Node" class="idlType"><code>Node</code></a>?</span> <span class="idlAttrName"><a href="#widl-Quad-graphName">graphName</a></span>;</span>
+};</span>
+</pre><div id="attributes" class="section"><h2><span class="secno">3.4.3.1 </span>Attributes</h2><dl class="attributes"><dt id="widl-Quad-graphName"><code>graphName</code> of type <span class="idlAttrType"><a href="#idl-def-Node" class="idlType"><code>Node</code></a></span>, readonly, nullable</dt><dd>If present, the name associated with the <a href="#idl-def-Quad" class="idlType"><code>Quad</code></a> identifying
+        it as a member of a <a class="tref internalDFN" title="named_graph" href="#dfn-named_graph">named graph</a>. If it is missing, the quad
+        is a member of the <a class="tref internalDFN" title="default_graph" href="#dfn-default_graph">default graph</a>.
+        <div class="issue"><div class="issue-title"><span>Issue 4</span></div><div class="">This element is at risk, and may be removed.</div></div>
+      </dd><dt id="widl-Quad-object"><code>object</code> of type <span class="idlAttrType"><a href="#idl-def-Node" class="idlType"><code>Node</code></a></span>, readonly</dt><dd>The <a class="tref internalDFN" title="object" href="#dfn-object">object</a> associated with the <a href="#idl-def-Quad" class="idlType"><code>Quad</code></a>.</dd><dt id="widl-Quad-predicate"><code>predicate</code> of type <span class="idlAttrType"><a href="#idl-def-Node" class="idlType"><code>Node</code></a></span>, readonly</dt><dd>The predicate associated with the <a href="#idl-def-Quad" class="idlType"><code>Quad</code></a>.
+        Within JSON-LD, an <dfn title="rdf_predicate" id="dfn-rdf_predicate">RDF predicate</dfn> is refered to as a
+        <a class="tref internalDFN" title="property" href="#dfn-property">property</a></dd><dt id="widl-Quad-subject"><code>subject</code> of type <span class="idlAttrType"><a href="#idl-def-Node" class="idlType"><code>Node</code></a></span>, readonly</dt><dd>The <a class="tref internalDFN" title="subject" href="#dfn-subject">subject</a> associated with the <a href="#idl-def-Quad" class="idlType"><code>Quad</code></a>.</dd></dl></div>
+    </div>
+
+    <div id="node" class="section">
+    <h4><span class="secno">3.4.4 </span>Node</h4>
+    <p><a class="datatype idlType" title="Node" href="#idl-def-Node"><code>Node</code></a> is the base class of <a class="datatype idlType" title="IRI" href="#idl-def-IRI"><code><abbr title="Internationalized Resource Identifier">IRI</abbr></code></a>,
+    <a class="datatype idlType" title="BlankNode" href="#idl-def-BlankNode"><code>BlankNode</code></a>, and <a class="datatype idlType" title="Literal" href="#idl-def-Literal"><code>Literal</code></a>. It is the IDL
+    representation of a <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a> <a class="tref internalDFN" title="node" href="#dfn-node">node</a>.</p>
+    <pre class="idl"><span class="idlInterface" id="idl-def-Node">[<span class="extAttr">NoInterfaceObject</span>]
+interface <span class="idlInterfaceID">Node</span> {
+};</span>
+</pre>
+    </div>
+
+    <div id="iri" class="section">
+    <h4><span class="secno">3.4.5 </span><abbr title="Internationalized Resource Identifier">IRI</abbr></h4>
+    <p>A <a class="tref internalDFN" title="node" href="#dfn-node">node</a> that is an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.</p>
+    <pre class="idl"><span class="idlInterface" id="idl-def-IRI">[<span class="extAttr">NoInterfaceObject</span>]
+interface <span class="idlInterfaceID">IRI</span> : <span class="idlSuperclass"><a href="#idl-def-Node" class="idlType"><code>Node</code></a></span> {
+<span class="idlAttribute">    readonly attribute <span class="idlAttrType"><a>DOMString</a></span> <span class="idlAttrName"><a href="#widl-IRI-value">value</a></span>;</span>
+};</span>
+</pre><div id="attributes-1" class="section"><h2><span class="secno">3.4.5.1 </span>Attributes</h2><dl class="attributes"><dt id="widl-IRI-value"><code>value</code> of type <span class="idlAttrType"><a>DOMString</a></span>, readonly</dt><dd>The <abbr title="Internationalized Resource Identifier">IRI</abbr> identifier of the <a class="tref internalDFN" title="node" href="#dfn-node">node</a> as a [<cite><a class="bibref" rel="biblioentry" href="#bib-UNICODE">UNICODE</a></cite>] string.</dd></dl></div>
+    </div>
+
+    <div id="blank-node" class="section">
+    <h4><span class="secno">3.4.6 </span><dfn title="blank_node" id="dfn-blank_node">Blank Node</dfn></h4>
+
+    <p>A <a class="tref internalDFN" title="node" href="#dfn-node">node</a> in the <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a> that
+    does not contain a de-reference-able identifier because it is either
+    ephemeral in nature or does not contain information that needs to be linked
+    to from outside of the <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a>.
+    A blank node is assigned an identifier starting
+    with the prefix <code>_:</code> and an implementation dependent,
+    auto-generated suffix that is unique to all information associated with the
+    particular blank node.
+    </p>
+
+    <pre class="idl"><span class="idlInterface" id="idl-def-BlankNode">[<span class="extAttr">NoInterfaceObject</span>]
+interface <span class="idlInterfaceID">BlankNode</span> : <span class="idlSuperclass"><a href="#idl-def-Node" class="idlType"><code>Node</code></a></span> {
+<span class="idlAttribute">    readonly attribute <span class="idlAttrType"><a>DOMString</a></span> <span class="idlAttrName"><a href="#widl-BlankNode-identifier">identifier</a></span>;</span>
+};</span>
+</pre><div id="attributes-2" class="section"><h2><span class="secno">3.4.6.1 </span>Attributes</h2><dl class="attributes"><dt id="widl-BlankNode-identifier"><code>identifier</code> of type <span class="idlAttrType"><a>DOMString</a></span>, readonly</dt><dd>The temporary identifier of the <a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">blank node</a>.
+        The <code>identifier</code> <em class="rfc2119" title="must not">must not</em> be relied upon in any way between two
+        separate processing runs of the same document or with a different document.</dd></dl></div>
+
+    <div class="note"><div class="note-title"><span>Note</span></div><p class="">Developers and authors must not assume that the
+      value of a <a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">blank node</a> will remain the same between two
+      processing runs. <a href="#idl-def-BlankNode" class="idlType"><code>BlankNode</code></a> values are only valid for the
+      most recent processing run on the document. <a href="#idl-def-BlankNode" class="idlType"><code>BlankNode</code></a>
+      values will often be generated differently by different processors.</p></div>
+
+    <div class="note"><div class="note-title"><span>Note</span></div><p class="">Implementers <em class="rfc2119" title="must">must</em> ensure that <a href="#idl-def-BlankNode" class="idlType"><code>BlankNode</code></a> values are unique
+      within the current environment, two <a class="datatype idlType" title="blanknode" href="#idl-def-blanknode"><code>BlankNodes</code></a> are considered equal if, and only
+      if, their values are strictly equal.</p></div>
+    </div>
+
+    <div id="literal" class="section">
+      <h4><span class="secno">3.4.7 </span>Literal</h4>
+      <p>Literals represent values such as numbers, dates and strings in
+        RDF data. A <a class="datatype idlType" title="Literal" href="#idl-def-Literal"><code>Literal</code></a> is comprised of three attributes:
+      </p>
+
+      <ul>
+        <li>a lexical form of the <code>value</code></li>
+        <li>an optional <code>language</code> tag</li>
+        <li>a <code>datatype</code> specified by an <a class="datatype idlType" title="IRI" href="#idl-def-IRI"><code><abbr title="Internationalized Resource Identifier">IRI</abbr></code></a></li>
+      </ul>
+
+      <p>Literals representing plain text in a natural language may have a
+        <code>language</code> tag specified by a string token, as specified in
+        [<cite><a class="bibref" rel="biblioentry" href="#bib-BCP47">BCP47</a></cite>], normalized to lowercase
+        (e.g., <code>'en'</code>, <code>'fr'</code>, <code>'en-gb'</code>).
+        They also have a datatype attribute such as <code>xsd:string</code>.
+        If unspecified, the <code>datatype</code> defaults to <code>xsd:string</code>.
+      </p>
+
+      <p>Literals representing values with a specific datatype, such as
+        the integer 72, may have a <code>datatype</code> attribute specified in the form
+        of a <a href="#idl-def-IRI" class="idlType"><code>IRI</code></a> (e.g.,
+        <code>xsd:integer</code>).</p>
+
+      <p> See[<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>] definition for
+      <cite><a href="http://www.w3.org/TR/rdf11-concepts/#dfn-literal">literal</a></cite>.</p>
+
+      <pre class="idl"><span class="idlInterface" id="idl-def-Literal">[<span class="extAttr">NoInterfaceObject</span>]
+interface <span class="idlInterfaceID">Literal</span> : <span class="idlSuperclass"><a href="#idl-def-Node" class="idlType"><code>Node</code></a></span> {
+<span class="idlAttribute">    readonly attribute <span class="idlAttrType"><a>DOMString</a></span>  <span class="idlAttrName"><a href="#widl-Literal-value">value</a></span>;</span>
+<span class="idlAttribute">    readonly attribute <span class="idlAttrType"><a>DOMString</a>?</span> <span class="idlAttrName"><a href="#widl-Literal-language">language</a></span>;</span>
+<span class="idlAttribute">    readonly attribute <span class="idlAttrType"><a href="#idl-def-IRI" class="idlType"><code>IRI</code></a>?</span>       <span class="idlAttrName"><a href="#widl-Literal-datatype">datatype</a></span>;</span>
+};</span>
+</pre><div id="attributes-3" class="section"><h2><span class="secno">3.4.7.1 </span>Attributes</h2><dl class="attributes"><dt id="widl-Literal-datatype"><code>datatype</code> of type <span class="idlAttrType"><a href="#idl-def-IRI" class="idlType"><code>IRI</code></a></span>, readonly, nullable</dt><dd>An optional datatype identified by a <abbr title="Internationalized Resource Identifier">IRI</abbr>.</dd><dt id="widl-Literal-language"><code>language</code> of type <span class="idlAttrType"><a>DOMString</a></span>, readonly, nullable</dt><dd>An optional language tag as defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-BCP47">BCP47</a></cite>], normalized to lowercase.</dd><dt id="widl-Literal-value"><code>value</code> of type <span class="idlAttrType"><a>DOMString</a></span>, readonly</dt><dd>The lexical form of the Literal's value.</dd></dl></div>
+    </div>
+  </div>
+
+</div>
+
+<div id="algorithms" class="section">
+
+<!-- OddPage -->
+<h2><span class="secno">4. </span>Algorithms</h2>
+
+<p>All algorithms described in this section are intended to operate on
+language-native data structures. That is, the serialization to a text-based
+JSON document isn't required as input or output to any of these algorithms and
+language-native data structures <em class="rfc2119" title="must">must</em> be used where applicable.</p>
+
+<div id="algorithm-terms" class="section">
+  <h3><span class="secno">4.1 </span>Algorithm Terms</h3>
+  <dl>
+    <dt><dfn title="initial_context" id="dfn-initial_context">initial context</dfn></dt>
+    <dd>
+      a context that is specified to the algorithm before processing begins. The contents of the
+      initial context is defined in <a href="#appendix-a">Appendix A</a>.
+    </dd>
+    <dt><dfn title="active_subject" id="dfn-active_subject">active subject</dfn></dt>
+    <dd>
+      the currently active subject that the processor should use when
+      processing.
+    </dd>
+    <dt><dfn title="active_property" id="dfn-active_property">active property</dfn></dt>
+    <dd>
+      the currently active property that the processor should use when
+      processing. The active property is represented in the original lexical form, which
+      is used for finding coercion mappings in the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>.
+    </dd>
+    <dt><dfn title="active_object" id="dfn-active_object">active object</dfn></dt>
+    <dd>
+      the currently active object that the processor should use when
+      processing.
+    </dd>
+    <dt><dfn title="active_context" id="dfn-active_context">active context</dfn></dt>
+    <dd>
+      a context that is used to resolve <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s while the processing
+      algorithm is running. The <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> is the context
+      contained within the <a class="tref internalDFN" title="processor_state" href="#dfn-processor_state">processor state</a>.
+    </dd>
+    <dt><dfn title="compact_iri" id="dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></dfn></dt>
+    <dd>
+      a compact <abbr title="Internationalized Resource Identifier">IRI</abbr> is has the form of <a class="tref internalDFN" title="prefix" href="#dfn-prefix">prefix</a> and <em>suffix</em> and is used as a way
+      of expressing an <abbr title="Internationalized Resource Identifier">IRI</abbr> without needing to define separate <a class="tref internalDFN" title="term" href="#dfn-term">term</a> definitions for
+      each <abbr title="Internationalized Resource Identifier">IRI</abbr> contained within a common vocabulary identified by <a class="tref internalDFN" title="prefix" href="#dfn-prefix">prefix</a>.
+    </dd>
+    <dt><dfn title="local_context" id="dfn-local_context">local context</dfn></dt>
+    <dd>
+      a context that is specified within a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a>,
+      specified via the <code>@context</code> <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a>.
+    </dd>
+    <dt><dfn title="processor_state" id="dfn-processor_state">processor state</dfn></dt>
+    <dd>
+      the <a class="tref internalDFN" title="processor_state" href="#dfn-processor_state">processor state</a>, which includes the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active
+      context</a>, <a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">active subject</a>, and
+      <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>. The <a class="tref internalDFN" title="processor_state" href="#dfn-processor_state">processor state</a> is managed
+      as a stack with elements from the previous <a class="tref internalDFN" title="processor_state" href="#dfn-processor_state">processor state</a>
+      copied into a new <a class="tref internalDFN" title="processor_state" href="#dfn-processor_state">processor state</a> when entering a new
+      <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a>.
+    </dd>
+    <dt><dfn title="json-ld_input" id="dfn-json-ld_input">JSON-LD input</dfn></dt>
+    <dd>
+      The JSON-LD data structure that is provided as input to the algorithm.
+    </dd>
+    <dt><dfn title="json-ld_output" id="dfn-json-ld_output">JSON-LD output</dfn></dt>
+    <dd>
+      The JSON-LD data structure that is produced as output by the algorithm.
+    </dd>
+    <dt><dfn title="term" id="dfn-term">term</dfn></dt><dd>
+      A <a class="tref internalDFN" title="term" href="#dfn-term">term</a> is a short word defined in a context that <em class="rfc2119" title="may">may</em> be expanded to an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>
+    </dd>
+    <dt><dfn title="prefix" id="dfn-prefix">prefix</dfn></dt><dd>
+      A <a class="tref internalDFN" title="prefix" href="#dfn-prefix">prefix</a> is a <a class="tref internalDFN" title="term" href="#dfn-term">term</a> that expands to a vocabulary base <abbr title="Internationalized Resource Identifier">IRI</abbr>. It
+      is typically used along with a <em>suffix</em> to form a <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a> to create an <abbr title="Internationalized Resource Identifier">IRI</abbr>
+      within a vocabulary.
+    </dd>
+    <dt><dfn title="language-tagged_literal" id="dfn-language-tagged_literal">language-tagged literal</dfn></dt><dd>
+      A <a class="tref internalDFN" title="language-tagged_literal" href="#dfn-language-tagged_literal">language-tagged literal</a> is a <a class="tref internalDFN" title="literal" href="#dfn-literal">literal</a> without a datatype, including
+      a language.
+      See <cite><a href="http://www.w3.org/TR/rdf11-concepts/#dfn-language-tagged-literal">languaged-tagged literal</a></cite> in [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>].
+    </dd>
+    <dt><dfn title="typed_literal" id="dfn-typed_literal">typed literal</dfn></dt><dd>
+      A <a class="tref internalDFN" title="typed_literal" href="#dfn-typed_literal">typed literal</a> is a <a class="tref internalDFN" title="literal" href="#dfn-literal">literal</a> with an associated <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>
+      which indicates the literal's datatype.
+      See <cite><a href="http://www.w3.org/TR/rdf11-concepts/#dfn-typed-literal">languaged-tagged literal</a></cite> in [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>].
+    </dd>
+  </dl>
+</div>
+
+<div id="context-processing" class="section">
+  <h3 id="context"><span class="secno">4.2 </span>Context Processing</h3>
+  <p>Processing of JSON-LD data structure is managed recursively.
+    During processing, each rule is applied using information provided by the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>.
+    Processing begins by pushing a new <a class="tref internalDFN" title="processor_state" href="#dfn-processor_state">processor state</a> onto the <a class="tref internalDFN" title="processor_state" href="#dfn-processor_state">processor state</a> stack and
+    initializing the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> with the <a class="tref internalDFN" title="initial_context" href="#dfn-initial_context">initial context</a>.
+    If a <a class="tref internalDFN" title="local_context" href="#dfn-local_context">local context</a> is encountered,
+    information from the <a class="tref internalDFN" title="local_context" href="#dfn-local_context">local context</a> is merged into the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>.</p>
+  <p>The <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> is used for expanding properties and values of a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> (or elements
+    of an array) using a <dfn title="term_mapping" id="dfn-term_mapping">term mapping</dfn>. It is also used to maintain
+    <dfn title="coercion_mapping" id="dfn-coercion_mapping">coercion mapping</dfn>s from terms to datatypes, <dfn title="language_mapping" id="dfn-language_mapping">language mapping</dfn>s from terms to language codes,
+    and <dfn title="list_mapping" id="dfn-list_mapping">list mapping</dfn>s and <dfn title="set_mapping" id="dfn-set_mapping">set mapping</dfn>s for terms. Processors <em class="rfc2119" title="must">must</em> use the
+    lexical form of the property when creating a mapping, as lookup is performed on lexical forms, not
+    expanded <abbr title="Internationalized Resource Identifier">IRI</abbr> representations.</p>
+  <p>A <a class="tref internalDFN" title="local_context" href="#dfn-local_context">local context</a> is identified within a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> having a <code>@context</code>
+    property with a <a class="tref internalDFN" title="string" href="#dfn-string">string</a>, <a class="tref internalDFN" title="array" href="#dfn-array">array</a> or a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> value.
+    When processing a <a class="tref internalDFN" title="local_context" href="#dfn-local_context">local context</a>, special processing rules apply:</p>
+  <ol class="algorithm">
+    <li>Create a new, empty <a class="tref internalDFN" title="local_context" href="#dfn-local_context">local context</a>.</li>
+    <li>Let <em>context</em> be the value of <code>@context</code>
+      <ol class="algorithm">
+        <li id="process-context">If <em>context</em> equals <a class="tref internalDFN" title="null" href="#dfn-null">null</a>, reset the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>
+          to the <a class="tref internalDFN" title="initial_context" href="#dfn-initial_context">initial context</a>.</li>
+        <li>If <em>context</em> is an <a class="tref internalDFN" title="array" href="#dfn-array">array</a>, process each element as <em>context</em> in order
+          by starting at <a href="#process-context">Step 2.1</a>.</li>
+        <li>If <em>context</em> is a <a class="tref internalDFN" title="string" href="#dfn-string">string</a>, it <em class="rfc2119" title="must">must</em> have a lexical form of <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a>.
+          <ol class="algorithm">
+            <li>Dereference <em>context</em>.</li>
+            <li>If the resulting document is a JSON document, extract the top-level <code>@context</code>
+              element using the JSON Pointer &quot;/@context&quot; as described in [<cite><a class="bibref" rel="biblioentry" href="#bib-JSON-POINTER">JSON-POINTER</a></cite>]. Set <em>context</em>
+              to the extracted content and process it by starting at <a href="#process-context">Step 2.1</a>.</li>
+          </ol>
+        </li>
+        <li>If <em>context</em> is a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a>, perform the following steps:
+          <ol class="algorithm">
+            <li>If <em>context</em> has a <code>@language</code> property, it <em class="rfc2119" title="must">must</em> have a value of a
+              simple <a class="tref internalDFN" title="string" href="#dfn-string">string</a> or <a class="tref internalDFN" title="null" href="#dfn-null">null</a>. Add the language to the <a class="tref internalDFN" title="local_context" href="#dfn-local_context">local context</a>.</li>
+            <li id="object-context">Otherwise, for each property in <em>context</em> perform the following steps:
+              <ol class="algorithm">
+                <li>If the property's value is a simple <a class="tref internalDFN" title="string" href="#dfn-string">string</a>, determine the <abbr title="Internationalized Resource Identifier">IRI</abbr> mapping value by
+                  performing <a href="#iri-expansion"><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion</a> on the associated value. If the result of the <abbr title="Internationalized Resource Identifier">IRI</abbr>
+                  mapping is an <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a>, merge the property into the <a class="tref internalDFN" title="local_context" href="#dfn-local_context">local context</a>
+                  <a class="tref internalDFN" title="term_mapping" href="#dfn-term_mapping">term mapping</a>, unless the property is a JSON-LD <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a>, in which
+                  case throw an exception.</li>
+                <li>Otherwise, if the property's value is <a class="tref internalDFN" title="null" href="#dfn-null">null</a> remove mapping, coercion,
+                  container and language information associated with property from the
+                  <a class="tref internalDFN" title="local_context" href="#dfn-local_context">local context</a>.</li>
+                <li>Otherwise, the <em>property</em>'s <em>value</em> <em class="rfc2119" title="must">must</em> be a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a>.
+                  <ol class="algorithm">
+                    <li>If the <em>property</em> is a JSON-LD <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a> and the value has
+                      <code>@id</code>, <code>@language</code> or <code>@type</code> properties, throw an exception.
+                      <div class="issue"><div class="issue-title"><span>Issue 5</span></div><div class="">Undecided if <code>@type</code> or <code>@graph</code> can take a
+                        <code>@container</code> with <code>@set</code>.
+                      </div></div>
+                    </li>
+                    <li>If the <em>property</em> has the form of <a class="tref internalDFN" title="term" href="#dfn-term">term</a>, its <em>value</em> <em class="rfc2119" title="must">must</em> have an
+                      <code>@id</code> property with a string value which <em class="rfc2119" title="must">must</em> have the form of a <a class="tref internalDFN" title="term" href="#dfn-term">term</a>,
+                      <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a>, or <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a>. Determine the <abbr title="Internationalized Resource Identifier">IRI</abbr> mapping
+                      by performing <a href="#iri-expansion"><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion</a> on the associated value.
+                      If the result of the <abbr title="Internationalized Resource Identifier">IRI</abbr> mapping is an <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a>, merge the
+                      <em>property</em> into the <a class="tref internalDFN" title="local_context" href="#dfn-local_context">local context</a> <a class="tref internalDFN" title="term_mapping" href="#dfn-term_mapping">term mapping</a>.</li>
+                    <li>If the <em>property</em> has the form of of a <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a> or <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a>,
+                      the <em>value</em> <em class="rfc2119" title="may">may</em> have a <code>@id</code> property with a string value which <em class="rfc2119" title="must">must</em> have the
+                      form of a <a class="tref internalDFN" title="term" href="#dfn-term">term</a>, <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a>, or absolute <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.
+                      Determine the <abbr title="Internationalized Resource Identifier">IRI</abbr> mapping by performing <a href="#iri-expansion"><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion</a> on the associated
+                      value. If the result of the <abbr title="Internationalized Resource Identifier">IRI</abbr> mapping is an <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a>, merge the
+                      <em>property</em> into the <a class="tref internalDFN" title="local_context" href="#dfn-local_context">local context</a> <a class="tref internalDFN" title="term_mapping" href="#dfn-term_mapping">term mapping</a>.</li>
+                    <li>If the <em>value</em> has a <code>@type</code> property, its value <em class="rfc2119" title="must">must</em> have the form of a <a class="tref internalDFN" title="term" href="#dfn-term">term</a>,
+                      <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a>, <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a>, or the <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a> <code>@id</code>.
+                      Determine the <abbr title="Internationalized Resource Identifier">IRI</abbr> by performing <a href="#iri-expansion"><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion</a> on the associated value.
+                      If the result of the <abbr title="Internationalized Resource Identifier">IRI</abbr> mapping is an <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a> or <code>@id</code>, merge into the
+                      <a class="tref internalDFN" title="local_context" href="#dfn-local_context">local context</a> <a class="tref internalDFN" title="coercion_mapping" href="#dfn-coercion_mapping">coercion mapping</a> using the lexical value of the <em>property</em>.</li>
+                    <li>If the <em>value</em> has a <code>@container</code> property, its value <em class="rfc2119" title="must">must</em> be <code>@list</code> or
+                      <code>@set</code>. Merge the <a class="tref internalDFN" title="list_mapping" href="#dfn-list_mapping">list mapping</a> or <a class="tref internalDFN" title="set_mapping" href="#dfn-set_mapping">set mapping</a> into the
+                      <a class="tref internalDFN" title="local_context" href="#dfn-local_context">local context</a> using the lexical value of the <em>property</em>.</li>
+                    <li>If the <em>value</em> has a <code>@language</code> property but no <code>@type</code> property, the value of the
+                      <code>@language</code> property <em class="rfc2119" title="must">must</em> be a <a class="tref internalDFN" title="string" href="#dfn-string">string</a> or <a class="tref internalDFN" title="null" href="#dfn-null">null</a>.
+                      Merge the <a class="tref internalDFN" title="language_mapping" href="#dfn-language_mapping">language mapping</a> into the <a class="tref internalDFN" title="local_context" href="#dfn-local_context">local context</a> using the lexical value of the
+                      <em>property</em>.</li>
+                  </ol>
+                </li>
+                <li>Merge the <a class="tref internalDFN" title="local_context" href="#dfn-local_context">local context</a> into the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>.</li>
+                <li>Repeat <a href="#object-context">Step 2.4.2</a> until no entries are added to the <a class="tref internalDFN" title="local_context" href="#dfn-local_context">local
+                  context</a>.</li>
+              </ol>
+            </li>
+          </ol>
+        </li>
+      </ol>
+    </li>
+  </ol>
+
+  <div class="note"><div class="note-title"><span>Note</span></div><p class="">It can be difficult to distinguish between a <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a> and an <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a>,
+    as a <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a> may seem to be a valid <abbr title="Internationalized Resource Identifier">IRI</abbr> <em>scheme</em>. When performing repeated <abbr title="Internationalized Resource Identifier">IRI</abbr> expansion,
+    a term used as a prefix may not have a valid mapping due to dependencies in resolving term definitions. By
+    continuing <a href="#object-context">Step 2.3.2</a> until no changes are made, mappings to IRIs created
+    using an undefined term prefix will eventually resolve to <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a>s.</p></div>
+
+  <div class="issue"><div class="issue-title"><span>Issue 6</span></div><p class=""><a href="https://github.com/json-ld/json-ld.org/issues/43">Issue 43</a>
+    concerns performing <abbr title="Internationalized Resource Identifier">IRI</abbr> expansion in the key position of a context definition.</p></div>
+</div>
+
+<div id="iri-expansion" class="section">
+  <h3><span class="secno">4.3 </span><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion</h3>
+  <p>Keys and some values are evaluated to produce an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>. This section defines an algorithm for
+    transforming a value representing an <abbr title="Internationalized Resource Identifier">IRI</abbr> into an actual <abbr title="Internationalized Resource Identifier">IRI</abbr>.</p>
+  <p><a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>s may be represented as an <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a>, a <a class="tref internalDFN" title="term" href="#dfn-term">term</a> or a <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a>.</p>
+  <p>An <dfn title="absolute_iri" id="dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></dfn> is defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3987">RFC3987</a></cite>] containing a <em>scheme</em> along with
+    <em>path</em> and optional <em>query</em> and fragment segments. A <dfn title="relative_iri" id="dfn-relative_iri">relative <abbr title="Internationalized Resource Identifier">IRI</abbr></dfn> is an <abbr title="Internationalized Resource Identifier">IRI</abbr>
+    that is relative some other <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a>; in the case of JSON-LD this is the base location
+    of the document.</p>
+
+  <p>The algorithm for generating an <abbr title="Internationalized Resource Identifier">IRI</abbr> is:
+    </p><ol class="algorithm">
+      <li>If the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> contains a <a class="tref internalDFN" title="term" href="#dfn-term">term</a> mapping for the value using
+        a case-sensitive comparison, use the mapped value as an <abbr title="Internationalized Resource Identifier">IRI</abbr>.</li>
+      <li>Otherwise, split the value into a <em>prefix</em> and <em>suffix</em> from the first occurrence of ':'.</li>
+      <li>If the prefix is a '_' (underscore), the value represents a named <a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">blank node</a>.</li>
+      <li>If the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> contains a <a class="tref internalDFN" title="term" href="#dfn-term">term</a> mapping for <em>prefix</em> using
+        a case-sensitive comparison, and <em>suffix</em> does not does not begin with '//'
+        (i.e., it does not match a <em>hier-part</em> including
+        <em>authority</em> (as defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3986">RFC3986</a></cite>]), generate an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>
+        by prepending the mapped prefix to the (possibly empty) suffix using textual concatenation. Note that an empty
+        suffix and no suffix (meaning the value contains no ':' string at all) are treated equivalently.</li>
+      <li>Otherwise, use the value directly as an <abbr title="Internationalized Resource Identifier">IRI</abbr>.</li>
+    </ol>
+  <p></p>
+  <div class="note"><div class="note-title"><span>Note</span></div><p class="">
+    Previous versions of this specification used <code>@base</code> and <code>@vocab</code> to define <abbr title="Internationalized Resource Identifier">IRI</abbr> prefixes
+    used to resolve <a class="tref internalDFN" title="relative_iri" href="#dfn-relative_iri">relative IRIs</a>. It was determined that this added too much complexity, but the issue
+    can be re-examined in the future based on community input.
+  </p></div>
+</div>
+
+<div id="iri-compaction" class="section">
+  <h3><span class="secno">4.4 </span><abbr title="Internationalized Resource Identifier">IRI</abbr> Compaction</h3>
+  <p>Some keys and values are expressed using <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>s. This section defines an
+    algorithm for transforming an <abbr title="Internationalized Resource Identifier">IRI</abbr> (<em>iri</em>) to a <a class="tref internalDFN" title="term" href="#dfn-term">term</a> or <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a> using the
+    <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s specified in the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> using an optional <em>value</em>.</p>
+
+<div id="iri-compaction-algorithm" class="section">
+  <h4><span class="secno">4.4.1 </span><abbr title="Internationalized Resource Identifier">IRI</abbr> Compaction Algorithm</h4>
+  <p>The algorithm for generating a <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a> is:
+    </p><ol class="algorithm">
+      <li>Create an empty list of terms <em>terms</em> that will be populated with
+        <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s that are ranked according to how closely they match
+        <em>value</em>. Initialize <em>highest rank</em> to <code>0</code>,
+        and set a flag <em>list container</em> to <code>false</code>.</li>
+      <li>For each <em>term</em> in the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>:
+        <ol class="algorithm">
+          <li>If the <em>term</em>'s <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> is not a complete match against
+            <em>iri</em>, continue to the next <em>term</em>.</li>
+          <li>If <em>value</em> is a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> containing only the property <code>@list</code>:
+            <ol class="algorithm">
+              <li>If <em>term</em> has a <code>@container</code> set to <code>@set</code>, continue
+                to the next <em>term</em>.</li>
+              <li>If <em>list container</em> is <code>true</code> and <em>term</em> does not have a
+                <code>container</code> set to <code>@list</code>, continue to the next <em>term</em>.</li>
+            </ol>
+          </li>
+          <li>Otherwise, if <em>term</em> has a <code>container</code> set to <code>@list</code>,
+            continue to the next <em>term</em>.</li>
+          <li>Set <em>rank</em> to the <a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">term rank</a> of <em>value</em> by passing
+            passing <em>term</em>, <em>value</em>, and <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> to
+            the <a href="#term-rank-algorithm">Term Rank Algorithm</a>.</li>
+          <li>If <em>rank</em> is greater than <code>0</code>:
+            <ol class="algorithm">
+              <li>If <em>term</em> has a <code>container</code> set to <code>@set</code>, then add
+                <code>1</code> to <em>rank</em>.</li>
+              <li>If <em>value</em> is a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> containing only the property <code>@list</code>
+                and <em>list container</em> is <code>false</code> and <em>term</em> has a <code>container</code>
+                set to <code>@list</code>, then set <em>list container</em> to <code>true</code>, clear
+                <em>terms</em>, set <em>highest rank</em> to <em>rank</em>, and add <em>term</em> to <em>terms</em>.</li>
+              <li>Otherwise, if <em>rank</em> is greater than or equal to <em>highest rank</em>:
+                <ol class="algorithm">
+                  <li>If <em>rank</em> is greater than <em>highest rank</em>, clear <em>terms</em> and set
+                    <em>highest rank</em> to <em>rank</em>.</li>
+                  <li>Add <em>term</em> to <em>terms</em>.</li>
+                </ol>
+              </li>
+            </ol>
+          </li>
+        </ol>
+      </li>
+      <li>If <em>terms</em> is empty, add a <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a> representation of <em>iri</em>
+        for each <a class="tref internalDFN" title="term" href="#dfn-term">term</a> in the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> which
+        maps to an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> which is a prefix for <em>iri</em> where
+        the resulting <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a> is not a <a class="tref internalDFN" title="term" href="#dfn-term">term</a> in the
+        <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>. The resulting <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a> is the
+        <a class="tref internalDFN" title="term" href="#dfn-term">term</a> associated with the partially
+        matched <abbr title="Internationalized Resource Identifier">IRI</abbr> in the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> concatenated with a
+        colon (:) character and the unmatched part of <em>iri</em>.</li>
+      <li>If <em>terms</em> is empty, return <em>iri</em>.</li>
+      <li>Otherwise, return the shortest and lexicographically least value in <em>terms</em>.</li>
+    </ol>
+  <p></p>
+</div>
+
+<div id="term-rank-algorithm" class="section">
+<h4><span class="secno">4.4.2 </span>Term Rank Algorithm</h4>
+<p>When selecting among multiple possible terms for a given property, it may be that multiple
+  <a class="tref internalDFN" title="term" href="#dfn-term">terms</a> are defined with the same <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>, but differ in <code>@type</code>, <code>@container</code>
+  or <code>@language</code>. The purpose of this algorithm is to take a <a class="tref internalDFN" title="term" href="#dfn-term">term</a>
+  and a value and give it a <dfn title="term_rank" id="dfn-term_rank">term rank</dfn>. The selection can then be based, partly, on
+  the term having the highest <a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">term rank</a>.</p>
+<p>Given a <a class="tref internalDFN" title="term" href="#dfn-term">term</a> <em>term</em>, <em>value</em>, and <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>
+  determine the <a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">term rank</a> using the following steps:</p>
+<ol class="algorithm">
+  <li>If <em>value</em> is <a class="tref internalDFN" title="null" href="#dfn-null">null</a>, <a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">term rank</a> is <code>3</code>.</li>
+  <li>Otherwise, if <em>value</em> is a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> containing only the property <code>@list</code>:
+    <ol class="algorithm">
+      <li>If the <code>@list</code> property is an empty array, if <em>term</em> has <code>@container</code>
+        set to <code>@list</code>, <a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">term rank</a> is <code>1</code>, otherwise <code>0</code>.</li>
+      <li>Otherwise, return the sum of the <a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">term rank</a>s for every entry in the list.</li>
+    </ol>
+  </li>
+  <li>Otherwise, <em>value</em> <em class="rfc2119" title="must">must</em> be a <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a>, <a class="tref internalDFN" title="subject_reference" href="#dfn-subject_reference">subject reference</a>,
+    or a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> having a <code>@value</code>.
+    <ol class="algorithm">
+      <li>If <em>value</em> has a <code>@value</code> property:
+        <ol class="algorithm">
+          <li>If <em>value</em> has a <code>@type</code> property matching a
+            <code>@type</code> coercion for <em>term</em>, <a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">term rank</a>
+            is <code>3</code>, otherwise if <em>term</em> has no <code>@type</code>
+            coercion and no <code>@language</code>, <a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">term rank</a> is
+            <code>1</code>, otherwise <code>0</code>.</li>
+          <li>Otherwise, if <code>@value</code> is not a <a class="tref internalDFN" title="string" href="#dfn-string">string</a>, if <em>term</em> has
+            no <code>@type</code> or <code>@language</code> it is <code>2</code>, otherwise <code>1</code>.</li>
+          <li>Otherwise, if <em>value</em> has no <code>@language</code> property, if <em>term</em> has
+            <code>@language</code> <a class="tref internalDFN" title="null" href="#dfn-null">null</a>, or <em>term</em> has no <code>@type</code> or
+            <code>@language</code> and the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> has no <code>@language</code>,
+            <a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">term rank</a> is <code>3</code>, otherwise <code>0</code>.</li>
+          <li>Otherwise, if <em>value</em> has a <code>@language</code> property matching a
+            <code>@language</code> definition for <em>term</em> (or
+            <em>term</em> has no <code>@type</code> or <code>@language</code> definition and
+            <code>@language</code> in the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> matches the
+            <em>value</em> <code>@language</code>), <a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">term rank</a> is
+            <code>3</code>, otherwise if <em>term</em> has no <code>@type</code>
+            coercion and no <code>@language</code>, <a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">term rank</a> is
+            <code>1</code>, otherwise <code>0</code>.</li>
+        </ol>
+      </li>
+      <li>Otherwise, if <em>term</em> has <code>@type</code> coerced to <code>@id</code>,
+        <a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">term rank</a> is <code>3</code>, otherwise
+        if <em>term</em> has no <code>@type</code> coercion and no <code>@language</code>,
+        <a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">term rank</a> is <code>1</code>, otherwise <code>0</code>.</li>
+    </ol>
+  </li>
+  <li>Return <a class="tref internalDFN" title="term_rank" href="#dfn-term_rank">term rank</a>.</li>
+</ol>
+</div>
+
+</div>
+
+<div id="value-expansion" class="section">
+  <h3><span class="secno">4.5 </span>Value Expansion</h3>
+  <p>Some values in JSON-LD can be expressed in a compact form. These values
+    are required to be expanded at times when processing JSON-LD documents.</p>
+
+  <p>The algorithm for expanding a <em>value</em> takes an <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>
+    and <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>. It is implemented as follows:</p>
+  <ol class="algorithm">
+    <li>If <em>value</em> is <a class="tref internalDFN" title="null" href="#dfn-null">null</a>, the <em>value</em> is already expanded.</li>
+    <li>If <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> is <code>@graph</code> or the target of an <code>@id</code> coercion,
+      expand the value into an object with a key-value pair where the key is <code>@id</code> and the value is
+      the expanded <abbr title="Internationalized Resource Identifier">IRI</abbr> according to the <a href="#iri-expansion"><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion</a> rules.</li>
+    <li>Otherwise, if <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> is not a <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a>, then expand <em>value</em> into an
+      object:
+      <ol class="algorithm">
+        <li>Set the first key-value pair to <code>@value</code> and the unexpanded <em>value</em>.</li>
+        <li>If the <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> is the target of typed literal coercion, set the second key-value pair
+          to <code>@type</code> and the associated coercion datatype expanded according to the
+          <a href="#iri-expansion"><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion</a> rules.</li>
+        <li>Otherwise, if the <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> is the target of language tagging, set the second key-value
+          pair to <code>@language</code> and value of the language tagging from the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>.</li>
+      </ol>
+    </li>
+    <li>Otherwise, <em>value</em> is already expanded.</li>
+  </ol>
+</div>
+
+<div id="value-compaction" class="section">
+  <h3><span class="secno">4.6 </span>Value Compaction</h3>
+  <p>Some values, such as <a class="tref internalDFN" title="iri" href="#dfn-iri">IRIs</a> and <a class="tref internalDFN" title="typed_literal" href="#dfn-typed_literal">typed literals</a>, may be expressed in an
+    expanded form in JSON-LD. These values are required to be compacted at
+    times when processing JSON-LD documents.
+  </p>
+
+  <p>The algorithm for compacting an expanded value <em>value</em> takes an <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>
+    and <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>. It is implemented as follows:</p>
+  <ol class="algorithm">
+    <li>If <em>value</em> only has one property and the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> has no default language,
+      then the compacted value is the value of <code>@value</code>.</li>
+    <li>Otherwise, if <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> is <code>@graph</code>, the compacted value is the
+      value associated with the <code>@id</code> key, processed according to
+      the <a href="#iri-compaction"><abbr title="Internationalized Resource Identifier">IRI</abbr> Compaction</a> steps.</li>
+    <li>Otherwise, if the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> contains a coercion target for the
+      key that matches the expression of the value, compact the value using the
+      following steps:
+      <ol class="algorithm">
+        <li>If the coercion target is an <code>@id</code>, the compacted
+          value is the value associated with the <code>@id</code> key,
+          processed according to the
+          <a href="#iri-compaction"><abbr title="Internationalized Resource Identifier">IRI</abbr> Compaction</a> steps.</li>
+        <li>If the coercion target is a <a class="tref internalDFN" title="typed_literal" href="#dfn-typed_literal">typed literal</a>, the compacted
+          value is the value associated with the <code>@value</code> key.</li>
+      </ol>
+    </li>
+    <li>Otherwise, if <em>value</em> contains an <code>@id</code> key, the compacted value is <em>value</em> with
+      the value of <code>@id</code> processed according to the
+      <a href="#iri-compaction"><abbr title="Internationalized Resource Identifier">IRI</abbr> Compaction</a> steps.</li>
+    <li>Otherwise, if the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> contains a <code>@language</code>, which
+      matches the <code>@language</code> of the value, or the value has only a <code>@value</code> key, the compacted
+      value is the value associated with the <code>@value</code> key.</li>
+    <li>Otherwise, if the value contains a <code>@type</code> key, the compacted value
+      is <em>value</em> with the <code>@type</code> value processed according to the
+      <a href="#iri-compaction"><abbr title="Internationalized Resource Identifier">IRI</abbr> Compaction</a> steps.</li>
+    <li>Otherwise, the value is not modified.</li>
+  </ol>
+</div>
+
+<div id="expansion-1" class="section">
+<h3><span class="secno">4.7 </span>Expansion</h3>
+
+<p>Expansion is the process of taking a JSON-LD document and applying a
+  context such that all <abbr title="Internationalized Resource Identifier">IRI</abbr>, datatypes, and literal values are expanded so
+  that the context is no longer necessary. JSON-LD document expansion
+  is typically used as a part of other JSON-LD API methods.</p>
+
+<p>For example, assume the following JSON-LD input document:</p>
+
+<div class="example"><div class="example-title"><span>Example 13</span></div><pre class="example">{
+   &quot;@context&quot;:
+   {
+      &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+      &quot;homepage&quot;: {
+        &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+        &quot;@type&quot;, &quot;@id&quot;
+      }
+   },
+   &quot;name&quot;: &quot;Manu Sporny&quot;,
+   &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;
+}</pre></div>
+
+<p>Running the JSON-LD Expansion algorithm against the JSON-LD input document
+  provided above would result in the following output:</p>
+
+<div class="example"><div class="example-title"><span>Example 14</span></div><pre class="example">{
+   &quot;http://xmlns.com/foaf/0.1/name&quot;: &quot;Manu Sporny&quot;,
+   &quot;http://xmlns.com/foaf/0.1/homepage&quot;: {
+      &quot;@id&quot;: &quot;http://manu.sporny.org/&quot;
+   }
+}</pre></div>
+
+<div id="expansion-algorithm" class="section">
+<h4><span class="secno">4.7.1 </span>Expansion Algorithm</h4>
+
+<p>The algorithm takes three input variables: an <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>,  an <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>, and an <em>element</em> to be expanded. To
+  begin, the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> is set to the result of performing, <a href="#context-processing">Context Processing</a> on the passed
+  <em>context</em>, or to the <a class="tref internalDFN" title="initial_context" href="#dfn-initial_context">initial context</a> if <em>context</em>
+  is <a class="tref internalDFN" title="null" href="#dfn-null">null</a>, <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> is set to
+  <a class="tref internalDFN" title="null" href="#dfn-null">null</a>, and <em>element</em> is set to the <a class="tref internalDFN" title="json-ld_input" href="#dfn-json-ld_input">JSON-LD
+  input</a>.</p>
+<ol class="algorithm">
+  <li>If <em>element</em> is an <a class="tref internalDFN" title="array" href="#dfn-array">array</a>, process each entry in <em>element</em> recursively
+    using this algorithm, passing copies of the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> and <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>.
+    If has a <code>@container</code> set to <code>@list</code> and any entry in <em>element</em> is an
+    <a class="tref internalDFN" title="array" href="#dfn-array">array</a>, or is a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> containing a <code>@list</code> property,
+    throw an exception, as lists of lists are not allowed.
+    If the expanded entry is null, drop it. If it's an array, merge its entries with <em>element</em>'s entries.</li>
+  <li>Otherwise, if <em>element</em> is an object
+    <ol class="algorithm">
+      <li>If <em>element</em> has a <code>@context</code> property, update the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> according to
+        the steps outlined in <a href="#context-processing">Context Processing</a> and remove the <code>@context</code>
+        property.</li>
+      <li>Then, proceed and process each <em>property</em> and <em>value</em> in <em>element</em> as follows:
+        <ol class="algorithm">
+          <li>Remove <em>property</em> from <em>element</em>, expand
+            <em>property</em> according to the steps outlined in <a href="#iri-expansion"><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion</a>.
+            Set the <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> to the original un-expanded <em>property</em> if
+            <em>property</em> is not a <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a>.</li>
+          <li>If <em>property</em> does not expand to a keyword or an <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a> (i.e., it doesn't contain a colon),
+            continue with the next property from <em>element</em>.</li>
+          <li>If <em>value</em> is <a class="tref internalDFN" title="null" href="#dfn-null">null</a> and <em>property</em> is not <code>@value</code>, continue with the next
+            property from <em>element</em>.</li>
+          <li>If the <em>property</em> is <code>@id</code> the <em>value</em> <em class="rfc2119" title="must">must</em> be a <a class="tref internalDFN" title="string" href="#dfn-string">string</a>.
+            Expand the <em>value</em> according to <a href="#iri-expansion"><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion</a>.</li>
+          <li>Otherwise, if the <em>property</em> is <code>@type</code>:
+            <ol class="algorithm">
+              <li>If <em>value</em> is a <a class="tref internalDFN" title="string" href="#dfn-string">string</a>, expand according to <a href="#iri-expansion"><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion</a>.</li>
+              <li>Otherwise, if <em>value</em> is a <a class="tref internalDFN" title="subject_reference" href="#dfn-subject_reference">subject reference</a>, the expanded value
+                is the result of performing <a href="#iri-expansion"><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion</a> on the value of <code>@id</code>.</li>
+              <li>Otherwise, if <em>value</em> is a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON Object</a>, it must be empty (used for
+                <cite><a href="../json-ld-framing/#framing">Framing</a></cite>).</li>
+              <li>Otherwise, if <em>value</em> is an <a class="tref internalDFN" title="array" href="#dfn-array">array</a>, all elements must be either a
+                <a class="tref internalDFN" title="string" href="#dfn-string">string</a> or <a class="tref internalDFN" title="subject_reference" href="#dfn-subject_reference">subject reference</a>. Expand <em>value</em> for each
+                of its entries using the previous three steps.</li>
+            </ol>
+          </li>
+          <li>Otherwise, if the <em>property</em> is <code>@value</code> or <code>@language</code> the <em>value</em> <em class="rfc2119" title="must not">must not</em> be a
+            <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> or an <a class="tref internalDFN" title="array" href="#dfn-array">array</a>.</li>
+          <li>Otherwise, if the <em>property</em> is <code>@list</code> or <code>@set</code> expand <em>value</em>
+            recursively using this algorithm, passing copies of the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> and <em>active property</em>. If the expanded
+            <em>value</em> is not an <a class="tref internalDFN" title="array" href="#dfn-array">array</a>, convert it to an <a class="tref internalDFN" title="array" href="#dfn-array">array</a>.
+            If <em>property</em> is <code>@list</code> and any entry in <em>value</em> is a
+            <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> containing an <code>@list</code> property, throw an exception, as
+            lists of lists are not supported.</li>
+          <li>Otherwise, expand <em>value</em> recursively using this algorithm, passing copies of the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> and
+            <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>.</li>
+          <li>If <em>property</em> is not a keyword
+            and <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> has a <code>@container</code> <code>@list</code>
+            and the expanded <em>value</em> is not <a class="tref internalDFN" title="null" href="#dfn-null">null</a>,
+            convert <em>value</em> to an <a class="tref internalDFN" title="object" href="#dfn-object">object</a> with an <code>@list</code> property whose value is
+            set to <em>value</em> (unless <em>value</em> is already in that form).</li>
+          <li>Convert <em>value</em> to <a class="tref internalDFN" title="array" href="#dfn-array">array</a> form unless <em>value</em> is <a class="tref internalDFN" title="null" href="#dfn-null">null</a> or <em>property</em> is
+            <code>@id</code>, <code>@type</code>, <code>@value</code>, or <code>@language</code>.</li>
+          <li>If <em>value</em> is not <a class="tref internalDFN" title="null" href="#dfn-null">null</a>, either merge <em>value</em> into an existing <em>property</em> property of
+            <em>element</em> or create a new <em>property</em> property with <em>value</em> as value.</li>
+        </ol>
+      </li>
+      <li>If the processed <em>element</em> has an <code>@value</code> property
+        <ol class="algorithm">
+          <li><em>element</em> <em class="rfc2119" title="must not">must not</em> have more than one other property, which can either be <code>@language</code> or <code>@type</code>
+            with a <a class="tref internalDFN" title="string" href="#dfn-string">string</a> value.</li>
+          <li>if the value of <code>@value</code> equals <a class="tref internalDFN" title="null" href="#dfn-null">null</a>,
+            replace <em>element</em> with the value of <code>@value</code>.</li>
+        </ol>
+      </li>
+      <li>Otherwise, if <em>element</em> has an <code>@type</code> property and its value is not in the form of an
+        <a class="tref internalDFN" title="array" href="#dfn-array">array</a>, convert it to an <a class="tref internalDFN" title="array" href="#dfn-array">array</a>.</li>
+      <li>If <em>element</em> has an <code>@set</code> or <code>@list</code> property, it <em class="rfc2119" title="must">must</em> be the only property.
+        Set <em>element</em> to the value of <code>@set</code>; leave <code>@list</code> untouched.</li>
+      <li>If <em>element</em> has just a <code>@language</code> property, set <em>element</em> to <a class="tref internalDFN" title="null" href="#dfn-null">null</a>.</li>
+    </ol>
+  </li>
+  <li>Otherwise, expand <em>element</em> according to the <a href="#value-expansion">Value Expansion</a> rules,
+    passing copies of the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> and <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>.</li>
+</ol>
+
+<p>If, after the algorithm outlined above is run, the resulting <em>element</em> is an <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> with just a <code>@graph</code>
+  property, <em>element</em> is set to the value of <code>@graph</code>'s value. Finally, if <em>element</em> is a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a>,
+  it is wrapped into an <a class="tref internalDFN" title="array" href="#dfn-array">array</a>.</p>
+
+</div>
+
+</div>
+
+<div id="compaction-1" class="section">
+<h3><span class="secno">4.8 </span>Compaction</h3>
+
+<p>Compaction is the process of taking a JSON-LD document and applying a
+  context such that the most compact form of the document is generated. JSON
+  is typically expressed in a very compact, key-value format. That is, full
+  IRIs are rarely used as keys. At times, a JSON-LD document may be received
+  that is not in its most compact form. JSON-LD, via the API, provides a way
+  to compact a JSON-LD document.</p>
+
+<p>For example, assume the following JSON-LD input document:</p>
+
+<div class="example"><div class="example-title"><span>Example 15</span></div><pre class="example">{
+  &quot;http://xmlns.com/foaf/0.1/name&quot;: &quot;Manu Sporny&quot;,
+  &quot;http://xmlns.com/foaf/0.1/homepage&quot;: {
+    &quot;@id&quot;: &quot;http://manu.sporny.org/&quot;
+  }
+}</pre></div>
+
+<p>Additionally, assume the following developer-supplied JSON-LD context:</p>
+
+<div class="example"><div class="example-title"><span>Example 16</span></div><pre class="example">{
+  &quot;@context&quot;: {
+    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+    &quot;homepage&quot;: {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    }
+  }
+}</pre></div>
+
+<p>Running the JSON-LD Compaction algorithm given the context supplied above
+  against the JSON-LD input document provided above would result in the following
+  output:</p>
+
+<div class="example"><div class="example-title"><span>Example 17</span></div><pre class="example">{
+  &quot;@context&quot;: {
+    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+    &quot;homepage&quot;: {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    }
+  },
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;
+}</pre></div>
+
+<p>The compaction algorithm also enables the developer to map any expanded
+  format into an application-specific compacted format. While the context
+  provided above mapped <code>http://xmlns.com/foaf/0.1/name</code> to
+  <strong>name</strong>, it could have also mapped it to any arbitrary string
+  provided by the developer.</p>
+
+<div id="compaction-algorithm" class="section">
+<h4><span class="secno">4.8.1 </span>Compaction Algorithm</h4>
+
+<p>The algorithm takes three input variables: an <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>, an <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>,
+  and an <em>element</em> to be compacted. To begin, the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> is
+  set to the result of performing <a href="#context-processing">Context Processing</a> on the passed <em>context</em>,
+  <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> is set to <a class="tref internalDFN" title="null" href="#dfn-null">null</a>, and <em>element</em> is set to the result of performing the
+  <a href="#expansion-algorithm">Expansion Algorithm</a> on the <a class="tref internalDFN" title="json-ld_input" href="#dfn-json-ld_input">JSON-LD input</a>. This removes any existing
+  context to allow the given <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> to be cleanly applied.</p>
+
+<ol class="algorithm">
+  <li>If <em>element</em> is an <a class="tref internalDFN" title="array" href="#dfn-array">array</a>, process each entry in <em>element</em> recursively
+    using this algorithm, passing a copy of the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> and the <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>.
+    If <em>element</em> has a single item, the compacted value is that item; otherwise the compacted value
+    is <em>element</em>.</li>
+  <li>Otherwise, if <em>element</em> is an object:
+    <ol class="algorithm">
+      <li>If <em>element</em> has an <code>@value</code> property or element is a <a class="tref internalDFN" title="subject_reference" href="#dfn-subject_reference">subject reference</a>,
+        return the result of performing
+        <a href="#value-compaction">Value Compaction</a> on <em>element</em> using <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>.</li>
+      <li>Otherwise, if the <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> has a <code>@container</code> mapping to <code>@list</code>
+        and <em>element</em> has a corresponding <code>@list</code> property, recursively compact that
+        property's value passing a copy of the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> and the <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> ensuring
+        that the result is an array and removing <a class="tref internalDFN" title="null" href="#dfn-null">null</a> values. Return either the
+        result as an array, as an object with a key of <code>@list</code> (or appropriate alias from
+        <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>).</li>
+      <li>Otherwise, construct <em>output</em> as a new <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> used for returning the result
+        of compacting <em>element</em>. For each <em>property</em> and <em>value</em> in <em>element:</em>
+        <ol class="algorithm">
+          <li>If <em>property</em> is <code>@id</code> or <code>@type</code>
+            <ol class="algorithm">
+              <li>Set <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> to the result of performing
+                <a href="#iri-compaction"><abbr title="Internationalized Resource Identifier">IRI</abbr> Compaction</a> on <em>property</em>.</li>
+              <li>If <em>value</em> is a <a class="tref internalDFN" title="string" href="#dfn-string">string</a>, the compacted <em>value</em> is the result of performing
+                <a href="#iri-compaction"><abbr title="Internationalized Resource Identifier">IRI</abbr> Compaction</a> on <em>value</em>.</li>
+              <li>Otherwise, <em>value</em> <em class="rfc2119" title="must">must</em> be an <a class="tref internalDFN" title="array" href="#dfn-array">array</a>. Perform <a href="#iri-compaction"><abbr title="Internationalized Resource Identifier">IRI</abbr> Compaction</a>
+                on every entry of <em>value</em>. If <em>value</em> contains just one entry, <em>value</em> is set to that entry.</li>
+              <li>Add <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> and the expanded <em>value</em> to <em>output</em>.</li>
+            </ol>
+          </li>
+          <li>Otherwise, <em>value</em> <em class="rfc2119" title="must">must</em> be an <a class="tref internalDFN" title="array" href="#dfn-array">array</a>.</li>
+          <li>If <em>value</em> is empty:
+            <ol class="algorithm">
+              <li>Set <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> to the result of performing
+                <a href="#iri-compaction"><abbr title="Internationalized Resource Identifier">IRI</abbr> Compaction</a> on <em>property</em>.</li>
+              <li>Create an entry in <em>output</em> for <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> and <em>value</em>.</li>
+            </ol>
+          </li>
+          <li>For each <em>item</em> in <em>value</em>:
+            <ol class="algorithm">
+              <li>Set <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> to the result of performing <a href="#iri-compaction"><abbr title="Internationalized Resource Identifier">IRI</abbr> Compaction</a>
+                for <em>property</em> and <em>item</em> using the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>.</li>
+              <li>Compact <em>item</em> by recursively performing this algorithm passing a copy of
+                the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> and the <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>.</li>
+              <li>If an entry already exists in <em>output</em> for <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>, convert it
+                to an <a class="tref internalDFN" title="array" href="#dfn-array">array</a> if necessary, and append the compacted <em>value</em>.</li>
+              <li>Otherwise, if the compacted <em>value</em> is not an <a class="tref internalDFN" title="array" href="#dfn-array">array</a> and <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>
+                has a <code>@container</code> mapping to <code>@set</code>,
+                create an entry in <em>output</em> for <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> and <em>value</em> as an
+                <a class="tref internalDFN" title="array" href="#dfn-array">array</a>.</li>
+              <li>Otherwise, create an entry in <em>output</em> for <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> and <em>value</em>.</li>
+            </ol>
+          </li>
+        </ol>
+      </li>
+    </ol>
+  </li>
+  <li>Otherwise, return <em>element</em> as the compacted <em>element</em>.
+    <div class="issue"><div class="issue-title"><span>Issue 7</span></div><div class="">Perhaps this should also call <a href="#value-compaction">Value Compaction</a> on
+      native types and strings, which could consolidate potential transformation in one place.</div></div>
+  </li>
+</ol>
+
+<p>If, after the algorithm outlined above is run, the resulting <em>element</em> is an <a class="tref internalDFN" title="array" href="#dfn-array">array</a>, put <em>element</em> into the
+  <code>@graph</code> property of a new <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> and then set <em>element</em> to that <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a>.
+  Finally, add a <code>@context</code> property to <em>element</em> and set it to the initially passed <em>context</em>.</p>
+
+</div>
+
+</div>
+
+<div id="rdf-conversion" class="section">
+<h3><span class="secno">4.9 </span>RDF Conversion</h3>
+
+<p>A JSON-LD document <em class="rfc2119" title="may">may</em> be converted between other RDF-compatible document
+  formats using the algorithms specified in this section.</p>
+
+<p>The JSON-LD Processing Model describes processing rules for extracting RDF
+  from a JSON-LD document, and for transforming an array of <a href="#idl-def-Quad" class="idlType"><code>Quad</code></a> retrieved by processing
+  another serialization format into JSON-LD. Note that many uses of JSON-LD may not require
+  generation of RDF.</p>
+
+<p>The processing algorithms described in this section are provided in
+  order to demonstrate how one might implement a JSON-LD to RDF processor.
+  Conformant implementations are only required to produce the same type and
+  number of quads during the output process and are not required to
+  implement the algorithm exactly as described.</p>
+
+<div class="informative section" id="overview">
+  <h4><span class="secno">4.9.1 </span>Overview</h4><p><em>This section is non-normative.</em></p>
+  <p>
+    JSON-LD is intended to have an easy to parse grammar that closely models existing
+    practice in using JSON for describing object representations. This allows the use
+    of existing libraries for parsing JSON.
+  </p>
+  <p>
+    As with other grammars used for describing <a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">Linked Data</a>, a key
+    concept is that of a <a class="tref internalDFN" title="node" href="#dfn-node">node</a> in a <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a>.
+    Nodes may be of three basic types.
+    The first is the <a class="datatype idlType" title="IRI" href="#idl-def-IRI"><code><abbr title="Internationalized Resource Identifier">IRI</abbr></code></a>, which is used to refer to
+    <a class="tref internalDFN" title="node" href="#dfn-node">node</a>s in other <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a>s.
+    The second is the
+    <a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">blank node</a>, which are nodes for which an external name does not
+    exist, or is not known. The third is a <a class="tref internalDFN" title="literal" href="#dfn-literal">Literal</a>, which express
+    values such as strings, dates and other information having a lexical
+    form, possibly including an explicit language or datatype.
+  </p>
+  <p>Data described with JSON-LD may be considered to be a graph made
+    up of <a class="tref internalDFN" title="subject" href="#dfn-subject">subject</a> and <a class="tref internalDFN" title="object" href="#dfn-object">object</a>
+    <a class="tref internalDFN" title="node" href="#dfn-node">nodes</a> related via a <a class="tref internalDFN" title="property" href="#dfn-property">property</a>
+    <a class="tref internalDFN" title="node" href="#dfn-node">node</a>. Specific implementations may also choose to operate
+    on the document as a normal JSON description of objects having
+    attributes. Both approaches are valid ways to interact with JSON-LD
+    documents.</p>
+</div>
+
+<div class="informative section" id="parsing-examples">
+  <h4><span class="secno">4.9.2 </span>Parsing Examples</h4><p><em>This section is non-normative.</em></p>
+
+  <p>The following examples show simple transformations of JSON-LD documents to Turtle [<cite><a class="bibref" rel="biblioentry" href="#bib-TURTLE-TR">TURTLE-TR</a></cite>].</p>
+
+  <p>The first example uses a simple document containing a simple FOAF profile:</p>
+
+<div class="example"><div class="example-title"><span>Example 18</span></div><pre class="example">{
+  &quot;@context&quot;: {&quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;},
+  &quot;@id&quot;: &quot;http://greggkellogg.net/foaf#me&quot;,
+  &quot;@type&quot;: &quot;foaf:Person&quot;,
+  &quot;foaf:name&quot;: &quot;Gregg Kellogg&quot;,
+  &quot;foaf:knows&quot;: {
+    &quot;@type&quot;: &quot;foaf:Person&quot;,
+    &quot;foaf:name&quot;: &quot;Manu Sporny&quot;
+  }
+}</pre></div>
+
+  <p>This translates fairly directly to a similar Turtle document:</p>
+
+<div class="example"><div class="example-title"><span>Example 19</span></div><pre class="example">@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt;.
+
+&lt;http://greggkellogg.net/foaf#me&gt; a foaf:Person;
+  foaf:name &quot;Gregg Kellogg&quot;;
+  foaf:knows [ a foaf:Person; foaf:name &quot;Manu Sporny&quot;].</pre></div>
+
+  <p>The actual parsing steps first require that the JSON-LD document be expanded,
+    to eliminate the <code>@context</code>:</p>
+
+<div class="example"><div class="example-title"><span>Example 20</span></div><pre class="example">[{
+  &quot;@id&quot;: &quot;http://greggkellogg.net/foaf#me&quot;,
+  &quot;@type&quot;: [&quot;http://xmlns.com/foaf/0.1/Person&quot;],
+  &quot;http://xmlns.com/foaf/0.1/name&quot;: [{&quot;@value&quot;: &quot;Gregg Kellogg&quot;}],
+  &quot;http://xmlns.com/foaf/0.1/knows&quot;: [{
+    &quot;@type&quot;: [&quot;http://xmlns.com/foaf/0.1/Person&quot;],
+    &quot;http://xmlns.com/foaf/0.1/name&quot;: [{&quot;@value&quot;: &quot;Manu Sporny&quot;}]
+  }]
+}]</pre></div>
+
+  <p>The process of translating this to RDF then operates over each
+    <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a> to find a subject,
+    each <a class="tref internalDFN" title="property" href="#dfn-property">property</a> to find an RDF <em>predicate</em>,
+    and each value of that property to find an <a class="tref internalDFN" title="object" href="#dfn-object">object</a>.
+    In this case, each property has just a single object:
+    <code>foaf:name</code> identifies a <a class="tref internalDFN" title="literal" href="#dfn-literal">literal</a>, and
+    <code>foaf:knows</code> identifies a second <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a>
+    similar to Turtle's <code>blankNodePropertyList</code>.</p>
+
+  <p>After expansion, JSON-LD <a class="tref internalDFN" title="number" href="#dfn-number">numbers</a>,
+    <a class="tref internalDFN" title="true" href="#dfn-true">booleans</a>, typed- and language-tagged-<a class="tref internalDFN" title="literal" href="#dfn-literal">literals</a>, and <a class="tref internalDFN" title="iri" href="#dfn-iri">IRIs</a>
+    become explicit, and can be directly transformed into their RDF representations.</p>
+
+<div class="example"><div class="example-title"><span>Example 21</span></div><pre class="example">[{
+  &quot;@id&quot;: &quot;http://greggkellogg.net/foaf#me&quot;,
+  &quot;@type&quot;: [&quot;http://xmlns.com/foaf/0.1/Person&quot;],
+  &quot;http://xmlns.com/foaf/0.1/name&quot;: [{&quot;@value&quot;: &quot;Gregg Kellogg&quot;}],
+  <span class="diff">&quot;http://xmlns.com/foaf/0.1/currentProject&quot;: [{&quot;@id&quot;: &quot;http://json-ld.org/&quot;}],
+  &quot;http://xmlns.com/foaf/0.1/birthday&quot;: [{
+    &quot;@value&quot;: &quot;1957-02-27&quot;,
+    &quot;@type&quot;: &quot;http://www.w3.org/2001/XMLSchema#date&quot;
+  }],</span>
+  &quot;http://xmlns.com/foaf/0.1/knows&quot;: [{
+    &quot;@type&quot;: [&quot;http://xmlns.com/foaf/0.1/Person&quot;],
+    &quot;http://xmlns.com/foaf/0.1/name&quot;: [{&quot;@value&quot;: &quot;Manu Sporny&quot;}]
+  }]
+}]</pre></div>
+
+  <p>Translates to:</p>
+
+<div class="example"><div class="example-title"><span>Example 22</span></div><pre class="example">@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt;.
+@prefix xsd: &lt;http://www.w3.org/2001/XMLSchema#&gt;.
+
+&lt;http://greggkellogg.net/foaf#me&gt; a foaf:Person;
+  foaf:name &quot;Gregg Kellogg&quot;;
+  <span class="diff">foaf:currentProject &lt;http://json-ld.org/&gt;;
+  foaf:birthday &quot;1957-02-27&quot;^^xsd:date;</span>
+  foaf:knows [ a foaf:Person; foaf:name &quot;Manu Sporny&quot;].</pre></div>
+
+</div>
+
+<div id="convert-to-rdf-algorithm" class="section">
+  <h4><span class="secno">4.9.3 </span>Convert to RDF Algorithm</h4>
+  <p>
+    The algorithm below is designed for in-memory implementations with random access to <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> elements.
+  </p>
+  <p>
+    A conforming JSON-LD processor implementing RDF conversion <em class="rfc2119" title="must">must</em> implement a
+    processing algorithm that results in the same set of RDF <a class="tref internalDFN" title="quad" href="#dfn-quad">Quads</a> that the following
+    algorithm generates:
+  </p>
+
+  <p>The algorithm takes five input variables: a <em>element</em> to be converted, an
+    <a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">active subject</a>, <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> and <a class="tref internalDFN" title="graph_name" href="#dfn-graph_name">graph name</a>.
+    To begin, the <a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">active subject</a>, <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> and <a class="tref internalDFN" title="graph_name" href="#dfn-graph_name">graph name</a>
+    are set to <a class="tref internalDFN" title="null" href="#dfn-null">null</a>, and <em>element</em> is
+    set to the result of performing the <a href="#expansion-algorithm">Expansion Algorithm</a> on
+    the <a class="tref internalDFN" title="json-ld_input" href="#dfn-json-ld_input">JSON-LD input</a>. This removes any existing context to allow the given context to be cleanly
+    applied.</p>
+
+  <ol class="algorithm">
+    <li id="processing-step-associative">
+      If <em>element</em> is a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a>, perform the following steps:
+      <ol class="algorithm">
+        <li>Set <a class="tref internalDFN" title="active_object" href="#dfn-active_object">active object</a> to <a class="tref internalDFN" title="null" href="#dfn-null">null</a>.</li>
+        <li>
+          If <em>element</em> has a <code>@value</code> property:
+          <ol class="algorithm">
+            <li>If the value of <code>@value</code> is a <a class="tref internalDFN" title="number" href="#dfn-number">number</a>, set the
+              <a class="tref internalDFN" title="active_object" href="#dfn-active_object">active object</a> to a <a class="tref internalDFN" title="typed_literal" href="#dfn-typed_literal">typed literal</a> using a string representation
+              of the value as defined in the section <a href="#data-round-tripping">Data Round Tripping</a>.
+              Set datatype to the value of the <code>@type</code> property if it exists, otherwise
+              either <code>xsd:integer</code> or <code>xsd:double</code>, depending
+              on if the value contains a fractional and/or an exponential component.</li>
+            <li>Otherwise, if the value of <code>@value</code> is <strong>true</strong> or <strong>false</strong>,
+              set the <a class="tref internalDFN" title="active_object" href="#dfn-active_object">active object</a> to a <a class="tref internalDFN" title="typed_literal" href="#dfn-typed_literal">typed literal</a> created from the
+              string representation of the value. Set datatype to the value of the <code>@type</code>
+              property if it exists, otherwise <code>xsd:boolean</code>.</li>
+            <li>
+              Otherwise, if <em>element</em> contains a <code>@type</code> property, set the
+              <a class="tref internalDFN" title="active_object" href="#dfn-active_object">active object</a> to a <a class="tref internalDFN" title="typed_literal" href="#dfn-typed_literal">typed literal</a>.
+            </li>
+            <li>
+              Otherwise, if <em>element</em> contains a <code>@language</code> property, set the
+              <a class="tref internalDFN" title="active_object" href="#dfn-active_object">active object</a> to a <a class="tref internalDFN" title="language-tagged_literal" href="#dfn-language-tagged_literal">language-tagged literal</a>.
+            </li>
+            <li>
+              Otherwise, set the <a class="tref internalDFN" title="active_object" href="#dfn-active_object">active object</a> to a <a class="tref internalDFN" title="typed_literal" href="#dfn-typed_literal">typed literal</a>
+              using <code>xsd:string</code> as the datatype.
+            </li>
+          </ol>
+        </li>
+        <li>
+          If <em>element</em> has a <code>@list</code> property the value <em class="rfc2119" title="must">must</em> be an <a class="tref internalDFN" title="array" href="#dfn-array">array</a>.
+          Process its value as a list as described in <a href="#list-conversion">List Conversion</a> using
+          the return value as the <a class="tref internalDFN" title="active_object" href="#dfn-active_object">active object</a>
+        </li>
+        <li>If <a class="tref internalDFN" title="active_object" href="#dfn-active_object">active object</a> is not <a class="tref internalDFN" title="null" href="#dfn-null">null</a>:
+          <ol class="algorithm">
+            <li>If neither <a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">active subject</a> nor <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> are <a class="tref internalDFN" title="null" href="#dfn-null">null</a>,
+              generate a <a href="#idl-def-Quad" class="idlType"><code>Quad</code></a>
+              representing <a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">active subject</a>, <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>,
+              <a class="tref internalDFN" title="active_object" href="#dfn-active_object">active object</a>, and <a class="tref internalDFN" title="graph_name" href="#dfn-graph_name">graph name</a>.</li>
+            <li>Return <a class="tref internalDFN" title="active_object" href="#dfn-active_object">active object</a>.</li>
+          </ol>
+        </li>
+        <li id="processing-step-subject">If <em>element</em> has a <code>@id</code> property,
+          the value <em class="rfc2119" title="must">must</em> be a <a class="tref internalDFN" title="string" href="#dfn-string">string</a>, set the <a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">active subject</a> to the previously
+          expanded value (either a <a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">blank node</a> or an <a class="datatype idlType" title="IRI" href="#idl-def-IRI"><code><abbr title="Internationalized Resource Identifier">IRI</abbr></code></a>).</li>
+        <li>
+          Otherwise, if <em>element</em> does not have a <code>@id</code> property, set the <a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">active
+          subject</a> to newly generated <a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">blank node</a>.</li>
+        <li>
+          Process each <em>property</em> and <em>value</em> in <em>element</em>, ordered by
+          <em>property</em>, as follows:
+          <ol class="algorithm">
+            <li>
+              If <em>property</em> is <code>@type</code>, set the <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>
+              to <code>rdf:type</code>.
+            </li>
+            <li>Otherwise, if <em>property</em> is <code>@graph</code>,
+              process <em>value</em> algorithm recursively, using <a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">active subject</a> as <a class="tref internalDFN" title="graph_name" href="#dfn-graph_name">graph name</a>
+              and null values for <a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">active subject</a> and <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> and then
+              proceed to next property.</li>
+            <li>Otherwise, if <em>property</em> is a <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a>, skip this step.</li>
+            <li>Otherwise, set <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> to the <abbr title="Internationalized Resource Identifier">IRI</abbr> value of <em>property</em>.</li>
+            <li>Process <em>value</em> recursively using this algorithm, passing copies of
+              <a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">active subject</a>, <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> and <a class="tref internalDFN" title="graph_name" href="#dfn-graph_name">graph name</a>.
+            </li>
+          </ol>
+        </li>
+        <li>
+          Set <a class="tref internalDFN" title="active_object" href="#dfn-active_object">active object</a> to <a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">active subject</a>.
+        </li>
+      </ol>
+    </li>
+
+    <li>Otherwise, if <em>element</em> is an <a class="tref internalDFN" title="array" href="#dfn-array">array</a>, process each value in the <a class="tref internalDFN" title="array" href="#dfn-array">array</a>
+      as follows, process <em>element</em> recursively using this algorithm, using copies of
+      <a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">active subject</a>, <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>, and <a class="tref internalDFN" title="graph_name" href="#dfn-graph_name">graph name</a>.</li>
+
+    <li>Otherwise, if <em>element</em> is a <a class="tref internalDFN" title="string" href="#dfn-string">string</a>, then the <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>
+      must be <code>rdf:type</code> so set the <a class="tref internalDFN" title="active_object" href="#dfn-active_object">active object</a> to an <a class="datatype idlType" title="IRI" href="#idl-def-IRI"><code><abbr title="Internationalized Resource Identifier">IRI</abbr></code></a>.</li>
+
+    <li>If any of these steps created an <a class="tref internalDFN" title="active_object" href="#dfn-active_object">active object</a> and neither <a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">active subject</a>
+      nor <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a> are <a class="tref internalDFN" title="null" href="#dfn-null">null</a>, generate a <a href="#idl-def-Quad" class="idlType"><code>Quad</code></a> using
+      <a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">active subject</a>,<a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>, <a class="tref internalDFN" title="active_object" href="#dfn-active_object">active object</a> and
+      <a class="tref internalDFN" title="graph_name" href="#dfn-graph_name">graph name</a>.
+    </li>
+    <li>Return <a class="tref internalDFN" title="active_object" href="#dfn-active_object">active object</a>.</li>
+  </ol>
+</div>
+<div id="list-conversion" class="section">
+  <h4><span class="secno">4.9.4 </span>List Conversion</h4>
+
+  <p>List Conversion is the process of taking an <a class="tref internalDFN" title="array" href="#dfn-array">array</a> of values and adding them to a newly
+    created <cite><a href="http://www.w3.org/TR/rdf-schema/#ch_collectionvocab">RDF Collection</a></cite> (see
+    [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SCHEMA">RDF-SCHEMA</a></cite>]) by linking each element of the list using <code>rdf:first</code> and <code>rdf:next</code>,
+    terminating the list with <code>rdf:nil</code> using the following sequence:</p>
+  <p>The algorithm is invoked with an <a class="tref internalDFN" title="array" href="#dfn-array">array</a> <em>array</em>, the <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>
+    and returns a value to be used as an <a class="tref internalDFN" title="active_object" href="#dfn-active_object">active object</a> in the calling location.</p>
+  <div class="note"><div class="note-title"><span>Note</span></div><div class="">This algorithm does not support lists containing lists.</div></div>
+  <ol class="algorithm">
+    <li>
+      If <em>array</em> is empty return <code>rdf:nil</code>.
+    </li>
+    <li>
+      Otherwise, generate a <a href="#idl-def-Quad" class="idlType"><code>Quad</code></a> using using the <a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">active subject</a>, <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>
+      and a newly generated <a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">blank node</a> identified as <em>first <a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">blank node</a></em>.
+    </li>
+    <li>
+      For each element in <em>array</em> other than the last element:
+      <ol class="algorithm">
+        <li>Create a processor state using
+          <em>first blank node</em> as the <a class="tref internalDFN" title="active_subject" href="#dfn-active_subject">active subject</a>, and
+          <code>rdf:first</code> as the <a class="tref internalDFN" title="active_property" href="#dfn-active_property">active property</a>.
+          <ol class="algorithm">
+            <li>Process the value starting at <a href="#processing-step-associative">Step 1</a>.</li>
+            <li>Proceed using the previous <a class="tref internalDFN" title="processor_state" href="#dfn-processor_state">processor state</a>.</li>
+          </ol>
+        </li>
+        <li>Unless this is the last element in <em>array</em>, generate a new <a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">blank node</a> identified as
+          <em>rest blank node</em>, otherwise use <code>rdf:nil</code>.</li>
+        <li>Generate a new <a href="#idl-def-Quad" class="idlType"><code>Quad</code></a> using <em>first blank node</em>,
+          <code>rdf:rest</code> and <em>rest blank node</em>.</li>
+        <li>Set <em>first blank node</em> to
+          <em>rest blank node</em>.</li>
+        <li>Return <em>first blank node</em>.</li>
+      </ol>
+    </li>
+  </ol>
+</div>
+
+<div id="convert-from-rdf-algorithm" class="section">
+  <h4><span class="secno">4.9.5 </span>Convert from RDF Algorithm</h4>
+  <p>In some cases, data exists natively in Triples or Quads form; for example, if the data was originally
+    represented in an RDF graph or triple/quad store. This algorithm is designed to simply translate
+    an array of <a class="datatype idlType" title="quad" href="#idl-def-quad"><code>Quads</code></a> into a JSON-LD document.</p>
+  <p>When expanding <a class="tref internalDFN" title="typed_literal" href="#dfn-typed_literal">typed literal</a> values having a datatype of <code>xsd:string</code>,
+    the <code>@type</code> <em class="rfc2119" title="must not">must not</em> be set to <code>xsd:string</code> and the resulting value
+    <em class="rfc2119" title="must">must</em> have only a <code>@value</code> property.</p>
+  <p>The conversion algorithm takes a single parameter <em>input</em> in the form of an
+    array of <a href="#idl-def-Quad" class="idlType"><code>Quad</code></a> representations.</p>
+  <ol class="algorithm">
+    <li id="new_graph">Construct <em>defaultGraph</em> as a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a>
+      containing <em>subjects</em> and <em>listMap</em>, each an empty <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a>.</li>
+    <li>Construct <em>graphs</em> as a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> containing <em>defaultGraph</em>
+      identified by
+      an empty <a class="tref internalDFN" title="string" href="#dfn-string">string</a>.</li>
+    <li>For each quad in <em>input</em>:
+      <ol class="algorithm">
+        <li>Set <em>graph</em> to the entry in <em>graphs</em> identified
+          by <em>name</em>, initializing it to a new entry using the mechanism
+          described in <a href="#new_graph">Step 1</a>.</li>
+        <li>If <em>property</em> is <code>rdf:first</code>,
+          use the entry in <em>graph.listMap</em> indexed by <em>subject</em>,
+          initializing it to a new <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> if nesessary. Represent
+          <em>object</em> in expanded form, as described in
+          <a href="#value-expansion">Value Expansion</a>. Add the
+          resulting <em>object representation</em> to the entry indexed by
+          <em>first</em>, and skip to the next quad.</li>
+        <li>If <em>property</em> is <code>rdf:rest</code>:
+          <ol class="algorithm">
+            <li>If <em>object</em> is a <a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">blank node</a>, use the entry in
+              <em>graph.listMap</em> indexed by <em>subject</em>, initializing it
+              to a new <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> if necessary. Add the <em>nominalValue</em> of
+              <em>object</em> to the entry indexed by <em>rest</em>.
+            </li>
+            <li>Skip to the next quad.</li>
+          </ol>
+        </li>
+        <li>If <em>name</em> is not <a class="tref internalDFN" title="null" href="#dfn-null">null</a>, and <em>defaultGraph.subjects</em>
+          does not contain an entry for <em>name</em>,
+          create a new entry for <em>name</em> from a new
+          <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> with key/value pair of <code>@id</code> and
+          a string representation of <em>name</em>.</li>
+        <li>Set <em>value</em> as the entry from <em>graph.subjects</em> for
+          <em>subject</em>, initializing it to a new
+          <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> with key/value pair of <code>@id</code> and
+          a string representation of <em>subject</em> if necessary.</li>
+        <li>If <em>property</em> is <code>rdf:type</code> and the <em>notType</em>
+          option is present and not <a class="tref internalDFN" title="true" href="#dfn-true">true</a>:
+          <ol class="algorithm">
+            <li>Append the string representation of <em>object</em> to the array value for the
+              key <code>@type</code>, creating an entry in <em>value</em> if necessary.</li>
+          </ol>
+        </li>
+        <li>Otherwise, if <em>object</em> is <code>rdf:nil</code>:
+          <ol class="algorithm">
+            <li>Let <em>key</em> be the string representation of <em>property</em>.</li>
+            <li>Append an empty <code>@list</code> representation to the array value for
+              <em>key</em>, creating an entry in <em>value</em> if necessary.</li>
+          </ol>
+        </li>
+        <li>Otherwise,
+          <ol class="algorithm">
+            <li>Let <em>key</em> be the string representation of <em>property</em> and let
+              <em>object representation</em>
+              be <em>object</em> represented in expanded form as described in
+              <a href="#value-expansion">Value Expansion</a>.</li>
+            <li>If <em>object</em> is a <a class="tref internalDFN" title="blank_node" href="#dfn-blank_node">blank node</a>,
+              use the entry in <em>graph.listMap</em> indexed by <em>object</em>,
+              initializing it to a new <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> if nesessary.
+              Add an entry for <em>head</em> with <em>object representation</em>.</li>
+            <li>Append <em>object representation</em> to the array value for
+              <em>key</em>, creating an entry in <em>value</em> if necessary.</li>
+          </ol>
+        </li>
+      </ol>
+    </li>
+    <li>For each <em>name</em> and <em>graph</em> in <em>graphs</em>:
+      <ol class="algorithm">
+        <li>For each <em>subject</em> and <em>entry</em> in <em>graph</em>
+          where <em>entry</em> has both <em>head</em> and <em>first</em> keys:
+          <ol class="algorithm">
+            <li>Set <em>value</em> to the value of <em>head</em> in <em>entry</em>.</li>
+            <li>Remove the entry for <code>@id</code> in <em>value</em>.</li>
+            <li>Add an entry to <em>value</em> for <code>@list</code> initialized to a new array
+              containing the value of <em>first</em> from <em>entry</em>.</li>
+            <li>While <em>entry</em> has a key for <em>rest</em>:
+              <ol class="algorithm">
+                <li>Set <em>entry</em> to the value of <em>graph.listMap</em> for <em>entry.rest</em>.</li>
+                <li>Add the value for <em>entry.first</em> to the list array.</li>
+              </ol>
+            </li>
+          </ol>
+        </li>
+      </ol>
+    </li>
+    <li>Create <em>array</em> as an empty <a class="tref internalDFN" title="array" href="#dfn-array">array</a>.</li>
+    <li>For each <em>subject</em> and <em>entry</em> in <em>defaultGraph.subjects</em>
+      ordered by <em>subject</em>:
+      <ol class="algorithm">
+        <li>Add <em>entry</em> to <em>array</em>.</li>
+        <li>If <em>graphs</em> has an entry for <em>subject</em>, add a property
+          <code>@graph</code> in <em>entry</em> containing the ordered entries
+          from <em>graphs[subject].subjects</em>.</li>
+      </ol>
+    </li>
+    <li>Return <em>array</em> as the result.</li>
+  </ol>
+</div>
+</div>
+
+</div>
+
+<div id="data-round-tripping" class="section">
+
+<!-- OddPage -->
+<h2><span class="secno">5. </span>Data Round Tripping</h2>
+
+<p>When coercing numbers to <strong>xsd:integer</strong> or <strong>xsd:double</strong>
+  as it, e.g., happens during <a href="#rdf-conversion">RDF Conversion</a>, implementers <em class="rfc2119" title="must">must</em>
+  ensure that the result is a canonical lexical form in the form of a
+  <a class="tref internalDFN" title="string" href="#dfn-string">string</a>. A <dfn title="canonical_lexical_form" id="dfn-canonical_lexical_form">canonical lexical form</dfn> is a set of literals
+  from among the valid set of literals for a datatype such that there is a one-to-one mapping
+  between the canonical lexical form and a value in the value space as defined in
+  [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>]]. In other words, every value <em class="rfc2119" title="must">must</em> be converted to a deterministic string
+  representation.</p>
+<p>The canonical lexical form of an <em>integer</em>, i.e., a number without fractions
+  or a number coerced to <strong>xsd:integer</strong>, is a finite-length sequence of decimal
+  digits (<code>0-9</code>) with an optional leading minus sign; leading zeroes are prohibited.
+  To convert the number in JavaScript, implementers can use the following snippet of code:</p>
+<div class="example"><div class="example-title"><span>Example 23</span></div><pre class="example">(value).toFixed(0).toString()</pre></div>
+<p>The canonical lexical form of a <em>double</em>, i.e., a number with fractions
+  or a number coerced to <strong>xsd:double</strong>, consists of a mantissa followed by the
+  character &quot;E&quot;, followed by an exponent. The mantissa <em class="rfc2119" title="must">must</em> be a decimal number. The exponent
+  <em class="rfc2119" title="must">must</em> be an integer. Leading zeroes and a preceding plus sign (<code>+</code>) are prohibited
+  in the exponent. If the exponent is zero, it must be indicated by <code>E0</code>.
+  For the mantissa, the preceding optional plus sign is prohibited and the decimal point is
+  required. Leading and trailing zeroes are prohibited subject to the following: number
+  representations must be normalized such that there is a single digit which is non-zero to the
+  left of the decimal point and at least a single digit to the right of the decimal point unless
+  the value being represented is zero. The canonical representation for zero is <code>0.0E0</code>.
+  To convert the number in JavaScript, implementers can use the following snippet of code:</p>
+<div class="example"><div class="example-title"><span>Example 24</span></div><pre class="example">(value).toExponential().replace(/e\+?/,'E')</pre></div>
+<p><strong>xsd:double</strong>'s value space is defined by the IEEE double-precision 64-bit
+floating point type [<cite><a class="bibref" rel="biblioentry" href="#bib-IEEE-754-1985">IEEE-754-1985</a></cite>].</p>
+
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">When data such as decimals need to be normalized, JSON-LD authors should
+not use values that are going to undergo automatic conversion. This is due to the lossy nature
+of <strong>xsd:double</strong> values. Authors should instead use the expanded object form to
+set the canonical lexical form directly.</p></div>
+
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">When JSON-native datatypes, like <a class="tref internalDFN" title="number" href="#dfn-number">number</a>s, are type coerced, lossless
+data round-tripping can not be guaranted. Consider the following code example:</p></div>
+
+<div class="example"><div class="example-title"><span>Example 25</span></div><pre class="example">var myObj1 = {
+               &quot;@context&quot;: {
+                 &quot;number&quot;: {
+                   &quot;@id&quot;: &quot;http://example.com/vocab#number&quot;,
+                   <span class="diff">&quot;@type&quot;: &quot;xsd:nonNegativeInteger&quot;</span>
+                 }
+               },
+               &quot;number&quot; : <span class="diff">42</span>
+             };
+
+// Convert the JSON-LD document to RDF; this converts 42 to a string
+var jsonldText = jsonld.toRDF(myObj1, myRdfTripleCollector);
+
+// Convert the RDF triples back to a JavaScript object
+var myObj2 = jsonld.fromRDF(myRdfTripleCollector.getTriples());</pre></div>
+
+<p>At this point, <code>myObj1</code> and <code>myObj2</code> will have different
+  values for the &quot;number&quot; property. <code>myObj1</code> will have the number
+  <code>42</code>, while <code>myObj2</code> have an object consisting of
+  <code>@value</code> set to the string <code>&quot;42&quot;</code> and <code>@type</code>
+  set to the expanded value of <em>xsd:nonNegativeInteger</em>.</p>
+
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">Some JSON serializers, such as PHP's native implementation in some versions,
+  backslash-escape the forward slash character. For example, the value
+  <code>http://example.com/</code> would be serialized as <code>http:\/\/example.com\/</code>.
+  This is problematic as other JSON parsers might not understand those escaping characters.
+  There is no need to backslash-escape forward slashes in JSON-LD. To aid interoperability
+  between JSON-LD processors, a JSON-LD serializer <em class="rfc2119" title="must not">must not</em> backslash-escape forward slashes.</p></div>
+
+</div>
+
+<div class="appendix section" id="appendix-a">
+  
+<!-- OddPage -->
+<h2><span class="secno">A. </span>Initial Context</h2>
+  <div class="issue"><div class="issue-title"><span>Issue 8</span></div><p class="">It is <a href="https://github.com/json-ld/json-ld.org/issues/80">still being
+    discussed</a> whether JSON-LD has the notion of an initial context or not. If JSON-LD has an
+    initial context, it <em class="rfc2119" title="must">must</em> be specified external to the JSON-LD Syntax specification at a
+    well-known location.</p></div>
+</div>
+
+<div class="appendix section" id="acknowledgements">
+
+<!-- OddPage -->
+<h2><span class="secno">B. </span>Acknowledgements</h2>
+
+<p>The editors would like to thank Mark Birbeck, who provided a great deal of
+the initial push behind the JSON-LD work via his work on RDFj,
+Dave Lehn and Mike Johnson who reviewed, provided feedback, and
+performed several implementations of the specification, and Ian Davis, who
+created RDF/JSON. Thanks also to Nathan Rixham, Bradley P. Allen,
+Kingsley Idehen, Glenn McDonald, Alexandre Passant, Danny Ayers, Ted
+Thibodeau Jr., Olivier Grisel, Josh Mandel, Eric Prud'hommeaux,
+David Wood, Guus Schreiber, Pat Hayes, Sandro Hawke, and Richard
+Cyganiak for their input on the specification.
+</p>
+</div>
+
+
+
+<div id="references" class="appendix section">
+<!-- OddPage -->
+<h2><span class="secno">C. </span>References</h2><div id="normative-references" class="section"><h3><span class="secno">C.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-BCP47">[BCP47]</dt><dd>A. Phillips; M. Davis. <a href="http://tools.ietf.org/html/bcp47"><cite>Tags for Identifying Languages</cite></a> September 2009. IETF Best Current Practice. URL: <a href="http://tools.ietf.org/html/bcp47">http://tools.ietf.org/html/bcp47</a> 
+</dd><dt id="bib-IEEE-754-1985">[IEEE-754-1985]</dt><dd>IEEE. <cite>IEEE Standard for Binary Floating-Point Arithmetic.</cite> See <a href="http://standards.ieee.org/reading/ieee/std_public/description/busarch/754-1985_desc.html">http://standards.ieee.org/reading/ieee/std_public/description/busarch/754-1985_desc.html</a>
+</dd><dt id="bib-JSON-LD">[JSON-LD]</dt><dd><cite><a href="http://json-ld.org/spec/ED/json-ld-syntax/20120522/">The JSON-LD Syntax</a></cite> Manu Sporny, Gregg Kellogg, Markus Lanthaler Editors. World Wide Web Consortium (work in progress). 22 May 2012. Editor's Draft. This edition of the JSON-LD Syntax specification is http://json-ld.org/spec/ED/json-ld-syntax/20120522/. The <a href="http://json-ld.org/spec/latest/json-ld-syntax/">latest edition of the JSON-LD Syntax</a> is available at http://json-ld.org/spec/latest/json-ld-syntax/
+</dd><dt id="bib-JSON-POINTER">[JSON-POINTER]</dt><dd><cite><a href="http://tools.ietf.org/html/draft-ietf-appsawg-json-pointer-02">JSON Pointer</a></cite> P. Bryan, Ed. IETF Draft. URL: <a href="http://tools.ietf.org/html/draft-ietf-appsawg-json-pointer-02">http://tools.ietf.org/html/draft-ietf-appsawg-json-pointer-02</a>
+</dd><dt id="bib-RDF-CONCEPTS">[RDF-CONCEPTS]</dt><dd><cite><a href="http://www.w3.org/TR/2011/WD-rdf11-concepts-20110830/">RDF 1.1 Concepts and Abstract Syntax</a></cite> Richard Cyganiak, David Wood, Editors. World Wide Web Consortium (work in progress). 30 May 2012. Editor's Draft. This edition of the JSON-LD Syntax specification is http://www.w3.org/TR/2011/WD-rdf11-concepts-20110830/. The <a href="http://www.w3.org/TR/rdf11-concepts/">latest edition of the JSON-LD Syntax</a> is available at http://www.w3.org/TR/rdf11-concepts/
+</dd><dt id="bib-RDF-SCHEMA">[RDF-SCHEMA]</dt><dd>Dan Brickley; Ramanathan V. Guha. <a href="http://www.w3.org/TR/2004/REC-rdf-schema-20040210"><cite>RDF Vocabulary Description Language 1.0: RDF Schema.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-schema-20040210">http://www.w3.org/TR/2004/REC-rdf-schema-20040210</a> 
+</dd><dt id="bib-RFC3986">[RFC3986]</dt><dd>T. Berners-Lee; R. Fielding; L. Masinter. <a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource Identifier (URI): Generic Syntax.</cite></a> January 2005. Internet RFC 3986. URL: <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a> 
+</dd><dt id="bib-RFC3987">[RFC3987]</dt><dd>M. Dürst; M. Suignard. <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized Resource Identifiers (IRIs).</cite></a> January 2005. Internet RFC 3987. URL: <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a> 
+</dd><dt id="bib-RFC4627">[RFC4627]</dt><dd>D. Crockford. <a href="http://www.ietf.org/rfc/rfc4627.txt"><cite>The application/json Media Type for JavaScript Object Notation (JSON)</cite></a> July 2006. Internet RFC 4627. URL: <a href="http://www.ietf.org/rfc/rfc4627.txt">http://www.ietf.org/rfc/rfc4627.txt</a>
+</dd><dt id="bib-WEBIDL">[WEBIDL]</dt><dd><cite><a href="http://www.w3.org/TR/2012/CR-WebIDL-20120419/">Web IDL</a></cite> Cameron McCormack, Editor. World Wide Web Consortium. 19 April 2012. Candidate Recommendataion. This edition of Web IDL is http://www.w3.org/TR/2012/CR-WebIDL-20120419/. The <a href="http://dev.w3.org/2006/webapi/WebIDL/">latest edition of Web IDL</a> is available at http://dev.w3.org/2006/webapi/WebIDL/
+</dd><dt id="bib-XMLSCHEMA11-2">[XMLSCHEMA11-2]</dt><dd>Henry S. Thompson; et al. <a href="http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/"><cite>W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes.</cite></a> 5 April 2012. W3C Recommendation URL: <a href="http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/">http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/</a> 
+</dd></dl></div><div id="informative-references" class="section"><h3><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-ECMA-262">[ECMA-262]</dt><dd><a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm"><cite>ECMAScript Language Specification.</cite></a> December 1999. URL: <a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">http://www.ecma-international.org/publications/standards/Ecma-262.htm</a> 
+</dd><dt id="bib-TURTLE-TR">[TURTLE-TR]</dt><dd>Eric Prud'hommeaux, Gavin Carothers. <cite><a href="http://www.w3.org/TR/2011/WD-turtle-20110809/">Turtle: Terse RDF Triple Language.</a></cite> 09 August 2011. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2011/WD-turtle-20110809/">http://www.w3.org/TR/2011/WD-turtle-20110809/</a>
+</dd><dt id="bib-UNICODE">[UNICODE]</dt><dd>The Unicode Consortium. <a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html"><cite>The Unicode Standard.</cite></a> 2003. Defined by: The Unicode Standard, Version 4.0 (Boston, MA, Addison-Wesley, ISBN 0-321-18578-1), as updated from time to time by the publication of new versions URL: <a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html">http://www.unicode.org/unicode/standard/versions/enumeratedversions.html</a> 
+</dd></dl></div></div></body></html>

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/spec/WD/json-ld-syntax/20120712/diff-20120626.html	Tue Jun 26 23:49:05 2012 -0400
@@ -0,0 +1,14775 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.1//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd">
+<html dir="ltr" xmlns="http://www.w3.org/1999/xhtml" typeof="bibo:Document">
+<head>
+<title>JSON-LD Syntax 1.0</title>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+
+<!-- 
+  === NOTA BENE ===
+  For the three scripts below, if your spec resides on dev.w3 you can check them
+  out in the same tree and use relative links so that they'll work offline,
+   -->
+
+
+
+<style type="text/css">
+.diff { font-weight:bold; color:#0a3; }
+</style>
+<style type="text/css">/*****************************************************************
+ * ReSpec 3 CSS
+ * Robin Berjon - http://berjon.com/
+ *****************************************************************/
+
+/* --- INLINES --- */
+em.rfc2119 { 
+    text-transform:     lowercase;
+    font-variant:       small-caps;
+    font-style:         normal;
+    color:              #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+    border: none;
+}
+
+dfn {
+    font-weight:    bold;
+}
+
+a.internalDFN {
+    color:  inherit;
+    border-bottom:  1px solid #99c;
+    text-decoration:    none;
+}
+
+a.externalDFN {
+    color:  inherit;
+    border-bottom:  1px dotted #ccc;
+    text-decoration:    none;
+}
+
+a.bibref {
+    text-decoration:    none;
+}
+
+cite .bibref {
+    font-style: normal;
+}
+
+code {
+    color:  #ff4500;
+}
+
+
+/* --- --- */
+ol.algorithm { counter-reset:numsection; list-style-type: none; }
+ol.algorithm li { margin: 0.5em 0; }
+ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }
+
+
+/* --- WEB IDL --- */
+pre.idl {
+    border-top: 1px solid #90b8de;
+    border-bottom: 1px solid #90b8de;
+    padding:    1em;
+    line-height:    120%;
+}
+
+pre.idl::before {
+    content:    "WebIDL";
+    display:    block;
+    width:      150px;
+    background: #90b8de;
+    color:  #fff;
+    font-family:    initial;
+    padding:    3px;
+    font-weight:    bold;
+    margin: -1em 0 1em -1em;
+}
+
+.idlType {
+    color:  #ff4500;
+    font-weight:    bold;
+    text-decoration:    none;
+}
+
+/*.idlModule*/
+/*.idlModuleID*/
+/*.idlInterface*/
+.idlInterfaceID, .idlDictionaryID, .idlCallbackID, .idlEnumID {
+    font-weight:    bold;
+    color:  #005a9c;
+}
+
+.idlSuperclass {
+    font-style: italic;
+    color:  #005a9c;
+}
+
+/*.idlAttribute*/
+.idlAttrType, .idlFieldType, .idlMemberType {
+    color:  #005a9c;
+}
+.idlAttrName, .idlFieldName, .idlMemberName {
+    color:  #ff4500;
+}
+.idlAttrName a, .idlFieldName a, .idlMemberName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlMethod*/
+.idlMethType, .idlCallbackType {
+    color:  #005a9c;
+}
+.idlMethName {
+    color:  #ff4500;
+}
+.idlMethName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlParam*/
+.idlParamType {
+    color:  #005a9c;
+}
+.idlParamName {
+    font-style: italic;
+}
+
+.extAttr {
+    color:  #666;
+}
+
+/*.idlConst*/
+.idlConstType {
+    color:  #005a9c;
+}
+.idlConstName {
+    color:  #ff4500;
+}
+.idlConstName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlException*/
+.idlExceptionID {
+    font-weight:    bold;
+    color:  #c00;
+}
+
+.idlTypedefID, .idlTypedefType {
+    color:  #005a9c;
+}
+
+.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
+    color:  #c00;
+    font-weight:    normal;
+}
+
+.excName a {
+    font-family:    monospace;
+}
+
+.idlRaises a.idlType, .excName a.idlType {
+    border-bottom:  1px dotted #c00;
+}
+
+.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
+    width:  45px;
+    text-align: center;
+}
+.excGetSetTrue, .prmNullTrue, .prmOptTrue { color:  #0c0; }
+.excGetSetFalse, .prmNullFalse, .prmOptFalse { color:  #c00; }
+
+.idlImplements a {
+    font-weight:    bold;
+}
+
+dl.attributes, dl.methods, dl.constants, dl.fields, dl.dictionary-members {
+    margin-left:    2em;
+}
+
+.attributes dt, .methods dt, .constants dt, .fields dt, .dictionary-members dt {
+    font-weight:    normal;
+}
+
+.attributes dt code, .methods dt code, .constants dt code, .fields dt code, .dictionary-members dt code {
+    font-weight:    bold;
+    color:  #000;
+    font-family:    monospace;
+}
+
+.attributes dt code, .fields dt code, .dictionary-members dt code {
+    background:  #ffffd2;
+}
+
+.attributes dt .idlAttrType code, .fields dt .idlFieldType code, .dictionary-members dt .idlMemberType code {
+    color:  #005a9c;
+    background:  transparent;
+    font-family:    inherit;
+    font-weight:    normal;
+    font-style: italic;
+}
+
+.methods dt code {
+    background:  #d9e6f8;
+}
+
+.constants dt code {
+    background:  #ddffd2;
+}
+
+.attributes dd, .methods dd, .constants dd, .fields dd, .dictionary-members dd {
+    margin-bottom:  1em;
+}
+
+table.parameters, table.exceptions {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    margin: 0.5em 0;
+    width:  100%;
+}
+table.parameters { border-bottom:  1px solid #90b8de; }
+table.exceptions { border-bottom:  1px solid #deb890; }
+
+.parameters th, .exceptions th {
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+    font-family:    initial;
+    font-weight:    normal;
+    text-shadow:    #666 1px 1px 0;
+}
+.parameters th { background: #90b8de; }
+.exceptions th { background: #deb890; }
+
+.parameters td, .exceptions td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+    vertical-align: top;
+}
+
+.parameters tr:first-child td, .exceptions tr:first-child td {
+    border-top: none;
+}
+
+.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
+    width:  100px;
+}
+
+.parameters td.prmType {
+    width:  120px;
+}
+
+table.exceptions table {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    width:  100%;
+}
+
+/* --- TOC --- */
+.toc a, .tof a {
+    text-decoration:    none;
+}
+
+a .secno, a .figno {
+    color:  #000;
+}
+
+ul.tof, ol.tof {
+    list-style: none outside none;
+}
+
+.caption {
+    margin-top: 0.5em;
+    font-style:   italic;
+}
+
+/* --- TABLE --- */
+table.simple {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    border-bottom:  3px solid #005a9c;
+}
+
+.simple th {
+    background: #005a9c;
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+}
+
+.simple th[scope="row"] {
+    background: inherit;
+    color:  inherit;
+    border-top: 1px solid #ddd;
+}
+
+.simple td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+    background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+    margin-top: 0;
+}
+
+.section dd > p:last-child {
+    margin-bottom: 0;
+}
+
+.section dd {
+    margin-bottom:  1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+    margin-bottom:  0;
+}
+</style><style type="text/css">/* --- EXAMPLES --- */
+div.example-title {
+    min-width: 7.5em;
+    color: #b9ab2d;
+}
+div.example-title span {
+    text-transform: uppercase;   
+}
+div.example, div.illegal-example {
+    padding: 0.5em;
+    margin: 1em 0;
+    position: relative;
+    clear: both;
+}
+div.illegal-example { color: red }
+div.illegal-example p { color: black }
+div.example {
+    padding: .5em;
+    border-left-width: .5em;
+    border-left-style: solid;
+    border-color: #e0cb52;
+    background: #fcfaee;    
+}
+</style><style type="text/css">/* --- ISSUES/NOTES --- */
+div.issue-title, div.note-title {
+    padding-right:  1em;
+    min-width: 7.5em;
+    color: #b9ab2d;
+}
+div.issue-title { color: #e05252; }
+div.note-title { color: #52e052; }
+div.issue-title span, div.note-title span {
+    text-transform: uppercase;
+}
+div.note, div.issue {
+    margin-top: 1em;
+    margin-bottom: 1em;
+}
+.note > p:first-child, .issue > p:first-child { margin-top: 0 }
+.issue, .note {
+    padding: .5em;
+    border-left-width: .5em;
+    border-left-style: solid;
+}
+div.issue, div.note {
+    padding: 0.5em;
+    margin: 1em 0;
+    position: relative;
+    clear: both;
+}
+span.note, span.issue { padding: .1em .5em .15em; }
+
+.issue {
+    border-color: #e05252;
+    background: #fbe9e9;
+}
+.note {
+    border-color: #52e052;
+    background: #e9fbe9;
+}
+
+
+</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD" /><script type="text/javascript" src="http://s3.amazonaws.com/green-turtle/RDFa.0.15.0.js"></script><meta name="green-turtle-rdfa-message" content="{ &quot;type&quot;: &quot;status&quot;, &quot;loaded&quot;: true, &quot;count&quot;: 44 }" /><style type='text/css'>
+.diff-old-a {
+  font-size: smaller;
+  color: red;
+}
+
+.diff-new { background-color: yellow; }
+.diff-chg { background-color: lime; }
+.diff-new:before,
+.diff-new:after
+    { content: "\2191" }
+.diff-chg:before, .diff-chg:after
+    { content: "\2195" }
+.diff-old { text-decoration: line-through; background-color: #FBB; }
+.diff-old:before,
+.diff-old:after
+    { content: "\2193" }
+:focus { border: thin red solid}
+</style>
+</head>
+
+
+<body>
+<div class="head">
+<p>
+<a href="http://www.w3.org/">
+<img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C" />
+</a>
+</p>
+<h1 class="title" id="title">
+JSON-LD
+Syntax
+1.0
+</h1>
+<h2 id="subtitle">
+A
+Context-based
+JSON
+Serialization
+for
+Linking
+Data
+</h2>
+<del class="diff-old">Final
+Community
+Group
+Specification
+26
+June
+</del>
+<h2 id="w3c-working-draft-12-july-2012">
+<acronym title="World Wide Web Consortium">
+<ins class="diff-chg">W3C
+</ins></acronym><ins class="diff-chg">
+Working
+Draft
+12
+July
+</ins>
+2012
+</h2>
+<dl>
+<dt>
+<ins class="diff-new">This
+version:
+</ins></dt><dd><a href="http://www.w3.org/TR/2012/WD-json-ld-syntax-20120712/"><ins class="diff-new">
+http://www.w3.org/TR/2012/WD-json-ld-syntax-20120712/
+</ins></a></dd><dt><ins class="diff-new">
+Latest
+published
+version:
+</ins></dt><dd><a href="http://www.w3.org/TR/json-ld-syntax/"><ins class="diff-new">
+http://www.w3.org/TR/json-ld-syntax/
+</ins></a></dd><dt>
+Latest
+editor's
+draft:
+</dt>
+<dd>
+<del class="diff-old">http://json-ld.org/spec/latest/json-ld-syntax/
+</del>
+<a href="http://dvcs.w3.org/hg/json-ld/raw-file/default/spec/latest/json-ld-syntax/index.html">
+<ins class="diff-chg">http://dvcs.w3.org/hg/json-ld/raw-file/default/spec/latest/json-ld-syntax/index.html
+</ins>
+</a>
+</dd>
+<dt>
+Editors:
+</dt>
+<dd rel="bibo:editor" inlist="">
+<span typeof="foaf:Person">
+<a rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="http://manu.sporny.org/">
+Manu
+Sporny
+</a>,
+<a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">
+Digital
+Bazaar
+</a>
+</span>
+</dd>
+<dd rel="bibo:editor" inlist="">
+<span typeof="foaf:Person">
+<a rel="foaf:homepage" property="foaf:name" content="Gregg Kellogg" href="http://greggkellogg.net/">
+Gregg
+Kellogg
+</a>,
+<a rel="foaf:workplaceHomepage" href="http://kellogg-assoc.com/">
+Kellogg
+Associates
+</a>
+</span>
+</dd>
+<dd rel="bibo:editor" inlist="">
+<span typeof="foaf:Person">
+<a rel="foaf:homepage" property="foaf:name" content="Markus Lanthaler" href="http://www.markus-lanthaler.com/">
+Markus
+Lanthaler
+</a>,
+<a rel="foaf:workplaceHomepage" href="http://www.tugraz.at/">
+Graz
+University
+of
+Technology
+</a>
+</span>
+</dd>
+<dt>
+Authors:
+</dt>
+<dd rel="dcterms:contributor">
+<span typeof="foaf:Person">
+<a rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="http://digitalbazaar.com/">
+Manu
+Sporny
+</a>,
+<a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">
+Digital
+Bazaar
+</a>
+</span>
+</dd>
+<dd rel="dcterms:contributor">
+<span typeof="foaf:Person">
+<a rel="foaf:homepage" property="foaf:name" content="Dave Longley" href="http://digitalbazaar.com/">
+Dave
+Longley
+</a>,
+<a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">
+Digital
+Bazaar
+</a>
+</span>
+</dd>
+<dd rel="dcterms:contributor">
+<span typeof="foaf:Person">
+<a rel="foaf:homepage" property="foaf:name" content="Gregg Kellogg" href="http://greggkellogg.net/">
+Gregg
+Kellogg
+</a>,
+<a rel="foaf:workplaceHomepage" href="http://kellogg-assoc.com/">
+Kellogg
+Associates
+</a>
+</span>
+</dd>
+<dd rel="dcterms:contributor">
+<span typeof="foaf:Person">
+<a rel="foaf:homepage" property="foaf:name" content="Markus Lanthaler" href="http://www.markus-lanthaler.com/">
+Markus
+Lanthaler
+</a>,
+<a rel="foaf:workplaceHomepage" href="http://www.tugraz.at/">
+Graz
+University
+of
+Technology
+</a>
+</span>
+</dd>
+<dd rel="dcterms:contributor">
+<span typeof="foaf:Person">
+<a rel="foaf:homepage" property="foaf:name" content="Mark Birbeck" href="http://webbackplane.com/">
+Mark
+Birbeck
+</a>,
+<a rel="foaf:workplaceHomepage" href="http://webbackplane.com/">
+Backplane
+Ltd.
+</a>
+</span>
+</dd>
+</dl>
+<p>
+This
+document
+is
+also
+available
+in
+this
+non-normative
+format:
+<a href="diff-20120626.html">
+diff
+to
+previous
+version
+</a>
+</p>
+<p class="copyright">
+<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">
+Copyright
+</a>
+©
+2010-2012
+<del class="diff-old">the
+Contributors
+to
+the
+JSON-LD
+Syntax
+1.0
+Specification,
+published
+by
+the
+JSON
+for
+Linking
+Data
+Community
+Group
+</del>
+<a href="http://www.w3.org/">
+<acronym title="World Wide Web Consortium">
+<ins class="diff-chg">W3C
+</ins></acronym>
+</a>
+<del class="diff-old">under
+the
+</del>
+<sup>
+<ins class="diff-chg">®
+</ins></sup><ins class="diff-chg">
+(
+</ins><a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology"><ins class="diff-chg">
+MIT
+</ins></acronym></a>,<a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics"><ins class="diff-chg">
+ERCIM
+</ins></acronym></a>,<a href="http://www.keio.ac.jp/"><ins class="diff-chg">
+Keio
+</ins></a><ins class="diff-chg">
+),
+All
+Rights
+Reserved.
+</ins><acronym title="World Wide Web Consortium">
+W3C
+<del class="diff-old">Community
+Final
+Specification
+Agreement
+(FSA)
+.
+A
+human-readable
+summary
+</del>
+</acronym>
+<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">
+<ins class="diff-chg">liability
+</ins></a>,<a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks"><ins class="diff-chg">
+trademark
+</ins>
+</a>
+<del class="diff-old">is
+available.
+</del>
+<ins class="diff-chg">and
+</ins><a href="http://www.w3.org/Consortium/Legal/copyright-documents"><ins class="diff-chg">
+document
+use
+</ins></a><ins class="diff-chg">
+rules
+apply.
+</ins>
+</p>
+<hr />
+</div>
+<div id="abstract" class="introductory section">
+<h2>
+Abstract
+</h2>
+<p>
+JSON
+has
+proven
+to
+be
+a
+highly
+useful
+object
+serialization
+and
+messaging
+format.
+In
+an
+attempt
+to
+harmonize
+the
+representation
+of
+<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
+Linked
+Data
+</a>
+in
+JSON,
+this
+specification
+outlines
+a
+common
+JSON
+representation
+format
+for
+expressing
+directed
+graphs;
+mixing
+both
+Linked
+Data
+and
+non-Linked
+Data
+in
+a
+single
+document.
+</p>
+</div>
+<div id="sotd" class="introductory section">
+<h2>
+Status
+of
+This
+Document
+</h2>
+<p>
+<em>
+This
+<del class="diff-old">specification
+was
+published
+by
+</del>
+<ins class="diff-chg">section
+describes
+</ins>
+the
+<del class="diff-old">JSON
+for
+Linking
+Data
+Community
+Group
+.
+It
+is
+not
+a
+W3C
+Standard
+nor
+is
+it
+on
+</del>
+<ins class="diff-chg">status
+of
+this
+document
+at
+</ins>
+the
+<ins class="diff-new">time
+of
+its
+publication.
+Other
+documents
+may
+supersede
+this
+document.
+A
+list
+of
+current
+</ins><acronym title="World Wide Web Consortium">
+W3C
+<del class="diff-old">Standards
+Track.
+Please
+note
+that
+under
+</del>
+</acronym>
+<ins class="diff-chg">publications
+and
+</ins>
+the
+<ins class="diff-chg">latest
+revision
+of
+this
+technical
+report
+can
+be
+found
+in
+the
+</ins><a href="http://www.w3.org/TR/"><acronym title="World Wide Web Consortium">
+W3C
+<del class="diff-old">Community
+Final
+Specification
+Agreement
+(FSA)
+</del>
+</acronym>
+<ins class="diff-chg">technical
+reports
+index
+</ins>
+</a>
+<del class="diff-old">other
+conditions
+apply.
+Learn
+more
+about
+W3C
+Community
+and
+Business
+Groups
+.
+</del>
+<ins class="diff-chg">at
+http://www.w3.org/TR/.
+</ins></em>
+</p>
+<p>
+This
+document
+has
+been
+under
+development
+for
+over
+18
+months
+in
+the
+JSON
+for
+Linking
+Data
+Community
+Group.
+The
+document
+has
+recently
+been
+<del class="diff-old">cleared
+</del>
+<ins class="diff-chg">transferred
+</ins>
+to
+<del class="diff-old">be
+moved
+into
+</del>
+the
+RDF
+Working
+Group
+for
+<del class="diff-old">review
+</del>
+<ins class="diff-chg">review,
+improvement,
+</ins>
+and
+publication
+along
+the
+Recommendation
+track.
+<del class="diff-old">This
+</del>
+<ins class="diff-chg">While
+this
+is
+a
+First
+Public
+Working
+Draft
+publication,
+the
+</ins>
+specification
+has
+undergone
+significant
+development,
+review,
+and
+changes
+during
+the
+course
+of
+the
+last
+18
+months
+and
+is
+<del class="diff-old">being
+published
+as
+a
+Final
+Community
+Group
+Specification
+to
+transition
+the
+work
+into
+</del>
+<ins class="diff-chg">more
+mature
+than
+</ins>
+the
+<del class="diff-old">RDF
+</del>
+<ins class="diff-chg">First
+Public
+</ins>
+Working
+<del class="diff-old">Group.
+</del>
+<ins class="diff-chg">Draft
+status
+implies.
+</ins>
+</p>
+<p>
+There
+are
+currently
+<a href="http://json-ld.org/#impl">
+five
+interoperable
+implementations
+</a>
+of
+this
+specification.
+There
+is
+a
+<a href="https://github.com/json-ld/json-ld.org/tree/master/test-suite">
+fairly
+complete
+test
+suite
+</a>
+and
+a
+<a href="http://json-ld.org/playground/">
+live
+JSON-LD
+editor
+</a>
+that
+is
+capable
+of
+demonstrating
+the
+features
+described
+in
+this
+document.
+While
+development
+on
+implementations,
+the
+test
+suite
+and
+the
+live
+editor
+will
+continue,
+they
+are
+believed
+to
+be
+mature
+enough
+to
+be
+integrated
+into
+a
+non-production
+system
+at
+this
+point
+in
+time
+with
+the
+expectation
+that
+they
+could
+be
+used
+in
+a
+production
+system
+within
+the
+next
+year.
+</p>
+<p>
+There
+are
+a
+number
+of
+ways
+that
+one
+may
+participate
+in
+the
+development
+of
+this
+specification:
+</p>
+<ul>
+<li>
+If
+you
+want
+to
+make
+sure
+that
+your
+feedback
+is
+formally
+addressed
+by
+the
+RDF
+Working
+Group,
+you
+should
+send
+it
+to
+public-rdf-comments:
+<a href="http://lists.w3.org/Archives/Public/public-rdf-comments/">
+public-rdf-comments@w3.org
+</a>
+</li>
+<li>
+Ad-hoc
+technical
+discussion
+primarily
+occurs
+on
+the
+public
+community
+mailing
+list:
+<a href="http://lists.w3.org/Archives/Public/public-linked-json/">
+public-linked-json@w3.org
+</a>
+</li>
+<li>
+<a href="http://json-ld.org/minutes/">
+Public
+JSON-LD
+Community
+Group
+teleconferences
+</a>
+are
+held
+on
+Tuesdays
+at
+1500UTC
+every
+week.
+</li>
+<li>
+RDF
+Working
+Group
+teleconferences
+are
+held
+on
+Wednesdays
+at
+1500UTC
+every
+week.
+Participation
+is
+limited
+to
+RDF
+Working
+Group
+members.
+</li>
+<li>
+Specification
+bugs
+and
+issues
+should
+be
+reported
+in
+the
+<a href="https://github.com/json-ld/json-ld.org/issues">
+issue
+tracker
+</a>
+if
+you
+do
+not
+want
+to
+send
+an
+e-mail
+to
+the
+public-rdf-comments
+mailing
+list.
+</li>
+<li>
+<a href="https://github.com/json-ld/json-ld.org/tree/master/spec">
+Source
+code
+</a>
+for
+the
+specification
+can
+be
+found
+on
+Github.
+</li>
+<li>
+The
+<a href="http://webchat.freenode.net/?channels=json-ld">
+#json-ld
+</a>
+IRC
+channel
+is
+available
+for
+real-time
+discussion
+on
+irc.freenode.net.
+</li>
+</ul>
+<p>
+<ins class="diff-new">This
+document
+was
+published
+by
+the
+</ins><a href="http://www.w3.org/2011/rdf-wg/"><ins class="diff-new">
+RDF
+Working
+Group
+</ins></a><ins class="diff-new">
+as
+a
+First
+Public
+Working
+Draft.
+This
+document
+is
+intended
+to
+become
+a
+</ins><acronym title="World Wide Web Consortium"><ins class="diff-new">
+W3C
+</ins></acronym><ins class="diff-new">
+Recommendation.
+If
+you
+wish
+to
+make
+comments
+regarding
+this
+document,
+please
+send
+them
+to
+</ins><a href="mailto:public-rdf-comments@w3.org"><ins class="diff-new">
+public-rdf-comments@w3.org
+</ins></a><ins class="diff-new">
+(
+</ins><a href="mailto:public-rdf-comments-request@w3.org?subject=subscribe"><ins class="diff-new">
+subscribe
+</ins></a>,<a href="http://lists.w3.org/Archives/Public/public-rdf-comments/"><ins class="diff-new">
+archives
+</ins></a><ins class="diff-new">
+).
+All
+feedback
+is
+welcome.
+</ins></p><p><ins class="diff-new">
+Publication
+as
+a
+Working
+Draft
+does
+not
+imply
+endorsement
+by
+the
+</ins><acronym title="World Wide Web Consortium"><ins class="diff-new">
+W3C
+</ins></acronym><ins class="diff-new">
+Membership.
+This
+is
+a
+draft
+document
+and
+may
+be
+updated,
+replaced
+or
+obsoleted
+by
+other
+documents
+at
+any
+time.
+It
+is
+inappropriate
+to
+cite
+this
+document
+as
+other
+than
+work
+in
+progress.
+</ins></p><p><ins class="diff-new">
+This
+document
+was
+produced
+by
+a
+group
+operating
+under
+the
+</ins><a href="http://www.w3.org/Consortium/Patent-Policy-20040205/"><ins class="diff-new">
+5
+February
+2004
+</ins><acronym title="World Wide Web Consortium"><ins class="diff-new">
+W3C
+</ins></acronym><ins class="diff-new">
+Patent
+Policy
+</ins></a>.<acronym title="World Wide Web Consortium"><ins class="diff-new">
+W3C
+</ins></acronym><ins class="diff-new">
+maintains
+a
+</ins><a href="http://www.w3.org/2004/01/pp-impl/46168/status" rel="disclosure"><ins class="diff-new">
+public
+list
+of
+any
+patent
+disclosures
+</ins></a><ins class="diff-new">
+made
+in
+connection
+with
+the
+deliverables
+of
+the
+group;
+that
+page
+also
+includes
+instructions
+for
+disclosing
+a
+patent.
+An
+individual
+who
+has
+actual
+knowledge
+of
+a
+patent
+which
+the
+individual
+believes
+contains
+</ins><a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential"><ins class="diff-new">
+Essential
+Claim(s)
+</ins></a><ins class="diff-new">
+must
+disclose
+the
+information
+in
+accordance
+with
+</ins><a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure"><ins class="diff-new">
+section
+6
+of
+the
+</ins><acronym title="World Wide Web Consortium"><ins class="diff-new">
+W3C
+</ins></acronym><ins class="diff-new">
+Patent
+Policy
+</ins></a>.</p>
+</div>
+<div id="toc" class="section">
+<h2 class="introductory">
+Table
+of
+Contents
+</h2>
+<ul class="toc">
+<li class="tocline">
+<a href="#introduction" class="tocxref">
+<span class="secno">
+1.
+</span>
+Introduction
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#how-to-read-this-document" class="tocxref">
+<span class="secno">
+1.1
+</span>
+How
+to
+Read
+this
+Document
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#design-goals-and-rationale" class="tocxref">
+<span class="secno">
+2.
+</span>
+Design
+Goals
+and
+Rationale
+</a>
+</li>
+<li class="tocline">
+<a href="#basic-concepts" class="tocxref">
+<span class="secno">
+3.
+</span>
+Basic
+Concepts
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#linking-data" class="tocxref">
+<span class="secno">
+3.1
+</span>
+Linking
+Data
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#syntax-tokens-and-keywords" class="tocxref">
+<span class="secno">
+3.1.1
+</span>
+Syntax
+Tokens
+and
+Keywords
+</a>
+</li>
+<li class="tocline">
+<a href="#the-context" class="tocxref">
+<span class="secno">
+3.1.2
+</span>
+The
+Context
+</a>
+</li>
+<li class="tocline">
+<a href="#from-json-to-json-ld" class="tocxref">
+<span class="secno">
+3.1.3
+</span>
+From
+JSON
+to
+JSON-LD
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#iris" class="tocxref">
+<span class="secno">
+3.2
+</span>
+IRIs
+</a>
+</li>
+<li class="tocline">
+<a href="#identifying-the-subject" class="tocxref">
+<span class="secno">
+3.3
+</span>
+Identifying
+the
+Subject
+</a>
+</li>
+<li class="tocline">
+<a href="#specifying-the-type" class="tocxref">
+<span class="secno">
+3.4
+</span>
+Specifying
+the
+Type
+</a>
+</li>
+<li class="tocline">
+<a href="#string-internationalization" class="tocxref">
+<span class="secno">
+3.5
+</span>
+String
+Internationalization
+</a>
+</li>
+<li class="tocline">
+<a href="#json-ld-syntax" class="tocxref">
+<span class="secno">
+3.6
+</span>
+JSON-LD
+Syntax
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#advanced-concepts" class="tocxref">
+<span class="secno">
+4.
+</span>
+Advanced
+Concepts
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#compact-iris" class="tocxref">
+<span class="secno">
+4.1
+</span>
+Compact
+IRIs
+</a>
+</li>
+<li class="tocline">
+<a href="#typed-values" class="tocxref">
+<span class="secno">
+4.2
+</span>
+Typed
+Values
+</a>
+</li>
+<li class="tocline">
+<a href="#external-contexts" class="tocxref">
+<span class="secno">
+4.3
+</span>
+External
+Contexts
+</a>
+</li>
+<li class="tocline">
+<a href="#referencing-contexts-from-json-documents" class="tocxref">
+<span class="secno">
+4.4
+</span>
+Referencing
+Contexts
+from
+JSON
+Documents
+</a>
+</li>
+<li class="tocline">
+<a href="#expanded-term-definition" class="tocxref">
+<span class="secno">
+4.5
+</span>
+Expanded
+Term
+Definition
+</a>
+</li>
+<li class="tocline">
+<a href="#type-coercion" class="tocxref">
+<span class="secno">
+4.6
+</span>
+Type
+Coercion
+</a>
+</li>
+<li class="tocline">
+<a href="#iri-expansion-within-a-context" class="tocxref">
+<span class="secno">
+4.7
+</span>
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Expansion
+Within
+a
+Context
+</a>
+</li>
+<li class="tocline">
+<a href="#sets-and-lists" class="tocxref">
+<span class="secno">
+4.8
+</span>
+Sets
+and
+Lists
+</a>
+</li>
+<li class="tocline">
+<a href="#embedding" class="tocxref">
+<span class="secno">
+4.9
+</span>
+Embedding
+</a>
+</li>
+<li class="tocline">
+<a href="#named-graphs" class="tocxref">
+<span class="secno">
+4.10
+</span>
+Named
+Graphs
+</a>
+</li>
+<li class="tocline">
+<a href="#identifying-unlabeled-nodes" class="tocxref">
+<span class="secno">
+4.11
+</span>
+Identifying
+Unlabeled
+Nodes
+</a>
+</li>
+<li class="tocline">
+<a href="#aliasing-keywords" class="tocxref">
+<span class="secno">
+4.12
+</span>
+Aliasing
+Keywords
+</a>
+</li>
+<li class="tocline">
+<a href="#expanded-document-form" class="tocxref">
+<span class="secno">
+4.13
+</span>
+Expanded
+Document
+Form
+</a>
+</li>
+<li class="tocline">
+<a href="#compact-document-form" class="tocxref">
+<span class="secno">
+4.14
+</span>
+Compact
+Document
+Form
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#json-ld-authoring-guidelines" class="tocxref">
+<span class="secno">
+A.
+</span>
+JSON-LD
+Authoring
+Guidelines
+</a>
+</li>
+<li class="tocline">
+<a href="#relationship-to-other-rdf-formats" class="tocxref">
+<span class="secno">
+B.
+</span>
+Relationship
+to
+other
+RDF
+Formats
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#rdf" class="tocxref">
+<span class="secno">
+B.1
+</span>
+RDF
+</a>
+</li>
+<li class="tocline">
+<a href="#turtle" class="tocxref">
+<span class="secno">
+B.2
+</span>
+Turtle
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#prefix-definitions" class="tocxref">
+<span class="secno">
+B.2.1
+</span>
+Prefix
+definitions
+</a>
+</li>
+<li class="tocline">
+<a href="#embedding-1" class="tocxref">
+<span class="secno">
+B.2.2
+</span>
+Embedding
+</a>
+</li>
+<li class="tocline">
+<a href="#lists" class="tocxref">
+<span class="secno">
+B.2.3
+</span>
+Lists
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#rdfa" class="tocxref">
+<span class="secno">
+B.3
+</span>
+RDFa
+</a>
+</li>
+<li class="tocline">
+<a href="#microformats" class="tocxref">
+<span class="secno">
+B.4
+</span>
+Microformats
+</a>
+</li>
+<li class="tocline">
+<a href="#microdata" class="tocxref">
+<span class="secno">
+B.5
+</span>
+Microdata
+</a>
+</li>
+</ul>
+</li>
+<li class="tocline">
+<a href="#iana-considerations" class="tocxref">
+<span class="secno">
+C.
+</span>
+IANA
+Considerations
+</a>
+</li>
+<li class="tocline">
+<a href="#acknowledgements" class="tocxref">
+<span class="secno">
+D.
+</span>
+Acknowledgements
+</a>
+</li>
+<li class="tocline">
+<a href="#references" class="tocxref">
+<span class="secno">
+E.
+</span>
+References
+</a>
+<ul class="toc">
+<li class="tocline">
+<a href="#normative-references" class="tocxref">
+<span class="secno">
+E.1
+</span>
+Normative
+references
+</a>
+</li>
+<li class="tocline">
+<a href="#informative-references" class="tocxref">
+<span class="secno">
+E.2
+</span>
+Informative
+references
+</a>
+</li>
+</ul>
+</li>
+</ul>
+</div>
+<div class="informative section" id="introduction">
+<h2>
+<span class="secno">
+1.
+</span>
+Introduction
+</h2>
+<p>
+<em>
+This
+section
+is
+non-normative.
+</em>
+</p>
+<p>
+JSON,
+as
+specified
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RFC4627">
+RFC4627
+</a>
+</cite>
+],
+is
+a
+simple
+language
+for
+representing
+data
+on
+the
+Web.
+<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
+Linked
+Data
+</a>
+is
+a
+technique
+for
+creating
+a
+network
+of
+inter-connected
+data
+across
+different
+Web
+documents
+and
+Web
+sites.
+A
+<em>
+document
+</em>
+in
+this
+data
+network
+is
+typically
+identified
+using
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+(Internationalized
+Resource
+Identifier).
+A
+software
+program
+can
+typically
+follow
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+just
+like
+you
+follow
+a
+URL
+by
+putting
+it
+into
+your
+browser's
+location
+bar.
+By
+following
+IRIs,
+a
+software
+program
+can
+find
+more
+information
+about
+the
+<em>
+document
+</em>
+and
+the
+<em>
+thing
+</em>
+s
+that
+the
+document
+describes.
+These
+<em>
+things
+</em>
+may
+also
+be
+identified
+using
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+s.
+The
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+allows
+a
+software
+program
+to
+start
+at
+one
+<em>
+document
+</em>
+and
+follow
+links
+to
+other
+<em>
+documents
+</em>
+or
+<em>
+things
+</em>
+in
+order
+to
+learn
+more
+about
+all
+of
+the
+<em>
+documents
+</em>
+and
+<em>
+things
+</em>
+described
+on
+the
+Web.
+</p>
+<p>
+JSON-LD
+is
+designed
+as
+a
+lightweight
+syntax
+that
+can
+be
+used
+to
+express
+<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
+Linked
+Data
+</a>.
+It
+is
+primarily
+intended
+to
+be
+a
+way
+to
+use
+Linked
+Data
+in
+Javascript
+and
+other
+Web-based
+programming
+environments.
+It
+is
+also
+useful
+when
+building
+inter-operable
+Web
+services
+and
+when
+storing
+Linked
+Data
+in
+JSON-based
+document
+storage
+engines.
+It
+is
+practical
+and
+designed
+to
+be
+as
+simple
+as
+possible,
+utilizing
+the
+large
+number
+of
+JSON
+parsers
+and
+libraries
+available
+today.
+</p>
+<p>
+The
+syntax
+does
+not
+necessarily
+require
+applications
+to
+change
+their
+JSON,
+but
+allows
+one
+to
+easily
+add
+meaning
+by
+simply
+adding
+or
+referencing
+a
+context.
+The
+syntax
+is
+designed
+to
+not
+disturb
+already
+deployed
+systems
+running
+on
+JSON,
+but
+provide
+a
+smooth
+upgrade
+path
+from
+JSON
+to
+JSON-LD.
+Finally,
+the
+format
+is
+intended
+to
+be
+easy
+to
+parse,
+efficient
+to
+generate,
+and
+only
+requires
+a
+very
+small
+memory
+footprint
+in
+order
+to
+operate.
+</p>
+<div id="how-to-read-this-document" class="section">
+<h3>
+<span class="secno">
+1.1
+</span>
+How
+to
+Read
+this
+Document
+</h3>
+<p>
+<em>
+This
+section
+is
+non-normative.
+</em>
+</p>
+<p>
+This
+document
+is
+a
+detailed
+specification
+for
+a
+serialization
+of
+Linked
+Data
+in
+JSON.
+The
+document
+is
+primarily
+intended
+for
+the
+following
+audiences:
+</p>
+<ul>
+<li>
+Software
+developers
+that
+want
+to
+encode
+Linked
+Data
+in
+a
+way
+that
+is
+cross-language
+compatible
+via
+JSON.
+</li>
+<li>
+Software
+developers
+that
+want
+to
+understand
+the
+design
+decisions
+and
+language
+syntax
+for
+JSON-LD.
+</li>
+<li>
+Software
+developers
+that
+want
+to
+implement
+processors
+and
+APIs
+for
+JSON-LD.
+</li>
+</ul>
+<p>
+This
+specification
+does
+not
+describe
+the
+programming
+interfaces
+for
+the
+JSON-LD
+Syntax.
+The
+specification
+that
+describes
+the
+programming
+interfaces
+for
+JSON-LD
+documents
+is
+the
+JSON-LD
+Application
+Programming
+Interface
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-JSON-LD-API">
+JSON-LD-API
+</a>
+</cite>
+].
+</p>
+<p>
+To
+understand
+the
+basics
+in
+this
+specification
+you
+must
+first
+be
+familiar
+with
+JSON,
+which
+is
+detailed
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RFC4627">
+RFC4627
+</a>
+</cite>
+].
+</p>
+<p>
+JSON
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RFC4627">
+RFC4627
+</a>
+</cite>
+]
+defines
+several
+terms
+which
+are
+used
+throughout
+this
+document:
+</p>
+<dl>
+<dt>
+<dfn title="json_object" id="dfn-json_object">
+JSON
+object
+</dfn>
+</dt>
+<dd>
+An
+object
+structure
+is
+represented
+as
+a
+pair
+of
+curly
+brackets
+surrounding
+zero
+or
+more
+name-value
+pairs.
+A
+name
+is
+a
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>.
+A
+single
+colon
+comes
+after
+each
+name,
+separating
+the
+name
+from
+the
+value.
+A
+single
+comma
+separates
+a
+value
+from
+a
+following
+name.
+The
+names
+within
+an
+object
+<em class="rfc2119" title="should">
+should
+</em>
+be
+unique.
+</dd>
+<dt>
+<dfn title="array" id="dfn-array">
+array
+</dfn>
+</dt>
+<dd>
+In
+JSON,
+an
+array
+is
+an
+<em>
+ordered
+</em>
+sequence
+of
+zero
+or
+more
+values.
+An
+array
+is
+represented
+as
+square
+brackets
+surrounding
+zero
+or
+more
+values
+that
+are
+separated
+by
+commas.
+While
+JSON-LD
+uses
+the
+same
+array
+representation
+as
+JSON,
+the
+collection
+is
+<em>
+unordered
+</em>
+by
+default.
+While
+order
+is
+preserved
+in
+regular
+JSON
+arrays,
+it
+is
+not
+in
+regular
+JSON-LD
+arrays
+unless
+specific
+markup
+is
+provided
+(see
+<a href="#sets-and-lists">
+Sets
+and
+Lists
+</a>
+).
+</dd>
+<dt>
+<dfn title="string" id="dfn-string">
+string
+</dfn>
+</dt>
+<dd>
+A
+string
+is
+a
+sequence
+of
+zero
+or
+more
+Unicode
+characters,
+wrapped
+in
+double
+quotes,
+using
+backslash
+escapes
+(if
+necessary).
+A
+character
+is
+represented
+as
+a
+single
+character
+string.
+</dd>
+<dt>
+<dfn title="number" id="dfn-number">
+number
+</dfn>
+</dt>
+<dd>
+A
+number
+is
+similar
+to
+that
+used
+in
+most
+programming
+languages,
+except
+that
+the
+octal
+and
+hexadecimal
+formats
+are
+not
+used
+and
+that
+leading
+zeros
+are
+not
+allowed.
+</dd>
+<dt>
+<dfn title="true" id="dfn-true">
+true
+</dfn>
+and
+<dfn title="false" id="dfn-false">
+false
+</dfn>
+</dt>
+<dd>
+Values
+that
+are
+used
+to
+express
+one
+of
+two
+possible
+boolean
+states.
+</dd>
+<dt>
+<dfn title="null" id="dfn-null">
+null
+</dfn>
+</dt>
+<dd>
+The
+null
+value
+is
+used
+to
+make
+the
+JSON-LD
+processor
+&quot;forget&quot;
+any
+previously
+defined
+JSON
+key
+that
+is
+associated
+with
+the
+null
+value.
+If
+a
+previous
+definition
+doesn't
+exist,
+the
+entire
+key-value
+is
+ignored.
+If
+a
+previous
+definition
+of
+the
+key
+does
+exist,
+the
+previous
+definition
+is
+undefined.
+</dd>
+<dt>
+<dfn title="subject_definition" id="dfn-subject_definition">
+subject
+definition
+</dfn>
+</dt>
+<dd>
+A
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+used
+to
+represent
+a
+<a class="tref internalDFN" title="subject" href="#dfn-subject">
+subject
+</a>
+and
+one
+or
+more
+properties
+of
+that
+subject.
+A
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+is
+a
+subject
+definition
+if
+it
+does
+not
+contain
+they
+keys
+<code>
+@value
+</code>,
+<code>
+@list
+</code>
+or
+<code>
+@set
+</code>
+and
+it
+has
+one
+or
+more
+keys
+other
+than
+<code>
+@id
+</code>.
+</dd>
+<dt>
+<dfn title="subject_reference" id="dfn-subject_reference">
+subject
+reference
+</dfn>
+</dt>
+<dd>
+A
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+used
+to
+reference
+a
+subject
+having
+only
+the
+<code>
+@id
+</code>
+key.
+</dd>
+</dl>
+<p>
+</p>
+</div>
+</div>
+<div class="informative section" id="design-goals-and-rationale">
+<h2>
+<span class="secno">
+2.
+</span>
+Design
+Goals
+and
+Rationale
+</h2>
+<p>
+<em>
+This
+section
+is
+non-normative.
+</em>
+</p>
+<p>
+A
+number
+of
+design
+goals
+were
+established
+before
+the
+creation
+of
+this
+markup
+language:
+</p>
+<dl>
+<dt>
+Simplicity
+</dt>
+<dd>
+No
+extra
+processors
+or
+software
+libraries
+should
+be
+necessary
+to
+use
+JSON-LD
+in
+its
+most
+basic
+form.
+The
+language
+will
+provide
+developers
+with
+a
+very
+easy
+learning
+curve.
+Developers
+need
+only
+know
+JSON
+and
+two
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keywords
+</a>
+(
+<code>
+@context
+</code>
+and
+<code>
+@id
+</code>
+)
+to
+use
+the
+basic
+functionality
+in
+JSON-LD.
+</dd>
+<dt>
+Compatibility
+</dt>
+<dd>
+The
+JSON-LD
+markup
+must
+be
+100%
+compatible
+with
+JSON.
+This
+ensures
+that
+all
+of
+the
+standard
+JSON
+libraries
+work
+seamlessly
+with
+JSON-LD
+documents.
+</dd>
+<dt>
+Expressiveness
+</dt>
+<dd>
+The
+syntax
+must
+be
+able
+to
+express
+directed
+graphs,
+which
+have
+been
+proven
+to
+be
+able
+to
+express
+almost
+every
+real
+world
+data
+model.
+</dd>
+<dt>
+Terseness
+</dt>
+<dd>
+The
+JSON-LD
+syntax
+must
+be
+very
+terse
+and
+human
+readable,
+requiring
+as
+little
+effort
+as
+possible
+from
+the
+developer.
+</dd>
+<dt>
+Zero
+Edits,
+most
+of
+the
+time
+</dt>
+<dd>
+JSON-LD
+must
+provide
+a
+<a href="#referencing-contexts-from-json-documents">
+mechanism
+</a>
+that
+allows
+developers
+to
+specify
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+in
+a
+way
+that
+is
+out-of-band.
+This
+allows
+organizations
+that
+have
+already
+deployed
+large
+JSON-based
+infrastructure
+to
+add
+meaning
+to
+their
+JSON
+documents
+in
+a
+way
+that
+is
+not
+disruptive
+to
+their
+day-to-day
+operations
+and
+is
+transparent
+to
+their
+current
+customers.
+At
+times,
+mapping
+JSON
+to
+a
+graph
+representation
+can
+become
+difficult.
+In
+these
+instances,
+rather
+than
+having
+JSON-LD
+support
+an
+esoteric
+use
+case,
+we
+chose
+not
+to
+support
+the
+use
+case
+and
+support
+a
+simplified
+syntax
+instead.
+So,
+while
+Zero
+Edits
+is
+a
+goal,
+it
+is
+not
+always
+possible
+without
+adding
+great
+complexity
+to
+the
+language.
+</dd>
+<dt>
+One-pass
+Processing
+</dt>
+<dd>
+JSON-LD
+supports
+one-pass
+processing,
+which
+results
+in
+a
+very
+small
+memory
+footprint
+when
+processing
+documents.
+For
+example,
+to
+expand
+a
+JSON-LD
+document
+from
+a
+compacted
+form,
+only
+one
+pass
+is
+required
+over
+the
+data.
+</dd>
+</dl>
+</div>
+<div class="normative section" id="basic-concepts">
+<h2>
+<span class="secno">
+3.
+</span>
+Basic
+Concepts
+</h2>
+<em>
+This
+section
+is
+normative.
+</em>
+<p>
+JSON-LD
+is
+designed
+to
+ensure
+that
+<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
+Linked
+Data
+</a>
+concepts
+can
+be
+marked
+up
+in
+a
+way
+that
+is
+simple
+to
+understand
+and
+create
+by
+Web
+authors.
+In
+many
+cases,
+regular
+JSON
+markup
+can
+become
+Linked
+Data
+with
+the
+simple
+addition
+of
+a
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>.
+As
+more
+JSON-LD
+features
+are
+used,
+more
+semantics
+are
+added
+to
+the
+JSON
+markup.
+</p>
+<div id="linking-data" class="section">
+<h3>
+<span class="secno">
+3.1
+</span>
+Linking
+Data
+</h3>
+<p>
+The
+following
+definition
+for
+<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
+Linked
+Data
+</a>
+is
+the
+one
+that
+will
+be
+used
+for
+this
+specification.
+</p>
+<ol>
+<li>
+<dfn title="linked_data" id="dfn-linked_data">
+Linked
+Data
+</dfn>
+is
+a
+set
+of
+documents,
+each
+containing
+a
+representation
+of
+a
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>.
+</li>
+<li>
+A
+<dfn title="linked_data_graph" id="dfn-linked_data_graph">
+linked
+data
+graph
+</dfn>
+is
+an
+unordered
+labeled
+directed
+graph,
+where
+nodes
+are
+<a class="tref internalDFN" title="subject" href="#dfn-subject">
+subject
+</a>
+s
+or
+<a class="tref internalDFN" title="object" href="#dfn-object">
+object
+</a>
+s,
+and
+edges
+are
+labeled
+using
+<a class="tref internalDFN" title="property" href="#dfn-property">
+properties
+</a>.
+</li>
+<li>
+A
+<dfn title="subject" id="dfn-subject">
+subject
+</dfn>
+is
+any
+node
+in
+a
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>
+with
+at
+least
+one
+outgoing
+edge.
+</li>
+<li>
+A
+<a class="tref internalDFN" title="subject" href="#dfn-subject">
+subject
+</a>
+<em class="rfc2119" title="should">
+should
+</em>
+be
+labeled
+with
+an
+<dfn title="iri" id="dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</dfn>
+(an
+Internationalized
+Resource
+Identifier
+as
+described
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RFC3987">
+RFC3987
+</a>
+</cite>
+]).
+</li>
+<li>
+An
+<dfn title="object" id="dfn-object">
+object
+</dfn>
+is
+a
+node
+in
+a
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>
+with
+at
+least
+one
+incoming
+edge.
+</li>
+<li>
+An
+<a class="tref internalDFN" title="object" href="#dfn-object">
+object
+</a>
+<em class="rfc2119" title="may">
+may
+</em>
+be
+labeled
+with
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+or
+a
+label
+that
+is
+not
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+such
+as
+plain
+text,
+internationalized
+text,
+or
+a
+strictly-typed
+data
+value.
+</li>
+<li>
+A
+node
+<em class="rfc2119" title="may">
+may
+</em>
+be
+a
+<a class="tref internalDFN" title="subject" href="#dfn-subject">
+subject
+</a>
+and
+an
+<a class="tref internalDFN" title="object" href="#dfn-object">
+object
+</a>
+at
+the
+same
+time.
+</li>
+<li>
+A
+<dfn title="property" id="dfn-property">
+property
+</dfn>
+is
+the
+label
+on
+an
+edge
+in
+a
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>.
+</li>
+<li>
+A
+<a class="tref internalDFN" title="property" href="#dfn-property">
+property
+</a>
+<em class="rfc2119" title="should">
+should
+</em>
+be
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+</li>
+<li>
+An
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+that
+is
+a
+label
+in
+a
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>
+<em class="rfc2119" title="should">
+should
+</em>
+be
+dereferencable
+to
+a
+<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
+Linked
+Data
+</a>
+document
+describing
+the
+labeled
+<a class="tref internalDFN" title="subject" href="#dfn-subject">
+subject
+</a>,
+<a class="tref internalDFN" title="property" href="#dfn-property">
+property
+</a>
+or
+<a class="tref internalDFN" title="object" href="#dfn-object">
+object
+</a>.
+</li>
+</ol>
+<div class="issue">
+<div class="issue-title">
+<span>
+Issue
+1
+</span>
+</div>
+<p class="">
+An
+illustration
+of
+a
+linked
+data
+graph
+would
+probably
+help
+here.
+</p>
+</div>
+<div class="issue">
+<div class="issue-title">
+<span>
+Issue
+2
+</span>
+</div>
+<p class="">
+EricP
+suggests
+that
+the
+definitions
+of
+subject
+and
+object,
+while
+being
+practical,
+are
+at
+odds
+with
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">
+RDF-CONCEPTS
+</a>
+</cite>
+]
+use
+in
+their
+roles
+within
+a
+triple.
+</p>
+</div>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+JSON-LD
+allows
+properties
+to
+be
+BNodes,
+while
+RDF
+does
+not.
+When
+used
+as
+just
+JSON-LD,
+this
+is
+not
+unreasonable;
+it
+only
+becomes
+an
+issue
+(and
+could
+raise
+an
+exception)
+when
+transformed
+to
+RDF.
+</p>
+</div>
+<p>
+Note
+that
+the
+definition
+for
+<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
+Linked
+Data
+</a>
+above
+is
+silent
+on
+the
+topic
+of
+<a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">
+unlabeled
+nodes
+</a>.
+Nevertheless,
+this
+specification
+allows
+for
+the
+expression
+of
+<a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">
+unlabeled
+nodes
+</a>,
+as
+most
+graph-based
+data
+sets
+on
+the
+Web
+contain
+a
+number
+of
+associated
+nodes
+that
+are
+not
+named
+and
+thus
+are
+not
+directly
+de-referenceable.
+</p>
+<p>
+JSON-LD
+defines
+a
+mechanism
+to
+map
+JSON
+terms,
+i.e.,
+keys
+and
+values,
+to
+IRIs.
+This
+does
+not
+mean
+that
+JSON-LD
+requires
+every
+key
+or
+value
+to
+be
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>,
+but
+rather
+ensures
+that
+keys
+and
+values
+can
+be
+mapped
+to
+IRIs
+if
+the
+developer
+desires
+to
+transform
+their
+data
+into
+<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
+Linked
+Data
+</a>.
+There
+are
+a
+few
+techniques
+that
+can
+ensure
+that
+developers
+will
+generate
+good
+Linked
+Data
+for
+the
+Web.
+JSON-LD
+formalizes
+those
+techniques.
+</p>
+<p>
+We
+will
+be
+using
+the
+following
+JSON
+markup
+as
+the
+example
+for
+the
+rest
+of
+this
+section:
+</p>
+<div class="example"><div class="example-title"><span>Example 1</span></div><pre class="example">{
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
+  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
+}
+</pre>
+</div>
+<div id="syntax-tokens-and-keywords" class="section">
+<h4>
+<span class="secno">
+3.1.1
+</span>
+Syntax
+Tokens
+and
+Keywords
+</h4>
+<p>
+JSON-LD
+specifies
+a
+number
+of
+syntax
+tokens
+and
+<dfn title="keyword" id="dfn-keyword">
+keywords
+</dfn>
+that
+are
+a
+core
+part
+of
+the
+language:
+</p>
+<dl>
+<dt>
+<code>
+@context
+</code>
+</dt>
+<dd>
+Used
+to
+define
+the
+short-hand
+names
+that
+are
+used
+throughout
+a
+JSON-LD
+document.
+These
+short-hand
+names
+are
+called
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s
+and
+help
+developers
+to
+express
+specific
+identifiers
+in
+a
+compact
+manner.
+The
+<code>
+@context
+</code>
+keyword
+is
+described
+in
+detail
+in
+the
+section
+titled
+<a href="#the-context">
+The
+Context
+</a>.
+</dd>
+<dt>
+<code>
+@graph
+</code>
+</dt>
+<dd>
+Used
+to
+explicitly
+label
+a
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>.
+This
+keyword
+is
+described
+in
+the
+section
+titled
+<a href="#named-graphs">
+Named
+Graphs
+</a>.
+</dd>
+<dt>
+<code>
+@id
+</code>
+</dt>
+<dd>
+Used
+to
+uniquely
+identify
+<em>
+things
+</em>
+that
+are
+being
+described
+in
+the
+document.
+This
+keyword
+is
+described
+in
+the
+section
+titled
+<a href="#identifying-the-subject">
+Identifying
+the
+Subject
+</a>.
+</dd>
+<dt>
+<code>
+@value
+</code>
+</dt>
+<dd>
+Used
+to
+specify
+the
+data
+that
+is
+associated
+with
+a
+particular
+<a class="tref internalDFN" title="property" href="#dfn-property">
+property
+</a>
+in
+the
+graph.
+This
+keyword
+is
+described
+in
+the
+sections
+titled
+<a href="#string-internationalization">
+String
+Internationalization
+</a>
+and
+<a href="#typed-values">
+Typed
+Values
+</a>.
+</dd>
+<dt>
+<code>
+@language
+</code>
+</dt>
+<dd>
+Used
+to
+specify
+the
+native
+language
+for
+a
+particular
+value
+or
+the
+default
+language
+of
+a
+JSON-LD
+document.
+This
+keyword
+is
+described
+in
+the
+section
+titled
+<a href="#string-internationalization">
+String
+Internationalization
+</a>.
+</dd>
+<dt>
+<code>
+@type
+</code>
+</dt>
+<dd>
+Used
+to
+set
+the
+data
+type
+of
+a
+<a class="tref internalDFN" title="subject" href="#dfn-subject">
+subject
+</a>
+or
+<a class="tref internalDFN" title="typed_value" href="#dfn-typed_value">
+typed
+value
+</a>.
+This
+keyword
+is
+described
+in
+the
+section
+titled
+<a href="#typed-values">
+Typed
+Values
+</a>.
+</dd>
+<dt>
+<code>
+@container
+</code>
+</dt>
+<dd>
+Used
+to
+set
+the
+container
+of
+a
+particular
+value.
+This
+keyword
+is
+described
+in
+the
+section
+titled
+<a href="#sets-and-lists">
+Sets
+and
+Lists
+</a>.
+</dd>
+<dt>
+<code>
+@list
+</code>
+</dt>
+<dd>
+Used
+to
+express
+an
+ordered
+set
+of
+data.
+This
+keyword
+is
+described
+in
+the
+section
+titled
+<a href="#sets-and-lists">
+Sets
+and
+Lists
+</a>.
+</dd>
+<dt>
+<code>
+@set
+</code>
+</dt>
+<dd>
+Used
+to
+express
+an
+unordered
+set
+of
+data.
+This
+keyword
+is
+described
+in
+the
+section
+titled
+<a href="#sets-and-lists">
+Sets
+and
+Lists
+</a>.
+</dd>
+<dt>
+<code>:
+</code>
+</dt>
+<dd>
+The
+separator
+for
+JSON
+keys
+and
+values
+that
+use
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+IRIs
+</a>.
+</dd>
+</dl>
+<p>
+For
+the
+avoidance
+of
+doubt,
+all
+keys,
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keywords
+</a>,
+and
+values
+in
+JSON-LD
+are
+case-sensitive.
+</p>
+</div>
+<div id="the-context" class="section">
+<h4>
+<span class="secno">
+3.1.2
+</span>
+The
+Context
+</h4>
+<p>
+In
+JSON-LD,
+a
+<dfn title="context" id="dfn-context">
+context
+</dfn>
+is
+used
+to
+map
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s,
+i.e.,
+properties
+with
+associated
+values
+in
+an
+JSON
+document,
+to
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+s.
+A
+<dfn title="term" id="dfn-term">
+term
+</dfn>
+is
+a
+short
+word
+that
+expands
+to
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+<a class="tref internalDFN" title="term" href="#dfn-term">
+Term
+</a>
+s
+<em class="rfc2119" title="may">
+may
+</em>
+be
+defined
+as
+any
+valid
+JSON
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>
+other
+than
+a
+JSON-LD
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>.
+To
+avoid
+forward-compatibility
+issues,
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s
+starting
+with
+an
+<code>
+@
+</code>
+character
+<em class="rfc2119" title="should not">
+should
+not
+</em>
+be
+used
+as
+they
+might
+be
+used
+as
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keywords
+</a>
+in
+future
+versions
+of
+JSON-LD.
+Furthermore,
+the
+use
+of
+empty
+terms
+(
+<code>
+&quot;&quot;
+</code>
+)
+is
+discouraged
+as
+not
+all
+programming
+languages
+are
+able
+to
+handle
+empty
+property
+names.
+</p>
+<p>
+The
+Web
+uses
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+IRIs
+</a>
+for
+unambiguous
+identification.
+The
+idea
+is
+that
+these
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s
+mean
+something
+that
+may
+be
+of
+use
+to
+other
+developers
+and
+that
+it
+is
+useful
+to
+give
+them
+an
+unambiguous
+identifier.
+That
+is,
+it
+is
+useful
+for
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s
+to
+expand
+to
+IRIs
+so
+that
+developers
+don't
+accidentally
+step
+on
+each
+other's
+<dfn title="vocabulary" id="dfn-vocabulary">
+vocabulary
+</dfn>
+terms
+and
+other
+resources.
+Furthermore,
+developers,
+and
+machines,
+are
+able
+to
+use
+this
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+(by
+plugging
+it
+directly
+into
+a
+web
+browser,
+for
+instance)
+to
+go
+to
+the
+term
+and
+get
+a
+definition
+of
+what
+the
+term
+means.
+This
+mechanism
+is
+analogous
+to
+the
+way
+we
+can
+use
+<a href="http://wordnet.princeton.edu/">
+WordNet
+</a>
+today
+to
+see
+the
+definition
+of
+words
+in
+the
+English
+language.
+Developers
+and
+machines
+need
+the
+same
+sort
+of
+definition
+of
+terms.
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+IRIs
+</a>
+provide
+a
+way
+to
+ensure
+that
+these
+terms
+are
+unambiguous.
+For
+example,
+the
+term
+<code>
+name
+</code>
+may
+map
+directly
+to
+the
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+<code>
+http://xmlns.com/foaf/0.1/name
+</code>.
+This
+allows
+JSON-LD
+documents
+to
+be
+constructed
+using
+the
+common
+JSON
+practice
+of
+simple
+name/value
+pairs
+while
+ensuring
+that
+the
+data
+is
+useful
+outside
+of
+the
+page,
+API
+or
+database
+in
+which
+it
+resides.
+The
+value
+of
+a
+term
+mapping
+<em class="rfc2119" title="must">
+must
+</em>
+be
+either;
+1)
+a
+simple
+string
+with
+the
+lexical
+form
+of
+an
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+or
+2)
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+or
+3)
+an
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+containing
+an
+<code>
+@id
+</code>,
+<code>
+@type
+</code>,
+<code>
+@language
+</code>,
+or
+<code>
+@container
+</code>
+keyword
+(all
+other
+keywords
+are
+ignored
+by
+a
+JSON-LD
+processor).
+</p>
+<p>
+These
+Linked
+Data
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s
+are
+typically
+collected
+in
+a
+context
+document
+that
+would
+look
+something
+like
+this:
+</p>
+<div class="example"><div class="example-title"><span>Example 2</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+    &quot;depiction&quot;:
+    {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/depiction&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    },
+    &quot;homepage&quot;:
+    {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    },
+  }
+}
+</pre>
+</div>
+<p>
+Assuming
+that
+this
+context
+document
+can
+be
+retrieved
+at
+<code>
+http://json-ld.org/contexts/person.jsonld
+</code>,
+it
+can
+be
+referenced
+from
+a
+JSON-LD
+document
+by
+adding
+a
+single
+line.
+The
+JSON
+markup
+shown
+in
+the
+previous
+section
+could
+be
+changed
+as
+follows:
+</p>
+<div class="example"><div class="example-title"><span>Example 3</span></div><pre class="example">{
+  <span class="diff">&quot;@context&quot;: &quot;http://json-ld.org/contexts/person.jsonld&quot;,</span>
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
+  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
+}
+</pre>
+</div>
+<p>
+The
+additions
+above
+transform
+the
+previous
+JSON
+document
+into
+a
+JSON
+document
+with
+added
+semantics
+because
+the
+<code>
+@context
+</code>
+specifies
+how
+the
+<strong>
+name
+</strong>,
+<strong>
+homepage
+</strong>,
+and
+<strong>
+depiction
+</strong>
+terms
+map
+to
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+IRIs
+</a>.
+Mapping
+those
+keys
+to
+IRIs
+gives
+the
+data
+global
+context.
+If
+two
+developers
+use
+the
+same
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+to
+describe
+a
+property,
+they
+are
+more
+than
+likely
+expressing
+the
+same
+concept.
+This
+allows
+both
+developers
+to
+re-use
+each
+others'
+data
+without
+having
+to
+agree
+to
+how
+their
+data
+will
+interoperate
+on
+a
+site-by-site
+basis.
+Contexts
+may
+also
+contain
+type
+information
+for
+certain
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s
+as
+well
+as
+other
+processing
+instructions
+for
+the
+JSON-LD
+processor.
+</p>
+<p>
+Contexts
+<em class="rfc2119" title="may">
+may
+</em>
+be
+specified
+in-line.
+This
+ensures
+that
+JSON-LD
+documents
+can
+be
+processed
+when
+a
+JSON-LD
+processor
+does
+not
+have
+access
+to
+the
+Web.
+</p>
+<div class="example"><div class="example-title"><span>Example 4</span></div><pre class="example">{
+  <span class="diff">&quot;@context&quot;:
+  {
+    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+    &quot;depiction&quot;:
+    {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/depiction&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    },
+    &quot;homepage&quot;:
+    {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    },
+  },</span>
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
+  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
+}
+</pre>
+</div>
+<p>
+Contexts
+<em class="rfc2119" title="may">
+may
+</em>
+be
+used
+at
+any
+time
+a
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>
+is
+defined.
+A
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>
+<em class="rfc2119" title="may">
+may
+</em>
+specify
+multiple
+contexts,
+using
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>,
+which
+is
+processed
+in
+order.
+This
+is
+useful
+when
+an
+author
+would
+like
+to
+use
+an
+existing
+context
+and
+add
+application-specific
+terms
+to
+the
+existing
+context.
+Duplicate
+context
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s
+<em class="rfc2119" title="must">
+must
+</em>
+be
+overridden
+using
+a
+last-defined-overrides
+mechanism.
+</p>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+If
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+is
+re-defined
+within
+a
+context,
+all
+previous
+rules
+associated
+with
+the
+previous
+definition
+are
+removed.
+A
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+defined
+in
+a
+previous
+context
+<em class="rfc2119" title="must">
+must
+</em>
+be
+removed,
+if
+it
+is
+re-defined
+to
+<code>
+null
+</code>.
+</p>
+</div>
+<p>
+The
+set
+of
+contexts
+defined
+within
+a
+specific
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>
+are
+referred
+to
+as
+<dfn title="local_context" id="dfn-local_context">
+local
+context
+</dfn>
+s.
+Setting
+the
+context
+to
+<code>
+null
+</code>
+effectively
+sets
+the
+<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
+local
+context
+</a>
+to
+the
+initial
+context
+(further
+explained
+in
+the
+JSON-LD
+API,
+Appendix
+A,
+Initial
+Context
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-JSON-LD-API">
+JSON-LD-API
+</a>
+</cite>
+]
+).
+The
+<dfn title="active_context" id="dfn-active_context">
+active
+context
+</dfn>
+refers
+to
+the
+accumulation
+of
+<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
+local
+context
+</a>
+s
+that
+are
+in
+scope
+at
+a
+specific
+point
+within
+the
+document.
+The
+following
+example
+specifies
+an
+external
+context
+and
+then
+layers
+a
+local
+context
+on
+top
+of
+the
+external
+context:
+</p>
+<div class="example"><div class="example-title"><span>Example 5</span></div><pre class="example">{
+  <span class="diff">&quot;@context&quot;: [
+    &quot;http://json-ld.org/contexts/person.jsonld&quot;,
+    {
+      &quot;pic&quot;: &quot;http://xmlns.com/foaf/0.1/depiction&quot;
+    }
+  ],</span>
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
+  <span class="diff">&quot;pic&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;</span>
+}
+</pre>
+</div>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+To
+ensure
+the
+best
+possible
+performance,
+it
+is
+a
+best
+practice
+to
+put
+the
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+definition
+at
+the
+top
+of
+the
+JSON-LD
+document.
+If
+it
+isn't
+listed
+first,
+processors
+have
+to
+save
+each
+key-value
+pair
+until
+the
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+is
+processed.
+This
+creates
+a
+memory
+and
+complexity
+burden
+for
+certain
+types
+of
+low-memory
+footprint
+JSON-LD
+processors.
+</p>
+</div>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+The
+<code>
+null
+</code>
+value
+is
+processed
+in
+a
+special
+way
+in
+JSON-LD.
+Unless
+otherwise
+specified,
+a
+JSON-LD
+processor
+<em class="rfc2119" title="must">
+must
+</em>
+act
+as
+if
+a
+key-value
+pair
+in
+the
+body
+of
+a
+JSON-LD
+document
+was
+never
+declared
+when
+the
+value
+equals
+<em>
+null
+</em>.
+If
+<code>
+@value
+</code>,
+<code>
+@list
+</code>,
+or
+<code>
+@set
+</code>
+is
+set
+to
+<em>
+null
+</em>
+in
+expanded
+form,
+then
+the
+entire
+JSON
+object
+is
+ignored.
+If
+<code>
+@context
+</code>
+is
+set
+to
+<em>
+null
+</em>,
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+is
+reset
+and
+when
+used
+within
+a
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>,
+it
+removes
+any
+definition
+associated
+with
+the
+key,
+unless
+otherwise
+specified.
+</p>
+</div>
+</div>
+<div id="from-json-to-json-ld" class="section">
+<h4>
+<span class="secno">
+3.1.3
+</span>
+From
+JSON
+to
+JSON-LD
+</h4>
+<p>
+If
+a
+set
+of
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s
+such
+as,
+<strong>
+name
+</strong>,
+<strong>
+homepage
+</strong>,
+and
+<strong>
+depiction
+</strong>,
+are
+defined
+in
+a
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>,
+and
+that
+context
+is
+used
+to
+resolve
+the
+names
+in
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+objects
+</a>,
+machines
+are
+able
+to
+automatically
+expand
+the
+terms
+to
+something
+meaningful
+and
+unambiguous,
+like
+this:
+</p>
+<div class="example"><div class="example-title"><span>Example 6</span></div><pre class="example">{
+  &quot;<span class="diff">http://xmlns.com/foaf/0.1/name</span>&quot;: &quot;Manu Sporny&quot;,
+  &quot;<span class="diff">http://xmlns.com/foaf/0.1/homepage</span>&quot;: &quot;http://manu.sporny.org&quot;
+  &quot;<span class="diff">http://xmlns.com/foaf/0.1/depiction</span>&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
+}
+</pre>
+</div>
+<p>
+Doing
+this
+allows
+JSON
+to
+be
+unambiguously
+machine-readable
+without
+requiring
+developers
+to
+drastically
+change
+their
+workflow.
+</p>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+The
+example
+above
+does
+not
+use
+the
+<code>
+@id
+</code>
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>
+to
+set
+the
+<a class="tref internalDFN" title="subject" href="#dfn-subject">
+subject
+</a>
+of
+the
+node
+being
+described
+above.
+This
+type
+of
+node
+is
+called
+an
+<a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">
+unlabeled
+node
+</a>.
+It
+is
+advised
+that
+all
+nodes
+described
+in
+JSON-LD
+are
+given
+unique
+identifiers
+via
+the
+<code>
+@id
+</code>
+keyword
+unless
+the
+data
+is
+not
+intended
+to
+be
+linked
+to
+from
+other
+data
+sets.
+</p>
+</div>
+<p>
+A
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+used
+to
+define
+property
+values
+is
+called
+a
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>.
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+Subject
+definitions
+</a>
+do
+not
+require
+an
+<code>
+@id
+</code>.
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+Subject
+definitions
+</a>
+that
+do
+not
+contain
+an
+<code>
+@id
+</code>
+are
+known
+as
+an
+<a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">
+unlabeled
+nodes
+</a>.
+</p>
+</div>
+</div>
+<div id="iris" class="section">
+<h3>
+<span class="secno">
+3.2
+</span>
+IRIs
+</h3>
+<p>
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+s
+are
+fundamental
+to
+<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
+Linked
+Data
+</a>
+as
+that
+is
+how
+most
+<a class="tref internalDFN" title="subject" href="#dfn-subject">
+subject
+</a>
+s,
+all
+<a class="tref internalDFN" title="property" href="#dfn-property">
+properties
+</a>
+and
+many
+<a class="tref internalDFN" title="object" href="#dfn-object">
+object
+</a>
+s
+are
+identified.
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+s
+can
+be
+expressed
+in
+a
+variety
+of
+different
+ways
+in
+JSON-LD.
+</p>
+<ol>
+<li>
+Except
+within
+a
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+definition,
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s
+in
+the
+key
+position
+in
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+that
+have
+a
+mapping
+to
+an
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+or
+another
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+in
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+are
+expanded
+to
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+by
+JSON-LD
+processors.
+</li>
+<li>
+An
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+is
+generated
+for
+the
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>
+value
+specified
+using
+<code>
+@id
+</code>
+or
+<code>
+@type
+</code>.
+</li>
+<li>
+An
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+is
+generated
+for
+the
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>
+value
+of
+any
+key
+for
+which
+there
+are
+<a class="tref internalDFN" title="coercion" href="#dfn-coercion">
+coercion
+</a>
+rules
+in
+effect
+that
+identify
+the
+value
+as
+an
+<code>
+@id
+</code>.
+</li>
+</ol>
+<p>
+IRIs
+may
+be
+represented
+as
+an
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+a
+<a class="tref internalDFN" title="relative_iri" href="#dfn-relative_iri">
+relative
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>,
+or
+a
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+</p>
+<p>
+An
+<dfn title="absolute_iri" id="dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</dfn>
+is
+defined
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RFC3987">
+RFC3987
+</a>
+</cite>
+]
+containing
+a
+<em>
+scheme
+</em>
+along
+with
+<em>
+path
+</em>
+and
+optional
+<em>
+query
+</em>
+and
+<em>
+fragment
+</em>
+segments.
+A
+<dfn title="relative_iri" id="dfn-relative_iri">
+relative
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</dfn>
+is
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+that
+is
+relative
+to
+some
+other
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+In
+JSON-LD
+all
+<a class="tref internalDFN" title="relative_iri" href="#dfn-relative_iri">
+relative
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+s
+are
+resolved
+relative
+to
+the
+<dfn title="base_iri" id="dfn-base_iri">
+base
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</dfn>
+associated
+with
+the
+document
+(typically,
+the
+directory
+that
+contains
+the
+document
+or
+the
+document
+itself).
+</p>
+<p>
+IRIs
+can
+be
+expressed
+directly
+in
+the
+key
+position
+like
+so:
+</p>
+<div class="example"><div class="example-title"><span>Example 7</span></div><pre class="example">{
+...
+  &quot;<span class="diff">http://xmlns.com/foaf/0.1/name</span>&quot;: &quot;Manu Sporny&quot;,
+...
+}
+</pre>
+</div>
+<p>
+In
+the
+example
+above,
+the
+key
+<code>
+http://xmlns.com/foaf/0.1/name
+</code>
+is
+interpreted
+as
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+because
+it
+contains
+a
+colon
+(
+<code>:
+</code>
+)
+and
+the
+'http'
+<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
+prefix
+</a>
+does
+not
+exist
+in
+the
+context.
+</p>
+<p>
+Term
+expansion
+occurs
+for
+IRIs
+if
+the
+value
+matches
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+defined
+within
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>:
+</p>
+<div class="example"><div class="example-title"><span>Example 8</span></div><pre class="example">{
+  &quot;<span class="diff">@context</span>&quot;:
+  {
+    &quot;<span class="diff">name</span>&quot;: &quot;<span class="diff">http://xmlns.com/foaf/0.1/name</span>&quot;
+...
+  },
+  &quot;<span class="diff">name</span>&quot;: &quot;Manu Sporny&quot;,
+  &quot;status&quot;: &quot;trollin'&quot;,
+...
+}
+</pre>
+</div>
+<p>
+<a class="tref internalDFN" title="term" href="#dfn-term">
+Term
+</a>
+s
+are
+case
+sensitive,
+and
+<em class="rfc2119" title="must">
+must
+</em>
+be
+matched
+using
+a
+case-sensitive
+comparison.
+</p>
+<p>
+JSON
+keys
+that
+do
+not
+expand
+to
+an
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+are
+ignored,
+or
+removed
+in
+some
+cases,
+by
+the
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-JSON-LD-API">
+JSON-LD-API
+</a>
+</cite>
+].
+However,
+JSON
+keys
+that
+do
+not
+include
+a
+mapping
+in
+the
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+are
+still
+considered
+valid
+expressions
+in
+JSON-LD
+documents
+-
+the
+keys
+just
+don't
+have
+any
+machine-readable,
+semantic
+meaning.
+</p>
+<p>
+<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
+Prefix
+</a>
+es
+are
+expanded
+when
+the
+form
+of
+the
+value
+is
+a
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+represented
+as
+a
+<code>
+prefix:suffix
+</code>
+combination,
+and
+the
+prefix
+matches
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+defined
+within
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>:
+</p>
+<div class="example"><div class="example-title"><span>Example 9</span></div><pre class="example">{
+  &quot;<span class="diff">@context</span>&quot;:
+  {
+    &quot;<span class="diff">foaf</span>&quot;: &quot;<span class="diff">http://xmlns.com/foaf/0.1/</span>&quot;
+...
+  },
+  &quot;<span class="diff">foaf:name</span>&quot;: &quot;Manu Sporny&quot;,
+...
+}
+</pre>
+</div>
+<p>
+<code>
+foaf:name
+</code>
+above
+will
+automatically
+expand
+out
+to
+the
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+<code>
+http://xmlns.com/foaf/0.1/name
+</code>.
+See
+<a href="#compact-iris">
+Compact
+IRIs
+</a>
+for
+more
+details.
+</p>
+<p>
+An
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+is
+generated
+when
+a
+JSON
+object
+is
+used
+in
+the
+value
+position
+that
+contains
+an
+<code>
+@id
+</code>
+keyword:
+</p>
+<div class="example"><div class="example-title"><span>Example 10</span></div><pre class="example">{
+...
+  &quot;homepage&quot;: { &quot;<span class="diff">@id</span>&quot;: &quot;http://manu.sporny.org&quot; }
+...
+}
+</pre>
+</div>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+Specifying
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+with
+an
+<code>
+@id
+</code>
+key
+is
+used
+to
+identify
+that
+object
+using
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+When
+the
+object
+has
+only
+the
+<code>
+@id
+</code>,
+it
+is
+called
+a
+<a class="tref internalDFN" title="subject_reference" href="#dfn-subject_reference">
+subject
+reference
+</a>.
+This
+facility
+<em class="rfc2119" title="may">
+may
+</em>
+also
+be
+used
+to
+link
+to
+another
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>
+using
+a
+mechanism
+called
+<a class="tref internalDFN" title="embedding" href="#dfn-embedding">
+embedding
+</a>,
+which
+is
+covered
+in
+the
+section
+titled
+<a href="#embedding">
+Embedding
+</a>.
+</p>
+</div>
+<p>
+If
+type
+<a class="tref internalDFN" title="coercion" href="#dfn-coercion">
+coercion
+</a>
+rules
+are
+specified
+in
+the
+<code>
+@context
+</code>
+for
+a
+particular
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+or
+property
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>,
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+is
+generated:
+</p>
+<div class="example"><div class="example-title"><span>Example 11</span></div><pre class="example">{<span class="diff">
+  &quot;@context&quot;:
+  {
+    ...
+    &quot;homepage&quot;:
+    {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    }
+    ...
+  }</span>
+...
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
+...
+}
+</pre>
+</div>
+<p>
+In
+the
+example
+above,
+even
+though
+the
+value
+<code>
+http://manu.sporny.org/
+</code>
+is
+expressed
+as
+a
+JSON
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>,
+the
+type
+<a class="tref internalDFN" title="coercion" href="#dfn-coercion">
+coercion
+</a>
+rules
+will
+transform
+the
+value
+into
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+when
+processed
+by
+a
+JSON-LD
+Processor.
+</p>
+</div>
+<div id="identifying-the-subject" class="section">
+<h3>
+<span class="secno">
+3.3
+</span>
+Identifying
+the
+Subject
+</h3>
+<p>
+To
+be
+able
+to
+externally
+reference
+nodes
+in
+a
+graph,
+it
+is
+important
+that
+each
+node
+has
+an
+unambiguous
+identifier.
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+s
+are
+a
+fundamental
+concept
+of
+<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
+Linked
+Data
+</a>,
+and
+nodes
+should
+have
+a
+de-referencable
+identifier
+used
+to
+name
+and
+locate
+them.
+For
+nodes
+to
+be
+truly
+linked,
+de-referencing
+the
+identifier
+should
+result
+in
+a
+representation
+of
+that
+node
+(for
+example,
+using
+a
+URL
+to
+retrieve
+a
+web
+page).
+Associating
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+with
+a
+node
+tells
+an
+application
+that
+the
+returned
+document
+contains
+a
+description
+of
+the
+node
+requested.
+</p>
+<p>
+JSON-LD
+documents
+may
+also
+contain
+descriptions
+of
+other
+nodes,
+so
+it
+is
+necessary
+to
+be
+able
+to
+uniquely
+identify
+each
+node
+which
+may
+be
+externally
+referenced.
+</p>
+<p>
+A
+<a class="tref internalDFN" title="subject" href="#dfn-subject">
+subject
+</a>
+of
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+is
+a
+node
+identified
+using
+the
+<code>
+@id
+</code>
+key.
+The
+subject
+is
+the
+first
+piece
+of
+information
+needed
+by
+the
+JSON-LD
+processor
+in
+order
+to
+create
+the
+(subject,
+property,
+object)
+tuple,
+also
+known
+as
+a
+triple.
+</p>
+<div class="example"><div class="example-title"><span>Example 12</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    ...
+    &quot;homepage&quot;:
+    {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    }
+    ...
+  },
+  &quot;<span class="diff">@id</span>&quot;: &quot;<span class="diff">http://example.org/people#joebob</span>&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
+...
+}
+</pre>
+</div>
+<p>
+The
+example
+above
+would
+set
+the
+subject
+to
+the
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+<code>
+http://example.org/people#joebob
+</code>.
+</p>
+<p>
+A
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+used
+to
+define
+property
+values
+is
+called
+a
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>.
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+Subject
+definitions
+</a>
+do
+not
+require
+an
+<code>
+@id
+</code>.
+A
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>
+that
+does
+not
+contain
+an
+<code>
+@id
+</code>
+property
+defines
+properties
+of
+an
+<a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">
+unlabeled
+node
+</a>.
+</p>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+To
+ensure
+the
+best
+possible
+performance,
+when
+possible,
+it
+is
+a
+best
+practice
+to
+put
+JSON-LD
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>
+s,
+such
+as
+<code>
+@id
+</code>
+and
+<code>
+@context
+</code>
+before
+other
+key-value
+pairs
+in
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>.
+However,
+keys
+in
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+are
+not
+ordered,
+so
+processors
+<em class="rfc2119" title="must not">
+must
+not
+</em>
+depend
+on
+key
+ordering.
+If
+keywords
+are
+not
+listed
+first,
+processors
+have
+to
+save
+each
+key-value
+pair
+until
+at
+least
+the
+<code>
+@context
+</code>
+and
+the
+<code>
+@id
+</code>
+are
+processed.
+Not
+specifying
+those
+keywords
+first
+creates
+a
+memory
+and
+complexity
+burden
+for
+low-memory
+footprint
+processors,
+forcing
+them
+to
+use
+more
+memory
+and
+computing
+cycles
+than
+necessary.
+</p>
+</div>
+</div>
+<div id="specifying-the-type" class="section">
+<h3>
+<span class="secno">
+3.4
+</span>
+Specifying
+the
+Type
+</h3>
+<p>
+The
+type
+of
+a
+particular
+subject
+can
+be
+specified
+using
+the
+<code>
+@type
+</code>
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>.
+Specifying
+the
+type
+in
+this
+way
+will
+generate
+a
+triple
+of
+the
+form
+(subject,
+type,
+type-
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+).
+To
+be
+considered
+<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
+Linked
+Data
+</a>,
+types
+<em class="rfc2119" title="must">
+must
+</em>
+be
+uniquely
+identified
+by
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+</p>
+<div class="example"><div class="example-title"><span>Example 13</span></div><pre class="example">{
+...
+  &quot;@id&quot;: &quot;http://example.org/people#joebob&quot;,
+  &quot;<span class="diff">@type</span>&quot;: &quot;<span class="diff">http://xmlns.com/foaf/0.1/Person</span>&quot;,
+...
+}
+</pre>
+</div>
+</div>
+<div id="string-internationalization" class="section">
+<h3>
+<span class="secno">
+3.5
+</span>
+String
+Internationalization
+</h3>
+<p>
+At
+times,
+it
+is
+important
+to
+annotate
+a
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>
+with
+its
+language.
+In
+JSON-LD
+this
+is
+possible
+in
+a
+variety
+of
+ways.
+Firstly,
+it
+is
+possible
+to
+define
+a
+default
+language
+for
+a
+JSON-LD
+document
+by
+setting
+the
+<code>
+@language
+</code>
+key
+in
+the
+<code>
+@context
+</code>
+or
+in
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+definition:
+</p>
+<div class="example"><div class="example-title"><span>Example 14</span></div><pre class="example">{
+  <span class="diff">&quot;@context&quot;:
+  {
+    ...
+    &quot;@language&quot;: &quot;ja&quot;
+  },</span>
+  &quot;name&quot;: <span class="diff">&quot;花澄&quot;</span>,
+  &quot;occupation&quot;: <span class="diff">&quot;科学者&quot;</span>
+}
+</pre>
+</div>
+<p>
+The
+example
+above
+would
+associate
+the
+<code>
+ja
+</code>
+language
+code
+with
+the
+two
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>
+s
+<em>
+花澄
+</em>
+and
+<em>
+科学者
+</em>.
+Languages
+<em class="rfc2119" title="must">
+must
+</em>
+be
+well-formed
+language
+tags
+according
+to
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-BCP47">
+BCP47
+</a>
+</cite>
+].
+</p>
+<p>
+It
+is
+possible
+to
+override
+the
+default
+language
+by
+using
+the
+expanded
+form
+of
+a
+value:
+</p>
+<div class="example"><div class="example-title"><span>Example 15</span></div><pre class="example">{
+  &quot;@context&quot;: {
+    ...
+    &quot;@language&quot;: &quot;ja&quot;
+  },
+  &quot;name&quot;: &quot;花澄&quot;,
+  &quot;occupation&quot;: <span class="diff">{
+    &quot;@value&quot;: &quot;Scientist&quot;,
+    &quot;@language&quot;: &quot;en&quot;
+  }</span>
+}
+</pre>
+</div>
+<p>
+It
+is
+also
+possible
+to
+override
+the
+default
+language
+or
+specify
+a
+plain
+value
+by
+omitting
+the
+<code>
+@language
+</code>
+tag
+or
+setting
+it
+to
+<code>
+null
+</code>
+when
+expressing
+the
+expanded
+value:
+</p>
+<div class="example"><div class="example-title"><span>Example 16</span></div><pre class="example">{
+  &quot;@context&quot;: {
+    ...
+    &quot;@language&quot;: &quot;ja&quot;
+  },
+  &quot;name&quot;: <span class="diff">{
+    &quot;@value&quot;: &quot;Frank&quot;
+  },</span>
+  &quot;occupation&quot;: <span class="diff"> {
+    &quot;@value&quot;: &quot;Ninja&quot;,
+    &quot;@language&quot;: &quot;en&quot;
+  }</span>,
+  &quot;speciality&quot;: &quot;手裏剣&quot;
+}
+</pre>
+</div>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+Please
+note
+that
+language
+associations
+<em class="rfc2119" title="must">
+must
+</em>
+only
+be
+applied
+to
+plain
+literal
+<a class="tref internalDFN" title="string" href="#dfn-string">
+string
+</a>
+s.
+That
+is,
+<a class="tref internalDFN" title="typed_value" href="#dfn-typed_value">
+typed
+value
+</a>
+s
+or
+values
+that
+are
+subject
+to
+<a href="#type-coercion">
+type
+coercion
+</a>
+won't
+be
+language
+tagged.
+</p>
+</div>
+<p>
+To
+clear
+the
+default
+language
+for
+a
+subtree,
+<code>
+@language
+</code>
+can
+be
+set
+to
+<code>
+null
+</code>
+in
+a
+<a class="tref internalDFN" title="local_context" href="#dfn-local_context">
+local
+context
+</a>
+as
+follows:
+</p>
+<div class="example"><div class="example-title"><span>Example 17</span></div><pre class="example">{
+  &quot;@context&quot;: {
+    ...
+    &quot;@language&quot;: &quot;ja&quot;
+  },
+  &quot;name&quot;: &quot;花澄&quot;,
+  &quot;details&quot;: {
+<span class="diff">    &quot;@context&quot;: {
+      &quot;@language&quot;: null
+    },</span>
+    &quot;occupation&quot;: &quot;Ninja&quot;
+  }
+}
+</pre>
+</div>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+JSON-LD
+allows
+one
+to
+associate
+language
+information
+with
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s.
+See
+<a href="#expanded-term-definition">
+Expanded
+Term
+Definition
+</a>
+for
+more
+details.
+</p>
+</div>
+</div>
+<div id="json-ld-syntax" class="section">
+<h3>
+<span class="secno">
+3.6
+</span>
+JSON-LD
+Syntax
+</h3>
+<p>
+A
+JSON-LD
+document
+is
+first,
+and
+foremost,
+a
+JSON
+document
+(as
+defined
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RFC5988">
+RFC5988
+</a>
+</cite>
+]),
+and
+any
+syntactically
+correct
+JSON
+document
+<em class="rfc2119" title="must">
+must
+</em>
+be
+processed
+by
+a
+conforming
+JSON-LD
+processor.
+However,
+JSON-LD
+describes
+a
+specific
+syntax
+to
+use
+for
+expressing
+Linked
+Data.
+This
+includes
+the
+use
+of
+specific
+keywords,
+as
+identified
+in
+<a href="#syntax-tokens-and-keywords">
+Syntax
+Tokens
+and
+Keywords
+</a>
+for
+expressing
+<a title="subject definition">
+subject
+definitions
+</a>,
+values,
+and
+the
+<a href="#dfn-context" class="internalDFN">
+context
+</a>.
+See
+<a href="#json-ld-authoring-guidelines">
+Appendix
+A
+</a>
+for
+authoring
+guidelines
+and
+a
+BNF
+description
+of
+JSON-LD.
+</p>
+</div>
+</div>
+<div id="advanced-concepts" class="section">
+<h2>
+<span class="secno">
+4.
+</span>
+Advanced
+Concepts
+</h2>
+<em>
+This
+section
+is
+normative.
+</em>
+<p>
+JSON-LD
+has
+a
+number
+of
+features
+that
+provide
+functionality
+above
+and
+beyond
+the
+core
+functionality
+described
+above.
+The
+following
+section
+describes
+this
+advanced
+functionality
+in
+more
+detail.
+</p>
+<div id="compact-iris" class="section">
+<h3>
+<span class="secno">
+4.1
+</span>
+Compact
+IRIs
+</h3>
+<p>
+<a class="tref internalDFN" title="term" href="#dfn-term">
+Term
+</a>
+s
+in
+<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
+Linked
+Data
+</a>
+documents
+may
+draw
+from
+a
+number
+of
+different
+<a class="tref internalDFN" title="vocabulary" href="#dfn-vocabulary">
+vocabularies
+</a>.
+At
+times,
+declaring
+every
+single
+term
+that
+a
+document
+uses
+can
+require
+the
+developer
+to
+declare
+tens,
+if
+not
+hundreds
+of
+potential
+<a class="tref internalDFN" title="vocabulary" href="#dfn-vocabulary">
+vocabulary
+</a>
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s
+that
+are
+used
+across
+an
+application.
+This
+is
+a
+concern
+for
+at
+least
+two
+reasons:
+the
+first
+is
+the
+cognitive
+load
+on
+the
+developer
+of
+remembering
+all
+of
+the
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s,
+and
+the
+second
+is
+the
+serialized
+size
+of
+the
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+if
+it
+is
+specified
+inline.
+In
+order
+to
+address
+these
+issues,
+the
+concept
+of
+a
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+is
+introduced.
+</p>
+<p>
+A
+<dfn title="compact_iri" id="dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</dfn>
+is
+a
+way
+of
+expressing
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+using
+a
+<em>
+prefix
+</em>
+and
+<em>
+suffix
+</em>
+separated
+by
+a
+colon
+(
+<code>:
+</code>
+)
+which
+is
+similar
+to
+the
+<cite>
+<a href="http://www.w3.org/TR/rdfa-core/#s_curies">
+CURIE
+Syntax
+</a>
+</cite>
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">
+RDFA-CORE
+</a>
+</cite>
+].
+The
+<dfn title="prefix" id="dfn-prefix">
+prefix
+</dfn>
+is
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+taken
+from
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+and
+is
+a
+short
+string
+identifying
+a
+particular
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+in
+a
+JSON-LD
+document.
+For
+example,
+the
+prefix
+<code>
+foaf
+</code>
+may
+be
+used
+as
+a
+short
+hand
+for
+the
+Friend-of-a-Friend
+vocabulary,
+which
+is
+identified
+using
+the
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+<code>
+http://xmlns.com/foaf/0.1/
+</code>.
+A
+developer
+may
+append
+any
+of
+the
+FOAF
+<a class="tref internalDFN" title="vocabulary" href="#dfn-vocabulary">
+vocabulary
+</a>
+terms
+to
+the
+end
+of
+the
+prefix
+to
+specify
+a
+short-hand
+version
+of
+the
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+for
+the
+<a class="tref internalDFN" title="vocabulary" href="#dfn-vocabulary">
+vocabulary
+</a>
+term.
+For
+example,
+<code>
+foaf:name
+</code>
+would
+be
+expanded
+out
+to
+the
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+<code>
+http://xmlns.com/foaf/0.1/name
+</code>.
+Instead
+of
+having
+to
+remember
+and
+type
+out
+the
+entire
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>,
+the
+developer
+can
+instead
+use
+the
+prefix
+in
+their
+JSON-LD
+markup.
+</p>
+<p>
+Terms
+are
+interpreted
+as
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+s
+if
+they
+contain
+at
+least
+one
+colon
+and
+the
+first
+colon
+is
+not
+followed
+by
+two
+slashes
+(
+<code>
+//
+</code>,
+as
+in
+<code>
+http://example.com
+</code>
+).
+To
+generate
+the
+full
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+the
+value
+is
+first
+split
+into
+a
+<em>
+prefix
+</em>
+and
+<em>
+suffix
+</em>
+at
+the
+first
+occurrence
+of
+a
+colon
+(
+<code>:
+</code>
+).
+If
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>
+contains
+a
+term
+mapping
+for
+<em>
+prefix
+</em>,
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+is
+generated
+by
+prepending
+the
+mapped
+<em>
+prefix
+</em>
+to
+the
+(possibly
+empty)
+<em>
+suffix
+</em>
+using
+textual
+concatenation.
+If
+no
+prefix
+mapping
+is
+defined,
+the
+value
+is
+interpreted
+as
+an
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+If
+the
+prefix
+is
+an
+underscore
+(
+<code>
+_
+</code>
+),
+the
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+remains
+unchanged.
+This
+effectively
+means
+that
+every
+term
+containing
+a
+colon
+will
+be
+interpreted
+by
+a
+JSON-LD
+processor
+as
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>.
+</p>
+<p>
+Consider
+the
+following
+example:
+</p>
+  <div class="example"><div class="example-title"><span>Example 18</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    <span class="diff">&quot;dc&quot;: &quot;http://purl.org/dc/elements/1.1/&quot;,</span>
+    <span class="diff">&quot;ex&quot;: &quot;http://example.org/vocab#&quot;</span>
+  },
+  &quot;@id&quot;: &quot;http://example.org/library&quot;,
+  &quot;@type&quot;: <span class="diff">&quot;ex:Library&quot;</span>,
+  <span class="diff">&quot;ex:contains&quot;</span>:
+  {
+    &quot;@id&quot;: &quot;http://example.org/library/the-republic&quot;,
+    &quot;@type&quot;: <span class="diff">&quot;ex:Book&quot;</span>,
+    <span class="diff">&quot;dc:creator&quot;</span>: &quot;Plato&quot;,
+    <span class="diff">&quot;dc:title&quot;</span>: &quot;The Republic&quot;,
+    <span class="diff">&quot;ex:contains&quot;</span>:
+    {
+      &quot;@id&quot;: &quot;http://example.org/library/the-republic#introduction&quot;,
+      &quot;@type&quot;: <span class="diff">&quot;ex:Chapter&quot;</span>,
+      <span class="diff">&quot;dc:description&quot;</span>: &quot;An introductory chapter on The Republic.&quot;,
+      <span class="diff">&quot;dc:title&quot;</span>: &quot;The Introduction&quot;
+    }
+  }
+}
+</pre>
+</div>
+<p>
+In
+this
+example,
+two
+different
+<a class="tref internalDFN" title="vocabulary" href="#dfn-vocabulary">
+vocabularies
+</a>
+are
+referred
+to
+using
+prefixes.
+Those
+prefixes
+are
+then
+used
+as
+type
+and
+property
+values
+using
+the
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+<code>
+prefix:suffix
+</code>
+notation.
+</p>
+<p>
+It's
+also
+possible
+to
+use
+compact
+IRIs
+within
+the
+context
+as
+shown
+in
+the
+following
+example:
+</p>
+  <div class="example"><div class="example-title"><span>Example 19</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;,
+    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;,
+    <span class="diff">&quot;foaf:homepage&quot;</span>: { &quot;@type&quot;: &quot;@id&quot; },
+    &quot;picture&quot;: { &quot;@id&quot;: <span class="diff">&quot;foaf:depiction&quot;</span>, &quot;@type&quot;: &quot;@id&quot; }
+  },
+  &quot;@id&quot;: &quot;http://me.markus-lanthaler.com/&quot;,
+  &quot;@type&quot;: &quot;foaf:Person&quot;,
+  &quot;foaf:name&quot;: &quot;Markus Lanthaler&quot;,
+  &quot;foaf:homepage&quot;: &quot;http://www.markus-lanthaler.com/&quot;,
+  &quot;picture&quot;: &quot;http://twitter.com/account/profile_image/markuslanthaler&quot;
+}
+</pre>
+</div>
+</div>
+<div id="typed-values" class="section">
+<h3>
+<span class="secno">
+4.2
+</span>
+Typed
+Values
+</h3>
+<p>
+A
+value
+with
+an
+associated
+type,
+also
+known
+as
+a
+<dfn title="typed_value" id="dfn-typed_value">
+typed
+value
+</dfn>,
+is
+indicated
+by
+associating
+a
+value
+with
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+which
+indicates
+the
+value's
+type.
+Typed
+values
+may
+be
+expressed
+in
+JSON-LD
+in
+two
+ways:
+</p>
+<ol>
+<li>
+By
+utilizing
+the
+<code>
+@type
+</code>
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>
+when
+defining
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+within
+a
+<code>
+@context
+</code>
+section.
+</li>
+<li>
+By
+utilizing
+the
+expanded
+form
+for
+specifying
+objects.
+</li>
+</ol>
+<p>
+The
+first
+example
+uses
+the
+<code>
+@type
+</code>
+keyword
+to
+associate
+a
+type
+with
+a
+particular
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+in
+the
+<code>
+@context
+</code>:
+</p>
+<div class="example"><div class="example-title"><span>Example 20</span></div><pre class="example">{
+  <span class="diff">&quot;@context&quot;:
+  {
+    &quot;modified&quot;:
+    {
+      &quot;@id&quot;: &quot;http://purl.org/dc/terms/modified&quot;,
+      &quot;@type&quot;: &quot;http://www.w3.org/2001/XMLSchema#dateTime&quot;
+    }
+  },</span>
+...
+  &quot;modified&quot;: &quot;2010-05-29T14:17:39+02:00&quot;,
+...
+}
+</pre>
+</div>
+<p>
+The
+<em>
+modified
+</em>
+key's
+value
+above
+is
+automatically
+type
+coerced
+to
+a
+datetime
+value
+because
+of
+the
+information
+specified
+in
+the
+<code>
+@context
+</code>.
+</p>
+<p>
+The
+second
+example
+uses
+the
+expanded
+form
+of
+setting
+the
+type
+information
+in
+the
+body
+of
+a
+JSON-LD
+document:
+</p>
+<div class="example"><div class="example-title"><span>Example 21</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;modified&quot;:
+    {
+      &quot;@id&quot;: &quot;http://purl.org/dc/terms/modified&quot;
+    }
+  },
+...
+  &quot;modified&quot;:
+  <span class="diff">{
+    &quot;@value&quot;: &quot;2010-05-29T14:17:39+02:00&quot;,
+    &quot;@type&quot;: &quot;http://www.w3.org/2001/XMLSchema#dateTime&quot;
+  }</span>
+...
+}
+</pre>
+</div>
+<p>
+Both
+examples
+above
+would
+generate
+an
+object
+with
+the
+value
+of
+<code>
+2010-05-29T14:17:39+02:00
+</code>
+and
+the
+type
+of
+<code>
+http://www.w3.org/2001/XMLSchema#dateTime
+</code>.
+Note
+that
+it
+is
+also
+possible
+to
+use
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+or
+a
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+to
+express
+the
+value
+of
+a
+type.
+</p>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+The
+<code>
+@type
+</code>
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>
+is
+also
+used
+to
+associate
+a
+type
+with
+a
+<a class="tref internalDFN" title="subject" href="#dfn-subject">
+subject
+</a>.
+Although
+the
+same
+keyword
+is
+used
+in
+both
+places,
+the
+concept
+of
+an
+<em>
+object
+type
+</em>
+and
+a
+<em>
+value
+type
+</em>
+are
+different.
+This
+is
+similar
+to
+object-oriented
+programming
+languages
+where
+both
+scalar
+and
+structured
+types
+use
+the
+same
+class
+inheritance
+mechanism,
+even
+though
+scalar
+types
+and
+structured
+types
+are
+inherently
+different.
+</p>
+</div>
+</div>
+<div id="external-contexts" class="section">
+<h3>
+<span class="secno">
+4.3
+</span>
+External
+Contexts
+</h3>
+<p>
+Authors
+may
+choose
+to
+declare
+JSON-LD
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+s
+in
+external
+documents
+to
+promote
+re-use
+of
+contexts
+as
+well
+as
+reduce
+the
+size
+of
+JSON-LD
+documents.
+</p>
+<p>
+In
+order
+to
+use
+an
+external
+context,
+an
+author
+<em class="rfc2119" title="must">
+must
+</em>
+specify
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+to
+a
+valid
+JSON-LD
+document.
+The
+referenced
+document
+<em class="rfc2119" title="must">
+must
+</em>
+have
+a
+top-level
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>.
+The
+value
+of
+any
+<code>
+@context
+</code>
+key
+within
+that
+object
+is
+substituted
+for
+the
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+within
+the
+referencing
+document
+to
+have
+the
+same
+effect
+as
+if
+the
+value
+were
+specified
+inline
+within
+the
+referencing
+document.
+</p>
+<p>
+The
+following
+example
+demonstrates
+the
+use
+of
+an
+external
+context:
+</p>
+<div class="example"><div class="example-title"><span>Example 22</span></div><pre class="example">{
+  <span class="diff">&quot;@context&quot;: &quot;http://json-ld.org/contexts/person.jsonld&quot;</span>,
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
+  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
+}
+</pre>
+</div>
+<p>
+Authors
+may
+also
+import
+multiple
+contexts
+or
+a
+combination
+of
+external
+and
+local
+contexts
+by
+specifying
+a
+list
+of
+contexts:
+</p>
+<div class="example"><div class="example-title"><span>Example 23</span></div><pre class="example">{
+  <span class="diff">&quot;@context&quot;:
+  [
+    &quot;http://json-ld.org/contexts/person.jsonld&quot;,
+    {
+      &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;
+    },
+    &quot;http://json-ld.org/contexts/event.jsonld&quot;
+  ],</span>
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
+  &quot;foaf:depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;,
+  <span class="diff">&quot;celebrates&quot;:
+  {
+    &quot;@type&quot;: &quot;Event&quot;,
+    &quot;description&quot;: &quot;International Talk Like a Pirate Day&quot;,
+    &quot;date&quot;: &quot;R/2011-09-19&quot;
+  }</span>
+}
+</pre>
+</div>
+<p>
+Each
+context
+in
+a
+list
+will
+be
+evaluated
+in-order.
+Duplicate
+mappings
+among
+the
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+s
+<em class="rfc2119" title="must">
+must
+</em>
+be
+overwritten
+on
+a
+last-defined-overrides
+basis.
+The
+context
+list
+<em class="rfc2119" title="must">
+must
+</em>
+contain
+either
+de-referenceable
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+s
+or
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+s
+that
+conform
+to
+the
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+syntax
+as
+described
+in
+this
+document.
+</p>
+<p>
+An
+author
+<em class="rfc2119" title="may">
+may
+</em>
+nest
+contexts
+within
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definitions
+</a>,
+with
+the
+more
+deeply
+nested
+contexts
+overriding
+the
+values
+in
+previously
+defined
+contexts:
+</p>
+<div class="example"><div class="example-title"><span>Example 24</span></div><pre class="example">{
+  <span class="diff">&quot;@context&quot;:
+  {
+    &quot;name&quot;: &quot;http://example.com/person#name&quot;,
+    &quot;details&quot;: &quot;http://example.com/person#details&quot;
+  },</span>
+  &quot;<span class="diff">name</span>&quot;: &quot;Markus Lanthaler&quot;,
+  ...
+  &quot;details&quot;:
+  {
+    <span class="diff">&quot;@context&quot;: {
+      &quot;name&quot;: &quot;http://example.com/organization#name&quot;
+    },</span>
+    &quot;<span class="diff">name</span>&quot;: &quot;Graz University of Technology&quot;
+  }
+}
+</pre>
+</div>
+<p>
+In
+the
+example
+above,
+the
+<code>
+name
+</code>
+prefix
+is
+overridden
+in
+the
+more
+deeply
+nested
+<code>
+details
+</code>
+structure.
+Note
+that
+this
+is
+rarely
+a
+good
+authoring
+practice
+and
+is
+typically
+used
+when
+the
+JSON
+object
+has
+legacy
+applications
+using
+the
+structure
+of
+the
+object.
+</p>
+<p>
+External
+JSON-LD
+context
+documents
+<em class="rfc2119" title="may">
+may
+</em>
+contain
+extra
+information
+located
+outside
+of
+the
+<code>
+@context
+</code>
+key,
+such
+as
+documentation
+about
+the
+<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
+prefixes
+</a>
+declared
+in
+the
+document.
+When
+importing
+a
+<code>
+@context
+</code>
+value
+from
+an
+external
+JSON-LD
+context
+document,
+any
+extra
+information
+contained
+outside
+of
+the
+<code>
+@context
+</code>
+value
+<em class="rfc2119" title="must">
+must
+</em>
+be
+discarded.
+It
+is
+also
+<em class="rfc2119" title="recommended">
+recommended
+</em>
+that
+a
+human-readable
+document
+is
+served
+as
+well
+to
+explain
+the
+correct
+usage
+of
+the
+JSON-LD
+context
+document.
+</p>
+</div>
+<div id="referencing-contexts-from-json-documents" class="section">
+<h3>
+<span class="secno">
+4.4
+</span>
+Referencing
+Contexts
+from
+JSON
+Documents
+</h3>
+<p>
+Ordinary
+JSON
+documents
+can
+be
+transformed
+into
+JSON-LD
+documents
+by
+referencing
+to
+an
+external
+JSON-LD
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+in
+an
+HTTP
+Link
+Header.
+Doing
+this
+allows
+JSON
+to
+be
+unambiguously
+machine-readable
+without
+requiring
+developers
+to
+drastically
+change
+their
+workflow
+and
+provides
+an
+upgrade
+path
+for
+existing
+infrastructure
+without
+breaking
+existing
+clients
+that
+rely
+on
+the
+<code>
+application/json
+</code>
+media
+type.
+</p>
+<p>
+In
+order
+to
+use
+an
+external
+context
+with
+an
+ordinary
+JSON
+document,
+an
+author
+<em class="rfc2119" title="must">
+must
+</em>
+specify
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+to
+a
+valid
+JSON-LD
+document
+in
+an
+HTTP
+Link
+Header
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RFC5988">
+RFC5988
+</a>
+</cite>
+]
+using
+the
+<code>
+describedby
+</code>
+link
+relation.
+The
+referenced
+document
+<em class="rfc2119" title="must">
+must
+</em>
+have
+a
+top-level
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>.
+The
+<code>
+@context
+</code>
+subtree
+within
+that
+object
+is
+added
+to
+the
+top-level
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>
+of
+the
+referencing
+document.
+If
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>
+is
+at
+the
+top-level
+of
+the
+referencing
+document
+and
+its
+items
+are
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definitions
+</a>,
+the
+<code>
+@context
+</code>
+subtree
+is
+added
+to
+all
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>
+items.
+All
+extra
+information
+located
+outside
+of
+the
+<code>
+@context
+</code>
+subtree
+in
+the
+referenced
+document
+<em class="rfc2119" title="must">
+must
+</em>
+be
+discarded.
+</p>
+<p>
+The
+following
+example
+demonstrates
+the
+use
+of
+an
+external
+context
+with
+an
+ordinary
+JSON
+document:
+</p>
+<div class="example"><div class="example-title"><span>Example 25</span></div><pre class="example">GET /ordinary-json-document.json HTTP/1.1
+Host: example.com
+Accept: application/ld+json,application/json,*/*;q=0.1
+====================================
+HTTP/1.0 200 OK
+...
+Content-Type: <span class="diff">application/json</span>
+<span class="diff">Link: &lt;http://json-ld.org/contexts/person.jsonld&gt;; rel=&quot;describedby&quot;; type=&quot;application/ld+json&quot;</span>
+{
+  &quot;name&quot;: &quot;Markus Lanthaler&quot;,
+  &quot;homepage&quot;: &quot;http://www.markus-lanthaler.com/&quot;,
+  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/markuslanthaler&quot;
+}
+</pre>
+</div>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+JSON-LD
+documents
+served
+with
+the
+<code>
+application/ld+json
+</code>
+media
+type
+<em class="rfc2119" title="must">
+must
+</em>
+have
+all
+context
+information,
+including
+references
+to
+external
+contexts,
+within
+the
+body
+of
+the
+document.
+</p>
+</div>
+</div>
+<div id="expanded-term-definition" class="section">
+<h3>
+<span class="secno">
+4.5
+</span>
+Expanded
+Term
+Definition
+</h3>
+<p>
+Within
+a
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+definition,
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s
+<em class="rfc2119" title="may">
+may
+</em>
+be
+defined
+using
+an
+expanded
+notation
+to
+allow
+for
+additional
+information
+associated
+with
+the
+term
+to
+be
+specified
+(see
+also
+<a href="#type-coercion">
+Type
+Coercion
+</a>
+and
+<a href="#sets-and-lists">
+Sets
+and
+Lists
+</a>
+).
+</p>
+<p>
+Instead
+of
+using
+a
+string
+representation
+of
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>,
+the
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+<em class="rfc2119" title="may">
+may
+</em>
+be
+specified
+using
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+having
+an
+<code>
+@id
+</code>
+key.
+The
+value
+of
+the
+<code>
+@id
+</code>
+key
+<em class="rfc2119" title="must">
+must
+</em>
+be
+either
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>,
+a
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+or
+an
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+Such
+an
+object
+is
+called
+a
+<a class="tref internalDFN" title="subject_reference" href="#dfn-subject_reference">
+subject
+reference
+</a>.
+</p>
+<div class="example"><div class="example-title"><span>Example 26</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;foaf&quot;: <span class="diff">{ &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/&quot; }</span>,
+    &quot;name&quot;: <span class="diff">{ &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot; }</span>,
+    &quot;homepage&quot;: <span class="diff">{ &quot;@id&quot;: &quot;foaf:homepage&quot; }</span>,
+    &quot;depiction&quot;: <span class="diff">{ &quot;@id&quot;: &quot;foaf:depiction&quot; }</span>
+  },
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
+  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
+}
+</pre>
+</div>
+<p>
+This
+allows
+additional
+information
+to
+be
+associated
+with
+the
+term.
+This
+<em class="rfc2119" title="may">
+may
+</em>
+be
+used
+for
+<a href="#type-coercion">
+Type
+Coercion
+</a>,
+<a href="#sets-and-lists">
+Sets
+and
+Lists
+</a>
+),
+or
+to
+associate
+language
+information
+with
+a
+term
+as
+shown
+in
+the
+following
+example:
+</p>
+<div class="example"><div class="example-title"><span>Example 27</span></div><pre class="example">{
+  &quot;@context&quot;: {
+    ...
+    &quot;ex&quot;: &quot;http://example.com/&quot;,
+    &quot;@language&quot;: &quot;ja&quot;,
+    &quot;name&quot;: { &quot;@id&quot;: &quot;ex:name&quot;, <span class="diff">&quot;@language&quot;: null</span> },
+    &quot;occupation&quot;: { &quot;@id&quot;: &quot;ex:occupation&quot; },
+    &quot;occupation_en&quot;: { &quot;@id&quot;: &quot;ex:occupation&quot;, <span class="diff">&quot;@language&quot;: &quot;en&quot;</span> },
+    &quot;occupation_cs&quot;: { &quot;@id&quot;: &quot;ex:occupation&quot;, <span class="diff">&quot;@language&quot;: &quot;cs&quot;</span> }
+  },
+  <span class="diff">&quot;name&quot;: &quot;Yagyū Muneyoshi&quot;,
+  &quot;occupation&quot;: &quot;忍者&quot;,
+  &quot;occupation_en&quot;: &quot;Ninja&quot;,
+  &quot;occupation_cs&quot;: &quot;Nindža&quot;,</span>
+  ...
+}
+</pre>
+</div>
+<p>
+The
+example
+above
+would
+associate
+<em>
+忍者
+</em>
+with
+the
+specified
+default
+language
+code
+<code>
+ja
+</code>,
+<em>
+Ninja
+</em>
+with
+the
+language
+code
+<code>
+en
+</code>,
+and
+<em>
+Nindža
+</em>
+with
+the
+language
+code
+<code>
+cs
+</code>.
+The
+value
+of
+<code>
+name
+</code>,
+<em>
+Yagyū
+Muneyoshi
+</em>
+wouldn't
+be
+associated
+with
+any
+language
+code
+since
+<code>
+@language
+</code>
+was
+reset
+to
+<a class="tref internalDFN" title="null" href="#dfn-null">
+null
+</a>
+in
+the
+expanded
+term
+definition.
+</p>
+<p>
+Expanded
+terms
+<em class="rfc2119" title="may">
+may
+</em>
+also
+be
+defined
+using
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+IRIs
+</a>
+or
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+IRIs
+</a>
+as
+keys.
+If
+the
+definition
+does
+not
+include
+an
+<code>
+@id
+</code>
+key,
+the
+expanded
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+is
+determined
+by
+performing
+expansion
+of
+the
+key
+within
+the
+current
+active
+context.
+This
+mechanism
+is
+mainly
+used
+to
+associate
+type
+or
+language
+information
+with
+a
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+or
+an
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+</p>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+While
+it
+is
+possible
+to
+define
+a
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+or
+an
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+to
+expand
+to
+some
+other
+unrelated
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+(for
+example,
+<code>
+foaf:name
+</code>
+expanding
+to
+<code>
+http://example.org/unrelated#species
+</code>
+),
+such
+usage
+is
+strongly
+discouraged.
+</p>
+</div>
+</div>
+<div id="type-coercion" class="section">
+<h3>
+<span class="secno">
+4.6
+</span>
+Type
+Coercion
+</h3>
+<p>
+JSON-LD
+supports
+the
+coercion
+of
+values
+to
+particular
+data
+types.
+Type
+<dfn title="coercion" id="dfn-coercion">
+coercion
+</dfn>
+allows
+someone
+deploying
+JSON-LD
+to
+coerce
+the
+incoming
+or
+outgoing
+values
+to
+the
+proper
+data
+type
+based
+on
+a
+mapping
+of
+data
+type
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+s
+to
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s.
+Using
+type
+coercion,
+value
+representation
+is
+preserved
+without
+requiring
+the
+data
+type
+to
+be
+specified
+with
+each
+piece
+of
+data.
+</p>
+<p>
+Type
+coercion
+is
+specified
+within
+an
+<a href="#expanded-term-definition">
+expanded
+term
+definition
+</a>
+using
+the
+<code>
+@type
+</code>
+key.
+The
+value
+of
+this
+key
+represents
+a
+type
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+and
+<em class="rfc2119" title="must">
+must
+</em>
+take
+the
+form
+of
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>,
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+or
+the
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>
+<code>
+@id
+</code>.
+Specifying
+<code>
+@id
+</code>
+indicates
+that
+within
+the
+body
+of
+a
+JSON-LD
+document,
+a
+string
+value
+of
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+coerced
+to
+<code>
+@id
+</code>
+is
+to
+be
+interpreted
+as
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+</p>
+<p>
+<a class="tref internalDFN" title="term" href="#dfn-term">
+Terms
+</a>
+or
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+IRIs
+</a>
+used
+as
+the
+value
+of
+a
+<code>
+@type
+</code>
+key
+<em class="rfc2119" title="may">
+may
+</em>
+be
+defined
+within
+the
+same
+context.
+This
+means
+that
+one
+may
+specify
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+like
+<code>
+xsd
+</code>
+and
+then
+use
+<code>
+xsd:integer
+</code>
+within
+the
+same
+context
+definition
+-
+the
+JSON-LD
+processor
+will
+be
+able
+to
+determine
+the
+proper
+expansion
+for
+<code>
+xsd:integer
+</code>.
+</p>
+<p>
+The
+example
+below
+demonstrates
+how
+a
+JSON-LD
+author
+can
+coerce
+values
+to
+<a class="tref internalDFN" title="typed_value" href="#dfn-typed_value">
+typed
+value
+</a>
+s,
+IRIs
+and
+lists.
+</p>
+<div class="example"><div class="example-title"><span>Example 28</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;,
+    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+    &quot;age&quot;:
+    <span class="diff">{
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/age&quot;,
+      &quot;@type&quot;: &quot;xsd:integer&quot;
+    }</span>,
+    &quot;homepage&quot;:
+    <span class="diff">{
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;,
+      &quot;@container&quot;: &quot;@list&quot;
+    }</span>
+  },
+  &quot;name&quot;: &quot;John Smith&quot;,
+  &quot;age&quot;: <span class="diff">&quot;41&quot;</span>,
+  &quot;homepage&quot;:
+  <span class="diff">[
+    &quot;http://personal.example.org/&quot;,
+    &quot;http://work.example.com/jsmith/&quot;
+  ]</span>
+}
+</pre>
+</div>
+<p>
+The
+example
+above
+would
+generate
+the
+following
+Turtle:
+</p>
+<div class="example"><div class="example-title"><span>Example 29</span></div><pre class="example">@prefix xsd: &lt;http://www.w3.org/2001/XMLSchema#&gt; .
+[ foaf:name &quot;John Smith&quot;;
+  foaf:age  &quot;41&quot;^^xsd:integer;
+  foaf:homepage ( &lt;http://personal.example.org/&gt; &lt;http://work.example.com/jsmith/&gt; )
+]
+.
+</pre>
+</div>
+<p>
+Terms
+may
+also
+be
+defined
+using
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+IRIs
+</a>
+or
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+IRIs
+</a>.
+This
+allows
+coercion
+rules
+to
+be
+applied
+to
+keys
+which
+are
+not
+represented
+as
+a
+simple
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>.
+For
+example:
+</p>
+<div class="example"><div class="example-title"><span>Example 30</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    <span class="diff">&quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;</span>,
+    &quot;<span class="diff">foaf:age</span>&quot;:
+    {
+      &quot;@type&quot;: &quot;xsd:integer&quot;
+    },
+    &quot;<span class="diff">foaf:homepage</span>&quot;:
+    <span class="diff">{
+      &quot;@type&quot;: &quot;@id&quot;
+    }</span>
+  },
+  &quot;foaf:name&quot;: &quot;John Smith&quot;,
+  &quot;foaf:age&quot;: <span class="diff">&quot;41&quot;</span>,
+  &quot;foaf:homepage&quot;:
+  <span class="diff">[
+    &quot;http://personal.example.org/&quot;,
+    &quot;http://work.example.com/jsmith/&quot;
+  ]</span>
+}
+</pre>
+</div>
+<p>
+In
+this
+case
+the
+<code>
+@id
+</code>
+definition
+is
+optional,
+but
+if
+it
+does
+exist,
+the
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+or
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+is
+treated
+as
+a
+term
+(not
+a
+<code>
+prefix:suffix
+</code>
+construct)
+so
+that
+the
+actual
+definition
+of
+a
+<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
+prefix
+</a>
+becomes
+unnecessary.
+</p>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+Keys
+in
+the
+context
+are
+treated
+as
+<a class="tref internalDFN" title="term" href="#dfn-term">
+terms
+</a>
+for
+the
+purpose
+of
+expansion
+and
+value
+coercion.
+At
+times,
+this
+may
+result
+in
+multiple
+representations
+for
+the
+same
+expanded
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>.
+For
+example,
+one
+could
+specify
+that
+<code>
+dog
+</code>
+and
+<code>
+cat
+</code>
+both
+expanded
+to
+<code>
+http://example.com/vocab#animal
+</code>.
+Doing
+this
+could
+be
+useful
+for
+establishing
+different
+type
+coercion
+or
+language
+specification
+rules.
+It
+also
+allows
+a
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+(or
+even
+an
+absolute
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+)
+to
+be
+defined
+as
+something
+else
+entirely.
+For
+example,
+one
+could
+specify
+that
+the
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+<code>
+http://example.org/zoo
+</code>
+should
+expand
+to
+<code>
+http://example.org/river
+</code>,
+but
+this
+usage
+is
+discouraged
+because
+it
+would
+lead
+to
+a
+great
+deal
+of
+confusion
+among
+developers
+attempting
+to
+understand
+the
+JSON-LD
+document.
+</p>
+</div>
+<p>
+Type
+coercion
+is
+performed
+using
+the
+unexpanded
+value
+of
+the
+key,
+which
+<em class="rfc2119" title="must">
+must
+</em>
+have
+an
+exact
+match
+for
+an
+entry
+in
+the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">
+active
+context
+</a>.
+</p>
+</div>
+<div id="iri-expansion-within-a-context" class="section">
+<h3>
+<span class="secno">
+4.7
+</span>
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+Expansion
+Within
+a
+Context
+</h3>
+<p>
+In
+general,
+normal
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+expansion
+rules
+apply
+anywhere
+an
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+is
+expected
+(see
+<a href="#iris">
+IRIs
+</a>
+).
+Within
+a
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+definition,
+this
+can
+mean
+that
+terms
+defined
+within
+the
+context
+<em class="rfc2119" title="may">
+may
+</em>
+also
+be
+used
+within
+that
+context
+as
+long
+as
+there
+are
+no
+circular
+dependencies.
+For
+example,
+it
+is
+common
+to
+use
+the
+<code>
+xsd
+</code>
+namespace
+when
+defining
+<a class="tref internalDFN" title="typed_value" href="#dfn-typed_value">
+typed
+value
+</a>
+s:
+</p>
+<div class="example"><div class="example-title"><span>Example 31</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    <span class="diff">&quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;</span>,
+    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+    &quot;age&quot;:
+    {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/age&quot;,
+      &quot;@type&quot;: <span class="diff">&quot;xsd:integer&quot;</span>
+    },
+    &quot;homepage&quot;:
+    {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    }
+  },
+  ...
+}
+</pre>
+</div>
+<p>
+In
+this
+example,
+the
+<code>
+xsd
+</code>
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+is
+defined
+and
+used
+as
+a
+<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
+prefix
+</a>
+for
+the
+<code>
+@type
+</code>
+coercion
+of
+the
+<code>
+age
+</code>
+property.
+</p>
+<p>
+<a class="tref internalDFN" title="term" href="#dfn-term">
+Term
+</a>
+s
+<em class="rfc2119" title="may">
+may
+</em>
+also
+be
+used
+when
+defining
+the
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+of
+another
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>:
+</p>
+<div class="example"><div class="example-title"><span>Example 32</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    <span class="diff">&quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;</span>,
+    &quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;,
+    &quot;name&quot;: <span class="diff">&quot;foaf:name&quot;</span>,
+    &quot;age&quot;:
+    {
+      &quot;@id&quot;: <span class="diff">&quot;foaf:age&quot;</span>,
+      &quot;@type&quot;: &quot;xsd:integer&quot;
+    },
+    &quot;homepage&quot;:
+    {
+      &quot;@id&quot;: <span class="diff">&quot;foaf:homepage&quot;</span>,
+      &quot;@type&quot;: &quot;@id&quot;
+    }
+  },
+  ...
+}
+</pre>
+</div>
+<p>
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+Compact
+IRIs
+</a>
+and
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+IRIs
+</a>
+<em class="rfc2119" title="may">
+may
+</em>
+be
+used
+on
+the
+left-hand
+side
+of
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+definition.
+</p>
+<div class="example"><div class="example-title"><span>Example 33</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    <span class="diff">&quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;</span>,
+    &quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;,
+    &quot;name&quot;: &quot;foaf:name&quot;,
+    &quot;<span class="diff">foaf:age</span>&quot;:
+    {
+      &quot;@type&quot;: &quot;xsd:integer&quot;
+    },
+    &quot;<span class="diff">foaf:homepage</span>&quot;:
+    <span class="diff">{
+      &quot;@type&quot;: &quot;@id&quot;
+    }</span>
+  },
+  ...
+}
+</pre>
+</div>
+<p>
+In
+this
+example,
+the
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+form
+is
+used
+in
+two
+different
+ways.
+In
+the
+first
+approach,
+<code>
+foaf:age
+</code>
+declares
+both
+the
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+for
+the
+term
+(using
+short-form)
+as
+well
+as
+the
+<code>
+@type
+</code>
+associated
+with
+the
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>.
+In
+the
+second
+approach,
+only
+the
+<code>
+@type
+</code>
+associated
+with
+the
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+is
+specified.
+The
+JSON-LD
+processor
+will
+derive
+the
+full
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+for
+<code>
+foaf:homepage
+</code>
+by
+looking
+up
+the
+<code>
+foaf
+</code>
+<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
+prefix
+</a>
+in
+the
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>.
+</p>
+<p>
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+Absolute
+IRIs
+</a>
+<em class="rfc2119" title="may">
+may
+</em>
+also
+be
+used
+in
+the
+key
+position
+in
+a
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>:
+</p>
+<div class="example"><div class="example-title"><span>Example 34</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;,
+    &quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;,
+    &quot;name&quot;: &quot;foaf:name&quot;,
+    &quot;foaf:age&quot;:
+    {
+      &quot;@id&quot;: &quot;foaf:age&quot;,
+      &quot;@type&quot;: &quot;xsd:integer&quot;
+    },
+    &quot;<span class="diff">http://xmlns.com/foaf/0.1/homepage</span>&quot;:
+    {
+      &quot;@type&quot;: &quot;@id&quot;
+    }
+  },
+  ...
+}
+</pre>
+</div>
+<p>
+In
+order
+for
+the
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+to
+match
+above,
+the
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">
+absolute
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+<em class="rfc2119" title="must">
+must
+</em>
+also
+be
+used
+in
+the
+JSON-LD
+document.
+Also
+note
+that
+<code>
+foaf:homepage
+</code>
+will
+not
+use
+the
+<code>
+{
+&quot;@type&quot;:
+&quot;@id&quot;
+}
+</code>
+declaration
+because
+<code>
+foaf:homepage
+</code>
+is
+not
+the
+same
+as
+<code>
+http://xmlns.com/foaf/0.1/homepage
+</code>.
+That
+is,
+a
+JSON-LD
+processor
+will
+use
+direct
+string
+comparison
+when
+looking
+up
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>
+s
+in
+a
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+before
+it
+applies
+the
+<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
+prefix
+</a>
+lookup
+mechanism.
+</p>
+<p>
+The
+only
+exception
+for
+using
+terms
+in
+the
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+is
+that
+they
+<em class="rfc2119" title="must not">
+must
+not
+</em>
+be
+used
+in
+a
+circular
+manner.
+That
+is,
+a
+definition
+of
+<em>
+term-1
+</em>
+<em class="rfc2119" title="must not">
+must
+not
+</em>
+depend
+on
+the
+definition
+of
+<em>
+term-2
+</em>
+if
+<em>
+term-2
+</em>
+also
+depends
+on
+<em>
+term-1
+</em>.
+For
+example,
+the
+following
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+definition
+is
+illegal:
+</p>
+<div class="example"><div class="example-title"><span>Example 35</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    <span class="diff">&quot;term1&quot;: &quot;term2:foo&quot;,
+    &quot;term2&quot;: &quot;term1:bar&quot;</span>
+  },
+  ...
+}
+</pre>
+</div>
+</div>
+<div id="sets-and-lists" class="section">
+<h3>
+<span class="secno">
+4.8
+</span>
+Sets
+and
+Lists
+</h3>
+<p>
+A
+JSON-LD
+author
+can
+express
+multiple
+values
+in
+a
+compact
+way
+by
+using
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>
+s.
+Since
+graphs
+do
+not
+describe
+ordering
+for
+links
+between
+nodes,
+arrays
+in
+JSON-LD
+do
+not
+provide
+an
+ordering
+of
+the
+listed
+<a class="tref internalDFN" title="object" href="#dfn-object">
+objects
+</a>
+by
+default.
+This
+is
+exactly
+the
+opposite
+from
+regular
+JSON
+arrays,
+which
+are
+ordered
+by
+default.
+For
+example,
+consider
+the
+following
+simple
+document:
+</p>
+<div class="example"><div class="example-title"><span>Example 36</span></div><pre class="example">{
+...
+  &quot;@id&quot;: &quot;http://example.org/people#joebob&quot;,
+  &quot;nick&quot;: <span class="diff">[ &quot;joe&quot;, &quot;bob&quot;, &quot;jaybee&quot; ]</span>,
+...
+}
+</pre>
+</div>
+<p>
+The
+markup
+shown
+above
+would
+result
+in
+three
+triples
+being
+generated,
+each
+relating
+the
+subject
+to
+an
+individual
+<a class="tref internalDFN" title="object" href="#dfn-object">
+object
+</a>,
+with
+no
+inherent
+order:
+</p>
+<div class="example"><div class="example-title"><span>Example 37</span></div><pre class="example">&lt;http://example.org/people#joebob&gt;
+   &lt;http://xmlns.com/foaf/0.1/nick&gt;
+      &quot;joe&quot; .
+&lt;http://example.org/people#joebob&gt;
+   &lt;http://xmlns.com/foaf/0.1/nick&gt;
+      &quot;bob&quot; .
+&lt;http://example.org/people#joebob&gt;
+   &lt;http://xmlns.com/foaf/0.1/nick&gt;
+&quot;jaybee&quot;
+.
+</pre>
+</div>
+<p>
+Multiple
+values
+may
+also
+be
+expressed
+using
+the
+expanded
+form:
+</p>
+<div class="example"><div class="example-title"><span>Example 38</span></div><pre class="example">{
+  &quot;@id&quot;: &quot;http://example.org/articles/8&quot;,
+  &quot;dc:title&quot;: <span class="diff">
+  [
+    {
+      &quot;@value&quot;: &quot;Das Kapital&quot;,
+      &quot;@language&quot;: &quot;de&quot;
+    },
+    {
+      &quot;@value&quot;: &quot;Capital&quot;,
+      &quot;@language&quot;: &quot;en&quot;
+    }
+  ]</span>
+}
+</pre>
+</div>
+<p>
+The
+markup
+shown
+above
+would
+generate
+the
+following
+triples,
+again
+with
+no
+inherent
+order:
+</p>
+<div class="example"><div class="example-title"><span>Example 39</span></div><pre class="example">&lt;http://example.org/articles/8&gt;
+   &lt;http://purl.org/dc/terms/title&gt;
+      &quot;Das Kapital&quot;@de .
+&lt;http://example.org/articles/8&gt;
+   &lt;http://purl.org/dc/terms/title&gt;
+&quot;Capital&quot;@en
+.
+</pre>
+</div>
+<p>
+As
+the
+notion
+of
+ordered
+collections
+is
+rather
+important
+in
+data
+modeling,
+it
+is
+useful
+to
+have
+specific
+language
+support.
+In
+JSON-LD,
+a
+list
+may
+be
+represented
+using
+the
+<code>
+@list
+</code>
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>
+as
+follows:
+</p>
+<div class="example"><div class="example-title"><span>Example 40</span></div><pre class="example">{
+...
+  &quot;@id&quot;: &quot;http://example.org/people#joebob&quot;,
+  &quot;foaf:nick&quot;:
+  <span class="diff">{
+    &quot;@list&quot;: [ &quot;joe&quot;, &quot;bob&quot;, &quot;jaybee&quot; ]
+  }</span>,
+...
+}
+</pre>
+</div>
+<p>
+This
+describes
+the
+use
+of
+this
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>
+as
+being
+ordered,
+and
+order
+is
+maintained
+when
+processing
+a
+document.
+If
+every
+use
+of
+a
+given
+multi-valued
+property
+is
+a
+list,
+this
+may
+be
+abbreviated
+by
+setting
+<code>
+@container
+</code>
+to
+<code>
+@list
+</code>
+in
+the
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>:
+</p>
+<div class="example"><div class="example-title"><span>Example 41</span></div><pre class="example">{
+  <span class="diff">&quot;@context&quot;:
+  {
+    ...
+    &quot;nick&quot;:
+    {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/nick&quot;,
+      &quot;@container&quot;: &quot;@list&quot;
+    }
+  }</span>,
+...
+  &quot;@id&quot;: &quot;http://example.org/people#joebob&quot;,
+  &quot;nick&quot;: <span class="diff">[ &quot;joe&quot;, &quot;bob&quot;, &quot;jaybee&quot; ]</span>,
+...
+}
+</pre>
+</div>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+List
+of
+lists
+are
+not
+allowed
+in
+this
+version
+of
+JSON-LD.
+If
+a
+list
+of
+lists
+is
+detected,
+a
+JSON-LD
+processor
+will
+throw
+an
+exception.
+This
+decision
+was
+made
+due
+to
+the
+extreme
+amount
+of
+added
+complexity
+when
+processing
+lists
+of
+lists.
+</p>
+</div>
+<p>
+Similarly
+to
+<code>
+@list
+</code>,
+there
+exists
+the
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>
+<code>
+@set
+</code>
+to
+describe
+unordered
+sets.
+While
+its
+use
+in
+the
+body
+of
+a
+JSON-LD
+document
+represents
+just
+syntactic
+sugar
+that
+<em class="rfc2119" title="must">
+must
+</em>
+be
+optimized
+away
+when
+processing
+the
+document,
+it
+is
+very
+helpful
+when
+used
+within
+the
+context
+of
+a
+document.
+Values
+of
+terms
+associated
+with
+a
+<code>
+@set
+</code>
+or
+<code>
+@list
+</code>
+container
+are
+always
+represented
+in
+the
+form
+of
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>
+-
+even
+if
+there
+is
+just
+a
+single
+value
+that
+would
+otherwise
+be
+optimized
+to
+a
+non-array
+form
+in
+a
+<a href="#compact-document-form">
+compacted
+document
+</a>.
+This
+makes
+post-processing
+of
+the
+data
+easier
+as
+the
+data
+is
+always
+in
+array
+form,
+even
+if
+the
+array
+only
+contains
+a
+single
+value.
+</p>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<p class="">
+The
+use
+of
+<code>
+@container
+</code>
+in
+the
+body
+of
+a
+JSON-LD
+document,
+i.e.,
+outside
+<code>
+@context
+</code>
+<em class="rfc2119" title="must">
+must
+</em>
+be
+ignored
+by
+JSON-LD
+processors.
+</p>
+</div>
+</div>
+<div id="embedding" class="section">
+<h3>
+<span class="secno">
+4.9
+</span>
+Embedding
+</h3>
+<p>
+Object
+<dfn title="embedding" id="dfn-embedding">
+embedding
+</dfn>
+is
+a
+JSON-LD
+feature
+that
+allows
+an
+author
+to
+use
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definitions
+</a>
+as
+<a class="tref internalDFN" title="property" href="#dfn-property">
+property
+</a>
+values.
+This
+is
+a
+commonly
+used
+mechanism
+for
+creating
+a
+parent-child
+relationship
+between
+two
+<a class="tref internalDFN" title="subject" href="#dfn-subject">
+subject
+</a>
+s.
+</p>
+<p>
+The
+example
+shows
+two
+subjects
+related
+by
+a
+property
+from
+the
+first
+subject:
+</p>
+  <div class="example"><div class="example-title"><span>Example 42</span></div><pre class="example">{
+...
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;<span class="diff">knows</span>&quot;:
+  {
+    &quot;<span class="diff">@type</span>&quot;: &quot;<span class="diff">Person</span>&quot;,
+    &quot;<span class="diff">name</span>&quot;: &quot;<span class="diff">Gregg Kellogg</span>&quot;,
+  }
+...
+}
+</pre>
+</div>
+<p>
+A
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>,
+like
+the
+one
+used
+above,
+<em class="rfc2119" title="may">
+may
+</em>
+be
+used
+in
+any
+value
+position
+in
+the
+body
+of
+a
+JSON-LD
+document.
+</p>
+</div>
+<div id="named-graphs" class="section">
+<h3>
+<span class="secno">
+4.10
+</span>
+Named
+Graphs
+</h3>
+<p>
+The
+<code>
+@graph
+</code>
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>
+is
+used
+to
+express
+a
+set
+of
+JSON-LD
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>
+s
+that
+may
+not
+be
+directly
+related
+to
+one
+another
+through
+a
+property.
+The
+mechanism
+may
+also
+be
+used
+where
+<a class="tref internalDFN" title="embedding" href="#dfn-embedding">
+embedding
+</a>
+is
+not
+desirable
+to
+the
+application.
+For
+example:
+</p>
+  <div class="example"><div class="example-title"><span>Example 43</span></div><pre class="example">{
+  &quot;@context&quot;: ...,
+  &quot;<span class="diff">@graph</span>&quot;:
+  [
+    {
+      &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
+      &quot;@type&quot;: &quot;foaf:Person&quot;,
+      &quot;name&quot;: &quot;Manu Sporny&quot;,
+      &quot;knows&quot;: &quot;http://greggkellogg.net/foaf#me&quot;
+    },
+    {
+      &quot;@id&quot;: &quot;http://greggkellogg.net/foaf#me&quot;,
+      &quot;@type&quot;: &quot;foaf:Person&quot;,
+      &quot;name&quot;: &quot;Gregg Kellogg&quot;,
+      &quot;knows&quot;: &quot;http://manu.sporny.org/i/public&quot;
+    }
+  ]
+}
+</pre>
+</div>
+<p>
+In
+this
+case,
+embedding
+doesn't
+work
+as
+each
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>
+references
+the
+other.
+Using
+the
+<code>
+@graph
+</code>
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>
+allows
+multiple
+resources
+to
+be
+defined
+within
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>,
+and
+allows
+the
+use
+of
+a
+shared
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>.
+When
+used
+in
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+that
+is
+not
+otherwise
+a
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>,
+this
+describes
+resources
+in
+the
+<em>
+default
+graph
+</em>.
+This
+is
+equivalent
+to
+using
+multiple
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definitions
+</a>
+in
+array
+and
+defining
+the
+<code>
+@context
+</code>
+within
+each
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>:
+</p>
+  <div class="example"><div class="example-title"><span>Example 44</span></div><pre class="example"><span class="diff">[</span>
+  {
+    <span class="diff">&quot;@context&quot;: ...,</span>
+    &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
+    &quot;@type&quot;: &quot;foaf:Person&quot;,
+    &quot;name&quot;: &quot;Manu Sporny&quot;,
+    &quot;knows&quot;: &quot;http://greggkellogg.net/foaf#me&quot;
+  },
+  {
+    <span class="diff">&quot;@context&quot;: ...,</span>
+    &quot;@id&quot;: &quot;http://greggkellogg.net/foaf#me&quot;,
+    &quot;@type&quot;: &quot;foaf:Person&quot;,
+    &quot;name&quot;: &quot;Gregg Kellogg&quot;,
+    &quot;knows&quot;: &quot;http://manu.sporny.org/i/public&quot;
+  }
+<span class="diff">
+]
+</span>
+</pre>
+</div>
+<p>
+JSON-LD
+allows
+you
+to
+<em>
+name
+</em>
+things
+on
+the
+Web
+by
+assigning
+an
+<code>
+@id
+</code>
+to
+them,
+which
+is
+typically
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+This
+notion
+extends
+to
+the
+ability
+to
+identify
+graphs
+in
+the
+same
+manner.
+A
+developer
+may
+name
+data
+expressed
+using
+the
+<code>
+@graph
+</code>
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>
+by
+pairing
+it
+with
+an
+<code>
+@id
+</code>
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>.
+This
+enables
+the
+developer
+to
+make
+statements
+about
+a
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>
+itself,
+rather
+than
+just
+a
+single
+<a class="tref internalDFN" title="subject" href="#dfn-subject">
+subject
+</a>.
+</p>
+  <div class="example"><div class="example-title"><span>Example 45</span></div><pre class="example">{
+  &quot;@context&quot;: ...,
+  <span class="diff">&quot;@id&quot;: &quot;http://example.org/graphs/73&quot;,
+  &quot;asOf&quot;: { &quot;@value&quot;: &quot;2012-04-09&quot;, &quot;@type&quot;: &quot;xsd:date&quot; },
+  &quot;@graph&quot;:</span>
+  [
+    {
+      &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
+      &quot;@type&quot;: &quot;foaf:Person&quot;,
+      &quot;name&quot;: &quot;Manu Sporny&quot;,
+      &quot;knows&quot;: &quot;http://greggkellogg.net/foaf#me&quot;
+    },
+    {
+      &quot;@id&quot;: &quot;http://greggkellogg.net/foaf#me&quot;,
+      &quot;@type&quot;: &quot;foaf:Person&quot;,
+      &quot;name&quot;: &quot;Gregg Kellogg&quot;,
+      &quot;knows&quot;: &quot;http://manu.sporny.org/i/public&quot;
+    }
+  ]
+}
+</pre>
+</div>
+<p>
+The
+example
+above
+expresses
+a
+<em>
+named
+</em>
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>
+that
+is
+identified
+by
+the
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+<code>
+http://example.org/graphs/73
+</code>.
+That
+graph
+is
+composed
+of
+the
+statements
+about
+Manu
+and
+Gregg.
+Meta-data
+about
+the
+graph
+itself
+is
+also
+expressed
+via
+the
+<code>
+asOf
+</code>
+property,
+which
+specifies
+when
+the
+information
+was
+retrieved
+from
+the
+Web.
+</p>
+<div class="issue">
+<div class="issue-title">
+<span>
+Issue
+3
+</span>
+</div>
+<p class="">
+These
+examples
+could
+all
+have
+TriG
+definitions
+of
+their
+RDF
+results,
+but
+that
+would
+involve
+adding
+RDF
+earlier
+in
+the
+document.
+</p>
+</div>
+</div>
+<div id="identifying-unlabeled-nodes" class="section">
+<h3>
+<span class="secno">
+4.11
+</span>
+Identifying
+Unlabeled
+Nodes
+</h3>
+<p>
+At
+times,
+it
+becomes
+necessary
+to
+be
+able
+to
+express
+information
+without
+being
+able
+to
+specify
+the
+subject.
+Typically,
+this
+type
+of
+node
+is
+called
+an
+<dfn title="unlabeled_node" id="dfn-unlabeled_node">
+unlabeled
+node
+</dfn>
+or
+a
+blank
+node
+(see
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">
+RDF-CONCEPTS
+</a>
+</cite>
+]
+<cite>
+<a href="http://www.w3.org/TR/rdf11-concepts/#section-blank-nodes">
+Section
+3.4:
+Blank
+Nodes
+</a>
+</cite>
+).
+In
+JSON-LD,
+<a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">
+unlabeled
+node
+</a>
+identifiers
+are
+automatically
+created
+if
+a
+subject
+is
+not
+specified
+using
+the
+<code>
+@id
+</code>
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keyword
+</a>.
+However,
+authors
+may
+provide
+identifiers
+for
+<a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">
+unlabeled
+nodes
+</a>
+by
+using
+the
+special
+<code>
+_
+</code>
+(underscore)
+<a class="tref internalDFN" title="prefix" href="#dfn-prefix">
+prefix
+</a>.
+This
+allows
+one
+to
+reference
+the
+node
+locally
+within
+the
+document,
+but
+makes
+it
+impossible
+to
+reference
+the
+node
+from
+an
+external
+document.
+The
+<a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">
+unlabeled
+node
+</a>
+identifier
+is
+scoped
+to
+the
+document
+in
+which
+it
+is
+used.
+</p>
+<div class="example"><div class="example-title"><span>Example 46</span></div><pre class="example">{
+...
+  &quot;@id&quot;: &quot;<span class="diff">_:foo</span>&quot;,
+...
+}
+</pre>
+</div>
+<p>
+The
+example
+above
+would
+set
+the
+subject
+to
+<code>
+_:foo
+</code>,
+which
+can
+then
+be
+used
+elsewhere
+in
+the
+JSON-LD
+document
+to
+refer
+back
+to
+the
+<a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">
+unlabeled
+node
+</a>.
+If
+a
+developer
+finds
+that
+they
+refer
+to
+the
+unlabeled
+node
+more
+than
+once,
+they
+should
+consider
+naming
+the
+node
+using
+a
+de-referenceable
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+so
+that
+it
+can
+be
+referenced
+also
+from
+other
+documents.
+</p>
+</div>
+<div id="aliasing-keywords" class="section">
+<h3>
+<span class="secno">
+4.12
+</span>
+Aliasing
+Keywords
+</h3>
+<p>
+Each
+of
+the
+JSON-LD
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keywords
+</a>,
+except
+for
+<code>
+@context
+</code>,
+<em class="rfc2119" title="may">
+may
+</em>
+be
+aliased
+to
+application-specific
+keywords.
+This
+feature
+allows
+legacy
+JSON
+content
+to
+be
+utilized
+by
+JSON-LD
+by
+re-using
+JSON
+keys
+that
+already
+exist
+in
+legacy
+documents.
+This
+feature
+also
+allows
+developers
+to
+design
+domain-specific
+implementations
+using
+only
+the
+JSON-LD
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>.
+</p>
+<div class="example"><div class="example-title"><span>Example 47</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+     <span class="diff">&quot;url&quot;: &quot;@id&quot;</span>,
+     <span class="diff">&quot;a&quot;: &quot;@type&quot;</span>,
+     &quot;name&quot;: &quot;http://schema.org/name&quot;
+  },
+  &quot;<span class="diff">url</span>&quot;: &quot;http://example.com/about#gregg&quot;,
+  &quot;<span class="diff">a</span>&quot;: &quot;http://schema.org/Person&quot;,
+  &quot;name&quot;: &quot;Gregg Kellogg&quot;
+}
+</pre>
+</div>
+<p>
+In
+the
+example
+above,
+the
+<code>
+@id
+</code>
+and
+<code>
+@type
+</code>
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">
+keywords
+</a>
+have
+been
+given
+the
+aliases
+<strong>
+url
+</strong>
+and
+<strong>
+a
+</strong>,
+respectively.
+</p>
+</div>
+<div id="expanded-document-form" class="section">
+<h3>
+<span class="secno">
+4.13
+</span>
+Expanded
+Document
+Form
+</h3>
+<p>
+The
+JSON-LD
+API
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-JSON-LD-API">
+JSON-LD-API
+</a>
+</cite>
+]
+defines
+an
+method
+for
+<em>
+expanding
+</em>
+a
+JSON-LD
+document.
+Expansion
+is
+the
+process
+of
+taking
+a
+JSON-LD
+document
+and
+applying
+a
+<code>
+@context
+</code>
+such
+that
+all
+IRIs,
+types,
+and
+values
+are
+expanded
+so
+that
+the
+<code>
+@context
+</code>
+is
+no
+longer
+necessary.
+</p>
+<p>
+For
+example,
+assume
+the
+following
+JSON-LD
+input
+document:
+</p>
+<div class="example"><div class="example-title"><span>Example 48</span></div><pre class="example">{
+   &quot;@context&quot;:
+   {
+      &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+      &quot;homepage&quot;: {
+        &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+        &quot;@type&quot;, &quot;@id&quot;
+      }
+   },
+   &quot;name&quot;: &quot;Manu Sporny&quot;,
+   &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;
+}
+</pre>
+</div>
+<p>
+Running
+the
+JSON-LD
+Expansion
+algorithm
+against
+the
+JSON-LD
+input
+document
+provided
+above
+would
+result
+in
+the
+following
+output:
+</p>
+<div class="example"><div class="example-title"><span>Example 49</span></div><pre class="example">[
+  {
+    &quot;http://xmlns.com/foaf/0.1/name&quot;: [
+      { &quot;@value&quot;: &quot;Manu Sporny&quot; }
+    ],
+    &quot;http://xmlns.com/foaf/0.1/homepage&quot;: [
+      { &quot;@id&quot;: &quot;http://manu.sporny.org/&quot; }
+    ]
+  }
+]
+</pre>
+</div>
+<p>
+Expanded
+document
+form
+is
+useful
+when
+an
+application
+has
+to
+process
+input
+data
+in
+a
+deterministic
+form.
+It
+has
+been
+optimized
+to
+ensure
+that
+the
+code
+that
+developers
+have
+to
+write
+is
+minimized
+compared
+to
+the
+code
+that
+would
+have
+to
+be
+written
+to
+operate
+on
+<a href="#compact-document-form">
+compact
+document
+form
+</a>.
+</p>
+</div>
+<div id="compact-document-form" class="section">
+<h3>
+<span class="secno">
+4.14
+</span>
+Compact
+Document
+Form
+</h3>
+<p>
+The
+JSON-LD
+API
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-JSON-LD-API">
+JSON-LD-API
+</a>
+</cite>
+]
+defines
+a
+method
+for
+<em>
+compacting
+</em>
+a
+JSON-LD
+document.
+Compaction
+is
+the
+process
+of
+taking
+a
+JSON-LD
+document
+and
+applying
+a
+context
+such
+that
+the
+most
+compact
+form
+of
+the
+document
+is
+generated.
+JSON
+is
+typically
+expressed
+in
+a
+very
+compact,
+key-value
+format.
+That
+is,
+full
+IRIs
+are
+rarely
+used
+as
+keys.
+At
+times,
+a
+JSON-LD
+document
+may
+be
+received
+that
+is
+not
+in
+its
+most
+compact
+form.
+JSON-LD,
+via
+the
+API,
+provides
+a
+way
+to
+compact
+a
+JSON-LD
+document.
+</p>
+<p>
+For
+example,
+assume
+the
+following
+JSON-LD
+input
+document:
+</p>
+<div class="example"><div class="example-title"><span>Example 50</span></div><pre class="example">[
+  {
+    &quot;http://xmlns.com/foaf/0.1/name&quot;: [ &quot;Manu Sporny&quot; ],
+    &quot;http://xmlns.com/foaf/0.1/homepage&quot;: [
+      {
+       &quot;@id&quot;: &quot;http://manu.sporny.org/&quot;
+      }
+    ]
+  }
+]
+</pre>
+</div>
+<p>
+Additionally,
+assume
+the
+following
+developer-supplied
+JSON-LD
+context:
+</p>
+<div class="example"><div class="example-title"><span>Example 51</span></div><pre class="example">{
+  &quot;@context&quot;: {
+    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+    &quot;homepage&quot;: {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    }
+  }
+}
+</pre>
+</div>
+<p>
+Running
+the
+JSON-LD
+Compaction
+algorithm
+given
+the
+context
+supplied
+above
+against
+the
+JSON-LD
+input
+document
+provided
+above
+would
+result
+in
+the
+following
+output:
+</p>
+<div class="example"><div class="example-title"><span>Example 52</span></div><pre class="example">{
+  &quot;@context&quot;: {
+    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+    &quot;homepage&quot;: {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    }
+  },
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;
+}
+</pre>
+</div>
+<p>
+The
+compaction
+algorithm
+enables
+a
+developer
+to
+map
+any
+document
+into
+an
+application-specific
+compacted
+form
+by
+first
+<a href="#expanded-document-form">
+expanding
+the
+document
+</a>.
+While
+the
+context
+provided
+above
+mapped
+<code>
+http://xmlns.com/foaf/0.1/name
+</code>
+to
+<strong>
+name
+</strong>,
+it
+could
+have
+also
+mapped
+it
+to
+any
+arbitrary
+string
+provided
+by
+the
+developer.
+This
+powerful
+mechanism,
+along
+with
+another
+JSON-LD
+API
+technique
+called
+<em>
+framing
+</em>,
+allows
+the
+developer
+to
+re-shape
+the
+incoming
+JSON
+data
+into
+a
+format
+that
+is
+optimized
+for
+their
+application.
+</p>
+</div>
+</div>
+<div class="appendix normative section" id="json-ld-authoring-guidelines">
+<h2>
+<span class="secno">
+A.
+</span>
+JSON-LD
+Authoring
+Guidelines
+</h2>
+<p>
+Since
+the
+JSON-LD
+syntax
+is
+a
+subset
+of
+the
+JSON
+syntax,
+it
+follows
+that
+all
+valid
+JSON-LD
+documents
+are
+valid
+JSON
+documents.
+It
+also
+means
+that
+an
+invalid
+JSON
+document
+can
+never
+be
+a
+valid
+JSON-LD
+document.
+Furthermore,
+JSON-LD
+places
+a
+number
+of
+restrictions
+on
+the
+JSON
+syntax
+in
+order
+to
+define
+a
+set
+of
+authoring
+<em>
+guidelines
+</em>
+that
+are
+used
+to
+express
+<em>
+well-formed
+</em>
+JSON-LD
+documents.
+At
+times,
+even
+if
+these
+guidelines
+are
+violated,
+a
+JSON-LD
+processor
+will
+do
+its
+best
+to
+recover
+from
+the
+mistake
+and
+will
+deterministically
+transform
+the
+author's
+markup
+into
+well-formed
+JSON-LD.
+</p>
+<div class="issue">
+<div class="issue-title">
+<span>
+Issue
+4
+</span>
+</div>
+<p class="">
+The
+final
+details
+of
+the
+guidelines
+are
+still
+being
+discussed
+(
+<a href="https://github.com/json-ld/json-ld.org/issues/114#issuecomment-5820544">
+ISSUE-114
+</a>
+),
+as
+well
+as
+the
+best
+mechanism
+to
+express
+these
+restrictions.
+EBNF
+doesn't
+quite
+capture
+what
+these
+guidelines
+are
+attempting
+to
+do
+-
+which
+is
+strongly
+express
+what
+constitutes
+a
+well-formed
+JSON-LD
+document.
+For
+the
+time
+being,
+a
+simple
+list
+of
+plain
+English
+guidelines
+are
+provided.
+</p>
+</div>
+<div class="issue">
+<div class="issue-title">
+<span>
+Issue
+5
+</span>
+</div>
+<p class="">
+Per
+<a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2012Jun/0111.html">
+Andy
+S's
+comment
+</a>,
+consider
+making
+this
+a
+normative
+syntax
+definition
+along
+with
+EBNF.
+</p>
+</div>
+<ol>
+<li>
+A
+JSON-LD
+document
+is
+composed
+of
+a
+single
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>
+or
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>
+of
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definitions
+</a>.
+</li>
+<li>
+The
+value
+of
+<code>
+@id
+</code>
+<em class="rfc2119" title="must">
+must
+</em>
+be
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>,
+a
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+or
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+</li>
+<li>
+An
+<code>
+@id
+</code>
+keyword
+and
+a
+<code>
+@language
+</code>
+keyword
+<em class="rfc2119" title="must not">
+must
+not
+</em>
+exist
+in
+the
+same
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>.
+</li>
+<li>
+An
+<code>
+@id
+</code>
+keyword
+and
+a
+<code>
+@container
+</code>
+keyword
+<em class="rfc2119" title="must not">
+must
+not
+</em>
+exist
+in
+the
+same
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>.
+</li>
+<li>
+A
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>
+<em class="rfc2119" title="may">
+may
+</em>
+contain
+a
+<code>
+@context
+</code>
+property.
+</li>
+<li>
+A
+<code>
+@context
+</code>
+value
+<em class="rfc2119" title="must not">
+must
+not
+</em>
+contain
+an
+embedded
+<code>
+@context
+</code>
+definition.
+</li>
+<li>
+The
+value
+associated
+with
+the
+<code>
+@context
+</code>
+keyword
+<em class="rfc2119" title="must">
+must
+</em>
+be
+a
+string
+expanding
+to
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>,
+null,
+or
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>
+containing
+a
+combination
+of
+the
+allowed
+values.
+</li>
+<li>
+The
+value
+associated
+with
+the
+keys
+used
+in
+a
+<code>
+@context
+</code>
+<em class="rfc2119" title="must">
+must
+</em>
+be
+a
+<code>
+null
+</code>,
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+or
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>.
+</li>
+<li>
+For
+each
+value
+that
+is
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+that
+is
+associated
+with
+a
+key
+in
+a
+<code>
+@context
+</code>:
+<ol>
+<li>
+<code>
+@id
+</code>
+and
+<code>
+@type
+</code>
+<em class="rfc2119" title="must">
+must
+</em>
+be
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+or
+<code>
+null
+</code>
+</li>
+<li>
+<code>
+@container
+</code>
+<em class="rfc2119" title="must">
+must
+</em>
+be
+associated
+with
+a
+value
+of
+either
+<code>
+@set
+</code>
+or
+<code>
+@list
+</code>.
+</li>
+<li>
+<code>
+@language
+</code>
+<em class="rfc2119" title="must">
+must
+</em>
+be
+a
+string
+expressed
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-BCP47">
+BCP47
+</a>
+</cite>
+]
+or
+<code>
+null
+</code>.
+</li>
+<li>
+Any
+other
+property
+<em class="rfc2119" title="must">
+must
+</em>
+be
+ignored
+by
+a
+JSON-LD
+processor
+and
+<em class="rfc2119" title="must">
+must
+</em>
+be
+preserved
+in
+compaction
+and
+framing.
+</li>
+</ol>
+</li>
+<li>
+A
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>
+<em class="rfc2119" title="may">
+may
+</em>
+have
+an
+<code>
+@graph
+</code>
+property.
+</li>
+<li>
+The
+value
+of
+a
+<code>
+@graph
+</code>
+property
+<em class="rfc2119" title="must">
+must
+</em>
+be
+a
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definition
+</a>
+or
+an
+array
+of
+zero
+or
+more
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">
+subject
+definitions
+</a>.
+</li>
+<li>
+A
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+containing
+a
+<code>
+@set
+</code>
+key
+<em class="rfc2119" title="must not">
+must
+not
+</em>
+have
+any
+other
+keys.
+</li>
+<li>
+A
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+containing
+a
+<code>
+@list
+</code>
+key
+<em class="rfc2119" title="must not">
+must
+not
+</em>
+have
+any
+other
+keys.
+</li>
+<li>
+The
+value
+of
+an
+<code>
+@set
+</code>
+or
+<code>
+@list
+</code>
+key
+can
+be
+a
+string,
+a
+number,
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>,
+or
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>
+containing
+a
+combination
+of
+the
+allowed
+values.
+</li>
+<li>
+For
+each
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>
+that
+contains
+a
+<code>
+@value
+</code>
+key:
+<ol>
+<li>
+It
+<em class="rfc2119" title="may">
+may
+</em>
+have
+a
+<code>
+@language
+</code>
+or
+<code>
+@type
+</code>
+property
+and
+<em class="rfc2119" title="must not">
+must
+not
+</em>
+have
+any
+other
+properties.
+</li>
+<li>
+It
+<em class="rfc2119" title="must not">
+must
+not
+</em>
+contain
+both
+the
+<code>
+@language
+</code>
+and
+<code>
+@type
+</code>
+keys
+at
+the
+same
+time.
+</li>
+<li>
+The
+value
+of
+the
+<code>
+@value
+</code>
+key
+<em class="rfc2119" title="must">
+must
+</em>
+be
+a
+string
+or
+a
+number.
+</li>
+<li>
+The
+value
+of
+the
+<code>
+@language
+</code>
+key
+<em class="rfc2119" title="must">
+must
+</em>
+be
+<code>
+null
+</code>
+or
+a
+string
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-BCP47">
+BCP47
+</a>
+</cite>
+]
+format.
+</li>
+<li>
+The
+value
+of
+<code>
+@type
+</code>
+<em class="rfc2119" title="must">
+must
+</em>
+be
+<code>
+null
+</code>,
+a
+<a class="tref internalDFN" title="term" href="#dfn-term">
+term
+</a>,
+a
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">
+compact
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+an
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>,
+a
+<a class="tref internalDFN" title="json_object" href="#dfn-json_object">
+JSON
+object
+</a>,
+or
+an
+<a class="tref internalDFN" title="array" href="#dfn-array">
+array
+</a>
+containing
+a
+combination
+of
+the
+allowed
+values.
+</li>
+</ol>
+</li>
+<li>
+In
+the
+body
+of
+a
+JSON-LD
+document,
+the
+value
+of
+<code>
+@type
+</code>
+<em class="rfc2119" title="must not">
+must
+not
+</em>
+be
+<code>
+@id
+</code>.
+This
+is
+in
+contrast
+to
+the
+use
+of
+<code>
+@type
+</code>
+in
+the
+<code>
+@context
+</code>,
+where
+this
+is
+allowed.
+</li>
+</ol>
+</div>
+<div class="appendix informative section" id="relationship-to-other-rdf-formats">
+<h2>
+<span class="secno">
+B.
+</span>
+Relationship
+to
+other
+RDF
+Formats
+</h2>
+<p>
+<em>
+This
+section
+is
+non-normative.
+</em>
+</p>
+<div class="issue">
+<div class="issue-title">
+<span>
+Issue
+6
+</span>
+</div>
+<p class="">
+The
+intent
+of
+the
+Working
+Group
+and
+the
+Editors
+of
+this
+specification
+is
+to
+eventually
+align
+terminology
+used
+in
+this
+document
+with
+the
+terminology
+used
+in
+the
+RDF
+Concepts
+document
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">
+RDF-CONCEPTS
+</a>
+</cite>
+]
+to
+the
+extent
+to
+which
+it
+makes
+sense
+to
+do
+so.
+In
+general,
+if
+there
+is
+an
+analogue
+to
+terminology
+used
+in
+this
+document
+in
+the
+RDF
+Concepts
+document,
+the
+preference
+is
+to
+use
+the
+terminology
+in
+the
+RDF
+Concepts
+document.
+</p>
+</div>
+<p>
+JSON-LD
+is
+a
+specification
+for
+representing
+<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
+Linked
+Data
+</a>
+in
+JSON.
+A
+common
+way
+of
+working
+with
+Linked
+Data
+is
+through
+<dfn title="rdf" id="dfn-rdf">
+RDF
+</dfn>,
+the
+Resource
+Description
+Framework.
+RDF
+can
+be
+expressed
+using
+JSON-LD
+by
+associating
+JSON-LD
+concepts
+such
+as
+<code>
+@id
+</code>
+and
+<code>
+@type
+</code>
+with
+the
+equivalent
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+s
+in
+RDF.
+Further
+information
+about
+RDF
+may
+be
+found
+in
+the
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RDF-PRIMER">
+RDF-PRIMER
+</a>
+</cite>
+].
+</p>
+<p>
+The
+JSON-LD
+markup
+examples
+below
+demonstrate
+how
+JSON-LD
+can
+be
+used
+to
+express
+semantic
+data
+marked
+up
+in
+other
+languages
+and
+data
+models
+such
+as
+RDF,
+Turtle,
+RDFa,
+Microformats,
+and
+Microdata.
+These
+sections
+are
+merely
+provided
+as
+evidence
+that
+JSON-LD
+is
+very
+flexible
+in
+what
+it
+can
+express
+across
+different
+<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">
+Linked
+Data
+</a>
+approaches.
+Further
+information
+on
+transforming
+JSON-LD
+into
+RDF
+are
+detailed
+in
+the
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-JSON-LD-API">
+JSON-LD-API
+</a>
+</cite>
+].
+</p>
+<div id="rdf" class="section">
+<h3>
+<span class="secno">
+B.1
+</span>
+RDF
+</h3>
+<p>
+<em>
+This
+section
+is
+non-normative.
+</em>
+</p>
+<p>
+The
+RDF
+data
+model,
+as
+outlined
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">
+RDF-CONCEPTS
+</a>
+</cite>
+],
+is
+an
+abstract
+syntax
+for
+representing
+a
+directed
+graph
+of
+information.
+JSON-LD
+is
+capable
+of
+serializing
+any
+RDF
+graph,
+and
+performing
+full
+RDF
+to
+JSON-LD
+to
+RDF
+round-tripping.
+A
+complete
+description
+of
+how
+JSON-LD
+maps
+to
+RDF
+and
+algorithms
+detailing
+how
+one
+can
+convert
+from
+RDF
+to
+JSON-LD
+and
+from
+JSON-LD
+to
+RDF
+are
+included
+in
+the
+JSON-LD
+API
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-JSON-LD-API">
+JSON-LD-API
+</a>
+</cite>
+]
+specification.
+</p>
+</div>
+<div id="turtle" class="section">
+<h3>
+<span class="secno">
+B.2
+</span>
+Turtle
+</h3>
+<p>
+The
+following
+are
+examples
+of
+converting
+<a class="tref internalDFN" title="rdf" href="#dfn-rdf">
+RDF
+</a>
+expressed
+in
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-TURTLE-TR">
+TURTLE-TR
+</a>
+</cite>
+]
+into
+JSON-LD.
+</p>
+<div id="prefix-definitions" class="section">
+<h4>
+<span class="secno">
+B.2.1
+</span>
+Prefix
+definitions
+</h4>
+<p>
+<em>
+This
+section
+is
+non-normative.
+</em>
+</p>
+<p>
+The
+JSON-LD
+context
+has
+direct
+equivalents
+for
+the
+Turtle
+<code>
+@prefix
+</code>
+declaration:
+</p>
+<div class="example"><div class="example-title"><span>Example 53</span></div><pre class="example">@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
+&lt;http://manu.sporny.org/i/public&gt; a foaf:Person;
+  foaf:name &quot;Manu Sporny&quot;;
+foaf:homepage
+&lt;http://manu.sporny.org/&gt;
+.
+</pre>
+</div>
+<div class="example"><div class="example-title"><span>Example 54</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;
+  },
+  &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
+  &quot;@type&quot;: &quot;foaf:Person&quot;,
+  &quot;foaf:name&quot;: &quot;Manu Sporny&quot;,
+  &quot;foaf:homepage&quot;: { &quot;@id&quot;: &quot;http://manu.sporny.org/&quot; }
+}
+</pre>
+</div>
+<div class="note">
+<div class="note-title">
+<span>
+Note
+</span>
+</div>
+<div class="">
+<p>
+JSON-LD
+has
+no
+equivalent
+for
+the
+Turtle
+<code>
+@base
+</code>
+declaration.
+Instead,
+authors
+may
+use
+a
+prefix
+definition
+to
+resolve
+<a class="tref internalDFN" title="relative_iri" href="#dfn-relative_iri">
+relative
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>
+s:
+</p>
+<div class="example"><div class="example-title"><span>Example 55</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    <span class="diff">&quot;base&quot;: &quot;http://manu.sporny.org/&quot;,</span>
+    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;
+  },
+  &quot;@id&quot;: <span class="diff">&quot;base:i/public&quot;</span>,
+  &quot;@type&quot;: &quot;foaf:Person&quot;,
+  &quot;foaf:name&quot;: &quot;Manu Sporny&quot;,
+  &quot;foaf:homepage&quot;: { &quot;@id&quot;: <span class="diff">&quot;base&quot; </span>}
+}
+</pre>
+</div>
+</div>
+</div>
+</div>
+<div id="embedding-1" class="section">
+<h4>
+<span class="secno">
+B.2.2
+</span>
+Embedding
+</h4>
+<p>
+Both
+Turtle
+and
+JSON-LD
+allow
+embedding
+of
+objects,
+although
+Turtle
+only
+allows
+embedding
+of
+objects
+which
+use
+<a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">
+unlabeled
+node
+</a>
+identifiers.
+</p>
+</div>
+<div class="example"><div class="example-title"><span>Example 56</span></div><pre class="example">@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
+&lt;http://manu.sporny.org/i/public&gt;
+  a foaf:Person;
+  foaf:name &quot;Manu Sporny&quot;;
+foaf:knows
+[
+a
+foaf:Person;
+foaf:name
+&quot;Gregg
+Kellogg&quot;
+]
+.
+</pre>
+</div>
+<div class="example"><div class="example-title"><span>Example 57</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;
+  },
+  &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
+  &quot;@type&quot;: &quot;foaf:Person&quot;,
+  &quot;foaf:name&quot;: &quot;Manu Sporny&quot;,
+  &quot;foaf:knows&quot;:
+  {
+    &quot;@type&quot;: &quot;foaf:Person&quot;,
+    &quot;foaf:name&quot;: &quot;Gregg Kellogg&quot;
+  }
+}
+</pre>
+</div>
+<div id="lists" class="section">
+<h4>
+<span class="secno">
+B.2.3
+</span>
+Lists
+</h4>
+<p>
+Both
+JSON-LD
+and
+Turtle
+can
+represent
+sequential
+lists
+of
+values.
+</p>
+<div class="example"><div class="example-title"><span>Example 58</span></div><pre class="example">@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
+&lt;http://example.org/people#joebob&gt; a foaf:Person;
+  foaf:name &quot;Joe Bob&quot;;
+foaf:nick
+(
+&quot;joe&quot;
+&quot;bob&quot;
+&quot;jaybee&quot;
+)
+.
+</pre>
+</div>
+<div class="example"><div class="example-title"><span>Example 59</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;
+  },
+  &quot;@id&quot;: &quot;http://example.org/people#joebob&quot;,
+  &quot;@type&quot;: &quot;foaf:Person&quot;,
+  &quot;foaf:name&quot;: &quot;Joe Bob&quot;,
+  &quot;foaf:nick&quot;:
+  {
+    &quot;@list&quot;: [ &quot;joe&quot;, &quot;bob&quot;, &quot;jaybee&quot; ]
+  }
+}
+</pre>
+</div>
+</div>
+</div>
+<div id="rdfa" class="section">
+<h3>
+<span class="secno">
+B.3
+</span>
+RDFa
+</h3>
+<p>
+The
+following
+example
+describes
+three
+people
+with
+their
+respective
+names
+and
+homepages.
+</p>
+<div class="example"><div class="example-title"><span>Example 60</span></div><pre class="example">&lt;div <span class="diff">prefix=&quot;foaf: http://xmlns.com/foaf/0.1/&quot;</span>&gt;
+   &lt;ul&gt;
+      &lt;li <span class="diff">typeof=&quot;foaf:Person&quot;</span>&gt;
+        &lt;a <span class="diff">rel=&quot;foaf:homepage&quot; href=&quot;http://example.com/bob/&quot; property=&quot;foaf:name&quot; </span>&gt;Bob&lt;/a&gt;
+      &lt;/li&gt;
+      &lt;li <span class="diff">typeof=&quot;foaf:Person&quot;</span>&gt;
+        &lt;a <span class="diff">rel=&quot;foaf:homepage&quot; href=&quot;http://example.com/eve/&quot; property=&quot;foaf:name&quot; </span>&gt;Eve&lt;/a&gt;
+      &lt;/li&gt;
+      &lt;li <span class="diff">typeof=&quot;foaf:Person&quot;</span>&gt;
+        &lt;a <span class="diff">rel=&quot;foaf:homepage&quot; href=&quot;http://example.com/manu/&quot; property=&quot;foaf:name&quot; </span>&gt;Manu&lt;/a&gt;
+      &lt;/li&gt;
+   &lt;/ul&gt;
+&lt;/div&gt;
+</pre>
+</div>
+<p>
+An
+example
+JSON-LD
+implementation
+using
+a
+single
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+is
+described
+below.
+</p>
+<div class="example"><div class="example-title"><span>Example 61</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;
+  },
+  &quot;@graph&quot;:
+  [
+    {
+      &quot;@type&quot;: &quot;foaf:Person&quot;,
+      &quot;foaf:homepage&quot;: &quot;http://example.com/bob/&quot;,
+      &quot;foaf:name&quot;: &quot;Bob&quot;
+    },
+    {
+      &quot;@type&quot;: &quot;foaf:Person&quot;,
+      &quot;foaf:homepage&quot;: &quot;http://example.com/eve/&quot;,
+      &quot;foaf:name&quot;: &quot;Eve&quot;
+    },
+    {
+      &quot;@type&quot;: &quot;foaf:Person&quot;,
+      &quot;foaf:homepage&quot;: &quot;http://example.com/manu/&quot;,
+      &quot;foaf:name&quot;: &quot;Manu&quot;
+    }
+  ]
+}
+</pre>
+</div>
+</div>
+<div id="microformats" class="section">
+<h3>
+<span class="secno">
+B.4
+</span>
+Microformats
+</h3>
+<p>
+The
+following
+example
+uses
+a
+simple
+Microformats
+hCard
+example
+to
+express
+how
+the
+Microformat
+is
+represented
+in
+JSON-LD.
+</p>
+<div class="example"><div class="example-title"><span>Example 62</span></div><pre class="example">&lt;div class=&quot;vcard&quot;&gt;
+ &lt;a class=&quot;url fn&quot; href=&quot;http://tantek.com/&quot;&gt;Tantek Çelik&lt;/a&gt;
+&lt;/div&gt;
+</pre>
+</div>
+<p>
+The
+representation
+of
+the
+hCard
+expresses
+the
+Microformat
+terms
+in
+the
+<a class="tref internalDFN" title="context" href="#dfn-context">
+context
+</a>
+and
+uses
+them
+directly
+for
+the
+<code>
+url
+</code>
+and
+<code>
+fn
+</code>
+properties.
+Also
+note
+that
+the
+Microformat
+to
+JSON-LD
+processor
+has
+generated
+the
+proper
+URL
+type
+for
+<code>
+http://tantek.com/
+</code>.
+</p>
+<div class="example"><div class="example-title"><span>Example 63</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;vcard&quot;: &quot;http://microformats.org/profile/hcard#vcard&quot;,
+    &quot;url&quot;:
+    {
+      &quot;@id&quot;: &quot;http://microformats.org/profile/hcard#url&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    },
+    &quot;fn&quot;: &quot;http://microformats.org/profile/hcard#fn&quot;
+  },
+  &quot;@type&quot;: &quot;vcard&quot;,
+  &quot;url&quot;: &quot;http://tantek.com/&quot;,
+  &quot;fn&quot;: &quot;Tantek Çelik&quot;
+}
+</pre>
+</div>
+</div>
+<div id="microdata" class="section">
+<h3>
+<span class="secno">
+B.5
+</span>
+Microdata
+</h3>
+<p>
+The
+microdata
+example
+below
+expresses
+book
+information
+as
+a
+microdata
+Work
+item.
+</p>
+<div class="example"><div class="example-title"><span>Example 64</span></div><pre class="example">&lt;dl itemscope
+    itemtype=&quot;http://purl.org/vocab/frbr/core#Work&quot;
+    itemid=&quot;http://purl.oreilly.com/works/45U8QJGZSQKDH8N&quot;&gt;
+ &lt;dt&gt;Title&lt;/dt&gt;
+ &lt;dd&gt;&lt;cite itemprop=&quot;http://purl.org/dc/terms/title&quot;&gt;Just a Geek&lt;/cite&gt;&lt;/dd&gt;
+ &lt;dt&gt;By&lt;/dt&gt;
+ &lt;dd&gt;&lt;span itemprop=&quot;http://purl.org/dc/terms/creator&quot;&gt;Wil Wheaton&lt;/span&gt;&lt;/dd&gt;
+ &lt;dt&gt;Format&lt;/dt&gt;
+ &lt;dd itemprop=&quot;http://purl.org/vocab/frbr/core#realization&quot;
+     itemscope
+     itemtype=&quot;http://purl.org/vocab/frbr/core#Expression&quot;
+     itemid=&quot;http://purl.oreilly.com/products/9780596007683.BOOK&quot;&gt;
+  &lt;link itemprop=&quot;http://purl.org/dc/terms/type&quot; href=&quot;http://purl.oreilly.com/product-types/BOOK&quot;&gt;
+  Print
+ &lt;/dd&gt;
+ &lt;dd itemprop=&quot;http://purl.org/vocab/frbr/core#realization&quot;
+     itemscope
+     itemtype=&quot;http://purl.org/vocab/frbr/core#Expression&quot;
+     itemid=&quot;http://purl.oreilly.com/products/9780596802189.EBOOK&quot;&gt;
+  &lt;link itemprop=&quot;http://purl.org/dc/terms/type&quot; href=&quot;http://purl.oreilly.com/product-types/EBOOK&quot;&gt;
+  Ebook
+ &lt;/dd&gt;
+&lt;/dl&gt;
+</pre>
+</div>
+<p>
+Note
+that
+the
+JSON-LD
+representation
+of
+the
+Microdata
+information
+stays
+true
+to
+the
+desires
+of
+the
+Microdata
+community
+to
+avoid
+contexts
+and
+instead
+refer
+to
+items
+by
+their
+full
+<a class="tref internalDFN" title="iri" href="#dfn-iri">
+<abbr title="Internationalized Resource Identifier">
+IRI
+</abbr>
+</a>.
+</p>
+<div class="example"><div class="example-title"><span>Example 65</span></div><pre class="example">[
+  {
+    &quot;@id&quot;: &quot;http://purl.oreilly.com/works/45U8QJGZSQKDH8N&quot;,
+    &quot;@type&quot;: &quot;http://purl.org/vocab/frbr/core#Work&quot;,
+    &quot;http://purl.org/dc/terms/title&quot;: &quot;Just a Geek&quot;,
+    &quot;http://purl.org/dc/terms/creator&quot;: &quot;Whil Wheaton&quot;,
+    &quot;http://purl.org/vocab/frbr/core#realization&quot;:
+    [
+      &quot;http://purl.oreilly.com/products/9780596007683.BOOK&quot;,
+      &quot;http://purl.oreilly.com/products/9780596802189.EBOOK&quot;
+    ]
+  },
+  {
+    &quot;@id&quot;: &quot;http://purl.oreilly.com/products/9780596007683.BOOK&quot;,
+    &quot;@type&quot;: &quot;http://purl.org/vocab/frbr/core#Expression&quot;,
+    &quot;http://purl.org/dc/terms/type&quot;: &quot;http://purl.oreilly.com/product-types/BOOK&quot;
+  },
+  {
+    &quot;@id&quot;: &quot;http://purl.oreilly.com/products/9780596802189.EBOOK&quot;,
+    &quot;@type&quot;: &quot;http://purl.org/vocab/frbr/core#Expression&quot;,
+    &quot;http://purl.org/dc/terms/type&quot;: &quot;http://purl.oreilly.com/product-types/EBOOK&quot;
+  }
+]
+</pre>
+</div>
+</div>
+</div>
+<div class="appendix informative section" id="iana-considerations">
+<h2>
+<span class="secno">
+C.
+</span>
+IANA
+Considerations
+</h2>
+<p>
+<em>
+This
+section
+is
+non-normative.
+</em>
+</p>
+<p>
+This
+section
+is
+included
+merely
+for
+standards
+community
+review
+and
+will
+be
+submitted
+to
+the
+Internet
+Engineering
+Steering
+Group
+if
+this
+specification
+becomes
+a
+<acronym title="World Wide Web Consortium">
+W3C
+</acronym>
+Recommendation.
+</p>
+<h2 id="application-ld-json">
+application/ld+json
+</h2>
+<dl>
+<dt>
+Type
+name:
+</dt>
+<dd>
+application
+</dd>
+<dt>
+Subtype
+name:
+</dt>
+<dd>
+ld+json
+</dd>
+<dt>
+Required
+parameters:
+</dt>
+<dd>
+None
+</dd>
+<dt>
+Optional
+parameters:
+</dt>
+<dd>
+<dl>
+<dt>
+<code>
+form
+</code>
+</dt>
+<dd>
+Determines
+the
+serialization
+form
+for
+the
+JSON-LD
+document.
+The
+only
+valid
+value
+at
+the
+moment
+is
+<code>
+expanded
+</code>.
+If
+no
+form
+is
+specified
+in
+an
+HTTP
+request
+header
+to
+an
+HTTP
+server,
+the
+server
+<em class="rfc2119" title="may">
+may
+</em>
+choose
+any
+form.
+If
+no
+form
+is
+specified
+in
+an
+HTTP
+response,
+the
+form
+<em class="rfc2119" title="must not">
+must
+not
+</em>
+be
+assumed
+to
+take
+any
+particular
+form.
+</dd>
+</dl>
+</dd>
+<dt>
+Encoding
+considerations:
+</dt>
+<dd>
+The
+same
+as
+the
+<code>
+application/json
+</code>
+MIME
+media
+type.
+</dd>
+<dt>
+Security
+considerations:
+</dt>
+<dd>
+Since
+JSON-LD
+is
+intended
+to
+be
+a
+pure
+data
+exchange
+format
+for
+directed
+graphs,
+the
+serialization
+<em class="rfc2119" title="should not">
+should
+not
+</em>
+be
+passed
+through
+a
+code
+execution
+mechanism
+such
+as
+JavaScript's
+<code>
+eval()
+</code>
+function.
+It
+is
+<em class="rfc2119" title="recommended">
+recommended
+</em>
+that
+a
+conforming
+parser
+does
+not
+attempt
+to
+directly
+evaluate
+the
+JSON-LD
+serialization
+and
+instead
+purely
+parse
+the
+input
+into
+a
+language-native
+data
+structure.
+</dd>
+<dt>
+Interoperability
+considerations:
+</dt>
+<dd>
+Not
+Applicable
+</dd>
+<dt>
+Published
+specification:
+</dt>
+<dd>
+The
+<a href="http://json-ld.org/spec/latest/">
+JSON-LD
+</a>
+specification.
+</dd>
+<dt>
+Applications
+that
+use
+this
+media
+type:
+</dt>
+<dd>
+Any
+programming
+environment
+that
+requires
+the
+exchange
+of
+directed
+graphs.
+Implementations
+of
+JSON-LD
+have
+been
+created
+for
+JavaScript,
+Python,
+Ruby,
+PHP
+and
+C++.
+</dd>
+<dt>
+Additional
+information:
+</dt>
+<dd>
+<dl>
+<dt>
+Magic
+number(s):
+</dt>
+<dd>
+Not
+Applicable
+</dd>
+<dt>
+File
+extension(s):
+</dt>
+<dd>.jsonld
+</dd>
+<dt>
+Macintosh
+file
+type
+code(s):
+</dt>
+<dd>
+TEXT
+</dd>
+</dl>
+</dd>
+<dt>
+Person
+&amp;
+email
+address
+to
+contact
+for
+further
+information:
+</dt>
+<dd>
+Manu
+Sporny
+&lt;msporny@digitalbazaar.com&gt;
+</dd>
+<dt>
+Intended
+usage:
+</dt>
+<dd>
+Common
+</dd>
+<dt>
+Restrictions
+on
+usage:
+</dt>
+<dd>
+None
+</dd>
+<dt>
+Author(s):
+</dt>
+<dd>
+Manu
+Sporny,
+Gregg
+Kellogg,
+Markus
+Lanthaler,
+Dave
+Longley
+</dd>
+<dt>
+Change
+controller:
+</dt>
+<dd>
+<acronym title="World Wide Web Consortium">
+W3C
+</acronym>
+</dd>
+</dl>
+<p>
+Fragment
+identifiers
+used
+with
+<a href="#application-ld-json">
+application/ld+json
+</a>
+resources
+<em class="rfc2119" title="may">
+may
+</em>
+identify
+a
+node
+in
+the
+<a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">
+linked
+data
+graph
+</a>
+expressed
+in
+the
+resource.
+This
+idiom,
+which
+is
+also
+used
+in
+RDF
+[
+<cite>
+<a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">
+RDF-CONCEPTS
+</a>
+</cite>
+],
+gives
+a
+simple
+way
+to
+&quot;mint&quot;
+new,
+document-local
+IRIs
+to
+label
+nodes
+and
+therefore
+contributes
+considerably
+to
+the
+expressive
+power
+of
+JSON-LD.
+</p>
+</div>
+<div class="appendix informative section" id="acknowledgements">
+<h2>
+<span class="secno">
+D.
+</span>
+Acknowledgements
+</h2>
+<p>
+<em>
+This
+section
+is
+non-normative.
+</em>
+</p>
+<p>
+The
+editors
+would
+like
+to
+thank
+Mark
+Birbeck,
+who
+provided
+a
+great
+deal
+of
+the
+initial
+push
+behind
+the
+JSON-LD
+work
+via
+his
+work
+on
+RDFj,
+Dave
+Lehn
+and
+Mike
+Johnson
+who
+reviewed,
+provided
+feedback,
+and
+performed
+several
+implementations
+of
+the
+specification,
+and
+Ian
+Davis,
+who
+created
+RDF/JSON.
+Thanks
+also
+to
+Nathan
+Rixham,
+Bradley
+P.
+Allen,
+Kingsley
+Idehen,
+Glenn
+McDonald,
+Alexandre
+Passant,
+Danny
+Ayers,
+Ted
+Thibodeau
+Jr.,
+Olivier
+Grisel,
+Josh
+Mandel,
+Eric
+Prud'hommeaux,
+David
+Wood,
+Guus
+Schreiber,
+Pat
+Hayes,
+Sandro
+Hawke,
+and
+Richard
+Cyganiak
+for
+their
+input
+on
+the
+specification.
+</p>
+</div>
+<div id="references" class="appendix section">
+<h2>
+<span class="secno">
+E.
+</span>
+References
+</h2>
+<div id="normative-references" class="section">
+<h3>
+<span class="secno">
+E.1
+</span>
+Normative
+references
+</h3>
+<dl class="bibliography">
+<dt id="bib-BCP47">
+[BCP47]
+</dt>
+<dd>
+A.
+Phillips;
+M.
+Davis.
+<a href="http://tools.ietf.org/html/bcp47">
+<cite>
+Tags
+for
+Identifying
+Languages
+</cite>
+</a>
+September
+2009.
+IETF
+Best
+Current
+Practice.
+URL:
+<a href="http://tools.ietf.org/html/bcp47">
+http://tools.ietf.org/html/bcp47
+</a>
+</dd>
+<dt id="bib-JSON-LD-API">
+[JSON-LD-API]
+</dt>
+<dd>
+<cite>
+<a href="http://json-ld.org/spec/ED/json-ld-api/20120524/">
+The
+JSON-LD
+API
+1.0
+</a>
+</cite>
+Manu
+Sporny,
+Gregg
+Kellogg,
+Dave
+Longley,
+Markus
+Lanthaler,
+Editors.
+World
+Wide
+Web
+Consortium
+(work
+in
+progress).
+24
+May
+2012.
+Editor's
+Draft.
+This
+edition
+of
+the
+JSON-LD
+Syntax
+specification
+is
+http://json-ld.org/spec/ED/json-ld-api/20120524/.
+The
+<a href="http://json-ld.org/spec/latest/json-ld-api/">
+latest
+edition
+of
+the
+JSON-LD
+Syntax
+</a>
+is
+available
+at
+http://json-ld.org/spec/latest/json-ld-api/
+</dd>
+<dt id="bib-RDF-CONCEPTS">
+[RDF-CONCEPTS]
+</dt>
+<dd>
+<cite>
+<a href="http://www.w3.org/TR/2011/WD-rdf11-concepts-20110830/">
+RDF
+1.1
+Concepts
+and
+Abstract
+Syntax
+</a>
+</cite>
+Richard
+Cyganiak,
+David
+Wood,
+Editors.
+World
+Wide
+Web
+Consortium
+(work
+in
+progress).
+30
+May
+2012.
+Editor's
+Draft.
+This
+edition
+of
+the
+JSON-LD
+Syntax
+specification
+is
+http://www.w3.org/TR/2011/WD-rdf11-concepts-20110830/.
+The
+<a href="http://www.w3.org/TR/rdf11-concepts/">
+latest
+edition
+of
+the
+JSON-LD
+Syntax
+</a>
+is
+available
+at
+http://www.w3.org/TR/rdf11-concepts/
+</dd>
+<dt id="bib-RFC3987">
+[RFC3987]
+</dt>
+<dd>
+M.
+Dürst;
+M.
+Suignard.
+<a href="http://www.ietf.org/rfc/rfc3987.txt">
+<cite>
+Internationalized
+Resource
+Identifiers
+(IRIs).
+</cite>
+</a>
+January
+2005.
+Internet
+RFC
+3987.
+URL:
+<a href="http://www.ietf.org/rfc/rfc3987.txt">
+http://www.ietf.org/rfc/rfc3987.txt
+</a>
+</dd>
+<dt id="bib-RFC4627">
+[RFC4627]
+</dt>
+<dd>
+D.
+Crockford.
+<a href="http://www.ietf.org/rfc/rfc4627.txt">
+<cite>
+The
+application/json
+Media
+Type
+for
+JavaScript
+Object
+Notation
+(JSON)
+</cite>
+</a>
+July
+2006.
+Internet
+RFC
+4627.
+URL:
+<a href="http://www.ietf.org/rfc/rfc4627.txt">
+http://www.ietf.org/rfc/rfc4627.txt
+</a>
+</dd>
+<dt id="bib-RFC5988">
+[RFC5988]
+</dt>
+<dd>
+<cite>
+<a href="http://tools.ietf.org/rfc/rfc5988">
+Web
+Linking
+</a>
+</cite>
+M.
+Nottingham.
+Editor.
+October
+2010.
+IETF
+Standard.
+URL:
+<a href="http://tools.ietf.org/rfc/rfc5988.txt">
+http://tools.ietf.org/rfc/rfc5988.txt
+</a>
+</dd>
+</dl>
+</div>
+<div id="informative-references" class="section">
+<h3>
+<span class="secno">
+E.2
+</span>
+Informative
+references
+</h3>
+<dl class="bibliography">
+<dt id="bib-RDF-PRIMER">
+[RDF-PRIMER]
+</dt>
+<dd>
+Frank
+Manola;
+Eric
+Miller.
+<a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/">
+<cite>
+RDF
+Primer.
+</cite>
+</a>
+10
+February
+2004.
+W3C
+Recommendation.
+URL:
+<a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/">
+http://www.w3.org/TR/2004/REC-rdf-primer-20040210/
+</a>
+</dd>
+<dt id="bib-RDFA-CORE">
+[RDFA-CORE]
+</dt>
+<dd>
+Shane
+McCarron;
+et
+al.
+<a href="http://www.w3.org/TR/2012/REC-rdfa-core-20120508/">
+<cite>
+RDFa
+Core
+1.1:
+Syntax
+and
+processing
+rules
+for
+embedding
+RDF
+through
+attributes.
+</cite>
+</a>
+7
+June
+2012.
+W3C
+Recommendation.
+URL:
+<a href="http://www.w3.org/TR/2012/REC-rdfa-core-20120607/">
+http://www.w3.org/TR/2012/REC-rdfa-core-20120607/
+</a>
+</dd>
+<dt id="bib-TURTLE-TR">
+[TURTLE-TR]
+</dt>
+<dd>
+Eric
+Prud'hommeaux,
+Gavin
+Carothers.
+<cite>
+<a href="http://www.w3.org/TR/2011/WD-turtle-20110809/">
+Turtle:
+Terse
+RDF
+Triple
+Language.
+</a>
+</cite>
+09
+August
+2011.
+W3C
+Working
+Draft.
+URL:
+<a href="http://www.w3.org/TR/2011/WD-turtle-20110809/">
+http://www.w3.org/TR/2011/WD-turtle-20110809/
+</a>
+</dd>
+</dl>
+</div>
+</div>
+</body>
+</html>

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/spec/WD/json-ld-syntax/20120712/index.html	Tue Jun 26 23:49:05 2012 -0400
@@ -0,0 +1,2868 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.1//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd">
+<html dir="ltr" xmlns="http://www.w3.org/1999/xhtml" typeof="bibo:Document">
+<head>
+<title>JSON-LD Syntax 1.0</title>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+
+<!-- 
+  === NOTA BENE ===
+  For the three scripts below, if your spec resides on dev.w3 you can check them
+  out in the same tree and use relative links so that they'll work offline,
+   -->
+
+
+
+<style type="text/css">
+.diff { font-weight:bold; color:#0a3; }
+</style>
+<style type="text/css">/*****************************************************************
+ * ReSpec 3 CSS
+ * Robin Berjon - http://berjon.com/
+ *****************************************************************/
+
+/* --- INLINES --- */
+em.rfc2119 { 
+    text-transform:     lowercase;
+    font-variant:       small-caps;
+    font-style:         normal;
+    color:              #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+    border: none;
+}
+
+dfn {
+    font-weight:    bold;
+}
+
+a.internalDFN {
+    color:  inherit;
+    border-bottom:  1px solid #99c;
+    text-decoration:    none;
+}
+
+a.externalDFN {
+    color:  inherit;
+    border-bottom:  1px dotted #ccc;
+    text-decoration:    none;
+}
+
+a.bibref {
+    text-decoration:    none;
+}
+
+cite .bibref {
+    font-style: normal;
+}
+
+code {
+    color:  #ff4500;
+}
+
+
+/* --- --- */
+ol.algorithm { counter-reset:numsection; list-style-type: none; }
+ol.algorithm li { margin: 0.5em 0; }
+ol.algorithm li:before { font-weight: bold; counter-increment: numsection; content: counters(numsection, ".") ") "; }
+
+
+/* --- WEB IDL --- */
+pre.idl {
+    border-top: 1px solid #90b8de;
+    border-bottom: 1px solid #90b8de;
+    padding:    1em;
+    line-height:    120%;
+}
+
+pre.idl::before {
+    content:    "WebIDL";
+    display:    block;
+    width:      150px;
+    background: #90b8de;
+    color:  #fff;
+    font-family:    initial;
+    padding:    3px;
+    font-weight:    bold;
+    margin: -1em 0 1em -1em;
+}
+
+.idlType {
+    color:  #ff4500;
+    font-weight:    bold;
+    text-decoration:    none;
+}
+
+/*.idlModule*/
+/*.idlModuleID*/
+/*.idlInterface*/
+.idlInterfaceID, .idlDictionaryID, .idlCallbackID, .idlEnumID {
+    font-weight:    bold;
+    color:  #005a9c;
+}
+
+.idlSuperclass {
+    font-style: italic;
+    color:  #005a9c;
+}
+
+/*.idlAttribute*/
+.idlAttrType, .idlFieldType, .idlMemberType {
+    color:  #005a9c;
+}
+.idlAttrName, .idlFieldName, .idlMemberName {
+    color:  #ff4500;
+}
+.idlAttrName a, .idlFieldName a, .idlMemberName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlMethod*/
+.idlMethType, .idlCallbackType {
+    color:  #005a9c;
+}
+.idlMethName {
+    color:  #ff4500;
+}
+.idlMethName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlParam*/
+.idlParamType {
+    color:  #005a9c;
+}
+.idlParamName {
+    font-style: italic;
+}
+
+.extAttr {
+    color:  #666;
+}
+
+/*.idlConst*/
+.idlConstType {
+    color:  #005a9c;
+}
+.idlConstName {
+    color:  #ff4500;
+}
+.idlConstName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlException*/
+.idlExceptionID {
+    font-weight:    bold;
+    color:  #c00;
+}
+
+.idlTypedefID, .idlTypedefType {
+    color:  #005a9c;
+}
+
+.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
+    color:  #c00;
+    font-weight:    normal;
+}
+
+.excName a {
+    font-family:    monospace;
+}
+
+.idlRaises a.idlType, .excName a.idlType {
+    border-bottom:  1px dotted #c00;
+}
+
+.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
+    width:  45px;
+    text-align: center;
+}
+.excGetSetTrue, .prmNullTrue, .prmOptTrue { color:  #0c0; }
+.excGetSetFalse, .prmNullFalse, .prmOptFalse { color:  #c00; }
+
+.idlImplements a {
+    font-weight:    bold;
+}
+
+dl.attributes, dl.methods, dl.constants, dl.fields, dl.dictionary-members {
+    margin-left:    2em;
+}
+
+.attributes dt, .methods dt, .constants dt, .fields dt, .dictionary-members dt {
+    font-weight:    normal;
+}
+
+.attributes dt code, .methods dt code, .constants dt code, .fields dt code, .dictionary-members dt code {
+    font-weight:    bold;
+    color:  #000;
+    font-family:    monospace;
+}
+
+.attributes dt code, .fields dt code, .dictionary-members dt code {
+    background:  #ffffd2;
+}
+
+.attributes dt .idlAttrType code, .fields dt .idlFieldType code, .dictionary-members dt .idlMemberType code {
+    color:  #005a9c;
+    background:  transparent;
+    font-family:    inherit;
+    font-weight:    normal;
+    font-style: italic;
+}
+
+.methods dt code {
+    background:  #d9e6f8;
+}
+
+.constants dt code {
+    background:  #ddffd2;
+}
+
+.attributes dd, .methods dd, .constants dd, .fields dd, .dictionary-members dd {
+    margin-bottom:  1em;
+}
+
+table.parameters, table.exceptions {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    margin: 0.5em 0;
+    width:  100%;
+}
+table.parameters { border-bottom:  1px solid #90b8de; }
+table.exceptions { border-bottom:  1px solid #deb890; }
+
+.parameters th, .exceptions th {
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+    font-family:    initial;
+    font-weight:    normal;
+    text-shadow:    #666 1px 1px 0;
+}
+.parameters th { background: #90b8de; }
+.exceptions th { background: #deb890; }
+
+.parameters td, .exceptions td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+    vertical-align: top;
+}
+
+.parameters tr:first-child td, .exceptions tr:first-child td {
+    border-top: none;
+}
+
+.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
+    width:  100px;
+}
+
+.parameters td.prmType {
+    width:  120px;
+}
+
+table.exceptions table {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    width:  100%;
+}
+
+/* --- TOC --- */
+.toc a, .tof a {
+    text-decoration:    none;
+}
+
+a .secno, a .figno {
+    color:  #000;
+}
+
+ul.tof, ol.tof {
+    list-style: none outside none;
+}
+
+.caption {
+    margin-top: 0.5em;
+    font-style:   italic;
+}
+
+/* --- TABLE --- */
+table.simple {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    border-bottom:  3px solid #005a9c;
+}
+
+.simple th {
+    background: #005a9c;
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+}
+
+.simple th[scope="row"] {
+    background: inherit;
+    color:  inherit;
+    border-top: 1px solid #ddd;
+}
+
+.simple td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+    background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+    margin-top: 0;
+}
+
+.section dd > p:last-child {
+    margin-bottom: 0;
+}
+
+.section dd {
+    margin-bottom:  1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+    margin-bottom:  0;
+}
+</style><style type="text/css">/* --- EXAMPLES --- */
+div.example-title {
+    min-width: 7.5em;
+    color: #b9ab2d;
+}
+div.example-title span {
+    text-transform: uppercase;   
+}
+div.example, div.illegal-example {
+    padding: 0.5em;
+    margin: 1em 0;
+    position: relative;
+    clear: both;
+}
+div.illegal-example { color: red }
+div.illegal-example p { color: black }
+div.example {
+    padding: .5em;
+    border-left-width: .5em;
+    border-left-style: solid;
+    border-color: #e0cb52;
+    background: #fcfaee;    
+}
+</style><style type="text/css">/* --- ISSUES/NOTES --- */
+div.issue-title, div.note-title {
+    padding-right:  1em;
+    min-width: 7.5em;
+    color: #b9ab2d;
+}
+div.issue-title { color: #e05252; }
+div.note-title { color: #52e052; }
+div.issue-title span, div.note-title span {
+    text-transform: uppercase;
+}
+div.note, div.issue {
+    margin-top: 1em;
+    margin-bottom: 1em;
+}
+.note > p:first-child, .issue > p:first-child { margin-top: 0 }
+.issue, .note {
+    padding: .5em;
+    border-left-width: .5em;
+    border-left-style: solid;
+}
+div.issue, div.note {
+    padding: 0.5em;
+    margin: 1em 0;
+    position: relative;
+    clear: both;
+}
+span.note, span.issue { padding: .1em .5em .15em; }
+
+.issue {
+    border-color: #e05252;
+    background: #fbe9e9;
+}
+.note {
+    border-color: #52e052;
+    background: #e9fbe9;
+}
+
+
+</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD" /><script type="text/javascript" src="http://s3.amazonaws.com/green-turtle/RDFa.0.15.0.js"></script><meta name="green-turtle-rdfa-message" content="{ &quot;type&quot;: &quot;status&quot;, &quot;loaded&quot;: true, &quot;count&quot;: 44 }" /></head>
+
+<body><div class="head">
+  <p>
+    
+      <a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C" /></a>
+    
+  </p>
+  <h1 class="title" id="title">JSON-LD Syntax 1.0</h1>
+  
+    <h2 id="subtitle">A Context-based JSON Serialization for Linking Data</h2>
+  
+  <h2 id="w3c-working-draft-12-july-2012"><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 12 July 2012</h2>
+  <dl>
+    
+      <dt>This version:</dt>
+      <dd><a href="http://www.w3.org/TR/2012/WD-json-ld-syntax-20120712/">http://www.w3.org/TR/2012/WD-json-ld-syntax-20120712/</a></dd>
+      <dt>Latest published version:</dt>
+      <dd><a href="http://www.w3.org/TR/json-ld-syntax/">http://www.w3.org/TR/json-ld-syntax/</a></dd>
+    
+    
+      <dt>Latest editor's draft:</dt>
+      <dd><a href="http://dvcs.w3.org/hg/json-ld/raw-file/default/spec/latest/json-ld-syntax/index.html">http://dvcs.w3.org/hg/json-ld/raw-file/default/spec/latest/json-ld-syntax/index.html</a></dd>
+    
+    
+    
+    
+    
+    
+    <dt>Editors:</dt>
+    <dd rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="http://manu.sporny.org/">Manu Sporny</a>, <a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">Digital Bazaar</a></span>
+</dd>
+<dd rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Gregg Kellogg" href="http://greggkellogg.net/">Gregg Kellogg</a>, <a rel="foaf:workplaceHomepage" href="http://kellogg-assoc.com/">Kellogg Associates</a></span>
+</dd>
+<dd rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Markus Lanthaler" href="http://www.markus-lanthaler.com/">Markus Lanthaler</a>, <a rel="foaf:workplaceHomepage" href="http://www.tugraz.at/">Graz University of Technology</a></span>
+</dd>
+
+    
+      <dt>Authors:</dt>
+      <dd rel="dcterms:contributor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="http://digitalbazaar.com/">Manu Sporny</a>, <a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">Digital Bazaar</a></span>
+</dd>
+<dd rel="dcterms:contributor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Dave Longley" href="http://digitalbazaar.com/">Dave Longley</a>, <a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">Digital Bazaar</a></span>
+</dd>
+<dd rel="dcterms:contributor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Gregg Kellogg" href="http://greggkellogg.net/">Gregg Kellogg</a>, <a rel="foaf:workplaceHomepage" href="http://kellogg-assoc.com/">Kellogg Associates</a></span>
+</dd>
+<dd rel="dcterms:contributor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Markus Lanthaler" href="http://www.markus-lanthaler.com/">Markus Lanthaler</a>, <a rel="foaf:workplaceHomepage" href="http://www.tugraz.at/">Graz University of Technology</a></span>
+</dd>
+<dd rel="dcterms:contributor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Mark Birbeck" href="http://webbackplane.com/">Mark Birbeck</a>, <a rel="foaf:workplaceHomepage" href="http://webbackplane.com/">Backplane Ltd.</a></span>
+</dd>
+
+    
+  </dl>
+  
+  
+    <p>
+      
+        This document is also available in this non-normative format: 
+      
+      <a href="diff-20120626.html">diff to previous version</a>
+    </p>
+  
+  
+  
+    
+      <p class="copyright">
+        <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 
+        2010-2012
+        
+        <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> 
+        (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>,
+        <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
+        <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved.
+        <acronym title="World Wide Web Consortium">W3C</acronym> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
+        <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
+        <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
+      </p>
+    
+  
+  <hr />
+</div>
+<div id="abstract" class="introductory section"><h2>Abstract</h2>
+<p>
+JSON has proven to be a highly useful object serialization and messaging format.
+In an attempt to harmonize the representation of <a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">Linked Data</a>
+in JSON, this specification outlines a common JSON representation format for
+expressing directed graphs; mixing both Linked Data and non-Linked Data in
+a single document.
+</p>
+</div><div id="sotd" class="introductory section"><h2>Status of This Document</h2>
+  
+    
+      
+        <p>
+          <em>This section describes the status of this document at the time of its publication. Other
+          documents may supersede this document. A list of current <acronym title="World Wide Web Consortium">W3C</acronym> publications and the latest revision
+          of this technical report can be found in the <a href="http://www.w3.org/TR/"><acronym title="World Wide Web Consortium">W3C</acronym> technical reports
+          index</a> at http://www.w3.org/TR/.</em>
+        </p>
+        
+<p>This document has been under development for over 18 months in the
+JSON for Linking Data Community Group. The document has recently been
+transferred to the RDF Working Group for review, improvement, and publication 
+along the Recommendation track. While this is a First Public Working Draft
+publication, the specification has undergone significant development, review, 
+and changes during the course of the last 18 months and is more mature than
+the First Public Working Draft status implies.
+</p>
+<p>
+There are currently
+<a href="http://json-ld.org/#impl">five interoperable implementations</a>
+of this specification. There is
+a <a href="https://github.com/json-ld/json-ld.org/tree/master/test-suite">fairly complete test suite</a>
+and a
+<a href="http://json-ld.org/playground/">live JSON-LD editor</a>
+that is capable of demonstrating the features described in
+this document. While development on implementations, the test suite
+and the live editor will continue, they are believed to be mature enough
+to be integrated into a non-production system at this point in time with
+the expectation that they could be used in a production system within the
+next year.
+</p>
+
+<p>There are a number of ways that one may participate in the development of
+this specification:</p>
+
+<ul>
+  <li>If you want to make sure that your feedback is formally addressed by
+    the RDF Working Group, you should send it to public-rdf-comments:
+    <a href="http://lists.w3.org/Archives/Public/public-rdf-comments/">public-rdf-comments@w3.org</a></li>
+
+  <li>Ad-hoc technical discussion primarily occurs on the public community mailing list:
+    <a href="http://lists.w3.org/Archives/Public/public-linked-json/">public-linked-json@w3.org</a></li>
+
+  <li><a href="http://json-ld.org/minutes/">Public JSON-LD Community Group teleconferences</a>
+  are held on Tuesdays at 1500UTC every week.</li>
+
+  <li>RDF Working Group teleconferences are held on Wednesdays at 1500UTC
+  every week. Participation is limited to RDF Working Group members.</li>
+
+  <li>Specification bugs and issues should be reported in the
+    <a href="https://github.com/json-ld/json-ld.org/issues">issue tracker</a>
+    if you do not want to send an e-mail to the public-rdf-comments mailing
+    list.</li>
+
+  <li><a href="https://github.com/json-ld/json-ld.org/tree/master/spec">Source code</a>
+    for the specification can be found on Github.</li>
+
+  <li>The <a href="http://webchat.freenode.net/?channels=json-ld">#json-ld</a>
+    IRC channel is available for real-time discussion on irc.freenode.net.</li>
+</ul>
+
+
+        <p>
+          This document was published by the <a href="http://www.w3.org/2011/rdf-wg/">RDF Working Group</a> as a First Public Working Draft.
+          
+            This document is intended to become a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation.
+          
+          If you wish to make comments regarding this document, please send them to 
+          <a href="mailto:public-rdf-comments@w3.org">public-rdf-comments@w3.org</a> 
+          (<a href="mailto:public-rdf-comments-request@w3.org?subject=subscribe">subscribe</a>,
+          <a href="http://lists.w3.org/Archives/Public/public-rdf-comments/">archives</a>).
+          
+          
+          All feedback is welcome.
+        </p>
+        
+          <p>
+            Publication as a Working Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership.
+            This is a draft document and may be updated, replaced or obsoleted by other documents at 
+            any time. It is inappropriate to cite this document as other than work in progress.
+          </p>
+        
+        
+        <p>
+          
+            This document was produced by a group operating under the 
+            <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.
+          
+          
+          
+            
+              <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="http://www.w3.org/2004/01/pp-impl/46168/status" rel="disclosure">public list of any patent disclosures</a> 
+            
+            made in connection with the deliverables of the group; that page also includes instructions for 
+            disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains
+            <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the
+            information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
+            6 of the <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.
+          
+          
+        </p>
+        
+      
+    
+  
+</div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#how-to-read-this-document" class="tocxref"><span class="secno">1.1 </span>How to Read this Document</a></li></ul></li><li class="tocline"><a href="#design-goals-and-rationale" class="tocxref"><span class="secno">2. </span>Design Goals and Rationale</a></li><li class="tocline"><a href="#basic-concepts" class="tocxref"><span class="secno">3. </span>Basic Concepts</a><ul class="toc"><li class="tocline"><a href="#linking-data" class="tocxref"><span class="secno">3.1 </span>Linking Data</a><ul class="toc"><li class="tocline"><a href="#syntax-tokens-and-keywords" class="tocxref"><span class="secno">3.1.1 </span>Syntax Tokens and Keywords</a></li><li class="tocline"><a href="#the-context" class="tocxref"><span class="secno">3.1.2 </span>The Context</a></li><li class="tocline"><a href="#from-json-to-json-ld" class="tocxref"><span class="secno">3.1.3 </span>From JSON to JSON-LD</a></li></ul></li><li class="tocline"><a href="#iris" class="tocxref"><span class="secno">3.2 </span>IRIs</a></li><li class="tocline"><a href="#identifying-the-subject" class="tocxref"><span class="secno">3.3 </span>Identifying the Subject</a></li><li class="tocline"><a href="#specifying-the-type" class="tocxref"><span class="secno">3.4 </span>Specifying the Type</a></li><li class="tocline"><a href="#string-internationalization" class="tocxref"><span class="secno">3.5 </span>String Internationalization</a></li><li class="tocline"><a href="#json-ld-syntax" class="tocxref"><span class="secno">3.6 </span>JSON-LD Syntax</a></li></ul></li><li class="tocline"><a href="#advanced-concepts" class="tocxref"><span class="secno">4. </span>Advanced Concepts</a><ul class="toc"><li class="tocline"><a href="#compact-iris" class="tocxref"><span class="secno">4.1 </span>Compact IRIs</a></li><li class="tocline"><a href="#typed-values" class="tocxref"><span class="secno">4.2 </span>Typed Values</a></li><li class="tocline"><a href="#external-contexts" class="tocxref"><span class="secno">4.3 </span>External Contexts</a></li><li class="tocline"><a href="#referencing-contexts-from-json-documents" class="tocxref"><span class="secno">4.4 </span>Referencing Contexts from JSON Documents</a></li><li class="tocline"><a href="#expanded-term-definition" class="tocxref"><span class="secno">4.5 </span>Expanded Term Definition</a></li><li class="tocline"><a href="#type-coercion" class="tocxref"><span class="secno">4.6 </span>Type Coercion</a></li><li class="tocline"><a href="#iri-expansion-within-a-context" class="tocxref"><span class="secno">4.7 </span><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion Within a Context</a></li><li class="tocline"><a href="#sets-and-lists" class="tocxref"><span class="secno">4.8 </span>Sets and Lists</a></li><li class="tocline"><a href="#embedding" class="tocxref"><span class="secno">4.9 </span>Embedding</a></li><li class="tocline"><a href="#named-graphs" class="tocxref"><span class="secno">4.10 </span>Named Graphs</a></li><li class="tocline"><a href="#identifying-unlabeled-nodes" class="tocxref"><span class="secno">4.11 </span>Identifying Unlabeled Nodes</a></li><li class="tocline"><a href="#aliasing-keywords" class="tocxref"><span class="secno">4.12 </span>Aliasing Keywords</a></li><li class="tocline"><a href="#expanded-document-form" class="tocxref"><span class="secno">4.13 </span>Expanded Document Form</a></li><li class="tocline"><a href="#compact-document-form" class="tocxref"><span class="secno">4.14 </span>Compact Document Form</a></li></ul></li><li class="tocline"><a href="#json-ld-authoring-guidelines" class="tocxref"><span class="secno">A. </span>JSON-LD Authoring Guidelines</a></li><li class="tocline"><a href="#relationship-to-other-rdf-formats" class="tocxref"><span class="secno">B. </span>Relationship to other RDF Formats</a><ul class="toc"><li class="tocline"><a href="#rdf" class="tocxref"><span class="secno">B.1 </span>RDF</a></li><li class="tocline"><a href="#turtle" class="tocxref"><span class="secno">B.2 </span>Turtle</a><ul class="toc"><li class="tocline"><a href="#prefix-definitions" class="tocxref"><span class="secno">B.2.1 </span>Prefix definitions</a></li><li class="tocline"><a href="#embedding-1" class="tocxref"><span class="secno">B.2.2 </span>Embedding</a></li><li class="tocline"><a href="#lists" class="tocxref"><span class="secno">B.2.3 </span>Lists</a></li></ul></li><li class="tocline"><a href="#rdfa" class="tocxref"><span class="secno">B.3 </span>RDFa</a></li><li class="tocline"><a href="#microformats" class="tocxref"><span class="secno">B.4 </span>Microformats</a></li><li class="tocline"><a href="#microdata" class="tocxref"><span class="secno">B.5 </span>Microdata</a></li></ul></li><li class="tocline"><a href="#iana-considerations" class="tocxref"><span class="secno">C. </span>IANA Considerations</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">D. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">E. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">E.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">E.2 </span>Informative references</a></li></ul></li></ul></div>
+
+
+
+<div class="informative section" id="introduction">
+
+<!-- OddPage -->
+<h2><span class="secno">1. </span>Introduction</h2><p><em>This section is non-normative.</em></p>
+
+<p>
+JSON, as specified in [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC4627">RFC4627</a></cite>], is a simple language for representing
+data on the Web. <a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">Linked Data</a> is a technique for creating a network
+of inter-connected data across different Web documents and Web sites.
+A <em>document</em> in this data network is typically identified using an
+<a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> (Internationalized Resource Identifier). A software program
+can typically follow an <abbr title="Internationalized Resource Identifier">IRI</abbr> just like you follow a URL by putting it into your
+browser's location bar. By following IRIs, a software program can find
+more information about the <em>document</em> and the <em>thing</em>s that
+the document describes.
+These <em>things</em> may also be identified using <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>s. The
+<a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> allows a software program to start at one
+<em>document</em> and follow links to other
+<em>documents</em> or <em>things</em> in order to learn more about all of
+the <em>documents</em> and <em>things</em> described on the Web.
+</p>
+
+<p>
+JSON-LD is designed as a lightweight syntax that can be used to express
+<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">Linked Data</a>. It is primarily intended to be a way to use Linked Data
+in Javascript and other Web-based programming environments. It is also
+useful when building inter-operable Web services and when storing Linked
+Data in JSON-based document storage engines. It is practical and designed
+to be as simple as possible, utilizing the large number of JSON parsers
+and libraries available today.
+</p>
+
+<p>
+The syntax does not necessarily require applications to change their JSON, but
+allows one to easily add meaning by simply adding or referencing a context.
+The syntax is designed to not disturb already deployed systems
+running on JSON, but provide a smooth upgrade path from JSON to JSON-LD.
+Finally, the format is intended to be easy to parse, efficient
+to generate, and only requires a very small memory footprint in order to
+operate.
+</p>
+
+<div id="how-to-read-this-document" class="section">
+<h3><span class="secno">1.1 </span>How to Read this Document</h3><p><em>This section is non-normative.</em></p>
+
+<p>
+This document is a detailed specification for a serialization of Linked
+Data in JSON. The document is primarily intended for the following audiences:
+</p>
+
+<ul>
+  <li>Software developers that want to encode Linked Data in a way that is
+  cross-language compatible via JSON.</li>
+  <li>Software developers that want to understand the design decisions and
+  language syntax for JSON-LD.</li>
+  <li>Software developers that want to implement processors and APIs for
+  JSON-LD.</li>
+</ul>
+
+<p>This specification does not describe the programming interfaces for the
+JSON-LD Syntax. The specification that describes the programming interfaces
+for JSON-LD documents is the JSON-LD Application Programming Interface
+[<cite><a class="bibref" rel="biblioentry" href="#bib-JSON-LD-API">JSON-LD-API</a></cite>].</p>
+
+<p>
+To understand the basics in this specification you must first be familiar with
+JSON, which is detailed in [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC4627">RFC4627</a></cite>].</p>
+
+<p>
+  JSON [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC4627">RFC4627</a></cite>] defines several terms which are used throughout this document:
+  </p><dl>
+    <dt><dfn title="json_object" id="dfn-json_object">JSON object</dfn></dt><dd>
+      An object structure is represented as a pair of curly brackets 
+      surrounding zero or more name-value pairs. A name is a 
+      <a class="tref internalDFN" title="string" href="#dfn-string">string</a>. A single colon comes after each name, separating the 
+      name from the value. A single comma separates a value from a following 
+      name. The names within an object <em class="rfc2119" title="should">should</em> be unique.
+    </dd>
+    <dt><dfn title="array" id="dfn-array">array</dfn></dt>
+    <dd>
+      In JSON, an array is an <em>ordered</em> sequence of zero or more values.
+      An array is represented as square brackets surrounding
+      zero or more values that are separated by commas. 
+      While JSON-LD uses the same array representation as JSON,
+      the collection is <em>unordered</em> by default. While order is
+      preserved in regular JSON arrays, it is not in regular JSON-LD arrays
+      unless specific markup is provided
+      (see <a href="#sets-and-lists">Sets and Lists</a>).</dd>
+    <dt><dfn title="string" id="dfn-string">string</dfn></dt><dd>
+      A string is a sequence of zero or more Unicode characters,
+      wrapped in double quotes, using backslash escapes (if necessary). A
+      character is represented as a single character string.</dd>
+    <dt><dfn title="number" id="dfn-number">number</dfn></dt>
+    <dd>
+      A number is similar to that used in most programming languages, except 
+      that the octal and hexadecimal formats are not used and that leading 
+      zeros are not allowed.</dd>
+    <dt><dfn title="true" id="dfn-true">true</dfn> and <dfn title="false" id="dfn-false">false</dfn></dt><dd>
+      Values that are used to express one of two possible boolean states.</dd>
+    <dt><dfn title="null" id="dfn-null">null</dfn></dt><dd>
+      The null value is used to make the JSON-LD processor &quot;forget&quot; any
+      previously defined JSON key that is associated with the null value.
+      If a previous definition doesn't exist, the entire key-value is ignored.
+      If a previous definition of the key does exist, the previous 
+      definition is undefined.</dd>
+    <dt><dfn title="subject_definition" id="dfn-subject_definition">subject definition</dfn></dt><dd>
+      A <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> used to represent a <a class="tref internalDFN" title="subject" href="#dfn-subject">subject</a> and 
+      one or more properties of that subject. A <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> is a 
+      subject definition if it does not contain they keys <code>@value</code>, 
+      <code>@list</code> or <code>@set</code> and it has one or more keys other 
+      than <code>@id</code>.</dd>
+    <dt><dfn title="subject_reference" id="dfn-subject_reference">subject reference</dfn></dt><dd>
+      A <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> used to reference a subject having only the 
+      <code>@id</code> key.</dd>
+  </dl>
+<p></p>
+
+</div>
+
+</div>
+
+<div class="informative section" id="design-goals-and-rationale">
+
+<!-- OddPage -->
+<h2><span class="secno">2. </span>Design Goals and Rationale</h2><p><em>This section is non-normative.</em></p>
+
+<p>A number of design goals were established before the creation of this
+  markup language:</p>
+
+<dl>
+ <dt>Simplicity</dt>
+ <dd>No extra
+ processors or software libraries should be necessary to use JSON-LD in its most
+ basic form. The language will provide developers with a very easy
+ learning curve. Developers need only know JSON and two
+ <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keywords</a> (<code>@context</code>
+ and <code>@id</code>) to use the basic functionality in JSON-LD.</dd>
+ <dt>Compatibility</dt>
+ <dd>The JSON-LD markup must be 100% compatible with JSON. This ensures that
+ all of the standard JSON libraries work seamlessly with JSON-LD documents.</dd>
+ <dt>Expressiveness</dt>
+ <dd>The syntax must be able to express directed graphs, which have been proven
+ to be able to express almost every real world data model.</dd>
+ <dt>Terseness</dt>
+ <dd>The JSON-LD syntax must be very terse and human readable, requiring as
+ little effort as possible from the developer.</dd>
+ 
+<!-- <dt>Pragmatism</dt>
+ <dd>Mixing the expression of pure Linked Data with data that is not
+ linked was an approach that was driven by pragmatism. JSON-LD attempts to be
+ more practical than theoretical in its approach to Linked Data.</dd> -->
+
+ <dt>Zero Edits, most of the time</dt>
+ <dd>JSON-LD must provide a
+ <a href="#referencing-contexts-from-json-documents">mechanism</a>
+ that allows developers to specify <a class="tref internalDFN" title="context" href="#dfn-context">context</a> in a way that is
+ out-of-band.
+ This allows organizations that have
+ already deployed large JSON-based infrastructure to add meaning to their
+ JSON documents in a way that is not disruptive to their day-to-day operations and is
+ transparent to their current customers. At times, mapping JSON to
+ a graph representation can become difficult. In these instances, rather than
+ having JSON-LD support an esoteric use case, we chose not to support the
+ use case and support a simplified syntax instead. So, while Zero Edits is
+ a goal, it is not always possible without adding great complexity to
+ the language.
+ </dd>
+ <dt>One-pass Processing</dt>
+ <dd>JSON-LD supports one-pass processing, which results in a very small memory
+ footprint when processing documents. For example, to expand a JSON-LD document
+ from a compacted form, only one pass is required over the data.</dd>
+</dl>
+</div>
+
+<div class="normative section" id="basic-concepts">
+
+<!-- OddPage -->
+<h2><span class="secno">3. </span>Basic Concepts</h2>
+
+<em>This section is normative.</em>
+
+<p>JSON-LD is designed to ensure that <a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">Linked Data</a> concepts can be
+marked up in a way that is simple to understand and create by Web authors.
+In many cases, regular JSON markup can become Linked Data with the
+simple addition of a <a class="tref internalDFN" title="context" href="#dfn-context">context</a>. As more JSON-LD features are
+used, more semantics are added to the JSON markup.</p>
+
+<div id="linking-data" class="section">
+<h3><span class="secno">3.1 </span>Linking Data</h3>
+
+<p>
+The following definition for <a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">Linked Data</a> is the one that will
+be used for this specification.
+</p>
+<ol>
+  <li><dfn title="linked_data" id="dfn-linked_data">Linked Data</dfn> is a set of documents, each containing a representation of a <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a>.</li>
+  <li>A <dfn title="linked_data_graph" id="dfn-linked_data_graph">linked data graph</dfn> is an unordered labeled directed graph, where nodes are <a class="tref internalDFN" title="subject" href="#dfn-subject">subject</a>s or <a class="tref internalDFN" title="object" href="#dfn-object">object</a>s, and edges are labeled using <a class="tref internalDFN" title="property" href="#dfn-property">properties</a>.</li>
+  <li>A <dfn title="subject" id="dfn-subject">subject</dfn> is any node in a <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a> with at least one outgoing edge.</li>
+  <li>A <a class="tref internalDFN" title="subject" href="#dfn-subject">subject</a> <em class="rfc2119" title="should">should</em> be labeled with an <dfn title="iri" id="dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></dfn> (an Internationalized Resource Identifier as described in [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3987">RFC3987</a></cite>]).</li>
+  <li>An <dfn title="object" id="dfn-object">object</dfn> is a node in a <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a> with at least one incoming edge.</li>
+  <li>An <a class="tref internalDFN" title="object" href="#dfn-object">object</a> <em class="rfc2119" title="may">may</em> be labeled with an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> or a label that is not an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> such as plain text, internationalized text, or a strictly-typed data value.</li>
+  <li>A node <em class="rfc2119" title="may">may</em> be a <a class="tref internalDFN" title="subject" href="#dfn-subject">subject</a> and an <a class="tref internalDFN" title="object" href="#dfn-object">object</a> at the same time.</li>
+  <li>A <dfn title="property" id="dfn-property">property</dfn> is the label on an edge in a
+    <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a>.</li>
+  <li>A <a class="tref internalDFN" title="property" href="#dfn-property">property</a> <em class="rfc2119" title="should">should</em> be an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.</li>
+  <li>An <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> that is a label in a <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a> <em class="rfc2119" title="should">should</em> be dereferencable to a <a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">Linked Data</a> document describing the labeled <a class="tref internalDFN" title="subject" href="#dfn-subject">subject</a>, <a class="tref internalDFN" title="property" href="#dfn-property">property</a> or <a class="tref internalDFN" title="object" href="#dfn-object">object</a>.</li>
+</ol>
+
+<div class="issue"><div class="issue-title"><span>Issue 1</span></div><p class="">An illustration of a linked data graph would probably help here.</p></div>
+
+<div class="issue"><div class="issue-title"><span>Issue 2</span></div><p class="">EricP suggests that the definitions of subject and
+object, while being practical, are at odds with [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>]
+use in their roles within a triple.</p></div>
+
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">JSON-LD allows properties to be BNodes, while RDF does
+  not. When used as just JSON-LD, this is not unreasonable;
+  it only becomes an issue (and could raise an exception) when
+  transformed to RDF.</p></div>
+
+<p>Note that the definition for <a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">Linked Data</a> above is silent on the
+topic of <a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">unlabeled nodes</a>. Nevertheless, this specification allows for the expression
+of <a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">unlabeled nodes</a>, as most graph-based data sets on the Web contain a number
+of associated nodes that are not named and thus are not directly
+de-referenceable.
+</p>
+
+<p>JSON-LD defines a mechanism to map JSON terms, i.e., keys and values, to IRIs. This does not mean
+that JSON-LD requires every key or value to be an <abbr title="Internationalized Resource Identifier">IRI</abbr>, but rather ensures that
+keys and values can be mapped to IRIs if the developer desires to transform
+their data into <a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">Linked Data</a>. There are a few techniques that can ensure
+that developers will generate good Linked Data for the Web. JSON-LD
+formalizes those techniques.
+</p>
+
+<p>We will be using the following JSON markup as the example for the
+rest of this section:
+</p>
+
+<div class="example"><div class="example-title"><span>Example 1</span></div><pre class="example">{
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
+  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
+}</pre></div>
+
+<div id="syntax-tokens-and-keywords" class="section">
+  <h4><span class="secno">3.1.1 </span>Syntax Tokens and Keywords</h4>
+
+  <p>JSON-LD specifies a number of syntax tokens and <dfn title="keyword" id="dfn-keyword">keywords</dfn>
+  that are a core part of the language:</p>
+
+  <dl>
+  <dt><code>@context</code></dt>
+  <dd>Used to define the short-hand names that are used throughout a JSON-LD
+    document. These short-hand names are called <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s and help
+    developers to express specific identifiers in a compact manner. The
+    <code>@context</code> keyword is described in detail in the section titled
+    <a href="#the-context">The Context</a>.</dd>
+  <dt><code>@graph</code></dt><dd>Used to explicitly label a <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a>.
+    This keyword is described in the section titled <a href="#named-graphs">Named Graphs</a>.</dd>
+  <dt><code>@id</code></dt>
+  <dd>Used to uniquely identify <em>things</em> that are being described in the document.
+    This keyword is described in the section titled
+    <a href="#identifying-the-subject">Identifying the Subject</a>.</dd>
+  <dt><code>@value</code></dt>
+  <dd>Used to specify the data that is associated with a particular
+    <a class="tref internalDFN" title="property" href="#dfn-property">property</a> in the graph. This keyword is described
+    in the sections titled
+    <a href="#string-internationalization">String Internationalization</a> and
+    <a href="#typed-values">Typed Values</a>.</dd>
+  <dt><code>@language</code></dt>
+  <dd>Used to specify the native language for a particular value or the default
+    language of a JSON-LD document. This keyword is described in the section titled
+    <a href="#string-internationalization">String Internationalization</a>.</dd>
+  <dt><code>@type</code></dt>
+  <dd>Used to set the data type of a <a class="tref internalDFN" title="subject" href="#dfn-subject">subject</a> or
+    <a class="tref internalDFN" title="typed_value" href="#dfn-typed_value">typed value</a>. This keyword is described in the section titled
+    <a href="#typed-values">Typed Values</a>.</dd>
+  <dt><code>@container</code></dt>
+  <dd>Used to set the container of a particular value.
+    This keyword is described in the section titled <a href="#sets-and-lists">Sets and Lists</a>.</dd>
+  <dt><code>@list</code></dt>
+  <dd>Used to express an ordered set of data.
+    This keyword is described in the section titled <a href="#sets-and-lists">Sets and Lists</a>.</dd>
+  <dt><code>@set</code></dt>
+  <dd>Used to express an unordered set of data.
+    This keyword is described in the section titled <a href="#sets-and-lists">Sets and Lists</a>.</dd>
+  <dt><code>:</code></dt>
+  <dd>The separator for JSON keys and values that use
+    <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact IRIs</a>.</dd>
+  </dl>
+
+  <p>For the avoidance of doubt, all keys, <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keywords</a>, and values in JSON-LD are
+  case-sensitive.</p>
+</div>
+
+<div id="the-context" class="section">
+<h4><span class="secno">3.1.2 </span>The Context</h4>
+
+<p>In JSON-LD, a <dfn title="context" id="dfn-context">context</dfn> is used to map <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s, i.e., properties with associated
+  values in an JSON document, to <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>s. A <dfn title="term" id="dfn-term">term</dfn> is a short word that expands to an
+  <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>. <a class="tref internalDFN" title="term" href="#dfn-term">Term</a>s <em class="rfc2119" title="may">may</em> be defined as any valid JSON <a class="tref internalDFN" title="string" href="#dfn-string">string</a> other
+  than a JSON-LD <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a>. To avoid
+  forward-compatibility issues, <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s starting with an <code>@</code> character <em class="rfc2119" title="should not">should not</em> be used
+  as they might be used as <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keywords</a> in future versions of JSON-LD. Furthermore,
+  the use of empty terms (<code>&quot;&quot;</code>) is discouraged as not all programming languages are able to handle
+  empty property names.</p>
+<p>The Web uses <a class="tref internalDFN" title="iri" href="#dfn-iri">IRIs</a> for unambiguous identification. The
+  idea is that these <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s mean something that may be of use to other developers and that it is useful to
+  give them an unambiguous identifier. That is, it is useful for <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s to expand to IRIs so that
+  developers don't accidentally step on each other's <dfn title="vocabulary" id="dfn-vocabulary">vocabulary</dfn> terms and other resources. Furthermore, developers, and
+  machines, are able to use this <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> (by plugging it directly into a web browser, for instance) to go to
+  the term and get a definition of what the term means. This mechanism is analogous to the way we can use
+  <a href="http://wordnet.princeton.edu/">WordNet</a> today to see the definition of words in the English language.
+  Developers and machines need the same sort of definition of terms. <a class="tref internalDFN" title="iri" href="#dfn-iri">IRIs</a> provide a way to
+  ensure that these terms are unambiguous. For example, the term <code>name</code> may
+  map directly to the <abbr title="Internationalized Resource Identifier">IRI</abbr> <code>http://xmlns.com/foaf/0.1/name</code>. This allows JSON-LD documents to be constructed
+  using the common JSON practice of simple name/value pairs while ensuring that the data is useful outside of the
+  page, API or database in which it resides. The value of a term mapping
+  <em class="rfc2119" title="must">must</em> be either; 1) a simple string with the lexical form of an <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a> or
+  2) <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a>, or 3) an <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> containing an
+  <code>@id</code>, <code>@type</code>, <code>@language</code>, or <code>@container</code> keyword
+  (all other keywords are ignored by a JSON-LD processor).
+</p>
+
+<p>These Linked Data <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s are typically collected in a
+context document that would look something like this:</p>
+
+<div class="example"><div class="example-title"><span>Example 2</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+    &quot;depiction&quot;:
+    {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/depiction&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    },
+    &quot;homepage&quot;:
+    {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    },
+  }
+}</pre></div>
+
+<p>Assuming that this context document can be retrieved at <code>http://json-ld.org/contexts/person.jsonld</code>,
+  it can be referenced from a JSON-LD document by adding a single line. The JSON markup shown in the previous
+  section could be changed as follows:</p>
+
+<div class="example"><div class="example-title"><span>Example 3</span></div><pre class="example">{
+  <span class="diff">&quot;@context&quot;: &quot;http://json-ld.org/contexts/person.jsonld&quot;,</span>
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
+  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
+}</pre></div>
+
+<p>The additions above transform the previous JSON document into a JSON document
+with added semantics because the <code>@context</code> specifies how the
+<strong>name</strong>, <strong>homepage</strong>, and <strong>depiction</strong>
+terms map to <a class="tref internalDFN" title="iri" href="#dfn-iri">IRIs</a>.
+Mapping those keys to IRIs gives the data global context. If two
+developers use the same <abbr title="Internationalized Resource Identifier">IRI</abbr> to describe a property, they are more than likely
+expressing the same concept. This allows both developers to re-use each others'
+data without having to agree to how their data will interoperate on a
+site-by-site basis. Contexts may also contain type information
+for certain <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s as well as other processing instructions for
+the JSON-LD processor.</p>
+
+<p>Contexts <em class="rfc2119" title="may">may</em> be specified in-line. This ensures that JSON-LD documents
+can be processed when a JSON-LD processor does not have access to the Web.</p>
+
+<div class="example"><div class="example-title"><span>Example 4</span></div><pre class="example">{
+  <span class="diff">&quot;@context&quot;:
+  {
+    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+    &quot;depiction&quot;:
+    {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/depiction&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    },
+    &quot;homepage&quot;:
+    {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    },
+  },</span>
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
+  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
+}</pre></div>
+
+<p>Contexts <em class="rfc2119" title="may">may</em> be used at any time a <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a> is defined.
+  A <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a> <em class="rfc2119" title="may">may</em> specify multiple contexts, using an
+  <a class="tref internalDFN" title="array" href="#dfn-array">array</a>, which is processed in order. This is useful
+  when an author would like to use an existing context and add
+  application-specific terms to the existing context. Duplicate context
+  <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s <em class="rfc2119" title="must">must</em> be overridden using a last-defined-overrides
+  mechanism.</p>
+
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">If a <a class="tref internalDFN" title="term" href="#dfn-term">term</a> is re-defined within a context, all previous
+  rules associated with the previous definition are removed. A <a class="tref internalDFN" title="term" href="#dfn-term">term</a> defined
+  in a previous context <em class="rfc2119" title="must">must</em> be removed, if it is re-defined to <code>null</code>.</p></div>
+
+<p>
+  The set of contexts defined within a specific <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a> are
+  referred to as <dfn title="local_context" id="dfn-local_context">local context</dfn>s. Setting the context to <code>null</code>
+  effectively sets the <a class="tref internalDFN" title="local_context" href="#dfn-local_context">local context</a> to the initial context
+  (further explained in the JSON-LD API, Appendix A, Initial Context 
+  [<cite><a class="bibref" rel="biblioentry" href="#bib-JSON-LD-API">JSON-LD-API</a></cite>] ). The
+  <dfn title="active_context" id="dfn-active_context">active context</dfn> refers to the accumulation of
+  <a class="tref internalDFN" title="local_context" href="#dfn-local_context">local context</a>s that are in scope at a specific point within
+  the document. The following example specifies an external context and then
+  layers a local context on top of the external context:</p>
+
+<div class="example"><div class="example-title"><span>Example 5</span></div><pre class="example">{
+  <span class="diff">&quot;@context&quot;: [
+    &quot;http://json-ld.org/contexts/person.jsonld&quot;,
+    {
+      &quot;pic&quot;: &quot;http://xmlns.com/foaf/0.1/depiction&quot;
+    }
+  ],</span>
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
+  <span class="diff">&quot;pic&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;</span>
+}</pre></div>
+
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">To ensure the best possible performance, it is a best practice to
+put the <a class="tref internalDFN" title="context" href="#dfn-context">context</a> definition at the top of the JSON-LD document. If it isn't listed
+first, processors have to save each key-value pair until the <a class="tref internalDFN" title="context" href="#dfn-context">context</a> is processed.
+This creates a memory and complexity burden for certain types of
+low-memory footprint JSON-LD processors.</p></div>
+
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">The <code>null</code> value is processed in a special way
+in JSON-LD. Unless otherwise specified, a JSON-LD processor <em class="rfc2119" title="must">must</em> act as if a 
+key-value pair in the body of a JSON-LD document was never declared when 
+the value equals <em>null</em>.
+If <code>@value</code>, <code>@list</code>, or <code>@set</code> is set 
+to <em>null</em> in expanded form, then the entire JSON object is 
+ignored. If <code>@context</code> is set to <em>null</em>, the 
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> is reset and when used within a 
+<a class="tref internalDFN" title="context" href="#dfn-context">context</a>, it removes any definition associated with the key, 
+unless otherwise specified.
+</p></div>
+
+</div>
+
+<div id="from-json-to-json-ld" class="section">
+<h4><span class="secno">3.1.3 </span>From JSON to JSON-LD</h4>
+
+<p>If a set of <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s such as, <strong>name</strong>,
+<strong>homepage</strong>, and <strong>depiction</strong>,
+are defined in a <a class="tref internalDFN" title="context" href="#dfn-context">context</a>, and that context is used to resolve the
+names in <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON objects</a>, machines are able to automatically expand the terms to
+something meaningful and unambiguous, like this:</p>
+
+<div class="example"><div class="example-title"><span>Example 6</span></div><pre class="example">{
+  &quot;<span class="diff">http://xmlns.com/foaf/0.1/name</span>&quot;: &quot;Manu Sporny&quot;,
+  &quot;<span class="diff">http://xmlns.com/foaf/0.1/homepage</span>&quot;: &quot;http://manu.sporny.org&quot;
+  &quot;<span class="diff">http://xmlns.com/foaf/0.1/depiction</span>&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
+}</pre></div>
+
+<p>Doing this allows JSON to be unambiguously machine-readable without
+requiring developers to drastically change their workflow.</p>
+
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">The example above does not use the <code>@id</code> <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a>
+to set the <a class="tref internalDFN" title="subject" href="#dfn-subject">subject</a> of the node being described above. This type
+of node is called an <a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">unlabeled node</a>. It is advised that all nodes
+described in JSON-LD are given unique identifiers via the
+<code>@id</code> keyword unless the data is not intended to be linked to
+from other data sets.</p></div>
+
+<p>A <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> used to define property values is called a
+  <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a>. <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">Subject definitions</a>
+  do not require an <code>@id</code>. 
+  <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">Subject definitions</a> that do not 
+  contain an <code>@id</code> are known as an <a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">unlabeled nodes</a>.</p>
+
+</div>
+</div>
+
+<div id="iris" class="section">
+<h3><span class="secno">3.2 </span>IRIs</h3>
+
+<p><a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>s are fundamental to <a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">Linked Data</a>
+as that is how most <a class="tref internalDFN" title="subject" href="#dfn-subject">subject</a>s, all
+<a class="tref internalDFN" title="property" href="#dfn-property">properties</a> and many <a class="tref internalDFN" title="object" href="#dfn-object">object</a>s are
+identified. <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>s can be expressed in a variety of different ways
+in JSON-LD.</p>
+
+<ol>
+  <li>Except within a <a class="tref internalDFN" title="context" href="#dfn-context">context</a> definition, <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s in the key position in
+    a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> that have a mapping to an <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a> or another <a class="tref internalDFN" title="term" href="#dfn-term">term</a> in the
+    <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> are expanded to an <abbr title="Internationalized Resource Identifier">IRI</abbr> by JSON-LD processors.</li>
+  <li>An <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> is generated for the <a class="tref internalDFN" title="string" href="#dfn-string">string</a> value specified using
+    <code>@id</code> or <code>@type</code>.</li>
+  <li>An <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> is generated for the <a class="tref internalDFN" title="string" href="#dfn-string">string</a> value of any key for which there
+    are <a class="tref internalDFN" title="coercion" href="#dfn-coercion">coercion</a> rules in effect that identify the value as an <code>@id</code>.</li>
+</ol>
+
+<p>IRIs may be represented as an <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a>, a <a class="tref internalDFN" title="relative_iri" href="#dfn-relative_iri">relative <abbr title="Internationalized Resource Identifier">IRI</abbr></a>, a <a class="tref internalDFN" title="term" href="#dfn-term">term</a>, or a <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a>.</p>
+
+<p>An <dfn title="absolute_iri" id="dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></dfn> is defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3987">RFC3987</a></cite>] containing a <em>scheme</em> along with
+  <em>path</em> and optional <em>query</em> and <em>fragment</em> segments. A <dfn title="relative_iri" id="dfn-relative_iri">relative <abbr title="Internationalized Resource Identifier">IRI</abbr></dfn> is an <abbr title="Internationalized Resource Identifier">IRI</abbr>
+  that is relative to some other <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a>. In JSON-LD all <a class="tref internalDFN" title="relative_iri" href="#dfn-relative_iri">relative <abbr title="Internationalized Resource Identifier">IRI</abbr></a>s are resolved relative to the
+  <dfn title="base_iri" id="dfn-base_iri">base <abbr title="Internationalized Resource Identifier">IRI</abbr></dfn> associated with the document (typically, the directory that contains the document or the document itself).</p>
+
+<p>IRIs can be expressed directly in the key position like so:</p>
+
+<div class="example"><div class="example-title"><span>Example 7</span></div><pre class="example">{
+...
+  &quot;<span class="diff">http://xmlns.com/foaf/0.1/name</span>&quot;: &quot;Manu Sporny&quot;,
+...
+}</pre></div>
+
+<p>In the example above, the key <code>http://xmlns.com/foaf/0.1/name</code> is interpreted
+  as an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> because it contains a colon
+  (<code>:</code>) and the 'http' <a class="tref internalDFN" title="prefix" href="#dfn-prefix">prefix</a> does not exist in 
+  the context.</p>
+
+<p>Term expansion occurs for IRIs if the value matches a <a class="tref internalDFN" title="term" href="#dfn-term">term</a> defined within the
+<a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>:</p>
+
+<div class="example"><div class="example-title"><span>Example 8</span></div><pre class="example">{
+  &quot;<span class="diff">@context</span>&quot;:
+  {
+    &quot;<span class="diff">name</span>&quot;: &quot;<span class="diff">http://xmlns.com/foaf/0.1/name</span>&quot;
+...
+  },
+  &quot;<span class="diff">name</span>&quot;: &quot;Manu Sporny&quot;,
+  &quot;status&quot;: &quot;trollin'&quot;,
+...
+}</pre></div>
+
+<p><a class="tref internalDFN" title="term" href="#dfn-term">Term</a>s are case sensitive, and <em class="rfc2119" title="must">must</em> be matched using a case-sensitive comparison.</p>
+
+<p>JSON keys that do not expand to an absolute <abbr title="Internationalized Resource Identifier">IRI</abbr> are ignored, or removed
+in some cases, by the [<cite><a class="bibref" rel="biblioentry" href="#bib-JSON-LD-API">JSON-LD-API</a></cite>]. However, JSON keys that do not include
+a mapping in the <a class="tref internalDFN" title="context" href="#dfn-context">context</a> are still considered valid expressions
+in JSON-LD documents - the keys just don't have any machine-readable,
+semantic meaning.</p>
+
+<p><a class="tref internalDFN" title="prefix" href="#dfn-prefix">Prefix</a>es are expanded when the form of the value is a
+  <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a> represented as a <code>prefix:suffix</code>
+  combination, and the prefix matches a <a class="tref internalDFN" title="term" href="#dfn-term">term</a> defined within the
+  <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>:</p>
+
+<div class="example"><div class="example-title"><span>Example 9</span></div><pre class="example">{
+  &quot;<span class="diff">@context</span>&quot;:
+  {
+    &quot;<span class="diff">foaf</span>&quot;: &quot;<span class="diff">http://xmlns.com/foaf/0.1/</span>&quot;
+...
+  },
+  &quot;<span class="diff">foaf:name</span>&quot;: &quot;Manu Sporny&quot;,
+...
+}</pre></div>
+
+<p><code>foaf:name</code> above will automatically expand out to the <abbr title="Internationalized Resource Identifier">IRI</abbr>
+<code>http://xmlns.com/foaf/0.1/name</code>. See <a href="#compact-iris">Compact IRIs</a> for more details.</p>
+
+<p>An <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> is generated when a JSON object is used in the
+value position that contains an <code>@id</code> keyword:</p>
+
+<div class="example"><div class="example-title"><span>Example 10</span></div><pre class="example">{
+...
+  &quot;homepage&quot;: { &quot;<span class="diff">@id</span>&quot;: &quot;http://manu.sporny.org&quot; }
+...
+}</pre></div>
+
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">Specifying a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> with an
+  <code>@id</code> key is used to identify that object using an
+  <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>. When the object has only the <code>@id</code>, it
+  is called a <a class="tref internalDFN" title="subject_reference" href="#dfn-subject_reference">subject reference</a>.
+  This facility <em class="rfc2119" title="may">may</em> also be used to link to another
+  <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a> using a mechanism called
+  <a class="tref internalDFN" title="embedding" href="#dfn-embedding">embedding</a>, which is covered in the section titled
+  <a href="#embedding">Embedding</a>.</p></div>
+
+<p>If type <a class="tref internalDFN" title="coercion" href="#dfn-coercion">coercion</a> rules are specified in the <code>@context</code> for
+a particular <a class="tref internalDFN" title="term" href="#dfn-term">term</a> or property <abbr title="Internationalized Resource Identifier">IRI</abbr>, an <abbr title="Internationalized Resource Identifier">IRI</abbr> is generated:</p>
+
+<div class="example"><div class="example-title"><span>Example 11</span></div><pre class="example">{<span class="diff">
+  &quot;@context&quot;:
+  {
+    ...
+    &quot;homepage&quot;:
+    {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    }
+    ...
+  }</span>
+...
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
+...
+}</pre></div>
+
+<p>In the example above, even though the value
+<code>http://manu.sporny.org/</code> is expressed as a JSON
+<a class="tref internalDFN" title="string" href="#dfn-string">string</a>, the type <a class="tref internalDFN" title="coercion" href="#dfn-coercion">coercion</a> rules will transform
+the value into an <abbr title="Internationalized Resource Identifier">IRI</abbr> when processed by a JSON-LD Processor.</p>
+
+</div>
+
+<div id="identifying-the-subject" class="section">
+<h3><span class="secno">3.3 </span>Identifying the Subject</h3>
+
+<p>
+  To be able to externally reference nodes in a graph, it is important that each node has
+  an unambiguous identifier. <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>s are a fundamental concept of
+  <a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">Linked Data</a>, and nodes should have a de-referencable
+  identifier used to name and locate them. For nodes to be truly linked,
+  de-referencing the identifier should result in a representation of that node
+  (for example, using a URL to retrieve a web page).
+  Associating an <abbr title="Internationalized Resource Identifier">IRI</abbr> with a node tells an application that the returned
+  document contains a description of the node requested.
+</p>
+<p>
+  JSON-LD documents may also contain descriptions of other nodes, so it is necessary to be able to
+  uniquely identify each node which may be externally referenced.
+</p>
+<p>A <a class="tref internalDFN" title="subject" href="#dfn-subject">subject</a>
+   of a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> is a node identified using the <code>@id</code> key. The subject is the
+first piece of information needed by the JSON-LD processor in order to
+create the (subject, property, object) tuple, also known as a triple.</p>
+
+<div class="example"><div class="example-title"><span>Example 12</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    ...
+    &quot;homepage&quot;:
+    {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    }
+    ...
+  },
+  &quot;<span class="diff">@id</span>&quot;: &quot;<span class="diff">http://example.org/people#joebob</span>&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
+...
+}</pre></div>
+
+<p>The example above would set the subject to the <abbr title="Internationalized Resource Identifier">IRI</abbr>
+<code>http://example.org/people#joebob</code>.
+</p>
+
+<p>A <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> used to define property values is called a
+  <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a>. <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">Subject definitions</a>
+  do not require an <code>@id</code>. A
+  <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a>
+  that does not contain an <code>@id</code> property defines properties of an
+  <a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">unlabeled node</a>.</p>
+
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">To ensure the best possible performance, when possible, it is a best practice
+  to put JSON-LD <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a>s, such as <code>@id</code> and 
+  <code>@context</code> before other key-value pairs in a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON 
+  object</a>. However, keys in a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> are not ordered, 
+  so processors <em class="rfc2119" title="must not">must not</em> depend on key ordering. If keywords are not listed 
+  first, processors have to save each key-value pair until at least the 
+  <code>@context</code> and the <code>@id</code> are processed. Not 
+  specifying those keywords first creates a memory and complexity burden for 
+  low-memory footprint processors, forcing them to use more memory and 
+  computing cycles than necessary.</p></div>
+
+
+</div>
+
+<div id="specifying-the-type" class="section">
+<h3><span class="secno">3.4 </span>Specifying the Type</h3>
+
+<p>The type of a particular subject can be specified using the
+<code>@type</code> <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a>. Specifying the type in this way will generate a
+triple of the form (subject, type, type-<abbr title="Internationalized Resource Identifier">IRI</abbr>). To be considered
+<a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">Linked Data</a>, types <em class="rfc2119" title="must">must</em> be uniquely identified by
+an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.</p>
+
+<div class="example"><div class="example-title"><span>Example 13</span></div><pre class="example">{
+...
+  &quot;@id&quot;: &quot;http://example.org/people#joebob&quot;,
+  &quot;<span class="diff">@type</span>&quot;: &quot;<span class="diff">http://xmlns.com/foaf/0.1/Person</span>&quot;,
+...
+}</pre></div>
+</div>
+
+<div id="string-internationalization" class="section">
+<h3><span class="secno">3.5 </span>String Internationalization</h3>
+
+<p>At times, it is important to annotate a <a class="tref internalDFN" title="string" href="#dfn-string">string</a>
+  with its language. In JSON-LD this is possible in a variety of ways.
+  Firstly, it is possible to define a default language for a JSON-LD document
+  by setting the <code>@language</code> key in the <code>@context</code> or in a
+  <a class="tref internalDFN" title="term" href="#dfn-term">term</a> definition:</p>
+
+<div class="example"><div class="example-title"><span>Example 14</span></div><pre class="example">{
+  <span class="diff">&quot;@context&quot;:
+  {
+    ...
+    &quot;@language&quot;: &quot;ja&quot;
+  },</span>
+  &quot;name&quot;: <span class="diff">&quot;花澄&quot;</span>,
+  &quot;occupation&quot;: <span class="diff">&quot;科学者&quot;</span>
+}</pre></div>
+
+<p>The example above would associate the <code>ja</code> language
+  code with the two <a class="tref internalDFN" title="string" href="#dfn-string">string</a>s <em>花澄</em> and <em>科学者</em>.
+  Languages <em class="rfc2119" title="must">must</em> be well-formed language tags according to [<cite><a class="bibref" rel="biblioentry" href="#bib-BCP47">BCP47</a></cite>].</p>
+
+<p>It is possible to override the default language by using the expanded
+form of a value:</p>
+
+<div class="example"><div class="example-title"><span>Example 15</span></div><pre class="example">{
+  &quot;@context&quot;: {
+    ...
+    &quot;@language&quot;: &quot;ja&quot;
+  },
+  &quot;name&quot;: &quot;花澄&quot;,
+  &quot;occupation&quot;: <span class="diff">{
+    &quot;@value&quot;: &quot;Scientist&quot;,
+    &quot;@language&quot;: &quot;en&quot;
+  }</span>
+}</pre></div>
+
+<p>It is also possible to override the default language or specify a plain
+value by omitting the <code>@language</code> tag or setting it to
+<code>null</code> when expressing the expanded value:</p>
+
+<div class="example"><div class="example-title"><span>Example 16</span></div><pre class="example">{
+  &quot;@context&quot;: {
+    ...
+    &quot;@language&quot;: &quot;ja&quot;
+  },
+  &quot;name&quot;: <span class="diff">{
+    &quot;@value&quot;: &quot;Frank&quot;
+  },</span>
+  &quot;occupation&quot;: <span class="diff"> {
+    &quot;@value&quot;: &quot;Ninja&quot;,
+    &quot;@language&quot;: &quot;en&quot;
+  }</span>,
+  &quot;speciality&quot;: &quot;手裏剣&quot;
+}</pre></div>
+
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">Please note that language associations <em class="rfc2119" title="must">must</em> only be applied
+  to plain literal <a class="tref internalDFN" title="string" href="#dfn-string">string</a>s. That is, <a class="tref internalDFN" title="typed_value" href="#dfn-typed_value">typed value</a>s
+  or values that are subject to <a href="#type-coercion">type coercion</a>
+  won't be language tagged.</p></div>
+
+<p>To clear the default language for a subtree, <code>@language</code> can
+be set to <code>null</code> in a <a class="tref internalDFN" title="local_context" href="#dfn-local_context">local context</a> as follows:</p>
+
+<div class="example"><div class="example-title"><span>Example 17</span></div><pre class="example">{
+  &quot;@context&quot;: {
+    ...
+    &quot;@language&quot;: &quot;ja&quot;
+  },
+  &quot;name&quot;: &quot;花澄&quot;,
+  &quot;details&quot;: {
+<span class="diff">    &quot;@context&quot;: {
+      &quot;@language&quot;: null
+    },</span>
+    &quot;occupation&quot;: &quot;Ninja&quot;
+  }
+}</pre></div>
+
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">JSON-LD allows one to associate language information with
+  <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s.
+  See <a href="#expanded-term-definition">Expanded Term Definition</a> for
+  more details.</p></div>
+
+</div>
+
+<div id="json-ld-syntax" class="section">
+  <h3><span class="secno">3.6 </span>JSON-LD Syntax</h3>
+  
+  <p>A JSON-LD document is first, and foremost, a JSON document
+    (as defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC5988">RFC5988</a></cite>]), and any syntactically correct JSON document 
+    <em class="rfc2119" title="must">must</em> be processed by a conforming JSON-LD processor. However, JSON-LD 
+    describes a specific syntax to use for expressing Linked Data. This 
+    includes the use of specific keywords, as identified in <a href="#syntax-tokens-and-keywords">Syntax Tokens and Keywords</a> for 
+    expressing <a title="subject definition">subject definitions</a>, values, 
+    and the <a href="#dfn-context" class="internalDFN">context</a>. See <a href="#json-ld-authoring-guidelines">Appendix A</a> for authoring 
+    guidelines and a BNF description of JSON-LD.</p>
+
+</div>
+</div>
+
+<div id="advanced-concepts" class="section">
+
+<!-- OddPage -->
+<h2><span class="secno">4. </span>Advanced Concepts</h2>
+
+<em>This section is normative.</em>
+
+<p>JSON-LD has a number of features that provide functionality above and beyond
+the core functionality described above. The following section describes this
+advanced functionality in more detail.
+</p>
+
+<div id="compact-iris" class="section">
+  <h3><span class="secno">4.1 </span>Compact IRIs</h3>
+  <p>
+    <a class="tref internalDFN" title="term" href="#dfn-term">Term</a>s in <a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">Linked Data</a> documents may draw from
+    a number of different <a class="tref internalDFN" title="vocabulary" href="#dfn-vocabulary">vocabularies</a>.
+    At times, declaring every single term that a document uses can require the
+    developer to declare tens, if not hundreds of potential
+    <a class="tref internalDFN" title="vocabulary" href="#dfn-vocabulary">vocabulary</a> <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s that are used across an
+    application. This is a concern for at least two reasons: the
+    first is the cognitive load on the developer of remembering all of the
+    <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s, and the second is the serialized size of the
+    <a class="tref internalDFN" title="context" href="#dfn-context">context</a> if it is specified inline. In order to address these issues,
+    the concept of a <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a> is introduced.</p>
+  <p>
+    A <dfn title="compact_iri" id="dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></dfn> is a way of expressing an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>
+    using a <em>prefix</em> and <em>suffix</em> separated by a colon (<code>:</code>) which is
+    similar to the <cite><a href="http://www.w3.org/TR/rdfa-core/#s_curies">CURIE Syntax</a></cite>
+    in [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>]. The <dfn title="prefix" id="dfn-prefix">prefix</dfn> is a <a class="tref internalDFN" title="term" href="#dfn-term">term</a> taken from the
+    <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a> and is a short string identifying a
+    particular <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> in a JSON-LD document.
+    For example, the prefix <code>foaf</code> may be used as a short
+    hand for the Friend-of-a-Friend vocabulary, which is identified using
+    the <abbr title="Internationalized Resource Identifier">IRI</abbr> <code>http://xmlns.com/foaf/0.1/</code>. A developer may append
+    any of the FOAF <a class="tref internalDFN" title="vocabulary" href="#dfn-vocabulary">vocabulary</a> terms to the end of the prefix
+    to specify a short-hand version of the <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a> for the
+    <a class="tref internalDFN" title="vocabulary" href="#dfn-vocabulary">vocabulary</a> term. For example, <code>foaf:name</code> would
+    be expanded out to the <abbr title="Internationalized Resource Identifier">IRI</abbr> <code>http://xmlns.com/foaf/0.1/name</code>.
+    Instead of having to remember and type out the entire <abbr title="Internationalized Resource Identifier">IRI</abbr>, the developer
+    can instead use the prefix in their JSON-LD markup.
+  </p>
+  <p>Terms are interpreted as <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a>s if they contain at least one
+    colon and the first colon is not followed by two slashes (<code>//</code>, as in
+    <code>http://example.com</code>). To generate the full <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>,
+    the value is first split into a <em>prefix</em> and <em>suffix</em> at the first
+    occurrence of a colon (<code>:</code>). If the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>
+    contains a term mapping for <em>prefix</em>, an <abbr title="Internationalized Resource Identifier">IRI</abbr> is generated by
+    prepending the mapped <em>prefix</em> to the (possibly empty) <em>suffix</em>
+    using textual concatenation.  If no prefix mapping is defined, the value is interpreted
+    as an <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a>. If the prefix is an underscore
+    (<code>_</code>), the <abbr title="Internationalized Resource Identifier">IRI</abbr> remains unchanged. This effectively means that every term
+    containing a colon will be interpreted by a JSON-LD processor as an <abbr title="Internationalized Resource Identifier">IRI</abbr>.
+  </p>
+  <p>Consider the following example:</p>
+  <div class="example"><div class="example-title"><span>Example 18</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    <span class="diff">&quot;dc&quot;: &quot;http://purl.org/dc/elements/1.1/&quot;,</span>
+    <span class="diff">&quot;ex&quot;: &quot;http://example.org/vocab#&quot;</span>
+  },
+  &quot;@id&quot;: &quot;http://example.org/library&quot;,
+  &quot;@type&quot;: <span class="diff">&quot;ex:Library&quot;</span>,
+  <span class="diff">&quot;ex:contains&quot;</span>:
+  {
+    &quot;@id&quot;: &quot;http://example.org/library/the-republic&quot;,
+    &quot;@type&quot;: <span class="diff">&quot;ex:Book&quot;</span>,
+    <span class="diff">&quot;dc:creator&quot;</span>: &quot;Plato&quot;,
+    <span class="diff">&quot;dc:title&quot;</span>: &quot;The Republic&quot;,
+    <span class="diff">&quot;ex:contains&quot;</span>:
+    {
+      &quot;@id&quot;: &quot;http://example.org/library/the-republic#introduction&quot;,
+      &quot;@type&quot;: <span class="diff">&quot;ex:Chapter&quot;</span>,
+      <span class="diff">&quot;dc:description&quot;</span>: &quot;An introductory chapter on The Republic.&quot;,
+      <span class="diff">&quot;dc:title&quot;</span>: &quot;The Introduction&quot;
+    }
+  }
+}</pre></div>
+  <p>
+    In this example, two different <a class="tref internalDFN" title="vocabulary" href="#dfn-vocabulary">vocabularies</a>
+    are referred to using prefixes. Those prefixes are then used as type and
+    property values using the compact <abbr title="Internationalized Resource Identifier">IRI</abbr> <code>prefix:suffix</code> notation.
+  </p>
+  <p>It's also possible to use compact IRIs within the context as shown in the
+    following example:</p>
+  <div class="example"><div class="example-title"><span>Example 19</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;,
+    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;,
+    <span class="diff">&quot;foaf:homepage&quot;</span>: { &quot;@type&quot;: &quot;@id&quot; },
+    &quot;picture&quot;: { &quot;@id&quot;: <span class="diff">&quot;foaf:depiction&quot;</span>, &quot;@type&quot;: &quot;@id&quot; }
+  },
+  &quot;@id&quot;: &quot;http://me.markus-lanthaler.com/&quot;,
+  &quot;@type&quot;: &quot;foaf:Person&quot;,
+  &quot;foaf:name&quot;: &quot;Markus Lanthaler&quot;,
+  &quot;foaf:homepage&quot;: &quot;http://www.markus-lanthaler.com/&quot;,
+  &quot;picture&quot;: &quot;http://twitter.com/account/profile_image/markuslanthaler&quot;
+}</pre></div>
+</div>
+
+<div id="typed-values" class="section">
+<h3><span class="secno">4.2 </span>Typed Values</h3>
+
+<p>
+  A value with an associated type, also known as a
+  <dfn title="typed_value" id="dfn-typed_value">typed value</dfn>, is indicated by associating a value with
+  an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> which indicates the value's type. Typed values may be
+  expressed in JSON-LD in two ways:
+</p>
+
+<ol>
+  <li>By utilizing the <code>@type</code> <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a> when defining
+    a <a class="tref internalDFN" title="term" href="#dfn-term">term</a> within a <code>@context</code> section.</li>
+  <li>By utilizing the expanded form for specifying objects.</li>
+</ol>
+
+<p>The first example uses the <code>@type</code> keyword to associate a
+type with a particular <a class="tref internalDFN" title="term" href="#dfn-term">term</a> in the <code>@context</code>:</p>
+
+<div class="example"><div class="example-title"><span>Example 20</span></div><pre class="example">{
+  <span class="diff">&quot;@context&quot;:
+  {
+    &quot;modified&quot;:
+    {
+      &quot;@id&quot;: &quot;http://purl.org/dc/terms/modified&quot;,
+      &quot;@type&quot;: &quot;http://www.w3.org/2001/XMLSchema#dateTime&quot;
+    }
+  },</span>
+...
+  &quot;modified&quot;: &quot;2010-05-29T14:17:39+02:00&quot;,
+...
+}</pre></div>
+
+<p>The <em>modified</em> key's value above is automatically type coerced to a
+datetime value because of the information specified in the
+<code>@context</code>.</p>
+
+<p>The second example uses the expanded form of setting the type information
+in the body of a JSON-LD document:</p>
+
+<div class="example"><div class="example-title"><span>Example 21</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;modified&quot;:
+    {
+      &quot;@id&quot;: &quot;http://purl.org/dc/terms/modified&quot;
+    }
+  },
+...
+  &quot;modified&quot;:
+  <span class="diff">{
+    &quot;@value&quot;: &quot;2010-05-29T14:17:39+02:00&quot;,
+    &quot;@type&quot;: &quot;http://www.w3.org/2001/XMLSchema#dateTime&quot;
+  }</span>
+...
+}</pre></div>
+
+<p>Both examples above would generate an object with the value of
+<code>2010-05-29T14:17:39+02:00</code> and the type of
+<code>http://www.w3.org/2001/XMLSchema#dateTime</code>. Note that it is
+also possible to use a <a class="tref internalDFN" title="term" href="#dfn-term">term</a> or a <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a> to
+express the value of a type.</p>
+
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">
+  The <code>@type</code> <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a> is also used to associate a type with
+  a <a class="tref internalDFN" title="subject" href="#dfn-subject">subject</a>. Although the same keyword is used in both places,
+  the concept of an <em>object type</em> and a <em>value type</em>
+  are different. This is similar to object-oriented programming languages
+  where both scalar and structured types use the same class inheritance
+  mechanism, even though scalar types and structured types are
+  inherently different.
+</p></div>
+
+</div>
+
+<div id="external-contexts" class="section">
+<h3><span class="secno">4.3 </span>External Contexts</h3>
+
+<p>Authors may choose to declare JSON-LD <a class="tref internalDFN" title="context" href="#dfn-context">context</a>s in external
+documents to promote re-use of contexts as well as reduce the size of JSON-LD
+documents.
+</p>
+
+<p>
+In order to use an external context, an author <em class="rfc2119" title="must">must</em> specify an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>
+to a valid JSON-LD document. The referenced document <em class="rfc2119" title="must">must</em> have a
+top-level <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a>. The value of any <code>@context</code> key
+within that object is substituted for the <abbr title="Internationalized Resource Identifier">IRI</abbr> within the referencing document
+to have the same effect as if the value were specified inline within the
+referencing document.</p>
+
+<p>The following example demonstrates the use of an external context:</p>
+
+<div class="example"><div class="example-title"><span>Example 22</span></div><pre class="example">{
+  <span class="diff">&quot;@context&quot;: &quot;http://json-ld.org/contexts/person.jsonld&quot;</span>,
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
+  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
+}</pre></div>
+
+<p>Authors may also import multiple contexts or a combination of external
+and local contexts by specifying a list of contexts:</p>
+
+<div class="example"><div class="example-title"><span>Example 23</span></div><pre class="example">{
+  <span class="diff">&quot;@context&quot;:
+  [
+    &quot;http://json-ld.org/contexts/person.jsonld&quot;,
+    {
+      &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;
+    },
+    &quot;http://json-ld.org/contexts/event.jsonld&quot;
+  ],</span>
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
+  &quot;foaf:depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;,
+  <span class="diff">&quot;celebrates&quot;:
+  {
+    &quot;@type&quot;: &quot;Event&quot;,
+    &quot;description&quot;: &quot;International Talk Like a Pirate Day&quot;,
+    &quot;date&quot;: &quot;R/2011-09-19&quot;
+  }</span>
+}</pre></div>
+
+<p>Each context in a list will be evaluated in-order. Duplicate mappings among
+the <a class="tref internalDFN" title="context" href="#dfn-context">context</a>s <em class="rfc2119" title="must">must</em> be overwritten on a last-defined-overrides
+basis. The context list <em class="rfc2119" title="must">must</em> contain either de-referenceable <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>s
+or <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a>s that conform to the <a class="tref internalDFN" title="context" href="#dfn-context">context</a> syntax
+as described in this document.</p>
+
+<p>An author <em class="rfc2119" title="may">may</em> nest contexts within <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definitions</a>, with the
+more deeply nested contexts overriding the values in previously defined
+contexts:</p>
+
+<div class="example"><div class="example-title"><span>Example 24</span></div><pre class="example">{
+  <span class="diff">&quot;@context&quot;:
+  {
+    &quot;name&quot;: &quot;http://example.com/person#name&quot;,
+    &quot;details&quot;: &quot;http://example.com/person#details&quot;
+  },</span>
+  &quot;<span class="diff">name</span>&quot;: &quot;Markus Lanthaler&quot;,
+  ...
+  &quot;details&quot;:
+  {
+    <span class="diff">&quot;@context&quot;: {
+      &quot;name&quot;: &quot;http://example.com/organization#name&quot;
+    },</span>
+    &quot;<span class="diff">name</span>&quot;: &quot;Graz University of Technology&quot;
+  }
+}</pre></div>
+
+<p>In the example above, the <code>name</code> prefix is overridden in the
+more deeply nested <code>details</code> structure. Note that this is
+rarely a good authoring practice and is typically used when the
+JSON object has legacy applications using the structure of the object.</p>
+
+<p>External JSON-LD context documents <em class="rfc2119" title="may">may</em> contain extra information located
+outside of the <code>@context</code> key, such as
+documentation about the <a class="tref internalDFN" title="prefix" href="#dfn-prefix">prefixes</a> declared in the document.
+When importing a <code>@context</code> value from an external JSON-LD context
+document, any extra information contained outside of the
+<code>@context</code> value <em class="rfc2119" title="must">must</em> be discarded. It is
+also <em class="rfc2119" title="recommended">recommended</em> that a human-readable document is served as well to
+explain the correct usage of the JSON-LD context document.
+</p>
+</div>
+
+<div id="referencing-contexts-from-json-documents" class="section">
+<h3><span class="secno">4.4 </span>Referencing Contexts from JSON Documents</h3>
+
+<p>Ordinary JSON documents can be transformed into JSON-LD documents by referencing
+to an external JSON-LD <a class="tref internalDFN" title="context" href="#dfn-context">context</a> in an HTTP Link Header. Doing this
+allows JSON to be unambiguously machine-readable without requiring developers to
+drastically change their workflow and provides an upgrade path for existing
+infrastructure without breaking existing clients that rely on the <code>application/json</code>
+media type.
+</p>
+
+<p>
+In order to use an external context with an ordinary JSON document, an author
+<em class="rfc2119" title="must">must</em> specify an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> to a valid JSON-LD document in an HTTP Link
+Header [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC5988">RFC5988</a></cite>] using the <code>describedby</code> link relation.
+
+The referenced document <em class="rfc2119" title="must">must</em> have a top-level <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a>. The
+<code>@context</code> subtree within that object is added to the top-level
+<a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a> of the referencing document. If an <a class="tref internalDFN" title="array" href="#dfn-array">array</a> is at the top-level of the
+referencing document and its items are <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definitions</a>, the <code>@context</code>
+subtree is added to all <a class="tref internalDFN" title="array" href="#dfn-array">array</a> items. All extra information located outside
+of the <code>@context</code> subtree in the referenced document <em class="rfc2119" title="must">must</em> be
+discarded.
+</p>
+
+<p>The following example demonstrates the use of an external context with an
+ordinary JSON document:</p>
+
+<div class="example"><div class="example-title"><span>Example 25</span></div><pre class="example">GET /ordinary-json-document.json HTTP/1.1
+Host: example.com
+Accept: application/ld+json,application/json,*/*;q=0.1
+
+====================================
+
+HTTP/1.0 200 OK
+...
+Content-Type: <span class="diff">application/json</span>
+<span class="diff">Link: &lt;http://json-ld.org/contexts/person.jsonld&gt;; rel=&quot;describedby&quot;; type=&quot;application/ld+json&quot;</span>
+
+{
+  &quot;name&quot;: &quot;Markus Lanthaler&quot;,
+  &quot;homepage&quot;: &quot;http://www.markus-lanthaler.com/&quot;,
+  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/markuslanthaler&quot;
+}</pre></div>
+
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">JSON-LD documents served with the <code>application/ld+json</code> media type
+  <em class="rfc2119" title="must">must</em> have all context information, including references to external contexts, within the
+  body of the document.</p></div>
+</div>
+
+<div id="expanded-term-definition" class="section">
+<h3><span class="secno">4.5 </span>Expanded Term Definition</h3>
+
+<p>Within a <a class="tref internalDFN" title="context" href="#dfn-context">context</a> definition, <a class="tref internalDFN" title="term" href="#dfn-term">term</a>s <em class="rfc2119" title="may">may</em> be
+   defined using an expanded notation to allow for additional information
+   associated with the term to be specified (see also
+   <a href="#type-coercion">Type Coercion</a> and
+   <a href="#sets-and-lists">Sets and Lists</a>).</p>
+
+<p>Instead of using a string representation of an <abbr title="Internationalized Resource Identifier">IRI</abbr>, the <abbr title="Internationalized Resource Identifier">IRI</abbr> <em class="rfc2119" title="may">may</em> be
+specified using a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> having an <code>@id</code> key.
+The value of the <code>@id</code> key <em class="rfc2119" title="must">must</em> be either a <a class="tref internalDFN" title="term" href="#dfn-term">term</a>, a
+<a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a>, or an <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a>. Such
+an object is called a <a class="tref internalDFN" title="subject_reference" href="#dfn-subject_reference">subject reference</a>.</p>
+
+<div class="example"><div class="example-title"><span>Example 26</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;foaf&quot;: <span class="diff">{ &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/&quot; }</span>,
+    &quot;name&quot;: <span class="diff">{ &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot; }</span>,
+    &quot;homepage&quot;: <span class="diff">{ &quot;@id&quot;: &quot;foaf:homepage&quot; }</span>,
+    &quot;depiction&quot;: <span class="diff">{ &quot;@id&quot;: &quot;foaf:depiction&quot; }</span>
+  },
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;,
+  &quot;depiction&quot;: &quot;http://twitter.com/account/profile_image/manusporny&quot;
+}</pre></div>
+
+<p>This allows additional information to be associated with the term. This
+  <em class="rfc2119" title="may">may</em> be used for <a href="#type-coercion">Type Coercion</a>,
+  <a href="#sets-and-lists">Sets and Lists</a>), or to associate language
+  information with a term as shown in the following example:</p>
+
+<div class="example"><div class="example-title"><span>Example 27</span></div><pre class="example">{
+  &quot;@context&quot;: {
+    ...
+    &quot;ex&quot;: &quot;http://example.com/&quot;,
+    &quot;@language&quot;: &quot;ja&quot;,
+    &quot;name&quot;: { &quot;@id&quot;: &quot;ex:name&quot;, <span class="diff">&quot;@language&quot;: null</span> },
+    &quot;occupation&quot;: { &quot;@id&quot;: &quot;ex:occupation&quot; },
+    &quot;occupation_en&quot;: { &quot;@id&quot;: &quot;ex:occupation&quot;, <span class="diff">&quot;@language&quot;: &quot;en&quot;</span> },
+    &quot;occupation_cs&quot;: { &quot;@id&quot;: &quot;ex:occupation&quot;, <span class="diff">&quot;@language&quot;: &quot;cs&quot;</span> }
+  },
+  <span class="diff">&quot;name&quot;: &quot;Yagyū Muneyoshi&quot;,
+  &quot;occupation&quot;: &quot;忍者&quot;,
+  &quot;occupation_en&quot;: &quot;Ninja&quot;,
+  &quot;occupation_cs&quot;: &quot;Nindža&quot;,</span>
+  ...
+}</pre></div>
+
+<p>The example above would associate <em>忍者</em> with the specified default
+  language code <code>ja</code>, <em>Ninja</em> with the language code
+  <code>en</code>, and <em>Nindža</em> with the language code <code>cs</code>.
+  The value of <code>name</code>, <em>Yagyū Muneyoshi</em> wouldn't be
+  associated with any language code since <code>@language</code> was reset to
+  <a class="tref internalDFN" title="null" href="#dfn-null">null</a> in the expanded term definition.</p>
+
+<p>Expanded terms <em class="rfc2119" title="may">may</em> also be defined using <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact IRIs</a> or
+  <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute IRIs</a> as keys. If the definition does not include an
+  <code>@id</code> key, the expanded <abbr title="Internationalized Resource Identifier">IRI</abbr> is determined by performing expansion of the key
+  within the current active context. This mechanism is mainly used to associate type or language
+  information with a <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a> or an <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a>.</p>
+
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">While it is possible to define a
+  <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a>, or an absolute <abbr title="Internationalized Resource Identifier">IRI</abbr> to expand to some
+  other unrelated <abbr title="Internationalized Resource Identifier">IRI</abbr> (for example, <code>foaf:name</code> expanding to
+  <code>http://example.org/unrelated#species</code>),
+  such usage is strongly discouraged.</p></div>
+</div>
+
+<div id="type-coercion" class="section">
+<h3><span class="secno">4.6 </span>Type Coercion</h3>
+
+<p>JSON-LD supports the coercion of values to particular data types.
+Type <dfn title="coercion" id="dfn-coercion">coercion</dfn> allows someone deploying JSON-LD to coerce the incoming or
+outgoing values to the proper data type based on a mapping of data type <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>s to
+<a class="tref internalDFN" title="term" href="#dfn-term">term</a>s. Using type coercion, value representation is preserved without requiring
+the data type to be specified with each piece of data.</p>
+
+<p>Type coercion is specified within an <a href="#expanded-term-definition">expanded term definition</a>
+  using the <code>@type</code> key. The value of this key represents a type <abbr title="Internationalized Resource Identifier">IRI</abbr> and <em class="rfc2119" title="must">must</em> take the form of
+  a <a class="tref internalDFN" title="term" href="#dfn-term">term</a>, <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a>, <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a>, or the <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a> <code>@id</code>. Specifying
+  <code>@id</code> indicates that within the body of a JSON-LD document, a string value of a <a class="tref internalDFN" title="term" href="#dfn-term">term</a> coerced to
+  <code>@id</code> is to be interpreted as an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.</p>
+
+<p><a class="tref internalDFN" title="term" href="#dfn-term">Terms</a> or <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact IRIs</a> used as the value of a
+  <code>@type</code> key <em class="rfc2119" title="may">may</em> be defined within the same context. This means that one may specify a
+  <a class="tref internalDFN" title="term" href="#dfn-term">term</a> like <code>xsd</code> and then use <code>xsd:integer</code> within the same
+  context definition - the JSON-LD processor will be able to determine the proper expansion for
+  <code>xsd:integer</code>.</p>
+
+<p>The example below demonstrates how a JSON-LD author can coerce values to
+<a class="tref internalDFN" title="typed_value" href="#dfn-typed_value">typed value</a>s, IRIs and lists.</p>
+
+<div class="example"><div class="example-title"><span>Example 28</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;,
+    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+    &quot;age&quot;:
+    <span class="diff">{
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/age&quot;,
+      &quot;@type&quot;: &quot;xsd:integer&quot;
+    }</span>,
+    &quot;homepage&quot;:
+    <span class="diff">{
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;,
+      &quot;@container&quot;: &quot;@list&quot;
+    }</span>
+  },
+  &quot;name&quot;: &quot;John Smith&quot;,
+  &quot;age&quot;: <span class="diff">&quot;41&quot;</span>,
+  &quot;homepage&quot;:
+  <span class="diff">[
+    &quot;http://personal.example.org/&quot;,
+    &quot;http://work.example.com/jsmith/&quot;
+  ]</span>
+}</pre></div>
+
+<p>The example above would generate the following Turtle:</p>
+
+<div class="example"><div class="example-title"><span>Example 29</span></div><pre class="example">@prefix xsd: &lt;http://www.w3.org/2001/XMLSchema#&gt; .
+
+[ foaf:name &quot;John Smith&quot;;
+  foaf:age  &quot;41&quot;^^xsd:integer;
+  foaf:homepage ( &lt;http://personal.example.org/&gt; &lt;http://work.example.com/jsmith/&gt; )
+] .</pre></div>
+
+<p>Terms may also be defined using <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute IRIs</a> or <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact IRIs</a>.
+  This allows coercion rules to be applied to keys which are not represented as a simple <a class="tref internalDFN" title="term" href="#dfn-term">term</a>.
+  For example:</p>
+
+<div class="example"><div class="example-title"><span>Example 30</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    <span class="diff">&quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;</span>,
+    &quot;<span class="diff">foaf:age</span>&quot;:
+    {
+      &quot;@type&quot;: &quot;xsd:integer&quot;
+    },
+    &quot;<span class="diff">foaf:homepage</span>&quot;:
+    <span class="diff">{
+      &quot;@type&quot;: &quot;@id&quot;
+    }</span>
+  },
+  &quot;foaf:name&quot;: &quot;John Smith&quot;,
+  &quot;foaf:age&quot;: <span class="diff">&quot;41&quot;</span>,
+  &quot;foaf:homepage&quot;:
+  <span class="diff">[
+    &quot;http://personal.example.org/&quot;,
+    &quot;http://work.example.com/jsmith/&quot;
+  ]</span>
+}</pre></div>
+
+<p>In this case the <code>@id</code> definition is optional, but if it does exist, the <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a>
+  or <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> is treated as a term (not a <code>prefix:suffix</code> construct)
+  so that the actual definition of a <a class="tref internalDFN" title="prefix" href="#dfn-prefix">prefix</a> becomes unnecessary.</p>
+
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">Keys in the context are treated as <a class="tref internalDFN" title="term" href="#dfn-term">terms</a> for the purpose of
+  expansion and value coercion. At times, this may result in multiple representations for the same expanded <abbr title="Internationalized Resource Identifier">IRI</abbr>.
+  For example, one could specify that <code>dog</code> and <code>cat</code> both expanded to <code>http://example.com/vocab#animal</code>.
+  Doing this could be useful for establishing different type coercion or language specification rules. It also allows a <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a> (or even an
+  absolute <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>) to be defined as something else entirely. For example, one could specify that
+  the <a class="tref internalDFN" title="term" href="#dfn-term">term</a> <code>http://example.org/zoo</code> should expand to
+  <code>http://example.org/river</code>, but this usage is discouraged because it would lead to a
+  great deal of confusion among developers attempting to understand the JSON-LD document.</p></div>
+
+<p>Type coercion is performed using the unexpanded value of the key,
+  which <em class="rfc2119" title="must">must</em> have an exact match for an entry in the <a class="tref internalDFN" title="active_context" href="#dfn-active_context">active context</a>.</p>
+
+</div>
+
+<div id="iri-expansion-within-a-context" class="section">
+  <h3><span class="secno">4.7 </span><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion Within a Context</h3>
+  <p>In general, normal <abbr title="Internationalized Resource Identifier">IRI</abbr> expansion rules apply
+    anywhere an <abbr title="Internationalized Resource Identifier">IRI</abbr> is expected (see <a href="#iris">IRIs</a>). Within
+    a <a class="tref internalDFN" title="context" href="#dfn-context">context</a> definition, this can mean that terms defined
+    within the context <em class="rfc2119" title="may">may</em> also be used within that context as long as
+    there are no circular dependencies. For example, it is common to use
+    the <code>xsd</code> namespace when defining <a class="tref internalDFN" title="typed_value" href="#dfn-typed_value">typed value</a>s:</p>
+<div class="example"><div class="example-title"><span>Example 31</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    <span class="diff">&quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;</span>,
+    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+    &quot;age&quot;:
+    {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/age&quot;,
+      &quot;@type&quot;: <span class="diff">&quot;xsd:integer&quot;</span>
+    },
+    &quot;homepage&quot;:
+    {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    }
+  },
+  ...
+}</pre></div>
+<p>In this example, the <code>xsd</code> <a class="tref internalDFN" title="term" href="#dfn-term">term</a> is defined
+  and used as a <a class="tref internalDFN" title="prefix" href="#dfn-prefix">prefix</a> for the <code>@type</code> coercion
+  of the <code>age</code> property.</p>
+
+<p><a class="tref internalDFN" title="term" href="#dfn-term">Term</a>s <em class="rfc2119" title="may">may</em> also be used when defining the <abbr title="Internationalized Resource Identifier">IRI</abbr> of another
+<a class="tref internalDFN" title="term" href="#dfn-term">term</a>:</p>
+
+<div class="example"><div class="example-title"><span>Example 32</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    <span class="diff">&quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;</span>,
+    &quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;,
+    &quot;name&quot;: <span class="diff">&quot;foaf:name&quot;</span>,
+    &quot;age&quot;:
+    {
+      &quot;@id&quot;: <span class="diff">&quot;foaf:age&quot;</span>,
+      &quot;@type&quot;: &quot;xsd:integer&quot;
+    },
+    &quot;homepage&quot;:
+    {
+      &quot;@id&quot;: <span class="diff">&quot;foaf:homepage&quot;</span>,
+      &quot;@type&quot;: &quot;@id&quot;
+    }
+  },
+  ...
+}</pre></div>
+
+<p><a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">Compact IRIs</a>
+  and <a class="tref internalDFN" title="iri" href="#dfn-iri">IRIs</a> <em class="rfc2119" title="may">may</em> be used on the left-hand side of a
+  <a class="tref internalDFN" title="term" href="#dfn-term">term</a> definition.</p>
+
+<div class="example"><div class="example-title"><span>Example 33</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    <span class="diff">&quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;</span>,
+    &quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;,
+    &quot;name&quot;: &quot;foaf:name&quot;,
+    &quot;<span class="diff">foaf:age</span>&quot;:
+    {
+      &quot;@type&quot;: &quot;xsd:integer&quot;
+    },
+    &quot;<span class="diff">foaf:homepage</span>&quot;:
+    <span class="diff">{
+      &quot;@type&quot;: &quot;@id&quot;
+    }</span>
+  },
+  ...
+}</pre></div>
+
+<p>
+In this example, the <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a> form is used in two different
+ways.
+In the first approach, <code>foaf:age</code> declares both the
+<a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> for the term (using short-form) as well as the
+<code>@type</code> associated with the <a class="tref internalDFN" title="term" href="#dfn-term">term</a>. In the second
+approach, only the <code>@type</code> associated with the <a class="tref internalDFN" title="term" href="#dfn-term">term</a> is
+specified. The JSON-LD processor will derive the full <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> for
+<code>foaf:homepage</code> by looking up the <code>foaf</code>
+<a class="tref internalDFN" title="prefix" href="#dfn-prefix">prefix</a> in the
+<a class="tref internalDFN" title="context" href="#dfn-context">context</a>.
+</p>
+
+<p>
+<a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">Absolute IRIs</a> <em class="rfc2119" title="may">may</em> also be used in the key position in a <a class="tref internalDFN" title="context" href="#dfn-context">context</a>:
+</p>
+
+<div class="example"><div class="example-title"><span>Example 34</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;,
+    &quot;xsd&quot;: &quot;http://www.w3.org/2001/XMLSchema#&quot;,
+    &quot;name&quot;: &quot;foaf:name&quot;,
+    &quot;foaf:age&quot;:
+    {
+      &quot;@id&quot;: &quot;foaf:age&quot;,
+      &quot;@type&quot;: &quot;xsd:integer&quot;
+    },
+    &quot;<span class="diff">http://xmlns.com/foaf/0.1/homepage</span>&quot;:
+    {
+      &quot;@type&quot;: &quot;@id&quot;
+    }
+  },
+  ...
+}</pre></div>
+
+<p>
+In order for the <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a> to match above, the <a class="tref internalDFN" title="absolute_iri" href="#dfn-absolute_iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a> <em class="rfc2119" title="must">must</em> also
+be used in the JSON-LD document. Also note that <code>foaf:homepage</code>
+will not use the <code>{ &quot;@type&quot;: &quot;@id&quot; }</code> declaration because
+<code>foaf:homepage</code> is not the same as
+<code>http://xmlns.com/foaf/0.1/homepage</code>. That is, a JSON-LD
+processor will use direct string comparison when looking up
+<a class="tref internalDFN" title="term" href="#dfn-term">term</a>s in a <a class="tref internalDFN" title="context" href="#dfn-context">context</a> before it applies the
+<a class="tref internalDFN" title="prefix" href="#dfn-prefix">prefix</a> lookup mechanism.
+</p>
+
+<p>The only exception for using terms in the <a class="tref internalDFN" title="context" href="#dfn-context">context</a> is that
+  they <em class="rfc2119" title="must not">must not</em> be used in a circular manner. That is,
+  a definition of <em>term-1</em> <em class="rfc2119" title="must not">must not</em> depend on the
+  definition of <em>term-2</em> if <em>term-2</em> also depends on
+  <em>term-1</em>. For example, the following <a class="tref internalDFN" title="context" href="#dfn-context">context</a> definition
+  is illegal:</p>
+<div class="example"><div class="example-title"><span>Example 35</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    <span class="diff">&quot;term1&quot;: &quot;term2:foo&quot;,
+    &quot;term2&quot;: &quot;term1:bar&quot;</span>
+  },
+  ...
+}</pre></div>
+</div>
+
+<div id="sets-and-lists" class="section">
+<h3><span class="secno">4.8 </span>Sets and Lists</h3>
+
+<p>A JSON-LD author can express multiple values in a compact way by using
+  <a class="tref internalDFN" title="array" href="#dfn-array">array</a>s. Since graphs do not describe ordering for links
+  between nodes, arrays in JSON-LD do not provide an ordering of the
+  listed <a class="tref internalDFN" title="object" href="#dfn-object">objects</a> by default. This is exactly the opposite from regular JSON
+  arrays, which are ordered by default. For example, consider the following
+  simple document:</p>
+<div class="example"><div class="example-title"><span>Example 36</span></div><pre class="example">{
+...
+  &quot;@id&quot;: &quot;http://example.org/people#joebob&quot;,
+  &quot;nick&quot;: <span class="diff">[ &quot;joe&quot;, &quot;bob&quot;, &quot;jaybee&quot; ]</span>,
+...
+}</pre></div>
+
+<p>The markup shown above would result in three triples being generated,
+  each relating the subject to an individual <a class="tref internalDFN" title="object" href="#dfn-object">object</a>, with no inherent order:</p>
+<div class="example"><div class="example-title"><span>Example 37</span></div><pre class="example">&lt;http://example.org/people#joebob&gt;
+   &lt;http://xmlns.com/foaf/0.1/nick&gt;
+      &quot;joe&quot; .
+&lt;http://example.org/people#joebob&gt;
+   &lt;http://xmlns.com/foaf/0.1/nick&gt;
+      &quot;bob&quot; .
+&lt;http://example.org/people#joebob&gt;
+   &lt;http://xmlns.com/foaf/0.1/nick&gt;
+      &quot;jaybee&quot; .</pre></div>
+
+<p>Multiple values may also be expressed using the expanded form:</p>
+
+<div class="example"><div class="example-title"><span>Example 38</span></div><pre class="example">{
+  &quot;@id&quot;: &quot;http://example.org/articles/8&quot;,
+  &quot;dc:title&quot;: <span class="diff">
+  [
+    {
+      &quot;@value&quot;: &quot;Das Kapital&quot;,
+      &quot;@language&quot;: &quot;de&quot;
+    },
+    {
+      &quot;@value&quot;: &quot;Capital&quot;,
+      &quot;@language&quot;: &quot;en&quot;
+    }
+  ]</span>
+}</pre></div>
+
+<p>The markup shown above would generate the following triples, again with
+  no inherent order:</p>
+
+<div class="example"><div class="example-title"><span>Example 39</span></div><pre class="example">&lt;http://example.org/articles/8&gt;
+   &lt;http://purl.org/dc/terms/title&gt;
+      &quot;Das Kapital&quot;@de .
+&lt;http://example.org/articles/8&gt;
+   &lt;http://purl.org/dc/terms/title&gt;
+      &quot;Capital&quot;@en .</pre></div>
+
+
+<p>As the notion of ordered collections is rather important in data
+  modeling, it is useful to have specific language support. In JSON-LD,
+  a list may be represented using the <code>@list</code> <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a> as follows:</p>
+<div class="example"><div class="example-title"><span>Example 40</span></div><pre class="example">{
+...
+  &quot;@id&quot;: &quot;http://example.org/people#joebob&quot;,
+  &quot;foaf:nick&quot;:
+  <span class="diff">{
+    &quot;@list&quot;: [ &quot;joe&quot;, &quot;bob&quot;, &quot;jaybee&quot; ]
+  }</span>,
+...
+}</pre></div>
+
+<p>This describes the use of this <a class="tref internalDFN" title="array" href="#dfn-array">array</a> as being ordered,
+  and order is maintained when processing a document. If every use of a given multi-valued
+  property is a list, this may be abbreviated by setting <code>@container</code>
+  to <code>@list</code> in the <a class="tref internalDFN" title="context" href="#dfn-context">context</a>:</p>
+<div class="example"><div class="example-title"><span>Example 41</span></div><pre class="example">{
+  <span class="diff">&quot;@context&quot;:
+  {
+    ...
+    &quot;nick&quot;:
+    {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/nick&quot;,
+      &quot;@container&quot;: &quot;@list&quot;
+    }
+  }</span>,
+...
+  &quot;@id&quot;: &quot;http://example.org/people#joebob&quot;,
+  &quot;nick&quot;: <span class="diff">[ &quot;joe&quot;, &quot;bob&quot;, &quot;jaybee&quot; ]</span>,
+...
+}</pre></div>
+
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">List of lists are not allowed in this version of JSON-LD.
+  If a list of lists is detected, a JSON-LD processor will throw an exception.
+  This decision was made due to the extreme amount of added complexity when
+  processing lists of lists.</p></div>
+
+<p>Similarly to <code>@list</code>, there exists the <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a> <code>@set</code> to
+  describe unordered sets. While its use in the body of a JSON-LD document
+  represents just syntactic sugar that <em class="rfc2119" title="must">must</em> be optimized away when processing
+  the document, it is very helpful when used within the context of a document.
+  Values of terms associated with a <code>@set</code> or <code>@list</code> container
+  are always represented in the form of an <a class="tref internalDFN" title="array" href="#dfn-array">array</a> - even if there is just a
+  single value that would otherwise be optimized to a non-array form in a
+  <a href="#compact-document-form">compacted document</a>. This makes post-processing of
+  the data easier as the data is always in array form, even if the array only
+  contains a single value.</p>
+
+<div class="note"><div class="note-title"><span>Note</span></div><p class="">The use of <code>@container</code> in the body of a JSON-LD
+  document, i.e., outside <code>@context</code> <em class="rfc2119" title="must">must</em> be ignored by
+  JSON-LD processors.</p></div>
+
+</div>
+
+<div id="embedding" class="section">
+  <h3><span class="secno">4.9 </span>Embedding</h3>
+  <p>
+    Object <dfn title="embedding" id="dfn-embedding">embedding</dfn> is a JSON-LD feature that allows an author to 
+    use <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definitions</a> as 
+    <a class="tref internalDFN" title="property" href="#dfn-property">property</a> values. This is a commonly used mechanism for 
+    creating a parent-child relationship between two <a class="tref internalDFN" title="subject" href="#dfn-subject">subject</a>s.</p>
+  <p>The example shows two subjects related by a property from the first subject:</p>
+
+  <div class="example"><div class="example-title"><span>Example 42</span></div><pre class="example">{
+...
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;<span class="diff">knows</span>&quot;:
+  {
+    &quot;<span class="diff">@type</span>&quot;: &quot;<span class="diff">Person</span>&quot;,
+    &quot;<span class="diff">name</span>&quot;: &quot;<span class="diff">Gregg Kellogg</span>&quot;,
+  }
+...
+}</pre></div>
+
+  <p>
+    A <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a>, like the one used above, <em class="rfc2119" title="may">may</em> be used in 
+    any value position in the body of a JSON-LD document.</p>
+</div>
+
+<div id="named-graphs" class="section">
+  <h3><span class="secno">4.10 </span>Named Graphs</h3>
+  <p>The <code>@graph</code> <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a> is used to express a set of
+    JSON-LD <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a>s that may not be directly related
+    to one another through a property. The mechanism may also be used where
+    <a class="tref internalDFN" title="embedding" href="#dfn-embedding">embedding</a> is not desirable to the application. For example:</p>
+
+  <div class="example"><div class="example-title"><span>Example 43</span></div><pre class="example">{
+  &quot;@context&quot;: ...,
+  &quot;<span class="diff">@graph</span>&quot;:
+  [
+    {
+      &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
+      &quot;@type&quot;: &quot;foaf:Person&quot;,
+      &quot;name&quot;: &quot;Manu Sporny&quot;,
+      &quot;knows&quot;: &quot;http://greggkellogg.net/foaf#me&quot;
+    },
+    {
+      &quot;@id&quot;: &quot;http://greggkellogg.net/foaf#me&quot;,
+      &quot;@type&quot;: &quot;foaf:Person&quot;,
+      &quot;name&quot;: &quot;Gregg Kellogg&quot;,
+      &quot;knows&quot;: &quot;http://manu.sporny.org/i/public&quot;
+    }
+  ]
+}</pre></div>
+
+  <p>In this case, embedding doesn't work as each
+    <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a> references the other. Using the 
+    <code>@graph</code> <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a> allows multiple resources to be 
+    defined within an <a class="tref internalDFN" title="array" href="#dfn-array">array</a>, and allows the use of a shared 
+    <a class="tref internalDFN" title="context" href="#dfn-context">context</a>. When used in a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> that is not otherwise
+    a <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a>, this describes resources in the <em>default graph</em>.
+    This is equivalent to using multiple <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definitions</a> in array and defining 
+    the <code>@context</code> within each <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a>:</p>
+
+  <div class="example"><div class="example-title"><span>Example 44</span></div><pre class="example"><span class="diff">[</span>
+  {
+    <span class="diff">&quot;@context&quot;: ...,</span>
+    &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
+    &quot;@type&quot;: &quot;foaf:Person&quot;,
+    &quot;name&quot;: &quot;Manu Sporny&quot;,
+    &quot;knows&quot;: &quot;http://greggkellogg.net/foaf#me&quot;
+  },
+  {
+    <span class="diff">&quot;@context&quot;: ...,</span>
+    &quot;@id&quot;: &quot;http://greggkellogg.net/foaf#me&quot;,
+    &quot;@type&quot;: &quot;foaf:Person&quot;,
+    &quot;name&quot;: &quot;Gregg Kellogg&quot;,
+    &quot;knows&quot;: &quot;http://manu.sporny.org/i/public&quot;
+  }
+<span class="diff">]</span></pre></div>
+
+  <p>JSON-LD allows you to <em>name</em> things on the Web by assigning
+    an <code>@id</code> to them, which is typically an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.
+    This notion extends to the ability to identify graphs in the same
+    manner. A developer may name data expressed using the <code>@graph</code>
+    <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a> by pairing it with an <code>@id</code>
+    <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a>. This enables the developer to make statements
+    about a <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a> itself,
+    rather than just a single <a class="tref internalDFN" title="subject" href="#dfn-subject">subject</a>.</p>
+
+  <div class="example"><div class="example-title"><span>Example 45</span></div><pre class="example">{
+  &quot;@context&quot;: ...,
+  <span class="diff">&quot;@id&quot;: &quot;http://example.org/graphs/73&quot;,
+  &quot;asOf&quot;: { &quot;@value&quot;: &quot;2012-04-09&quot;, &quot;@type&quot;: &quot;xsd:date&quot; },
+  &quot;@graph&quot;:</span>
+  [
+    {
+      &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
+      &quot;@type&quot;: &quot;foaf:Person&quot;,
+      &quot;name&quot;: &quot;Manu Sporny&quot;,
+      &quot;knows&quot;: &quot;http://greggkellogg.net/foaf#me&quot;
+    },
+    {
+      &quot;@id&quot;: &quot;http://greggkellogg.net/foaf#me&quot;,
+      &quot;@type&quot;: &quot;foaf:Person&quot;,
+      &quot;name&quot;: &quot;Gregg Kellogg&quot;,
+      &quot;knows&quot;: &quot;http://manu.sporny.org/i/public&quot;
+    }
+  ]
+}</pre></div>
+
+  <p>The example above expresses a <em>named</em>
+    <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a> that is identified by the <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>
+    <code>http://example.org/graphs/73</code>. That graph is composed of the
+    statements about Manu and Gregg. Meta-data about the graph itself is also
+    expressed via the <code>asOf</code> property, which specifies when the
+    information was retrieved from the Web.</p>
+
+  <div class="issue"><div class="issue-title"><span>Issue 3</span></div><p class="">These examples could all have TriG definitions of their RDF results,
+    but that would involve adding RDF earlier in the document.</p></div>
+
+</div>
+
+<div id="identifying-unlabeled-nodes" class="section">
+<h3><span class="secno">4.11 </span>Identifying Unlabeled Nodes</h3>
+
+<p>At times, it becomes necessary to be able to express information without
+being able to specify the subject. Typically, this type of node is called
+an <dfn title="unlabeled_node" id="dfn-unlabeled_node">unlabeled node</dfn> or a blank node (see [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>] <cite><a href="http://www.w3.org/TR/rdf11-concepts/#section-blank-nodes">Section 3.4: Blank Nodes</a></cite>).
+In JSON-LD, <a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">unlabeled node</a> identifiers are
+automatically created if a subject is not specified using the
+<code>@id</code> <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a>. However, authors may provide identifiers for
+<a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">unlabeled nodes</a> by using the special <code>_</code> (underscore)
+<a class="tref internalDFN" title="prefix" href="#dfn-prefix">prefix</a>. This allows one to reference the node locally within the
+document, but makes it impossible to reference the node from an
+external document. The <a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">unlabeled node</a> identifier is scoped to the
+document in which it is used.</p>
+
+<div class="example"><div class="example-title"><span>Example 46</span></div><pre class="example">{
+...
+  &quot;@id&quot;: &quot;<span class="diff">_:foo</span>&quot;,
+...
+}</pre></div>
+
+<p>The example above would set the subject to <code>_:foo</code>, which can
+then be used elsewhere in the JSON-LD document to refer back to the
+<a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">unlabeled node</a>. If a developer finds that they refer to the unlabeled
+node more than once, they should consider naming the node using a de-referenceable
+<a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> so that it can be referenced also from other documents.
+</p>
+
+</div>
+
+<div id="aliasing-keywords" class="section">
+<h3><span class="secno">4.12 </span>Aliasing Keywords</h3>
+
+<p>Each of the JSON-LD <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keywords</a>,
+except for <code>@context</code>, <em class="rfc2119" title="may">may</em> be aliased to application-specific
+keywords. This feature allows legacy JSON content to be utilized
+by JSON-LD by re-using JSON keys that already exist in legacy documents.
+This feature also allows developers to design domain-specific implementations
+using only the JSON-LD <a class="tref internalDFN" title="context" href="#dfn-context">context</a>.</p>
+
+<div class="example"><div class="example-title"><span>Example 47</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+     <span class="diff">&quot;url&quot;: &quot;@id&quot;</span>,
+     <span class="diff">&quot;a&quot;: &quot;@type&quot;</span>,
+     &quot;name&quot;: &quot;http://schema.org/name&quot;
+  },
+  &quot;<span class="diff">url</span>&quot;: &quot;http://example.com/about#gregg&quot;,
+  &quot;<span class="diff">a</span>&quot;: &quot;http://schema.org/Person&quot;,
+  &quot;name&quot;: &quot;Gregg Kellogg&quot;
+}</pre></div>
+
+<p>In the example above, the <code>@id</code> and <code>@type</code>
+<a class="tref internalDFN" title="keyword" href="#dfn-keyword">keywords</a> have been given the aliases <strong>url</strong> and
+<strong>a</strong>, respectively.
+</p>
+
+</div>
+
+<div id="expanded-document-form" class="section">
+<h3><span class="secno">4.13 </span>Expanded Document Form</h3>
+<p>The JSON-LD API [<cite><a class="bibref" rel="biblioentry" href="#bib-JSON-LD-API">JSON-LD-API</a></cite>] defines an method for <em>expanding</em> a
+  JSON-LD document.
+  Expansion is the process of taking a JSON-LD document and applying a
+  <code>@context</code> such that all IRIs, types, and values
+  are expanded so that the <code>@context</code> is no longer necessary.</p>
+
+<p>For example, assume the following JSON-LD input document:</p>
+
+<div class="example"><div class="example-title"><span>Example 48</span></div><pre class="example">{
+   &quot;@context&quot;:
+   {
+      &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+      &quot;homepage&quot;: {
+        &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+        &quot;@type&quot;, &quot;@id&quot;
+      }
+   },
+   &quot;name&quot;: &quot;Manu Sporny&quot;,
+   &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;
+}</pre></div>
+
+<p>Running the JSON-LD Expansion algorithm against the JSON-LD input document
+  provided above would result in the following output:</p>
+
+<div class="example"><div class="example-title"><span>Example 49</span></div><pre class="example">[
+  {
+    &quot;http://xmlns.com/foaf/0.1/name&quot;: [
+      { &quot;@value&quot;: &quot;Manu Sporny&quot; }
+    ],
+    &quot;http://xmlns.com/foaf/0.1/homepage&quot;: [
+      { &quot;@id&quot;: &quot;http://manu.sporny.org/&quot; }
+    ]
+  }
+]</pre></div>
+
+<p>Expanded document form is useful when an application has to process input
+data in a deterministic form. It has been optimized to ensure that the code
+that developers have to write is minimized compared to the code that would
+have to be written to operate on
+<a href="#compact-document-form">compact document form</a>.</p>
+
+</div>
+
+<div id="compact-document-form" class="section">
+<h3><span class="secno">4.14 </span>Compact Document Form</h3>
+<p>The JSON-LD API [<cite><a class="bibref" rel="biblioentry" href="#bib-JSON-LD-API">JSON-LD-API</a></cite>] defines a method for <em>compacting</em> a JSON-LD document.
+  Compaction is the process of taking a JSON-LD document and applying a
+  context such that the most compact form of the document is generated. JSON
+  is typically expressed in a very compact, key-value format. That is, full
+  IRIs are rarely used as keys. At times, a JSON-LD document may be received
+  that is not in its most compact form. JSON-LD, via the API, provides a way
+  to compact a JSON-LD document.</p>
+
+<p>For example, assume the following JSON-LD input document:</p>
+
+<div class="example"><div class="example-title"><span>Example 50</span></div><pre class="example">[
+  {
+    &quot;http://xmlns.com/foaf/0.1/name&quot;: [ &quot;Manu Sporny&quot; ],
+    &quot;http://xmlns.com/foaf/0.1/homepage&quot;: [
+      {
+       &quot;@id&quot;: &quot;http://manu.sporny.org/&quot;
+      }
+    ]
+  }
+]</pre></div>
+
+<p>Additionally, assume the following developer-supplied JSON-LD context:</p>
+
+<div class="example"><div class="example-title"><span>Example 51</span></div><pre class="example">{
+  &quot;@context&quot;: {
+    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+    &quot;homepage&quot;: {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    }
+  }
+}</pre></div>
+
+<p>Running the JSON-LD Compaction algorithm given the context supplied above
+  against the JSON-LD input document provided above would result in the following
+  output:</p>
+
+<div class="example"><div class="example-title"><span>Example 52</span></div><pre class="example">{
+  &quot;@context&quot;: {
+    &quot;name&quot;: &quot;http://xmlns.com/foaf/0.1/name&quot;,
+    &quot;homepage&quot;: {
+      &quot;@id&quot;: &quot;http://xmlns.com/foaf/0.1/homepage&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    }
+  },
+  &quot;name&quot;: &quot;Manu Sporny&quot;,
+  &quot;homepage&quot;: &quot;http://manu.sporny.org/&quot;
+}</pre></div>
+
+<p>The compaction algorithm enables a developer to map any document into an
+  application-specific compacted form by first <a href="#expanded-document-form">expanding the document</a>.
+  While the context provided above mapped <code>http://xmlns.com/foaf/0.1/name</code>
+  to <strong>name</strong>, it could have also mapped it to any arbitrary string
+  provided by the developer. This powerful mechanism, along with another
+  JSON-LD API technique called <em>framing</em>, allows the developer to
+  re-shape the incoming JSON data into a format that is optimized for
+  their application.</p>
+</div>
+
+</div>
+
+<div class="appendix normative section" id="json-ld-authoring-guidelines">
+
+<!-- OddPage -->
+<h2><span class="secno">A. </span>JSON-LD Authoring Guidelines</h2>
+
+<p>Since the JSON-LD syntax is a subset of the JSON syntax, it follows that
+all valid JSON-LD documents are valid JSON documents. It also
+means that an invalid JSON document can never be a valid
+JSON-LD document. Furthermore, JSON-LD places a number of restrictions on
+the JSON syntax in order to define a set of authoring <em>guidelines</em>
+that are used to express <em>well-formed</em> JSON-LD documents. At times,
+even if these guidelines are violated, a JSON-LD processor will do its best
+to recover from the mistake and will deterministically transform the author's
+markup into well-formed JSON-LD.</p>
+
+<div class="issue"><div class="issue-title"><span>Issue 4</span></div><p class="">The final details of the guidelines are still being
+discussed (<a href="https://github.com/json-ld/json-ld.org/issues/114#issuecomment-5820544">ISSUE-114</a>),
+as well as the best mechanism to express these restrictions.
+EBNF doesn't quite capture what these guidelines are attempting to do -
+which is strongly express what constitutes a well-formed JSON-LD document.
+For the time being, a simple list of plain English guidelines are provided.
+</p></div>
+
+<div class="issue"><div class="issue-title"><span>Issue 5</span></div><p class="">Per
+  <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2012Jun/0111.html">Andy S's comment</a>,
+  consider making this a normative syntax definition along with EBNF.</p></div>
+
+<ol>
+<li>A JSON-LD document is composed of a single <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a> or an <a class="tref internalDFN" title="array" href="#dfn-array">array</a> of <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definitions</a>.</li>
+<li>The value of <code>@id</code> <em class="rfc2119" title="must">must</em> be a <a class="tref internalDFN" title="term" href="#dfn-term">term</a>, a <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a>, or an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.</li>
+<li>An <code>@id</code> keyword and a <code>@language</code> keyword <em class="rfc2119" title="must not">must not</em> exist in the same <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a>.</li>
+<li>An <code>@id</code> keyword and a <code>@container</code> keyword <em class="rfc2119" title="must not">must not</em> exist in the same <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a>.</li>
+<li>A <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a> <em class="rfc2119" title="may">may</em> contain a <code>@context</code> property.</li>
+<li>A <code>@context</code> value <em class="rfc2119" title="must not">must not</em> contain an embedded <code>@context</code> definition.</li>
+<li>The value associated with the <code>@context</code> keyword <em class="rfc2119" title="must">must</em> be a string expanding to an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>, a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a>, null, or an <a class="tref internalDFN" title="array" href="#dfn-array">array</a> containing a combination of the allowed values.</li>
+<li>The value associated with the keys used in a <code>@context</code> <em class="rfc2119" title="must">must</em> be a <code>null</code>, an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>, or a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a>.</li>
+<li>For each value that is a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> that is associated with a key in a <code>@context</code>:
+  <ol>
+    <li><code>@id</code> and <code>@type</code> <em class="rfc2119" title="must">must</em> be an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> or <code>null</code></li>
+    <li><code>@container</code> <em class="rfc2119" title="must">must</em> be associated with a value of either <code>@set</code> or <code>@list</code>.</li>
+    <li><code>@language</code> <em class="rfc2119" title="must">must</em> be a string expressed in [<cite><a class="bibref" rel="biblioentry" href="#bib-BCP47">BCP47</a></cite>] or <code>null</code>.</li>
+    <li>Any other property <em class="rfc2119" title="must">must</em> be ignored by a JSON-LD processor and <em class="rfc2119" title="must">must</em> be preserved in compaction and framing.</li>
+  </ol>
+</li>
+<li>A <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a> <em class="rfc2119" title="may">may</em> have an <code>@graph</code> property.</li>
+<li>The value of a <code>@graph</code> property <em class="rfc2119" title="must">must</em> be a
+  <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definition</a> or an array of zero or more
+  <a class="tref internalDFN" title="subject_definition" href="#dfn-subject_definition">subject definitions</a>.</li>
+<li>A <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> containing a <code>@set</code> key <em class="rfc2119" title="must not">must not</em> have any other keys.</li>
+<li>A <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> containing a <code>@list</code> key <em class="rfc2119" title="must not">must not</em> have any other keys.</li>
+<li>The value of an <code>@set</code> or <code>@list</code> key can be a string, a number, a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a>, or an <a class="tref internalDFN" title="array" href="#dfn-array">array</a> containing a combination of the allowed values.</li>
+<li>For each <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a> that contains a <code>@value</code> key:
+  <ol>
+    <li>It <em class="rfc2119" title="may">may</em> have a <code>@language</code> or <code>@type</code> property and <em class="rfc2119" title="must not">must not</em> have any other properties.</li>
+    <li>It <em class="rfc2119" title="must not">must not</em> contain both the <code>@language</code> and <code>@type</code> keys at the same time.</li>
+    <li>The value of the <code>@value</code> key <em class="rfc2119" title="must">must</em> be a string or a number.</li>
+    <li>The value of the <code>@language</code> key <em class="rfc2119" title="must">must</em> be <code>null</code> or a string in [<cite><a class="bibref" rel="biblioentry" href="#bib-BCP47">BCP47</a></cite>] format.</li>
+    <li>The value of <code>@type</code> <em class="rfc2119" title="must">must</em> be <code>null</code>, a <a class="tref internalDFN" title="term" href="#dfn-term">term</a>, a <a class="tref internalDFN" title="compact_iri" href="#dfn-compact_iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></a>, an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>, a <a class="tref internalDFN" title="json_object" href="#dfn-json_object">JSON object</a>, or an <a class="tref internalDFN" title="array" href="#dfn-array">array</a> containing a combination of the allowed values.</li>
+  </ol>
+</li>
+<li>In the body of a JSON-LD document, the value of <code>@type</code> <em class="rfc2119" title="must not">must not</em> be <code>@id</code>. This is in contrast to the use of <code>@type</code> in the <code>@context</code>, where this is allowed.</li>
+</ol>
+
+</div>
+
+<div class="appendix informative section" id="relationship-to-other-rdf-formats">
+
+<!-- OddPage -->
+<h2><span class="secno">B. </span>Relationship to other RDF Formats</h2><p><em>This section is non-normative.</em></p>
+
+<div class="issue"><div class="issue-title"><span>Issue 6</span></div><p class="">
+The intent of the Working Group and the Editors of this specification is to
+eventually align terminology used in this document with the terminology used
+in the RDF Concepts document [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>] to the extent to which it makes sense to do so.
+In general, if there is an analogue to terminology used in this document in
+the RDF Concepts document, the preference is to use the terminology in the
+RDF Concepts document.
+</p></div>
+
+<p>JSON-LD is a specification for representing <a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">Linked Data</a> in JSON. A common
+  way of working with Linked Data is through <dfn title="rdf" id="dfn-rdf">RDF</dfn>, the Resource Description Framework.
+  RDF can be expressed using JSON-LD by associating JSON-LD concepts such as <code>@id</code>
+  and <code>@type</code> with the equivalent <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>s in RDF. Further information about
+  RDF may be found in the [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-PRIMER">RDF-PRIMER</a></cite>].</p>
+
+<p>The JSON-LD markup examples below demonstrate how JSON-LD can be used to
+  express semantic data marked up in other languages and data models
+  such as RDF, Turtle, RDFa, Microformats,
+  and Microdata. These sections are merely provided as evidence that JSON-LD is
+  very flexible in what it can express across different <a class="tref internalDFN" title="linked_data" href="#dfn-linked_data">Linked Data</a> approaches.
+  Further information on transforming JSON-LD into RDF are detailed in the
+  [<cite><a class="bibref" rel="biblioentry" href="#bib-JSON-LD-API">JSON-LD-API</a></cite>].</p>
+
+<div id="rdf" class="section">
+  <h3><span class="secno">B.1 </span>RDF</h3><p><em>This section is non-normative.</em></p>
+
+  <p>The RDF data model, as outlined in [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>], is an abstract
+  syntax for representing a directed graph of information. JSON-LD is
+  capable of serializing any RDF graph, and performing full RDF to
+  JSON-LD to RDF round-tripping. A complete description of how JSON-LD maps
+  to RDF and algorithms detailing how one can convert from RDF to
+  JSON-LD and from JSON-LD to RDF are included in the JSON-LD API
+  [<cite><a class="bibref" rel="biblioentry" href="#bib-JSON-LD-API">JSON-LD-API</a></cite>] specification.
+  </p>
+
+</div>
+
+<div id="turtle" class="section">
+  <h3><span class="secno">B.2 </span>Turtle</h3>
+
+  <p>The following are examples of converting <a class="tref internalDFN" title="rdf" href="#dfn-rdf">RDF</a>
+  expressed in [<cite><a class="bibref" rel="biblioentry" href="#bib-TURTLE-TR">TURTLE-TR</a></cite>] into JSON-LD.</p>
+
+<div id="prefix-definitions" class="section">
+<h4><span class="secno">B.2.1 </span>Prefix definitions</h4><p><em>This section is non-normative.</em></p>
+<p>The JSON-LD context has direct equivalents for the Turtle
+  <code>@prefix</code> declaration:</p>
+
+<div class="example"><div class="example-title"><span>Example 53</span></div><pre class="example">@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
+
+&lt;http://manu.sporny.org/i/public&gt; a foaf:Person;
+  foaf:name &quot;Manu Sporny&quot;;
+  foaf:homepage &lt;http://manu.sporny.org/&gt; .</pre></div>
+
+<div class="example"><div class="example-title"><span>Example 54</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;
+  },
+  &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
+  &quot;@type&quot;: &quot;foaf:Person&quot;,
+  &quot;foaf:name&quot;: &quot;Manu Sporny&quot;,
+  &quot;foaf:homepage&quot;: { &quot;@id&quot;: &quot;http://manu.sporny.org/&quot; }
+}</pre></div>
+
+<div class="note"><div class="note-title"><span>Note</span></div><div class="">
+<p>JSON-LD has no equivalent for the Turtle <code>@base</code> declaration.
+  Instead, authors may use a prefix definition to resolve
+  <a class="tref internalDFN" title="relative_iri" href="#dfn-relative_iri">relative <abbr title="Internationalized Resource Identifier">IRI</abbr></a>s:</p>
+<div class="example"><div class="example-title"><span>Example 55</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    <span class="diff">&quot;base&quot;: &quot;http://manu.sporny.org/&quot;,</span>
+    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;
+  },
+  &quot;@id&quot;: <span class="diff">&quot;base:i/public&quot;</span>,
+  &quot;@type&quot;: &quot;foaf:Person&quot;,
+  &quot;foaf:name&quot;: &quot;Manu Sporny&quot;,
+  &quot;foaf:homepage&quot;: { &quot;@id&quot;: <span class="diff">&quot;base&quot; </span>}
+}</pre></div>
+</div></div>
+</div>
+
+<div id="embedding-1" class="section">
+<h4><span class="secno">B.2.2 </span>Embedding</h4>
+<p>Both Turtle and JSON-LD allow embedding of objects, although Turtle only allows embedding of objects which
+  use <a class="tref internalDFN" title="unlabeled_node" href="#dfn-unlabeled_node">unlabeled node</a> identifiers.</p>
+</div>
+
+<div class="example"><div class="example-title"><span>Example 56</span></div><pre class="example">@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
+
+&lt;http://manu.sporny.org/i/public&gt;
+  a foaf:Person;
+  foaf:name &quot;Manu Sporny&quot;;
+  foaf:knows [ a foaf:Person; foaf:name &quot;Gregg Kellogg&quot; ] .</pre></div>
+
+<div class="example"><div class="example-title"><span>Example 57</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;
+  },
+  &quot;@id&quot;: &quot;http://manu.sporny.org/i/public&quot;,
+  &quot;@type&quot;: &quot;foaf:Person&quot;,
+  &quot;foaf:name&quot;: &quot;Manu Sporny&quot;,
+  &quot;foaf:knows&quot;:
+  {
+    &quot;@type&quot;: &quot;foaf:Person&quot;,
+    &quot;foaf:name&quot;: &quot;Gregg Kellogg&quot;
+  }
+}</pre></div>
+<div id="lists" class="section">
+<h4><span class="secno">B.2.3 </span>Lists</h4>
+<p>Both JSON-LD and Turtle can represent sequential lists of values.</p>
+
+<div class="example"><div class="example-title"><span>Example 58</span></div><pre class="example">@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
+
+&lt;http://example.org/people#joebob&gt; a foaf:Person;
+  foaf:name &quot;Joe Bob&quot;;
+  foaf:nick ( &quot;joe&quot; &quot;bob&quot; &quot;jaybee&quot; ) .</pre></div>
+
+<div class="example"><div class="example-title"><span>Example 59</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;
+  },
+  &quot;@id&quot;: &quot;http://example.org/people#joebob&quot;,
+  &quot;@type&quot;: &quot;foaf:Person&quot;,
+  &quot;foaf:name&quot;: &quot;Joe Bob&quot;,
+  &quot;foaf:nick&quot;:
+  {
+    &quot;@list&quot;: [ &quot;joe&quot;, &quot;bob&quot;, &quot;jaybee&quot; ]
+  }
+}</pre></div>
+</div>
+
+</div>
+
+<div id="rdfa" class="section">
+<h3><span class="secno">B.3 </span>RDFa</h3>
+
+<p>The following example describes three people with their respective names and
+homepages.</p>
+
+<div class="example"><div class="example-title"><span>Example 60</span></div><pre class="example">&lt;div <span class="diff">prefix=&quot;foaf: http://xmlns.com/foaf/0.1/&quot;</span>&gt;
+   &lt;ul&gt;
+      &lt;li <span class="diff">typeof=&quot;foaf:Person&quot;</span>&gt;
+        &lt;a <span class="diff">rel=&quot;foaf:homepage&quot; href=&quot;http://example.com/bob/&quot; property=&quot;foaf:name&quot; </span>&gt;Bob&lt;/a&gt;
+      &lt;/li&gt;
+      &lt;li <span class="diff">typeof=&quot;foaf:Person&quot;</span>&gt;
+        &lt;a <span class="diff">rel=&quot;foaf:homepage&quot; href=&quot;http://example.com/eve/&quot; property=&quot;foaf:name&quot; </span>&gt;Eve&lt;/a&gt;
+      &lt;/li&gt;
+      &lt;li <span class="diff">typeof=&quot;foaf:Person&quot;</span>&gt;
+        &lt;a <span class="diff">rel=&quot;foaf:homepage&quot; href=&quot;http://example.com/manu/&quot; property=&quot;foaf:name&quot; </span>&gt;Manu&lt;/a&gt;
+      &lt;/li&gt;
+   &lt;/ul&gt;
+&lt;/div&gt;</pre></div>
+
+<p>An example JSON-LD implementation using a single <a class="tref internalDFN" title="context" href="#dfn-context">context</a> is
+described below.</p>
+
+<div class="example"><div class="example-title"><span>Example 61</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;foaf&quot;: &quot;http://xmlns.com/foaf/0.1/&quot;
+  },
+  &quot;@graph&quot;:
+  [
+    {
+      &quot;@type&quot;: &quot;foaf:Person&quot;,
+      &quot;foaf:homepage&quot;: &quot;http://example.com/bob/&quot;,
+      &quot;foaf:name&quot;: &quot;Bob&quot;
+    },
+    {
+      &quot;@type&quot;: &quot;foaf:Person&quot;,
+      &quot;foaf:homepage&quot;: &quot;http://example.com/eve/&quot;,
+      &quot;foaf:name&quot;: &quot;Eve&quot;
+    },
+    {
+      &quot;@type&quot;: &quot;foaf:Person&quot;,
+      &quot;foaf:homepage&quot;: &quot;http://example.com/manu/&quot;,
+      &quot;foaf:name&quot;: &quot;Manu&quot;
+    }
+  ]
+}</pre></div>
+
+</div>
+
+<div id="microformats" class="section">
+<h3><span class="secno">B.4 </span>Microformats</h3>
+
+<p>The following example uses a simple Microformats hCard example to express
+how the Microformat is represented in JSON-LD.</p>
+
+<div class="example"><div class="example-title"><span>Example 62</span></div><pre class="example">&lt;div class=&quot;vcard&quot;&gt;
+ &lt;a class=&quot;url fn&quot; href=&quot;http://tantek.com/&quot;&gt;Tantek Çelik&lt;/a&gt;
+&lt;/div&gt;</pre></div>
+
+<p>The representation of the hCard expresses the Microformat terms in the
+<a class="tref internalDFN" title="context" href="#dfn-context">context</a> and uses them directly for the <code>url</code> and <code>fn</code>
+properties. Also note that the Microformat to JSON-LD processor has
+generated the proper URL type for <code>http://tantek.com/</code>.</p>
+
+<div class="example"><div class="example-title"><span>Example 63</span></div><pre class="example">{
+  &quot;@context&quot;:
+  {
+    &quot;vcard&quot;: &quot;http://microformats.org/profile/hcard#vcard&quot;,
+    &quot;url&quot;:
+    {
+      &quot;@id&quot;: &quot;http://microformats.org/profile/hcard#url&quot;,
+      &quot;@type&quot;: &quot;@id&quot;
+    },
+    &quot;fn&quot;: &quot;http://microformats.org/profile/hcard#fn&quot;
+  },
+  &quot;@type&quot;: &quot;vcard&quot;,
+  &quot;url&quot;: &quot;http://tantek.com/&quot;,
+  &quot;fn&quot;: &quot;Tantek Çelik&quot;
+}</pre></div>
+
+</div>
+
+<div id="microdata" class="section">
+<h3><span class="secno">B.5 </span>Microdata</h3>
+
+<p>The microdata example below expresses book information as a microdata Work
+item.
+</p>
+
+<div class="example"><div class="example-title"><span>Example 64</span></div><pre class="example">&lt;dl itemscope
+    itemtype=&quot;http://purl.org/vocab/frbr/core#Work&quot;
+    itemid=&quot;http://purl.oreilly.com/works/45U8QJGZSQKDH8N&quot;&gt;
+ &lt;dt&gt;Title&lt;/dt&gt;
+ &lt;dd&gt;&lt;cite itemprop=&quot;http://purl.org/dc/terms/title&quot;&gt;Just a Geek&lt;/cite&gt;&lt;/dd&gt;
+ &lt;dt&gt;By&lt;/dt&gt;
+ &lt;dd&gt;&lt;span itemprop=&quot;http://purl.org/dc/terms/creator&quot;&gt;Wil Wheaton&lt;/span&gt;&lt;/dd&gt;
+ &lt;dt&gt;Format&lt;/dt&gt;
+ &lt;dd itemprop=&quot;http://purl.org/vocab/frbr/core#realization&quot;
+     itemscope
+     itemtype=&quot;http://purl.org/vocab/frbr/core#Expression&quot;
+     itemid=&quot;http://purl.oreilly.com/products/9780596007683.BOOK&quot;&gt;
+  &lt;link itemprop=&quot;http://purl.org/dc/terms/type&quot; href=&quot;http://purl.oreilly.com/product-types/BOOK&quot;&gt;
+  Print
+ &lt;/dd&gt;
+ &lt;dd itemprop=&quot;http://purl.org/vocab/frbr/core#realization&quot;
+     itemscope
+     itemtype=&quot;http://purl.org/vocab/frbr/core#Expression&quot;
+     itemid=&quot;http://purl.oreilly.com/products/9780596802189.EBOOK&quot;&gt;
+  &lt;link itemprop=&quot;http://purl.org/dc/terms/type&quot; href=&quot;http://purl.oreilly.com/product-types/EBOOK&quot;&gt;
+  Ebook
+ &lt;/dd&gt;
+&lt;/dl&gt;</pre></div>
+
+<p>Note that the JSON-LD representation of the Microdata information stays
+true to the desires of the Microdata community to avoid contexts and
+instead refer to items by their full <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.</p>
+
+<div class="example"><div class="example-title"><span>Example 65</span></div><pre class="example">[
+  {
+    &quot;@id&quot;: &quot;http://purl.oreilly.com/works/45U8QJGZSQKDH8N&quot;,
+    &quot;@type&quot;: &quot;http://purl.org/vocab/frbr/core#Work&quot;,
+    &quot;http://purl.org/dc/terms/title&quot;: &quot;Just a Geek&quot;,
+    &quot;http://purl.org/dc/terms/creator&quot;: &quot;Whil Wheaton&quot;,
+    &quot;http://purl.org/vocab/frbr/core#realization&quot;:
+    [
+      &quot;http://purl.oreilly.com/products/9780596007683.BOOK&quot;,
+      &quot;http://purl.oreilly.com/products/9780596802189.EBOOK&quot;
+    ]
+  },
+  {
+    &quot;@id&quot;: &quot;http://purl.oreilly.com/products/9780596007683.BOOK&quot;,
+    &quot;@type&quot;: &quot;http://purl.org/vocab/frbr/core#Expression&quot;,
+    &quot;http://purl.org/dc/terms/type&quot;: &quot;http://purl.oreilly.com/product-types/BOOK&quot;
+  },
+  {
+    &quot;@id&quot;: &quot;http://purl.oreilly.com/products/9780596802189.EBOOK&quot;,
+    &quot;@type&quot;: &quot;http://purl.org/vocab/frbr/core#Expression&quot;,
+    &quot;http://purl.org/dc/terms/type&quot;: &quot;http://purl.oreilly.com/product-types/EBOOK&quot;
+  }
+]</pre></div>
+</div>
+</div>
+
+<div class="appendix informative section" id="iana-considerations">
+
+<!-- OddPage -->
+<h2><span class="secno">C. </span>IANA Considerations</h2><p><em>This section is non-normative.</em></p>
+
+<p>This section is included merely for standards community review and will be
+submitted to the Internet Engineering Steering Group if this specification
+becomes a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation.</p>
+
+<h2 id="application-ld-json">application/ld+json</h2>
+<dl>
+  <dt>Type name:</dt>
+  <dd>application</dd>
+  <dt>Subtype name:</dt>
+  <dd>ld+json</dd>
+  <dt>Required parameters:</dt>
+  <dd>None</dd>
+  <dt>Optional parameters:</dt>
+  <dd>
+    <dl>
+      <dt><code>form</code></dt>
+      <dd>Determines the serialization form for the JSON-LD document. The only
+        valid value at the moment is <code>expanded</code>. If no form is
+        specified in an HTTP request header to an HTTP server, the server <em class="rfc2119" title="may">may</em>
+        choose any form. If no form is specified in an HTTP response, the form
+        <em class="rfc2119" title="must not">must not</em> be assumed to take any particular form.</dd>
+    </dl>
+  </dd>
+  <dt>Encoding considerations:</dt>
+  <dd>The same as the <code>application/json</code> MIME media type.</dd>
+  <dt>Security considerations:</dt>
+  <dd>Since JSON-LD is intended to be a pure data exchange format for
+    directed graphs, the serialization <em class="rfc2119" title="should not">should not</em> be passed through a
+    code execution mechanism such as JavaScript's <code>eval()</code>
+    function. It is <em class="rfc2119" title="recommended">recommended</em> that a conforming parser does not attempt to
+    directly evaluate the JSON-LD serialization and instead purely parse the
+    input into a language-native data structure. </dd>
+  <dt>Interoperability considerations:</dt>
+  <dd>Not Applicable</dd>
+  <dt>Published specification:</dt>
+  <dd>The <a href="http://json-ld.org/spec/latest/">JSON-LD</a> specification.</dd>
+  <dt>Applications that use this media type:</dt>
+  <dd>Any programming environment that requires the exchange of
+    directed graphs. Implementations of JSON-LD have been created for
+    JavaScript, Python, Ruby, PHP and C++.
+  </dd>
+  <dt>Additional information:</dt>
+  <dd>
+    <dl>
+      <dt>Magic number(s):</dt>
+      <dd>Not Applicable</dd>
+      <dt>File extension(s):</dt>
+      <dd>.jsonld</dd>
+      <dt>Macintosh file type code(s):</dt>
+      <dd>TEXT</dd>
+    </dl>
+  </dd>
+  <dt>Person &amp; email address to contact for further information:</dt>
+  <dd>Manu Sporny &lt;msporny@digitalbazaar.com&gt;</dd>
+  <dt>Intended usage:</dt>
+  <dd>Common</dd>
+  <dt>Restrictions on usage:</dt>
+  <dd>None</dd>
+  <dt>Author(s):</dt>
+  <dd>Manu Sporny, Gregg Kellogg, Markus Lanthaler, Dave Longley</dd>
+  <dt>Change controller:</dt>
+  <dd><acronym title="World Wide Web Consortium">W3C</acronym></dd>
+</dl>
+
+<p>Fragment identifiers used with <a href="#application-ld-json">application/ld+json</a>
+  resources <em class="rfc2119" title="may">may</em> identify a node in the <a class="tref internalDFN" title="linked_data_graph" href="#dfn-linked_data_graph">linked data graph</a> expressed in
+  the resource. This idiom, which is also used in RDF [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>], gives a
+  simple way to &quot;mint&quot; new, document-local IRIs to label nodes and therefore contributes
+  considerably to the expressive power of JSON-LD.</p>
+
+</div>
+
+<div class="appendix informative section" id="acknowledgements">
+
+<!-- OddPage -->
+<h2><span class="secno">D. </span>Acknowledgements</h2><p><em>This section is non-normative.</em></p>
+
+<p>The editors would like to thank Mark Birbeck, who provided a great deal of
+the initial push behind the JSON-LD work via his work on RDFj,
+Dave Lehn and Mike Johnson who reviewed, provided feedback, and
+performed several implementations of the specification, and Ian Davis, who
+created RDF/JSON. Thanks also to Nathan Rixham, Bradley P. Allen,
+Kingsley Idehen, Glenn McDonald, Alexandre Passant, Danny Ayers, Ted
+Thibodeau Jr., Olivier Grisel, Josh Mandel, Eric Prud'hommeaux,
+David Wood, Guus Schreiber, Pat Hayes, Sandro Hawke, and Richard
+Cyganiak for their input on the specification.
+</p>
+</div>
+
+
+
+<div id="references" class="appendix section">
+<!-- OddPage -->
+<h2><span class="secno">E. </span>References</h2><div id="normative-references" class="section"><h3><span class="secno">E.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-BCP47">[BCP47]</dt><dd>A. Phillips; M. Davis. <a href="http://tools.ietf.org/html/bcp47"><cite>Tags for Identifying Languages</cite></a> September 2009. IETF Best Current Practice. URL: <a href="http://tools.ietf.org/html/bcp47">http://tools.ietf.org/html/bcp47</a> 
+</dd><dt id="bib-JSON-LD-API">[JSON-LD-API]</dt><dd><cite><a href="http://json-ld.org/spec/ED/json-ld-api/20120524/">The JSON-LD API 1.0</a></cite> Manu Sporny, Gregg Kellogg, Dave Longley, Markus Lanthaler, Editors. World Wide Web Consortium (work in progress). 24 May 2012. Editor's Draft. This edition of the JSON-LD Syntax specification is http://json-ld.org/spec/ED/json-ld-api/20120524/. The <a href="http://json-ld.org/spec/latest/json-ld-api/">latest edition of the JSON-LD Syntax</a> is available at http://json-ld.org/spec/latest/json-ld-api/
+</dd><dt id="bib-RDF-CONCEPTS">[RDF-CONCEPTS]</dt><dd><cite><a href="http://www.w3.org/TR/2011/WD-rdf11-concepts-20110830/">RDF 1.1 Concepts and Abstract Syntax</a></cite> Richard Cyganiak, David Wood, Editors. World Wide Web Consortium (work in progress). 30 May 2012. Editor's Draft. This edition of the JSON-LD Syntax specification is http://www.w3.org/TR/2011/WD-rdf11-concepts-20110830/. The <a href="http://www.w3.org/TR/rdf11-concepts/">latest edition of the JSON-LD Syntax</a> is available at http://www.w3.org/TR/rdf11-concepts/
+</dd><dt id="bib-RFC3987">[RFC3987]</dt><dd>M. Dürst; M. Suignard. <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized Resource Identifiers (IRIs).</cite></a> January 2005. Internet RFC 3987. URL: <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a> 
+</dd><dt id="bib-RFC4627">[RFC4627]</dt><dd>D. Crockford. <a href="http://www.ietf.org/rfc/rfc4627.txt"><cite>The application/json Media Type for JavaScript Object Notation (JSON)</cite></a> July 2006. Internet RFC 4627. URL: <a href="http://www.ietf.org/rfc/rfc4627.txt">http://www.ietf.org/rfc/rfc4627.txt</a>
+</dd><dt id="bib-RFC5988">[RFC5988]</dt><dd><cite><a href="http://tools.ietf.org/rfc/rfc5988">Web Linking</a></cite> M. Nottingham. Editor. October 2010. IETF Standard. URL: <a href="http://tools.ietf.org/rfc/rfc5988.txt">http://tools.ietf.org/rfc/rfc5988.txt</a>
+</dd></dl></div><div id="informative-references" class="section"><h3><span class="secno">E.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-RDF-PRIMER">[RDF-PRIMER]</dt><dd>Frank Manola; Eric Miller. <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/"><cite>RDF Primer.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/">http://www.w3.org/TR/2004/REC-rdf-primer-20040210/</a> 
+</dd><dt id="bib-RDFA-CORE">[RDFA-CORE]</dt><dd>Shane McCarron; et al. <a href="http://www.w3.org/TR/2012/REC-rdfa-core-20120508/"><cite>RDFa Core 1.1: Syntax and processing rules for embedding RDF through attributes.</cite></a> 7 June 2012. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2012/REC-rdfa-core-20120607/">http://www.w3.org/TR/2012/REC-rdfa-core-20120607/</a> 
+</dd><dt id="bib-TURTLE-TR">[TURTLE-TR]</dt><dd>Eric Prud'hommeaux, Gavin Carothers. <cite><a href="http://www.w3.org/TR/2011/WD-turtle-20110809/">Turtle: Terse RDF Triple Language.</a></cite> 09 August 2011. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2011/WD-turtle-20110809/">http://www.w3.org/TR/2011/WD-turtle-20110809/</a>
+</dd></dl></div></div></body></html>

--- a/spec/latest/json-ld-api/index.html	Tue Jun 26 21:08:49 2012 -0400
+++ b/spec/latest/json-ld-api/index.html	Tue Jun 26 23:49:05 2012 -0400
@@ -149,8 +149,8 @@
       var respecConfig = {
           doRDFa: "1.1",
           // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
-          specStatus:           "CG-FINAL",
-          publishDate:          "2012-06-26",
+          specStatus:           "FPWD",
+          publishDate:          "2012-07-12",
           copyrightStart:       "2010",
 
           // the specification's short name, as in http://www.w3.org/TR/short-name/
@@ -161,13 +161,13 @@
 
           // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
           // and its maturity status
-          previousPublishDate:  "2012-05-24",
-          previousMaturity:     "CG-DRAFT",
-          previousDiffURI:      "http://json-ld.org/spec/ED/json-ld-api/20120524/",
+          previousPublishDate:  "2012-06-26",
+          previousMaturity:     "CG-FINAL",
+          previousDiffURI:      "http://json-ld.org/spec/ED/json-ld-api/20120626/",
           diffTool:             "http://www.aptest.com/standards/htmldiff/htmldiff.pl",
 
           // if there a publicly available Editor's Draft, this is the link
-          edDraftURI:           "http://json-ld.org/spec/latest/json-ld-api/",
+          edDraftURI:           "http://dvcs.w3.org/hg/json-ld/raw-file/default/spec/latest/json-ld-api/index.html",
 
           // if this is a LCWD, uncomment and set the end of its review period
           // lcEnd: "2009-08-05",
@@ -205,10 +205,10 @@
           ],
 
           // name of the WG
-          wg:           "JSON for Linking Data Community Group",
+          wg:           "RDF Working Group",
 
           // URI of the public WG page
-          wgURI:        "http://www.w3.org/community/json-ld/",
+          wgURI:        "http://www.w3.org/2011/rdf-wg/",
 
           // name (with the @w3c.org) of the public mailing to which comments are due
           wgPublicList: "public-rdf-comments",
@@ -221,7 +221,7 @@
           wgPatentURI:  "http://www.w3.org/2004/01/pp-impl/46168/status",
           maxTocLevel: 4,
           preProcess: [ preProc ],
-          alternateFormats: [ {uri: "diff-20120524.html", label: "diff to previous version"} ],
+          alternateFormats: [ {uri: "diff-20120626.html", label: "diff to previous version"} ],
       };
 
       function _esc(s) {
@@ -264,13 +264,11 @@
 <section id='sotd'>
 <p>This document has been under development for over 18 months in the
 JSON for Linking Data Community Group. The document has recently been
-approved for transfer into the RDF Working Group for
-review with the intent to publish the
-document along the W3C
-Recommendation track. This specification has undergone significant
-development, review, and changes during the course of the last 18
-months and is being published as a Final Community Group Specification so that
-it may gain wider review and feedback.
+transferred to the RDF Working Group for review, improvement, and publication 
+along the Recommendation track. While this is a First Public Working Draft
+publication, the specification has undergone significant development, review, 
+and changes during the course of the last 18 months and is more mature than
+the First Public Working Draft status implies.
 </p>
 <p>
 There are currently

--- a/spec/latest/json-ld-syntax/index.html	Tue Jun 26 21:08:49 2012 -0400
+++ b/spec/latest/json-ld-syntax/index.html	Tue Jun 26 23:49:05 2012 -0400
@@ -147,8 +147,8 @@
       var respecConfig = {
           doRDFa: "1.1",
           // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
-          specStatus:           "CG-FINAL",
-          publishDate:          "2012-06-26",
+          specStatus:           "FPWD",
+          publishDate:          "2012-07-12",
           copyrightStart:       "2010",
 
           // the specification's short name, as in http://www.w3.org/TR/short-name/
@@ -159,13 +159,13 @@
 
           // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
           // and its maturity status
-          previousPublishDate:  "2012-05-22",
-          previousMaturity:     "CG-DRAFT",
-          previousDiffURI:      "http://json-ld.org/spec/ED/json-ld-syntax/20120522/",
+          previousPublishDate:  "2012-06-26",
+          previousMaturity:     "CG-FINAL",
+          previousDiffURI:      "http://json-ld.org/spec/FCGS/json-ld-syntax/20120626/",
           diffTool:             "http://www.aptest.com/standards/htmldiff/htmldiff.pl",
 
           // if there a publicly available Editor's Draft, this is the link
-          edDraftURI:           "http://json-ld.org/spec/latest/json-ld-syntax/",
+          edDraftURI:           "http://dvcs.w3.org/hg/json-ld/raw-file/default/spec/latest/json-ld-syntax/index.html",
 
           // if this is a LCWD, uncomment and set the end of its review period
           // lcEnd: "2009-08-05",
@@ -202,10 +202,10 @@
           ],
 
           // name of the WG
-          wg:           "JSON for Linking Data Community Group",
+          wg:           "RDF Working Group",
 
           // URI of the public WG page
-          wgURI:        "http://www.w3.org/community/json-ld/",
+          wgURI:        "http://www.w3.org/2011/rdf-wg/",
 
           // name (with the @w3c.org) of the public mailing to which comments are due
           wgPublicList: "public-rdf-comments",
@@ -218,7 +218,7 @@
           wgPatentURI:  "http://www.w3.org/2004/01/pp-impl/46168/status",
           maxTocLevel: 4,
           preProcess: [ preProc ],
-          alternateFormats: [ {uri: "diff-20120522.html", label: "diff to previous version"} ],
+          alternateFormats: [ {uri: "diff-20120626.html", label: "diff to previous version"} ],
       };
 
       function _esc(s) {
@@ -258,12 +258,11 @@
 <section id='sotd'>
 <p>This document has been under development for over 18 months in the
 JSON for Linking Data Community Group. The document has recently been
-cleared to be moved into the RDF Working Group for review and
-publication along the
-Recommendation track. This specification has undergone significant
-development, review, and changes during the course of the last 18
-months and is being published as a Final Community Group Specification
-to transition the work into the RDF Working Group.
+transferred to the RDF Working Group for review, improvement, and publication 
+along the Recommendation track. While this is a First Public Working Draft
+publication, the specification has undergone significant development, review, 
+and changes during the course of the last 18 months and is more mature than
+the First Public Working Draft status implies.
 </p>
 <p>
 There are currently
@@ -280,7 +279,6 @@
 next year.
 </p>
 
-
 <p>There are a number of ways that one may participate in the development of
 this specification:</p>

author	Manu Sporny <msporny@digitalbazaar.com>
	Tue, 26 Jun 2012 23:49:05 -0400
changeset 767	b53e28df4bfd
parent 766	c8eb0049885f
child 768	cedc42e247d2

spec/WD/json-ld-api/20120712/diff-20120626.html
spec/WD/json-ld-api/20120712/index.html
spec/WD/json-ld-syntax/20120712/diff-20120626.html
spec/WD/json-ld-syntax/20120712/index.html
spec/latest/json-ld-api/index.html
spec/latest/json-ld-syntax/index.html