prov-n examples for literal
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Fri, 29 Jun 2012 12:43:52 +0100
changeset 3511 7d78c77364db
parent 3510 0cf57c0be6f0
child 3512 c314e89f238d
prov-n examples for literal
model/prov-n.html
--- a/model/prov-n.html	Fri Jun 29 12:38:41 2012 +0100
+++ b/model/prov-n.html	Fri Jun 29 12:43:52 2012 +0100
@@ -2259,34 +2259,37 @@
 
 <p> In particular, a Literal may be an IRI-typed string (with datatype <span class="name">xsd:anyURI</span>);  such IRI has no specific interpretation in the context of PROV.</p>
 
-<!--
-<table border="1" style="margin-left: auto; margin-right: auto;">
-<caption id="permitted-datatypes">Permitted datatypes in literals</caption>
-<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#decimal">xsd:decimal</a></td> <td><a href="http://www.w3.org/TR/xmlschema11-2/#double">xsd:double</a></td>  <td><a href="http://www.w3.org/TR/xmlschema11-2/#dateTime">xsd:dateTime</a></td> </tr>
-<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#integer">xsd:integer</a></td> <td><a href="http://www.w3.org/TR/xmlschema11-2/#float">xsd:float</a></td>  <td><a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-XMLLiteral">rdf:XMLLiteral</a></td></tr>
-<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#nonNegativeInteger">xsd:nonNegativeInteger</a></td> <td><a href="http://www.w3.org/TR/xmlschema11-2/#string">xsd:string</a></td> <td><a href="#prod-QUALIFIED_NAME">prov:QUALIFIED_NAME</a></td> </tr>
-<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#nonPositiveInteger">xsd:nonPositiveInteger</a></td><td><a href="http://www.w3.org/TR/xmlschema11-2/#normalizedString">xsd:normalizedString</a></td> <td></td></tr>
-<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#positiveInteger">xsd:positiveInteger</a></td> <td><a href="http://www.w3.org/TR/xmlschema11-2/#token">xsd:token</a></td> <td></td></tr>
-<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#negativeInteger">xsd:negativeInteger</a></td> <td><a href="http://www.w3.org/TR/xmlschema11-2/#language">xsd:language</a></td> <td></td></tr>
-<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#long">xsd:long</a></td> <td><a href="http://www.w3.org/TR/xmlschema11-2/#Name">xsd:Name</a></td> <td></td></tr>
-<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#int">xsd:int</a></td>  <td><a href="http://www.w3.org/TR/xmlschema11-2/#NCName">xsd:NCName</a></td> <td></td></tr>
-<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#short">xsd:short</a></td> <td><a href="http://www.w3.org/TR/xmlschema11-2/#NMTOKEN">xsd:NMTOKEN</a></td> <td></td></tr>
-<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#byte">xsd:byte</a></td>  <td><a href="http://www.w3.org/TR/xmlschema11-2/#boolean">xsd:boolean</a></td> <td></td></tr>
-<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#unsignedLong">xsd:unsignedLong</a></td> <td><a href="http://www.w3.org/TR/xmlschema11-2/#hexBinary">xsd:hexBinary</a></td> <td></td></tr>
-<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#unsignedInt">xsd:unsignedInt</a></td>  <td><a href="http://www.w3.org/TR/xmlschema11-2/#base64Binary">xsd:base64Binary</a></td><td></td> </tr>
-<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#unsignedShort">xsd:unsignedShort</a></td><td><a href="http://www.w3.org/TR/xmlschema11-2/#anyURI">xsd:anyURI</a></td> <td></td></tr>
-<tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#unsignedByte">xsd:unsignedByte</a></td> <td><a href="http://www.w3.org/TR/xmlschema11-2/#anyURI">xsd:QName</a></td><td></td></tr>
-</table>
--->
+
 <p><b>Note:</b>The productions for <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">prov:QUALIFIED_NAME</a></code> and
 <code class="content"><a class="grammarRef" href="#prod-INT_LITERAL">INT_LITERAL</a></code> are conflicting.  In the context of a 
 <code class="content"><a class="grammarRef" href="#prod-literal">literal</a></code>, a parser should give precedence to the production for
 <code class="content"><a class="grammarRef" href="#prod-INT_LITERAL">INT_LITERAL</a></code>. 
 </p>
 
+<div class="anexample" id="anexample-value">
+<p>
+The following examples respectively are the string "abc", the string (in French) "bonjour", the integer number 1, and the IRI "http://example.org/foo".
+<pre class="codeexample">
+  "abc"
+  "bonjour"@fr
+  "1" %% xsd:integer
+  "http://example.org/foo" %% xsd:anyURI
+</pre>
+<p>The following example shows a value of type <span class="name">prov:QUALIFIED_NAME</span> (see
+<span class="name"><a href="#prod-QUALIFIED_NAME">prov:QUALIFIED_NAME</a></span>).
+The prefix <span class="name">ex</span>  MUST be bound to a <a>namespace</a> declared in a <a>namespace declaration</a>.</p>
+<pre class="codeexample"> 
+  "ex:value" %% prov:QUALIFIED_NAME
+</pre>
+Alternatively, the same value can be expressed using the following convenience notation.
+<pre class="codeexample"> 
+  'ex:value'
+</pre>
+
 </div>
 
 
+
 <section id="expression-types">
 <h4>Reserved Type Values</h4>