In toRDF, use expanded IRI form of property rather than IRI value. This is consistent with properties potentially being BNodes.
--- a/spec/latest/json-ld-api/index.html Fri Nov 09 16:03:12 2012 -0800
+++ b/spec/latest/json-ld-api/index.html Fri Nov 09 17:15:51 2012 -0800
@@ -2123,7 +2123,7 @@
and null values for <tref>active subject</tref> and <tref>active property</tref> and then
proceed to next property.</li>
<li>Otherwise, if <em>property</em> is a <tref>keyword</tref>, skip this step.</li>
- <li>Otherwise, set <tref>active property</tref> to the IRI value of <em>property</em>.</li>
+ <li>Otherwise, set <tref>active property</tref> to the <tref>expanded IRI form</tref> of <em>property</em>.</li>
<li>Process <em>value</em> recursively using this algorithm, passing copies of
<tref>active subject</tref>, <tref>active property</tref> and <tref>graph name</tref>.
</li>
@@ -2257,7 +2257,7 @@
<ol class="algorithm">
<li>If the literal's type is <code>xsd:boolean</code>, the
<em>converted value</em> is <tref>true</tref> if the literal
- matches the value <code>true</code> or <tref>false</tref> if
+ matches the value <code>true</code> or <code>false</code> if
the literal matches the value <code>false</code>.</li>
<li>If the literal's type is <code>xsd:integer</code> or
<code>xsd:double</code>, try to convert the literal to a