--- a/dc-note/Overview.html Wed Oct 31 13:09:26 2012 +0000
+++ b/dc-note/Overview.html Wed Oct 31 13:10:51 2012 +0000
@@ -509,15 +509,17 @@
pre.sh_sourceCode .sh_paren { color: red; }
pre.sh_sourceCode .sh_attribute { color: #006400; }
-</style><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css" charset="utf-8" /></head>
+</style><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css" charset="utf-8" />
+<script src="http://www.w3.org/2007/OWL/toggles.js"></script>
+</head>
<body style="display: inherit; ">
<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">Dublin Core to PROV Mapping</h1><h2 id="w3c-working-draft-19-august-2012">
<acronym title="World Wide Web Consortium">W3C</acronym> Editor's Draft 19 August 2012</h2>
- <dl><dt>This version:</dt><dd><a href="https://dvcs.w3.org/hg/prov/raw-file/37f9692fb7a0/dc-note/Overview.html">https://dvcs.w3.org/hg/prov/raw-file/37f9692fb7a0/dc-note/Overview.html</a></dd>
- <dt>Latest published version:</dt><dd><a href="https://dvcs.w3.org/hg/prov/raw-file/37f9692fb7a0/dc-note/Overview.html">https://dvcs.w3.org/hg/prov/raw-file/37f9692fb7a0/dc-note/Overview.html</a></dd>
- <dt>Latest editor's draft:</dt><dd><a href="https://dvcs.w3.org/hg/prov/raw-file/37f9692fb7a0/dc-note/Overview.html">https://dvcs.w3.org/hg/prov/raw-file/37f9692fb7a0/dc-note/Overview.html</a></dd>
+ <dl><dt>This version:</dt><dd><a href="https://dvcs.w3.org/hg/prov/raw-file/00b0a04d7c34/dc-note/Overview.html">https://dvcs.w3.org/hg/prov/raw-file/00b0a04d7c34/dc-note/Overview.html</a></dd>
+ <dt>Latest published version:</dt><dd><a href="https://dvcs.w3.org/hg/prov/raw-file/00b0a04d7c34/dc-note/Overview.html">https://dvcs.w3.org/hg/prov/raw-file/00b0a04d7c34/dc-note/Overview.html</a></dd>
+ <dt>Latest editor's draft:</dt><dd><a href="https://dvcs.w3.org/hg/prov/raw-file/00b0a04d7c34/dc-note/Overview.html">https://dvcs.w3.org/hg/prov/raw-file/00b0a04d7c34/dc-note/Overview.html</a></dd>
<dt>Editors:</dt>
<dd><a href="http://www.bib.uni-mannheim.de/279.html">Kai Eckert</a>, Manheim University Library, Manheim, Germany</dd>
<dd><a href="http://www.oeg-upm.net/index.php/en/phdstudents/28-dgarijo">Daniel Garijo</a></span>, Universidad Politécnica de Madrid</dd>
@@ -577,7 +579,7 @@
<li class="tocline"><a href="#Mapping" class="tocxref"><span class="secno">2. </span>Mapping Dublin Core to PROV</a></li>
<ul class="toc">
<li class="tocline"><a href="#basic" class="tocxref"><span class="secno">2.1 </span>Basic considerations</a></li>
- <li class="tocline"><a href="#entities_in_dc" class="tocxref"><span class="secno">2.2 </span>What is ex:document1? Entities in Dublin Core</a></li>
+ <li class="tocline"><a href="#entities_in_dc" class="tocxref"><span class="secno">2.2 </span>What is ex:doc1? Entities in Dublin Core</a></li>
<li class="tocline"><a href="#mappings" class="tocxref"><span class="secno">2.3 </span>Direct Mappings</a></li>
<li class="tocline"><a href="#refinements" class="tocxref"><span class="secno">2.4 </span>PROV Refinements</a></li>
<li class="tocline"><a href="#complex_mappings" class="tocxref"><span class="secno">2.5 </span>Complex Mappings</a></li>
@@ -626,10 +628,10 @@
<h2><span class="secno">1. </span>Introduction</h2>
<p>
The Dublin Core Metadata Initiative (DCMI) [<a href="#bib-DCMI">DCMI</a>] provides a core metadata vocabulary,
- commonly refered to as Dublin Core. Originally, it consisted of 15 elements that are still available and called
- the element set. The elements are defined very broadly, in particular they have no
+ commonly referred to as Dublin Core. The original element set consisted of 15 elements that are still available nowadays.
+ These elements are defined very broadly, in particular they have no
range specification, i.e., they can be used with arbitrary values as objects. The elements have been further
- refined and types have been introduced. This more specific vocabulary is called the terms and currently consists
+ refined and new types have been introduced. This more specific vocabulary is called the terms and currently consists
of 55 properties [<a href="#bib-DCTERMS">DCTERMS</a>].
</p>
The Dublin Core elements are considered legacy and the use of the DCMI terms is preferred. They have different namespaces;
@@ -637,8 +639,10 @@
prefix is used for the terms.
Consider the following example for a metadata record:
+</p><p>
+<a href="#example1">Example 1</a>: a simple metadata record:
<pre class="example" id="example1">
- ex:document1 dct:title "A mapping from Dublin Core..." ;
+ ex:doc1 dct:title "A mapping from Dublin Core..." ;
dct:creator ex:kai, ex:daniel, ex:simon, ex:michael ;
dct:created "2012-02-28" ;
dct:publisher ex:w3c ;
@@ -649,18 +653,18 @@
</pre>
<p>
Clearly not all metadata statements deal with provenance.
- <code>dct:title</code>, <code>dct:subject</code> and <code>dct:format</code> are descriptions of the resource <code>ex:document1</code>.
-They do not provide any information how the resource was created or modified in the past.
+ <code>dct:title</code>, <code>dct:subject</code> and <code>dct:format</code> are descriptions of the resource <code>ex:doc1</code>.
+They do not provide any information on how the resource was created or modified in the past.
On the other hand, some statements imply provenance-related information. For example <code>dct:creator</code>
- implies that the document has been created and refers to the author. Similarly, the existence
+ implies that the document has been created and refers an author. Similarly, the existence
of the <code>dct:issued</code> date implies that the document has been published. This information is redundantly
- implied by the dct:publisher statement as well. Finally, <code>dct:replaces</code> relates
- our document to another document <code>ex:doc2</code> which had probably
- some kind of influence on <code>ex:document1</code>.
+ implied by the <code>dct:publisher</code> statement as well. Finally, <code>dct:replaces</code> relates
+ the document to another document <code>ex:doc2</code> which had probably
+ some kind of influence on <code>ex:doc1</code>.
</p><p>
-Following this pattern, we can generally categorize the existing metadata as
-description metadata and provenance metadata. To be more precise, we define provenance
-metadata as metadata providing provenance information according to the definition of
+Following this pattern, the existing metadata can be categorized as
+description metadata and provenance metadata. To be more precise, provenance
+metadata is defined as metadata providing provenance information according to the definition of
the Provenance Working Group [<a href="#bib-PROV-DEF">PROV-DEF</a>] and description metadata as all other metadata.
</p>
<p>
@@ -680,12 +684,12 @@
This is a conservative classification of provenance metadata. It can be argued that other elements contain
provenance information as well, depending on their usage in a concrete implementation or application.
</p><p>
-According to our classification, there are 25 terms out of 55 that can be considered as provenance related.
+According to the proposed classification, there are 25 terms out of 55 that can be considered as provenance related.
The terms can further be categorized according to the question they answer regarding the provenance of a resource:
</p><p>
<b>Who?</b> (contributor, creator, publisher, rightsHolder): Category that includes all properties that have <code>dct:Agent</code> as range,
i.e., a resource that acts or has the power to act. The contributor, creator, and publisher clearly influence
- the resource and therefore are important for its origin. This is not immediately clear for the rightsHolder,
+ the resource and therefore are important for its origin. This is not immediately clear for the <code>dct:rightsHolder</code>,
but as ownership is considered the important provenance information for many resources, like artworks, it is included in this category.
</p><p>
<b>When?</b> (available, created, date, dateAccepted, dateCopyrighted, dateSubmitted, issued, modified, valid):
@@ -693,11 +697,11 @@
being published or not. Depending on the application, however, the publication can be seen as an action that changes
the state of the resource. Two dates can be considered special regarding their relevance for
provenance: available and valid. They are different from the other dates as by definition they can represent a
- date range. Often, the range of availability or validity of a resource is inhererent to the resource and known
- beforehand – consider the validity of a passport or a credit card or the availability of a limited special offer.
+ date range. Often, the range of availability or validity of a resource is inherent to the resource and known
+ beforehand – consider the validity of a passport or the availability of a limited special offer published on the web.
In these cases, there is no action involved that makes the resource invalid or unavailable, it is simply determined
by the validity range. On the other hand, if an action is involved, e.g., a resource is declared invalid because
- a mistake has been found, this is relevant for its provenance.
+ a mistake has been found, then it is relevant for its provenance.
</p><p>
<b>How?</b> (isVersionOf, hasVersion, isFormatOf, hasFormat, references, isReferencedBy, replaces, isReplacedBy, source, rights, license):
Resources are often derived from other resources. In this case, the original resource becomes part of the provenance
@@ -759,19 +763,19 @@
</table>
</div>
<p>
-This leaves one very special term: <i>provenance</i>. It is defined as a "statement of any changes in ownership and
+This leaves one very special term: <i>provenance</i>. This term is defined as a "statement of any changes in ownership and
custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation" [<a href="#bib-DCTERMS">DC-TERMS</a>],
-which refers to the traditional definition of provenance for artworks. Despite being relevant for provenance,
+which corresponds to the traditional definition of provenance for artworks. Despite being relevant for provenance,
this definition may overlap partially with almost half of the DCMI terms, which
specify concrete aspects of provenance of a resource.
</p><p>
In summary, the DCMI terms – and therefore any Dublin Core metadata record – hold a lot of provenance information and
- tell us about a resource, when it was affected in the past, who affected it and how it was affected.
- The description metadata, i.e., the other DCMI terms, tells us what was affected. There is
- no direct information in Dublin Core describing where a resource was affected. Such information is usually only available for the
- publication of a resource, i.e., this action is located at the address of the publisher. Note that spatial is not related
- to this question, as this is a descriptive property that tells us for instance that a book is about Berlin, but not that
- it was created in Berlin – or even that it has ever been or is otherwise related to Berlin. <!--And finally, the question,
+ tell us about a resource, <i>when</i> it was affected in the past, <i>who</i> affected it and <i>how</i> it was affected.
+ The other DCMI terms (description metadata), tell us <i>what</i> was affected. There is
+ no direct information in Dublin Core describing <i>where</i> a resource was affected. Such information is usually only available for the
+ publication of a resource (i.e., an action located at the address of the publisher). Note that spatial is not related
+ to this question, as it is a descriptive property that links a resource to the location referred to in its content, but not to the
+ location where it was created, modified, issued or published. <!--– or even that it has ever been or is otherwise related to Berlin. <!--And finally, the question,
why a resource was affected, lacks – apart from subtle hints from terms like replaces – as usual a satisfying answer. -->
</p>
<h3 id ="namespaces">1.1 Namespaces</h3>
@@ -792,15 +796,15 @@
<div id="Mapping" class="section">
<h2>2. Mapping from Dublin Core to PROV</h2>
<p>A mapping between Dublin Core Terms and PROV-O has many advantages. First, it can provide valuable insights
- into the different characteristics of both data models (in particular it explains PROV from a Dublin Core view point).
+ into the different characteristics of both data models (in particular it explains PROV from a Dublin Core point of view).
Second, such a mapping can be used to extract PROV data from the huge amount of Dublin Core data that is available on
- the Web today. Third, it can translate PROV data to Dublin Core and therefore make it accessible for applications that
- understand Dublin Core. And not least, it can lower the barrier to adopt PROV, as simple Dublin Core statements can be
+ the Web today. Third, it can translate PROV data to Dublin Core and make it accessible for applications that
+ understand Dublin Core. Last, but not least, it can lower the barrier to adopt PROV, as simple Dublin Core statements can be
used as starting point to generate PROV data. </p>
<div id="basic" class="section">
<h3>2.1 Basic considerations </h3>
<p>
-Substantially, a complete mapping from Dublin Core to PROV consists of four parts:
+Substantially, a complete mapping from Dublin Core to PROV consists of three parts:
</p><p>
1) <b>Direct mappings</b> between terms that can be expressed in form of subclass or subproperty relationships in RDFS
– or equivalent relationships in OWL.
@@ -828,13 +832,13 @@
<p>
</div>
<div id="entities_in_dc" class="section">
-<h3><span class="secno">2.2 </span>What is ex:document1? Entities in Dublin Core</h3>
+<h3><span class="secno">2.2 </span>What is ex:doc1? Entities in Dublin Core</h3>
<p>
-Consider the example metadata record shown at the beggining of the document (<a href="#example1">example 1)</a>. As a <code>dc</code>
+Consider the example metadata record shown at the beginning of this document (in <a href="#example1">example 1</a>). As a <code>dc</code>
metadata record describes the resulting document as a whole,
it is not clear how this document relates to the different states that the document had until it reached its final state.
- For example, a document can have assigned a <code>dct:created</code> date and a <code>dct:issued</code> date. According to
- the PROV ontology, the activity of issuing a document involves two different states of the document: the document beffore it was issued
+ For example, a document may have a <code>dct:created</code> date and a <code>dct:issued</code> date. According to
+ the PROV ontology, the activity of issuing a document involves two different states of the document: the document before it was issued
and the issued document. Each of these states correspond to a different specialization of the document, even if the document
has not changed. Generally, there are two possibilities to deal with this issue:</p>
</p><p>
@@ -846,14 +850,15 @@
<div id = "figure_mapping_example" class="figure" style="text-align: center;">
<img src="img/example1.png"></img>
<div style="text-align: center;">
- <a href="#figure_mapping_example">Figure 1</a>. A mapping example creating blank nodes for each state of the resource.
+ <a href="#figure_mapping_example">Figure 1</a>. A mapping example creating blank nodes for each state of the resource. In PROV entities are represented
+with ellipses, activities with rectangles and agents with pentagons.
</div>
</div>
</p><p>
- 2) Use the original document as the instance used as <code>prov:Entity</code>. However, to have an activity that uses
- an entity and generates the same entity is not compliant with the prov constraints [<a href="#bib-Constraints">PROV-CONTRAINTS</a>.]
- Also, if an activity actually generates an entity,
- it is semantically incorrect to have several activities that generate the same entity at different points in time.
+ 2) Use the original resource (<code>ex:doc1</code>) as the instance used and generated as <code>prov:Entity</code>. However, to have an activity that uses
+ an entity and generates the same entity or to have different activities that generate the same entity at different points in time
+ is not compliant with the PROV constraints [<a href="#bib-Constraints">PROV-CONTRAINTS</a>]. <a href="#figure_mapping_example_conflating">Figure 2</a>
+ provides an example that illustrates this approach.
<!--<b>This has to be investigated and discussed further. For references, see PROV-DM Generation, PROV-DM Derivation,
PROV-O Activity</b>.
Removed this from the text above: The implications regarding
@@ -863,11 +868,11 @@
<div id = "figure_mapping_example_conflating" class="figure" style="text-align: center;">
<img src="img/mapping-example - conflating.png"></img>
<div style="text-align: center;">
- <a href="#figure_mapping_example_conflating">Figure 2</a>. A mapping example conflating blank nodes in the same resource. The used and generated resource have the same identifier.
+ <a href="#figure_mapping_example_conflating">Figure 2</a>. A mapping example conflating blank nodes in the same resource. The used and generated resources have the same identifier.
</div>
</div>
</p><p>
-As the first option is the most conservative with respect to the underlying semantics, it has been chosen as guideline in the context-free mapping.
+Since the first option is the most conservative with respect to the underlying semantics, it has been chosen as guideline in the complex mapping.
Blank nodes are used for the mapping, although any naming mechanism could be provided if necessary,
leaving the conflating of nodes to the clean-up phase.
<!-- I comment this because it repeats what it has already been stated
@@ -876,12 +881,12 @@
How do we reduce the number of specializations, e.g., by stating that the specialization that is generated by activity
1 is the same entity that is used by activity 2?
</p><p>
- How do we relate the specializations to <code>ex:document1</code>? We could create two entities based on the actual creation activity:
- <code>ex:document1</code> and a first specialization. We could further declare the last produced specialization as the same entity as <code>ex:document1</code>.
+ How do we relate the specializations to <code>ex:doc1</code>? We could create two entities based on the actual creation activity:
+ <code>ex:doc1</code> and a first specialization. We could further declare the last produced specialization as the same entity as <code>ex:doc1</code>.
Depending on the underlying data, this can be the entity that is identified by the URI of the original document. However,
we have to be careful to avoid cycles in the provenance we produce. For now, this remains undecided.
+-->
</p>
--->
</div>
<div id="mappings" class="section">
<h3><span class="secno">2.3 </span>Direct mappings</h3>
@@ -889,7 +894,7 @@
<!--Direct mappings can particularly be provided for classes and the “shortcuts”, i.e. the direct relationships in PROV between
an entity and an agent or an entity and a date.-->
The direct mappings provide basic interoperability using the integration mechanisms of RDF. By means
- of RDFS-reasoning, any PROV application can at least make some sense from Dublin Core data. The direct mappings also
+ of OWL 2 RL reasoning, any PROV application can at least make some sense from Dublin Core data. The direct mappings also
contribute to the formal definition of the vocabularies by translating them to PROV.</p>
<p>Dublin Core, while less complex from a modeling perspective,
is more specific about the type of the activity taking place. PROV provides general attribution, and
@@ -897,7 +902,7 @@
</p>
<p>
<a href="#list_of_direct_terms">Table 3</a> and <a href="#list_of_direct_mappings2">Table 4</a> provide the detailed mapping plus the rationale for each term.
- For more information see the
+ The rest of the terms can be found in the
<a href="#list_of_excluded_terms">list of terms left out of the mapping</a>.
</p><p>
<div id="list_of_direct_terms" ALIGN="center">
@@ -914,7 +919,7 @@
<td><b>dct:Agent</b></td>
<td>owl:equivalentClass</td>
<td> prov:Agent.</td>
- <td>Both <code>dct:Agent</code> and <code>prov:Agent</code> refer to the same concept: a resource that has the power to act (which then has responsability for an activity)</td>
+ <td>Both <code>dct:Agent</code> and <code>prov:Agent</code> refer to the same concept: a resource that has the power to act (which then has responsibility for an activity).</td>
</tr>
<tr>
<td><b>dct:rightsHolder</b></td>
@@ -933,13 +938,13 @@
<td><b>dct:publisher</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:wasAttributedTo</td>
- <td>A publisher has the attribution of the publishing activity that led to the published resource</td>
+ <td>A publisher has the attribution of the publishing activity that led to the published resource.</td>
</tr>
<tr>
<td><b>dct:contributor</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:wasAttributedTo</td>
- <td>A contributor is involved either in the creation activity or in the updating of the resource. Therefore he is attributed to take
+ <td>A contributor is involved either in the creation activity or in the updating of the resource. Therefore he/she is attributed to take
part in those activities.</td>
</tr>
<tr>
@@ -953,7 +958,7 @@
<td><b>dct:isFormatOf</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:alternateOf</td>
- <td><code>dct:isFormatOf</code> refers to another resource which is the same but in another format. Thus the mapping is straightforward to <code>prov:alternateOf</code></td>
+ <td><code>dct:isFormatOf</code> refers to another resource which is the same but in another format. Thus the mapping is straightforward to <code>prov:alternateOf</code>.</td>
</tr>
<tr>
<td><b>dct:hasFormat</b></td>
@@ -1001,10 +1006,10 @@
<td><b>dct:dateAccepted</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:generatedAtTime</td>
- <td>The rationale is similar to the previous 2 properties: the version of the resource which was accepted could be different from the created or issued one.</td>
+ <td>The rationale is similar to the previous two properties: the version of the resource which was accepted could be different from the created or issued one.</td>
</tr>
<tr>
- <td><b>dct:dateCopyRighted</b></td>
+ <td><b>dct:dateCopyrighted</b></td>
<td>rdfs:subPropertyOf</td>
<td>prov:generatedAtTime</td>
<td>See <code>dct:dateAccepted</code></td>
@@ -1025,13 +1030,13 @@
</table>
</div>
With the direct mapping, a metadata record such as <a href="#example1">example 1</a> will infer that
-the resource was <code>prov:generatedAtTime</code> at two different times. Although this may seem inconsistent, it is supported by PROV and it is due the difference
+the resource was <code>prov:generatedAtTime</code> at two different times. Although this may seem inconsistent, it is supported by PROV and it is due to the difference
between Dublin Core and PROV resources: while the former conflates more than one version or "state" of the resource in a single entity, the latter
-proposes to separate all of them. Thus, the mapping would produce provenance that would comply with the current definition of entity but
-it would not comply with all the PROV consraints [<a href="#bib-Constraints">PROV_CONSTRAINTS]</a>.
+proposes to separate all of them. Thus, the mapping produces provenance that complies with the current definition of entity but
+it does not comply with all the PROV constraints [<a href="#bib-Constraints">PROV_CONSTRAINTS]</a>.
</p>
<p>
-Some properties have been found to be superproperties of certain prov concepts. The summary can be seen below in <a href="#list_of_direct_mappings2">Table 4</a>
+Some properties have been found to be superproperties of certain prov concepts. These can be seen below in <a href="#list_of_direct_mappings2">Table 4</a>:
<!-- SHOULD ADD THIS FOR EACH
<pre rel="prov:wasQuotedFrom" resource="http://dvcs.w3.org/hg/prov/raw-file/tip/examples/eg-24-prov-o-html-examples/rdf/create/rdf/property_qualifiedAttribution.ttl"
-->
@@ -1051,8 +1056,9 @@
<td>prov:hadPrimarySource</td>
<td>rdfs:subPropertyOf</td>
<td><b>dct:source</b></td>
- <td>It is surprising to see that some terms of Dublin Core are more general than the ones defined in PROV. However the definition of <code>prov:hadPrimarySource</code>
- ("something produced by some agent with direct experience and knowledge about the topic") is more restrictive than <code>dct:source</code> ( "A related resource from which the described resource is derived").</td>
+ <td>The definition of <code>prov:hadPrimarySource</code> ("something produced by some agent with direct experience
+ and knowledge about the topic") is more restrictive than <code>dct:source</code> ( "A related resource from which the
+ described resource is derived").</td>
</tr>
<tr>
<td>prov:wasRevisionOf</td>
@@ -1136,25 +1142,28 @@
<div id="complex_mappings" class="section">
<h3><span class="secno">2.5 </span>Complex Mappings</h3>
<p>
+The complex mappings consist on a set of patterns defined to generate qualified PROV statements from Dublin Core statements. This type of qualification may not be
+always needed, and it is the choice of the implementor whether to use them or not depending on the use case. It is also important to note that not all the
+direct mappings have a complex mapping associated, just those which imply a specific activity: creation, publication, etc.
The complex mappings are provided in form of SPARQL CONSTRUCT queries, i.e., queries that describe a
resulting RDF graph based on another RDF graph found in the original data. We divide the queries in different categories:
</p>
<div id="entity_agent_mappings">
<h4><span class="secno">2.5.1 </span>Entity-Agent mappings (Who)</h4>
<p>
-In this category, we have four terms: contributor, creator, publisher, and rightsHolder. The former three
- can be mapped with the same pattern, similar to the one presented in <a href="#figure_mapping_example">Figure 1</a>.
+In this category, we have three terms: <code>dct:contributor</code>, <code>dct:creator</code> and <code>dct:publisher</code>.
+The three of them can be mapped with the same pattern, similar to the one presented in <a href="#figure_mapping_example">Figure 1</a>.
The only changes required are the roles and activities involved for each term.
<p>
- In the text below, variables ?document and ?agent are set to different matching values depending
+ In the text below, variables <code>?document</code> and <code>?agent</code> are set to different matching values depending
on the data found in the triple store. The graph in the CONSTRUCT part can be seen as a template
where the variables are placeholders that are filled with the values found in the data.
The mapping corresponds to the graph in <a href="#figure_mapping_example">Figure 1</a> (with small changes
for creator and rightsHolder). With this mapping,
the difference in the complexity becomes obvious. Many blank nodes are created, so a subsequent clean-up phase that relates them and provides stable
URIs for the entities is required. Depending on the implementation, URIs can also be coined here for every specialization.
- Sometimes, URIs for the specializations are also available and simply not exposed to the Dublin Core record.
+ <!--Sometimes URIs for the specializations are also available and simply not exposed to the Dublin Core record.-->
The implementation proposed in this document is an example that works conservatively. The assumption is that no further
information about the identity of the specializations is available.
@@ -1170,12 +1179,12 @@
?agent a prov:Agent .
- _:activity a prov:Activity, dcprov:CreationActivity ;
+ _:activity a prov:Activity, prov:CreationActivity ;
prov:wasAssociatedWith ?agent;
prov:qualifiedAssociation [
a prov:Association;
prov:agent ?agent;
- prov:hadRole dcprov:CreatorRole .
+ prov:hadRole prov:CreatorRole .
].
_:resulting_entity a prov:Entity ;
@@ -1264,115 +1273,118 @@
<div id="entity_date_mappings">
<h4><span class="secno">2.5.2 </span>Entity-Date mappings (When)</h4>
<p>
-The dates often correspond with a who-property, e.g., creator and created or publisher and issued.
- Therefore, they lead to similar statements, only providing a date instead of an agent associated with the activity.
+Dates often correspond with a who-property, e.g., creator and created or publisher and issued.
+ Therefore, they lead to similar complex patterns (providing a date instead of an agent associated with the corresponding activity).
+ When using Dublin Core terms, it is usual to see that a resource is annotated with several <code>dct</code> assertions like creator, publisher,
+ issued, date, etc., but in this phase of the mapping each term is treated independently.
+
</p>
-<p>
-When using Dublin Core terms, it is usual to see that a resource is annotated with several dc assertions like creator, publisher,
- issued, date, etc. In this phase of the mapping each term is trated independently.
-</p>
+
<h5 id="term_created"><span class="secno">2.5.2.1 </span>dct:created</h5>
-</p><p><pre class="code">
+</p>
+<pre class="code">
CONSTRUCT{
- ?document a prov:Entity .
+ ?document a prov:Entity .
- _:activity a prov:Activity, prov:CreationActivity ;
+ _:activity a prov:Activity, prov:CreationActivity ;
# The “output”
- _:created_entity a prov:Entity ;
- prov:specializationOf ?document ;
- prov:wasGeneratedBy _:activity ;
- prov:wasGeneratedAtTime ?date;
- prov:qualifiedGeneration [
- a prov:Generation ;
- prov:atTime ?date ;
- prov:activity _:activity .
- ] .
+ _:created_entity a prov:Entity ;
+ prov:specializationOf ?document ;
+ prov:wasGeneratedBy _:activity ;
+ prov:wasGeneratedAtTime ?date;
+ prov:qualifiedGeneration [
+ a prov:Generation ;
+ prov:atTime ?date ;
+ prov:activity _:activity .
+ ] .
} WHERE {
?document dct:created ?date.
}
</pre>
+
<h5 id="term_issued"><span class="secno">2.5.2.2 </span>dct:issued</h5>
-<p><pre class="code">
+<p>
+<pre class="code">
CONSTRUCT{
- ?document a prov:Entity .
+ ?document a prov:Entity .
- _:activity a prov:Activity, prov:PublicationActivity ;
- prov:used _:used_entity .
+ _:activity a prov:Activity, prov:PublicationActivity ;
+ prov:used _:used_entity .
# The “input”
- _:used_entity a prov:Entity .
- prov:specializationOf ?document .
+ _:used_entity a prov:Entity .
+ prov:specializationOf ?document .
# The “output”
- _:iss_entity a prov:Entity ;
- prov:specializationOf ?document ;
- prov:wasGeneratedBy _:activity ;
- prov:wasGeneratedAtTime ?date;
- prov:wasDerivedFrom _:used_entity ;
- prov:qualifiedGeneration [
- a prov:Generation ;
- prov:atTime ?date ;
- prov:activity _:activity .
- ] .
+ _:iss_entity a prov:Entity ;
+ prov:specializationOf ?document ;
+ prov:wasGeneratedBy _:activity ;
+ prov:wasGeneratedAtTime ?date;
+ prov:wasDerivedFrom _:used_entity ;
+ prov:qualifiedGeneration [
+ a prov:Generation ;
+ prov:atTime ?date ;
+ prov:activity _:activity .
+ ] .
} WHERE {
?document dct:issued ?date.
}
</pre>
</p>
+
<h5 id="term_modified"><span class="secno">2.5.2.3 </span>dct:modified</h5>
-<p>
-As seen with the previous terms, most entity/date properties will have a similar structure.
-</p><p><pre class="code">
+<p><pre class="code">
CONSTRUCT{
- ?document a prov:Entity .
+ ?document a prov:Entity .
- _:activity a prov:Activity, prov:ModificationActivity ;
- prov:used _:used_entity .
+ _:activity a prov:Activity, prov:ModificationActivity ;
+ prov:used _:used_entity .
# The “input”
- _:used_entity a prov:Entity .
- prov:specializationOf ?document .
+ _:used_entity a prov:Entity .
+ prov:specializationOf ?document .
# The “output”
- _:modified_entity a prov:Entity ;
- prov:specializationOf ?document ;
- prov:wasGeneratedBy _:activity ;
- prov:wasGeneratedAtTime ?date;
- prov:wasDerivedFrom _:used_entity ;
- prov:qualifiedGeneration [
- a prov:Generation ;
- prov:atTime ?date ;
- prov:activity _:activity .
- ] .
+ _:modified_entity a prov:Entity ;
+ prov:specializationOf ?document ;
+ prov:wasGeneratedBy _:activity ;
+ prov:wasGeneratedAtTime ?date;
+ prov:wasDerivedFrom _:used_entity ;
+ prov:qualifiedGeneration [
+ a prov:Generation ;
+ prov:atTime ?date ;
+ prov:activity _:activity .
+ ] .
} WHERE {
?document dct:modified ?date.
}
</pre>
-</p><p>
+</p>
+
<h5 id="term_dateAccepted"><span class="secno">2.5.2.4 </span>dct:dateAccepted</h5>
-</p><p><pre class="code">
+<p><pre class="code">
CONSTRUCT{
- ?document a prov:Entity .
+ ?document a prov:Entity .
- _:activity a prov:Activity, prov:AcceptanceActivity ;
- prov:used _:used_entity .
+ _:activity a prov:Activity, prov:AcceptanceActivity ;
+ prov:used _:used_entity .
# The “input”
- _:used_entity a prov:Entity .
- prov:specializationOf ?document .
+ _:used_entity a prov:Entity .
+ prov:specializationOf ?document .
# The “output”
- _:accepted_entity a prov:Entity ;
- prov:specializationOf ?document ;
- prov:wasGeneratedBy _:activity ;
- prov:wasGeneratedAtTime ?date;
- prov:wasDerivedFrom _:used_entity ;
- prov:qualifiedGeneration [
- a prov:Generation ;
- prov:atTime ?date ;
- prov:activity _:activity .
- ] .
+ _:accepted_entity a prov:Entity ;
+ prov:specializationOf ?document ;
+ prov:wasGeneratedBy _:activity ;
+ prov:wasGeneratedAtTime ?date;
+ prov:wasDerivedFrom _:used_entity ;
+ prov:qualifiedGeneration [
+ a prov:Generation ;
+ prov:atTime ?date ;
+ prov:activity _:activity .
+ ] .
} WHERE {
?document dct:dateAccepted ?date.
}
@@ -1381,26 +1393,26 @@
<h5 id="term_dateCopyRighted"><span class="secno">2.5.2.5 </span>dct:dateCopyrighted</h5>
<p><pre class="code">
CONSTRUCT{
- ?document a prov:Entity .
+ ?document a prov:Entity .
- _:activity a prov:Activity, prov:CopyrightingActivity ;
- prov:used _:used_entity .
+ _:activity a prov:Activity, prov:CopyrightingActivity ;
+ prov:used _:used_entity .
# The “input”
- _:used_entity a prov:Entity .
- prov:specializationOf ?document .
+ _:used_entity a prov:Entity .
+ prov:specializationOf ?document .
# The “output”
- _:copyrighted_entity a prov:Entity ;
- prov:specializationOf ?document ;
- prov:wasGeneratedBy _:activity ;
- prov:wasGeneratedAtTime ?date;
- prov:wasDerivedFrom _:used_entity ;
- prov:qualifiedGeneration [
- a prov:Generation ;
- prov:atTime ?date ;
- prov:activity _:activity .
- ] .
+ _:copyrighted_entity a prov:Entity ;
+ prov:specializationOf ?document ;
+ prov:wasGeneratedBy _:activity ;
+ prov:wasGeneratedAtTime ?date;
+ prov:wasDerivedFrom _:used_entity ;
+ prov:qualifiedGeneration [
+ a prov:Generation ;
+ prov:atTime ?date ;
+ prov:activity _:activity .
+ ] .
} WHERE {
?document dct:dateCopyrighted ?date.
}
@@ -1408,158 +1420,69 @@
<h5 id="term_dateSubmitted"><span class="secno">2.5.2.6 </span>dct:dateSubmitted</h5>
<p><pre class="code">
CONSTRUCT{
- ?document a prov:Entity .
+ ?document a prov:Entity .
- _:activity a prov:Activity, prov:SubmissionActivity ;
- prov:used _:used_entity .
+ _:activity a prov:Activity, prov:SubmissionActivity ;
+ prov:used _:used_entity .
# The “input”
- _:used_entity a prov:Entity .
- prov:specializationOf ?document .
+ _:used_entity a prov:Entity .
+ prov:specializationOf ?document .
# The “output”
- _:submitted_entity a prov:Entity ;
- prov:specializationOf ?document ;
- prov:wasGeneratedBy _:activity ;
- prov:wasGeneratedAtTime ?date;
- prov:wasDerivedFrom _:used_entity ;
- prov:qualifiedGeneration [
- a prov:Generation ;
- prov:atTime ?date ;
- prov:activity _:activity .
- ] .
+ _:submitted_entity a prov:Entity ;
+ prov:specializationOf ?document ;
+ prov:wasGeneratedBy _:activity ;
+ prov:wasGeneratedAtTime ?date;
+ prov:wasDerivedFrom _:used_entity ;
+ prov:qualifiedGeneration [
+ a prov:Generation ;
+ prov:atTime ?date ;
+ prov:activity _:activity .
+ ] .
} WHERE {
?document dct:dateSubmitted ?date.
}
</pre>
</p>
</div>
-<!--
-<div id="entity_entity_mappings">
-<h4><span class="secno">2.5.3 </span>Entity-Entity mappings (How)</h4>
-<p>
-Most Dublin Core terms in this category are related to the <code>prov:wasDerivedFrom</code> property.
- They can be mapped directly, but also a complex mapping can be provided. In these cases, a specialty of SPARQL
- CONSTRUCT queries can be used to deal with the inverse properties in Dublin Core.
-</p>
-<h5 id="term_has_Version"><span class="secno">2.5.3.1 </span>dct:isVersionOf / dct:hasVersion</h5>
-<p>
-I would say that <code>prov:wasDerivedFrom</code>><code>dct:isVersionOf</code>><code>prov:wasRevisionOf</code>. Thus:
-</p><p><pre class="code">
- CONSTRUCT {
- ?document1 a prov:Entity ;
- prov:wasDerivedFrom ?document2.
- ?document2 a prov:Entity .
- } WHERE {
- OPTIONAL { ?document1 dct:isVersionOf ?document2 . }
- OPTIONAL { ?document2 dct:hasVersion ?document1 .}
- }
-</pre>
-</p><p>
- The OPTIONAL keyword means that the included statement does not need to exist.
- Triples in the resulting graph with variables that have no binding simply are omitted.
- In this case this leads to the correct PROV statement, if either or both source statements are present.
- From the entity/entity relations, <b>an activity can also be inferred (e.g., the activity that led to the creation of the new version)
- . We omit it here for brevity.</b>
- </p>
- <!--<p>
- In essence, these examples sketch the first part of the mapping. As everything is provided as
- RDF statements or SPARQL CONSTRUCT queries, this mapping can simply applied to arbitrary RDF data by
- adding the statements and the resulting graphs from the queries to the data.
- </p> this should be commented
- <p>
-<h5 id="term_has_Format"><span class="secno">2.5.3.2 </span>dct:isFormatOf / dct:hasFormat</h5>
-</p><p>
-isFormatOf is defined as “A related resource that is substantially the same as the described resource, but in another format”. This
- would map to <code>prov:alternateOf</code>. We don’t know which entities are both of them specializing, but we know that one is an alternate of the other.
-</p><p> <pre class="code">
- CONSTRUCT {
- ?document1 a prov:Entity ;
- prov:alternateOf ?document2.
- ?document2 a prov:Entity .
- } WHERE {
- OPTIONAL { ?document1 dct:isFormatof ?document2 . }
- OPTIONAL { ?document2 dct:hasFormat ?document1 .}
- }
-</pre></p><p>
-
-<!--
-dct:isReferencedBy / dct:references
-</p><p>
-IsReferencedBy: A related resource that references, cites, or otherwise points to the described resource.
-</p><p><pre class="code">
-
- CONSTRUCT {
- ?document1 a prov:Entity ;
- ?document2 a prov:Entity .
- prov:wasDerivedFrom ?document2.
- } WHERE {
- OPTIONAL { ?document1 dct:isReferencedBy ?document2 . }
- OPTIONAL { ?document2 dct:references ?document1 .}
- }
-
-</pre></p><p>
-</p>
-<h5 id="term_replaces"><span class="secno">2.5.3.3 </span>dct:replaces / dct:isReplacedBy</h5>
-<p><pre class="code">
- CONSTRUCT {
- ?document1 a prov:Entity ;
- prov:wasInfluencedBy ?document2.
- ?document2 a prov:Entity .
- } WHERE {
- OPTIONAL { ?document1 dct:replaces ?document2 . }
- OPTIONAL { ?document2 dct:isReplacedBy ?document1 .}
- }
-</pre></p><p>
-<h5 id="term_source"><span class="secno">2.5.3.4 </span>dct:source</h5>
-</p><p><pre class="code">
- CONSTRUCT{
- ?document1 a prov:Entity ;
- prov:wasDerivedFrom :subj2 .
- ?document2 a prov:Entity .
- } WHERE {
- ?document1 dct:source ?document2.
- }
-</pre>
-</p>
-</div>
--->
+
</div>
<div id="cleanup" class="section">
<h3><span class="secno">2.5.3 </span>Cleanup</h3>
<p>
-The clean-up phase depends on how implementors interpret the described resources. The approach presented in this document
+The clean-up phase depends on how implementers interpret the described resources. The approach presented in this document
is conservative and it leads to the proliferation of blank nodes. Blank nodes could be renamed to specific identifiers
- by the implementor, in order to avoid obtaining additional blank nodes when reapplying the construct queries presented
+ by the implementer, in order to avoid obtaining additional blank nodes when reapplying the construct queries presented
in the previous section.</p>
<p> Providing a set of rules to conflate the blank nodes is not in the scope of this document. However, the group has
- created a list of suggestions for implementors with proposals on how this could be achieved:</p>
- <p>1)<b> Conflate properties referring to the same state of the resource</b>: In Dublin Core certain properties complement each other (e.g.,
- creator and created, publisher and issued, modified and contributor, etc.). By combining some of the queries, we could group
- some of the records and create more complete PROV assertions.</p>
- <p>The example below shows how a modification to the previous pattern would conflate the blank nodes for <code>dct:creator</code> and <code>dct:created</code> properties:
+ created a list of suggestions for implementers with proposals on how this could be achieved:</p>
+ <p>1) <b>Conflate properties referring to the same state of the resource</b>: In Dublin Core certain properties complement each other (e.g.,
+ creator and created, publisher and issued, modified and contributor, etc.). By combining some of the queries, some of the records
+ could be grouped creating more complete PROV assertions.</p>
+ <p>The example below shows how to conflate the blank nodes for <code>dct:creator</code> and <code>dct:created</code> properties:
<pre class="code">
CONSTRUCT{
- ?document a prov:Entity .
+ ?document a prov:Entity .
- _:activity a prov:Activity, prov:CreationActivity.
- prov:wasAssociatedWith ?agent
- prov:qualifiedAssociation [
- a prov:Association;
- prov:agent ?agent;
- prov:hadRole prov:CreatorRole .
- ]
+ _:activity a prov:Activity, prov:CreationActivity.
+ prov:wasAssociatedWith ?agent
+ prov:qualifiedAssociation [
+ a prov:Association;
+ prov:agent ?agent;
+ prov:hadRole prov:CreatorRole .
+ ] .
# The “output”
- _:created_entity a prov:Entity ;
- prov:specializationOf ?document ;
- prov:wasGeneratedBy _:activity ;
- prov:wasGeneratedAtTime ?date;
- prov:qualifiedGeneration [
- a prov:Generation ;
- prov:atTime ?date ;
- prov:activity _:activity .
- ] .
+ _:created_entity a prov:Entity ;
+ prov:specializationOf ?document ;
+ prov:wasGeneratedBy _:activity ;
+ prov:wasGeneratedAtTime ?date;
+ prov:qualifiedGeneration [
+ a prov:Generation ;
+ prov:atTime ?date ;
+ prov:activity _:activity .
+ ] .
} WHERE {
?document dct:creator ?agent;
dct:created ?date.
@@ -1570,7 +1493,7 @@
<div id = "figure_cleanup1" class="figure" style="text-align: center;">
<img src="img/cleanup1.png"></img>
<div style="text-align: center;">
- <a href="#figure_mapping_example">Figure 3</a>. Gathering complementing properties to conflate blank nodes.
+ <a href="#figure_cleanup1">Figure 3</a>. Gathering complementing properties to conflate blank nodes.
</div>
</div>
@@ -1578,18 +1501,18 @@
<p>2) Another solution is to <b>sort all the activities according to their date</b>, if known, and conflate the blank
nodes result of one activity and the input of the subsequent activity, in case they are both specializations of the same entity.
<a href="#figure_cleanup2">Figure 4</a> shows a graphical example with two different activities (creation and publication) that happened at different
-points in time. Instead of creating different blank nodes for the respective usage and generation, both activities shared the same
-blank node (_:created_entity).
+points in time. Instead of creating different blank nodes for the respective usage and generation, both activities share the same
+blank node (<code>_:created_entity</code>).
<div id = "figure_cleanup2" class="figure" style="text-align: center;">
<img src="img/cleanup2.png"></img>
<div style="text-align: center;">
- <a href="#figure_mapping_example">Figure 4</a>. Sorting the activities by date to conflate blank nodes.
+ <a href="#figure_cleanup2">Figure 4</a>. Sorting the activities by date to conflate blank nodes.
</div>
</div>
</p>
-<p>3) Finally, another solution is to <b>ignore all the specializations of ex:document1 and use the resource itself</b>. This solution
+<p>3) Finally, another solution is to <b>ignore all the specializations of <code>ex:doc1</code> and use the resource itself</b>. This solution
would avoid the majority of the blank nodes, linking all the activities with the resource. However, the results would be confusing in
-case there are several dublin core statements describing the same resource (like publisher and creator), since most of the
+case there are several Dublin Core statements describing the same resource (like <code>dct:publisher</code> and <code>creator</code>), since most of the
activities would use and generate the same resource at different times (all the provenance of the different versions of the resource
would be conflated in the same entity). A graphical representation of an example can be seen in <a href="#figure_mapping_example_conflating">Figure 2</a>.
</p>
@@ -1613,15 +1536,15 @@
</tr><tr>
<td><b id="term_accrualMethod">dct:accrualMethod</b></td>
<td>Descriptive Metadata</td>
- <td>Method by which items are added to a collection. It doesn't describe the action itslef, so we decided to leave this term out of the mpping</td>
+ <td>Method by which items are added to a collection. It doesn't describe the action itself, so it is out of the scope of the mapping</td>
</tr><tr>
<td><b id="term_accrualPeriodicity">dct:accrualPeriodicity</b></td>
<td>Descriptive metadata</td>
- <td>Frequency of the items added to a collection.</td>
+ <td>Frequency of the addition of items to a collection.</td>
</tr><tr>
<td><b id="term_accrualPolicy">dct:accrualPolicy</b></td>
<td>Descriptive metadata</td>
- <td>Policy associated with the insertion of items to a collection. We could use it to enrich the qualified
+ <td>Policy associated with the insertion of items to a collection. It could be used to enrich the qualified
involvement, but there is no direct mapping of this relationship.</td>
</tr><tr>
<td><b id="term_alternative">dct:alternative</b></td>
@@ -1654,7 +1577,7 @@
</tr><tr>
<td><b id="term_format">dct:format</b></td>
<td>Descriptive metadata</td>
- <td>Format of the resource. Descriptive metadata.</td>
+ <td>Format of the resource. </td>
</tr><tr>
<td><b id="term_identifier">dct:identifier</b></td>
<td>Descriptive metadata</td>
@@ -1666,7 +1589,7 @@
</tr><tr>
<td><b id="term_isPartOf">dct:isPartOf</b></td>
<td>Descriptive metadata</td>
- <td>Inverse of hasPart.</td>
+ <td>Inverse of <code>dct:hasPart</code>.</td>
</tr><tr>
<td><b id="term_isRequiredBy">dct:isRequiredBy</b></td>
<td>Descriptive metadata</td>
@@ -1688,16 +1611,16 @@
</tr><tr>
<td><b id="term_requires">dct:requires</b></td>
<td>Descriptive metadata</td>
- <td>Inverse property of isRequiredBy (see isRequiredBy).</td>
+ <td>Inverse property of <code>dct:isRequiredBy</code> (see <code>dct:isRequiredBy</code>).</td>
</tr><tr>
<td><b id="term_hasPart">dct:hasPart</b></td>
<td>Descriptive metadata</td>
- <td>A resource that is included in the current resource. Entity composition is out of the scope of DM, so
- we leave it out of the mapping list as well</td>
+ <td>A resource that is included in the current resource. Since entity composition is out of the scope of PROV,
+ this property has been excluded from the mapping</td>
</tr><tr>
<td><b id="term_spatial">dct:spatial</b></td>
<td>Descriptive metadata</td>
- <td>Spatial characteristics of the content of the resource resource (e.g., the book is about Spain). Thus it can't be mapped to <code>prov:hadLocation</code>.</td>
+ <td>Spatial characteristics of the content of the resource (e.g., the book is about Spain). Thus it can't be mapped to <code>prov:hadLocation</code>.</td>
</tr><tr>
<td><b id="term_subject">dct:subject</b></td>
<td>Descriptive metadata</td>
@@ -1721,27 +1644,27 @@
</tr><tr>
<td><b id="term_bibliographicCitation">dct:bibliographicCitation</b></td>
<td>Descriptive metadata</td>
- <td>Property that relates the Literal representing the bibliographic citation of the resource to the
+ <td>Property that relates the literal representing the bibliographic citation of the resource to the
actual resource (e.g., <code>:el_Quijote dct:bibliographicCitation "Miguel de Cervantes Saavedra: El Quijote, España"</code>).</td>
</tr><tr>
<td id="term_references"><b>dct:references</b></td>
<td> Provenance: How </td>
<td>This term could be used to refer to sources that have been used to create the document, but it could
- be also used to cite the sources that are not relevant for the current work. Since we could not reach consensus on how
- to map it to prov, we have left it out of the mapping</td>
+ be also used to cite the sources that are not relevant for the current work. For this reason it has been dropped
+ from the mapping.</td>
</tr><tr>
<td id="term_isReferencedBy"><b>dct:isRefrencedBy</b></td>
<td> Provenance: How </td>
- <td>Inverse to dct:references.</td>
+ <td>Inverse to <code>dct:references</code>.</td>
</tr><tr>
<td><b id="term_accessRights">dct:accessRights</b></td>
<td>Provenance: How</td>
- <td>Who can access the resource (security status). Since the privileges of the resource are part of the
- description of the resource, it’s not included in the list.</td>
+ <td>Agents who can access the resource (security status). Since the privileges of the resource are part of the
+ description of the resource, the property has been excluded from the mapping.</td>
</tr><tr>
<td><b id="term_license">dct:license</b></td>
<td>Provenance: How</td>
- <td>License of the resource. It has been left out of the list because there is no term in PROV-O to map to.</td>
+ <td>License of the resource. It has been left out of the mapping because there is no term in PROV-O to represent this information.</td>
</tr><tr>
<td><b id="term_rights">dct:rights</b></td>
<td>Provenance: How</td>
@@ -1749,31 +1672,31 @@
</tr><tr>
<td><b id="term_date">dct:date</b></td>
<td>Provenance: When</td>
- <td>Date is a very general property. It is the superproperty which all the other specialize. We have decided to leave it with no mapping</td>
+ <td>Date is a very general property. It is the superproperty which all the other specialize, but there is no equivalent concept in PROV. It has been excluded from the mapping</td>
</tr><tr>
<td><b id="term_available">dct:available</b></td>
<td>Provenance: When</td>
- <td>Property that states when a resource is available. We couldn't find consensus on how to map this property, so it was dropped.</td>
+ <td>Property that states when a resource is available. The group could not reach consensus on how to map this property, so it was finally dropped from the mapping.</td>
</tr><tr>
<td><b id="term_valid">dct:valid</b></td>
<td>Provenance: When</td>
- <td>Property that states when a resource is valid. We have the notion of invalidation in PROV-O, but not the notion of validation. Thus we leave this property out of the mapping</td>
+ <td>Property that states when a resource is valid. The notion of invalidation is defined in PROV-DM, but not the notion of validation. Thus this property is left out of the mapping.</td>
</tr><tr>
<td><b id="term_relation">dct:relation</b></td>
<td>Provenance </td>
<td>A related resource. This relationship is very broad and could relate either provenance resources or not.
- It could be seen as a superproperty of wasDerivedFrom, wasInfluencedBy, alternateOf, specializationOf, etc. Thus there is no direct mapping.<td>
+ Therefore it could be seen as a superproperty of <code>prov:wasDerivedFrom</code>, <code>prov:wasInfluencedBy</code>, <code>prov:alternateOf</code>, <code>prov:specializationOf</code>, etc. Thus there is no direct mapping.<td>
</tr>
</tbody></table>
</p>
<div id="prov_to_dc" class="section">
<h2><span class="secno">3. </span>Mapping from PROV to DC</h2>
<p>
-The mapping from PROV to DC is not part of this note.
+The mapping from PROV to Dublin Core is not part of this note.
It can be questioned, if a mapping without additional information would provide meaningful data.
- If refinements are used, the mapping would be straight forward and more or less the inverse of the
- mapping patterns that we used. However, without such refinements, almost no DC statements can be inferred,
- besides some unqualified dates. Dublin Core includes provenance information, but the focus lies on
+ If refinements are used, the mapping would be straight forward using the inverse of the
+ mapping patterns used in this document. However, without such refinements, few Dublin Core statements can be inferred,
+ apart from some unqualified dates. Dublin Core includes provenance information, but the focus lies on
the description of the resources. Pure PROV data models a provenance chain, but it contains almost
no information about the resulting resource itself. </p>
</div>
@@ -1783,7 +1706,7 @@
<!-- OddPage -->
<h2><span class="secno">A. </span>Acknowledgements</h2>
<p>
- We would like to thank Antoine Isaac, Timothy Lebo, Simon Miles, Satya Sahoo and Ivan Herman for their feedback.
+ We would like to thank Antoine Isaac, Ivan Herman, Timothy Lebo, Simon Miles and Satya Sahoo for their comments and feedback, and Idafen Santana Pérez for his help with the HTML generation.
</p>
</div>
--- a/dc-note/files/construct queries/entity-agent/creator.ttl Wed Oct 31 13:09:26 2012 +0000
+++ b/dc-note/files/construct queries/entity-agent/creator.ttl Wed Oct 31 13:10:51 2012 +0000
@@ -10,12 +10,12 @@
?agent a prov:Agent .
- _:activity a prov:Activity, dcprov:CreationActivity ;
+ _:activity a prov:Activity, prov:CreationActivity ;
prov:wasAssociatedWith ?agent;
prov:qualifiedAssociation [
a prov:Association;
prov:agent ?agent;
- prov:hadRole dcprov:CreatorRole .
+ prov:hadRole prov:CreatorRole .
].
_:resulting_entity a prov:Entity ;
--- a/dc-note/img-files/cleanup1.graphml Wed Oct 31 13:09:26 2012 +0000
+++ b/dc-note/img-files/cleanup1.graphml Wed Oct 31 13:10:51 2012 +0000
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<graphml xmlns="http://graphml.graphdrawing.org/xmlns" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:y="http://www.yworks.com/xml/graphml" xmlns:yed="http://www.yworks.com/xml/yed/3" xsi:schemaLocation="http://graphml.graphdrawing.org/xmlns http://www.yworks.com/xml/schema/graphml/1.1/ygraphml.xsd">
- <!--Created by yFiles for Java 2.8-->
+ <!--Created by yFiles for Java 2.9-->
<key for="graphml" id="d0" yfiles.type="resources"/>
<key for="port" id="d1" yfiles.type="portgraphics"/>
<key for="port" id="d2" yfiles.type="portgeometry"/>
@@ -59,7 +59,7 @@
<node id="n3">
<data key="d6">
<y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="-223.31797235022987" y="444.052419354839"/>
+ <y:Geometry height="41.0" width="120.0" x="-256.31797235022987" y="430.71266021753934"/>
<y:Fill color="#FFFFFF" transparent="false"/>
<y:BorderStyle color="#3366FF" type="line" width="3.0"/>
<y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="19.92626953125" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="10.536865234375">ex:doc1</y:NodeLabel>
@@ -71,7 +71,7 @@
<node id="n4">
<data key="d6">
<y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="91.49539170506876" y="412.052419354839"/>
+ <y:Geometry height="41.0" width="120.0" x="58.495391705068755" y="398.71266021753934"/>
<y:Fill color="#FFFFFF" transparent="false"/>
<y:BorderStyle color="#3366FF" type="line" width="3.0"/>
<y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="2.57373046875">dct:Agent
@@ -84,7 +84,7 @@
<node id="n5">
<data key="d6">
<y:ShapeNode>
- <y:Geometry height="41.0" width="146.0" x="-78.91129032258056" y="902.0362903225808"/>
+ <y:Geometry height="41.0" width="146.0" x="-108.91129032258056" y="902.0362903225808"/>
<y:Fill color="#C0C0C0" transparent="false"/>
<y:BorderStyle color="#3366FF" type="line" width="3.0"/>
<y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="146.0" x="0.0" y="2.57373046875">prov:Entity
@@ -97,12 +97,13 @@
<node id="n6">
<data key="d6">
<y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="-65.91129032258056" y="578.7137096774196"/>
- <y:Fill color="#FFFFFF" transparent="false"/>
+ <y:Geometry height="59.0" width="212.6267281105993" x="-142.2246543778802" y="731.3750000000002"/>
+ <y:Fill color="#C0C0C0" transparent="false"/>
<y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="2.57373046875">prov:Agent
-ex:creator</y:NodeLabel>
- <y:Shape type="ellipse"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="51.77880859375" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="212.6267281105993" x="0.0" y="3.610595703125">prov:Activity,
+prov:CreationActivity
+_:activity</y:NodeLabel>
+ <y:Shape type="rectangle"/>
<y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
</y:ShapeNode>
</data>
@@ -110,21 +111,18 @@
<node id="n7">
<data key="d6">
<y:ShapeNode>
- <y:Geometry height="59.0" width="212.6267281105993" x="-112.2246543778802" y="731.3750000000002"/>
- <y:Fill color="#C0C0C0" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="51.77880859375" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="212.6267281105993" x="0.0" y="3.610595703125">prov:Activity,
-dcprov:CreationActivity
-_:activity</y:NodeLabel>
+ <y:Geometry height="30.0" width="30.0" x="-53.911290322580555" y="460.0312086046357"/>
+ <y:Fill hasColor="false" transparent="false"/>
+ <y:BorderStyle hasColor="false" type="line" width="1.0"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="content" borderDistance="0.0" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" hasText="false" height="4.0" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="4.0" x="13.0" y="13.0"/>
<y:Shape type="rectangle"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
</y:ShapeNode>
</data>
</node>
<node id="n8">
<data key="d6">
<y:ShapeNode>
- <y:Geometry height="30.0" width="30.0" x="-20.911290322580555" y="473.3709677419354"/>
+ <y:Geometry height="30.0" width="30.0" x="-20.911290322580555" y="566.3750000000003"/>
<y:Fill hasColor="false" transparent="false"/>
<y:BorderStyle hasColor="false" type="line" width="1.0"/>
<y:NodeLabel alignment="center" autoSizePolicy="content" borderDistance="0.0" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" hasText="false" height="4.0" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="4.0" x="13.0" y="13.0"/>
@@ -135,18 +133,7 @@
<node id="n9">
<data key="d6">
<y:ShapeNode>
- <y:Geometry height="30.0" width="30.0" x="-20.911290322580555" y="566.3750000000003"/>
- <y:Fill hasColor="false" transparent="false"/>
- <y:BorderStyle hasColor="false" type="line" width="1.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="content" borderDistance="0.0" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" hasText="false" height="4.0" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="4.0" x="13.0" y="13.0"/>
- <y:Shape type="rectangle"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n10">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="91.49539170506876" y="483.052419354839"/>
+ <y:Geometry height="41.0" width="120.0" x="58.495391705068755" y="469.71266021753934"/>
<y:Fill color="#FFFFFF" transparent="false"/>
<y:BorderStyle color="#3366FF" type="line" width="3.0"/>
<y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="19.92626953125" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="10.536865234375">ex:dateCreation</y:NodeLabel>
@@ -155,7 +142,7 @@
</y:ShapeNode>
</data>
</node>
- <node id="n11">
+ <node id="n10">
<data key="d6">
<y:ShapeNode>
<y:Geometry height="41.0" width="120.0" x="228.02880184331838" y="902.0362903225808"/>
@@ -168,7 +155,7 @@
</y:ShapeNode>
</data>
</node>
- <node id="n12">
+ <node id="n11">
<data key="d6">
<y:ShapeNode>
<y:Geometry height="41.0" width="120.0" x="228.02880184331838" y="740.3750000000002"/>
@@ -180,7 +167,7 @@
</y:ShapeNode>
</data>
</node>
- <node id="n13">
+ <node id="n12">
<data key="d6">
<y:ShapeNode>
<y:Geometry height="35.0" width="127.62672811059929" x="100.40207373271909" y="650.7137096774196"/>
@@ -193,7 +180,7 @@
</y:ShapeNode>
</data>
</node>
- <node id="n14">
+ <node id="n13">
<data key="d6">
<y:ShapeNode>
<y:Geometry height="35.0" width="127.62672811059929" x="100.40207373271909" y="828.7056451612905"/>
@@ -206,7 +193,7 @@
</y:ShapeNode>
</data>
</node>
- <node id="n15">
+ <node id="n14">
<data key="d6">
<y:ShapeNode>
<y:Geometry height="41.0" width="120.0" x="228.02880184331838" y="578.7137096774196"/>
@@ -219,17 +206,41 @@
</y:ShapeNode>
</data>
</node>
+ <node id="n15">
+ <data key="d6">
+ <y:ShapeNode>
+ <y:Geometry height="35.796720787701815" width="96.0" x="-86.91129032258056" y="595.3264240000003"/>
+ <y:Fill color="#FFFFFF" transparent="false"/>
+ <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="96.0" x="0.0" y="-0.027909137399092288">dct:Agent
+ex:creator</y:NodeLabel>
+ <y:Shape type="rectangle"/>
+ <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
+ </y:ShapeNode>
+ </data>
+ </node>
+ <node id="n16">
+ <data key="d6">
+ <y:ShapeNode>
+ <y:Geometry height="27.902848000000006" width="96.0" x="-86.91129032258056" y="567.4235760000004"/>
+ <y:Fill color="#FFFFFF" transparent="false"/>
+ <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" hasText="false" height="4.0" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="96.0" x="0.0" y="11.951423999999975"/>
+ <y:Shape type="triangle"/>
+ </y:ShapeNode>
+ </data>
+ </node>
<edge id="e0" source="n3" target="n4">
<data key="d10">
<y:BezierEdge>
<y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
<y:LineStyle color="#000000" type="line" width="1.0"/>
<y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="66.689453125" x="66.55303462859132" y="-22.504953692035997">dct:creator</y:EdgeLabel>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="66.689453125" x="66.55303462859132" y="-22.504960632070038">dct:creator</y:EdgeLabel>
</y:BezierEdge>
</data>
</edge>
- <edge id="e1" source="n5" target="n6">
+ <edge id="e1" source="n5" target="n15">
<data key="d10">
<y:BezierEdge>
<y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0">
@@ -237,107 +248,107 @@
</y:Path>
<y:LineStyle color="#000000" type="line" width="1.0"/>
<y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="123.384765625" x="-169.9648263957654" y="-91.34336606917816">prov:wasAttributedTo</y:EdgeLabel>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="123.384765625" x="-155.32394585977983" y="-91.02891294417816">prov:wasAttributedTo</y:EdgeLabel>
</y:BezierEdge>
</data>
</edge>
- <edge id="e2" source="n7" target="n6">
+ <edge id="e2" source="n6" target="n15">
<data key="d10">
<y:BezierEdge>
<y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
<y:LineStyle color="#000000" type="line" width="1.0"/>
<y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="140.716796875" x="-70.35839859131835" y="-68.18123109879002">prov:wasAssociatedWith</y:EdgeLabel>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="140.716796875" x="-71.37687035069172" y="-62.47651354364882">prov:wasAssociatedWith</y:EdgeLabel>
</y:BezierEdge>
</data>
</edge>
- <edge id="e3" source="n8" target="n9">
+ <edge id="e3" source="n7" target="n8">
<data key="d10">
<y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
+ <y:Path sx="0.0" sy="0.0" tx="-33.0" ty="-18.87500000000034"/>
<y:LineStyle color="#000000" type="line" width="5.0"/>
<y:Arrows source="none" target="standard"/>
</y:BezierEdge>
</data>
</edge>
- <edge id="e4" source="n5" target="n7">
- <data key="d10">
- <y:PolyLineEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="128.728515625" x="-64.36425796631835" y="-68.18125669417827">prov:wasGeneratedBy</y:EdgeLabel>
- <y:BendStyle smoothed="false"/>
- </y:PolyLineEdge>
- </data>
- </edge>
- <edge id="e5" source="n3" target="n10">
+ <edge id="e4" source="n5" target="n6">
<data key="d10">
<y:PolyLineEdge>
<y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
<y:LineStyle color="#000000" type="line" width="1.0"/>
<y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="69.3671875" x="66.31644710417726" y="0.16158073179212806">dct:created</y:EdgeLabel>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="128.728515625" x="-64.36425891999266" y="-68.18125669417827">prov:wasGeneratedBy</y:EdgeLabel>
<y:BendStyle smoothed="false"/>
</y:PolyLineEdge>
</data>
</edge>
- <edge id="e6" source="n5" target="n11">
- <data key="d10">
- <y:PolyLineEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="121.38671875" x="19.776689415154067" y="-12.35061153288791">prov:specializationOf</y:EdgeLabel>
- <y:BendStyle smoothed="false"/>
- </y:PolyLineEdge>
- </data>
- </edge>
- <edge id="e7" source="n7" target="n13">
+ <edge id="e5" source="n3" target="n9">
<data key="d10">
<y:PolyLineEdge>
<y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
<y:LineStyle color="#000000" type="line" width="1.0"/>
<y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="18.701171875" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="136.744140625" x="-26.454858056839868" y="-32.18123109879002">prov:qualifiedAssociation</y:EdgeLabel>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="69.3671875" x="66.31644710417726" y="0.16160430933621228">dct:created</y:EdgeLabel>
<y:BendStyle smoothed="false"/>
</y:PolyLineEdge>
</data>
</edge>
- <edge id="e8" source="n13" target="n6">
+ <edge id="e6" source="n5" target="n10">
<data key="d10">
<y:PolyLineEdge>
<y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
<y:LineStyle color="#000000" type="line" width="1.0"/>
<y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="18.701171875" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="60.70703125" x="-70.52303517669681" y="-25.64251571756347">prov:agent</y:EdgeLabel>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="121.38671875" x="34.7766856004568" y="-12.35061153288791">prov:specializationOf</y:EdgeLabel>
<y:BendStyle smoothed="false"/>
</y:PolyLineEdge>
</data>
</edge>
- <edge id="e9" source="n5" target="n14">
+ <edge id="e7" source="n6" target="n12">
<data key="d10">
<y:PolyLineEdge>
<y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
<y:LineStyle color="#000000" type="line" width="1.0"/>
<y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="18.701171875" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="134.751953125" x="-17.699332742103635" y="-31.63898098853315">prov:qualifiedGeneration</y:EdgeLabel>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="18.701171875" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="136.744140625" x="-19.06321407450787" y="-32.18123109879002">prov:qualifiedAssociation</y:EdgeLabel>
<y:BendStyle smoothed="false"/>
</y:PolyLineEdge>
</data>
</edge>
- <edge id="e10" source="n14" target="n7">
+ <edge id="e8" source="n12" target="n15">
<data key="d10">
<y:PolyLineEdge>
<y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
<y:LineStyle color="#000000" type="line" width="1.0"/>
<y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="18.701171875" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="67.3515625" x="-71.84593255806756" y="-28.495627126385898">prov:activity</y:EdgeLabel>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="18.701171875" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="60.70703125" x="-77.75981917139558" y="-22.184068297275644">prov:agent</y:EdgeLabel>
<y:BendStyle smoothed="false"/>
</y:PolyLineEdge>
</data>
</edge>
- <edge id="e11" source="n5" target="n12">
+ <edge id="e9" source="n5" target="n13">
+ <data key="d10">
+ <y:PolyLineEdge>
+ <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
+ <y:LineStyle color="#000000" type="line" width="1.0"/>
+ <y:Arrows source="none" target="standard"/>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="18.701171875" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="134.751953125" x="-6.6615863821832875" y="-32.50775540259565">prov:qualifiedGeneration</y:EdgeLabel>
+ <y:BendStyle smoothed="false"/>
+ </y:PolyLineEdge>
+ </data>
+ </edge>
+ <edge id="e10" source="n13" target="n6">
+ <data key="d10">
+ <y:PolyLineEdge>
+ <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
+ <y:LineStyle color="#000000" type="line" width="1.0"/>
+ <y:Arrows source="none" target="standard"/>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="18.701171875" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="67.3515625" x="-78.60124482955348" y="-28.506064138104648">prov:activity</y:EdgeLabel>
+ <y:BendStyle smoothed="false"/>
+ </y:PolyLineEdge>
+ </data>
+ </edge>
+ <edge id="e11" source="n5" target="n11">
<data key="d10">
<y:PolyLineEdge>
<y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0">
@@ -345,12 +356,12 @@
</y:Path>
<y:LineStyle color="#000000" type="line" width="1.0"/>
<y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="18.701171875" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="122.728515625" x="38.05959836898316" y="-21.031116376948262">prov:generatedAtTime</y:EdgeLabel>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="18.701171875" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="122.728515625" x="52.02383939681519" y="-21.25152050773113">prov:generatedAtTime</y:EdgeLabel>
<y:BendStyle smoothed="true"/>
</y:PolyLineEdge>
</data>
</edge>
- <edge id="e12" source="n14" target="n12">
+ <edge id="e12" source="n13" target="n11">
<data key="d10">
<y:PolyLineEdge>
<y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
@@ -361,7 +372,7 @@
</y:PolyLineEdge>
</data>
</edge>
- <edge id="e13" source="n13" target="n15">
+ <edge id="e13" source="n12" target="n14">
<data key="d10">
<y:PolyLineEdge>
<y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
--- a/dc-note/img-files/cleanup2.graphml Wed Oct 31 13:09:26 2012 +0000
+++ b/dc-note/img-files/cleanup2.graphml Wed Oct 31 13:10:51 2012 +0000
@@ -100,7 +100,7 @@
<y:Fill color="#C0C0C0" transparent="false"/>
<y:BorderStyle color="#3366FF" type="line" width="3.0"/>
<y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="51.77880859375" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="212.6267281105993" x="0.0" y="3.610595703125">prov:Activity,
-dcprov:CreationActivity
+prov:CreationActivity
_:activity1</y:NodeLabel>
<y:Shape type="rectangle"/>
<y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
@@ -173,7 +173,7 @@
<y:Fill color="#C0C0C0" transparent="false"/>
<y:BorderStyle color="#3366FF" type="line" width="3.0"/>
<y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="51.77880859375" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="212.6267281105993" x="0.0" y="3.610595703125">prov:Activity,
-dcprov:PublicationActivity
+prov:PublicationActivity
_:activity2</y:NodeLabel>
<y:Shape type="rectangle"/>
<y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
@@ -302,7 +302,6 @@
</data>
</edge>
<edge id="e9" source="n13" target="n10">
- <data key="d9"/>
<data key="d10">
<y:ArcEdge>
<y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0">
--- a/dc-note/img-files/mapping-example - conflating.graphml Wed Oct 31 13:09:26 2012 +0000
+++ b/dc-note/img-files/mapping-example - conflating.graphml Wed Oct 31 13:10:51 2012 +0000
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<graphml xmlns="http://graphml.graphdrawing.org/xmlns" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:y="http://www.yworks.com/xml/graphml" xmlns:yed="http://www.yworks.com/xml/yed/3" xsi:schemaLocation="http://graphml.graphdrawing.org/xmlns http://www.yworks.com/xml/schema/graphml/1.1/ygraphml.xsd">
- <!--Created by yFiles for Java 2.8-->
+ <!--Created by yFiles for Java 2.9-->
<key for="graphml" id="d0" yfiles.type="resources"/>
<key for="port" id="d1" yfiles.type="portgraphics"/>
<key for="port" id="d2" yfiles.type="portgeometry"/>
@@ -59,7 +59,7 @@
<node id="n3">
<data key="d6">
<y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="-63.34792626728142" y="474.052419354839"/>
+ <y:Geometry height="41.0" width="120.0" x="-63.34792626728142" y="477.05645161290363"/>
<y:Fill color="#FFFFFF" transparent="false"/>
<y:BorderStyle color="#3366FF" type="line" width="3.0"/>
<y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="19.92626953125" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="10.536865234375">ex:doc1</y:NodeLabel>
@@ -71,7 +71,7 @@
<node id="n4">
<data key="d6">
<y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="258.49539170506876" y="474.052419354839"/>
+ <y:Geometry height="41.0" width="120.0" x="258.49539170506876" y="477.05645161290363"/>
<y:Fill color="#FFFFFF" transparent="false"/>
<y:BorderStyle color="#3366FF" type="line" width="3.0"/>
<y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="2.57373046875">dct:Agent
@@ -84,12 +84,13 @@
<node id="n5">
<data key="d6">
<y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="101.08870967741944" y="869.3750000000003"/>
- <y:Fill color="#FFFFFF" transparent="false"/>
+ <y:Geometry height="59.0" width="239.6267281105993" x="42.7753456221198" y="731.3750000000002"/>
+ <y:Fill color="#C0C0C0" transparent="false"/>
<y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="2.57373046875">prov:Entity
-ex:doc1</y:NodeLabel>
- <y:Shape type="ellipse"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="51.77880859375" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="239.6267281105993" x="0.0" y="3.610595703125">prov:Activity,
+prov:PublicationActivity
+_:activity</y:NodeLabel>
+ <y:Shape type="rectangle"/>
<y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
</y:ShapeNode>
</data>
@@ -97,34 +98,7 @@
<node id="n6">
<data key="d6">
<y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="-90.71716589861762" y="611.3750000000001"/>
- <y:Fill color="#FFFFFF" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="2.57373046875">prov:Agent
-ex:publisher</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n7">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="59.0" width="212.6267281105993" x="54.7753456221198" y="731.3750000000002"/>
- <y:Fill color="#C0C0C0" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="51.77880859375" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="212.6267281105993" x="0.0" y="3.610595703125">prov:Activity,
-dcprov:PublicationActivity
-_:activity</y:NodeLabel>
- <y:Shape type="rectangle"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n8">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="30.0" width="30.0" x="146.08870967741944" y="499.3709677419354"/>
+ <y:Geometry height="30.0" width="30.0" x="146.08870967741944" y="502.375"/>
<y:Fill hasColor="false" transparent="false"/>
<y:BorderStyle hasColor="false" type="line" width="1.0"/>
<y:NodeLabel alignment="center" autoSizePolicy="content" borderDistance="0.0" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" hasText="false" height="4.0" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="4.0" x="13.0" y="13.0"/>
@@ -132,10 +106,10 @@
</y:ShapeNode>
</data>
</node>
- <node id="n9">
+ <node id="n7">
<data key="d6">
<y:ShapeNode>
- <y:Geometry height="30.0" width="30.0" x="146.08870967741944" y="592.3750000000003"/>
+ <y:Geometry height="30.0" width="30.0" x="146.08870967741944" y="595.379032258065"/>
<y:Fill hasColor="false" transparent="false"/>
<y:BorderStyle hasColor="false" type="line" width="1.0"/>
<y:NodeLabel alignment="center" autoSizePolicy="content" borderDistance="0.0" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" hasText="false" height="4.0" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="4.0" x="13.0" y="13.0"/>
@@ -143,16 +117,40 @@
</y:ShapeNode>
</data>
</node>
+ <node id="n8">
+ <data key="d6">
+ <y:ShapeNode>
+ <y:Geometry height="41.0" width="153.1635944700463" x="82.08870967741944" y="611.3750000000001"/>
+ <y:Fill color="#FFFFFF" transparent="false"/>
+ <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="153.1635944700463" x="0.0" y="2.57373046875">prov:Entity
+ex:doc1</y:NodeLabel>
+ <y:Shape type="ellipse"/>
+ <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
+ </y:ShapeNode>
+ </data>
+ </node>
+ <node id="n9">
+ <data key="d6">
+ <y:ShapeNode>
+ <y:Geometry height="35.796720787701815" width="96.0" x="-159.71716589861762" y="613.9766396061492"/>
+ <y:Fill color="#FFFFFF" transparent="false"/>
+ <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="96.0" x="0.0" y="-0.027909137399092288">dct:Agent
+ex:publisher</y:NodeLabel>
+ <y:Shape type="rectangle"/>
+ <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
+ </y:ShapeNode>
+ </data>
+ </node>
<node id="n10">
<data key="d6">
<y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="101.08870967741944" y="611.3750000000001"/>
+ <y:Geometry height="27.902848000000006" width="96.0" x="-159.71716589861762" y="586.0737916061493"/>
<y:Fill color="#FFFFFF" transparent="false"/>
<y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="2.57373046875">prov:Entity
-ex:doc1</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" hasText="false" height="4.0" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="96.0" x="0.0" y="11.951423999999975"/>
+ <y:Shape type="triangle"/>
</y:ShapeNode>
</data>
</node>
@@ -162,33 +160,21 @@
<y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
<y:LineStyle color="#000000" type="line" width="1.0"/>
<y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="78.0390625" x="61.902128562399525" y="-12.350595781879747">dct:publisher</y:EdgeLabel>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="78.0390625" x="61.902128562399525" y="-12.35059184412762">dct:publisher</y:EdgeLabel>
</y:BezierEdge>
</data>
</edge>
- <edge id="e1" source="n5" target="n6">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0">
- <y:Point x="-3.7171658986176226" y="889.8750000000003"/>
- </y:Path>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="123.384765625" x="-178.50623868942887" y="-125.73730468749977">prov:wasAttributedTo</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e2" source="n7" target="n6">
+ <edge id="e1" source="n5" target="n9">
<data key="d10">
<y:BezierEdge>
<y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
<y:LineStyle color="#000000" type="line" width="1.0"/>
<y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="140.716796875" x="-129.0896568089842" y="-51.85058593749977">prov:wasAssociatedWith</y:EdgeLabel>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="140.716796875" x="-157.28611582685625" y="-53.230772494477606">prov:wasAssociatedWith</y:EdgeLabel>
</y:BezierEdge>
</data>
</edge>
- <edge id="e3" source="n8" target="n9">
+ <edge id="e2" source="n6" target="n7">
<data key="d10">
<y:BezierEdge>
<y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
@@ -197,24 +183,75 @@
</y:BezierEdge>
</data>
</edge>
- <edge id="e4" source="n5" target="n7">
+ <edge id="e3" source="n8" target="n5">
+ <data key="d10">
+ <y:ArcEdge>
+ <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0">
+ <y:Point x="192.87960815429688" y="695.3954467773438"/>
+ </y:Path>
+ <y:LineStyle color="#000000" type="line" width="1.0"/>
+ <y:Arrows source="none" target="standard"/>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="18.701171875" modelName="free" modelPosition="anywhere" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="122.728515625" x="-30.258071205371095" y="41.68280029296898">prov:wasGeneratedBy</y:EdgeLabel>
+ <y:Arc height="32.26487350463867" ratio="1.0" type="fixedRatio"/>
+ </y:ArcEdge>
+ </data>
+ </edge>
+ <edge id="e4" source="n5" target="n8">
+ <data key="d10">
+ <y:ArcEdge>
+ <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0">
+ <y:Point x="128.37960815429688" y="697.3545532226562"/>
+ </y:Path>
+ <y:LineStyle color="#000000" type="line" width="1.0"/>
+ <y:Arrows source="none" target="standard"/>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="18.701171875" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="56.69921875" x="-30.44011774013029" y="-61.291229248046875">prov:used</y:EdgeLabel>
+ <y:Arc height="32.26487350463867" ratio="1.0" type="fixedRatio"/>
+ </y:ArcEdge>
+ </data>
+ </edge>
+ <edge id="e5" source="n8" target="n8">
+ <data key="d10">
+ <y:ArcEdge>
+ <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0">
+ <y:Point x="158.67050170898438" y="631.875"/>
+ </y:Path>
+ <y:LineStyle color="#000000" type="line" width="1.0"/>
+ <y:Arrows source="none" target="standard"/>
+ <y:Arc height="0.0" ratio="1.0" type="fixedRatio"/>
+ </y:ArcEdge>
+ </data>
+ </edge>
+ <edge id="e6" source="n8" target="n8">
+ <data key="d10">
+ <y:ArcEdge>
+ <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0">
+ <y:Point x="158.67050170898438" y="631.875"/>
+ </y:Path>
+ <y:LineStyle color="#000000" type="line" width="1.0"/>
+ <y:Arrows source="none" target="standard"/>
+ <y:Arc height="0.0" ratio="1.0" type="fixedRatio"/>
+ </y:ArcEdge>
+ </data>
+ </edge>
+ <edge id="e7" source="n8" target="n8">
+ <data key="d10">
+ <y:ArcEdge>
+ <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0">
+ <y:Point x="158.67050170898438" y="631.875"/>
+ </y:Path>
+ <y:LineStyle color="#000000" type="line" width="1.0"/>
+ <y:Arrows source="none" target="standard"/>
+ <y:Arc height="0.0" ratio="1.0" type="fixedRatio"/>
+ </y:ArcEdge>
+ </data>
+ </edge>
+ <edge id="e8" source="n8" target="n9">
<data key="d10">
<y:PolyLineEdge>
<y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
<y:LineStyle color="#000000" type="line" width="1.0"/>
<y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="128.728515625" x="-64.36426273468993" y="-51.85058593749977">prov:wasGeneratedBy</y:EdgeLabel>
- <y:BendStyle smoothed="false"/>
- </y:PolyLineEdge>
- </data>
- </edge>
- <edge id="e5" source="n7" target="n10">
- <data key="d10">
- <y:PolyLineEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="18.701171875" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="56.69921875" x="-28.34961429718993" y="-48.85058593749977">prov:used</y:EdgeLabel>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="18.701171875" modelName="free" modelPosition="anywhere" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="117.384765625" x="-125.3752220808556" y="-9.37466700548623">prov:wasAttributedTo</y:EdgeLabel>
<y:BendStyle smoothed="false"/>
</y:PolyLineEdge>
</data>
--- a/dc-note/img-files/mapping-example - dani.graphml Wed Oct 31 13:09:26 2012 +0000
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,277 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<graphml xmlns="http://graphml.graphdrawing.org/xmlns" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:y="http://www.yworks.com/xml/graphml" xmlns:yed="http://www.yworks.com/xml/yed/3" xsi:schemaLocation="http://graphml.graphdrawing.org/xmlns http://www.yworks.com/xml/schema/graphml/1.1/ygraphml.xsd">
- <!--Created by yFiles for Java 2.8-->
- <key for="graphml" id="d0" yfiles.type="resources"/>
- <key for="port" id="d1" yfiles.type="portgraphics"/>
- <key for="port" id="d2" yfiles.type="portgeometry"/>
- <key for="port" id="d3" yfiles.type="portuserdata"/>
- <key attr.name="url" attr.type="string" for="node" id="d4"/>
- <key attr.name="description" attr.type="string" for="node" id="d5"/>
- <key for="node" id="d6" yfiles.type="nodegraphics"/>
- <key attr.name="Description" attr.type="string" for="graph" id="d7"/>
- <key attr.name="url" attr.type="string" for="edge" id="d8"/>
- <key attr.name="description" attr.type="string" for="edge" id="d9"/>
- <key for="edge" id="d10" yfiles.type="edgegraphics"/>
- <graph edgedefault="directed" id="G">
- <data key="d7"/>
- <node id="n0">
- <data key="d4"/>
- <data key="d6">
- <y:GenericNode configuration="com.yworks.bpmn.Artifact.withShadow">
- <y:Geometry height="164.10822652164057" width="153.1635944700463" x="462.3652073732717" y="445.173709319825"/>
- <y:Fill color="#FFFFFF" transparent="false"/>
- <y:BorderStyle hasColor="false" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" hasText="false" height="4.0" modelName="internal" modelPosition="b" textColor="#000000" visible="true" width="4.0" x="74.58179723502315" y="156.10822652164063"/>
- <y:StyleProperties>
- <y:Property class="com.yworks.yfiles.bpmn.view.BPMNTypeEnum" name="com.yworks.bpmn.type" value="ARTIFACT_TYPE_ANNOTATION"/>
- <y:Property name="com.yworks.bpmn.icon.line.color"/>
- <y:Property class="java.awt.Color" name="com.yworks.bpmn.icon.fill" value="#ffffff"/>
- <y:Property class="java.awt.Color" name="com.yworks.bpmn.icon.fill2" value="#ffffff"/>
- </y:StyleProperties>
- </y:GenericNode>
- </data>
- </node>
- <node id="n1">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="48.0" width="115.15668202764982" x="478.94700460829483" y="454.8491401425408"/>
- <y:Fill color="#FFFFFF" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="bold" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="115.15668202764982" x="0.0" y="6.07373046875">Identified
-Resources</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n2">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="48.0" width="115.15668202764982" x="478.94700460829483" y="544.1747587797053"/>
- <y:Fill color="#C0C0C0" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="bold" hasBackgroundColor="false" hasLineColor="false" height="19.92626953125" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="115.15668202764982" x="0.0" y="14.036865234375">Blank nodes</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n3">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="-63.34792626728142" y="474.052419354839"/>
- <y:Fill color="#FFFFFF" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="19.92626953125" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="10.536865234375">ex:doc1</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n4">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="258.49539170506876" y="474.052419354839"/>
- <y:Fill color="#FFFFFF" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="2.57373046875">dct:Agent
-ex:publisher</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n5">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="-210.15668202764982" y="726.3750000000002"/>
- <y:Fill color="#FFFFFF" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="2.57373046875">prov:Entity
-ex:doc1</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n6">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="102.28283410138238" y="604.3750000000002"/>
- <y:Fill color="#C0C0C0" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="2.57373046875">prov:Entity
-_:used_entity</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n7">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="50.0" width="128.0" x="98.28283410138238" y="726.3750000000002"/>
- <y:Fill color="#C0C0C0" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="128.0" x="0.0" y="7.07373046875">prov:Entity
-_:resulting_entity</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n8">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="102.28283410138238" y="871.3750000000001"/>
- <y:Fill color="#FFFFFF" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="2.57373046875">prov:Agent
-ex:publisher</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n9">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="59.0" width="212.6267281105993" x="421.05990783410107" y="717.3750000000002"/>
- <y:Fill color="#C0C0C0" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="51.77880859375" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="212.6267281105993" x="0.0" y="3.610595703125">prov:Activity,
-dcprov:PublicationActivity
-_:activity</y:NodeLabel>
- <y:Shape type="rectangle"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n10">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="30.0" width="30.0" x="146.08870967741944" y="499.3709677419354"/>
- <y:Fill hasColor="false" transparent="false"/>
- <y:BorderStyle hasColor="false" type="line" width="1.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="content" borderDistance="0.0" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" hasText="false" height="4.0" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="4.0" x="13.0" y="13.0"/>
- <y:Shape type="rectangle"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n11">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="30.0" width="30.0" x="146.08870967741944" y="592.3750000000003"/>
- <y:Fill hasColor="false" transparent="false"/>
- <y:BorderStyle hasColor="false" type="line" width="1.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="content" borderDistance="0.0" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" hasText="false" height="4.0" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="4.0" x="13.0" y="13.0"/>
- <y:Shape type="rectangle"/>
- </y:ShapeNode>
- </data>
- </node>
- <edge id="e0" source="n3" target="n4">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="78.0390625" x="61.902128562399525" y="-12.350595781879747">dct:publisher</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e1" source="n7" target="n5">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="121.38671875" x="-154.95657728344622" y="-13.708248934647372">prov:specializationOf</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e2" source="n6" target="n5">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="121.38671875" x="-177.40280531078997" y="33.22161865234398">prov:specializationOf</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e3" source="n7" target="n8">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="123.384765625" x="-61.69238562518012" y="35.14941406250023">prov:wasAttributedTo</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e4" source="n5" target="n8">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="123.384765625" x="58.95528795092878" y="43.64074707031273">prov:wasAttributedTo</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e5" source="n9" target="n8">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="140.716796875" x="-192.6903673992465" y="36.23500702444221">prov:wasAssociatedWith</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e6" source="n7" target="n6">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="127.36328125" x="-63.68164343768012" y="-52.85058593749977">prov:wasDerivedFrom</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e7" source="n7" target="n9">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0">
- <y:Point x="242.5" y="746.5"/>
- </y:Path>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="128.728515625" x="37.101059874081784" y="-13.978140721976843">prov:wasGeneratedBy</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e8" source="n9" target="n6">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="62.69921875" x="-148.77143909085203" y="-51.5887102896188">prov:used</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e9" source="n10" target="n11">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="5.0"/>
- <y:Arrows source="none" target="standard"/>
- </y:BezierEdge>
- </data>
- </edge>
- </graph>
- <data key="d0">
- <y:Resources/>
- </data>
-</graphml>
--- a/dc-note/img-files/mapping-example.graphml Wed Oct 31 13:09:26 2012 +0000
+++ b/dc-note/img-files/mapping-example.graphml Wed Oct 31 13:10:51 2012 +0000
@@ -1,275 +1,288 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<graphml xmlns="http://graphml.graphdrawing.org/xmlns" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:y="http://www.yworks.com/xml/graphml" xmlns:yed="http://www.yworks.com/xml/yed/3" xsi:schemaLocation="http://graphml.graphdrawing.org/xmlns http://www.yworks.com/xml/schema/graphml/1.1/ygraphml.xsd">
- <!--Created by yFiles for Java 2.8-->
- <key for="graphml" id="d0" yfiles.type="resources"/>
- <key for="port" id="d1" yfiles.type="portgraphics"/>
- <key for="port" id="d2" yfiles.type="portgeometry"/>
- <key for="port" id="d3" yfiles.type="portuserdata"/>
- <key attr.name="url" attr.type="string" for="node" id="d4"/>
- <key attr.name="description" attr.type="string" for="node" id="d5"/>
- <key for="node" id="d6" yfiles.type="nodegraphics"/>
- <key attr.name="Description" attr.type="string" for="graph" id="d7"/>
- <key attr.name="url" attr.type="string" for="edge" id="d8"/>
- <key attr.name="description" attr.type="string" for="edge" id="d9"/>
- <key for="edge" id="d10" yfiles.type="edgegraphics"/>
- <graph edgedefault="directed" id="G">
- <data key="d7"/>
- <node id="n0">
- <data key="d4"/>
- <data key="d6">
- <y:GenericNode configuration="com.yworks.bpmn.Artifact.withShadow">
- <y:Geometry height="164.10822652164057" width="153.1635944700463" x="462.3652073732717" y="445.173709319825"/>
- <y:Fill color="#FFFFFF" transparent="false"/>
- <y:BorderStyle hasColor="false" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" hasText="false" height="4.0" modelName="internal" modelPosition="b" textColor="#000000" visible="true" width="4.0" x="74.58179723502315" y="156.10822652164063"/>
- <y:StyleProperties>
- <y:Property class="com.yworks.yfiles.bpmn.view.BPMNTypeEnum" name="com.yworks.bpmn.type" value="ARTIFACT_TYPE_ANNOTATION"/>
- <y:Property name="com.yworks.bpmn.icon.line.color"/>
- <y:Property class="java.awt.Color" name="com.yworks.bpmn.icon.fill" value="#ffffff"/>
- <y:Property class="java.awt.Color" name="com.yworks.bpmn.icon.fill2" value="#ffffff"/>
- </y:StyleProperties>
- </y:GenericNode>
- </data>
- </node>
- <node id="n1">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="48.0" width="115.15668202764982" x="478.94700460829483" y="454.8491401425408"/>
- <y:Fill color="#FFFFFF" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="bold" hasBackgroundColor="false" hasLineColor="false" height="34.265625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="115.15668202764982" x="0.0" y="6.8671875">Identified
-Resources</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n2">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="48.0" width="115.15668202764982" x="478.94700460829483" y="544.1747587797053"/>
- <y:Fill color="#C0C0C0" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="bold" hasBackgroundColor="false" hasLineColor="false" height="19.1328125" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="115.15668202764982" x="0.0" y="14.43359375">Blank nodes</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n3">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="-63.34792626728142" y="474.052419354839"/>
- <y:Fill color="#FFFFFF" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="19.1328125" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="10.93359375">ex:doc1</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n4">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="258.49539170506876" y="474.052419354839"/>
- <y:Fill color="#FFFFFF" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="34.265625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="3.3671875">dct:Agent
-ex:publisher</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n5">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="-210.15668202764982" y="726.3750000000002"/>
- <y:Fill color="#FFFFFF" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="34.265625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="3.3671875">prov:Entity
-ex:doc1</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n6">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="102.28283410138238" y="604.3750000000002"/>
- <y:Fill color="#C0C0C0" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="34.265625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="3.3671875">prov:Entity
-_:in</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n7">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="102.28283410138238" y="726.3750000000002"/>
- <y:Fill color="#C0C0C0" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="34.265625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="3.3671875">prov:Entity
-_:out</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n8">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="41.0" width="120.0" x="102.28283410138238" y="871.3750000000001"/>
- <y:Fill color="#FFFFFF" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="34.265625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="3.3671875">prov:Agent
-ex:publisher</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n9">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="59.0" width="212.6267281105993" x="421.05990783410107" y="717.3750000000002"/>
- <y:Fill color="#C0C0C0" transparent="false"/>
- <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="49.3984375" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="212.6267281105993" x="0.0" y="4.80078125">prov:Activity,
-dcprov:PublicationActivity
-_:act</y:NodeLabel>
- <y:Shape type="ellipse"/>
- <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n10">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="30.0" width="30.0" x="146.08870967741944" y="499.3709677419354"/>
- <y:Fill hasColor="false" transparent="false"/>
- <y:BorderStyle hasColor="false" type="line" width="1.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="content" borderDistance="0.0" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" hasText="false" height="4.0" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="4.0" x="13.0" y="13.0"/>
- <y:Shape type="rectangle"/>
- </y:ShapeNode>
- </data>
- </node>
- <node id="n11">
- <data key="d6">
- <y:ShapeNode>
- <y:Geometry height="30.0" width="30.0" x="146.08870967741944" y="592.3750000000003"/>
- <y:Fill hasColor="false" transparent="false"/>
- <y:BorderStyle hasColor="false" type="line" width="1.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="content" borderDistance="0.0" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" hasText="false" height="4.0" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="4.0" x="13.0" y="13.0"/>
- <y:Shape type="rectangle"/>
- </y:ShapeNode>
- </data>
- </node>
- <edge id="e0" source="n3" target="n4">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="23.96875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="88.64453125" x="56.599394187399525" y="-11.984384844379747">dct:publisher</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e1" source="n7" target="n5">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="23.96875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="136.55078125" x="-164.49515150219622" y="-11.984374999999773">prov:specializationOf</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e2" source="n6" target="n5">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="23.96875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="136.55078125" x="-184.98483656078997" y="33.58782958984398">prov:specializationOf</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e3" source="n7" target="n8">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="23.96875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="139.943359375" x="-69.97168250018012" y="40.01562500000023">prov:wasAttributedTo</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e4" source="n5" target="n8">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="23.96875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="139.943359375" x="50.67599107592879" y="44.00695800781273">prov:wasAttributedTo</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e5" source="n9" target="n8">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="23.96875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="157.01171875" x="-214.22646969416837" y="41.91866180959846">prov:wasAssociatedWith</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e6" source="n7" target="n6">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="23.96875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="142.31640625" x="-71.15820593768012" y="-52.48437499999977">prov:wasDerivedFrom</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e7" source="n7" target="n9">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="23.96875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="143.453125" x="27.661971553679223" y="-11.984374999999773">prov:wasGeneratedBy</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e8" source="n9" target="n6">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="1.0"/>
- <y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="23.96875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="69.89453125" x="-172.7318577920239" y="-58.02700374665005">prov:used</y:EdgeLabel>
- </y:BezierEdge>
- </data>
- </edge>
- <edge id="e9" source="n10" target="n11">
- <data key="d10">
- <y:BezierEdge>
- <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
- <y:LineStyle color="#000000" type="line" width="5.0"/>
- <y:Arrows source="none" target="standard"/>
- </y:BezierEdge>
- </data>
- </edge>
- </graph>
- <data key="d0">
- <y:Resources/>
- </data>
-</graphml>
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<graphml xmlns="http://graphml.graphdrawing.org/xmlns" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:y="http://www.yworks.com/xml/graphml" xmlns:yed="http://www.yworks.com/xml/yed/3" xsi:schemaLocation="http://graphml.graphdrawing.org/xmlns http://www.yworks.com/xml/schema/graphml/1.1/ygraphml.xsd">
+ <!--Created by yFiles for Java 2.9-->
+ <key for="graphml" id="d0" yfiles.type="resources"/>
+ <key for="port" id="d1" yfiles.type="portgraphics"/>
+ <key for="port" id="d2" yfiles.type="portgeometry"/>
+ <key for="port" id="d3" yfiles.type="portuserdata"/>
+ <key attr.name="url" attr.type="string" for="node" id="d4"/>
+ <key attr.name="description" attr.type="string" for="node" id="d5"/>
+ <key for="node" id="d6" yfiles.type="nodegraphics"/>
+ <key attr.name="Description" attr.type="string" for="graph" id="d7"/>
+ <key attr.name="url" attr.type="string" for="edge" id="d8"/>
+ <key attr.name="description" attr.type="string" for="edge" id="d9"/>
+ <key for="edge" id="d10" yfiles.type="edgegraphics"/>
+ <graph edgedefault="directed" id="G">
+ <data key="d7"/>
+ <node id="n0">
+ <data key="d4"/>
+ <data key="d6">
+ <y:GenericNode configuration="com.yworks.bpmn.Artifact.withShadow">
+ <y:Geometry height="164.10822652164057" width="153.1635944700463" x="462.3652073732717" y="445.173709319825"/>
+ <y:Fill color="#FFFFFF" transparent="false"/>
+ <y:BorderStyle hasColor="false" type="line" width="3.0"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" hasText="false" height="4.0" modelName="internal" modelPosition="b" textColor="#000000" visible="true" width="4.0" x="74.58179723502315" y="156.10822652164063"/>
+ <y:StyleProperties>
+ <y:Property class="com.yworks.yfiles.bpmn.view.BPMNTypeEnum" name="com.yworks.bpmn.type" value="ARTIFACT_TYPE_ANNOTATION"/>
+ <y:Property name="com.yworks.bpmn.icon.line.color"/>
+ <y:Property class="java.awt.Color" name="com.yworks.bpmn.icon.fill" value="#ffffff"/>
+ <y:Property class="java.awt.Color" name="com.yworks.bpmn.icon.fill2" value="#ffffff"/>
+ </y:StyleProperties>
+ </y:GenericNode>
+ </data>
+ </node>
+ <node id="n1">
+ <data key="d6">
+ <y:ShapeNode>
+ <y:Geometry height="48.0" width="115.15668202764982" x="478.94700460829483" y="454.8491401425408"/>
+ <y:Fill color="#FFFFFF" transparent="false"/>
+ <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="bold" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="115.15668202764982" x="0.0" y="6.07373046875">Identified
+Resources</y:NodeLabel>
+ <y:Shape type="ellipse"/>
+ <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
+ </y:ShapeNode>
+ </data>
+ </node>
+ <node id="n2">
+ <data key="d6">
+ <y:ShapeNode>
+ <y:Geometry height="48.0" width="115.15668202764982" x="478.94700460829483" y="544.1747587797053"/>
+ <y:Fill color="#C0C0C0" transparent="false"/>
+ <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="bold" hasBackgroundColor="false" hasLineColor="false" height="19.92626953125" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="115.15668202764982" x="0.0" y="14.036865234375">Blank nodes</y:NodeLabel>
+ <y:Shape type="ellipse"/>
+ <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
+ </y:ShapeNode>
+ </data>
+ </node>
+ <node id="n3">
+ <data key="d6">
+ <y:ShapeNode>
+ <y:Geometry height="41.0" width="120.0" x="-63.34792626728142" y="474.052419354839"/>
+ <y:Fill color="#FFFFFF" transparent="false"/>
+ <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="19.92626953125" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="10.536865234375">ex:doc1</y:NodeLabel>
+ <y:Shape type="ellipse"/>
+ <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
+ </y:ShapeNode>
+ </data>
+ </node>
+ <node id="n4">
+ <data key="d6">
+ <y:ShapeNode>
+ <y:Geometry height="41.0" width="120.0" x="-210.15668202764982" y="726.3750000000002"/>
+ <y:Fill color="#FFFFFF" transparent="false"/>
+ <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="2.57373046875">prov:Entity
+ex:doc1</y:NodeLabel>
+ <y:Shape type="ellipse"/>
+ <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
+ </y:ShapeNode>
+ </data>
+ </node>
+ <node id="n5">
+ <data key="d6">
+ <y:ShapeNode>
+ <y:Geometry height="41.0" width="120.0" x="102.28283410138238" y="604.3750000000002"/>
+ <y:Fill color="#C0C0C0" transparent="false"/>
+ <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="2.57373046875">prov:Entity
+_:used_entity</y:NodeLabel>
+ <y:Shape type="ellipse"/>
+ <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
+ </y:ShapeNode>
+ </data>
+ </node>
+ <node id="n6">
+ <data key="d6">
+ <y:ShapeNode>
+ <y:Geometry height="50.0" width="128.0" x="98.28283410138238" y="726.3750000000002"/>
+ <y:Fill color="#C0C0C0" transparent="false"/>
+ <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="128.0" x="0.0" y="7.07373046875">prov:Entity
+_:resulting_entity</y:NodeLabel>
+ <y:Shape type="ellipse"/>
+ <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
+ </y:ShapeNode>
+ </data>
+ </node>
+ <node id="n7">
+ <data key="d6">
+ <y:ShapeNode>
+ <y:Geometry height="59.0" width="212.6267281105993" x="421.05990783410107" y="717.3750000000002"/>
+ <y:Fill color="#C0C0C0" transparent="false"/>
+ <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="51.77880859375" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="212.6267281105993" x="0.0" y="3.610595703125">prov:Activity,
+prov:PublicationActivity
+_:activity</y:NodeLabel>
+ <y:Shape type="rectangle"/>
+ <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
+ </y:ShapeNode>
+ </data>
+ </node>
+ <node id="n8">
+ <data key="d6">
+ <y:ShapeNode>
+ <y:Geometry height="30.0" width="30.0" x="146.08870967741944" y="499.3709677419354"/>
+ <y:Fill hasColor="false" transparent="false"/>
+ <y:BorderStyle hasColor="false" type="line" width="1.0"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="content" borderDistance="0.0" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" hasText="false" height="4.0" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="4.0" x="13.0" y="13.0"/>
+ <y:Shape type="rectangle"/>
+ </y:ShapeNode>
+ </data>
+ </node>
+ <node id="n9">
+ <data key="d6">
+ <y:ShapeNode>
+ <y:Geometry height="30.0" width="30.0" x="146.08870967741944" y="592.3750000000003"/>
+ <y:Fill hasColor="false" transparent="false"/>
+ <y:BorderStyle hasColor="false" type="line" width="1.0"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="content" borderDistance="0.0" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" hasText="false" height="4.0" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="4.0" x="13.0" y="13.0"/>
+ <y:Shape type="rectangle"/>
+ </y:ShapeNode>
+ </data>
+ </node>
+ <node id="n10">
+ <data key="d6">
+ <y:ShapeNode>
+ <y:Geometry height="41.0" width="120.0" x="258.49539170506876" y="474.052419354839"/>
+ <y:Fill color="#FFFFFF" transparent="false"/>
+ <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="120.0" x="0.0" y="2.57373046875">dct:Agent
+ex:publisher</y:NodeLabel>
+ <y:Shape type="ellipse"/>
+ <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
+ </y:ShapeNode>
+ </data>
+ </node>
+ <node id="n11">
+ <data key="d6">
+ <y:ShapeNode>
+ <y:Geometry height="35.796720787701815" width="96.0" x="114.28283410138238" y="873.9766396061492"/>
+ <y:Fill color="#FFFFFF" transparent="false"/>
+ <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="35.8525390625" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="96.0" x="0.0" y="-0.027909137399092288">dct:Agent
+ex:publisher</y:NodeLabel>
+ <y:Shape type="rectangle"/>
+ <y:DropShadow color="#B3A691" offsetX="5" offsetY="5"/>
+ </y:ShapeNode>
+ </data>
+ </node>
+ <node id="n12">
+ <data key="d6">
+ <y:ShapeNode>
+ <y:Geometry height="27.902848000000006" width="96.0" x="114.28283410138238" y="846.0737916061493"/>
+ <y:Fill color="#FFFFFF" transparent="false"/>
+ <y:BorderStyle color="#3366FF" type="line" width="3.0"/>
+ <y:NodeLabel alignment="center" autoSizePolicy="node_width" fontFamily="Dialog" fontSize="13" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" hasText="false" height="4.0" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="96.0" x="0.0" y="11.951423999999975"/>
+ <y:Shape type="triangle"/>
+ </y:ShapeNode>
+ </data>
+ </node>
+ <edge id="e0" source="n3" target="n10">
+ <data key="d10">
+ <y:BezierEdge>
+ <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
+ <y:LineStyle color="#000000" type="line" width="1.0"/>
+ <y:Arrows source="none" target="standard"/>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="78.0390625" x="61.902128562399525" y="-12.350595781879747">dct:publisher</y:EdgeLabel>
+ </y:BezierEdge>
+ </data>
+ </edge>
+ <edge id="e1" source="n6" target="n4">
+ <data key="d10">
+ <y:BezierEdge>
+ <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
+ <y:LineStyle color="#000000" type="line" width="1.0"/>
+ <y:Arrows source="none" target="standard"/>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="121.38671875" x="-154.95657728344622" y="-13.708248934647372">prov:specializationOf</y:EdgeLabel>
+ </y:BezierEdge>
+ </data>
+ </edge>
+ <edge id="e2" source="n5" target="n4">
+ <data key="d10">
+ <y:BezierEdge>
+ <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
+ <y:LineStyle color="#000000" type="line" width="1.0"/>
+ <y:Arrows source="none" target="standard"/>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="121.38671875" x="-177.40280531078997" y="33.22161865234398">prov:specializationOf</y:EdgeLabel>
+ </y:BezierEdge>
+ </data>
+ </edge>
+ <edge id="e3" source="n6" target="n12">
+ <data key="d10">
+ <y:BezierEdge>
+ <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
+ <y:LineStyle color="#000000" type="line" width="1.0"/>
+ <y:Arrows source="none" target="standard"/>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="123.384765625" x="-61.69238562518012" y="22.498809865574685">prov:wasAttributedTo</y:EdgeLabel>
+ </y:BezierEdge>
+ </data>
+ </edge>
+ <edge id="e4" source="n4" target="n11">
+ <data key="d10">
+ <y:BezierEdge>
+ <y:Path sx="0.0" sy="0.0" tx="-20.282834101382377" ty="-4.375000000000114"/>
+ <y:LineStyle color="#000000" type="line" width="1.0"/>
+ <y:Arrows source="none" target="standard"/>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="123.384765625" x="62.008841616207164" y="47.19104221098155">prov:wasAttributedTo</y:EdgeLabel>
+ </y:BezierEdge>
+ </data>
+ </edge>
+ <edge id="e5" source="n7" target="n11">
+ <data key="d10">
+ <y:BezierEdge>
+ <y:Path sx="0.0" sy="0.0" tx="10.717165898617623" ty="-0.3750000000001137"/>
+ <y:LineStyle color="#000000" type="line" width="1.0"/>
+ <y:Arrows source="none" target="standard"/>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="140.716796875" x="-199.37877299740063" y="40.30455058898292">prov:wasAssociatedWith</y:EdgeLabel>
+ </y:BezierEdge>
+ </data>
+ </edge>
+ <edge id="e6" source="n6" target="n5">
+ <data key="d10">
+ <y:BezierEdge>
+ <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
+ <y:LineStyle color="#000000" type="line" width="1.0"/>
+ <y:Arrows source="none" target="standard"/>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="127.36328125" x="-63.68164343768012" y="-52.85058593749977">prov:wasDerivedFrom</y:EdgeLabel>
+ </y:BezierEdge>
+ </data>
+ </edge>
+ <edge id="e7" source="n6" target="n7">
+ <data key="d10">
+ <y:BezierEdge>
+ <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0">
+ <y:Point x="242.5" y="746.5"/>
+ </y:Path>
+ <y:LineStyle color="#000000" type="line" width="1.0"/>
+ <y:Arrows source="none" target="standard"/>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="128.728515625" x="37.101059874081784" y="-13.978140721976843">prov:wasGeneratedBy</y:EdgeLabel>
+ </y:BezierEdge>
+ </data>
+ </edge>
+ <edge id="e8" source="n7" target="n5">
+ <data key="d10">
+ <y:BezierEdge>
+ <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
+ <y:LineStyle color="#000000" type="line" width="1.0"/>
+ <y:Arrows source="none" target="standard"/>
+ <y:EdgeLabel alignment="center" backgroundColor="#FFFFFF" bottomInset="5" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasLineColor="false" height="24.701171875" leftInset="5" modelName="centered" modelPosition="center" preferredPlacement="anywhere" ratio="0.5" rightInset="5" textColor="#000000" topInset="5" visible="true" width="62.69921875" x="-148.77143909085203" y="-51.5887102896188">prov:used</y:EdgeLabel>
+ </y:BezierEdge>
+ </data>
+ </edge>
+ <edge id="e9" source="n8" target="n9">
+ <data key="d10">
+ <y:BezierEdge>
+ <y:Path sx="0.0" sy="0.0" tx="0.0" ty="0.0"/>
+ <y:LineStyle color="#000000" type="line" width="5.0"/>
+ <y:Arrows source="none" target="standard"/>
+ </y:BezierEdge>
+ </data>
+ </edge>
+ </graph>
+ <data key="d0">
+ <y:Resources/>
+ </data>
+</graphml>
Binary file dc-note/img/ComplexMapping.png has changed
Binary file dc-note/img/cleanup1.png has changed
Binary file dc-note/img/cleanup2.png has changed
Binary file dc-note/img/example1.png has changed
Binary file dc-note/img/mapping-example - conflating.png has changed
--- a/examples/eg-24-prov-o-html-examples/rdf/create/rdf/class_Bundle.ttl Wed Oct 31 13:09:26 2012 +0000
+++ b/examples/eg-24-prov-o-html-examples/rdf/create/rdf/class_Bundle.ttl Wed Oct 31 13:10:51 2012 +0000
@@ -1,14 +1,17 @@
-@base: <http://www.example.com/example.ttl> .
+@base <http://www.example.com/example.ttl> .
@prefix my: <http://example.com/my#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
+@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
+@prefix : <http://example.com/#> .
+
## A provenance file located a http://example.com/example.ttl
-< > a prov:Bundle;
+<> a prov:Bundle;
prov:generatedAtTime "2012-05-24T10:30:00"^^xsd:dateTime;
prov:wasAttributedTo :Bob.
my:report1
a my:Report, prov:Entity;
my:version "1";
- prov:generatedAtTime "2012-05-24T10:00:01"^^xsd:dateTime.
\ No newline at end of file
+ prov:generatedAtTime "2012-05-24T10:00:01"^^xsd:dateTime.
--- a/examples/eg-24-prov-o-html-examples/rdf/create/rdf/class_EntityInfluence.ttl Wed Oct 31 13:09:26 2012 +0000
+++ b/examples/eg-24-prov-o-html-examples/rdf/create/rdf/class_EntityInfluence.ttl Wed Oct 31 13:10:51 2012 +0000
@@ -16,5 +16,5 @@
prov:generated :sortedData;
.
-:rawData rdf:type prov:Entity .
-:sortedData rdf:type prov:Entity .
+:rawData a prov:Entity .
+:sortedData a prov:Entity .
--- a/examples/eg-24-prov-o-html-examples/rdf/create/rdf/property_hasAnchor.ttl Wed Oct 31 13:09:26 2012 +0000
+++ b/examples/eg-24-prov-o-html-examples/rdf/create/rdf/property_hasAnchor.ttl Wed Oct 31 13:10:51 2012 +0000
@@ -1,7 +0,0 @@
-@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
-@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
-@prefix owl: <http://www.w3.org/2002/07/owl#> .
-@prefix prov: <http://www.w3.org/ns/prov#> .
-@prefix : <http://example.com/> .
-
-# TODO
--- a/examples/eg-24-prov-o-html-examples/rdf/create/rdf/property_qualifiedInfluence.ttl Wed Oct 31 13:09:26 2012 +0000
+++ b/examples/eg-24-prov-o-html-examples/rdf/create/rdf/property_qualifiedInfluence.ttl Wed Oct 31 13:10:51 2012 +0000
@@ -16,7 +16,7 @@
# This unqualified influence is unknown in PROV,
# this would be a subproperty of wasAssociatedWith.
- ex:wasConductedBy :bob;
+ my:wasConductedBy :bob;
prov:wasInfluencedBy :bob;
prov:qualifiedInfluence [
# Even though PROV systems do not understand :wasConductedBy,
--- a/examples/eg-24-prov-o-html-examples/rdf/create/rdf/property_removed.ttl Wed Oct 31 13:09:26 2012 +0000
+++ b/examples/eg-24-prov-o-html-examples/rdf/create/rdf/property_removed.ttl Wed Oct 31 13:10:51 2012 +0000
@@ -1,19 +0,0 @@
-@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
-@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
-@prefix owl: <http://www.w3.org/2002/07/owl#> .
-@prefix prov: <http://www.w3.org/ns/prov#> .
-@prefix : <http://example.com/> .
-
-:c2
- a prov:Dictionary,
- prov:Entity;
- prov:derivedByRemovalFrom :c1;
- prov:qualifiedRemoval [
- a prov:Removal,
- prov:DictionaryInfluence;
- prov:dictionary :c1;
- prov:removed "k1"^^xsd:string,
- 1337,
- 3.14;
- ];
-.
--- a/examples/eg-40-xml-examples-by-term/xml/PrimarySource.xml Wed Oct 31 13:09:26 2012 +0000
+++ b/examples/eg-40-xml-examples-by-term/xml/PrimarySource.xml Wed Oct 31 13:10:51 2012 +0000
@@ -17,6 +17,7 @@
<prov:wasDerivedFrom>
<prov:generatedEntity prov:ref="ex:la-campagne-de-Russie-1812-1813"/>
<prov:usedEntity prov:ref="ex:revue-d-Histoire-de-la-Pharmacie-t-XVIII"/>
+ <prov:type>prov:PrimarySource</prov:type>
</prov:wasDerivedFrom>
</prov:document>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/model/comments/issue-576-antoine-zimmermann.txt Wed Oct 31 13:10:51 2012 +0000
@@ -0,0 +1,603 @@
+ > Dear PROV working group,
+ >
+ >
+ >
+ > I'm sorry to send my comments so late, but I hope you will take a close attention to what I'm saying here.
+ >
+ >
+ > I've read PROV data model and PROV constraints and while I find PROV-DM satisfying, I have concerns about PROV Constraints.
+ >
+ > The document tries to define a kind of semantics for the PROV-DM, but it's not actually defining a proper semantics at all. And since it does not truly define a formal semantics, it has to redefine the terms that are borrowed from logic, and subtly diverge from the standard notions found in logic. For someone who knows about logic, it makes the document larger, more complicated than it should be, more difficult to read, and more difficult to implement. For someone who does not know about logic, it's not made at all simpler, on the contrary.
+ >
+
+We would like to clarify that we are not attempting to define a
+semantics (in the sense of model theory or programming language
+semantics) for PROV in PROV-CONSTRAINTS. We may do this in a future
+version of PROV-SEM.
+
+What PROV-CONSTRAINTS does is define a subset of PROV documents,
+currently called "valid" by analogy with the notion of validity in
+other Web standards such as XML, CSS, and so on.
+
+We agree that it would be best to avoid redefining standard
+terminology from logic in nonstandard ways, and you are correct that
+"valid" means something different in logic than the sense in which it
+is usually used in Web standards.
+
+Possible actions:
+- change to consistent/consistency checking
+- keep as is, for compatibility with previous standards, but flag the
+ terminological difference
+
+ > To give an example before getting into the details, let us examine the notion of PROV-equivalence, in Section 2.4. Equivalence is a well known and understood notion in maths and logics, which is necessarily reflexive. In PROV, equivalence isn't reflexive! For X to be PROV-equivalent to Y, it is required that both X and Y are PROV-valid, which is the PROV term used to say "consistent".
+ >
+
+
+
+This issue was discussed within the group already, and we could not
+come to an agreement on how equivalence should behave on invalid
+instances. Therefore, we decided not to define equivalence on invalid
+instances.
+
+From a mathematical point of view, we only define equivalence as a
+relation over valid documents/instances, not all instances. This
+avoids the problem of deciding what to do with equivalence for invalid
+instances.
+
+By analogy consider a typed programming language. An expression 1 +
+"foo" is not well-typed; technically one could consider a notion of
+equivalence on such expressions, so that for example, 1 + "foo" would
+be equivalent to 1 + 1 + "foo". But these ill-typed expressions are
+(by the definition of the language) not allowed. Similarly, for
+applications that care about validity, invalid PROV documents can be
+ignored, so (to us) there seems to be no negative consequence to
+defining equivalence to hold only on this subset of documents, or to
+defining all invalid documents to be equivalent (as would follow from
+the logical definition of equivalence).
+
+However, for other applications, such as information retrieval, it is
+not safe to assume that an invalid instance is equivalent to "false";
+we can imagine scenarios where an application wants to search for
+documents similar to an existing (possibly invalid) document. If the
+definition of equivalence considers all invalid documents equivalent,
+then there will be a hige number of matches that have no (intuitive)
+similarity to the query document.
+
+We propose to resolve your concern as follows:
+- specify that equivalence is an equivalence relation on *all* documents
+- specify that no invalid document is equivalent to a valid one
+- specify equivalence between valid documents as already done
+- leave it up to implementations how (if at all) to test equivalence
+on different invalid documents.
+
+
+ > If a proper semantics was defined, there would be no way the document diverge from legacy logical concepts. There would be less chances for mistakes in the definitions and in the rules laters. There would be more flexibililty in the way implementations support the semantics.
+ >
+ > I see two escapes for this:
+ > 1) define an ad hoc model theory for PROV-DM, in the line of what's sketched in PROV-SEM;
+ > 2) rely on a well known logic (such as FOL), to which all PROV statements are mapped, and add FOL axioms to model the constraints.
+ >
+ > 1) is ambitious and I understand there is not enough time to investigate it enough. But 2) is really easy. PROV statements already look a lot like FOL predicates, and PROV Constraints already rely heavily on FOL notions and notations.
+ >
+
+
+
+This is intentional; the goal was to reuse as much of standard
+techniques from logic and particularly database theory as possible.
+However, since our audience (as reflected by the composition of the
+WG) is not expected to be familiar already with first-order logic.
+
+Moreover, writing an arbitrary FOL axiomatization has its own
+problems: since there is currently no standard way to do this we would
+have to restate a lot of the standard definitions in order to make the
+spceification self-contained (as we have already done). In addition,
+an arbitrary FOL theory is not guaranteed to be decidable, even over
+finite models. We resolved that the constraints document had to
+demonstrate decidability/computability, as a basic prerequisite for
+implementability. Simply giving a set of FOL axioms on its own would
+not be enough to do this, and would leave (the vast majority of)
+implementors not familiar with FOL theorem proving/databases/
+constraint solving at sea with respect to implementation.
+
+Proposed solution: Add non-normative material to appendix / sec. 2 giving a FOL axiomatization, possibly proof of soundness/completeness with respect to the algorithm in the spec.
+
+ > Definitions and inferences of 4.1 are not needed if the semantics is defined on the abstract syntax. The abstract syntax is not PROV-N and does not have "syntactic sugar" or "syntactic shortcuts". Meaning, relations in abstract syntax always contain all the arguments, optional or not, possibly with existential variables. The short forms only exist in the surface syntax.
+ >
+
+This is not true; PROV-DM and PROV-N nowhere specify how missing
+arguments are to be expanded. You're correct that Definition 1 (which
+expands short forms) is in a sense implicit in PROV-DM, which only
+discusses the long forms and their optional arguments, but it isn't
+said explicitly in either PROV-DM or PROV-N how the PROV-N short forms
+are to be expanded to PROV-DM. Furthermore, Def. 2-4 deal with
+special cases concerning optional/implicit parameters which are
+definitely not explicit anywhere else. We recognize that there is a
+certain amount of PROV-N centrism in these definitions, but since
+PROV-N is formally specified and the abstract syntax is not, we feel
+it's important to make fully clear how arbitrary PROV-N can be
+translated to the subset of PROV-N that corresponds to the abstract
+syntax of PROV-DM. This is to ensure that there is no room for
+misinterpretation among multiple readers, who may expect different
+conventions for expansion/implicit parameters (even if the rules we
+specified seem "obvious").
+
+
+ > Inferences in 4.2, 4.3, 4.4 and 4.5 are all writable as FOL axioms.
+ >
+
+
+In fact, they already are, modulo trivial syntactic distinctions, as
+explained in sec. 2. We plan to address this by giving the
+axiomatization explicitly as a non-normative appendix.
+
+ > Constraints require equality and an infinite total order (Time with order "precedes"). This does not make the logic more complicated than FOL.
+ >
+ >
+
+Agreed; this is consistent with the specification as is. (however, in
+fact it is fine to limit attention to a finite partial order, because
+event ordering does not necessarily correspond to a fixed timeline
+ordering, to avoid e.g. time-zone centrism).
+
+
+ > Detailed comments:
+ > -----------------
+ >
+ > Section 1.2:
+ > """
+ > We define validity and equivalence in terms of a concept called normalization.
+ > """
+ >
+ > This is not required and suggests that implementations have to rely on normalisation. The choice of formalisation, being entirely procedural, imposes that normalisation is explicitely mentioned in almost all definitions, which in turn asks for repeatedly marking that implementations are not forced to produce normal forms. This obfuscates the document, which could be smaller and simpler.
+ >
+
+Just saying that we *define* validity and equivalence in terms of a
+normalization procedure does not require that all implementations
+explicitly perform normalization. We discussed this issue
+extensively, and one consequence of this is that the implementation
+criteria for the constraints document will only test the extensional
+behavior of validity/equivalence checks; implementations only need to
+classify documents as valid/invalid/equivalent etc. in the same way as
+the reference implementation, they do not have to "be" the reference implementation.
+
+Nevertheless, you are correct that as written, it is difficult to see
+how else one could implement the specification. In fact, you are
+correct that there is a simple, declarative specification via a FOL
+theory of what the normalization algorithm does, which could be used
+as a starting point for people with a formal background or those who
+wish to implement the specification in some other way. However, we
+disagree that it would improve the specification to adopt the
+declarative view as normative.
+
+Making the document smaller and simpler in this way would detract
+from its usefulness to implementors that are not already experts in
+coputational logic. In other words, we recognize that some implementors may want to
+check the constraints in other ways, but we believe that the
+algorithm we used to specify validity and equivalence is a particular,
+good way by default, because it sits within a well-understood formalism known
+from database constraints and finite first-order model theory.
+
+The normal forms are essentially "universal instances" in the sense of
+Fagin et al. 2005, and the algoithm we outline is easily seen to be in
+polynomial time; in contrast, simply giving a FOL theory on its own
+gives no guarantee of efficiency or even decidability.
+
+Proposed solution:
+
+- present the declarative specification as a (non-normative) appendix, building on the discussion in sec. 2. Logicians ought to be able to understand the specification just by reading sec. 2 and the appendix.
+- Keep the procedural specification as is, but clarify that it is just one of many possible ways of implementing the declarative specification, and that other way that gives the same answers to validity / equivalence checks is allowed.
+
+ >
+ > """
+ > Definitions, inferences, and uniqueness constraints can be applied to normalize PROV instances, and event ordering, typing, and impossibility constraints can be checked on the normal form to determine validity. Equivalence of two PROV instances can be determined by comparing their normal forms.
+ > """
+ >
+ > This also strongly suggests normalising by "applying" constraints, as later defined, although it is said later that normalisation is not required in implementations.
+ >
+
+We disagree that this strongly suggests normalization; we discussed
+the wording extensively within the group since several members also
+felt it was important to avoid "specifying the algorithm". Simply
+saying that something can be done in a certain way does not say that
+it MUST be done that way; we were very careful not to make the
+adoption of the algorithm a formal requirement.
+
+By analogy, one can define greatest common divisors procedurally by
+giving Euclid's algorithm or declaratively by a formula that specifies
+the greatest common divisor property. The latter is mathematically
+cleaner but gives little indication how one can efficiently compute
+the GCD. Similarly, specifications such as XQuery describe the
+semantics of expressions by giving an algorithm that serves as a
+reference implementation for the language, but this is not required or
+even encouraged as the only or best way to implement XQuery. To
+facilitate implementation, we chose to specify in terms of an
+algorithm that presents one (reasonably efficient, but in any case
+clearly defined) default way to determine validity or equivalence,
+without specifying that it is the only (or best) way.
+
+Moreover, it is true that normalization is a somewhat extraneous
+concept, but it is a totally natural one from the point of view of
+finite model theory; we are working within a class of constraints that
+admits universal solutions, and the normal form is a universal
+solution.
+
+However, this issue arose relatively late in the process and we did
+miss some places where the document gives a misleading impression that
+normalization is required to implement the spec.
+
+Proposed solution: Revise this and other paragraphs to make sure that
+normalization is an auxiliary notion used to specify validity and
+equivalence. This may be tied in with the non-normative declarative
+specification which implementors may use as a starting point for
+alternative implementations.
+
+ >
+ > """
+ > For PROV documents, validity and equivalence amount to checking the validity or pairwise equivalence of their respective documents.
+ > """
+ >
+ > should be: "... of their respective instances."
+ >
+
+Thanks. Proposed solution: adopt change.
+
+
+ >
+ > """
+ > This specification defines how validity and equivalence are to be checked, if an application elects to support them at all.
+ > """
+ >
+ > It was said before that implementations can choose the way they check validity or equivalence. Again, this is a very strong suggestion that implementation should be made according to the presented procedures.
+ >
+
+Thanks, we agree this is too strong, and it escaped our notice when
+revising to make it clearer that we are not specifying the algorithm.
+
+Proposed solution: Rewrite to "This specification defines validity and
+equivalence. If an application elects to support validity and
+equivalence checking, then it must define these concepts as specified
+here."
+
+
+ >
+ > """
+ > Applications [...] should treat equivalent instances or documents in the same way.
+ > """
+ >
+ > Does it mean that an instance in a bundle can be safely replaced by another equivalent instance inside the bundle? This is important because it may be understood that a bundle identifier identifies the exact set of PROV statements given in a PROV document, or that the bundle identifier simply identifies the logical content of the bundle, or even any content that logically "implies" the content of the bundle in the said document.
+ > The definitions of equivalence and inference suggests that it is the later option. Note that this is something that may have to be understood when writing PROV documents as RDF datasets, given that RDF 1.1 is not specifying any particular relationship between a graph IRI and the content of a named graph.
+ >
+
+
+Since validity and equivalence are optional, this is not a formal
+requirement, but a guideline; what it means for an application to
+treat equivalent instances/documents "in the same way" is application
+specific, and there are natural settings where it makes sense for an
+application (evenone that cares about validity) to have different
+behavior for equivalent documents. We give one example of
+formatting/pretty printing. You give some additional examples;
+digital signing is a third. Because we have no way of circumscribing
+what applications might do or what it means for an application to
+treat documents "in the same way", we just leave this as a guideline.
+
+Proposed solution: Make it clearer that this is a guideline, not a
+formal requirement; give additional examples such as the above.
+
+
+ >
+ > Section 2.4:
+ >
+ > """
+ > Merging
+ >
+ > Merging is an operation that takes two terms and compares them to see if they are equal, or can be made equal by substituting an existential variable with another term.
+ > """
+ >
+ > Normally, merging is an operation that takes two terms and produce a single term. I do not understand what this definition has to do with "merging". After, it is said:
+ >
+ > """
+ > Merging two terms t,t' results in either substitution S such that S(t) = S(t'), or failure indicating that there is no substitution that can be applied to both t and t' to make them equal.
+ > """
+ >
+ > Now, merging results in a substitution. Again, it is at odd with standard definitions of "merging".
+ >
+
+
+The high-level description we give first is consistent with what comes
+later, but can be rewritten to be clearer.
+
+For terms, "merging" is exactly unification in the usual first-order
+logic / logic programming sense, as we state in a remark. For
+predicates that carry attribute lists, things are more complicated
+since key constraints require the attribute lists be unioned, not
+unified in the usual sense.
+
+Proposed solution:
+- Use "unification" for "merging" at the level of terms
+- Declaratively describe unification as producing "either failure or a
+ substitution that makes both sides equal", as well as giving the
+ (standard) algorithm
+- Retain "merging" for the nonstandard operation on predicates that
+unifies the term arguments and unions the lists of attributes.
+
+
+ >
+ > """
+ > Applying definitions, inferences, and constraints
+ > """
+ >
+ > This section is really not needed if all is defined in terms of FOL. This section very strongly suggests one way of implementing PROV-CONSTRAINTS, which is not good. The description, and what's presented later in the normative sections, almost imposes inference materialisation as the normal way to implement all the logical operations on PROV statements (even though the spec says later, in passing, that implementations that lead to the same results are OK).
+ >
+ > Using the notion of "failure" again strongly suggests that the spec is implemented with applications of operations indicated in this section and in Section 6, when in fact any consistency checker would be alright too.
+ >
+
+As noted above, we disagree that rewriting everything in terms of pure
+first-order logic would lead to a satisfactory specification (as
+opposed to a satisfactory research paper, say). The goal of the
+non-normative section here is essentially to link the (implicit)
+declarative semantics of the first-order theory, which we described
+informally earlier, with the procedural way in which normalization
+handles this behavior.
+
+Proposed solution: As noted above, give the declarative specification
+as an annex; make it more explicit that the goal of the specification
+is to give a procedural implementation that is definitely correct.
+
+Alternatively, we could make the declarative specification itself the
+normative thing, and make the rest non-normative, with a comment that
+it is one correct way to implement.
+
+
+ >
+ > """
+ > Checking ordering, typing, and impossibility constraints
+ >
+ > The ordering, typing, and impossibility constraints are checked rather than applied. This means that they do not generate new formulas expressible in PROV,
+ > """
+ >
+ > This sentence again strongly suggests that constraints are "applied", in the sense defined previously, indicating that implementations should follow the operations mentioned previously, when in fact there is no reason to force any materialisation or "normalisastion" at all.
+ > This is again supported by the following sentence:
+ >
+ > "Checking such constraints follows a saturation strategy similar to that for normalization"
+ >
+ > What follows is again dictating an implementation when everything is in fact just logical formulas that have to be consistency-checked.
+ >
+
+See above; same response.
+
+ > PROV then uses the word "valid" where logic would use "consistent". In logic, a formula is valid iff it is necessarily true (it's a tautology). The use of a different term does not help non-logician (they would not be disturbed by the term "consistent") but may be a problem for logicians who are used to other terms.
+ >
+
+See above, where we've discussed the reasons for the use of the term
+"valid" in this context.
+
+
+ >
+ > """
+ > Equivalence and Isomorphism
+ >
+ > [...] This is similar to the notion of equivalence used in [RDF]
+ > """
+ >
+ > RDF does not defined its own notion of equivalence. Equivalence in RDF is simply imposed by its formal semantics, following the standard notion of equivalence in all logics.
+ >
+
+OK. It's not clear what needs to change here, provided that our
+refinement of the notion o equivalence (to be an equivalence relation
+on all instances, and point out that it is the same as "theory
+equivalence" on valid instances) is acceptable.
+
+
+ >
+ > """
+ > [...] to be considered equivalent, the two instances must also be valid
+ > """
+ >
+ > This is very strange, as "equivalence" is defined as a non-reflexive relationship. Again, the definition of equivalence would simply follow from a proper formalisation in FOL or model theory.
+ >
+ > Moreover, again, the paragraph strongly suggests relying on "applying" normalisation to check equivalence.
+ >
+ > See comments on Section 6.1.
+ >
+
+
+These restate issues already discussed above. Briefly, we disagree
+that the notion of equivalence should be aligned with that of standard
+model theory, but agree that it is better if we can make it an
+equivalence relation over all instances, even if we only care about
+its behavior on valid ones.
+
+
+ >
+ > """
+ > From Instances to Bundles and Documents
+ >
+ > [...] a toplevel instance consisting of the set of statements not appearing within a bundle
+ > """
+ >
+ > This /seems/ to indicate that a statement in the top-level instance cannot be repeated in a bundle, while the PROV data model does not have this constraint.
+ >
+
+This is unclear.
+
+Proposed solution: rewrite to "a toplevel instance consisting of statements that appear outside of any bundle"
+
+- to make it clear that appearing in the toplevel instance does not rule out appearing inside a bundle too.
+
+
+ >
+ > """
+ > Analogously to blank nodes in [RDF], the scope of an existential variable in PROV is the instance level
+ > """
+ >
+ > This is true for RDF graphs, but RDF doesn't say anything about the scope of bnodes in complex structures formed out of multiple RDF graphs, such as RDF datasets. This is therefore a constraint that must be indicated and highlighted in PROV.
+ >
+
+We believe that it is clear that any complex structure built up out of
+RDF graphs would, at least, have the behavior we describe, because
+the blank nodes are scoped at the level of each individual graph
+within it. To do otherwise would cause huge problems with
+compositionality, but it does appear that this hasn't been specified
+(nor seems likely to be in the near future) in RDF.
+
+To avoid confusion, we propose to revise this to avoid reference to
+RDF blank nodes, and just say "the scope of an existential variable in
+PROV is at the instance level". This is implicit in the notion of
+equivalence of instances (where bijective renaming of existential
+variables preserves equivalence) and documents (where the existential
+variables in different instances are considered independently).
+
+ >
+ > Section 3:
+ >
+ > This section uses vocabulary that is not yet defined normatively at this position in the document.
+ >
+ > """
+ > If determining whether two PROV instances or documents are equivalent, an application must determine whether their normal forms are equal
+ > """
+ >
+ > This is once more dictating a way of implementing, while relying on normal forms should be completely irrelevant, as indicated by the following sentence.
+ >
+
+This sentence merely defines that equivalence means that the normal forms of the two documents/instances are equal (actually should be isomorphic). This in turn (declaratively) means that the two documents/instances are valid and logically equivalent with respect to the declarative theory. Any implementation that determines equivalence therefore has also determined that their normal forms are isomorphic, whether or not these normal forms are explicitly constructed.
+
+Proposed solution: Rewrite this to make the distinction between specification and implementation clearer here.
+
+ >
+ > Section 4.1
+ >
+ > This section defines equivalence of syntactic constructs that are purely a PROV-N issue. There is no reason to put this in the logic of PROV structures.
+ >
+
+This is discussed above; briefly, the syntactic desugaring rules need
+to be said somewhere, and do not seem to belong in PROV-DM or PROV-N.
+
+An alternative would be for PROV-DM to give a formal abstract syntax
+and for one of PROV-DM or PROV-N to specify the expansion/desugaring
+rules. This might have advantages but the group feels that this
+additional material detracts from the simplicity of the other
+documents, for a purpose that only becomes evident for
+constraint-checking.
+
+ >
+ > Section 5.1
+ >
+ > Merging is defined in a strange way, with a procedure, which makes it difficult to grasp what notion it is supposed to convey.
+ >
+
+Merging/unification is discussed above; briefly, we plan to add its declarative specification and clarify that this is basically standard unification. (There is already a remark saying this.)
+
+ >
+ > Section 5.2
+ >
+ > It is never specified explicitly that "strictly-precedes" is irreflexive. Therefore, the algorithm given in Section 6.1 for checking validity, which relies on this assumption, provides strictly more information than the definition of validity.
+ >
+
+Good point; since section 6.1 is also normative, what is there is correct but unclear.
+
+Proposed solution: Make irreflexivity of strictly-precedes a formal
+constraint.
+
+ >
+ > Section 6.1
+ >
+ > """
+ > A PROV instance is valid if its normal form exists and satisfies all of the validity constraints
+ > """
+ >
+ > Here, it is not clear what "satisfies" means. Satisfaction is a standard term in logic, provided that a proper semantics is defined. Here, there is no proper semantics so the notion of satisfaction would have to be defined. Assuming that PROV statements are indeed mapped to FOL, and constraints expressed as FOL axioms, then the standard notion of "satisfaction" would not work here. For example, the empty document doesn't satisfy any of the constraints (an empty FOL theory only satisfies tautologies, a.k.a., valid formulas, in the usual logical sense of "valid").
+ >
+ > There wouldn't be any problem and it would be very much shorter with a proper first order semantics.
+ >
+
+We disagree that making the specification shorter and more declarative
+would be appropriate, but agree that this passage is unclear about
+what "satisfies" means.
+
+Proposed solution: Align terminology and make sure that we either
+define "satisfies" or use a clearer term for the constraint checking
+process.
+
+ >
+ > In this section, "equivalence" does not require validity, as opposed to Section 2.4.
+ >
+
+Good point; this and other discussion needs to be revised anyway
+following the discussion above.
+
+
+ > Equivalence is defined according to the notion of isomorphic normal form, which is never normatively defined (the only definition being in the non-normative Section 2.4). In any case, there is no reason to rely on isomorphims at all, if only the logic of PROV was properly defined.
+ >
+
+It is also the case that equivalence (for valid instances) is the same
+as logical equivalence of theories. This is because the normal form
+is a universal instance and two theories are equivalent (modulo the
+PROV FOL axiomatization) iff they have isomorphic universal instances.
+For perhaps not very good reasons, such as conciseness and a perceived
+need to avoid making the constraints document too formalism-heavy, the
+spec does not include the formal details explicitly linking the
+procedural and declarative specifications. We plan to address this by
+including the declarative specification as a non-normative appendix.
+
+ > Unfortunately, since equivalence is given in terms of normal forms, and normal forms are given purely in procedural terms, there can be no sensible justification for 2 instances to be non-equivalent. The justification would be "because the procedure gave us different results", which isn't satisfactory at all. This is again a drawback of not providing an appropriate logical account of PROV statements.
+ >
+
+By definition, equivalence (for valid instances0 means *determining*
+whether the normal forms are equivalent. This does not require
+materializing the normal forms or computing them in a specific way,
+only producing the same answers as if this had been done. Any
+algorithm that determines that two instances are not equivalent,
+essentially has determined that their normal forms are different.
+This is just because any inequivalent (valid) instances have different
+universal instances, obtained by the chase procedure in Fagin et al.
+This is true for any FOL theory consisting of tuple-generating and
+functional dependencies, and has nothing to do with any specific
+algorithm.
+
+This would not change (for valid instances) if we took the definition
+of equivalence to be equivalence modulo the FOL axiomatization,
+because it is a theorem (Fagin et al. 2005) that two finite structures
+are equivalent modulo a weakly acyclic TGD+EGD theory precisely when
+their universal instances are isomorphic, i.e., precisely when their
+normal forms are isomorphic. Since the normal forms are essentially
+the "meaning" of the instance either way we define equivalence, we
+chose to make the definition in terms of procedural terms that we
+believe will be more immediately accessible to the expected audience
+of PROV-CONSTRAINTS.
+
+This partly reflects the process followed by the group of developing
+and agreeing to the constraints; we are assuming that the target
+audience for PROV-CONSTRAINTS is primarily implementors of (Semantic)
+Web tools who may not have a formal background, and the group
+consensus is that presenting the definitions of validity and
+equivalence in easily-grasped (and easily-implemented) procedural
+terms is preferable for making the constraints document accessible to
+this audience.
+
+
+
+However we agree it would be helpful to make it clear that
+(in)equivalence (for valid instances) corresponds to logical
+(in)equivalence, as a starting point for any alternative
+implementations of the declarative specification. The idea of making
+the declarative specification normative and providing the
+normalization algorithm as a non-normative suggested reference
+implementation is attractive, but ultimately we feel that doing so
+would be misleading to developers who may not be able to understand
+how to implement the FOL specification in an efficient way without
+reading the non-normative materials, making PROV-CONSTRAINTS
+inaccessible to most of its intended audience.
+
+ >
+ > Best regards,
+ > --
+ > Antoine Zimmermann
+ > ISCOD / LSTI - Institut Henri Fayol
+ > cole Nationale Suprieure des Mines de Saint-tienne
+ > 158 cours Fauriel
+ > 42023 Saint-tienne Cedex 2
+ > France
+ > Tl:+33(0)4 77 42 66 03
+ > Fax:+33(0)4 77 42 66 66
+ > http://zimmer.aprilfoolsreview.com/
+ >
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/model/comments/lc-ack-robert.txt Wed Oct 31 13:10:51 2012 +0000
@@ -0,0 +1,294 @@
+ 1.1.2 ISSUE-525 (Specialization/Alternate)
+
+ I think my comment was misunderstood. Fig 8 in
+ http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html
+ shows the entity-entity relationship as the more general
+ "wasInfluencedBy" relationship, which is defined within that
+ figure to have an ID and attributes (gray box). This is also
+ stated in section 5.3.5. Section 5.5 defines SpecializationOf,
+ AlternateOf, and MentionOf, all of which are entity-entity
+ relationships. Therefore, it seems that specialization is a type
+ of influence and should therefore contain the ID/attributes
+ pattern. If this is not the case, the text may require
+ clarification.
+
+New change implemented.
+Acknowledgement expected.
+
+ 1.1.4 ISSUE-504 (collection/bundle)
+
+ In my opinion, a prov description is as much a "thing in the
+ world" as an activity, attribution, or association (all of which
+ can have an ID). Applications that merge, aggregate, and/or infer
+ provenance will need to track the provenance of individual
+ statements; doing so will require an ID for each statement. It
+ should be noted that if descriptions cannot be given IDs directly,
+ they can (individually) be wrapped in a bundle but this is a
+ highly inefficient workaround.
+
+Suggested change implemented.
+Further response added.
+
+Given that this point has been debated at length (there is no support
+to introduce identifiers for individual prov statements), I propose
+to close this issue.
+
+ 1.1.5 ISSUE-503 (adopt plan)
+
+ The use case in question is simply indicating that a given plan
+ was adopted by a given entity (without necessarily specifying an
+ associated activity). It is not an influence, so wasDerivedFrom
+ and wasAttributedTo do not address the issue. The proposed OWL
+ solution (inverse hadPlan) is technology-specific and isn't quite
+ sufficient, as it requires an activity. I think I'm looking for
+ something similar to wasAssociatedWith, which allows one to
+ associate an activity (required) with an agent and/or plan
+ (optional). In this case, I want to link a plan (required) to an
+ agent (required) with an optional activity.
+
+Suggested change implemented.
+Further response added.
+
+Acknowledgement expected.
+
+ 1.1.15 ISSUE-516 (DerivationAsBundle) Section 5.2.1 states, "there
+ must be some underpinning activities performing the necessary
+ actions resulting in such a derivation". Note both "activities"
+ and "actions" are plural. The statement wasDerivedFrom, however,
+ allows only a single activity to be specified. Is derivation
+ intended to support multiple activities (as per the text), and if
+ so, are multiple statements necessary (one for each activity)?
+ The question about derivation as a bundle was based on the
+ impression that multiple activities might be part of "a
+ derivation" (as per the text).
+
+Clarification about activity/activities implemented.
+http://dvcs.w3.org/hg/prov/rev/65532a436d0c
+Acknowledgement expected.
+
+ 1.1.16 ISSUE-514 (Starter/EnderActivity) The new table helps. I
+ might suggest defining the significance of the terms in
+ parentheses within the table. Also, the agent column probably
+ could be deleted.
+
+Added cross-linking to attribute definitions.
+http://dvcs.w3.org/hg/prov/rev/a995233c4419
+Acknowledgement expected.
+
+ 1.1.12 ISSUE-528 (MentionOf) - I don't feel strongly about this.
+ The comment was in response to an editorial notation in the DM
+ inquiring whether this relation was necessary.
+
+I propose to close. Debate continues for issue-475.
+
+ 1.1.13 ISSUE-517 (Revision/Quotation) I agree that "The
+ definitions of Revision and Quotation are reasonably intuitive."
+ However, the line between the two is fuzzy and it should be
+ acknowledged that those creating provenance statements may face an
+ arbitrary choice between the two.
+
+I extended the response with "We acknowledge the reviewer's follow-on
+comment. Ultimately, the Working Group provides a vocabulary, and
+users of that Vocabulary will have to make judgement as to which
+constructs they have to use. This issue is not specific to revision
+and quotation. (e.g. What is entity? what is activity? Is this
+specialization or alternate? etc)"
+
+I propose to close.
+
+ 1.1.22 ISSUE-515 (Invalidation) Re: temporarily unavailable
+ entities. Thanks for the example. This may address the question.
+ Re: invalidation due to state change. The response by the working
+ group makes sense ("As a minimum, an entity must have a fixed
+ identity during its lifetime." and "some aspects, represented as
+ attributes, that do not change over that lifespan"). That
+ question was motivated by the traffic light example in the DM: "An
+ entity's lifetime can end for different reasons: ... an entity
+ attribute is changing: e.g. the traffic light changed from green
+ to red", then further down in the text "the traffic light became
+ red and therefore is regarded as a different entity to the green
+ light". In that example, the identity of the traffic light did
+ not change, and some attributes of the light remain constant;
+ therefore, it is difficult for me to understand why the state
+ change would invalidate the entity. This example seems to
+ contradict the working group's response to the question.
+
+I added the following to our response.
+
+In the follow-on message, the reviewer discusses the traffic light example. As the light changes from red to green, the green traffic light is invalidated and the red traffic light is generated. Both are specializations of the traffic-light, which continues its existence across this change state, since color is not one of its attributes.
+entity(ex:traffic-light)
+entity(ex:green-traffic-light, [ex:color="green"])
+entity(ex:red-traffic-light, [ex:color="red"])
+specializationOf(ex:green-traffic-light, ex:traffic-light)
+specializationOf(ex:red-traffic-light, ex:traffic-light)
+wasGeneratedBy(ex:red-traffic-light,-,2011-11-16T16:00:00)
+wasInvalidatedBy(ex:green-traffic-light,-,2011-11-16T16:00:00)
+
+I proposed to close this issue.
+
+ 1.1.23 ISSUE-530 (attributes) I understand the group's difficulty
+ in reaching consensus on this issue. Since it is possible to
+ support these attributes via the optional user-defined attributes,
+ leaving them out of the spec will not prevent their use.
+ Variability in implementation is likely, however, so it might be
+ worthwhile to centralize these within an extension once
+ implementations have a chance to experiment with the spec.
+
+Added a comment:
+
+ In response to the follow-on message, the Working Group, as it
+ wraps up its activities, will consider follow-on activities, and
+ mechanisms for community to share information. The Semantic Web
+ wiki is a starting point.
+
+I propose to close this issue.
+
+ 1.1.25 ISSUE-522 (Activity Delegation) There were two parts to my
+ comment. First, agents can be either entities or activities.
+ Does delegation apply to only those agents that are entities, or
+ can activity-agents also delegate? Second, the definition of
+ delegation includes only the delegate and responsible agents;
+ activity is optional. Therefore, it is possible to state that one
+ agent is the delegate of another, irrespective of any activity.
+ This delegation likely is not indefinite, however, and is bounded
+ by some context (e.g., time, role within an organization, etc).
+ It should be possible to describe the bounds of the delegation.
+ This might be done using user-defined attributes, but
+ interoperability would suffer without some guidance within the
+ spec.
+
+Added comment to address this point:
+
+ - It is true that, in a delegation, activity is optional. The reviewer suggests "Therefore, it is possible to state that one agent is the delegate of another, irrespective of any activity. This delegation likely is not indefinite, however, and is bounded by some context (e.g., time, role within an organization, etc). It should be possible to describe the bounds of the delegation.". But it is not the intended semantics:
+ o PROV constraints defines the semantics of optional arguments, and
+ specifically, in Table 3, explains that activity in delegation is
+ expandable.
+ o It means that an absent activity can be replaced by an
+ existential variable. Hence, actedOnBehalfOf(ag2,ag1) really means
+ that agent ag2 acted on behalf of agent ag1 in the context of some
+ unspecified activity. Some activity, not all activity.
+ o This (unspecified) activity defines the bounds of the
+ delegation. If these bounds need to be made explicit, than an
+ activity also needs to be made explicit.
+
+Acknowledgment expected.
+
+ 1.1.27 ISSUE-526 (Alternate) The text in the working group's
+ response to this comment (see below) is helpful. It might be
+ beneficial to add this to the DM document.
+
+ "Note that alternateOf is a necessarily very general
+ relationship that, in reasoning, only tells you that the two
+ alternate entities fix different aspects of some common thing
+ (possibly evolving over time), and so there is some relevant
+ connection between the provenance of the alternates. In a
+ specific application context, alternateOf, or a subtype of it,
+ could allow you to infer more."
+
+Change made
+http://dvcs.w3.org/hg/prov/diff/60b6ee097555/model/prov-dm.html
+Acknowledgment expected.
+
+
+ 1.1.28 ISSUE-502 (Derivation) In my opinion, the initial
+ emphasis on transformation may muddle the definition. The
+ working group's response contained a helpful phrase ("The focus
+ of derivation is on connecting a generated entity to a used
+ entity.") that would add clarity to the definition of
+ derivation.
+
+Sentence was added to the text explaining the notion of derivation:
+ http://dvcs.w3.org/hg/prov/diff/780b82818bcf/model/prov-dm.html
+
+Acknowledgment expected.
+
+
+----------------------------------------------------------------------
+
+All issues below are now closed.
+
+----------------------------------------------------------------------
+
+
+ 1.1.1 ISSUE-532 (Role) - prov:type seems to satisfy the requirement
+
+Closed
+
+
+ 1.1.3 ISSUE-507 (Inverse Relations) - I know there has been
+ considerable discussion regarding the normative/informative
+ sections of the documents. This should address the original
+ comment.
+
+Closed
+
+
+ 1.1.8 ISSUE-500 (activity hierarchy)
+
+ I believe hierarchies of activities will be important when
+ maintaining provenance. I understand the working group is not
+ going to support this use case. I will consider extending the
+ prov spec to support activity hierarchies.
+
+Closed
+
+ 1.1.9 ISSUE-505 (prov-n notation) I believe I reviewed a version
+ of the DM that did not consistently apply the semi-colon
+ convention. The core of the comment, however, duplicates
+ issue-533 (still pending).
+
+Closed
+
+ 1.1.10 ISSUE-508 (Table 5) - Thanks for clarifying the text.
+ Issue-533 will address the remainder of the comment.
+
+Closed
+
+ 1.1.11 ISSUE-531 (Multiple location) - Addressed - no further comment
+
+Closed
+
+ 1.1.14 ISSUE-501 (DrivingACarToBoston) - no further comment
+
+Closed
+ 1.1.17 ISSUE-513 (StartSubActivity) As for Issue-500, I believe it
+ will be important to support these features. As they are not part
+ of the core spec, it may be possible to support them through an
+ extension.
+
+Closed
+
+ 1.1.18 ISSUE-511 (UsageSubActivity) As for Issue-500, I believe it
+ will be important to support these features. As they are not part
+ of the core spec, it may be possible to support them through an
+ extension.
+
+Closed
+
+ 1.1.19 ISSUE-510 (GenerationSubActivity) As for Issue-500, I
+ believe it will be important to support these features. As they
+ are not part of the core spec, it may be possible to support them
+ through an extension.
+
+Closed
+
+ 1.1.20 ISSUE-512 (FinePayingExample) - I think this is more clear.
+ No further comment.
+
+Closed
+
+ 1.1.21 ISSUE-497 (Figure 1) - No further comment
+
+Closed
+
+
+ 1.1.24 ISSUE-520 (Person/Organization/SoftwareAgent)
+ Thank you for the detailed response - it helped clarify for me the intended distinction between entity and agent. I tend to think about these concepts in a different way.
+
+
+Closed.
+
+ 1.1.26 ISSUE-509 (AttributesInUML) - no further comment
+
+Closed
+
--- a/model/diff-n.html Wed Oct 31 13:09:26 2012 +0000
+++ b/model/diff-n.html Wed Oct 31 13:10:51 2012 +0000
@@ -475,15 +475,13 @@
border-width: 1px;
padding: 0px;
border-style: solid;
- border-color: gray;<span class="insert">
- -moz-border-radius: ;</span>
+ border-color: gray;
}
table.thinborder td {
border-width: 1px;
padding: 2px;
border-style: solid;
- border-color: gray;<span class="insert">
- -moz-border-radius: ;</span>
+ border-color: gray;
}
</style>
@@ -967,7 +965,7 @@
pre.sh_sourceCode .sh_attribute { color: #006400; }
</style><link href="./extra.css" rel="stylesheet" type="text/css" charset="utf-8"><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css" charset="utf-8"></head>
- <body style="display: inherit; "><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">PROV-N: The Provenance Notation</h1><h2 id="subtitle"><a href="diff-n.html"><span class="insert">Diffs</span></a><span class="insert"> since LC Release </span></h2><h2 id="w3c-editor-s-draft-16-october-2012"><acronym title="World Wide Web Consortium">W3C</acronym> <span class="delete">Working</span><span class="insert">Editor's</span> Draft <span class="delete">24 July</span><span class="insert">16 October</span> 2012</h2><dl><dt>This version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-n-20120724/</span><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html</span></a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html</a></dd><dt>Previous version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-n-20120503/</span><span class="delete"> (</span><span class="delete">color-coded diffs</span><span class="delete">)</span><a href="http://www.w3.org/TR/2012/WD-prov-n-20120724/"><span class="insert">http://www.w3.org/TR/2012/WD-prov-n-20120724/</span></a></dd><dt>Editors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
+ <body style="display: inherit; "><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">PROV-N: The Provenance Notation</h1><h2 id="subtitle"><a href="diff-n.html"><span class="insert">Diffs</span></a><span class="insert"> since LC Release </span></h2><h2 id="w3c-editor-s-draft-30-october-2012"><acronym title="World Wide Web Consortium">W3C</acronym> <span class="delete">Working</span><span class="insert">Editor's</span> Draft <span class="delete">24 July</span><span class="insert">30 October</span> 2012</h2><dl><dt>This version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-n-20120724/</span><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html</span></a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html</a></dd><dt>Previous version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-n-20120503/</span><span class="delete"> (</span><span class="delete">color-coded diffs</span><span class="delete">)</span><a href="http://www.w3.org/TR/2012/WD-prov-n-20120724/"><span class="insert">http://www.w3.org/TR/2012/WD-prov-n-20120724/</span></a></dd><dt>Editors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
<dd><a href="http://www.cs.ncl.ac.uk/people/Paolo.Missier">Paolo Missier</a>, Newcastle University</dd>
<dt><span class="delete">Contributors:</span><span class="insert">Authors:</span></dt><dd><a href="http://homepages.inf.ed.ac.uk/jcheney/">James Cheney</a>, University of Edinburgh</dd>
<dd><a href="http://soiland-reyes.com/stian/">Stian Soiland-Reyes</a>, University of Manchester</dd>
@@ -1336,7 +1334,7 @@
<h3><span class="secno">2.5 </span>Identifiers and attributes</h3>
<p>Almost all expressions defined in the grammar include an identifier (see <a href="#expression-identifier">Section 3.7.1</a> for the full syntax of identifiers). Most expressions
-can aslo include a set of attribute-value pairs, delimited by square brackets. Identifiers are optional except for Entities, Activites, and Agents. Identifiers are always the first term in any expression. Optional identifiers <em class="rfc2119" title="must">must</em> be separated using a semi-colon ';', but where the identifiers are required, a regular comma ',' <em class="rfc2119" title="must">must</em> be used. This makes it possible to completely omit an optional identifier with no ambiguity arising. Also, if the set of attribute-value pairs is present, it is always the last term in any expression.</p>
+can aslo include a set of attribute-value pairs, delimited by square brackets. Identifiers are optional except for Entities, Activites, and Agents. Identifiers are always the first term in any expression. <em>Optional</em> identifiers <em class="rfc2119" title="must">must</em> be separated using a semi-colon ';', but where the identifiers are required, a regular comma ',' <em class="rfc2119" title="must">must</em> be used. This makes it possible to completely omit an optional identifier with no ambiguity arising. Also, if the set of attribute-value pairs is present, it is always the last term in any expression.</p>
<div class="anexample" id="example_9"><div class="anexampleTitle"><a class="internalDFN" href="#example_9">Example 9</a></div>
<p>Derivation has an optional identifier. In the first expression, the identifier is not available, while it is explicit in the second. The third example shows that one can optionally indicate the missing identifier using the <span class="name">-</span> marker. This is equivalent to the first expression. </p>
@@ -1389,7 +1387,10 @@
<div id="expression-Entity" class="section">
<h4><span class="secno">3.1.1 </span>Entity</h4>
-<div class="withPn">
+
+
+
+
<p>
@@ -1428,7 +1429,7 @@
-</div></div>
+</div>
<div id="expression-Activity" class="section">
<h4><span class="secno">3.1.2 </span>Activity</h4>
@@ -1483,7 +1484,14 @@
<h4><span class="secno">3.1.3 </span>Generation</h4>
-<div class="withPn">
+
+
+
+
+
+
+
+
@@ -1534,7 +1542,7 @@
-</div></div>
+</div>
<div id="expression-Usage" class="section">
<h4><span class="secno">3.1.4 </span>Usage</h4>
@@ -1759,7 +1767,10 @@
<h4><span class="secno">3.1.8 </span>Invalidation</h4>
-<div class="withPn">
+
+
+
+
@@ -1812,7 +1823,7 @@
-</div></div>
+</div>
@@ -1954,7 +1965,9 @@
</pre>
<p>Here, the derivation is provided with a <span class="name">prov:type</span> attribute and value <span class="name">prov:PrimarySource</span>.
-</p></div>
+
+ </p>
+</div>
</div>
@@ -2248,7 +2261,7 @@
<p><span class="insert">The following table summarizes how each constituent of a PROV-DM bundle maps to a PROV-N syntax element.</span></p>
<div style="text-align: left; ">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<tbody><tr><td><b><a href="http://www.w3.org/TR/prov-dm/#dfn-bundle"><span class="insert">Bundle</span></a></b></td><td><b><span class="insert">Non-Terminal</span></b></td></tr>
+<tbody><tr><td><b><a href="http://www.w3.org/TR/prov-dm/#dfn-bundle-constructor"><span class="insert">Bundle</span></a></b></td><td><b><span class="insert">Non-Terminal</span></b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
<tr><td><a href="http://www.w3.org/TR/prov-dm/#bundle.constructor.id"><span class="attribute" id="bundle.id"><span class="insert">id</span></span></a></td><td><code class="content"><a class="grammarRef" href="#prod-optionalIdentifier"><span class="insert">optionalIdentifier</span></a></code></td></tr>
@@ -2680,7 +2693,7 @@
<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-literal" name="prod-literal"></a>[<span class="prodNo">42</span>] </td> <td><code class="production prod">literal</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-typedLiteral">typedLiteral</a></span><br> | <span class="prod"><a class="grammarRef" href="#prod-convenienceNotation">convenienceNotation</a></span></code></td> </tr> </tbody>
<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-typedLiteral" name="prod-typedLiteral"></a>[<span class="prodNo">43</span>] </td> <td><code class="production prod">typedLiteral</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-STRING_LITERAL">STRING_LITERAL</a></span> "%%" <span class="prod"><a class="grammarRef" href="#prod-datatype">datatype</a></span></code></td> </tr> </tbody>
<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-datatype" name="prod-datatype"></a>[<span class="prodNo">44</span>] </td> <td><code class="production prod">datatype</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></span></code></td> </tr> </tbody>
-<tbody><tr valign="baseline"><td></td><td></td><td></td></tr></tbody>
+
<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-convenienceNotation" name="prod-convenienceNotation"></a>[<span class="prodNo">45</span>] </td> <td><code class="production prod">convenienceNotation</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-STRING_LITERAL">STRING_LITERAL</a></span> (<span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rLANGTAG">LANGTAG</a></span>)?<br> | <span class="prod"><a class="grammarRef" href="#prod-INT_LITERAL">INT_LITERAL</a></span><br> | <span class="prod"><a class="grammarRef" href="#prod-QUALIFIED_NAME_LITERAL">QUALIFIED_NAME_LITERAL</a></span></code></td> </tr> </tbody>
<tbody class="term"> <tr valign="baseline"> <td><a id="prod-STRING_LITERAL" name="prod-STRING_LITERAL"></a>[<span class="prodNo"><span class="delete">67</span><span class="insert">60</span></span>] </td> <td><<code class="production term">STRING_LITERAL</code>></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rSTRING_LITERAL2">STRING_LITERAL2</a></span><br> | <span class="prod"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rSTRING_LITERAL_LONG2">STRING_LITERAL_LONG2</a></span></code></td> </tr> </tbody>
<tbody class="term"> <tr valign="baseline"> <td><a id="prod-INT_LITERAL" name="prod-INT_LITERAL"></a>[<span class="prodNo"><span class="delete">69</span><span class="insert">62</span></span>] </td> <td><<code class="production term">INT_LITERAL</code>></td> <td> ::= </td> <td><code class="content">("-")? (<span class="prod"><a class="grammarRef" href="#prod-DIGIT">DIGIT</a></span>)+</code></td> </tr> </tbody>
@@ -2828,7 +2841,7 @@
<span class="delete">
the scope of a namespace declaration directly occurring in a</span> <code><a class="grammarRef" href="#prod-bundle"><span class="delete">toplevel </span>bundle</a></code> <span class="insert">itself.</span></li>
<li><span class="insert">
-The scope of a namespace declaration directly occurring in a </span><code><a class="grammarRef" href="#prod-document"><span class="insert">document</span></a></code> is<span class="insert"> the </span><code><a class="grammarRef" href="#prod-document"><span class="insert">document</span></a></code><span class="insert"> itself, exclunding</span> the <code><a class="grammarRef" href="#prod-bundle"><span class="delete">toplevel bundle</span><span class="delete"> itself, except and </span><span class="delete">namedBundle</span><span class="insert">bundles</span></a></code> it may contain.</li>
+The scope of a namespace declaration directly occurring in a </span><code><a class="grammarRef" href="#prod-document"><span class="insert">document</span></a></code> is<span class="insert"> the </span><code><a class="grammarRef" href="#prod-document"><span class="insert">document</span></a></code><span class="insert"> itself, excluding</span> the <code><a class="grammarRef" href="#prod-bundle"><span class="delete">toplevel bundle</span><span class="delete"> itself, except and </span><span class="delete">namedBundle</span><span class="insert">bundles</span></a></code> it may contain.</li>
</ul>
<p>A set of namespace declarations <code><a class="grammarRef" href="#prod-namespaceDeclarations">namespaceDeclarations</a></code> <em class="rfc2119" title="must not">must not</em> re-declare the same prefix.</p>
@@ -2881,8 +2894,8 @@
<div id="semantic-rules-summary" class="section">
<h4><span class="secno">3.7.5 </span>Summary of additional semantic rules</h4>
-Some of the grammar productions allow for expressions that are syntactically correct, and yet according to [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] they are not acceptable, because additional semantic rules are defined for those expressions.
- The following table provides a summary of such expressions along with examples of syntactically correct but unacceptable forms, and the additional semantic rules.<p></p>
+<p>Some of the grammar productions allow for expressions that are syntactically correct, and yet according to [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] they are not acceptable, because additional semantic rules are defined for those expressions.
+ The following table provides a summary of such expressions along with examples of syntactically correct but unacceptable forms, and the additional semantic rules.</p>
<div style="text-align: left;">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
@@ -2899,7 +2912,8 @@
<tr><td><a class="grammarRef" href="#prod-usageExpression">Usage expression</a></td>
<td><span class="name">used(a2, -, -)</span><br><span class="name">used(-; a2, -, -)</span></td>
<td>At least one of <a href="http://www.w3.org/TR/prov-dm/#usage.id"><span class="attribute">id</span></a>, <a href="http://www.w3.org/TR/prov-dm/#usage.entity"><span class="attribute">entity</span></a>, <a href="http://www.w3.org/TR/prov-dm/#usage.time"><span class="attribute">time</span></a>, and <a href="http://www.w3.org/TR/prov-dm/#usage.attributes"><span class="attribute">attributes</span></a> <em class="rfc2119" title="must">must</em> be present</td>
-</tr><tr>
+</tr>
+<tr>
<td><a class="grammarRef" href="#prod-startExpression">Start expression</a></td>
<td> <span class="name">wasStartedBy(e2, -, -, -)</span><br><span class="name">wasStartedBy(-; e2, -, -, -)</span></td>
<td>At least one of <a href="http://www.w3.org/TR/prov-dm/#start.id"><span class="attribute">id</span></a>, <a href="http://www.w3.org/TR/prov-dm/#start.trigger"><span class="attribute">trigger</span></a>, <a href="http://www.w3.org/TR/prov-dm/#start.starter"><span class="attribute">starter</span></a>, <a href="http://www.w3.org/TR/prov-dm/#start.time"><span class="attribute">time</span></a>, and <a href="http://www.w3.org/TR/prov-dm/#start.attributes"><span class="attribute">attributes</span></a> <em class="rfc2119" title="must">must</em> be present</td>
@@ -2999,13 +3013,17 @@
<h2><span class="secno">5. </span>Extensibility</h2>
<p>The PROV data model is extensible by means of attributes <span class="name">prov:type</span> and <span class="name">prov:role</span> allowing subtyping of expressions. For some applications, novel syntax may also be convenient. Hence, the normative requirements are as follow.
-</p><ul>
+</p>
+<ul>
<li> PROV-N compliant parsers <em class="rfc2119" title="must">must</em> be able to parse expressions matching the <code class="content"><a class="grammarRef" href="#prod-extensibilityExpression">extensibilityExpression</a></code> production defined below.
</li><li> As PROV provides no definition for these expressions, PROV compliant implementations
<em class="rfc2119" title="may">may</em> ignore these expressions.</li>
<li> Extensions to PROV and PROV-N <em class="rfc2119" title="may">may</em> specify more specific productions and interpretations for these expressions, which applications <em class="rfc2119" title="may">may</em> adopt to follow. </li>
</ul>
-<p></p>
+
+
+
+
<table class="grammar">
@@ -3024,7 +3042,7 @@
<div class="anexample" id="example_43"><div class="anexampleTitle"><a class="internalDFN" href="#example_43">Example 43</a></div>
<p>
-<a href="#component6">Collections</a> are sets of entities, whose membership can be expressed using the <span class="name">hadMember</span> relation. The following example shows how one can express membership for <em><span class="insert">dictionaries</span></em><span class="insert">, </span>an <span class="insert">illustrative </span>extension of <span class="delete">Collections, namely</span><span class="insert">Collections consisting of</span> sets of <span class="delete">key-value pairs.</span><span class="insert">key-entity pairs, where a key is a </span><a class="grammarRef" href="#prod-literal"><span class="insert">literal</span></a><span class="insert">.</span> The notation is a variation of that used for Collections membership, allowing multiple member elements to be declared, and in which the elements are pairs. The name of the relation is qualified with the extension-specific namespace <span class="name">http://example.org/dictionaries</span>.
+<a href="#component6">Collections</a> are sets of entities, whose membership can be expressed using the <span class="name">hadMember</span> relation. The following example shows how one can express membership for <em><span class="insert">dictionaries</span></em><span class="insert">, </span>an <span class="insert">illustrative </span>extension of <span class="delete">Collections, namely</span><span class="insert">Collections consisting of</span> sets of <span class="delete">key-value pairs.</span><span class="insert">key-entity pairs, where a key is a </span><code><a class="grammarRef" href="#prod-literal"><span class="insert">literal</span></a></code><span class="insert">.</span> The notation is a variation of that used for Collections membership, allowing multiple member elements to be declared, and in which the elements are pairs. The name of the relation is qualified with the extension-specific namespace <span class="name">http://example.org/dictionaries</span>.
</p>
<pre class="codeexample"> prefix dictExt <http://example.org/dictionaries>
dictExt:hadMembers(mId; d, {("k1",e1), ("k2",e2), ("k3",e3)}, [])
@@ -3076,12 +3094,12 @@
<dt>Subtype name:</dt>
<dd>provenance-notation</dd>
<dt>Required parameters:</dt>
- <dd>None</dd>
+ <dd><span class="delete">None</span><kbd><span class="insert">charset</span></kbd><span class="insert"> — the value of </span><kbd><span class="insert">charset</span></kbd> <em class="rfc2119" title="must"><span class="insert">must</span></em><span class="insert"> always be </span><kbd><span class="insert">UTF-8</span></kbd><span class="insert">.</span></dd>
<dt>Optional parameters:</dt>
- <dd><tt>charset</tt> — this parameter is mandatory. The value of <tt>charset</tt> is always <tt>UTF-8</tt>.</dd>
-
- <dt>Encoding considerations:</dt>
- <dd>The syntax of PROV-N is expressed over code points in Unicode [<cite><a class="bibref" rel="biblioentry" href="#bib-UNICODE5">UNICODE5</a></cite>]. The encoding is always UTF-8 [<cite><a class="bibref" rel="biblioentry" href="#bib-UTF-8">UTF-8</a></cite>].</dd>
+ <dd><span class="delete">charset</span><span class="delete"> — this parameter is mandatory. The value of </span><span class="delete">charset</span><span class="delete"> is always </span><span class="delete">UTF-8</span><span class="delete">.</span><span class="insert">None</span></dd>
+
+ <dt>Encoding considerations:<span class="insert"> 8bit</span></dt>
+ <dd>The syntax of PROV-N is expressed over code points in Unicode [<cite><span class="delete">UNICODE5</span><a class="bibref" rel="biblioentry" href="#bib-UNICODE"><span class="insert">UNICODE</span></a></cite>]. The encoding is always UTF-8 [<cite><a class="bibref" rel="biblioentry" href="#bib-UTF-8">UTF-8</a></cite>].</dd>
<dd>Unicode code points may also be expressed using an \uXXXX (U+0 to U+FFFF) or \UXXXXXXXX syntax (for U+10000 onwards) where X is a hexadecimal digit [0-9A-F]</dd>
<dt>Security considerations:</dt>
<dd>PROV-N is a general-purpose language for describing the provenance of things; applications may evaluate given data to infer more descriptions or to dereference URIs, invoking the security considerations of the scheme for that URI. Note in particular, the privacy issues in [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3023">RFC3023</a></cite>] section 10 for HTTP URIs. Data obtained from an inaccurate or malicious data source may lead to inaccurate or misleading conclusions, as well as the dereferencing of unintended URIs. Care must be taken to align the trust in consulted resources with the sensitivity of the intended use of the data.</dd>
@@ -3111,7 +3129,7 @@
<dd>PROV-N: The Provenance Notation, Moreau, Missier, (eds), Cheney, Soiland-Reyes
<a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a></dd>
<dt>Applications which use this media type:</dt>
- <dd>No widely deployed applications are known to use this media type. It may be used by some web services and clients consuming their data.</dd>
+ <dd><span class="delete">No widely deployed applications are known</span><span class="insert">It may be used by any application for publishing provenance information. This format is designed</span> to <span class="delete">use this media type. It may </span>be <span class="delete">used by some web services and clients consuming their data.</span><span class="insert">a human-readable form of provenance. </span></dd>
<dt>Additional information:</dt>
<dt>Magic number(s):</dt>
<dd>PROV-N documents may have the strings <span class="delete">'bundle'</span><span class="insert">'document'</span> near the beginning of the document.</dd>
@@ -3122,7 +3140,7 @@
<dt>Macintosh file type code(s):</dt>
<dd>"TEXT"</dd>
<dt>Person & email address to contact for further information:</dt>
- <dd>public-prov-comments@w3.org</dd>
+ <dd><span class="delete">public-prov-comments@w3.org</span><span class="insert">Ivan Herman, ivan@w3.org</span></dd>
<dt>Intended usage:</dt>
<dd>COMMON</dd>
<dt>Restrictions on usage:</dt>
@@ -3143,11 +3161,12 @@
<h2><span class="secno">A. </span><span class="insert">Changes since last version</span></h2><p><em><span class="insert">This section is non-normative.</span></em></p>
<p>
</p><ul>
-<p> <a href="http://www.w3.org/2011/prov/track/issues/543"><span class="insert">ISSUE-543</span></a><span class="insert">: uses key-entity pair terminology for example 43.
-</span></p><p> <a href="http://www.w3.org/2011/prov/track/issues/538"><span class="insert">ISSUE-538</span></a><span class="insert">: rephrasing of text in example 10.
-</span></p><p> <a href="http://www.w3.org/2011/prov/track/issues/547"><span class="insert">ISSUE-547</span></a><span class="insert">: aligned terminology and productions with prov-constraints document, renaming 'toplevel bundle' to 'document', and renaming 'named bundle' to 'bundle'.
-</span></p><p> <a href="http://www.w3.org/2011/prov/track/issues/496"><span class="insert">ISSUE-496</span></a><span class="insert">: For each prov-n term, added a cross-reference to corresponding prov-dm term (see table following each production). Rephrased text related to scope of a namespace declaration. Added an informative file with all productions.
-</span></p></ul>
+<li> <a href="http://www.w3.org/2011/prov/track/issues/543"><span class="insert">ISSUE-543</span></a><span class="insert">: Uses key-entity pair terminology for example 43.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/538"><span class="insert">ISSUE-538</span></a><span class="insert">: Rephrasing of text in example 10.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/547"><span class="insert">ISSUE-547</span></a><span class="insert">: Aligned terminology and productions with prov-constraints document, renaming 'toplevel bundle' to 'document', and renaming 'named bundle' to 'bundle'.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/496"><span class="insert">ISSUE-496</span></a><span class="insert">: For each prov-n term, added a cross-reference to corresponding prov-dm term (see table following each production). Rephrased text related to scope of a namespace declaration. Added an informative file with all productions.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/573"><span class="insert">ISSUE-573</span></a><span class="insert">: Updated Media Type section.
+</span></li></ul>
</div>
<div class="appendix informative section" id="acknowledgements">
@@ -3229,6 +3248,7 @@
</dd><dt id="bib-RFC3023">[RFC3023]</dt><dd>M. Murata; S. St.Laurent; D. Kohn. <a href="http://www.ietf.org/rfc/rfc3023.txt"><cite>XML Media Types</cite></a> January 2001. Internet RFC 3023. URL: <a href="http://www.ietf.org/rfc/rfc3023.txt">http://www.ietf.org/rfc/rfc3023.txt</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-UNICODE"><span class="insert">[UNICODE]</span></dt><dd><span class="insert">The Unicode Consortium. </span><a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html"><cite><span class="insert">The Unicode Standard.</span></cite></a><span class="insert">. Defined by: The Unicode Standard, Version 6.2.0, (Mountain View, CA: The Unicode Consortium, 2012. ISBN 978-1-936213-07-8) , as updated from time to time by the publication of new versions URL: </span><a href="http://www.unicode.org/unicode/standard/versions/enumeratedversions.html"><span class="insert">http://www.unicode.org/unicode/standard/versions/enumeratedversions.html</span></a>
</dd><dt id="bib-URI">[URI]</dt><dd>T. Berners-Lee; R. Fielding; L. Masinter. <a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource Identifiers (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-UTF-8">[UTF-8]</dt><dd>F. Yergeau. <a href="http://www.ietf.org/rfc/rfc3629.txt"><cite>UTF-8, a transformation format of ISO 10646</cite></a>. IETF RFC 3629. November 2003. URL: <a href="http://www.ietf.org/rfc/rfc3629.txt">http://www.ietf.org/rfc/rfc3629.txt</a>
</dd><dt id="bib-XML-NAMES">[XML-NAMES]</dt><dd>Richard Tobin; et al. <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/"><cite>Namespaces in XML 1.0 (Third Edition).</cite></a> 8 December 2009. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2009/REC-xml-names-20091208/">http://www.w3.org/TR/2009/REC-xml-names-20091208/</a>
@@ -3240,9 +3260,7 @@
</dd><dt id="bib-PROV-RDF">[PROV-RDF]</dt><dd>James Cheney<a href="http://www.w3.org/2011/prov/wiki/ProvRDF"><cite>PROV-RDF Mapping </cite></a>2012, Working in Progress. URL: <a href="http://www.w3.org/2011/prov/wiki/ProvRDF">http://www.w3.org/2011/prov/wiki/ProvRDF</a>
</dd><dt id="bib-PROV-SEM">[PROV-SEM]</dt><dd>James Cheney <a href="http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman"><cite>Formal Semantics Strawman</cite></a>. 2011, Work in progress. URL: <a href="http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman">http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman</a>
</dd><dt id="bib-PROV-XML">[PROV-XML]</dt><dd>James Cheney <a href="http://www.w3.org/2011/prov/wiki/ProvXML"><cite>PROV-XML Mapping </cite></a>2012, Working in Progress. URL: <a href="http://www.w3.org/2011/prov/wiki/ProvXML">http://www.w3.org/2011/prov/wiki/ProvXML</a>
-</dd><dt id="bib-UNICODE5">[UNICODE5]</dt><dd>The Unicode Consortium. <a href="http://www.unicode.org/versions/Unicode5.1.0/"><cite>The Unicode Standard, Version 5.1.0.</cite></a> Addison-Wesley. 2007. ISBN 0-321-48091-0. URL: <a href="http://www.unicode.org/versions/Unicode5.1.0/">http://www.unicode.org/versions/Unicode5.1.0/</a>
-</dd><dt id="bib-UNISEC">[UNISEC]</dt><dd> Mark Davis and Michel Suignard. <a href="http://www.unicode.org/reports/tr36/"><cite>Unicode Security Considerations<cite></cite></cite></a>. 4 August 2010. URL: <a href="http://www.unicode.org/reports/tr36/">http://www.unicode.org/reports/tr36/</a>
+</dd><span class="delete">[UNICODE5]</span><span class="delete">The Unicode Consortium. </span><span class="delete">The Unicode Standard, Version 5.1.0.</span><span class="delete"> Addison-Wesley. 2007. ISBN 0-321-48091-0. URL: </span><span class="delete">http://www.unicode.org/versions/Unicode5.1.0/</span>
+<dt id="bib-UNISEC">[UNISEC]</dt><dd> Mark Davis and Michel Suignard. <a href="http://www.unicode.org/reports/tr36/"><cite>Unicode Security Considerations<cite></cite></cite></a>. 4 August 2010. URL: <a href="http://www.unicode.org/reports/tr36/">http://www.unicode.org/reports/tr36/</a>
</dd></dl></div></div></body></html>
-
-
--- a/model/diff.html Wed Oct 31 13:09:26 2012 +0000
+++ b/model/diff.html Wed Oct 31 13:10:51 2012 +0000
@@ -1,3 +1,4 @@
+
<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'>
<html lang="en" dir="ltr">
<head><style type="text/css"><!--
@@ -1026,7 +1027,7 @@
pre.sh_sourceCode .sh_attribute { color: #006400; }
</style><link href="./extra-dm.css" rel="stylesheet" type="text/css" charset="utf-8"><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css" charset="utf-8"></head>
- <body style="display: inherit; "><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">PROV-DM: The PROV Data Model</h1><h2 id="subtitle"><a href="diff.html"><span class="insert">Changes</span></a><span class="insert"> since LC release</span></h2><h2 id="w3c-editor-s-draft-11-october-2012"><acronym title="World Wide Web Consortium">W3C</acronym> <span class="delete">Working</span><span class="insert">Editor's</span> Draft <span class="delete">24 July</span><span class="insert">11 October</span> 2012</h2><dl><dt>This version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120724/</span><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</span></a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</a></dd><dt>Previous version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120503/</span><span class="delete"> (</span><span class="delete">color-coded diffs</span><span class="delete">)</span><a href="http://www.w3.org/TR/2012/WD-prov-dm-20120724/"><span class="insert">http://www.w3.org/TR/2012/WD-prov-dm-20120724/</span></a></dd><dt>Editors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
+ <body style="display: inherit; "><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">PROV-DM: The PROV Data Model</h1><h2 id="subtitle"><a href="diff.html"><span class="insert">Changes</span></a><span class="insert"> since LC release</span></h2><h2 id="w3c-editor-s-draft-30-october-2012"><acronym title="World Wide Web Consortium">W3C</acronym> <span class="delete">Working</span><span class="insert">Editor's</span> Draft <span class="delete">24 July</span><span class="insert">30 October</span> 2012</h2><dl><dt>This version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120724/</span><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</span></a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</a></dd><dt>Previous version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120503/</span><span class="delete"> (</span><span class="delete">color-coded diffs</span><span class="delete">)</span><a href="http://www.w3.org/TR/2012/WD-prov-dm-20120724/"><span class="insert">http://www.w3.org/TR/2012/WD-prov-dm-20120724/</span></a></dd><dt>Editors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
<dd><a href="http://www.cs.ncl.ac.uk/people/Paolo.Missier">Paolo Missier</a>, Newcastle University</dd>
<dt><span class="delete">Contributors:</span><span class="insert">Authors:</span></dt><dd><a href="http://semanticweb.org/wiki/Khalid_Belhajjame">Khalid Belhajjame</a>, University of Manchester</dd>
<dd><span>Reza B'Far</span>, Oracle Corporation</dd>
@@ -1503,7 +1504,9 @@
</div>
-<p>
+<p><span class="insert">
+The focus of derivation is on connecting a generated entity to a used
+entity.</span>
While the basic idea is simple, the concept of derivation can be quite
subtle: implicit is the notion that the generated entity was affected
in some way by the used entity.
@@ -1653,9 +1656,16 @@
<p><a class="section-ref" href="#core-structures"><span>Section 2.1</span></a> shows that seven concepts are mapped to binary relations in the core of PROV. However, some advanced uses of these concepts cannot be captured by a binary relation, but require relations to be expanded to n-ary relations.</p>
-<p>To illustrate expanded relations, we consider the concept of
-association, described
-in <a class="section-ref" href="#section-agents-attribution-association-delegation"><span>Section 2.1.3</span></a>. Agents may adopt <em>plans</em>, i.e. sets of actions or steps, to achieve their
+
+
+<p><span class="insert">Indeed, binary relations are actually shorthands that can be 'opened up' by applications and filled in with further application details. For example, derivation is a very high level relationship between two entities: an application may decide to 'open up' that relationship in an expanded relation that describes how an entity was derived from another by virtue of listing the generation, usage, and activity involved in the 'WasDerivedFrom' relationship. Applications are free to decide which level of granularity they want describe, and PROV gives them the way to do that.</span></p>
+
+
+
+<p>To illustrate expanded relations, we <span class="delete">consider</span><span class="insert">revisit</span> the concept of
+association, <span class="delete">described</span><span class="insert">introduced</span>
+in <a class="section-ref" href="#section-agents-attribution-association-delegation"><span>Section 2.1.3</span></a><span class="delete">.</span><span class="insert"> (full definition of the expanded association can be found
+in </span><a class="section-ref" href="#term-Association"><span><span class="insert">Section 5.3.3</span></span></a><span class="insert">).</span> Agents may <span class="delete">adopt</span><span class="insert">rely on</span> <em>plans</em>, i.e. sets of actions or steps, to achieve their
goals in the context of an activity.
Hence, an expanded form of
association relation allows for a plan to be specified. Plan is defined by subtyping and
@@ -1752,7 +1762,7 @@
<h4><span class="secno">2.2.3 </span>Collections</h4>
<p>
-<span class="glossary-ref"> A <span class="dfn">collection</span> is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be <span class="dfn">member of</span> the collections. </span> Many different types of collections exist, such as <em>sets</em>, <em>dictionaries</em>, or <em>lists</em>.
+<span class="glossary-ref"> A <span class="dfn">collection</span> is an entity that provides a structure to some <span class="delete">constituents, which are</span><span class="insert">constituents that must</span> themselves<span class="insert"> be</span> entities. These constituents are said to be <span class="dfn">member of</span> the collections. </span> Many different types of collections exist, such as <em>sets</em>, <em>dictionaries</em>, or <em>lists</em>.
Using Collections, one can express the provenance of the collection itself in addition to that of the members. </p>
<div class="anexample conceptexample" id="collection-example"><div class="anexampleTitle">Example <span class="delete">14</span><span class="insert">15</span><sup><a class="internalDFN" href="#collection-example"><span class="diamond"> ◊</span></a></sup></div>
@@ -1829,19 +1839,21 @@
<div class="anexample" id="anexample-prov-n"><div class="anexampleTitle">Example <span class="delete">15</span><span class="insert">16</span><sup><a class="internalDFN" href="#anexample-prov-n"><span class="diamond"> ◊</span></a></sup></div>
<p>
An activity with identifier <span class="name">a1</span> and an attribute <span class="name">type</span> with value <span class="name">createFile</span>.
-</p><pre class="codeexample">activity(a1, [prov:type="createFile"])
+</p><pre class="codeexample">activity(a1, <span class="delete">[prov:type="createFile"])</span><span class="insert">[ prov:type="createFile" ])</span>
</pre>
Two entities with identifiers <span class="name">e1</span> and <span class="name">e2</span>.
<pre class="codeexample">entity(e1)
entity(e2)
</pre>
The activity <span class="name">a1</span> used <span class="name">e1</span>, and <span class="name">e2</span> was generated by <span class="name">a1</span>.
-<pre class="codeexample">used(a1,e1)
-wasGeneratedBy(e2,a1)
+<pre class="codeexample"><span class="delete">used(a1,e1)
+wasGeneratedBy(e2,a1)</span><span class="insert">used(a1, e1)
+wasGeneratedBy(e2, a1)</span>
</pre>
The same descriptions, but with an explicit identifier <span class="name">u1</span> for the usage, and the syntactic marker '<span class="name">-</span>' to mark the absence of identifier in the generation. Both are followed by '<span class="name">;</span>'.
-<pre class="codeexample">used(u1;a1,e1)
-wasGeneratedBy(-;e2,a1)
+<pre class="codeexample"><span class="delete">used(u1;a1,e1)
+wasGeneratedBy(-;e2,a1)</span><span class="insert">used(u1; a1, e1)
+wasGeneratedBy(-; e2, a1)</span>
</pre>
</div>
@@ -1897,11 +1909,11 @@
</li>
<li>There was an editing activity.
-<pre>activity(ex:edit1,[prov:type="edit"])
+<pre><span class="delete">activity(ex:edit1,[prov:type="edit"])</span><span class="insert">activity(ex:edit1, [ prov:type="edit" ])</span>
</pre>
</li>
-<li>The document was generated by the editing activity: this was a <a title="concept-generation">Generation</a>.
+<li>The document was generated by the editing activity: this was a <a title="concept-generation">Generation</a>.<span class="insert"> Its time is not specified, hence, the marker '-'.</span>
<pre>wasGeneratedBy(tr:WD-prov-dm-20111215, ex:edit1, -)
</pre>
</li>
@@ -1913,7 +1925,7 @@
</pre>
</li>
-<li>Agents were assigned various responsibilities in the editing activity: contributor and editor.
+<li>Agents were assigned various responsibilities in the editing activity: contributor and editor.<span class="insert"> The plan the agent relied upon is not specified, hence, the marker '-'.</span>
<pre>wasAssociatedWith(ex:edit1, ex:Paolo, -, [ prov:role="editor" ])
wasAssociatedWith(ex:edit1, ex:Simon, -, [ prov:role="contributor" ])
</pre>
@@ -1983,11 +1995,11 @@
</pre>
</li>
<li>There was a publication activity.
-<pre>activity(ex:act2,[prov:type="publish"])
+<pre><span class="delete">activity(ex:act2,[prov:type="publish"])</span><span class="insert">activity(ex:act2, [ prov:type="publish" ])</span>
</pre>
</li>
-<li>The document was generated by the publication activity: this was a <a title="concept-Generation">Generation</a>.
+<li>The document was generated by the publication activity: this was a <a title="concept-Generation">Generation</a>.<span class="insert"> Its time is not specified, hence, the marker '-'.</span>
<pre>wasGeneratedBy(tr:WD-prov-dm-20111215, ex:act2, -)
</pre>
</li>
@@ -1998,7 +2010,7 @@
</pre>
</li>
-<li>The activity required a publication request: this was a <a title="concept-Usage">Usage</a>.
+<li>The activity required a publication request: this was a <a title="concept-Usage">Usage</a>.<span class="insert"> Its time is not specified, hence, the marker '-'.</span>
<pre>used(ex:act2, email:2011Dec/0111, -)
</pre>
</li>
@@ -2053,10 +2065,10 @@
<p>To express their respective provenance, these bundles must be seen as entities, and all PROV constructs are now available to express their provenance. In the example below, <span class="name">ex:author-view</span> is attributed to the agent <span class="name">ex:Simon</span>, whereas <span class="name">ex:process-view</span> to <span class="name">w3:Consortium</span>.
-</p><pre class="codeexample">entity(ex:author-view, [prov:type='prov:Bundle' ])
+</p><pre class="codeexample">entity(ex:author-view, <span class="delete">[prov:type='prov:Bundle'</span><span class="insert">[ prov:type='prov:Bundle'</span> ])
wasAttributedTo(ex:author-view, ex:Simon)
-entity(ex:process-view, [prov:type='prov:Bundle' ])
+entity(ex:process-view, <span class="delete">[prov:type='prov:Bundle'</span><span class="insert">[ prov:type='prov:Bundle'</span> ])
wasAttributedTo(ex:process-view, w3:Consortium)
</pre>
@@ -2143,11 +2155,11 @@
<div id="secondary-elements-relations-at-a-glance-div" style="text-align: center;">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<caption id="secondary-elements-relations-at-a-glance"><span><span class="insert">Table 5</span><sup><a class="internalDFN" href="#secondary-elements-relations-at-a-glance"><span class="diamond"><span class="insert"> ◊:</span></span></a></sup> </span><span class="insert">Secondary optional elements in PROV-DM Relations</span></caption>
-<tbody><tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td colspan="6"><span class="insert">Secondary Object</span></td></tr>
+<tbody><tr><td style="border-width: 0px; "></td><td style="border-width: 0px;§> "></td><td colspan="6"><span class="insert">Secondary Object</span></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td><span class="insert">Entity</span></td><td><span class="insert">Activity</span></td><td><span class="insert">Agent</span></td></tr>
-<tr><td rowspan="3"><span class="insert">Subject</span></td><td><span class="insert">Entity</span></td><td class="component5-color"><a href="#dfn-mentionof" class="internalDFN"><span class="insert">MentionOf</span></a><span class="insert"> (bundle)</span></td><td class="component2-color"><a href="#dfn-wasderivedfrom" class="internalDFN"><span class="insert">WasDerivedFrom</span></a><span class="insert"> (activity)</span><br><a><span class="insert">Revision (activity)</span></a><br><a><span class="insert">Quotation (activity)</span></a><br><a><span class="insert">PrimarySource (activity)</span></a></td><td colspan="2"><span class="insert">—</span></td></tr>
-<tr><td><span class="insert">Activity</span></td><td class="component3-color"><a href="#dfn-wasassociatedwith" class="internalDFN"><span class="insert">WasAssociatedWith</span></a><span class="insert"> (plan)</span></td><td class="component1-color"><a href="#dfn-wasstartedby" class="internalDFN"><span class="insert">WasStartedBy</span></a><span class="insert"> (starter)</span><br><a href="#dfn-wasendedby" class="internalDFN"><span class="insert">WasEndedBy</span></a><span class="insert"> (ender)</span></td><td colspan="2"><span class="insert">—</span></td></tr>
-<tr><td><span class="insert">Agent</span></td><td><span class="insert">—</span></td><td class="component3-color"><a href="#dfn-actedonbehalfof" class="internalDFN"><span class="insert">ActedOnBehalfOf</span></a><span class="insert"> (activity)</span></td><td><span class="insert">—</span></td></tr>
+<tr><td rowspan="3"><span class="insert">Subject</span></td><td><span class="insert">Entity</span></td><td class="component5-color"><a href="#dfn-mentionof" class="internalDFN"><span class="insert">MentionOf</span></a><span class="insert"> (</span><a href="#mention.bundle"><span class="insert">bundle</span></a><span class="insert">)</span></td><td class="component2-color"><a href="#dfn-wasderivedfrom" class="internalDFN"><span class="insert">WasDerivedFrom</span></a><span class="insert"> (</span><a href="#derivation.activity"><span class="insert">activity</span></a><span class="insert">)</span></td><td colspan="2"><span class="insert">—</span></td></tr>
+<tr><td><span class="insert">Activity</span></td><td class="component3-color"><a href="#dfn-wasassociatedwith" class="internalDFN"><span class="insert">WasAssociatedWith</span></a><span class="insert"> (</span><a href="#association.plan"><span class="insert">plan</span></a><span class="insert">)</span></td><td class="component1-color"><a href="#dfn-wasstartedby" class="internalDFN"><span class="insert">WasStartedBy</span></a><span class="insert"> (</span><a href="#start.starter"><span class="insert">starter</span></a><span class="insert">)</span><br><a href="#dfn-wasendedby" class="internalDFN"><span class="insert">WasEndedBy</span></a><span class="insert"> (</span><a href="#end.ender"><span class="insert">ender</span></a><span class="insert">)</span></td><td colspan="2"><span class="insert">—</span></td></tr>
+<tr><td><span class="insert">Agent</span></td><td><span class="insert">—</span></td><td class="component3-color"><a href="#dfn-actedonbehalfof" class="internalDFN"><span class="insert">ActedOnBehalfOf</span></a><span class="insert"> (</span><a href="#delegation.activity"><span class="insert">activity</span></a><span class="insert">)</span></td><td><span class="insert">—</span></td></tr>
</tbody></table>
</div>
@@ -2242,7 +2254,7 @@
<p></p><div class="attributes" id="attributes-entity">An <dfn title="dfn-Entity" id="dfn-entity" class="internalDFN">entity</dfn><sup><a class="internalDFN" href="#dfn-entity"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression" id="pn-entity">entity(id, [attr1=val1, ...])</span> in PROV-N, </span> has:
<ul>
<li><span class="attribute" id="entity.id">id</span>: an identifier for an entity; </li>
-<li><span class="attribute" id="entity.attributes">attributes</span>: an <em class="rfc2119" title="optional">optional</em> set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this entity.</li>
+<li><span class="attribute" id="entity.attributes">attributes</span>: an <em class="rfc2119" title="optional">optional</em> set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about <span class="insert">the fixed aspects of </span>this entity.</li>
</ul></div>
<div class="anexample" id="anexample-entity"><div class="anexampleTitle">Example <span class="delete">16</span><span class="insert">17</span><sup><a class="internalDFN" href="#anexample-entity"><span class="diamond"> ◊</span></a></sup></div>
@@ -2276,7 +2288,7 @@
<div class="anexample" id="anexample-activity"><div class="anexampleTitle">Example <span class="delete">17</span><span class="insert">18</span><sup><a class="internalDFN" href="#anexample-activity"><span class="diamond"> ◊</span></a></sup></div>
<p>
The following expression</p>
-<pre class="codeexample">activity(a1,2011-11-16T16:05:00,2011-11-16T16:06:00,
+<pre class="codeexample"><span class="delete">activity(a1,2011-11-16T16:05:00,2011-11-16T16:06:00,</span><span class="insert">activity(a1, 2011-11-16T16:05:00, 2011-11-16T16:06:00,</span>
[ ex:host="server.example.org", prov:type='ex:edit' ])
</pre>
<p>states the existence of an activity with identifier <span class="name">a1</span>, start time <span class="name">2011-11-16T16:05:00</span>, and end time <span class="name">2011-11-16T16:06:00</span>, running on host <span class="name">server.example.org</span>, and of type <span class="name">edit</span>. The attribute <span class="name">host</span> is application specific (declared in some namespace with prefix <span class="name">ex</span>). The attribute <span class="name">type</span> is a reserved attribute of PROV-DM, allowing for sub-typing to be expressed (see <a href="#term-attribute-type">Section 5.7.4.4</a>).</p>
@@ -2299,6 +2311,9 @@
<div class="glossary-ref"> <dfn id="concept-generation" class="internalDFN">Generation</dfn><sup><a class="internalDFN" href="#concept-generation"><span class="diamond"> ◊</span></a></sup> is the completion of production of a new entity by an activity. This entity did not exist before generation and becomes available for usage after this generation. </div>
+<p><span class="insert">Given that a generation is the completion of production of an entity,
+it is instantaneous.</span></p>
+
<p>
</p><div class="attributes" id="attributes-generation"><dfn title="wasGeneratedBy" id="dfn-wasgeneratedby" class="internalDFN">Generation</dfn><sup><a class="internalDFN" href="#dfn-wasgeneratedby"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression">wasGeneratedBy(id; e, a, t, attrs)</span> in PROV-N,</span> has:
<ul>
@@ -2346,6 +2361,11 @@
<p><span class="glossary-ref"> <dfn id="concept-usage" class="internalDFN">Usage</dfn><sup><a class="internalDFN" href="#concept-usage"><span class="diamond"> ◊</span></a></sup> is the beginning of utilizing an entity by an activity. Before usage, the activity had not begun to utilize this entity and could not have been affected by the entity. </span> (Note: This definition is formulated for a given usage; it is permitted for an activity to have used a same entity multiple times.)</p>
+
+
+<p><span class="insert">Given that a usage is the beginning of utilizing an entity, it is
+instantaneous.</span></p>
+
<p></p><div class="attributes" id="attributes-usage"><dfn title="used" id="dfn-used" class="internalDFN">Usage</dfn><sup><a class="internalDFN" href="#dfn-used"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression">used(id; a, e, t, attrs)</span> in PROV-N,</span> has:
<ul>
<li><span class="attribute" id="usage.id">id</span>: an <em class="rfc2119" title="optional">optional</em> identifier for a usage;</li>
@@ -2420,6 +2440,11 @@
<div class="glossary-ref"> <dfn id="concept-start" class="internalDFN">Start</dfn><sup><a class="internalDFN" href="#concept-start"><span class="diamond"> ◊</span></a></sup> is when an activity is deemed to have started. The activity did not exist before its start. Any usage or generation involving an activity follows the activity's start. A start may refer to an entity, known as <dfn id="concept-start-trigger" class="internalDFN">trigger</dfn><sup><a class="internalDFN" href="#concept-start-trigger"><span class="diamond"> ◊</span></a></sup>, that set off the activity, or to an activity, known as <dfn id="concept-start-starter" class="internalDFN">starter</dfn><sup><a class="internalDFN" href="#concept-start-starter"><span class="diamond"> ◊</span></a></sup>, that generated the trigger. </div>
+
+
+<p><span class="insert">Given that a start is when an activity is deemed to have started, it
+is instantaneous.</span></p>
+
<p></p><div class="attributes" id="attributes-start">An activity <dfn title="wasStartedBy" id="dfn-wasstartedby" class="internalDFN">start</dfn><sup><a class="internalDFN" href="#dfn-wasstartedby"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression">wasStartedBy(id; a2, e, a1, t, attrs)</span> in PROV-N,</span> has:
<ul>
<li><span class="attribute" id="start.id">id</span>: an <em class="rfc2119" title="optional">optional</em> identifier for the activity start;</li>
@@ -2495,6 +2520,11 @@
<div class="glossary-ref"> <dfn id="concept-end" class="internalDFN">End</dfn><sup><a class="internalDFN" href="#concept-end"><span class="diamond"> ◊</span></a></sup> is when an activity is deemed to have ended. The activity no longer exists after its end. Any usage, generation, or invalidation involving an activity precedes the activity's end. An end may refer to an entity, known as <dfn id="concept-end-trigger" class="internalDFN">trigger</dfn><sup><a class="internalDFN" href="#concept-end-trigger"><span class="diamond"> ◊</span></a></sup>, that terminated the activity, or to an activity, known as <dfn id="concept-end-ender" class="internalDFN">ender</dfn><sup><a class="internalDFN" href="#concept-end-ender"><span class="diamond"> ◊</span></a></sup> that generated the trigger. </div>
+
+
+<p><span class="insert">Given that an end is when an activity is deemed to have ended, it is
+instantaneous.</span></p>
+
<p></p><div class="attributes" id="attributes-end">An activity <dfn title="wasEndedBy" id="dfn-wasendedby" class="internalDFN">end</dfn><sup><a class="internalDFN" href="#dfn-wasendedby"><span class="diamond"> ◊</span></a></sup><span class="withAsn">, written <span class="pnExpression">wasEndedBy(id; a2, e, a1, t, attrs)</span> in PROV-N,</span> has:
<ul>
<li><span class="attribute" id="end.id">id</span>: an <em class="rfc2119" title="optional">optional</em> identifier for the activity end;</li>
@@ -2527,6 +2557,11 @@
+
+
+<p><span class="insert">Given that an invalidation is the start of destruction, cessation, or
+expiry, it is instantaneous.</span></p>
+
<p>
Entities have a duration. Generation marks the beginning of an entity, whereas invalidation marks its end.
An entity's lifetime can end for different reasons:</p>
@@ -2660,7 +2695,7 @@
<p>According to <a href="#section-prov-overview">Section 2</a>, for an entity to be transformed from, created from, or resulting from an update to another, there must be some
-underpinning activities performing the necessary actions resulting in such a derivation.
+underpinning <span class="insert">activity or </span>activities performing the necessary <span class="delete">actions</span><span class="insert">action(s)</span> resulting in such a derivation.
A derivation can be described at various levels of precision. In its simplest form, derivation relates two entities. Optionally, attributes can be added to represent further information about the derivation. If the derivation is the result of a single known activity, then this activity can also be optionally expressed. To provide a completely accurate description of the derivation, the generation and usage of the generated and used entities, respectively, can be provided, so as to make the derivation path, through usage, activity, and generation, explicit. Optional information such as activity, generation, and usage can be linked to derivations to aid analysis of provenance and to facilitate provenance-based reproducibility. </p>
@@ -2861,6 +2896,9 @@
<div class="glossary-ref"> An <dfn id="concept-agent" class="internalDFN">agent</dfn><sup><a class="internalDFN" href="#concept-agent"><span class="diamond"> ◊</span></a></sup> is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity. </div>
+<p><span class="insert">An agent may be a particular type of entity or activity. This means that the model can be
+ used to express provenance of the agents themselves. </span></p>
+
<p></p><div class="attributes" id="attributes-agent">An <dfn title="dfn-agent" id="dfn-agent" class="internalDFN">agent</dfn><sup><a class="internalDFN" href="#dfn-agent"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression" id="pn-agent">agent(id, [attr1=val1, ...])</span> in PROV-N,</span> has:
<ul>
@@ -2956,7 +2994,7 @@
<li><span class="attribute" id="association.id">id</span>: an <em class="rfc2119" title="optional">optional</em> identifier for the association between an activity and an agent;</li>
<li><span class="attribute" id="association.activity">activity</span>: an identifier (<span class="name">a</span>) for the activity;</li>
<li><span class="attribute" id="association.agent">agent</span>: an <em class="rfc2119" title="optional">optional</em> identifier (<span class="name">ag</span>) for the agent associated with the activity;</li>
-<li><span class="attribute" id="association.plan">plan</span>: an <em class="rfc2119" title="optional">optional</em> identifier (<span class="name">pl</span>) for the plan adopted by the agent in the context of this activity;
+<li><span class="attribute" id="association.plan">plan</span>: an <em class="rfc2119" title="optional">optional</em> identifier (<span class="name">pl</span>) for the plan<span class="delete"> adopted by </span> the agent<span class="insert"> relied on</span> in the context of this activity;
</li><li><span class="attribute" id="association.attributes">attributes</span>: an <em class="rfc2119" title="optional">optional</em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this association of this activity with this agent.</li>
</ul></div>
@@ -3185,7 +3223,7 @@
<p>
-A bundle description is of the form <span class="pnExpression">entity(id,[prov:type='prov:Bundle', attr1=val1, ...])</span>
+A bundle description is of the form <span class="pnExpression"><span class="delete">entity(id,[prov:type='prov:Bundle',</span><span class="insert">entity(id, [ prov:type='prov:Bundle',</span> attr1=val1, <span class="delete">...])</span><span class="insert">...] )</span></span>
where <span class="name">id</span> is an identifier denoting a bundle,
a type <span>prov:Bundle</span> and
an <em class="rfc2119" title="optional">optional</em> set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this bundle.
@@ -3230,7 +3268,7 @@
<p>The first bundle contains the descriptions corresponding to Bob observing the creation of <span class="name">ex:report1</span>. Its provenance can be described as follows.</p>
<pre class="codeexample">
-entity(bob:bundle1, [prov:type='prov:Bundle'])
+entity(bob:bundle1, <span class="delete">[prov:type='prov:Bundle'])</span><span class="insert">[ prov:type='prov:Bundle' ])</span>
wasGeneratedBy(bob:bundle1, -, 2012-05-24T10:30:00)
wasAttributedTo(bob:bundle1, ex:Bob)
</pre>
@@ -3270,6 +3308,9 @@
+
+
+
</div>
@@ -3326,6 +3367,12 @@
</div>
+
+
+<p><span class="insert">Specialization is not defined as Influence, and therefore does not have an id and attributes.</span></p>
+
+
+
<div class="anexample" id="anexample-specialization"><div class="anexampleTitle">Example <span class="delete">42</span><span class="insert">43</span><sup><a class="internalDFN" href="#anexample-specialization"><span class="diamond"> ◊</span></a></sup></div>
<p>
The BBC news home page on 2012-03-23 <span class="name">ex:bbcNews2012-03-23</span>
@@ -3354,6 +3401,10 @@
+
+
+
+
<p></p><div class="attributes" id="attributes-alternate">An <dfn title="alternateOf" id="dfn-alternateof" class="internalDFN">alternate</dfn><sup><a class="internalDFN" href="#dfn-alternateof"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression">alternateOf(e1, e2)</span> in PROV-N,</span> has:
<ul>
<li><span class="attribute" id="alternate.alternate1">alternate1</span>: an identifier (<span class="name">e1</span>) of the first of the two entities;</li>
@@ -3361,6 +3412,19 @@
</ul>
</div>
+<p><span class="insert">Alternate is not defined as Influence, and therefore does not have an id and attributes.</span></p>
+
+<p><span class="insert">
+Note that </span><a title="alternateOf" href="#dfn-alternateof" class="internalDFN"><span class="insert">alternateOf</span></a><span class="insert"> is a necessarily very general
+relationship that, in reasoning, only states that the two
+alternate entities fix different aspects of some common thing
+(possibly evolving over time), and so there is some relevant
+connection between the provenance of the alternates. In a
+specific application context, </span><a title="alternateOf" href="#dfn-alternateof" class="internalDFN"><span class="insert">alternateOf</span></a><span class="insert">, or a subtype of it,
+could allow more inferences.
+</span></p>
+
+
<div class="anexample" id="anexample-alternate"><div class="anexampleTitle">Example <span class="delete">43</span><span class="insert">44</span><sup><a class="internalDFN" href="#anexample-alternate"><span class="diamond"> ◊</span></a></sup></div>
<p>
A given news item on the BBC News site
@@ -3382,7 +3446,7 @@
Considering again the two versions of the technical report <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft). They are alternate of each other.
</p><pre class="codeexample">entity(tr:WD-prov-dm-20111018)
entity(tr:WD-prov-dm-20111215)
-alternateOf(tr:WD-prov-dm-20111018,tr:WD-prov-dm-20111215)
+<span class="delete">alternateOf(tr:WD-prov-dm-20111018,tr:WD-prov-dm-20111215)</span><span class="insert">alternateOf(tr:WD-prov-dm-20111018, tr:WD-prov-dm-20111215)</span>
</pre>
<p>They are both specialization of the page <a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a>.</p>
</div>
@@ -3430,6 +3494,11 @@
+
+
+
+
+
<p></p><div class="attributes" id="attributes-mention">A <dfn title="mentionOf" id="dfn-mentionof" class="internalDFN">mention</dfn><sup><a class="internalDFN" href="#dfn-mentionof"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression">mentionOf(infra, supra, b)</span> in PROV-N,</span> has:
<ul>
<li><span class="attribute" id="mention.specificEntity">specificEntity</span>: an identifier (<span class="name">infra</span>)
@@ -3439,6 +3508,8 @@
</ul>
</div>
+<p><span class="insert">Mention is not defined as Influence, and therefore does not have an id and attributes.</span></p>
+
<div class="anexample" id="anexample-mention-rating"><div class="anexampleTitle">Example <span class="delete">45</span><span class="insert">46</span><sup><a class="internalDFN" href="#anexample-mention-rating"><span class="diamond"> ◊</span></a></sup></div>
<p>This example is concerned with a performance rating tool that reads and processes provenance to determine the performance of agents. To keep the example simple, an agent's performance is determined by the duration of the activities it is associated with. </p>
<p>As an illustration, we consider that two bundles <span class="name">ex:run1</span> and <span class="name">ex:run2</span> refer to an agent <span class="name">ex:Bob</span> that controlled two activities <span class="name">ex:a1</span> and <span class="name">ex:a2</span>. </p>
@@ -3470,10 +3541,10 @@
<p>Consider the following bundle of descriptions, in which derivation and generations have been identified.
</p><pre class="codeexample">
bundle obs:bundle1
- entity(ex:report1, [prov:type="report", ex:version=1])
- wasGeneratedBy(ex:g1; ex:report1,-,2012-05-24T10:00:01)
- entity(ex:report2, [prov:type="report", ex:version=2])
- wasGeneratedBy(ex:g2; ex:report2,-,2012-05-25T11:00:01)
+ entity(ex:report1, <span class="delete">[prov:type="report", ex:version=1])</span><span class="insert">[ prov:type="report", ex:version=1 ])</span>
+ wasGeneratedBy(ex:g1; <span class="delete">ex:report1,-,2012-05-24T10:00:01)</span><span class="insert">ex:report1, -, 2012-05-24T10:00:01)</span>
+ entity(ex:report2, <span class="delete">[prov:type="report", ex:version=2])</span><span class="insert">[ prov:type="report", ex:version=2 ])</span>
+ wasGeneratedBy(ex:g2; <span class="delete">ex:report2,-,2012-05-25T11:00:01)</span><span class="insert">ex:report2, -, 2012-05-25T11:00:01)</span>
wasDerivedFrom(ex:report2, ex:report1)
endBundle
entity(obs:bundle1, [ prov:type='prov:Bundle' ])
@@ -3485,10 +3556,10 @@
entity(tool:bundle2, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
wasAttributedTo(tool:bundle2, viz:Visualizer)
- entity(tool:report1, [viz:color="orange"])
+ entity(tool:report1, <span class="delete">[viz:color="orange"])</span><span class="insert">[ viz:color="orange" ])</span>
mentionOf(tool:report1, ex:report1, obs:bundle1)
- entity(tool:report2, [viz:color="blue"])
+ entity(tool:report2, <span class="delete">[viz:color="blue"])</span><span class="insert">[ viz:color="blue" ])</span>
mentionOf(tool:report2, ex:report2, obs:bundle1)
endBundle
</pre>
@@ -3513,6 +3584,10 @@
+
+
+
+
</div>
<div id="component6" class="section">
@@ -3537,7 +3612,7 @@
<div id="term-collection" class="section">
<h4><span class="secno">5.6.1 </span>Collection</h4>
-<span class="glossary-ref"> A <dfn id="concept-collection" class="internalDFN">collection</dfn><sup><a class="internalDFN" href="#concept-collection"><span class="diamond"> ◊</span></a></sup> is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be <dfn id="dfn-member-of" class="internalDFN">member of</dfn><sup><a class="internalDFN" href="#dfn-member-of"><span class="diamond"> ◊</span></a></sup> the collections. </span>
+<span class="glossary-ref"> A <dfn id="concept-collection" class="internalDFN">collection</dfn><sup><a class="internalDFN" href="#concept-collection"><span class="diamond"> ◊</span></a></sup> is an entity that provides a structure to some <span class="delete">constituents, which are</span><span class="insert">constituents that must</span> themselves<span class="insert"> be</span> entities. These constituents are said to be <dfn id="dfn-member-of" class="internalDFN">member of</dfn><sup><a class="internalDFN" href="#dfn-member-of"><span class="diamond"> ◊</span></a></sup> the collections. </span>
<span class="glossary-ref"> An <dfn id="concept-empty-collection" class="internalDFN">empty collection</dfn><sup><a class="internalDFN" href="#concept-empty-collection"><span class="diamond"> ◊</span></a></sup> is a collection without members. </span>
@@ -3555,8 +3630,8 @@
<p><span class="insert">PROV defines no collection-specific attributes.</span></p>
<div class="anexample" id="example_48"><div class="anexampleTitle">Example <span class="delete">47</span><span class="insert">48</span><sup><a class="internalDFN" href="#example_48"><span class="diamond"> ◊</span></a></sup></div>
-<pre class="codeexample">entity(c0, [prov:type='prov:EmptyCollection' ]) // c0 is an empty collection
-entity(c1, [prov:type='prov:Collection' ]) // c1 is a collection, with unknown content
+<pre class="codeexample">entity(c0, <span class="delete">[prov:type='prov:EmptyCollection'</span><span class="insert">[ prov:type='prov:EmptyCollection'</span> ]) // c0 is an empty collection
+entity(c1, <span class="delete">[prov:type='prov:Collection'</span><span class="insert">[ prov:type='prov:Collection'</span> ]) // c1 is a collection, with unknown content
</pre>
</div>
@@ -3582,6 +3657,12 @@
+
+
+
+<p><span class="insert">Membership is not defined as Influence, and therefore does not have an id and attributes.</span></p>
+
+
<div class="anexample" id="example_49"><div class="anexampleTitle">Example <span class="delete">48</span><span class="insert">49</span><sup><a class="internalDFN" href="#example_49"><span class="diamond"> ◊</span></a></sup></div>
<p>In this example, <span class="name">c</span> is a collection known to have <span class="name">e0</span>, <span class="name">e1</span>, and <span class="name">e2</span> as members, and may have other members.</p>
<pre class="codeexample">entity(e0)
@@ -3623,7 +3704,11 @@
name</a>.
</p>
-</div>
+<p><a href="#concept-entity" class="internalDFN"><span class="insert">Entity</span></a><span class="insert">, </span><a href="#concept-activity" class="internalDFN"><span class="insert">Activity</span></a><span class="insert">, and </span><a href="#concept-agent" class="internalDFN"><span class="insert">Agent</span></a><span class="insert"> have a mandatory identifier. Two entities (resp. activities, agents) are equal if they have the same identifier.</span></p>
+
+<p><a href="#concept-generation" class="internalDFN"><span class="insert">Generation</span></a><span class="insert">, </span><a href="#concept-usage" class="internalDFN"><span class="insert">Usage</span></a><span class="insert">, </span><a href="#concept-communication" class="internalDFN"><span class="insert">Communication</span></a><span class="insert">, </span><a href="#concept-start" class="internalDFN"><span class="insert">Start</span></a><span class="insert">, </span><a href="#concept-end" class="internalDFN"><span class="insert">End</span></a><span class="insert">, </span><a href="#concept-invalidation" class="internalDFN"><span class="insert">Invalidation</span></a><span class="insert">, </span><a href="#concept-derivation" class="internalDFN"><span class="insert">Derivation</span></a><span class="insert">, </span><a href="#concept-attribution" class="internalDFN"><span class="insert">Attribution</span></a><span class="insert">, </span><a href="#concept-activityAssociation" class="internalDFN"><span class="insert">Association</span></a><span class="insert">, </span><a href="#concept-delegation" class="internalDFN"><span class="insert">Delegation</span></a><span class="insert">, </span><a href="#concept-influence" class="internalDFN"><span class="insert">Influence</span></a><span class="insert"> have an optional identifier. Two generations (resp. usages, communications, etc.) are equal if they have the same identifier.
+
+</span></p></div>
<div id="term-attribute" class="section">
<h4><span class="secno">5.7.2 </span>Attribute</h4>
@@ -3758,13 +3843,13 @@
<div id="term-attribute-value" class="section">
<h5><span class="secno">5.7.2.5 </span>prov:value</h5>
-<p><span class="glossary-ref"> The attribute <dfn id="concept-value-attribute" title="value-attribute" class="internalDFN"><span class="name">prov:value</span></dfn><sup><a class="internalDFN" href="#concept-value-attribute"><span class="diamond"> ◊</span></a></sup> provides a <a href="#concept-value" class="internalDFN">Value</a> for an entity. </span></p>
+<p><span class="glossary-ref"> The attribute <dfn id="concept-value-attribute" title="value-attribute" class="internalDFN"><span class="name">prov:value</span></dfn><sup><a class="internalDFN" href="#concept-value-attribute"><span class="diamond"> ◊</span></a></sup> provides a <span class="insert">value that is a direct representation of an entity as a PROV-DM </span><a title="value" href="#concept-value" class="internalDFN">Value</a><span class="delete"> for an entity.</span><span class="insert">.</span> </span></p>
<p>The attribute <span class="name">prov:value</span> is an <em class="rfc2119" title="optional">optional</em> attribute of entity. The value associated with the attribute <span class="name">prov:value</span> <em class="rfc2119" title="must">must</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>. The attribute <span class="name">prov:value</span> <em class="rfc2119" title="may">may</em> occur at most once in a set of attribute-value pairs.</p>
-<div class="anexample" id="example_54"><div class="anexampleTitle">Example <span class="delete">53</span><span class="insert">54</span><sup><a class="internalDFN" href="#example_54"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-value1"><div class="anexampleTitle">Example <span class="delete">53</span><span class="insert">54</span><sup><a class="internalDFN" href="#anexample-value1"><span class="diamond"> ◊</span></a></sup></div>
<p>The following example illustrates the provenance of the number <span class="name">4</span> obtained by an activity that computed the length of an input string <span class="name">"abcd"</span>.
The input and the output are expressed as entities <span class="name">ex:in</span> and <span class="name">ex:out</span>, respectively. They each have a <span class="name">prov:value</span> attribute associated with the corresponding value.
</p>
@@ -3777,6 +3862,26 @@
</pre>
</div>
+<p><span class="insert">
+Two different entities </span><em class="rfc2119" title="may"><span class="insert">may</span></em><span class="insert"> have the same value for the attribute
+prov:value. For instance,
+when two entities, with the same prov:value, are generated by two
+different activities, as illustrated
+by the following example.</span></p>
+
+<div class="anexample" id="anexample-value2"><div class="anexampleTitle"><span class="insert">Example 55</span><sup><a class="internalDFN" href="#anexample-value2"><span class="diamond"><span class="insert"> ◊</span></span></a></sup></div>
+<p><a href="#anexample-value1" class="anexample-ref"><span><span class="insert">Example 54</span></span></a><span class="insert"> illustrates an entity with a given value
+ </span><span class="name"><span class="insert">4</span></span><span class="insert">. This examples shows that another entity with the same value may be computed differently (by an addition).
+</span></p>
+<pre class="codeexample"><span class="insert">entity(ex:in1, [ prov:value=3 ])
+entity(ex:in2, [ prov:value=1 ])
+entity(ex:out2, [ prov:value=4 ]) // ex:out2 also has value 4
+activity(ex:add1, [ prov:type="addition" ])
+used(ex:add1, ex:in1)
+used(ex:add1, ex:in2)
+wasGeneratedBy(ex:out2, ex:add1)
+</span></pre>
+</div>
</div>
@@ -3784,6 +3889,10 @@
+
+
+
+
</div>
<div id="term-value" class="section">
@@ -3826,7 +3935,7 @@
-<div class="anexample" id="anexample-value"><div class="anexampleTitle">Example <span class="delete">54</span><span class="insert">55</span><sup><a class="internalDFN" href="#anexample-value"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-value"><div class="anexampleTitle">Example <span class="delete">54</span><span class="insert">56</span><sup><a class="internalDFN" href="#anexample-value"><span class="diamond"> ◊</span></a></sup></div>
<p>
The following examples respectively are the string "abc", the integer number 1, and the IRI "http://example.org/foo".
</p><pre class="codeexample"> "abc"
@@ -3848,7 +3957,7 @@
<p>We note that PROV-DM <dfn title="time" id="dfn-time" class="internalDFN">time instants</dfn><sup><a class="internalDFN" href="#dfn-time"><span class="diamond"> ◊</span></a></sup> are defined according to xsd:dateTime [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>].</p>
-<div class="anexample" id="anexample-time"><div class="anexampleTitle">Example <span class="delete">55</span><span class="insert">56</span><sup><a class="internalDFN" href="#anexample-time"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-time"><div class="anexampleTitle">Example <span class="delete">55</span><span class="insert">57</span><sup><a class="internalDFN" href="#anexample-time"><span class="diamond"> ◊</span></a></sup></div>
<p>
In the following example, the generation time of entity <span class="name">e1</span> is expressed according to
<a href="http://www.w3.org/TR/xmlschema11-2/#dateTime">xsd:dateTime</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>].</p>
@@ -3912,7 +4021,7 @@
<li>Sub-types and sub-relations can be expressed by means of the reserved attribute
<a href="#term-attribute-type"><span class="name">prov:type</span></a>.
-<div class="anexample" id="anexample-sub-relation"><div class="anexampleTitle">Example <span class="delete">56</span><span class="insert">57</span><sup><a class="internalDFN" href="#anexample-sub-relation"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-sub-relation"><div class="anexampleTitle">Example <span class="delete">56</span><span class="insert">58</span><sup><a class="internalDFN" href="#anexample-sub-relation"><span class="diamond"> ◊</span></a></sup></div>
<p>
In the following example, <span class="name">e2</span> is a translation of <span class="name">e1</span>,
expressed as a sub-type of derivation.
@@ -3921,7 +4030,7 @@
</pre>
</div>
-<div class="anexample" id="anexample-sub-type"><div class="anexampleTitle">Example <span class="delete">57</span><span class="insert">58</span><sup><a class="internalDFN" href="#anexample-sub-type"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-sub-type"><div class="anexampleTitle">Example <span class="delete">57</span><span class="insert">59</span><sup><a class="internalDFN" href="#anexample-sub-type"><span class="diamond"> ◊</span></a></sup></div>
<p>
In the following example, <span class="name">e</span> is described as a Car, a type of entity.
</p><pre class="codeexample">
@@ -3937,7 +4046,7 @@
<li>Application and domain specific roles can be expressed by means of the reserved attribute
<a href="#term-attribute-role"><span class="name">prov:role</span></a>.
-<div class="anexample" id="anexample-usage-with-role"><div class="anexampleTitle">Example <span class="delete">58</span><span class="insert">59</span><sup><a class="internalDFN" href="#anexample-usage-with-role"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-usage-with-role"><div class="anexampleTitle">Example <span class="delete">58</span><span class="insert">60</span><sup><a class="internalDFN" href="#anexample-usage-with-role"><span class="diamond"> ◊</span></a></sup></div>
<p>
In the following example, two computers <span class="name">ex:laptop4</span> and <span class="name">ex:desktop9</span> are used in different roles in a work activity.
</p><pre class="codeexample">
@@ -4241,6 +4350,21 @@
</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/519"><span class="insert">ISSUE-519</span></a><span class="insert">, </span><a href="http://www.w3.org/2011/prov/track/issues/523"><span class="insert">ISSUE-523</span></a><span class="insert">, </span><a href="http://www.w3.org/2011/prov/track/issues/524"><span class="insert">ISSUE-524</span></a><span class="insert">, </span><a href="http://www.w3.org/2011/prov/track/issues/529"><span class="insert">ISSUE-529</span></a><span class="insert">: changed UML diagram of figure 8 by removing explicit inheritance from influence for usage, start, end, generation, invalidation, communication, derivation, attribution, association, and delegation. Instead, introduced correspondance table 7. Furthermore, in response to these issues, it was made clear that PROV defines no attribute specific to subtypes such as SoftwareAgent, ..., Plan, Revision, Bundle, Collection.
</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/495"><span class="insert">ISSUE-495</span></a><span class="insert">: made explicit which section, figure, table was informative or normative.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/521"><span class="insert">ISSUE-521</span></a><span class="insert">: now states that "an agent relied on a plan" instead of "an agent adopted a plan".
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/499"><span class="insert">ISSUE-499</span></a><span class="insert">: Made explicit that generation/usage/invalidation/start/end are implicit.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/449"><span class="insert">ISSUE-449</span></a><span class="insert">: Clarified definition of prov:value attribute and added an example.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/495"><span class="insert">ISSUE-495</span></a><span class="insert">: added paragraph about 'relations opening up'. Clarified the role of '-' in example. Fixed dates in biblio. Fixed space issue in prov-n examples
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/516"><span class="insert">ISSUE-516</span></a><span class="insert">: Stating that there moust be some underpinning activity or activities for a derivation, instead of just activities.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/525"><span class="insert">ISSUE-525</span></a><span class="insert">: Made it explicit that Membership, Alternate, Specialization are not Influence
+</span></li><li><span class="insert"> Copied the sentence " An agent may be a particular type of entity or activity. This means that the model can be
+ used to express provenance of the agents themselves. " from the informative section into the normative section.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/504"><span class="insert">ISSUE-504</span></a><span class="insert">: Updated definition of collection.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/503"><span class="insert">ISSUE-503</span></a><span class="insert">: Rephrased the introduction of expanded association in section 2.2.1.2 Expanded Relations.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/514"><span class="insert">ISSUE-514</span></a><span class="insert">: added links to the attributes listed in the secondary element table. Also removed PrimarySource, Quotation, Revision.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/502"><span class="insert">ISSUE-502</span></a><span class="insert">: Added sentence in section 2.1.2 explaining that the focus
+ of derivation is on connecting a generated entity to a used entity.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/526"><span class="insert">ISSUE-526</span></a><span class="insert">: Added sentence clarifying sentence in section 5.5.2.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/462"><span class="insert">ISSUE-462</span></a><span class="insert">: Added clarification regarding entity attributes (with respect to fixed aspects) and role of identifier with respect to equality.
</span></li></ul>
</div>
@@ -4327,11 +4451,11 @@
</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"><span class="delete">C.2</span><span class="insert">D.2</span> </span>Informative references</h3><dl class="bibliography"><dt id="bib-Logic">[Logic]</dt><dd>W. E. Johnson <a href="http://www.ditext.com/johnson/intro-3.html"><cite>Logic: Part III</cite></a>.1924. URL: <a href="http://www.ditext.com/johnson/intro-3.html">http://www.ditext.com/johnson/intro-3.html</a>
</dd><dt id="bib-Mappings">[Mappings]</dt><dd>Satya Sahoo and Paul Groth and Olaf Hartig and Simon Miles and Sam Coppens and James Myers and Yolanda Gil and Luc Moreau and Jun Zhao and Michael Panzer and Daniel Garijo <a href="http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings"><cite>Provenance Vocabulary Mappings</cite></a>. August 2010 URL: <a href="http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings">http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings</a>
-</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne and Paul Groth (eds.) Luc Moreau, Olaf Hartig, Yogesh Simmhan, James Meyers, Timothy Lebo, Khalid Belhajjame, and Simon Miles <a href="http://www.w3.org/TR/prov-aq/"><cite>Provenance Access and Query</cite></a>. 2011, Working Draft. URL: <a href="http://www.w3.org/TR/prov-aq/">http://www.w3.org/TR/prov-aq/</a>
-</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney, Paolo Missier, and Luc Moreau (eds.) <a href="http://www.w3.org/TR/prov-constraints/"><cite>Constraints of the PROV Data Model</cite></a>. 2011, Working Draft. URL: <a href="http://www.w3.org/TR/prov-constraints/">http://www.w3.org/TR/prov-constraints/</a>
-</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau and Paolo Missier (eds.) James Cheney, Stian Soiland-Reyes <a href="http://www.w3.org/TR/prov-n/"><cite>PROV-N: The Provenance Notation</cite></a>. 2011, Working Draft. URL: <a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a>
-</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo, Satya Sahoo and Deborah McGuinness (eds.) Khalid Belhajjame, James Cheney, David Corsar, Daniel Garijo, Stian Soiland-Reyes, and Stephan Zednik <a href="http://www.w3.org/TR/prov-o/"><cite>Provenance Formal Model</cite></a>. 2011, Working Draft. URL: <a href="http://www.w3.org/TR/prov-o/">http://www.w3.org/TR/prov-o/</a>
-</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil and Simon Miles (eds.) Khalid Belhajjame, Helena Deus, Daniel Garijo, Graham Klyne, Paolo Missier, Stian Soiland-Reyes, and Stephan Zednik <a href="http://www.w3.org/TR/prov-primer/"><cite>Prov Model Primer</cite></a>. 2011, Working Draft. URL: <a href="http://www.w3.org/TR/prov-primer/">http://www.w3.org/TR/prov-primer/</a>
+</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne and Paul Groth (eds.) Luc Moreau, Olaf Hartig, Yogesh Simmhan, James Meyers, Timothy Lebo, Khalid Belhajjame, and Simon Miles <a href="http://www.w3.org/TR/prov-aq/"><cite>Provenance Access and Query</cite></a>. <span class="delete">2011,</span><span class="insert">2012,</span> Working Draft. URL: <a href="http://www.w3.org/TR/prov-aq/">http://www.w3.org/TR/prov-aq/</a>
+</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney, Paolo Missier, and Luc Moreau (eds.) <a href="http://www.w3.org/TR/prov-constraints/"><cite>Constraints of the PROV Data Model</cite></a>. <span class="delete">2011,</span><span class="insert">2012,</span> Working Draft. URL: <a href="http://www.w3.org/TR/prov-constraints/">http://www.w3.org/TR/prov-constraints/</a>
+</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau and Paolo Missier (eds.) James Cheney, Stian Soiland-Reyes <a href="http://www.w3.org/TR/prov-n/"><cite>PROV-N: The Provenance Notation</cite></a>. <span class="delete">2011,</span><span class="insert">2012,</span> Working Draft. URL: <a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a>
+</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo, Satya Sahoo and Deborah McGuinness (eds.) Khalid Belhajjame, James Cheney, David Corsar, Daniel Garijo, Stian Soiland-Reyes, and Stephan Zednik <a href="http://www.w3.org/TR/prov-o/"><cite>Provenance Formal Model</cite></a>. <span class="delete">2011,</span><span class="insert">2012,</span> Working Draft. URL: <a href="http://www.w3.org/TR/prov-o/">http://www.w3.org/TR/prov-o/</a>
+</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil and Simon Miles (eds.) Khalid Belhajjame, Helena Deus, Daniel Garijo, Graham Klyne, Paolo Missier, Stian Soiland-Reyes, and Stephan Zednik <a href="http://www.w3.org/TR/prov-primer/"><cite>Prov Model Primer</cite></a>. <span class="delete">2011,</span><span class="insert">2012,</span> Working Draft. URL: <a href="http://www.w3.org/TR/prov-primer/">http://www.w3.org/TR/prov-primer/</a>
</dd><dt id="bib-RDF-CONCEPTS11">[RDF-CONCEPTS11]</dt><dd>Richard Cyganiak and David Wood (eds.) RDF 1.1 Concepts and Abstract Syntax <a href="http://www.w3.org/TR/rdf11-concepts/"><cite>RDF 1.1 Concepts and Abstract Syntax</cite></a>. URL: <a href="http://www.w3.org/TR/rdf11-concepts/">http://www.w3.org/TR/rdf11-concepts/</a>
</dd></dl></div></div></body></html>
--- a/model/glossary.html Wed Oct 31 13:09:26 2012 +0000
+++ b/model/glossary.html Wed Oct 31 13:10:51 2012 +0000
@@ -36,7 +36,7 @@
</span>
<span class="glossary" id="glossary-collection">
-A <dfn id="concept-collection">collection</dfn> is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be <dfn>member of</dfn> the collections.
+A <dfn id="concept-collection">collection</dfn> is an entity that provides a structure to some constituents that must themselves be entities. These constituents are said to be <dfn>member of</dfn> the collections.
</span>
@@ -273,7 +273,7 @@
<span class="glossary" id="glossary-value-attribute">
-The attribute <dfn id="concept-value-attribute" title="value-attribute"><span class="name">prov:value</span></dfn> provides a <a>Value</a> for an entity.
+The attribute <dfn id="concept-value-attribute" title="value-attribute"><span class="name">prov:value</span></dfn> provides a value that is a direct representation of an entity as a PROV-DM <a title="value">Value</a>.
</span>
<span class="glossary" id="glossary-provenance-service">
--- a/model/glossary.js Wed Oct 31 13:09:26 2012 +0000
+++ b/model/glossary.js Wed Oct 31 13:10:51 2012 +0000
@@ -3,7 +3,7 @@
// with <script src="glossary.js" class="remove"></script>
//Insert glossary definitions with the following
// <div class="glossary-ref" ref="glossary-generation"></div>
-glossary_hg='http://dvcs.w3.org/hg/prov/file/90c3e84c18cd/model/glossary.html';
+glossary_hg='http://dvcs.w3.org/hg/prov/file/38b9e40267bb/model/glossary.html';
glossary_string=
' ' +
'<html> ' +
@@ -43,7 +43,7 @@
'</span> ' +
' ' +
'<span class="glossary" id="glossary-collection"> ' +
-'A <dfn id="concept-collection">collection</dfn> is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be <dfn>member of</dfn> the collections. ' +
+'A <dfn id="concept-collection">collection</dfn> is an entity that provides a structure to some constituents that must themselves be entities. These constituents are said to be <dfn>member of</dfn> the collections. ' +
'</span> ' +
' ' +
' ' +
@@ -280,7 +280,7 @@
' ' +
' ' +
'<span class="glossary" id="glossary-value-attribute"> ' +
-'The attribute <dfn id="concept-value-attribute" title="value-attribute"><span class="name">prov:value</span></dfn> provides a <a>Value</a> for an entity. ' +
+'The attribute <dfn id="concept-value-attribute" title="value-attribute"><span class="name">prov:value</span></dfn> provides a value that is a direct representation of an entity as a PROV-DM <a title="value">Value</a>. ' +
'</span> ' +
' ' +
'<span class="glossary" id="glossary-provenance-service"> ' +
--- a/model/prov-constraints.html Wed Oct 31 13:09:26 2012 +0000
+++ b/model/prov-constraints.html Wed Oct 31 13:10:51 2012 +0000
@@ -318,7 +318,7 @@
};
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "LC",
+ specStatus: "ED",
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "prov-constraints",
@@ -330,8 +330,8 @@
// if you wish the publication date to be other than today, set this
- // publishDate: "2012-05-03",
- publishDate: "2012-09-11",
+ // FPWD publishDate: "2012-05-03",
+ // LC publishDate: "2012-09-11",
// if the specification's copyright date is a range of years, specify
// the start date here:
@@ -424,8 +424,11 @@
<p> This document defines a subset of PROV instances called
-<i><a>valid</a></i> PROV instances.
-The intent of validation is ensure that a PROV instance represents a history of objects and their interactions which is consistent, and thus safe to use for the purpose of logical reasoning and other kinds of analysis.
+<i><a>valid</a></i> PROV instances, by analogy with notions of
+validity for other Web standards.
+The intent of validation is ensure that a PROV instance represents a
+consistent history of objects and their interactions that is safe to
+use for the purpose of logical reasoning and other kinds of analysis.
Valid PROV instances satisfy
certain <a>definitions</a>, <a>inferences</a>, and
<a>constraints</a>. These definitions, inferences, and constraints
@@ -468,13 +471,16 @@
<li>The Linked Data and Semantic Web community should focus on PROV-O
defining PROV classes and properties specified in an OWL2
ontology. For further details, PROV-DM and PROV-CONSTRAINTS specify
-the constraints applicable to the data model, and its interpretation.
-<!--PROV-SEM provides a mathematical semantics.
--->
+the constraints applicable to the data model, and its interpretation.
</li>
<li>Developers seeking to retrieve or publish provenance should focus on PROV-AQ.</li>
<li>Readers seeking to implement other PROV serializations
-should focus on PROV-DM and PROV-CONSTRAINTS. PROV-O and PROV-N offer examples of mapping to RDF and text, respectively.</li>
+should focus on PROV-DM and PROV-CONSTRAINTS. PROV-O and PROV-N offer
+examples of mapping to RDF and text, respectively.</li>
+<li>[[PROV-SEM]] provides a mathematical semantics and a collection of
+axioms that provide a (non-normative, but equivalent) declarative specification, aimed
+at readers with a mathematical logic or formal background. This can
+serve as a starting point for alternative implementations. </li>
</ul>
</section>
@@ -530,8 +536,16 @@
PROV-DM specification [[PROV-DM]] imposes minimal requirements upon
PROV instances. A <a>valid</a> PROV instance corresponds to a
consistent history of objects and interactions to which logical
-reasoning can be safely applied. By default, PROV instances need not
-be <a>valid</a>. </p>
+reasoning can be safely applied. PROV instances need not
+be <a>valid</a>.
+</p>
+<p>
+The term <a>valid</a> is chosen by analogy with
+notions of validity in other W3C specifications. Unfortunately, this
+terminology is incompatible with the usual meaning of "validity" in logic;
+our notion of validity of a PROV instance/document is closer to
+logical "consistency".
+</p>
<p> This document specifies <em>definitions</em> of some
provenance statements in terms of others, <em>inferences</em> over PROV instances
@@ -543,7 +557,8 @@
constraints</em>.
Further discussion
of the semantics of PROV statements, which justifies the definitions, inferences
-and constraints, can be found in the formal semantics [[PROV-SEM]].
+and constraints, and relates the procedural specification approach
+taken here to a declarative specification, can be found in the formal semantics [[PROV-SEM]].
</p>
<p>We define validity and equivalence in terms of a
@@ -554,26 +569,31 @@
<a title="valid">validity</a>. Equivalence of two PROV
instances can be determined by comparing their normal forms. For PROV
documents, validity and equivalence amount to checking the validity or
-pairwise equivalence of their respective documents.
+pairwise equivalence of their respective instances.
</p>
<p>
-This document outlines an algorithm for validity checking based on
+This specification defines
+validity and equivalence procedurally, via an algorithm based on
<a title="normal form">normalization</a>. Applications MAY implement
-validity and equivalence checking using normalization, as suggested
-here, or in
+validity and equivalence checking using normalization, as outlined
+here. Applications MAY also implement validation and equivalence
+checking in
any other way as long as the same instances or documents are considered valid or
equivalent, respectively.
</p>
-<p>Checking validity or equivalence are RECOMMENDED, but not required, for
-applications compliant with PROV. This specification defines how
-validity and equivalence are to be checked, if an application elects
-to support them at all.
+<p> Checking validity or equivalence are RECOMMENDED, but not required, for
+applications compliant with PROV.
Applications producing provenance SHOULD ensure that it is
<a>valid</a>, and similarly applications consuming provenance MAY reject provenance that is not <a>valid</a>. Applications
which are determining whether PROV instances or documents convey the same
information SHOULD check equivalence as specified here, and SHOULD
-treat equivalent instances or documents in the same way.
+treat equivalent instances or documents in the same way. This is a
+guideline only, because meaning of "in the same way" is
+application-specific. For example, applications that manipulate the syntax of
+PROV instances in particular representations, such as pretty-printing
+or digital signing, have good reasons to treat syntactically
+different, but equivalent, documents differently.
</p>
</section>
<section>
@@ -995,9 +1015,25 @@
does not attempt to provide a complete introduction to these topics,
but it is provided in order to aid readers familiar with one or more
of these topics in understanding the specification, and to clarify
- some of the motivations for choices in the specification to all readers.
+ some of the motivations for choices in the specification to all
+ readers.
</p>
+ <p>As discussed below, the definitions, inferences and constraints
+can be viewed as pure logical assertions that could be checked in a
+variety of ways. The rest of this document specifies validity and
+equivalence procedurally, that is, in terms of a reference
+implementation based on normalization. Although both declarative and
+procedural specification techniques have advantages, a purely
+declarative specification offers much less assistance for
+implementers, while a procedural approach immediately demonstrates
+implementability and provides an adequate (polynomial-time) default implementation. In
+this section we relate the declarative meaning of formulas to their
+procedural meaning. [[PROV-SEM]] will provide an alternative,
+declarative characterization of validity and equivalence which could
+be used as a starting point for other implementation strategies. </p>
+
+
<h4>Constants, Variables and Placeholders</h4>
<p>
@@ -1151,17 +1187,24 @@
substitution for <span class="math">x<sub>1</sub>...x<sub>n</sub></span> making <span class="math">A<sub>1</sub> ∧ ... ∧ A<sub>l</sub></span> true.
</ol>
-<h4>Merging</h4>
-
- <p><em>Merging</em> is an operation that takes two terms and compares them to
- see if they are equal, or can be made equal by substituting an
- existential variable with another term. This operation is a special
- case of <em>unification</em>, a common operation in logical
- reasoning, including logic programming and automated reasoning.
-Merging two terms <span class="math">t,t'</span> results in either substitution <span class="math">S</span>
+<h4>Unification and Merging</h4>
+
+ <p><em>Unification</em> is an operation that takes two terms and compares them to
+ determine whether they can be made equal by substituting an
+ existential variable with another term. If so, the result is such a
+ substitution; otherwise, the result is failure. Unification is an
+ essential concept in logic programming and automated reasoning,
+where terms can involve variables, constants and function symbols. In PROV,
+ by comparison, unification only needs to deal with
+</p>
+<p>
+Unifying two terms <span class="math">t,t'</span> results in either substitution <span class="math">S</span>
such that <span class="math">S(t) = S(t')</span>, or failure indicating that there is no
substitution that can be applied to both <span class="math">t</span> and <span class="math">t'</span> to make
- them equal.
+ them equal. Unification is also used to define an operation on PROV
+ statements called <em>merging</em>. Merging takes two statements
+ that have equal identifiers, unifies their corresponding term
+ arguments, and combines their attribute lists.
</p>
@@ -1205,20 +1248,20 @@
x<sub>1</sub>...x<sub>n</sub>. A<sub>1</sub> ∧ ... ∧ A<sub>p</sub> ⇒ t
= t'</span> can be
applied by searching for an occurrence <span class="math">A<sub>1</sub> ∧ ... ∧ A<sub>p</sub></span> in the instance, and
- if one is found, merging the terms <span class="math">t</span> and
+ if one is found, unifying the terms <span class="math">t</span> and
<span class="math">t'</span>. If successful, the resulting
substitution is applied to the instance; otherwise, the application
of the uniqueness constraint fails. </li>
<li>A key constraint can similarly be applied by searching for
-different occurrences of a statement with the same identifier, merging the
+different occurrences of a statement with the same identifier, unifying the
corresponding parameters of the statements, and concatenating their
-attribute lists. The substitutions obtained by merging are applied to
-the instance.
+attribute lists, to form a single statement. The substitutions obtained by unification are applied to
+the merged statement and the rest of the instance.
</li>
</ul>
<p>As noted above, uniqueness or key constraint
- application can <em>fail</em>, if a required merging step fails. Failure of constraint
+ application can <em>fail</em>, if a required unification or merging step fails. Failure of constraint
application means that there is no way to add information to the
instance to satisfy the constraint, which in turn implies that the
instance is <em>invalid</em>.
@@ -1230,6 +1273,16 @@
called <em>chasing</em> [[DBCONSTRAINTS]] or <em>saturation</em>
[[CHR]]. We call this process <em>normalization</em>.
</p>
+ <p>
+ Although this specification outlines one particular way of
+ performing inferences and checking constraints, based on
+ normalization, implementations can use any other equivalent
+ algorithm. The logical formulas corresponding to the definitions,
+ inferences, and constraints outlined above (and further elaborated
+ in [[PROV-SEM]]) provides an equivalent specification, and any
+ implementation that correctly checks validity and equivalence (whether it performs normalization or not) complies
+ with this specification.
+ </p>
<h4>Termination</h4>
@@ -1350,7 +1403,8 @@
</li>
</ol>
<p>
- A normalized instance that satisfies all of the checked constraints
+ A normalized instance that passes all of the ordering, typing,
+ and impossibility constraint checks
is called <a>valid</a>. Validity can be, but is not required to be,
checked by normalizing and then checking constraints. Any other
algorithm that provides equivalent behavior (that is, accepts the
@@ -1379,8 +1433,11 @@
notion of equivalence of normal forms is <em>isomorphism</em>. Two
instances <span class="math">I<sub>1</sub></span> and <span class="math">I<sub>2</sub></span> are <em>isomorphic</em> if there is an invertible
substitution <span class="math">S</span> mapping existential variables to existential variables such that <span class="math">S(I<sub>1</sub>) = I<sub>2</sub></span>.
+<!--
This is similar to the notion of equivalence used in [[RDF]], where
- blank nodes play an analogous role to existential variables. </p>
+ blank nodes play an analogous role to existential variables.
+ -->
+ </p>
<p>Equivalence can be checked by normalizing instances, checking that
both instances are valid, then
@@ -1395,18 +1452,47 @@
those obtained by the algorithm in this specification.
</p>
+<p>Equivalence is only explicitly specified for
+valid instances (whose normal forms exist and are unique up to
+isomorphism). Implementations may test equivalences involving valid
+and invalid documents. This specification does not constrain the
+behavior of equivalence checking involving invalid instances, provided
+that:
+</p>
+<ul>
+ <li>instance equivalence is <a>reflexive</a>, <a>symmetric</a> and
+ <a>transitive</a> on all instances</li>
+ <li> no valid instance is equivalent to an invalid instance.</li>
+ </ul>
+<p>
+Because of the second constraint, equivalence is essentially the union
+ of two equivalence relations on the disjoint sets of valid and
+ invalid instances.
+ There are two simple implementations of equivalence for invalid
+ documents that are correct:</p>
+ <ol>
+ <li>each invalid instance is equivalent only to itself</li>
+ <li>every pair of invalid instances are equivalent</li>
+ </ol>
+
<h4>From Instances to Bundles and Documents</h4>
<p>PROV documents can contain multiple instances: a <a>toplevel
-instance</a> consisting of the set of statements not appearing within a bundle, and
-zero or more named instances called <a>bundle</a>s. For the purpose
+instance</a>, and
+zero or more additional, named instances called <a>bundle</a>s. For the purpose
of inference and constraint checking, these instances are treated independently. That is,
a PROV document is valid provided that each instance in it is valid
-and the names of its bundles are distinct. Similarly, a PROV document is
+and the names of its bundles are distinct. In other words, there are
+no validity constraints that need to be checked across the different
+instances in a PROV document; the contents of one instance in a
+multi-instance PROV document cannot affect the validity of another instance.
+Similarly, a PROV document is
equivalent to another if their toplevel instances are equivalent, they
have the same number of bundles with the same names, and the instances
-of their corresponding bundles are equivalent. Analogously to blank nodes in
-[[RDF]], the scope of an existential variable in PROV is the instance
+of their corresponding bundles are equivalent.
+<!--Analogously to blank nodes in
+[[RDF]],-->
+The scope of an existential variable in PROV is delimited at the instance
level, so existential variables with the same name occurring in
different instances do not necessarily denote the same term. This
is a consequence of the fact that the instances of two equivalent
@@ -1711,9 +1797,10 @@
application MAY apply the inferences and definitions in <a
href="#inferences" class='sectionRef'></a>.</li>
<li>If determining whether a PROV instance or document is <a>valid</a>, an
- application MUST check that all of the
+ application MUST determine whether all of the
constraints of <a href="#constraints" class="sectionRef"></a> are
- satisfied on the <a>normal form</a> of the instance or document. </li>
+ satisfied on
+ the <a>normal form</a> of the instance or document. </li>
<li> If producing provenance meant for other applications to
use, the application SHOULD produce <a>valid</a> provenance, as specified in <a href="#normalization-validity-equivalence" class="sectionRef"></a>. </li>
<li>If determining whether two PROV instances or documents are
@@ -1721,10 +1808,15 @@
normal forms are equal, as specified in <a href="#normalization-validity-equivalence" class="sectionRef"></a>.
</ol>
- <p>Compliant applications are not required to explicitly compute
- normal forms; however, if checking validity or equivalence, the
- results should be the same as would be obtained by computing normal
- forms as defined in this specification.</p>
+ <p>This specification defines validity and equivalence procedurally
+ via reduction to normal forms. If checking validity or equivalence, the
+ results MUST be the same as would be obtained by computing normal
+ forms as defined in this specification. Applications that explicitly compute
+ normal forms, following the implementation strategy suggested by
+ this specification, are by definition compliant. However,
+ applications can also comply by checking validity and equivalence in any
+ other way that yields the same answers without explicitly applying
+ definitions, inferences, and constraints or constructing normal forms.</p>
<p>
All figures are for illustration purposes
@@ -1784,6 +1876,11 @@
its definition.
</p>
+ <div class="remark">
+ We use definitions primarily to expand the compact, concrete
+ PROV-N syntax, including short forms and optional parameters to the abstract syntax
+ implicitly used in PROV-DM.
+ </div>
<p> Inferences have the following general form:</p>
<div class='inference-example' id='inference-example'>
@@ -1808,7 +1905,9 @@
identifiers might later be found to be equal to known identifiers;
they play a similar role in PROV constraints to existential
variables in logic, to "labeled nulls" in database theory
- [[DBCONSTRAINTS]], or to blank nodes in [[!RDF]]. In general, omitted optional parameters to
+ [[DBCONSTRAINTS]].
+ <!--, or to blank nodes in [[!RDF]].-->
+ In general, omitted optional parameters to
[[PROV-N]] statements, or explicit <span class="name">-</span>
markers, are placeholders for existentially quantified variables;
that is, they denote unknown values. There are a few exceptions to
@@ -1822,8 +1921,11 @@
should be viewed as existentially quantified variables, meaning that
through subsequent reasoning steps they may turn out to be equal to
other identifiers that are already known, or to other existentially
- quantified variables. Their treatment is analogous to that of blank
- nodes in RDF. In contrast, distinct URIs or literal values in PROV
+ quantified variables.
+ <!--
+ Their treatment is analogous to that of blank
+ nodes in RDF.-->
+ In contrast, distinct URIs or literal values in PROV
are assumed to be distinct for the purpose of checking validity or
inferences. This issue is discussed in more detail under <a
href="#uniqueness-constraints">Uniqueness Constraints</a>.
@@ -2109,7 +2211,7 @@
Essentially, the definitions state that parameters
<span class="name">g,u</span> are expandable only if the activity is specified, i.e., if parameter <span class="name">a</span> is provided.
-The rationale for this is that when a is provided, then there have to be two events, namely <span class="name">u</span> and <span class="name">g</span>, which account for the usage of <span class="name">e1</span> and the generation of <span class="name">e2</span>, respectively, by <span class="name">a</span>. Conversely, if <span class="name">a</span> is not provided, then one cannot tell whether one or more activities are involved in the derivation, and the explicit introduction of such events, which correspond to a single acitivity, would therefore not be justified. </p>
+The rationale for this is that when a is provided, then there have to be two events, namely <span class="name">u</span> and <span class="name">g</span>, which account for the usage of <span class="name">e1</span> and the generation of <span class="name">e2</span>, respectively, by <span class="name">a</span>. Conversely, if <span class="name">a</span> is not provided, then one cannot tell whether one or more activities are involved in the derivation, and the explicit introduction of such events, which correspond to a single activity, would therefore not be justified. </p>
<p> A later constraint, <a class="rule-ref"
@@ -2558,10 +2660,10 @@
<div class="remark">
In the above inference, <span class="name">_pl</span> is an
- existential variable, so it can be
- merged with a constant identifier, another existential variable, or a
+ existential variable, so it can be unified
+with a constant identifier, another existential variable, or a
placeholder <span class="name">-</span>, as explained
- in the definition of <a>merging</a>.
+ in the definition of <a>unification</a>.
</div>
<hr />
<p id='delegation-inference_text'> Delegation relates agents where one agent acts on behalf of
@@ -2594,7 +2696,7 @@
<span class="name">_pl1</span> and <span class="name">_pl2</span>
can be replaced with constant identifiers, existential variables, or
placeholders <span class="name">-</span> independently, as explained
- in the definition of <a>merging</a>.
+ in the definition of <a>unification</a>.
</div>
<hr />
@@ -2830,44 +2932,41 @@
class="name">a</span>) is <span
class="name">activity(a,2011-11-16T16:00:00,2011-11-16T18:00:00,[a=1,b=2])</span>. </p>
- <p> <dfn>Merging</dfn> is an operation that can be applied
- to a pair of terms, or a pair of attribute lists.
- The result of merging is either a substitution (mapping
- existentially quantified variables to terms) or failure, indicating that the merge
- cannot be performed. Merging of pairs of terms, attribute lists,
- or statements is defined as follows.</p>
+ <p> <dfn>Unification</dfn> is an operation that can be applied
+ to a pair of terms.
+ The result of unification is either a <dfn>unifier</dfn>, that is,
+ a substitution <span class="math">S</span> such that <span class="math">S(t)
+ = S(t')</span>, or failure, indicating
+ that there is no <a>unifier</a>. Unification of pairs of terms is defined as follows.</p>
<ul>
<li> If <span class="name">t</span> and <span
class="name">t'</span> are constant identifiers or values
(including the placeholder <span class="name">-</span>), then
- their <a>merge</a> exists only if they are equal, otherwise merging
+ there are two cases. If <span class="name">t = t'</span> then their <a>unifier</a> is the
+ empty substitution, otherwise unification
fails. </li>
<li> If <span class="name">x</span> is an existential variable
and
<span class="name">t'</span> is any term (identifier, constant,
placeholder <span class="name">-</span>, or
existential variable), then their
- <a>merge</a> is <span class="name">t'</span>, and the resulting substitution is
- <span class="name">[x=t']</span>. In the special case where <span class="name">t'=x</span>, the merge is
- <span class="name">x</span> and the resulting substitution is empty.</li>
+ <a>unifier</a> is
+ <span class="name">[x=t']</span>. In the special case where
+ <span class="name">t'=x</span>, the unifier is the empty substitution.</li>
<li> If <span class="name">t</span> is any term (identifier, constant,
placeholder <span class="name">-</span>, or
existential variable) and
<span class="name">x'</span> is an existential variable, then their
- merge is the same as the merge of <span class="name">x</span> and <span class="name">t</span>.</li>
- <li> The <a>merge</a> of two attribute lists <span
- class="name">attrs1</span> and <span class="name">attrs2</span>
- is their union, considered as sets of key-value pairs, written <span
- class="name">attrs1 ∪ attrs2</span>. Duplicate keys with
- different are
- allowed, but equal key-value pairs are merged.</li>
-</ul>
-
-
-<div class="remark">Merging for terms is analogous to unification in
+ unifier is the same as the unifier of <span class="name">x</span>
+ and <span class="name">t</span>.</li>
+ </ul>
+
+
+
+<div class="remark">Unification is analogous to unification in
logic programming and theorem proving, restricted to flat terms with
- no function symbols. No occurs check is needed because there are no
+constants and variables but no function symbols. No occurs check is needed because there are no
function symbols.</div>
<p>
@@ -2881,15 +2980,15 @@
<ol> <li>Suppose PROV instance <span class="math">I</span> contains all of the hypotheses
<span class="name">hyp<sub>1</sub></span> and ... and <span class="name">hyp<sub>n</sub></span>.
</li>
- <li>Attempt to merge all of the equated terms in the conclusion
+ <li>Attempt to unify all of the equated terms in the conclusion
<span class="name">t<sub>1</sub></span> = <span class="name">u<sub>1</sub></span> and ... and <span class="name">t<sub>n</sub></span> = <span class="name">u<sub>n</sub></span>.
</li>
- <li>If merging fails, then the constraint
+ <li>If unification fails, then the constraint
is unsatisfiable, so application of the constraint to <span class="math">I</span>
fails. If this failure occurs during <a>normalization</a> prior to
validation, then <span class="math">I</span> is invalid, as explained in <a href="#normalization-validity-equivalence">Section 6</a>.
</li>
- <li>If merging succeeds with a substitution <span class="math">S</span>, then
+ <li>If unification succeeds with a substitution <span class="math">S</span>, then
<span class="math">S</span> is applied to the instance <span class="math">I</span>, yielding result <span class="math">S(I)</span>.</li>
</ol>
@@ -2906,20 +3005,20 @@
<p> Because of the presence of attributes, key constraints do not
reduce directly to uniqueness constraints. Instead, we enforce key
- constraints as follows. </p>
+ constraints using the following <dfn>merging</dfn> process. </p>
<ol>
<li> Suppose <span
class="name">r(a<sub>0</sub>; a<sub>1</sub>,...a<sub>n</sub>,attrs1)</span> and <span
class="name">r(b<sub>0</sub>; b<sub>1</sub>,...b<sub>n</sub>,attrs2)</span> hold in PROV instance <span class="math">I</span>, where the key fields <span
class="name">a<sub>k</sub> = b<sub>k</sub></span> are equal.</li>
- <li> Attempt to merge all of the corresponding parameters <span
+ <li> Attempt to unify all of the corresponding parameters <span
class="name">a<sub>0</sub> = b<sub>0</sub> </span> and ... and <span
class="name">a<sub>n</sub> = b<sub>n</sub></span>.
</li>
- <li>If merging fails, then the constraint is unsatisfiable, so
+ <li>If unification fails, then the constraint is unsatisfiable, so
application of the key constraint to <span class="math">I</span> fails.
</li>
- <li>If merging succeeds with substitution <span class="math">S</span>, then we remove <span
+ <li>If unification succeeds with substitution <span class="math">S</span>, then we remove <span
class="name">r(a<sub>0</sub>; a<sub>1</sub>,...a<sub>n</sub>,attrs1)</span> and <span
class="name">r(b<sub>0</sub>; b<sub>1</sub>,...b<sub>n</sub>,attrs2)</span> from <span class="math">I</span>, obtaining
instance <span class="math">I'</span>, and return instance <span
@@ -2927,14 +3026,15 @@
attrs2)}</span> ∪ <span class="math">S(I')</span>.
</ol>
+
<p>Thus, if a PROV instance contains an apparent violation of a uniqueness
- constraint or key constraint, merging can be used to determine
+ constraint or key constraint, unification or merging can be used to determine
whether the constraint can be satisfied by instantiating some existential
variables with other terms. For key constraints, this is the same
as merging pairs of statements whose keys are equal and whose
corresponding arguments are compatible, because after
- merging respective arguments and attribute lists, the two statements
+ unifying respective arguments and combining attribute lists, the two statements
become equal and one can be omitted. </p>
@@ -2952,14 +3052,14 @@
</p>
<div class='constraint' id='key-object'>
<p><ol>
- <li>The identifier field <span class="name">e</span> is a <span class="conditional">KEY</span> for
- the <span class="name">entity(e,attrs)</span> statement.
+ <li>The identifier field <span class="name">id</span> is a <span class="conditional">KEY</span> for
+ the <span class="name">entity(id,attrs)</span> statement.
</li>
- <li>The identifier field <span class="name">a</span> is a <span class="conditional">KEY</span> for
- the <span class="name">activity(a,t1,t2,attrs)</span> statement.
+ <li>The identifier field <span class="name">id</span> is a <span class="conditional">KEY</span> for
+ the <span class="name">activity(id,t1,t2,attrs)</span> statement.
</li>
-<li>The identifier field <span class="name">ag</span> is a <span class="conditional">KEY</span> for
- the <span class="name">agent(ag,attrs)</span> statement.
+<li>The identifier field <span class="name">id</span> is a <span class="conditional">KEY</span> for
+ the <span class="name">agent(id,attrs)</span> statement.
</li>
</ol>
</div>
@@ -3208,7 +3308,7 @@
orders: we say <span class="name">e1</span> <dfn>strictly precedes</dfn> <span
class="name">e2</span> to indicate that <span class="name">e1</span>
happened before <span class="name">e2</span>, but not at the same time. This is a
-<a>transitive</a> relation. </p>
+<a>transitive</a>, <a>irreflexive</a> relation. </p>
<p>PROV also allows for time observations to be inserted in
@@ -3222,7 +3322,7 @@
implies event ordering, or vice versa. However, an application MAY flag time values
that appear inconsistent with the event ordering as possible
inconsistencies. When generating provenance, an application SHOULD
-use a consistent imeline for related PROV statements within an
+use a consistent timeline for related PROV statements within an
instance.</p>
@@ -3926,7 +4026,7 @@
<p>
<hr />
-<p id='actedOnBehalfOf-ordering_text'>For delegation, two agents need to have some overlap in their lifetime.</p>
+<p id='actedOnBehalfOf-ordering_text'>For delegation, the responsible agent has to precede or have some overlap with the subordinate agent.</p>
<div class='constraint' id='actedOnBehalfOf-ordering'>
@@ -4421,7 +4521,8 @@
variables), yielding an instance <span class="math">I<sub>2</sub></span>.
</li>
<li>
- Apply all uniqueness constraints to <span class="math">I<sub>2</sub></span> by merging terms or statements
+ Apply all uniqueness constraints to <span
+ class="math">I<sub>2</sub></span> by unifying terms or merging statements
and applying the resulting substitution to the instance, yielding
an instance <span class="math">I<sub>3</sub></span>. If some uniqueness constraint cannot be
applied, then normalization fails.
@@ -4446,9 +4547,8 @@
<p>
A PROV instance is <dfn id="dfn-valid">valid</dfn>
-if its normal form exists and satisfies all of
- the validity constraints; this implies that the instance satisfies
- all of the definitions, inferences, and constraints.
+if its normal form exists and all of
+ the validity constraints succeed on the normal form.
The following algorithm can be used to test
validity:</p>
@@ -4473,14 +4573,34 @@
</li>
</ol>
-<p>A normal form of a PROV instance does not exist when a uniqueness constraint fails due to merging failure. </p>
-
-
- <p>Two PROV instances are <dfn>equivalent</dfn> if they have isomorphic normal forms (that is, after applying all possible inference
+<p>A normal form of a PROV instance does not exist when a uniqueness
+ constraint fails due to unification or merging failure. </p>
+
+
+ <p>Two PROV instances <span class="math">I</span> and <span class="math">I'</span> are <dfn>isomorphic</dfn> if
+ there exists an invertible substitution <span class="math">S</span> that maps each
+ variable of <span class="math">I</span> to a distinct variable of <span class="math">I'</span> and such that
+ <span class="math">S(I) = I'</span>.</p>
+
+<p> Two <a>valid</a> PROV instances are <dfn>equivalent</dfn> if they
+ have <a>isomorphic</a> normal forms. That is, after applying all possible inference
rules, the two instances produce the same set of PROV statements,
up to reordering of statements and attributes within attribute lists,
- and renaming of existential variables).
-Equivalence has the following characteristics: </p>
+ and renaming of existential variables.
+</p>
+ <p>Equivalence can also be checked over pairs of PROV instances that
+ are not necessarily valid, subject to the following rules:
+ <ul>
+ <li>If both are valid, then equivalence is
+ defined above.</li>
+ <li>If both are invalid, then equivalence can be
+ implemented in any way provided it is <a>reflexive</a>, <a>symmetric</a>, and <a>transitive</a>.
+ </li>
+ <li>If one instance is valid and the other is invalid, then the two
+ instances are not equivalent.</li>
+ </ul>
+ <p>
+Equivalence has the following characteristics over valid instances: </p>
<ul>
<li>
@@ -4504,17 +4624,20 @@
<li>
Applying inference rules, definitions, and uniqueness constraints preserves equivalence. That is, a <a>PROV
instance</a> is equivalent to the instance obtained by applying any
- inference rule or definition, or by <a>merging</a> two statements to
+ inference rule or definition, or by <a title="unification">unifying</a> two terms or <a>merging</a> two statements to
enforce a uniqueness constraint.
</li>
- <li>Equivalence is <a>reflexive</a>, <a>symmetric</a>, and <a>transitive</a>.</li>
+ <li>Equivalence is <a>reflexive</a>, <a>symmetric</a>, and
+ <a>transitive</a>. (This is because a valid instance has a unique
+ normal form up to isomorphism [[DBCONSTRAINTS]]). </li>
</ul>
<p> An application that processes PROV data SHOULD handle
-equivalent instances in the same way. (Common exceptions to this rule
-include, for example, pretty-printers that seek to preserve the
-original order of statements in a file and avoid expanding
-inferences.) </p>
+equivalent instances in the same way. This guideline is necessarily
+imprecise because "in the same way" is application-specific.
+Common exceptions to this guideline
+include, for example, applications that pretty-print or digitally sign
+provenance, where the order and syntactic form of statements matters. </p>
</section>
@@ -4871,7 +4994,11 @@
-->
<!-- LocalWords: disjointness inferrable subtyping subtype subtypes hadMember
-->
-<!-- LocalWords: hasMember toplevel sameAs tuple acyclicity isomorphism
+<!-- LocalWords: hasMember toplevel sameAs tuple acyclicity isomorphism IRI
-->
-<!-- LocalWords: endBundle typeof equational acyclic invertible
+<!-- LocalWords: endBundle typeof equational acyclic invertible procedurally
-->
+<!-- LocalWords: implementers multi unifier ERCIM Groth Stian Soiland Ilkay
+ -->
+<!-- LocalWords: Altintas Reza
+ -->
--- a/model/prov-dm.html Wed Oct 31 13:09:26 2012 +0000
+++ b/model/prov-dm.html Wed Oct 31 13:10:51 2012 +0000
@@ -325,32 +325,32 @@
"PROV-PRIMER":
"Yolanda Gil and Simon Miles (eds.) Khalid Belhajjame, Helena Deus, Daniel Garijo, Graham Klyne, Paolo Missier, Stian Soiland-Reyes, and Stephan Zednik "+
"<a href=\"http://www.w3.org/TR/prov-primer/\"><cite>Prov Model Primer</cite></a>. "+
- "2011, Working Draft. "+
+ "2012, Working Draft. "+
"URL: <a href=\"http://www.w3.org/TR/prov-primer/\">http://www.w3.org/TR/prov-primer/</a>",
"PROV-O":
"Timothy Lebo, Satya Sahoo and Deborah McGuinness (eds.) Khalid Belhajjame, James Cheney, David Corsar, Daniel Garijo, Stian Soiland-Reyes, and Stephan Zednik "+
"<a href=\"http://www.w3.org/TR/prov-o/\"><cite>Provenance Formal Model</cite></a>. "+
- "2011, Working Draft. "+
+ "2012, Working Draft. "+
"URL: <a href=\"http://www.w3.org/TR/prov-o/\">http://www.w3.org/TR/prov-o/</a>",
"PROV-CONSTRAINTS":
"James Cheney, Paolo Missier, and Luc Moreau (eds.) "+
"<a href=\"http://www.w3.org/TR/prov-constraints/\"><cite>Constraints of the PROV Data Model</cite></a>. "+
- "2011, Working Draft. "+
+ "2012, Working Draft. "+
"URL: <a href=\"http://www.w3.org/TR/prov-constraints/\">http://www.w3.org/TR/prov-constraints/</a>",
"PROV-N":
"Luc Moreau and Paolo Missier (eds.) James Cheney, Stian Soiland-Reyes "+
"<a href=\"http://www.w3.org/TR/prov-n/\"><cite>PROV-N: The Provenance Notation</cite></a>. "+
- "2011, Working Draft. "+
+ "2012, Working Draft. "+
"URL: <a href=\"http://www.w3.org/TR/prov-n/\">http://www.w3.org/TR/prov-n/</a>",
"PROV-AQ":
"Graham Klyne and Paul Groth (eds.) Luc Moreau, Olaf Hartig, Yogesh Simmhan, James Meyers, Timothy Lebo, Khalid Belhajjame, and Simon Miles "+
"<a href=\"http://www.w3.org/TR/prov-aq/\"><cite>Provenance Access and Query</cite></a>. "+
- "2011, Working Draft. "+
+ "2012, Working Draft. "+
"URL: <a href=\"http://www.w3.org/TR/prov-aq/\">http://www.w3.org/TR/prov-aq/</a>",
"UML":
@@ -948,6 +948,8 @@
<p>
+The focus of derivation is on connecting a generated entity to a used
+entity.
While the basic idea is simple, the concept of derivation can be quite
subtle: implicit is the notion that the generated entity was affected
in some way by the used entity.
@@ -1103,10 +1105,14 @@
<p><a class="section-ref" href="#core-structures"><span>TBD</span></a> shows that seven concepts are mapped to binary relations in the core of PROV. However, some advanced uses of these concepts cannot be captured by a binary relation, but require relations to be expanded to n-ary relations.</p>
-
-<p>To illustrate expanded relations, we consider the concept of
-association, described
-in <a class="section-ref" href="#section-agents-attribution-association-delegation"><span>TBD</span></a>. Agents may rely on <em>plans</em>, i.e. sets of actions or steps, to achieve their
+<p>Indeed, binary relations are actually shorthands that can be 'opened up' by applications and filled in with further application details. For example, derivation is a very high level relationship between two entities: an application may decide to 'open up' that relationship in an expanded relation that describes how an entity was derived from another by virtue of listing the generation, usage, and activity involved in the 'WasDerivedFrom' relationship. Applications are free to decide which level of granularity they want describe, and PROV gives them the way to do that.</p>
+
+
+
+<p>To illustrate expanded relations, we revisit the concept of
+association, introduced
+in <a class="section-ref" href="#section-agents-attribution-association-delegation"><span>TBD</span></a> (full definition of the expanded association can be found
+in <a class="section-ref" href="#term-Association"><span>TBD</span></a>). Agents may rely on <em>plans</em>, i.e. sets of actions or steps, to achieve their
goals in the context of an activity.
Hence, an expanded form of
association relation allows for a plan to be specified. Plan is defined by subtyping and
@@ -1281,7 +1287,7 @@
<p>
An activity with identifier <span class="name">a1</span> and an attribute <span class="name">type</span> with value <span class="name">createFile</span>.
<pre class="codeexample" >
-activity(a1, [prov:type="createFile"])
+activity(a1, [ prov:type="createFile" ])
</pre>
Two entities with identifiers <span class="name">e1</span> and <span class="name">e2</span>.
<pre class="codeexample" >
@@ -1290,13 +1296,13 @@
</pre>
The activity <span class="name">a1</span> used <span class="name">e1</span>, and <span class="name">e2</span> was generated by <span class="name">a1</span>.
<pre class="codeexample" >
-used(a1,e1)
-wasGeneratedBy(e2,a1)
+used(a1, e1)
+wasGeneratedBy(e2, a1)
</pre>
The same descriptions, but with an explicit identifier <span class="name">u1</span> for the usage, and the syntactic marker '<span class="name">-</span>' to mark the absence of identifier in the generation. Both are followed by '<span class="name">;</span>'.
<pre class="codeexample" >
-used(u1;a1,e1)
-wasGeneratedBy(-;e2,a1)
+used(u1; a1, e1)
+wasGeneratedBy(-; e2, a1)
</pre>
</div>
@@ -1354,11 +1360,11 @@
<li>There was an editing activity.
<pre>
-activity(ex:edit1,[prov:type="edit"])
+activity(ex:edit1, [ prov:type="edit" ])
</pre>
</li>
-<li>The document was generated by the editing activity: this was a <a title="concept-generation">Generation</a>.
+<li>The document was generated by the editing activity: this was a <a title="concept-generation">Generation</a>. Its time is not specified, hence, the marker '-'.
<pre>
wasGeneratedBy(tr:WD-prov-dm-20111215, ex:edit1, -)
</pre>
@@ -1372,7 +1378,7 @@
</pre>
</li>
-<li>Agents were assigned various responsibilities in the editing activity: contributor and editor.
+<li>Agents were assigned various responsibilities in the editing activity: contributor and editor. The plan the agent relied upon is not specified, hence, the marker '-'.
<pre>
wasAssociatedWith(ex:edit1, ex:Paolo, -, [ prov:role="editor" ])
wasAssociatedWith(ex:edit1, ex:Simon, -, [ prov:role="contributor" ])
@@ -1445,11 +1451,11 @@
</li>
<li>There was a publication activity.
<pre>
-activity(ex:act2,[prov:type="publish"])
+activity(ex:act2, [ prov:type="publish" ])
</pre>
</li>
-<li>The document was generated by the publication activity: this was a <a title="concept-Generation">Generation</a>.
+<li>The document was generated by the publication activity: this was a <a title="concept-Generation">Generation</a>. Its time is not specified, hence, the marker '-'.
<pre>
wasGeneratedBy(tr:WD-prov-dm-20111215, ex:act2, -)
</pre>
@@ -1462,7 +1468,7 @@
</pre>
</li>
-<li>The activity required a publication request: this was a <a title="concept-Usage">Usage</a>.
+<li>The activity required a publication request: this was a <a title="concept-Usage">Usage</a>. Its time is not specified, hence, the marker '-'.
<pre>
used(ex:act2, email:2011Dec/0111, -)
</pre>
@@ -1522,10 +1528,10 @@
<p>To express their respective provenance, these bundles must be seen as entities, and all PROV constructs are now available to express their provenance. In the example below, <span class="name">ex:author-view</span> is attributed to the agent <span class="name">ex:Simon</span>, whereas <span class="name">ex:process-view</span> to <span class="name">w3:Consortium</span>.
<pre class="codeexample">
-entity(ex:author-view, [prov:type='prov:Bundle' ])
+entity(ex:author-view, [ prov:type='prov:Bundle' ])
wasAttributedTo(ex:author-view, ex:Simon)
-entity(ex:process-view, [prov:type='prov:Bundle' ])
+entity(ex:process-view, [ prov:type='prov:Bundle' ])
wasAttributedTo(ex:process-view, w3:Consortium)
</pre>
@@ -1612,11 +1618,11 @@
<div id="secondary-elements-relations-at-a-glance-div" style="text-align: center;">
<table class="thinborder" style="margin-left: auto; margin-right: auto;">
<caption id="secondary-elements-relations-at-a-glance">Secondary optional elements in PROV-DM Relations</caption> <!-- Table 4 -->
-<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td colspan="6">Secondary Object</td></tr>
+<tr><td style="border-width: 0px; "></td><td style="border-width: 0px;§> "></td><td colspan="6">Secondary Object</td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td>Entity</td><td>Activity</td><td >Agent</td></tr>
-<tr><td rowspan="3">Subject</td><td>Entity</td><td class="component5-color"><a>MentionOf</a> (bundle)</td><td class="component2-color"><a >WasDerivedFrom</a> (activity)<br><a>Revision (activity)</a><br><a>Quotation (activity)</a><br><a>PrimarySource (activity)</a></td><td colspan="2">—</td></tr>
-<tr><td>Activity</td><td class="component3-color"><a>WasAssociatedWith</a> (plan)</td><td class="component1-color"><a>WasStartedBy</a> (starter)<br><a>WasEndedBy</a> (ender)</td><td colspan="2">—</td></tr>
-<tr><td>Agent</td><td>—</td><td class="component3-color"><a>ActedOnBehalfOf</a> (activity)</td><td>—</td></tr>
+<tr><td rowspan="3">Subject</td><td>Entity</td><td class="component5-color"><a>MentionOf</a> (<a href="#mention.bundle">bundle</a>)</td><td class="component2-color"><a >WasDerivedFrom</a> (<a href="#derivation.activity">activity</a>)</td><td colspan="2">—</td></tr>
+<tr><td>Activity</td><td class="component3-color"><a>WasAssociatedWith</a> (<a href="#association.plan">plan</a>)</td><td class="component1-color"><a>WasStartedBy</a> (<a href="#start.starter">starter</a>)<br><a>WasEndedBy</a> (<a href="#end.ender">ender</a>)</td><td colspan="2">—</td></tr>
+<tr><td>Agent</td><td>—</td><td class="component3-color"><a>ActedOnBehalfOf</a> (<a href="#delegation.activity">activity</a>)</td><td>—</td></tr>
</table>
</div>
@@ -1711,7 +1717,7 @@
<p><div class="attributes" id="attributes-entity">An <dfn title="dfn-Entity" id="dfn-entity">entity</dfn><span class="withPn">, written <span class="pnExpression" id="pn-entity">entity(id, [attr1=val1, ...])</span> in PROV-N, </span> has:
<ul>
<li><span class='attribute' id="entity.id">id</span>: an identifier for an entity; </li>
-<li><span class='attribute' id="entity.attributes">attributes</span>: an OPTIONAL set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this entity.</li>
+<li><span class='attribute' id="entity.attributes">attributes</span>: an OPTIONAL set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about the fixed aspects of this entity.</li>
</ul></div>
<div class="anexample" id="anexample-entity">
@@ -1755,7 +1761,7 @@
<p>
The following expression</p>
<pre class="codeexample">
-activity(a1,2011-11-16T16:05:00,2011-11-16T16:06:00,
+activity(a1, 2011-11-16T16:05:00, 2011-11-16T16:06:00,
[ ex:host="server.example.org", prov:type='ex:edit' ])
</pre>
<p>states the existence of an activity with identifier <span class="name">a1</span>, start time <span class="name">2011-11-16T16:05:00</span>, and end time <span
@@ -1780,6 +1786,9 @@
<div class="glossary-ref" data-ref="glossary-generation"></div>
+<p>Given that a generation is the completion of production of an entity,
+it is instantaneous.</p>
+
<p>
<div class="attributes" id="attributes-generation"><dfn title="wasGeneratedBy">Generation</dfn><span class="withPn">, written <span class="pnExpression">wasGeneratedBy(id; e, a, t, attrs)</span> in PROV-N,</span> has:
<ul>
@@ -1829,6 +1838,8 @@
<p><span class="glossary-ref" data-ref="glossary-usage"></span> (Note: This definition is formulated for a given usage; it is permitted for an activity to have used a same entity multiple times.)</p>
+<p>Given that a usage is the beginning of utilizing an entity, it is
+instantaneous.</p>
<p><div class="attributes" id="attributes-usage"><dfn title="used">Usage</dfn><span class="withPn">, written <span class="pnExpression">used(id; a, e, t, attrs)</span> in PROV-N,</span> has:
<ul>
@@ -1907,6 +1918,8 @@
<div class="glossary-ref" data-ref="glossary-start"></div>
+<p>Given that a start is when an activity is deemed to have started, it
+is instantaneous.</p>
<p><div class="attributes" id="attributes-start">An activity <dfn title="wasStartedBy">start</dfn><span class="withPn">, written <span class="pnExpression">wasStartedBy(id; a2, e, a1, t, attrs)</span> in PROV-N,</span> has:
<ul>
@@ -1988,6 +2001,8 @@
<div class="glossary-ref" data-ref="glossary-end"></div>
+<p>Given that an end is when an activity is deemed to have ended, it is
+instantaneous.</p>
<p><div class="attributes" id="attributes-end">An activity <dfn title="wasEndedBy">end</dfn><span class="withAsn">, written <span class="pnExpression">wasEndedBy(id; a2, e, a1, t, attrs)</span> in PROV-N,</span> has:
<ul>
@@ -2020,7 +2035,8 @@
<div class="glossary-ref" data-ref="glossary-invalidation"></div>
-
+<p>Given that an invalidation is the start of destruction, cessation, or
+expiry, it is instantaneous.</p>
<p>
Entities have a duration. Generation marks the beginning of an entity, whereas invalidation marks its end.
@@ -2158,7 +2174,7 @@
<p>According to <a href="#section-prov-overview">Section 2</a>, for an entity to be transformed from, created from, or resulting from an update to another, there must be some
-underpinning activities performing the necessary actions resulting in such a derivation.
+underpinning activity or activities performing the necessary action(s) resulting in such a derivation.
A derivation can be described at various levels of precision. In its simplest form, derivation relates two entities. Optionally, attributes can be added to represent further information about the derivation. If the derivation is the result of a single known activity, then this activity can also be optionally expressed. To provide a completely accurate description of the derivation, the generation and usage of the generated and used entities, respectively, can be provided, so as to make the derivation path, through usage, activity, and generation, explicit. Optional information such as activity, generation, and usage can be linked to derivations to aid analysis of provenance and to facilitate provenance-based reproducibility. </p>
@@ -2373,6 +2389,9 @@
<div class="glossary-ref" data-ref="glossary-agent"></div>
+<p>An agent may be a particular type of entity or activity. This means that the model can be
+ used to express provenance of the agents themselves. </p>
+
<p><div class="attributes" id="attributes-agent">An <dfn title="dfn-agent" id="dfn-agent">agent</dfn><span class="withPn">, written <span class="pnExpression" id="pn-agent">agent(id, [attr1=val1, ...])</span> in PROV-N,</span> has:
<ul>
@@ -2705,7 +2724,7 @@
<p>
-A bundle description is of the form <span class="pnExpression">entity(id,[prov:type='prov:Bundle', attr1=val1, ...])</span>
+A bundle description is of the form <span class="pnExpression">entity(id, [ prov:type='prov:Bundle', attr1=val1, ...] )</span>
where <span class='name'>id</span> is an identifier denoting a bundle,
a type <span>prov:Bundle</span> and
an OPTIONAL set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this bundle.
@@ -2750,7 +2769,7 @@
<p>The first bundle contains the descriptions corresponding to Bob observing the creation of <span class="name">ex:report1</span>. Its provenance can be described as follows.</p>
<pre class="codeexample">
-entity(bob:bundle1, [prov:type='prov:Bundle'])
+entity(bob:bundle1, [ prov:type='prov:Bundle' ])
wasGeneratedBy(bob:bundle1, -, 2012-05-24T10:30:00)
wasAttributedTo(bob:bundle1, ex:Bob)
</pre>
@@ -2844,6 +2863,9 @@
</ul>
</div>
+<p>Specialization is not defined as Influence, and therefore does not have an id and attributes.</p>
+
+
<div class="anexample" id="anexample-specialization">
<p>
@@ -2872,7 +2894,6 @@
<span class="glossary-ref" data-ref="glossary-alternate"></span>
-
<p><div class="attributes" id="attributes-alternate">An <dfn title="alternateOf">alternate</dfn> relation<span class="withPn">, written <span class="pnExpression">alternateOf(e1, e2)</span> in PROV-N,</span> has:
<ul>
@@ -2881,6 +2902,19 @@
</ul>
</div>
+<p>Alternate is not defined as Influence, and therefore does not have an id and attributes.</p>
+
+<p>
+Note that <a title="alternateOf">alternateOf</a> is a necessarily very general
+relationship that, in reasoning, only states that the two
+alternate entities fix different aspects of some common thing
+(possibly evolving over time), and so there is some relevant
+connection between the provenance of the alternates. In a
+specific application context, <a title="alternateOf">alternateOf</a>, or a subtype of it,
+could allow more inferences.
+</p>
+
+
<div class="anexample" id="anexample-alternate">
<p>
A given news item on the BBC News site
@@ -2904,7 +2938,7 @@
<pre class="codeexample">
entity(tr:WD-prov-dm-20111018)
entity(tr:WD-prov-dm-20111215)
-alternateOf(tr:WD-prov-dm-20111018,tr:WD-prov-dm-20111215)
+alternateOf(tr:WD-prov-dm-20111018, tr:WD-prov-dm-20111215)
</pre>
<p>They are both specialization of the page <a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a>.</p>
</div>
@@ -2952,6 +2986,7 @@
+
<p><div class="attributes" id="attributes-mention">A <dfn title="mentionOf">mention</dfn> relation<span class="withPn">, written <span class="pnExpression">mentionOf(infra, supra, b)</span> in PROV-N,</span> has:
<ul>
<li><span class='attribute' id="mention.specificEntity">specificEntity</span>: an identifier (<span class="name">infra</span>)
@@ -2961,6 +2996,8 @@
</ul>
</div>
+<p>Mention is not defined as Influence, and therefore does not have an id and attributes.</p>
+
<div class="anexample" id="anexample-mention-rating">
<p>This example is concerned with a performance rating tool that reads and processes provenance to determine the performance of agents. To keep the example simple, an agent's performance is determined by the duration of the activities it is associated with. </p>
<p>As an illustration, we consider that two bundles <span class="name">ex:run1</span> and <span class="name">ex:run2</span> refer to an agent <span class="name">ex:Bob</span> that controlled two activities <span class="name">ex:a1</span> and <span class="name">ex:a2</span>. </p>
@@ -2994,10 +3031,10 @@
<p>Consider the following bundle of descriptions, in which derivation and generations have been identified.
<pre class="codeexample">
bundle obs:bundle1
- entity(ex:report1, [prov:type="report", ex:version=1])
- wasGeneratedBy(ex:g1; ex:report1,-,2012-05-24T10:00:01)
- entity(ex:report2, [prov:type="report", ex:version=2])
- wasGeneratedBy(ex:g2; ex:report2,-,2012-05-25T11:00:01)
+ entity(ex:report1, [ prov:type="report", ex:version=1 ])
+ wasGeneratedBy(ex:g1; ex:report1, -, 2012-05-24T10:00:01)
+ entity(ex:report2, [ prov:type="report", ex:version=2 ])
+ wasGeneratedBy(ex:g2; ex:report2, -, 2012-05-25T11:00:01)
wasDerivedFrom(ex:report2, ex:report1)
endBundle
entity(obs:bundle1, [ prov:type='prov:Bundle' ])
@@ -3009,10 +3046,10 @@
entity(tool:bundle2, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
wasAttributedTo(tool:bundle2, viz:Visualizer)
- entity(tool:report1, [viz:color="orange"])
+ entity(tool:report1, [ viz:color="orange" ])
mentionOf(tool:report1, ex:report1, obs:bundle1)
- entity(tool:report2, [viz:color="blue"])
+ entity(tool:report2, [ viz:color="blue" ])
mentionOf(tool:report2, ex:report2, obs:bundle1)
endBundle
</pre>
@@ -3075,8 +3112,8 @@
<div class="anexample">
<pre class="codeexample">
-entity(c0, [prov:type='prov:EmptyCollection' ]) // c0 is an empty collection
-entity(c1, [prov:type='prov:Collection' ]) // c1 is a collection, with unknown content
+entity(c0, [ prov:type='prov:EmptyCollection' ]) // c0 is an empty collection
+entity(c1, [ prov:type='prov:Collection' ]) // c1 is a collection, with unknown content
</pre>
</div>
@@ -3101,6 +3138,8 @@
</div>
+<p>Membership is not defined as Influence, and therefore does not have an id and attributes.</p>
+
<div class="anexample" >
<p>In this example, <span class="name">c</span> is a collection known to have <span class="name">e0</span>, <span class="name">e1</span>, and <span class="name">e2</span> as members, and may have other members.</p>
@@ -3144,6 +3183,10 @@
name</a>.
</p>
+<p><a>Entity</a>, <a>Activity</a>, and <a>Agent</a> have a mandatory identifier. Two entities (resp. activities, agents) are equal if they have the same identifier.</p>
+
+<p><a>Generation</a>, <a>Usage</a>, <a>Communication</a>, <a>Start</a>, <a>End</a>, <a>Invalidation</a>, <a>Derivation</a>, <a>Attribution</a>, <a>Association</a>, <a>Delegation</a>, <a>Influence</a> have an optional identifier. Two generations (resp. usages, communications, etc.) are equal if they have the same identifier.
+
</section>
<section id="term-attribute">
@@ -3292,7 +3335,7 @@
<p>The attribute <span class="name">prov:value</span> is an OPTIONAL attribute of entity. The value associated with the attribute <span class="name">prov:value</span> MUST be a PROV-DM <a title="value">Value</a>. The attribute <span class="name">prov:value</span> MAY occur at most once in a set of attribute-value pairs.</p>
-<div class="anexample">
+<div class="anexample" id="anexample-value1">
<p>The following example illustrates the provenance of the number <span class="name">4</span> obtained by an activity that computed the length of an input string <span class="name">"abcd"</span>.
The input and the output are expressed as entities <span class="name">ex:in</span> and <span class="name">ex:out</span>, respectively. They each have a <span class="name">prov:value</span> attribute associated with the corresponding value.
</p>
@@ -3306,6 +3349,28 @@
</pre>
</div>
+<p>
+Two different entities MAY have the same value for the attribute
+prov:value. For instance,
+when two entities, with the same prov:value, are generated by two
+different activities, as illustrated
+by the following example.</p>
+
+<div class="anexample" id="anexample-value2">
+<p><a href="#anexample-value1" class="anexample-ref"><span>Example REF</span></a> illustrates an entity with a given value
+ <span class="name">4</span>. This examples shows that another entity with the same value may be computed differently (by an addition).
+</p>
+<pre class="codeexample">
+entity(ex:in1, [ prov:value=3 ])
+entity(ex:in2, [ prov:value=1 ])
+entity(ex:out2, [ prov:value=4 ]) // ex:out2 also has value 4
+activity(ex:add1, [ prov:type="addition" ])
+used(ex:add1, ex:in1)
+used(ex:add1, ex:in2)
+wasGeneratedBy(ex:out2, ex:add1)
+</pre>
+</div>
+
</section>
@@ -3851,6 +3916,20 @@
<li> <a href="http://www.w3.org/2011/prov/track/issues/519">ISSUE-519</a>, <a href="http://www.w3.org/2011/prov/track/issues/523">ISSUE-523</a>, <a href="http://www.w3.org/2011/prov/track/issues/524">ISSUE-524</a>, <a href="http://www.w3.org/2011/prov/track/issues/529">ISSUE-529</a>: changed UML diagram of figure 8 by removing explicit inheritance from influence for usage, start, end, generation, invalidation, communication, derivation, attribution, association, and delegation. Instead, introduced correspondance table 7. Furthermore, in response to these issues, it was made clear that PROV defines no attribute specific to subtypes such as SoftwareAgent, ..., Plan, Revision, Bundle, Collection.
<li> <a href="http://www.w3.org/2011/prov/track/issues/495">ISSUE-495</a>: made explicit which section, figure, table was informative or normative.
<li> <a href="http://www.w3.org/2011/prov/track/issues/521">ISSUE-521</a>: now states that "an agent relied on a plan" instead of "an agent adopted a plan".
+<li> <a href="http://www.w3.org/2011/prov/track/issues/499">ISSUE-499</a>: Made explicit that generation/usage/invalidation/start/end are implicit.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/449">ISSUE-449</a>: Clarified definition of prov:value attribute and added an example.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/495">ISSUE-495</a>: added paragraph about 'relations opening up'. Clarified the role of '-' in example. Fixed dates in biblio. Fixed space issue in prov-n examples
+<li> <a href="http://www.w3.org/2011/prov/track/issues/516">ISSUE-516</a>: Stating that there moust be some underpinning activity or activities for a derivation, instead of just activities.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/525">ISSUE-525</a>: Made it explicit that Membership, Alternate, Specialization are not Influence
+<li> Copied the sentence " An agent may be a particular type of entity or activity. This means that the model can be
+ used to express provenance of the agents themselves. " from the informative section into the normative section.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/504">ISSUE-504</a>: Updated definition of collection.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/503">ISSUE-503</a>: Rephrased the introduction of expanded association in section 2.2.1.2 Expanded Relations.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/514">ISSUE-514</a>: added links to the attributes listed in the secondary element table. Also removed PrimarySource, Quotation, Revision.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/502">ISSUE-502</a>: Added sentence in section 2.1.2 explaining that the focus
+ of derivation is on connecting a generated entity to a used entity.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/526">ISSUE-526</a>: Added sentence clarifying sentence in section 5.5.2.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/462">ISSUE-462</a>: Added clarification regarding entity attributes (with respect to fixed aspects) and role of identifier with respect to equality.
</ul>
</section>
--- a/model/prov-n.html Wed Oct 31 13:09:26 2012 +0000
+++ b/model/prov-n.html Wed Oct 31 13:10:51 2012 +0000
@@ -216,6 +216,10 @@
"2011, Working Draft. "+
"URL: <a href=\"http://www.w3.org/TR/prov-aq/\">http://www.w3.org/TR/prov-aq/</a>",
+ "UNICODE" :
+ "The Unicode Consortium. "+
+ " <a href=\"http://www.unicode.org/unicode/standard/versions/enumeratedversions.html\"><cite>The Unicode Standard.</cite></a>. " +
+ " Defined by: The Unicode Standard, Version 6.2.0, (Mountain View, CA: The Unicode Consortium, 2012. ISBN 978-1-936213-07-8) , 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> ",
"UNISEC":
" Mark Davis and Michel Suignard. " +
"<a href=\"http://www.unicode.org/reports/tr36/\"><cite>Unicode Security Considerations<cite></a>. " +
@@ -2451,12 +2455,12 @@
<dt>Subtype name:</dt>
<dd>provenance-notation</dd>
<dt>Required parameters:</dt>
- <dd>None</dd>
+ <dd><kbd>charset</kbd> — the value of <kbd>charset</kbd> MUST always be <kbd>UTF-8</kbd>.</dd>
<dt>Optional parameters:</dt>
- <dd><kbd>charset</kbd> — this parameter is mandatory. The value of <kbd>charset</kbd> is always <kbd>UTF-8</kbd>.</dd>
-
- <dt>Encoding considerations:</dt>
- <dd>The syntax of PROV-N is expressed over code points in Unicode [[UNICODE5]]. The encoding is always UTF-8 [[!UTF-8]].</dd>
+ <dd>None</dd>
+
+ <dt>Encoding considerations: 8bit</dt>
+ <dd>The syntax of PROV-N is expressed over code points in Unicode [[!UNICODE]]. The encoding is always UTF-8 [[!UTF-8]].</dd>
<dd>Unicode code points may also be expressed using an \uXXXX (U+0 to U+FFFF) or \UXXXXXXXX syntax (for U+10000 onwards) where X is a hexadecimal digit [0-9A-F]</dd>
<dt>Security considerations:</dt>
<dd>PROV-N is a general-purpose language for describing the provenance of things; applications may evaluate given data to infer more descriptions or to dereference URIs, invoking the security considerations of the scheme for that URI. Note in particular, the privacy issues in [[!RFC3023]] section 10 for HTTP URIs. Data obtained from an inaccurate or malicious data source may lead to inaccurate or misleading conclusions, as well as the dereferencing of unintended URIs. Care must be taken to align the trust in consulted resources with the sensitivity of the intended use of the data.</dd>
@@ -2486,7 +2490,7 @@
<dd>PROV-N: The Provenance Notation, Moreau, Missier, (eds), Cheney, Soiland-Reyes
<a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a></dd>
<dt>Applications which use this media type:</dt>
- <dd>No widely deployed applications are known to use this media type. It may be used by some web services and clients consuming their data.</dd>
+ <dd>It may be used by any application for publishing provenance information. This format is designed to be a human-readable form of provenance. </dd>
<dt>Additional information:</dt>
<dt>Magic number(s):</dt>
<dd>PROV-N documents may have the strings 'document' near the beginning of the document.</dd>
@@ -2497,7 +2501,7 @@
<dt>Macintosh file type code(s):</dt>
<dd>"TEXT"</dd>
<dt>Person & email address to contact for further information:</dt>
- <dd>public-prov-comments@w3.org</dd>
+ <dd>Ivan Herman, ivan@w3.org</dd>
<dt>Intended usage:</dt>
<dd>COMMON</dd>
<dt>Restrictions on usage:</dt>
@@ -2526,10 +2530,11 @@
<h2>Changes since last version</h2>
<p>
<ul>
-<li> <a href="http://www.w3.org/2011/prov/track/issues/543">ISSUE-543</a>: uses key-entity pair terminology for example 43.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/538">ISSUE-538</a>: rephrasing of text in example 10.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/547">ISSUE-547</a>: aligned terminology and productions with prov-constraints document, renaming 'toplevel bundle' to 'document', and renaming 'named bundle' to 'bundle'.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/543">ISSUE-543</a>: Uses key-entity pair terminology for example 43.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/538">ISSUE-538</a>: Rephrasing of text in example 10.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/547">ISSUE-547</a>: Aligned terminology and productions with prov-constraints document, renaming 'toplevel bundle' to 'document', and renaming 'named bundle' to 'bundle'.
<li> <a href="http://www.w3.org/2011/prov/track/issues/496">ISSUE-496</a>: For each prov-n term, added a cross-reference to corresponding prov-dm term (see table following each production). Rephrased text related to scope of a namespace declaration. Added an informative file with all productions.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/573">ISSUE-573</a>: Updated Media Type section.
</ul>
</section>
--- a/ontology/ProvenanceOntology.owl Wed Oct 31 13:09:26 2012 +0000
+++ b/ontology/ProvenanceOntology.owl Wed Oct 31 13:10:51 2012 +0000
@@ -94,17 +94,14 @@
<rdfs:subPropertyOf rdf:resource="&rdfs;seeAlso"/>
<rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
</owl:AnnotationProperty>
-
<owl:AnnotationProperty rdf:about="http://www.w3.org/ns/prov#category">
<rdfs:comment xml:lang="en">Classify prov-o terms into three categories, including 'starting-point', 'qualifed', and 'extended'. This classification is used by the prov-o html document to gently introduce prov-o terms to its users. </rdfs:comment>
<rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
</owl:AnnotationProperty>
-
<owl:AnnotationProperty rdf:about="http://www.w3.org/ns/prov#order">
<rdfs:comment xml:lang="en">The position that this OWL term should be listed within documentation. The scope of the documentation (e.g., among all terms, among terms within a prov:category, among properties applying to a particular class, etc.) is unspecified.</rdfs:comment>
<rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
</owl:AnnotationProperty>
-
<owl:AnnotationProperty rdf:about="&rdfs;isDefinedBy"/>
<owl:AnnotationProperty rdf:about="http://www.w3.org/ns/prov#editorsDefinition">
<rdfs:comment xml:lang="en">When the prov-o term does not have a definition drawn from prov-dm, and the prov-o editor provides one.</rdfs:comment>
@@ -201,12 +198,12 @@
<owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#agent">
<rdfs:label>agent</rdfs:label>
+ <editorsDefinition xml:lang="en">The property prov:agent describes an prov:Agent which influenced a resource. This property applies to an prov:AgentInfluence, which is given by prov:qualifiedInfluence or its subproperties from the influenced prov:Entity, prov:Activity or prov:Agent.</editorsDefinition>
<category>qualified</category>
<component>alternate</component>
<inverse>agentOfInfluence</inverse>
<rdfs:comment xml:lang="en">The property used by a prov:AgentInfluence to cite the Agent that influenced an Entity, Activity, or Agent. It can be used to express the agent involved in being responsible for an activity, being attributed to an entity, starting or ending an activity, or being responsible for another subordinate agent in an activity.</rdfs:comment>
<editorialNote xml:lang="en">This property behaves in spirit like rdf:object; it references the object of a prov:wasInfluencedBy triple.</editorialNote>
- <editorsDefinition xml:lang="en">The property prov:agent describes an prov:Agent which influenced a resource. This property applies to an prov:AgentInfluence, which is given by prov:qualifiedInfluence or its subproperties from the influenced prov:Entity, prov:Activity or prov:Agent.</editorsDefinition>
<rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
<rdfs:range rdf:resource="http://www.w3.org/ns/prov#Agent"/>
<rdfs:domain rdf:resource="http://www.w3.org/ns/prov#AgentInfluence"/>
@@ -258,13 +255,14 @@
<owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#atLocation">
<rdfs:label>atLocation</rdfs:label>
<rdfs:comment xml:lang="en">The Location of any resource.</rdfs:comment>
+ <inverse>locationOf</inverse>
<editorialNote xml:lang="en">The naming of prov:atLocation parallels prov:atTime, and is not named prov:hadLocation to avoid conflicting with the convention that prov:had* properties are used on prov:Influence classes.</editorialNote>
- <inverse>locationOf</inverse>
+ <rdfs:comment>This property has multiple RDFS domains to suit multiple OWL Profiles. See <a href="#prov-o-owl-profile">PROV-O OWL Profile</a>.</rdfs:comment>
<editorialNote xml:lang="en">This property is not functional because the many values could be at a variety of granularies (In this building, in this room, in that chair).</editorialNote>
<category>expanded</category>
<rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
+ <rdfs:range rdf:resource="http://www.w3.org/ns/prov#Location"/>
<sharesDefinitionWith rdf:resource="http://www.w3.org/ns/prov#Location"/>
- <rdfs:range rdf:resource="http://www.w3.org/ns/prov#Location"/>
<rdfs:domain>
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
@@ -318,6 +316,7 @@
<owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#hadActivity">
<rdfs:label>hadActivity</rdfs:label>
+ <rdfs:comment>This property has multiple RDFS domains to suit multiple OWL Profiles. See <a href="#prov-o-owl-profile">PROV-O OWL Profile</a>.</rdfs:comment>
<rdfs:comment xml:lang="en">The _optional_ Activity of an Influence, which used, generated, invalidated, or was the responsibility of some Entity. This property is _not_ used by ActivityInfluence (use prov:activity instead).</rdfs:comment>
<editorialNote xml:lang="en">The multiple rdfs:domain assertions are intended. One is simpler and works for OWL-RL, the union is more specific but is not recognized by OWL-RL.</editorialNote>
<component>derivations</component>
@@ -430,6 +429,7 @@
<component>agents-responsibility</component>
<editorsDefinition xml:lang="en">prov:hadRole references the Role (i.e. the function of an entity with respect to an activity), in the context of an instantaneous usage, generation, association, start, and end.</editorsDefinition>
<inverse>wasRoleIn</inverse>
+ <rdfs:comment>This property has multiple RDFS domains to suit multiple OWL Profiles. See <a href="#prov-o-owl-profile">PROV-O OWL Profile</a>.</rdfs:comment>
<category>qualified</category>
<rdfs:comment xml:lang="en">The _optional_ Role that an Entity assumed in the context of an Activity. For example, :baking prov:used :spoon; prov:qualified [ a prov:Usage; prov:entity :spoon; prov:hadRole roles:mixing_implement ].</rdfs:comment>
<rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
@@ -961,6 +961,7 @@
<owl:ObjectProperty rdf:about="http://www.w3.org/ns/prov#wasInfluencedBy">
<rdfs:label>wasInfluencedBy</rdfs:label>
+ <rdfs:comment>This property has multiple RDFS domains to suit multiple OWL Profiles. See <a href="#prov-o-owl-profile">PROV-O OWL Profile</a>.</rdfs:comment>
<rdfs:comment>Because prov:wasInfluencedBy is a broad relation, the more specific relations (prov:wasInformedBy, prov:actedOnBehalfOf, prov:endedBy, etc.) should be used when applicable.</rdfs:comment>
<editorialNote xml:lang="en">The sub-properties of prov:wasInfluencedBy can be elaborated in more detail using the Qualification Pattern. For example, the binary relation :baking prov:used :spoon can be qualified by asserting :baking prov:qualifiedUsage [ a prov:Usage; prov:entity :spoon; prov:atLocation :kitchen ] .
@@ -993,9 +994,9 @@
</rdfs:domain>
</owl:ObjectProperty>
<owl:Axiom>
+ <definition>influencee: an identifier (o2) for an entity, activity, or agent; </definition>
<dm>http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html#term-influence</dm>
- <definition>influencer: an identifier (o1) for an ancestor entity, activity, or agent that the former depends on;</definition>
- <owl:annotatedProperty rdf:resource="&rdfs;range"/>
+ <owl:annotatedProperty rdf:resource="&rdfs;domain"/>
<owl:annotatedSource rdf:resource="http://www.w3.org/ns/prov#wasInfluencedBy"/>
<owl:annotatedTarget>
<owl:Class>
@@ -1009,8 +1010,8 @@
</owl:Axiom>
<owl:Axiom>
<dm>http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html#term-influence</dm>
- <definition>influencee: an identifier (o2) for an entity, activity, or agent; </definition>
- <owl:annotatedProperty rdf:resource="&rdfs;domain"/>
+ <definition>influencer: an identifier (o1) for an ancestor entity, activity, or agent that the former depends on;</definition>
+ <owl:annotatedProperty rdf:resource="&rdfs;range"/>
<owl:annotatedSource rdf:resource="http://www.w3.org/ns/prov#wasInfluencedBy"/>
<owl:annotatedTarget>
<owl:Class>
@@ -1608,7 +1609,7 @@
<definition xml:lang="en">A location can be an identifiable geographic place (ISO 19112), but it can also be a non-geographic place such as a directory, row, or column. As such, there are numerous ways in which location can be expressed, such as by a coordinate, address, landmark, and so forth.</definition>
<category>expanded</category>
<rdfs:isDefinedBy rdf:resource="http://www.w3.org/ns/prov#"/>
- <rdfs:seeAlso rdf:resource="http://www.w3.org/ns/prov#hadLocation"/>
+ <rdfs:seeAlso rdf:resource="http://www.w3.org/ns/prov#atLocation"/>
</owl:Class>
--- a/ontology/prov-o-html-sections/description-starting-points.inc.html Wed Oct 31 13:09:26 2012 +0000
+++ b/ontology/prov-o-html-sections/description-starting-points.inc.html Wed Oct 31 13:10:51 2012 +0000
@@ -21,7 +21,7 @@
By applying usage and generation, one can construct provenance chains comprising both Activities and Entities.
</p>
- <p>In addiition, we can say that an Activity <a href='#wasInformedBy' class="qname">prov:wasInformedBy</a>
+ <p>In addition, we can say that an Activity <a href='#wasInformedBy' class="qname">prov:wasInformedBy</a>
another Activity to provide some dependency information without explicitly providing the activities' start and end times.
A <span class="repeated">prov:wasInformedBy</span> relation between Activities suggests that the informed Activity used an Entity that was generated by the informing
Activity, but the Entity itself is not interesting or is unknown.
--- a/ontology/prov.ttl Wed Oct 31 13:09:26 2012 +0000
+++ b/ontology/prov.ttl Wed Oct 31 13:10:51 2012 +0000
@@ -277,7 +277,7 @@
a owl:Class ;
rdfs:isDefinedBy <http://www.w3.org/ns/prov#> ;
rdfs:label "Location" ;
- rdfs:seeAlso :hadLocation ;
+ rdfs:seeAlso :atLocation ;
:category "expanded" ;
:definition "A location can be an identifiable geographic place (ISO 19112), but it can also be a non-geographic place such as a directory, row, or column. As such, there are numerous ways in which location can be expressed, such as by a coordinate, address, landmark, and so forth."@en ;
:dm "http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html#term-attribute-location"^^xsd:anyURI ;
@@ -450,6 +450,7 @@
:category "qualified" ;
:component "alternate" ;
:editorialNote "This property behaves in spirit like rdf:object; it references the object of a prov:wasInfluencedBy triple."@en ;
+ :editorsDefinition "The property prov:agent describes an prov:Agent which influenced a resource. This property applies to an prov:AgentInfluence, which is given by prov:qualifiedInfluence or its subproperties from the influenced prov:Entity, prov:Activity or prov:Agent."@en ;
:inverse "agentOfInfluence" ;
:sharesDefinitionWith :AgentInfluence .
@@ -488,7 +489,7 @@
:atLocation
a owl:ObjectProperty ;
- rdfs:comment "The Location of any resource."@en ;
+ rdfs:comment "The Location of any resource."@en, "This property has multiple RDFS domains to suit multiple OWL Profiles. See <a href=\"#prov-o-owl-profile\">PROV-O OWL Profile</a>." ;
rdfs:domain [
a owl:Class ;
owl:unionOf (:Activity
@@ -608,7 +609,7 @@
:hadActivity
a owl:ObjectProperty ;
- rdfs:comment "The _optional_ Activity of an Influence, which used, generated, invalidated, or was the responsibility of some Entity. This property is _not_ used by ActivityInfluence (use prov:activity instead)."@en ;
+ rdfs:comment "The _optional_ Activity of an Influence, which used, generated, invalidated, or was the responsibility of some Entity. This property is _not_ used by ActivityInfluence (use prov:activity instead)."@en, "This property has multiple RDFS domains to suit multiple OWL Profiles. See <a href=\"#prov-o-owl-profile\">PROV-O OWL Profile</a>." ;
rdfs:domain :Influence, [
a owl:Class ;
owl:unionOf (:Delegation
@@ -679,7 +680,7 @@
:hadRole
a owl:ObjectProperty ;
- rdfs:comment "The _optional_ Role that an Entity assumed in the context of an Activity. For example, :baking prov:used :spoon; prov:qualified [ a prov:Usage; prov:entity :spoon; prov:hadRole roles:mixing_implement ]."@en ;
+ rdfs:comment "The _optional_ Role that an Entity assumed in the context of an Activity. For example, :baking prov:used :spoon; prov:qualified [ a prov:Usage; prov:entity :spoon; prov:hadRole roles:mixing_implement ]."@en, "This property has multiple RDFS domains to suit multiple OWL Profiles. See <a href=\"#prov-o-owl-profile\">PROV-O OWL Profile</a>." ;
rdfs:domain :Influence, [
a owl:Class ;
owl:unionOf (:Association
@@ -1164,7 +1165,7 @@
:wasInfluencedBy
a owl:ObjectProperty ;
- rdfs:comment "Because prov:wasInfluencedBy is a broad relation, the more specific relations (prov:wasInformedBy, prov:actedOnBehalfOf, prov:endedBy, etc.) should be used when applicable." ;
+ rdfs:comment "Because prov:wasInfluencedBy is a broad relation, the more specific relations (prov:wasInformedBy, prov:actedOnBehalfOf, prov:endedBy, etc.) should be used when applicable.", "This property has multiple RDFS domains to suit multiple OWL Profiles. See <a href=\"#prov-o-owl-profile\">PROV-O OWL Profile</a>." ;
rdfs:domain [
a owl:Class ;
owl:unionOf (:Activity
@@ -1303,6 +1304,20 @@
[]
a owl:Axiom ;
+ owl:annotatedProperty rdfs:domain ;
+ owl:annotatedSource :wasInfluencedBy ;
+ owl:annotatedTarget [
+ a owl:Class ;
+ owl:unionOf (:Activity
+ :Agent
+ :Entity
+ )
+ ] ;
+ :definition "influencee: an identifier (o2) for an entity, activity, or agent; " ;
+ :dm "http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html#term-influence" .
+
+[]
+ a owl:Axiom ;
owl:annotatedProperty rdfs:range ;
owl:annotatedSource :wasInfluencedBy ;
owl:annotatedTarget [
@@ -1317,20 +1332,6 @@
[]
a owl:Axiom ;
- owl:annotatedProperty rdfs:domain ;
- owl:annotatedSource :wasInfluencedBy ;
- owl:annotatedTarget [
- a owl:Class ;
- owl:unionOf (:Activity
- :Agent
- :Entity
- )
- ] ;
- :definition "influencee: an identifier (o2) for an entity, activity, or agent; " ;
- :dm "http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html#term-influence" .
-
-[]
- a owl:Axiom ;
rdfs:comment "Quotation is a particular case of derivation (see http://www.w3.org/TR/prov-dm/#term-quotation) in which an entity is derived from an original entity by copying, or \"quoting\", some or all of it. " ;
owl:annotatedProperty rdfs:subPropertyOf ;
owl:annotatedSource :wasQuotedFrom ;
--- a/presentations/wg-overview/overview/index.html Wed Oct 31 13:09:26 2012 +0000
+++ b/presentations/wg-overview/overview/index.html Wed Oct 31 13:10:51 2012 +0000
@@ -466,8 +466,8 @@
<tr><td>prov-dm</td>
<td><a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a></td></tr>
-<tr><td>prov-dm-constraints</td>
- <td><a href="http://www.w3.org/TR/prov-dm-constraints/">http://www.w3.org/TR/prov-dm-constraints/</a></td></tr>
+<tr><td>prov-constraints</td>
+ <td><a href="http://www.w3.org/TR/prov-constraints/">http://www.w3.org/TR/prov-constraints/</a></td></tr>
<tr><td>prov-n</td>
<td><a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a></td></tr>
--- a/primer/Primer.html Wed Oct 31 13:09:26 2012 +0000
+++ b/primer/Primer.html Wed Oct 31 13:10:51 2012 +0000
@@ -63,7 +63,7 @@
"<a href=\"http://www.w3.org/2005/Incubator/prov/XGR-prov/\"><cite>Provenance XG Final Report</cite></a>. "+
"8 December 2010. "+
"URL: <a href=\"http://www.w3.org/2005/Incubator/prov/XGR-prov/\">http://www.w3.org/2005/Incubator/prov/XGR-prov/</a>"
- };
+ };
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
@@ -402,7 +402,6 @@
"addition to be made to the document", to generate a further entity in the role of "edited document".
Roles are application specific, so PROV does not define any particular roles.
</p>
- <!--p>Roles are intended as an extension point in the model; it is expected users will define and use custom role taxonomies. Role interpretation is application specific.</p -->
</section>
<section>
@@ -556,7 +555,13 @@
<p>Betty finds the following descriptions of entities in the provenance.</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:article a prov:Entity ;
dcterms:title "Crime rises in cities" .
@@ -568,7 +573,13 @@
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
entity(ex:article, [dcterms:title='Crime rises in cities'])
entity(ex:dataSet1)
@@ -604,14 +615,26 @@
</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:compile a prov:Activity .
</pre>
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
activity(ex:compile)
</pre>
@@ -628,7 +651,13 @@
</p -->
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:compose a prov:Activity .
ex:illustrate a prov:Activity .
@@ -636,7 +665,13 @@
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
activity(ex:compose)
activity(ex:illustrate)
@@ -664,7 +699,13 @@
</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:compose prov:used ex:dataSet1 ;
prov:used ex:regionList .
@@ -673,12 +714,22 @@
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
used(ex:compose, ex:dataSet1, -)
used(ex:compose, ex:regionList, -)
wasGeneratedBy(ex:composition, ex:compose, -)
</pre>
+ <p>Note that the - argument in the examples above denote unspecified optional
+ information. See the [[PROV-N]] specification for the details of what arguments
+ may be expressed in each PROV-N statement.
+ </p>
</div>
<p>
Similarly, the chart graphic creation activity (<code>ex:illustrate</code>)
@@ -686,7 +737,13 @@
</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:illustrate prov:used ex:composition .
ex:chart1 prov:wasGeneratedBy ex:illustrate .
@@ -694,7 +751,13 @@
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
used(ex:illustrate, ex:composition, -)
wasGeneratedBy(ex:chart1, ex:illustrate, -)
@@ -717,7 +780,13 @@
</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:compose prov:wasAssociatedWith ex:derek .
ex:illustrate prov:wasAssociatedWith ex:derek .
@@ -725,7 +794,13 @@
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
wasAssociatedWith(ex:compose, ex:derek, -)
wasAssociatedWith(ex:illustrate, ex:derek, -)
@@ -739,7 +814,13 @@
</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:derek a prov:Agent ;
a prov:Person ;
@@ -749,7 +830,13 @@
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
agent(ex:derek,
[prov:type='prov:Person', foaf:givenName='Derek',
@@ -763,7 +850,13 @@
</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:derek prov:actedOnBehalfOf ex:chartgen .
ex:chartgen a prov:Agent ;
@@ -773,7 +866,13 @@
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
agent(ex:chartgen,
[prov:type='prov:Organization',
@@ -787,14 +886,26 @@
</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:chart1 prov:wasAttributedTo ex:derek .
</pre>
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
wasAttributedTo(ex:chart1, ex:derek)
</pre>
@@ -828,7 +939,13 @@
</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:dataToCompose a prov:Role .
ex:regionsToAggregateBy a prov:Role .
@@ -842,7 +959,13 @@
as follows.
</p>
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:compose prov:used ex:dataSet1 .
</pre>
@@ -861,7 +984,13 @@
to be composed (<code>ex:dataToCompose</code>).
</p>
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:compose prov:qualifiedUsage [
a prov:Usage ;
@@ -876,7 +1005,13 @@
expression, with the attribute name <code>prov:role</code>.
</p>
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
used(ex:compose, ex:dataSet1, -, [prov:role='ex:dataToCompose'])
</pre>
@@ -887,7 +1022,13 @@
</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:compose prov:qualifiedUsage [
a prov:Usage ;
@@ -898,7 +1039,13 @@
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
used(ex:compose, ex:regionList, -, [prov:role='ex:regionsToAggregateBy'])
</pre>
@@ -911,7 +1058,13 @@
</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:compose prov:qualifiedAssociation [
a prov:Association ;
@@ -927,7 +1080,13 @@
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
wasAssociatedWith(ex:compose, ex:derek, -, [prov:role='ex:analyst'])
wasGeneratedBy(ex:composition, ex:compose, -, [prov:role='ex:composedData'])
@@ -954,7 +1113,13 @@
</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:dataSet2 a prov:Entity ;
prov:wasRevisionOf ex:dataSet1 .
@@ -962,7 +1127,13 @@
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
entity(ex:dataSet2)
wasDerivedFrom(ex:dataSet2, ex:dataSet1, [prov:type='prov:Revision'])
@@ -972,11 +1143,18 @@
Derek notices that there is a new dataset available and creates a new chart based on the revised data,
using another compilation activity. Betty checks the article again at a
later point, and wants to know if it is based on the old or new GovData.
- She sees a new description stating that the new chart is derived from the new dataset.
+ She sees a new description stating that the new chart is derived from the new dataset
+ (the same relation could be expressed between the old chart and old dataset).
</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:chart2 a prov:Entity ;
prov:wasDerivedFrom ex:dataSet2 .
@@ -984,7 +1162,13 @@
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
wasDerivedFrom(ex:chart2, ex:dataSet2)
</pre>
@@ -993,7 +1177,13 @@
</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:chart2 a prov:Entity ;
prov:wasRevisionOf ex:chart1 .
@@ -1001,7 +1191,13 @@
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
entity(ex:chart2)
wasDerivedFrom(ex:chart2, ex:chart1, [prov:type='prov:Revision'])
@@ -1027,7 +1223,13 @@
are described.
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:correct a prov:Activity .
ex:edith a prov:Agent, prov:Person .
@@ -1036,7 +1238,13 @@
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
activity(ex:correct)
agent(ex:edith, [prov:type='prov:Person'])
@@ -1050,7 +1258,13 @@
including that she followed the above correction instructions.
</p>
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:correct prov:qualifiedAssociation [
a Association ;
@@ -1065,7 +1279,13 @@
In PROV-N, the plan is an optional parameter to wasAssociatedWith descriptions.
</p>
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
wasAssociatedWith(ex:correct, ex:edith, ex:instructions)
wasGeneratedBy(ex:dataSet2, ex:correct, -)
@@ -1090,7 +1310,13 @@
</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:chart1 prov:generatedAtTime "2012-03-02T10:30:00"^^xsd:dateTime .
ex:chart2 prov:generatedAtTime "2012-04-01T15:21:00"^^xsd:dateTime .
@@ -1098,7 +1324,13 @@
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
wasGeneratedBy(ex:chart1, ex:compile, 2012-03-02T10:30:00)
wasGeneratedBy(ex:chart2, ex:compile2, 2012-04-01T15:21:00)
@@ -1114,7 +1346,13 @@
</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:correct prov:startedAtTime "2012-03-31T09:21:00"^^xsd:dateTime ;
prov:endedAtTime "2012-04-01T15:21:00"^^xsd:dateTime .
@@ -1122,7 +1360,13 @@
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
activity(ex:correct, 2012-03-31T09:21:00, 2012-04-01T15:21:00)
</pre>
@@ -1144,7 +1388,13 @@
</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:blogEntry a prov:Entity ;
prov:wasQuotedFrom ex:article .
@@ -1152,7 +1402,13 @@
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
entity(ex:blogEntry)
wasDerivedFrom(ex:blogEntry, ex:article, [prov:type='prov:Quotation'])
@@ -1168,7 +1424,13 @@
</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:articleV1 a prov:Entity ;
prov:specializationOf ex:article .
@@ -1176,7 +1438,13 @@
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
entity(ex:articleV1)
specializationOf(ex:articleV1, ex:article)
@@ -1192,7 +1460,13 @@
</p>
<div class="turtle example">
<div class="exampleheader">
- <span class="exampleheader"><b>Turtle Example</b></span></div>
+ <span class="exampleheader"><b>Turtle Example</b>
+ <a onclick="
+ set_display_by_class('pre','turtle example','none');
+ set_display_by_class('div','turtle example','none');
+ set_display_by_id('hide-turtle-examples','none');
+ set_display_by_id('show-turtle-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
ex:articleV2 prov:specializationOf ex:article .
ex:articleV2 prov:alternateOf ex:articleV1 .
@@ -1200,7 +1474,13 @@
</div>
<div class="provn example">
<div class="exampleheader">
- <span class="exampleheader"><b>PROV-N Example</b></span></div>
+ <span class="exampleheader"><b>PROV-N Example</b>
+ <a onclick="
+ set_display_by_class('pre','provn example','none');
+ set_display_by_class('div','provn example','none');
+ set_display_by_id('hide-provn-examples','none');
+ set_display_by_id('show-provn-examples','');"><u><i>(hide)</i></u></a>
+ </span></div>
<pre>
specializationOf(ex:articleV2, ex:article)
alternateOf(ex:articleV2, ex:articleV1)
@@ -1220,6 +1500,8 @@
<section>
<h3>Complete PROV data</h3>
<p>
+ The full set of examples shown above are available in <a href="primer-turtle-examples.txt">PROV-O Turtle format</a>
+ or <a href="primer-provn-examples.txt">PROV-N format</a>.
We visualize the whole example below.
</p>
<img src="images/everything.png" alt="Provenance graph for whole example" width="95%"/>
@@ -1238,6 +1520,10 @@
<ul>
<li>Corrected mailing list address for public comments.</li>
<li>Fixed the status to clarify this is a note, not a recommendation.</li>
+ <li>Added note explaining unspecified arguments in PROV-N statements.</li>
+ <li>Clarified derivation example discrepancies for old and new charts/datasets.</li>
+ <li>Added supporting files containing full PROV-O and PROV-N examples.</li>
+ <li>Figures edited so that each CURIEs is on one line rather being split across two.</li>
<li>Fixed minor typos.</li>
</ul>
</section>
Binary file primer/images/activities.png has changed
--- a/primer/images/activities.svg Wed Oct 31 13:09:26 2012 +0000
+++ b/primer/images/activities.svg Wed Oct 31 13:10:51 2012 +0000
@@ -17,12 +17,12 @@
height="106.33577"
xml:space="preserve"
sodipodi:docname="activities.svg"
- inkscape:export-filename="C:\Work\standards\w3c\prov\primer\images\activities.png"
+ inkscape:export-filename="C:\Mercurial\prov\primer\images\activities.png"
inkscape:export-xdpi="90"
inkscape:export-ydpi="90"><metadata
id="metadata8"><rdf:RDF><cc:Work
rdf:about=""><dc:format>image/svg+xml</dc:format><dc:type
- rdf:resource="http://purl.org/dc/dcmitype/StillImage" /><dc:title /></cc:Work></rdf:RDF></metadata><defs
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" /><dc:title></dc:title></cc:Work></rdf:RDF></metadata><defs
id="defs6"><linearGradient
id="linearGradient4511"><stop
style="stop-color:#d19d00;stop-opacity:1;"
@@ -193,6 +193,7 @@
+
</g><g
transform="matrix(1.2454971,0,0,-1,-49.371993,1092.4584)"
id="g262-0"><path
@@ -215,6 +216,7 @@
+
</g>
@@ -239,6 +241,7 @@
style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:compile</tspan></text>
+
<flowRoot
xml:space="preserve"
id="flowRoot3032"
@@ -249,4 +252,4 @@
height="70.82563"
x="-21.70463"
y="-21.607307" /></flowRegion><flowPara
- id="flowPara3038"></flowPara></flowRoot></g></g></svg>
\ No newline at end of file
+ id="flowPara3038" /></flowRoot></g></g></svg>
\ No newline at end of file
Binary file primer/images/agents.png has changed
--- a/primer/images/agents.svg Wed Oct 31 13:09:26 2012 +0000
+++ b/primer/images/agents.svg Wed Oct 31 13:10:51 2012 +0000
@@ -17,7 +17,7 @@
height="376.13803"
xml:space="preserve"
sodipodi:docname="agents.svg"
- inkscape:export-filename="C:\Work\standards\w3c\prov\primer\images\agents.png"
+ inkscape:export-filename="C:\Mercurial\prov\primer\images\agents.png"
inkscape:export-xdpi="90"
inkscape:export-ydpi="90"><metadata
id="metadata8"><rdf:RDF><cc:Work
@@ -380,7 +380,7 @@
inkscape:window-x="-8"
inkscape:window-y="-8"
inkscape:window-maximized="1"
- inkscape:current-layer="g12"
+ inkscape:current-layer="g544-9-6-4-2"
fit-margin-top="0"
fit-margin-left="0"
fit-margin-right="0"
@@ -404,17 +404,15 @@
transform="matrix(1,0,0,-1,195.9912,804.8)"
id="g266"><text
id="text268"
- transform="translate(-13.23096,5)"><tspan
- y="0"
- x="0"
- id="tspan270"
+ style="font-size:9.60000038px"
+ x="-14.830959"
+ y="11.400001"><tspan
+ id="tspan4509"
+ y="11.400001"
+ x="-14.830959"
sodipodi:role="line"
- style="font-size:11.19999981px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:</tspan><tspan
- id="tspan4509"
- y="14"
- x="0"
- sodipodi:role="line"
- style="font-size:11.19999981px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">compose</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:compose</tspan></text>
+
@@ -443,18 +441,16 @@
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
id="g544-9-6"
transform="matrix(1,0,0,-1,24.41479,797.44439)"><text
- transform="translate(-7.640396,-2)"
- id="text546-3-0"><tspan
- id="tspan3196-2"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="0"
- y="0"
- sodipodi:role="line">ex:</tspan><tspan
+ id="text546-3-0"
+ style="font-size:9.60000038px"
+ x="-12.440397"
+ y="4.4000001"><tspan
id="tspan4448-4"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="0"
- y="13.75"
- sodipodi:role="line">regionList</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ x="-12.440397"
+ y="4.4000001"
+ sodipodi:role="line">ex:regionList</tspan></text>
+
@@ -473,17 +469,15 @@
transform="matrix(1,0,0,-1,525.13557,804.552)"
id="g266-6"><text
id="text268-18"
- transform="translate(-13.23096,5)"><tspan
- y="0"
- x="0"
- id="tspan270-4"
+ style="font-size:9.60000038px"
+ x="-14.830959"
+ y="11.400001"><tspan
+ id="tspan4509-9"
+ y="11.400001"
+ x="-14.830959"
sodipodi:role="line"
- style="font-size:11.19999981px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:</tspan><tspan
- id="tspan4509-9"
- y="14"
- x="0"
- sodipodi:role="line"
- style="font-size:11.19999981px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">illustrate</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:illustrate</tspan></text>
+
@@ -518,6 +512,7 @@
+
</g><g
transform="matrix(0.9368205,0,0,-1,-142.39394,1034.7)"
id="g340"
@@ -560,6 +555,7 @@
+
</g><g
transform="matrix(1,0,0,-1,-175.5,1034.7)"
id="g498"
@@ -636,6 +632,7 @@
+
</g>
@@ -648,17 +645,14 @@
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3"
- transform="translate(-7.640396,-2)"><tspan
+ x="-6.0403962"
+ y="4.4000001"><tspan
sodipodi:role="line"
- y="0"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448">dataSet1</tspan></text>
+ y="4.4000001"
+ x="-6.0403962"
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448">ex:dataSet1</tspan></text>
+
@@ -705,6 +699,7 @@
+
</g><g
transform="matrix(1,0,0,-1,629.04784,802.28001)"
id="g334-3"
@@ -726,6 +721,7 @@
+
</g><g
transform="matrix(1.5826615,0,0,-1,38.212014,965.3546)"
id="g936-0"
@@ -742,17 +738,15 @@
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3-3"
- transform="translate(-7.640396,-2)"><tspan
+ style="font-size:9.60000038px"
+ x="-13.351429"
+ y="3.4832747"><tspan
sodipodi:role="line"
- y="0"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196-8">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448-9">composition</tspan></text>
+ y="3.4832747"
+ x="-13.351429"
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448-9">ex:composition</tspan></text>
+
@@ -795,17 +789,15 @@
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3-3-3"
- transform="translate(-7.640396,-2)"><tspan
+ style="font-size:9.60000038px"
+ x="-9.2403965"
+ y="4.1693954"><tspan
sodipodi:role="line"
- y="0"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196-8-5">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448-9-9">chart1</tspan></text>
+ y="4.1693954"
+ x="-9.2403965"
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448-9-9">ex:chart1</tspan></text>
+
@@ -847,18 +839,15 @@
id="g544-9-6-4"
transform="matrix(1,0,0,-1,26.408902,680.37281)"><text
id="text546-3-0-8"
- x="-0.32936299"
- y="-2"><tspan
- id="tspan3196-2-8"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="-0.32936299"
- y="-2"
- sodipodi:role="line">ex:</tspan><tspan
+ x="-3.5293629"
+ y="2.8"
+ style="font-size:9.60000038px"><tspan
id="tspan4448-4-2"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="-0.32936299"
- y="11.75"
- sodipodi:role="line">derek</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ x="-3.5293629"
+ y="2.8"
+ sodipodi:role="line">ex:derek</tspan></text>
+
@@ -882,6 +871,7 @@
+
<text
style="font-size:11.99999905px"
y="-654.78522"
@@ -899,6 +889,7 @@
+
<path
style="fill:none;stroke:#000000;stroke-width:0.92126256px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
d="M 506.9356,780.19235 79.473094,677.8999"
@@ -938,6 +929,7 @@
+
<g
transform="matrix(1,0,0,-1,-170.83865,906.41306)"
id="g318-4"
@@ -955,18 +947,15 @@
id="g544-9-6-4-2"
transform="matrix(1,0,0,-1,25.138656,595.70772)"><text
id="text546-3-0-8-4"
- x="-5.1293631"
- y="-2"><tspan
- id="tspan3196-2-8-5"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="-5.1293631"
- y="-2"
- sodipodi:role="line">ex:</tspan><tspan
+ x="-9.9293633"
+ y="4.4000001"
+ style="font-size:9.60000038px"><tspan
id="tspan4448-4-2-5"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="-5.1293631"
- y="11.75"
- sodipodi:role="line">chartgen</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ x="-9.9293633"
+ y="4.4000001"
+ sodipodi:role="line">ex:chartgen</tspan></text>
+
@@ -1031,6 +1020,7 @@
+
<g
transform="matrix(1.6167515,0,0,0.92048921,-60.257445,-125.07222)"
id="g558-1-3"
@@ -1060,6 +1050,7 @@
+
<g
transform="matrix(0.43309751,0.00230963,0.02385816,1.4614635,60.59143,-253.39309)"
id="g572-5-1"
@@ -1096,6 +1087,7 @@
+
</g>
Binary file primer/images/derivation.png has changed
--- a/primer/images/derivation.svg Wed Oct 31 13:09:26 2012 +0000
+++ b/primer/images/derivation.svg Wed Oct 31 13:10:51 2012 +0000
@@ -17,7 +17,7 @@
height="57.177254"
xml:space="preserve"
sodipodi:docname="derivation.svg"
- inkscape:export-filename="C:\Work\standards\w3c\prov\primer\images\derivation.png"
+ inkscape:export-filename="C:\Mercurial\prov\primer\images\derivation.png"
inkscape:export-xdpi="90"
inkscape:export-ydpi="90"><metadata
id="metadata8"><rdf:RDF><cc:Work
@@ -468,7 +468,7 @@
inkscape:window-x="-8"
inkscape:window-y="-8"
inkscape:window-maximized="1"
- inkscape:current-layer="g12"
+ inkscape:current-layer="g544-9-61-1-3"
fit-margin-top="0"
fit-margin-left="0"
fit-margin-right="0"
@@ -503,17 +503,15 @@
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3"
- transform="translate(-7.640396,-2)"><tspan
+ style="font-size:9.60000038px"
+ x="-11.295913"
+ y="3.7138791"><tspan
sodipodi:role="line"
- y="0"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448">dataSet1</tspan></text>
+ y="3.7138791"
+ x="-11.295913"
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448">ex:dataSet1</tspan></text>
+
@@ -546,18 +544,15 @@
inkscape:connector-curvature="0" /></g><text
transform="scale(1,-1)"
id="text546-3-35"
- x="123.34532"
- y="-905.05206"><tspan
- id="tspan3196-9"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="123.34532"
- y="-905.05206"
- sodipodi:role="line">ex:</tspan><tspan
+ x="120.14532"
+ y="-898.65216"
+ style="font-size:9.60000038px"><tspan
id="tspan4448-8"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="123.34532"
- y="-891.30206"
- sodipodi:role="line">dataSet2</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ x="120.14532"
+ y="-898.65216"
+ sodipodi:role="line">ex:dataSet2</tspan></text>
+
@@ -579,6 +574,7 @@
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -611,17 +607,15 @@
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3-3-3-9"
- transform="translate(-7.640396,-2)"><tspan
+ style="font-size:9.60000038px"
+ x="-10.840397"
+ y="2.8000002"><tspan
sodipodi:role="line"
- y="0"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196-8-5-8">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448-9-9-8">chart2</tspan></text>
+ y="2.8000002"
+ x="-10.840397"
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448-9-9-8">ex:chart2</tspan></text>
+
@@ -643,6 +637,7 @@
sodipodi:role="line"
id="tspan338-76-4">wasDerivedFrom</tspan></text>
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
Binary file primer/images/entities.png has changed
--- a/primer/images/entities.svg Wed Oct 31 13:09:26 2012 +0000
+++ b/primer/images/entities.svg Wed Oct 31 13:10:51 2012 +0000
@@ -17,7 +17,7 @@
height="144.10878"
xml:space="preserve"
sodipodi:docname="entities.svg"
- inkscape:export-filename="C:\Work\standards\w3c\prov\primer\images\entities.png"
+ inkscape:export-filename="C:\Mercurial\prov\primer\images\entities.png"
inkscape:export-xdpi="90"
inkscape:export-ydpi="90"><metadata
id="metadata8"><rdf:RDF><cc:Work
@@ -139,7 +139,7 @@
inkscape:window-x="46"
inkscape:window-y="1"
inkscape:window-maximized="0"
- inkscape:current-layer="g12"
+ inkscape:current-layer="g544-9-61-1"
fit-margin-top="0"
fit-margin-left="0"
fit-margin-right="0"
@@ -166,18 +166,16 @@
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
id="g544-9-6"
transform="matrix(1,0,0,-1,284.7052,833.33051)"><text
- transform="translate(-7.640396,-2)"
- id="text546-3-0"><tspan
- id="tspan3196-2"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="0"
- y="0"
- sodipodi:role="line">ex:</tspan><tspan
+ id="text546-3-0"
+ style="font-size:9.60000038px"
+ x="-12.440397"
+ y="4.4000001"><tspan
id="tspan4448-4"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="0"
- y="13.75"
- sodipodi:role="line">regionList</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ x="-12.440397"
+ y="4.4000001"
+ sodipodi:role="line">ex:regionList</tspan></text>
+
@@ -196,23 +194,21 @@
<g
- transform="matrix(1,0,0,-1,285.13331,901.79626)"
+ transform="matrix(1,0,0,-1,285.13331,900.19626)"
id="g544-9"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3"
- transform="translate(-7.640396,-2)"><tspan
+ style="font-size:9.60000038px"
+ x="-10.840397"
+ y="2.8"><tspan
sodipodi:role="line"
- y="0"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448">dataSet1</tspan></text>
+ y="2.8"
+ x="-10.840397"
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448">ex:dataSet1</tspan></text>
+
@@ -233,17 +229,15 @@
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3-3"
- transform="translate(-7.640396,-2)"><tspan
+ style="font-size:9.60000038px"
+ x="-12.440397"
+ y="4.4000001"><tspan
sodipodi:role="line"
- y="0"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196-8">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448-9">composition</tspan></text>
+ y="4.4000001"
+ x="-12.440397"
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448-9">ex:composition</tspan></text>
+
@@ -263,17 +257,15 @@
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3-3-3"
- transform="translate(-7.640396,-2)"><tspan
+ style="font-size:9.60000038px"
+ x="-10.840397"
+ y="4.4000001"><tspan
sodipodi:role="line"
- y="0"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196-8-5">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448-9-9">chart1</tspan></text>
+ y="4.4000001"
+ x="-10.840397"
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448-9-9">ex:chart1</tspan></text>
+
@@ -287,23 +279,20 @@
style="fill:url(#linearGradient3487);fill-opacity:1;stroke:#000000;stroke-width:1;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
d="m 238.6758,155.4437 c 10.3144,8.5915 10.3144,22.5211 0,31.1126 -10.3145,8.5916 -27.0375,8.5916 -37.3519,0 -10.3145,-8.5915 -10.3145,-22.5211 0,-31.1126 10.3144,-8.5916 27.0374,-8.5916 37.3519,0"
inkscape:connector-curvature="0" /></g><g
- transform="matrix(1,0,0,-1,376.38119,903.38979)"
+ transform="matrix(1,0,0,-1,376.38119,901.78979)"
id="g544-9-3"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3-2"
- x="-7.6403961"
- y="-2"><tspan
+ x="-10.840397"
+ y="2.8"
+ style="font-size:9.60000038px"><tspan
sodipodi:role="line"
- y="-2"
- x="-7.6403961"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196-21">ex:</tspan><tspan
- sodipodi:role="line"
- y="11.75"
- x="-7.6403961"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448-6">article</tspan></text>
+ y="2.8"
+ x="-10.840397"
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448-6">ex:article</tspan></text>
+
</g></g></svg>
\ No newline at end of file
Binary file primer/images/everything.png has changed
--- a/primer/images/everything.svg Wed Oct 31 13:09:26 2012 +0000
+++ b/primer/images/everything.svg Wed Oct 31 13:10:51 2012 +0000
@@ -17,7 +17,7 @@
height="766.44946"
xml:space="preserve"
sodipodi:docname="everything.svg"
- inkscape:export-filename="C:\Work\standards\w3c\prov\primer\images\everything.png"
+ inkscape:export-filename="C:\Mercurial\prov\primer\images\everything.png"
inkscape:export-xdpi="90"
inkscape:export-ydpi="90"><metadata
id="metadata8"><rdf:RDF><cc:Work
@@ -468,7 +468,7 @@
inkscape:window-x="-8"
inkscape:window-y="-8"
inkscape:window-maximized="1"
- inkscape:current-layer="g12"
+ inkscape:current-layer="g266-7-8"
fit-margin-top="0"
fit-margin-left="0"
fit-margin-right="0"
@@ -521,6 +521,8 @@
+
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -554,6 +556,8 @@
+
+
</g><g
transform="matrix(1.2454971,0,0,-1,65.32126,1035.0947)"
id="g262-0"><path
@@ -581,6 +585,8 @@
+
+
</g><g
transform="matrix(1,0,0,-1,294.12,802.15)"
id="g334"
@@ -609,6 +615,8 @@
+
+
</g><g
transform="matrix(0.9368205,0,0,-1,-142.39394,1034.7)"
id="g340"
@@ -653,6 +661,8 @@
+
+
</g><g
transform="matrix(1,0,0,-1,-175.5,1034.7)"
id="g498"
@@ -731,6 +741,8 @@
+
+
</g>
@@ -761,6 +773,8 @@
+
+
</g><g
transform="matrix(0.71351425,0,0,-1,254.12833,1034.83)"
id="g498-2"
@@ -800,6 +814,8 @@
+
+
</g><g
transform="matrix(1,0,0,-1,629.04784,802.28001)"
id="g334-3"
@@ -823,6 +839,8 @@
+
+
</g><g
transform="matrix(1.5826615,0,0,-1,38.212014,965.3546)"
id="g936-0"
@@ -856,6 +874,8 @@
+
+
</g><g
id="g3270"
transform="translate(0,-36.8)"><g
@@ -907,6 +927,8 @@
+
+
</g><g
transform="matrix(1,0,0,-1,-169.56841,991.0782)"
id="g318"
@@ -956,6 +978,8 @@
+
+
</g><text
style="font-size:12px"
y="-421.20554"
@@ -975,6 +999,8 @@
+
+
<text
style="font-size:11.99999905px"
y="-654.78522"
@@ -994,6 +1020,8 @@
+
+
<path
style="fill:none;stroke:#000000;stroke-width:0.92126256px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
d="M 506.9356,780.19235 79.473094,677.8999"
@@ -1035,6 +1063,8 @@
+
+
<g
transform="matrix(1,0,0,-1,-170.83865,906.41306)"
id="g318-4"
@@ -1067,6 +1097,8 @@
+
+
</g><path
id="path344-6-9-2-6-1"
style="fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none"
@@ -1114,6 +1146,8 @@
+
+
</g><g
transform="matrix(1.6167515,0,0,-1,-69.14114,1403.714)"
id="g558"
@@ -1149,6 +1183,8 @@
+
+
</g><g
transform="matrix(0.43309751,-0.00230963,0.02385816,-1.4614635,51.707733,1511.0808)"
id="g572"
@@ -1203,6 +1239,8 @@
+
+
<g
transform="matrix(1.6167515,0,0,0.92048921,-60.257445,-125.07222)"
id="g558-1-3"
@@ -1234,6 +1272,8 @@
+
+
<g
transform="matrix(0.43309751,0.00230963,0.02385816,1.4614635,60.59143,-253.39309)"
id="g572-5-1"
@@ -1272,6 +1312,8 @@
+
+
</g><g
transform="matrix(1.4146437,0,0,-0.84786888,92.069991,1075.8453)"
id="g558-3"
@@ -1307,6 +1349,8 @@
+
+
</g><g
transform="matrix(0.29192986,0.32279258,1.7382768,-0.60122387,-303.94221,938.06345)"
id="g572-2"
@@ -1351,6 +1395,8 @@
+
+
</g><g
transform="matrix(-0.6837653,0.41048076,1.4796713,1.9262836,-179.39281,286.98448)"
id="g572-2-5"
@@ -1395,6 +1441,8 @@
+
+
</g><g
transform="matrix(-0.62188296,0.39975874,1.3457576,1.8759678,-168.43478,203.36898)"
id="g572-2-5-9"
@@ -1439,6 +1487,8 @@
+
+
</g><g
transform="matrix(0.00870226,0.28186705,1.6936272,-0.18063826,-164.96914,810.84161)"
id="g572-2-8"
@@ -1475,6 +1525,8 @@
+
+
<g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -1495,6 +1547,8 @@
+
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -1535,6 +1589,8 @@
+
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -1567,6 +1623,8 @@
+
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -1587,6 +1645,8 @@
+
+
</g><path
inkscape:connector-curvature="0"
inkscape:export-ydpi="79.550438"
@@ -1625,6 +1685,8 @@
+
+
</g><g
transform="matrix(1.0394571,0,0,-1,502.75321,1071.8623)"
id="g936-0-2-1"
@@ -1655,6 +1717,8 @@
+
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -1700,6 +1764,8 @@
+
+
</g><g
transform="matrix(0.9376888,0.34747621,0.34747621,-0.9376888,651.76262,989.27394)"
id="g334-3-1-0"
@@ -1723,6 +1789,8 @@
+
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -1762,6 +1830,8 @@
+
+
</g><g
transform="matrix(1.0611643,0,0,-1,-123.33092,1236.364)"
id="g262-7-3"><path
@@ -1773,7 +1843,10 @@
id="g266-7-8"><text
id="text268-2-4"
transform="translate(-13.23096,5)"
- style="font-size:9.60000038px"><tspan
+ style="font-size:9.60000038px"
+ inkscape:export-filename="C:\Mercurial\prov\primer\images\everything.png"
+ inkscape:export-xdpi="90"
+ inkscape:export-ydpi="90"><tspan
id="tspan4509-0-9"
y="0"
x="0"
@@ -1786,6 +1859,8 @@
+
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -1822,6 +1897,8 @@
+
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -1843,6 +1920,8 @@
+
+
</g><path
inkscape:connector-curvature="0"
inkscape:export-ydpi="79.550438"
@@ -1882,6 +1961,8 @@
+
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -1918,6 +1999,8 @@
+
+
</g><path
sodipodi:type="arc"
style="fill:#151b23;fill-opacity:0.97916667;stroke:#000000;stroke-width:1.20000005;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
@@ -1961,6 +2044,8 @@
+
+
</g><path
id="path342-6-0-2"
style="fill:none;stroke:#000000;stroke-width:1.27020955;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
@@ -1992,6 +2077,8 @@
+
+
</g><g
transform="matrix(1.4146052,0,0,-0.84786888,359.52897,1054.7903)"
id="g558-3-4-2"
@@ -2027,6 +2114,8 @@
+
+
</g><g
transform="matrix(-0.79741846,0.01415798,0.60418273,1.6898123,522.91277,437.9406)"
id="g572-2-8-3"
@@ -2071,6 +2160,8 @@
+
+
</g><g
transform="matrix(-0.4860202,-0.23750576,-0.18759351,1.1471291,727.3055,719.20578)"
id="g572-2-8-3-2"
@@ -2125,6 +2216,8 @@
+
+
</g><g
transform="matrix(0.0340166,0.0659249,2.399107,-0.03142758,-305.93401,1016.1301)"
id="g572-2-5-1"
@@ -2169,6 +2262,8 @@
+
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -2215,6 +2310,8 @@
+
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -2251,6 +2348,8 @@
+
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -2286,6 +2385,8 @@
+
+
<g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -2305,6 +2406,8 @@
+
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -2341,6 +2444,8 @@
+
+
</g><g
transform="matrix(1.2806619,0,0,-1,201.63694,1272.02)"
id="g936-4-8-8"
@@ -2371,6 +2476,8 @@
+
+
</g><path
id="path344-6-9-0"
style="fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none"
@@ -2412,6 +2519,8 @@
+
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -2437,6 +2546,8 @@
+
+
<path
id="path344-6-9-0-5"
style="fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none"
@@ -2498,4 +2609,6 @@
sodipodi:role="line"
id="tspan338-5-3-1-2">wasRevisionOf</tspan></text>
+
+
</g></svg>
\ No newline at end of file
Binary file primer/images/plans.png has changed
--- a/primer/images/plans.svg Wed Oct 31 13:09:26 2012 +0000
+++ b/primer/images/plans.svg Wed Oct 31 13:10:51 2012 +0000
@@ -17,7 +17,7 @@
height="169.59584"
xml:space="preserve"
sodipodi:docname="plans.svg"
- inkscape:export-filename="C:\Work\standards\w3c\prov\primer\images\plans.png"
+ inkscape:export-filename="C:\Mercurial\prov\primer\images\plans.png"
inkscape:export-xdpi="90"
inkscape:export-ydpi="90"><metadata
id="metadata8"><rdf:RDF><cc:Work
@@ -385,23 +385,20 @@
<g
- transform="matrix(1,0,0,-1,-75.9571,910.71014)"
+ transform="matrix(1,0,0,-1,-74.3571,902.71014)"
id="g544-9"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3"
- transform="translate(-7.640396,-2)"><tspan
+ transform="translate(-7.640396,-2)"
+ style="font-size:9.60000038px"><tspan
sodipodi:role="line"
y="0"
x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448">dataSet1</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448">ex:dataSet1</tspan></text>
+
@@ -434,18 +431,15 @@
inkscape:connector-curvature="0" /></g><text
transform="scale(1,-1)"
id="text546-3-35"
- x="384.71475"
- y="-960.81244"><tspan
- id="tspan3196-9"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="384.71475"
- y="-960.81244"
- sodipodi:role="line">ex:</tspan><tspan
+ x="381.51474"
+ y="-954.41254"
+ style="font-size:9.60000038px"><tspan
id="tspan4448-8"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="384.71475"
- y="-947.06244"
- sodipodi:role="line">dataSet2</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ x="381.51474"
+ y="-954.41254"
+ sodipodi:role="line">ex:dataSet2</tspan></text>
+
@@ -467,6 +461,7 @@
+
</g><path
inkscape:connector-curvature="0"
inkscape:export-ydpi="79.550438"
@@ -481,20 +476,17 @@
id="path264-3-4"
style="fill:url(#linearGradient4503);fill-opacity:1;stroke:#000000;stroke-width:1;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
d="m 354.703,221.25 44.17639,0 0,37.5 -44.17639,0 0,-37.5 z" /></g><g
- transform="matrix(1,0,0,-1,271.45542,1006.4641)"
+ transform="matrix(1,0,0,-1,268.25542,1000.0641)"
id="g266-7-8"><text
id="text268-2-4"
- transform="translate(-13.23096,5)"><tspan
+ transform="translate(-13.23096,5)"
+ style="font-size:9.60000038px"><tspan
+ id="tspan4509-0-9"
y="0"
x="0"
- id="tspan270-6-9"
sodipodi:role="line"
- style="font-size:11.19999981px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:</tspan><tspan
- id="tspan4509-0-9"
- y="14"
- x="0"
- sodipodi:role="line"
- style="font-size:11.19999981px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">correct</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:correct</tspan></text>
+
@@ -532,6 +524,7 @@
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -550,6 +543,7 @@
+
</g><path
inkscape:connector-curvature="0"
inkscape:export-ydpi="79.550438"
@@ -574,18 +568,15 @@
id="g544-9-6-4-8"
transform="matrix(1,0,0,-1,-62.980418,1002.3184)"><text
id="text546-3-0-8-9"
- x="-0.32936299"
- y="-2"><tspan
- id="tspan3196-2-8-0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="-0.32936299"
- y="-2"
- sodipodi:role="line">ex:</tspan><tspan
+ x="-6.729363"
+ y="4.4000001"
+ style="font-size:9.60000038px"><tspan
id="tspan4448-4-2-7"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="-0.32936299"
- y="11.75"
- sodipodi:role="line">edith</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ x="-6.729363"
+ y="4.4000001"
+ sodipodi:role="line">ex:edith</tspan></text>
+
@@ -623,6 +614,7 @@
+
</g><path
sodipodi:type="arc"
style="fill:#151b23;fill-opacity:0.97916667;stroke:#000000;stroke-width:1.20000005;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
@@ -645,24 +637,21 @@
style="fill:url(#linearGradient4836);fill-opacity:1;stroke:#000000;stroke-width:1;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
d="m 238.6758,155.4437 c 10.3144,8.5915 10.3144,22.5211 0,31.1126 -10.3145,8.5916 -27.0375,8.5916 -37.3519,0 -10.3145,-8.5915 -10.3145,-22.5211 0,-31.1126 10.3144,-8.5916 27.0374,-8.5916 37.3519,0"
inkscape:connector-curvature="0" /></g><g
- transform="matrix(1,0,0,-1,-75.368809,957.8994)"
+ transform="matrix(1,0,0,-1,-78.568809,951.4994)"
id="g544-9-39"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3-24"
x="-7.6403961"
- y="-2"><tspan
+ y="-2"
+ style="font-size:9.60000038px"><tspan
sodipodi:role="line"
y="-2"
x="-7.6403961"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196-6">ex:</tspan><tspan
- sodipodi:role="line"
- y="11.75"
- x="-7.6403961"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448-1">instructions</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448-1">ex:instructions</tspan></text>
+
@@ -700,6 +689,7 @@
+
</g><path
style="fill:none;stroke:#000000;stroke-width:0.65616947px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
d="m 304.6916,995.61216 71.60192,-29.59491"
Binary file primer/images/roles.png has changed
--- a/primer/images/roles.svg Wed Oct 31 13:09:26 2012 +0000
+++ b/primer/images/roles.svg Wed Oct 31 13:10:51 2012 +0000
@@ -17,7 +17,7 @@
height="332.392"
xml:space="preserve"
sodipodi:docname="roles.svg"
- inkscape:export-filename="C:\Work\standards\w3c\prov\primer\images\roles.png"
+ inkscape:export-filename="C:\Mercurial\prov\primer\images\roles.png"
inkscape:export-xdpi="90"
inkscape:export-ydpi="90"><metadata
id="metadata8"><rdf:RDF><cc:Work
@@ -495,20 +495,17 @@
id="path264"
style="fill:url(#linearGradient4517);fill-opacity:1;stroke:#000000;stroke-width:1;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
d="m 354.703,221.25 44.17639,0 0,37.5 -44.17639,0 0,-37.5 z" /></g><g
- transform="matrix(1,0,0,-1,195.9912,804.8)"
+ transform="matrix(1,0,0,-1,194.3912,798.4)"
id="g266"><text
id="text268"
- transform="translate(-13.23096,5)"><tspan
+ transform="translate(-13.23096,5)"
+ style="font-size:9.60000038px"><tspan
+ id="tspan4509"
y="0"
x="0"
- id="tspan270"
sodipodi:role="line"
- style="font-size:11.19999981px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:</tspan><tspan
- id="tspan4509"
- y="14"
- x="0"
- sodipodi:role="line"
- style="font-size:11.19999981px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">compose</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:compose</tspan></text>
+
@@ -535,19 +532,16 @@
inkscape:export-xdpi="79.550438"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
id="g544-9-6"
- transform="matrix(1,0,0,-1,24.41479,797.44439)"><text
+ transform="matrix(1,0,0,-1,18.01479,791.04439)"><text
transform="translate(-7.640396,-2)"
- id="text546-3-0"><tspan
- id="tspan3196-2"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="text546-3-0"
+ style="font-size:9.60000038px"><tspan
+ id="tspan4448-4"
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
x="0"
y="0"
- sodipodi:role="line">ex:</tspan><tspan
- id="tspan4448-4"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="0"
- y="13.75"
- sodipodi:role="line">regionList</tspan></text>
+ sodipodi:role="line">ex:regionList</tspan></text>
+
@@ -580,6 +574,7 @@
+
</g><g
transform="matrix(0.9368205,0,0,-1,-142.39394,1034.7)"
id="g340"
@@ -621,6 +616,7 @@
+
</g><g
transform="matrix(1,0,0,-1,-175.5,1034.7)"
id="g498"
@@ -696,29 +692,27 @@
+
</g>
<g
- transform="matrix(1,0,0,-1,-66.3571,902.71014)"
+ transform="matrix(1,0,0,-1,-71.1571,896.31014)"
id="g544-9"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3"
- transform="translate(-7.640396,-2)"><tspan
+ transform="translate(-7.640396,-2)"
+ style="font-size:9.60000038px"><tspan
sodipodi:role="line"
y="0"
x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448">dataSet1</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448">ex:dataSet1</tspan></text>
+
@@ -737,23 +731,20 @@
style="fill:url(#linearGradient4539);fill-opacity:1;stroke:#000000;stroke-width:1;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
d="m 238.6758,155.4437 c 10.3144,8.5915 10.3144,22.5211 0,31.1126 -10.3145,8.5916 -27.0375,8.5916 -37.3519,0 -10.3145,-8.5915 -10.3145,-22.5211 0,-31.1126 10.3144,-8.5916 27.0374,-8.5916 37.3519,0"
inkscape:connector-curvature="0" /></g><g
- transform="matrix(1,0,0,-1,366.35927,796.56467)"
+ transform="matrix(1,0,0,-1,363.15927,790.16467)"
id="g544-9-61"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3-3"
- transform="translate(-7.640396,-2)"><tspan
+ transform="translate(-7.640396,-2)"
+ style="font-size:9.60000038px"><tspan
sodipodi:role="line"
y="0"
x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196-8">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448-9">composition</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448-9">ex:composition</tspan></text>
+
@@ -792,20 +783,16 @@
inkscape:export-xdpi="79.550438"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
id="g544-9-6-4"
- transform="matrix(1,0,0,-1,26.408902,680.37281)"><text
+ transform="matrix(1,0,0,-1,21.608902,673.97281)"><text
id="text546-3-0-8"
x="-0.32936299"
y="-2"><tspan
- id="tspan3196-2-8"
+ id="tspan4448-4-2"
style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
x="-0.32936299"
y="-2"
- sodipodi:role="line">ex:</tspan><tspan
- id="tspan4448-4-2"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="-0.32936299"
- y="11.75"
- sodipodi:role="line">derek</tspan></text>
+ sodipodi:role="line">ex:derek</tspan></text>
+
@@ -831,6 +818,7 @@
+
<path
id="path344-6-9-2"
style="fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none"
@@ -874,6 +862,7 @@
+
</g><g
transform="matrix(0.40082252,0.4151758,2.3866708,-0.77329411,-480.79716,961.35321)"
id="g572-2"
@@ -915,6 +904,7 @@
+
</g><g
transform="matrix(-0.6837653,0.41048076,1.4796713,1.9262836,-179.39281,286.98448)"
id="g572-2-5"
@@ -956,6 +946,7 @@
+
</g><g
transform="matrix(-0.62188296,0.39975874,1.3457576,1.8759678,-168.43478,203.36898)"
id="g572-2-5-9"
@@ -997,6 +988,7 @@
+
</g><g
transform="matrix(0.00870226,0.28186705,1.6936272,-0.18063826,-164.96914,810.84161)"
id="g572-2-8"
Binary file primer/images/specialization.png has changed
--- a/primer/images/specialization.svg Wed Oct 31 13:09:26 2012 +0000
+++ b/primer/images/specialization.svg Wed Oct 31 13:10:51 2012 +0000
@@ -17,7 +17,7 @@
height="197.32617"
xml:space="preserve"
sodipodi:docname="specialization.svg"
- inkscape:export-filename="C:\Work\standards\w3c\prov\primer\images\specialization.png"
+ inkscape:export-filename="C:\Mercurial\prov\primer\images\specialization.png"
inkscape:export-xdpi="90"
inkscape:export-ydpi="90"><metadata
id="metadata8"><rdf:RDF><cc:Work
@@ -408,23 +408,20 @@
<g
- transform="matrix(1,0,0,-1,-16.7571,1099.5101)"
+ transform="matrix(1,0,0,-1,-19.9571,1093.1101)"
id="g544-9"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3"
- transform="translate(-7.640396,-2)"><tspan
+ transform="translate(-7.640396,-2)"
+ style="font-size:9.60000038px"><tspan
sodipodi:role="line"
y="0"
x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448">dataSet1</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448">ex:dataSet1</tspan></text>
+
@@ -451,24 +448,21 @@
style="fill:url(#linearGradient3236);fill-opacity:1;stroke:#000000;stroke-width:1;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
d="m 238.6758,155.4437 c 10.3144,8.5915 10.3144,22.5211 0,31.1126 -10.3145,8.5916 -27.0375,8.5916 -37.3519,0 -10.3145,-8.5915 -10.3145,-22.5211 0,-31.1126 10.3144,-8.5916 27.0374,-8.5916 37.3519,0"
inkscape:connector-curvature="0" /></g><g
- transform="matrix(1,0,0,-1,167.31306,1163.9891)"
+ transform="matrix(1,0,0,-1,164.11306,1157.5891)"
id="g544-9-3"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3-2"
x="-7.6403961"
- y="-2"><tspan
+ y="-2"
+ style="font-size:9.60000038px"><tspan
sodipodi:role="line"
y="-2"
x="-7.6403961"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196-21">ex:</tspan><tspan
- sodipodi:role="line"
- y="11.75"
- x="-7.6403961"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448-6">article</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448-6">ex:article</tspan></text>
+
@@ -503,6 +497,7 @@
+
</g><g
transform="matrix(0.43309751,-0.00230963,0.02385816,-1.4614635,51.707733,1511.0808)"
id="g572"
@@ -524,24 +519,21 @@
style="fill:url(#linearGradient3403);fill-opacity:1;stroke:#000000;stroke-width:1;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
d="m 238.6758,155.4437 c 10.3144,8.5915 10.3144,22.5211 0,31.1126 -10.3145,8.5916 -27.0375,8.5916 -37.3519,0 -10.3145,-8.5915 -10.3145,-22.5211 0,-31.1126 10.3144,-8.5916 27.0374,-8.5916 37.3519,0"
inkscape:connector-curvature="0" /></g><g
- transform="matrix(1,0,0,-1,161.29517,1101.3682)"
+ transform="matrix(1,0,0,-1,156.49517,1094.9682)"
id="g544-9-3-2"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3-2-4"
x="-7.6403961"
- y="-2"><tspan
+ y="-2"
+ style="font-size:9.60000038px"><tspan
sodipodi:role="line"
y="-2"
x="-7.6403961"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196-21-5">ex:</tspan><tspan
- sodipodi:role="line"
- y="11.75"
- x="-7.6403961"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448-6-5">articleV1</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448-6-5">ex:articleV1</tspan></text>
+
</g><g
@@ -570,24 +562,21 @@
style="fill:url(#linearGradient3510);fill-opacity:1;stroke:#000000;stroke-width:1;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
d="m 238.6758,155.4437 c 10.3144,8.5915 10.3144,22.5211 0,31.1126 -10.3145,8.5916 -27.0375,8.5916 -37.3519,0 -10.3145,-8.5915 -10.3145,-22.5211 0,-31.1126 10.3144,-8.5916 27.0374,-8.5916 37.3519,0"
inkscape:connector-curvature="0" /></g><g
- transform="matrix(1,0,0,-1,335.18702,1164.4634)"
+ transform="matrix(1,0,0,-1,331.98702,1159.6634)"
id="g544-9-3-2-3"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3-2-4-2"
x="-7.6403961"
- y="-2"><tspan
+ y="-2"
+ style="font-size:9.60000038px"><tspan
sodipodi:role="line"
y="-2"
x="-7.6403961"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196-21-5-2">ex:</tspan><tspan
- sodipodi:role="line"
- y="11.75"
- x="-7.6403961"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448-6-5-1">blogEntry</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448-6-5-1">ex:blogEntry</tspan></text>
+
</g><g
@@ -622,6 +611,7 @@
id="tspan338-76-71-89">wasQuotedFrom</tspan></text>
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -644,6 +634,7 @@
id="tspan338-5-3">wasDerivedFrom</tspan></text>
+
<g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -659,6 +650,7 @@
id="tspan338-76-2-3">specializationOf</tspan></text>
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -691,6 +683,7 @@
id="tspan338-76-71-89-8">alternateOf</tspan></text>
+
</g><g
transform="matrix(1.2806619,0,0,-1,201.63694,1272.02)"
id="g936-4-8-8"
@@ -701,24 +694,21 @@
style="fill:url(#linearGradient3766);fill-opacity:1;stroke:#000000;stroke-width:1;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
d="m 238.6758,155.4437 c 10.3144,8.5915 10.3144,22.5211 0,31.1126 -10.3145,8.5916 -27.0375,8.5916 -37.3519,0 -10.3145,-8.5915 -10.3145,-22.5211 0,-31.1126 10.3144,-8.5916 27.0374,-8.5916 37.3519,0"
inkscape:connector-curvature="0" /></g><g
- transform="matrix(1,0,0,-1,468.98445,1103.2301)"
+ transform="matrix(1,0,0,-1,465.78445,1096.8301)"
id="g544-9-3-2-0"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3-2-4-24"
x="-7.6403961"
- y="-2"><tspan
+ y="-2"
+ style="font-size:9.60000038px"><tspan
sodipodi:role="line"
y="-2"
x="-7.6403961"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196-21-5-8">ex:</tspan><tspan
- sodipodi:role="line"
- y="11.75"
- x="-7.6403961"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448-6-5-6">articleV2</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448-6-5-6">ex:articleV2</tspan></text>
+
</g><path
@@ -738,23 +728,20 @@
style="fill:url(#linearGradient3439);fill-opacity:1;stroke:#000000;stroke-width:1;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
d="m 238.6758,155.4437 c 10.3144,8.5915 10.3144,22.5211 0,31.1126 -10.3145,8.5916 -27.0375,8.5916 -37.3519,0 -10.3145,-8.5915 -10.3145,-22.5211 0,-31.1126 10.3144,-8.5916 27.0374,-8.5916 37.3519,0"
inkscape:connector-curvature="0" /></g><g
- transform="matrix(1,0,0,-1,250.0613,1052.7504)"
+ transform="matrix(1,0,0,-1,245.2613,1046.3504)"
id="g544-9-2"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3-4"
- transform="translate(-7.640396,-2)"><tspan
+ transform="translate(-7.640396,-2)"
+ style="font-size:9.60000038px"><tspan
sodipodi:role="line"
y="0"
x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196-5">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448-5">dataSet2</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448-5">ex:dataSet2</tspan></text>
+
</g><g
inkscape:export-ydpi="79.550438"
@@ -777,6 +764,7 @@
sodipodi:role="line"
id="tspan338-5-3-1">wasDerivedFrom</tspan></text>
+
<path
id="path344-6-9-0-5"
style="fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none"
@@ -814,4 +802,5 @@
sodipodi:role="line"
id="tspan338-76-2-3-2">specializationOf</tspan></text>
+
</g></g></svg>
\ No newline at end of file
Binary file primer/images/time.png has changed
--- a/primer/images/time.svg Wed Oct 31 13:09:26 2012 +0000
+++ b/primer/images/time.svg Wed Oct 31 13:10:51 2012 +0000
@@ -17,12 +17,12 @@
height="334.96368"
xml:space="preserve"
sodipodi:docname="time.svg"
- inkscape:export-filename="C:\Work\standards\w3c\prov\primer\images\time.png"
+ inkscape:export-filename="C:\Mercurial\prov\primer\images\time.png"
inkscape:export-xdpi="90"
inkscape:export-ydpi="90"><metadata
id="metadata8"><rdf:RDF><cc:Work
rdf:about=""><dc:format>image/svg+xml</dc:format><dc:type
- rdf:resource="http://purl.org/dc/dcmitype/StillImage" /><dc:title /></cc:Work></rdf:RDF></metadata><defs
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" /><dc:title></dc:title></cc:Work></rdf:RDF></metadata><defs
id="defs6"><linearGradient
id="linearGradient3148"><stop
style="stop-color:#ffffff;stop-opacity:1;"
@@ -456,23 +456,20 @@
<g
- transform="matrix(1,0,0,-1,-66.3571,902.71014)"
+ transform="matrix(1,0,0,-1,-71.1571,896.31014)"
id="g544-9"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3"
- transform="translate(-7.640396,-2)"><tspan
+ transform="translate(-7.640396,-2)"
+ style="font-size:9.60000038px"><tspan
sodipodi:role="line"
y="0"
x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448">dataSet1</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448">ex:dataSet1</tspan></text>
+
@@ -504,18 +501,15 @@
inkscape:connector-curvature="0" /></g><text
transform="scale(1,-1)"
id="text546-3-35"
- x="384.71475"
- y="-960.81244"><tspan
- id="tspan3196-9"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="384.71475"
- y="-960.81244"
- sodipodi:role="line">ex:</tspan><tspan
+ x="381.51474"
+ y="-954.41254"
+ style="font-size:9.60000038px"><tspan
id="tspan4448-8"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="384.71475"
- y="-947.06244"
- sodipodi:role="line">dataSet2</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ x="381.51474"
+ y="-954.41254"
+ sodipodi:role="line">ex:dataSet2</tspan></text>
+
@@ -541,6 +535,7 @@
+
</g><path
inkscape:connector-curvature="0"
inkscape:export-ydpi="79.550438"
@@ -562,20 +557,17 @@
id="path264-3-6"
style="fill:url(#linearGradient3791-3);fill-opacity:1;stroke:#000000;stroke-width:1;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
d="m 354.703,221.25 44.17639,0 0,37.5 -44.17639,0 0,-37.5 z" /></g><g
- transform="matrix(1,0,0,-1,521.55993,964.62775)"
+ transform="matrix(1,0,0,-1,518.35993,958.22775)"
id="g266-7-4"><text
id="text268-2-0"
- transform="translate(-13.23096,5)"><tspan
+ transform="translate(-13.23096,5)"
+ style="font-size:9.60000038px"><tspan
+ id="tspan4509-0-1"
y="0"
x="0"
- id="tspan270-6-6"
sodipodi:role="line"
- style="font-size:11.19999981px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:</tspan><tspan
- id="tspan4509-0-1"
- y="14"
- x="0"
- sodipodi:role="line"
- style="font-size:11.19999981px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">compile2</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:compile2</tspan></text>
+
@@ -592,23 +584,20 @@
style="fill:url(#linearGradient4283);fill-opacity:1;stroke:#000000;stroke-width:1;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
d="m 238.6758,155.4437 c 10.3144,8.5915 10.3144,22.5211 0,31.1126 -10.3145,8.5916 -27.0375,8.5916 -37.3519,0 -10.3145,-8.5915 -10.3145,-22.5211 0,-31.1126 10.3144,-8.5916 27.0374,-8.5916 37.3519,0"
inkscape:connector-curvature="0" /></g><g
- transform="matrix(1,0,0,-1,721.54046,901.47234)"
+ transform="matrix(1,0,0,-1,719.94046,895.07234)"
id="g544-9-61-1-3"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3-3-3-9"
- transform="translate(-7.640396,-2)"><tspan
+ transform="translate(-7.640396,-2)"
+ style="font-size:9.60000038px"><tspan
sodipodi:role="line"
y="0"
x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196-8-5-8">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448-9-9-8">chart2</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448-9-9-8">ex:chart2</tspan></text>
+
@@ -659,6 +648,7 @@
+
</g><g
transform="matrix(0.9376888,0.34747621,0.34747621,-0.9376888,651.76262,989.27394)"
id="g334-3-1-0"
@@ -681,6 +671,7 @@
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -719,6 +710,7 @@
+
</g><g
transform="matrix(1.0611643,0,0,-1,-123.33092,1236.364)"
id="g262-7-3"><path
@@ -726,20 +718,17 @@
id="path264-3-4"
style="fill:url(#linearGradient4503);fill-opacity:1;stroke:#000000;stroke-width:1;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
d="m 354.703,221.25 44.17639,0 0,37.5 -44.17639,0 0,-37.5 z" /></g><g
- transform="matrix(1,0,0,-1,271.45542,1006.4641)"
+ transform="matrix(1,0,0,-1,268.25542,1000.0641)"
id="g266-7-8"><text
id="text268-2-4"
- transform="translate(-13.23096,5)"><tspan
+ transform="translate(-13.23096,5)"
+ style="font-size:9.60000038px"><tspan
+ id="tspan4509-0-9"
y="0"
x="0"
- id="tspan270-6-9"
sodipodi:role="line"
- style="font-size:11.19999981px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:</tspan><tspan
- id="tspan4509-0-9"
- y="14"
- x="0"
- sodipodi:role="line"
- style="font-size:11.19999981px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">correct</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:correct</tspan></text>
+
@@ -781,6 +770,7 @@
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -801,6 +791,7 @@
+
</g><path
inkscape:connector-curvature="0"
inkscape:export-ydpi="79.550438"
@@ -842,6 +833,7 @@
+
</g><g
transform="matrix(1.694849,0,0,-1.5821629,158.89211,1431.5985)"
id="g558-3-4-2-1-2"
@@ -886,6 +878,7 @@
+
</g><path
style="fill:none;stroke:#000000;stroke-width:0.65616947px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
d="m 304.6916,995.61216 71.60192,-29.59491"
@@ -927,6 +920,7 @@
+
</g><g
transform="matrix(-0.79741846,0.01415798,0.60418273,1.6898123,518.66471,439.49058)"
id="g572-2-8-3"
@@ -980,20 +974,17 @@
id="path264-3"
style="fill:url(#linearGradient3791);fill-opacity:1;stroke:#000000;stroke-width:1;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
d="m 354.703,221.25 44.17639,0 0,37.5 -44.17639,0 0,-37.5 z" /></g><g
- transform="matrix(1,0,0,-1,375.42439,910.30792)"
+ transform="matrix(1,0,0,-1,373.82439,903.90792)"
id="g266-7"><text
id="text268-2"
- transform="translate(-13.23096,5)"><tspan
+ transform="translate(-13.23096,5)"
+ style="font-size:9.60000038px"><tspan
+ id="tspan4509-0"
y="0"
x="0"
- id="tspan270-6"
sodipodi:role="line"
- style="font-size:11.19999981px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:</tspan><tspan
- id="tspan4509-0"
- y="14"
- x="0"
- sodipodi:role="line"
- style="font-size:11.19999981px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">compile</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:compile</tspan></text>
+
@@ -1025,6 +1016,7 @@
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -1041,6 +1033,7 @@
+
</g><g
inkscape:export-ydpi="79.550438"
inkscape:export-xdpi="79.550438"
@@ -1058,23 +1051,20 @@
d="m -8.2692543,899.96275 8.00000003,-3 0,6 -8.00000003,-3 z"
style="fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none"
id="path344-1" /><g
- transform="matrix(1,0,0,-1,636.2526,835.82601)"
+ transform="matrix(1,0,0,-1,633.0526,829.42601)"
id="g544-9-61-1-3-4"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3-3-3-9-5"
- transform="translate(-7.640396,-2)"><tspan
+ transform="translate(-7.640396,-2)"
+ style="font-size:9.60000038px"><tspan
sodipodi:role="line"
y="0"
x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196-8-5-8-5">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448-9-9-8-1">chart1</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448-9-9-8-1">ex:chart1</tspan></text>
+
Binary file primer/images/use-generate.png has changed
--- a/primer/images/use-generate.svg Wed Oct 31 13:09:26 2012 +0000
+++ b/primer/images/use-generate.svg Wed Oct 31 13:10:51 2012 +0000
@@ -17,7 +17,7 @@
height="143.57451"
xml:space="preserve"
sodipodi:docname="use-generate.svg"
- inkscape:export-filename="C:\Work\standards\w3c\prov\primer\images\use-generate.png"
+ inkscape:export-filename="C:\Mercurial\prov\primer\images\use-generate.png"
inkscape:export-xdpi="90"
inkscape:export-ydpi="90"><metadata
id="metadata8"><rdf:RDF><cc:Work
@@ -151,20 +151,17 @@
id="path264"
style="fill:url(#linearGradient4517);fill-opacity:1;stroke:#000000;stroke-width:1;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
d="m 354.703,221.25 44.17639,0 0,37.5 -44.17639,0 0,-37.5 z" /></g><g
- transform="matrix(1,0,0,-1,195.9912,841.6)"
+ transform="matrix(1,0,0,-1,194.3912,835.2)"
id="g266"><text
id="text268"
- transform="translate(-13.23096,5)"><tspan
+ transform="translate(-13.23096,5)"
+ style="font-size:9.60000038px"><tspan
+ id="tspan4509"
y="0"
x="0"
- id="tspan270"
sodipodi:role="line"
- style="font-size:11.19999981px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:</tspan><tspan
- id="tspan4509"
- y="14"
- x="0"
- sodipodi:role="line"
- style="font-size:11.19999981px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">compose</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:compose</tspan></text>
+
@@ -186,19 +183,16 @@
inkscape:export-xdpi="79.550438"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
id="g544-9-6"
- transform="matrix(1,0,0,-1,24.41479,834.24439)"><text
+ transform="matrix(1,0,0,-1,19.61479,827.84439)"><text
transform="translate(-7.640396,-2)"
- id="text546-3-0"><tspan
- id="tspan3196-2"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="text546-3-0"
+ style="font-size:9.60000038px"><tspan
+ id="tspan4448-4"
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
x="0"
y="0"
- sodipodi:role="line">ex:</tspan><tspan
- id="tspan4448-4"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- x="0"
- y="13.75"
- sodipodi:role="line">regionList</tspan></text>
+ sodipodi:role="line">ex:regionList</tspan></text>
+
</g><g
@@ -208,20 +202,17 @@
id="path264-6"
style="fill:url(#linearGradient4584);fill-opacity:1;stroke:#000000;stroke-width:1;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
d="m 354.703,221.25 44.17639,0 0,37.5 -44.17639,0 0,-37.5 z" /></g><g
- transform="matrix(1,0,0,-1,525.13557,841.352)"
+ transform="matrix(1,0,0,-1,523.53557,834.952)"
id="g266-6"><text
id="text268-18"
- transform="translate(-13.23096,5)"><tspan
+ transform="translate(-13.23096,5)"
+ style="font-size:9.60000038px"><tspan
+ id="tspan4509-9"
y="0"
x="0"
- id="tspan270-4"
sodipodi:role="line"
- style="font-size:11.19999981px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:</tspan><tspan
- id="tspan4509-9"
- y="14"
- x="0"
- sodipodi:role="line"
- style="font-size:11.19999981px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">illustrate</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">ex:illustrate</tspan></text>
+
</g><g
@@ -244,6 +235,7 @@
+
</g><g
transform="matrix(0.9368205,0,0,-1,-142.39394,1071.5)"
id="g340"
@@ -280,6 +272,7 @@
+
</g><g
transform="matrix(1,0,0,-1,-175.5,1071.5)"
id="g498"
@@ -359,29 +352,27 @@
+
</g>
<g
- transform="matrix(1,0,0,-1,24.8429,902.71014)"
+ transform="matrix(1,0,0,-1,23.2429,896.31014)"
id="g544-9"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3"
- transform="translate(-7.640396,-2)"><tspan
+ transform="translate(-7.640396,-2)"
+ style="font-size:9.60000038px"><tspan
sodipodi:role="line"
y="0"
x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448">dataSet1</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448">ex:dataSet1</tspan></text>
+
@@ -425,6 +416,7 @@
style="font-size:12px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">used</tspan></text>
+
</g><g
transform="matrix(1,0,0,-1,629.04784,839.08001)"
id="g334-3"
@@ -440,6 +432,7 @@
style="font-size:12px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT">wasGeneratedBy</tspan></text>
+
</g><g
transform="matrix(1,0,0,-1,159.42784,1071.63)"
id="g340-4"
@@ -459,23 +452,20 @@
style="fill:url(#linearGradient4539);fill-opacity:1;stroke:#000000;stroke-width:1;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
d="m 238.6758,155.4437 c 10.3144,8.5915 10.3144,22.5211 0,31.1126 -10.3145,8.5916 -27.0375,8.5916 -37.3519,0 -10.3145,-8.5915 -10.3145,-22.5211 0,-31.1126 10.3144,-8.5916 27.0374,-8.5916 37.3519,0"
inkscape:connector-curvature="0" /></g><g
- transform="matrix(1,0,0,-1,366.35927,833.36467)"
+ transform="matrix(1,0,0,-1,361.55927,826.96467)"
id="g544-9-61"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3-3"
- transform="translate(-7.640396,-2)"><tspan
+ transform="translate(-7.640396,-2)"
+ style="font-size:9.60000038px"><tspan
sodipodi:role="line"
y="0"
x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196-8">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448-9">composition</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448-9">ex:composition</tspan></text>
+
</g><path
@@ -495,23 +485,20 @@
style="fill:url(#linearGradient4670);fill-opacity:1;stroke:#000000;stroke-width:1;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;stroke-opacity:1;stroke-dasharray:none"
d="m 238.6758,155.4437 c 10.3144,8.5915 10.3144,22.5211 0,31.1126 -10.3145,8.5916 -27.0375,8.5916 -37.3519,0 -10.3145,-8.5915 -10.3145,-22.5211 0,-31.1126 10.3144,-8.5916 27.0374,-8.5916 37.3519,0"
inkscape:connector-curvature="0" /></g><g
- transform="matrix(1,0,0,-1,702.38205,832.92622)"
+ transform="matrix(1,0,0,-1,700.78205,826.52622)"
id="g544-9-61-1"
inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/images/w3-publication1.png"
inkscape:export-xdpi="79.550438"
inkscape:export-ydpi="79.550438"><text
id="text546-3-3-3"
- transform="translate(-7.640396,-2)"><tspan
+ transform="translate(-7.640396,-2)"
+ style="font-size:9.60000038px"><tspan
sodipodi:role="line"
y="0"
x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan3196-8-5">ex:</tspan><tspan
- sodipodi:role="line"
- y="13.75"
- x="0"
- style="font-size:11px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
- id="tspan4448-9-9">chart1</tspan></text>
+ style="font-size:9.60000038px;font-variant:normal;font-weight:normal;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none;font-family:ArialMT;-inkscape-font-specification:ArialMT"
+ id="tspan4448-9-9">ex:chart1</tspan></text>
+
</g></g></svg>
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/primer/primer-provn-examples.txt Wed Oct 31 13:10:51 2012 +0000
@@ -0,0 +1,84 @@
+prefix prov <http://www.w3.org/ns/prov#>
+prefix ex <http://www.example.org#>
+prefix dcterms <http://purl.org/dc/terms/>
+prefix foaf <http://xmlns.com/foaf/0.1/>
+
+// The examples below are taken from, and follow the same order
+// as in, the W3C PROV Primer, http://www.w3.org/TR/prov-primer/
+
+// Entities
+
+entity(ex:article, [dcterms:title='Crime rises in cities'])
+entity(ex:dataSet1)
+entity(ex:regionList)
+entity(ex:composition)
+entity(ex:chart1)
+
+// Activities
+
+activity(ex:compile)
+activity(ex:compose)
+activity(ex:illustrate)
+
+// Usage and Generation
+
+used(ex:compose, ex:dataSet1, -)
+used(ex:compose, ex:regionList, -)
+wasGeneratedBy(ex:composition, ex:compose, -)
+used(ex:illustrate, ex:composition, -)
+wasGeneratedBy(ex:chart1, ex:illustrate, -)
+
+// Agents and Responsibility
+
+wasAssociatedWith(ex:compose, ex:derek, -)
+wasAssociatedWith(ex:illustrate, ex:derek, -)
+agent(ex:derek,
+ [prov:type='prov:Person', foaf:givenName='Derek',
+ foaf:mbox='<mailto:derek@example.org>'])
+
+agent(ex:chartgen,
+ [prov:type='prov:Organization',
+ foaf:name = 'Chart Generators Inc'])
+actedOnBehalfOf(ex:derek, ex:chartgen, ex:compose)
+
+wasAttributedTo(ex:chart1, ex:derek)
+
+// Roles
+
+used(ex:compose, ex:dataSet1, -, [prov:role='ex:dataToCompose'])
+used(ex:compose, ex:regionList, -, [prov:role='ex:regionsToAggregateBy'])
+wasAssociatedWith(ex:compose, ex:derek, -, [prov:role='ex:analyst'])
+wasGeneratedBy(ex:composition, ex:compose, -, [prov:role='ex:composedData'])
+
+// Derivation and Revision
+
+entity(ex:dataSet2)
+wasDerivedFrom(ex:dataSet2, ex:dataSet1, [prov:type='prov:Revision'])
+wasDerivedFrom(ex:chart2, ex:dataSet2)
+entity(ex:chart2)
+wasDerivedFrom(ex:chart2, ex:chart1, [prov:type='prov:Revision'])
+
+// Plans
+
+activity(ex:correct)
+agent(ex:edith, [prov:type='prov:Person'])
+entity(ex:instructions)
+wasAssociatedWith(ex:correct, ex:edith, ex:instructions)
+wasGeneratedBy(ex:dataSet2, ex:correct, -)
+
+// Time
+
+wasGeneratedBy(ex:chart1, ex:compile, 2012-03-02T10:30:00)
+wasGeneratedBy(ex:chart2, ex:compile2, 2012-04-01T15:21:00)
+activity(ex:correct, 2012-03-31T09:21:00, 2012-04-01T15:21:00)
+
+// Alternate Entities and Specialization
+
+entity(ex:blogEntry)
+wasDerivedFrom(ex:blogEntry, ex:article, [prov:type='prov:Quotation'])
+
+entity(ex:articleV1)
+specializationOf(ex:articleV1, ex:article)
+specializationOf(ex:articleV2, ex:article)
+alternateOf(ex:articleV2, ex:articleV1)
+
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/primer/primer-turtle-examples.txt Wed Oct 31 13:10:51 2012 +0000
@@ -0,0 +1,113 @@
+@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
+@prefix prov: <http://www.w3.org/ns/prov#> .
+@prefix ex: <http://www.example.org#> .
+@prefix dcterms: <http://purl.org/dc/terms/> .
+@prefix foaf: <http://xmlns.com/foaf/0.1/> .
+
+# The examples below are taken from, and follow the same order
+# as in the W3C PROV Primer, http://www.w3.org/TR/prov-primer/
+
+# Entities
+
+ex:article a prov:Entity ;
+ dcterms:title "Crime rises in cities" .
+ex:dataset1 a prov:Entity .
+ex:regionList a prov:Entity .
+ex:composition a prov:Entity .
+ex:chart1 a prov:Entity .
+
+# Activities
+
+ex:compile a prov:Activity .
+ex:compose a prov:Activity .
+ex:illustrate a prov:Activity .
+
+# Usage and Generation
+
+ex:compose prov:used ex:dataSet1 ;
+ prov:used ex:regionList .
+ex:composition prov:wasGeneratedBy ex:compose .
+ex:illustrate prov:used ex:composition .
+ex:chart1 prov:wasGeneratedBy ex:illustrate .
+
+# Agents and Responsibility
+
+ex:compose prov:wasAssociatedWith ex:derek .
+ex:illustrate prov:wasAssociatedWith ex:derek .
+ex:derek a prov:Agent ;
+ a prov:Person ;
+ foaf:givenName "Derek"^^xsd:string ;
+ foaf:mbox <mailto:derek@example.org> .
+ex:derek prov:actedOnBehalfOf ex:chartgen .
+ex:chartgen a prov:Agent ;
+ a prov:Organization ;
+ foaf:name "Chart Generators Inc" .
+ex:chart1 prov:wasAttributedTo ex:derek .
+
+# Roles
+
+ex:dataToCompose a prov:Role .
+ex:regionsToAggregateBy a prov:Role .
+ex:composedData a prov:Role .
+ex:analyst a prov:Role .
+ex:compose prov:qualifiedUsage [
+ a prov:Usage ;
+ prov:entity ex:dataSet1 ;
+ prov:hadRole ex:dataToCompose
+] .
+ex:compose prov:qualifiedUsage [
+ a prov:Usage ;
+ prov:entity ex:regionList ;
+ prov:hadRole ex:regionsToAggregateBy
+] .
+ex:compose prov:qualifiedAssociation [
+ a prov:Association ;
+ prov:agent ex:derek ;
+ prov:hadRole ex:analyst
+] .
+ex:composition prov:qualifiedGeneration [
+ a prov:Generation ;
+ prov:activity ex:compose ;
+ prov:hadRole ex:composedData
+] .
+
+# Revision and Derivation
+
+ex:dataSet2 a prov:Entity ;
+ prov:wasRevisionOf ex:dataSet1 .
+ex:chart2 a prov:Entity ;
+ prov:wasDerivedFrom ex:dataSet2 .
+ex:chart2 a prov:Entity ;
+ prov:wasRevisionOf ex:chart1 .
+
+# Plans
+
+ex:correct a prov:Activity .
+ex:edith a prov:Agent, prov:Person .
+ex:instructions a prov:Plan .
+
+ex:correct prov:qualifiedAssociation [
+ a Association ;
+ prov:agent ex:edith ;
+ prov:hadPlan ex:instructions
+] .
+ex:dataSet2 prov:wasGeneratedBy ex:correct .
+
+# Time
+
+ex:chart1 prov:generatedAtTime "2012-03-02T10:30:00"^^xsd:dateTime .
+ex:chart2 prov:generatedAtTime "2012-04-01T15:21:00"^^xsd:dateTime .
+
+ex:correct prov:startedAtTime "2012-03-31T09:21:00"^^xsd:dateTime ;
+ prov:endedAtTime "2012-04-01T15:21:00"^^xsd:dateTime .
+
+# Alternate Entities and Specialization
+
+ex:blogEntry a prov:Entity ;
+ prov:wasQuotedFrom ex:article .
+
+ex:articleV1 a prov:Entity ;
+ prov:specializationOf ex:article .
+
+ex:articleV2 prov:specializationOf ex:article .
+ex:articleV2 prov:alternateOf ex:articleV1 .
\ No newline at end of file
--- a/reports/prov-implementations.html Wed Oct 31 13:09:26 2012 +0000
+++ b/reports/prov-implementations.html Wed Oct 31 13:10:51 2012 +0000
@@ -720,13 +720,13 @@
<td class="notused"> </td>
</tr>
<tr>
- <td class="feature"><a href="http://www.w3.org/TR/prov-constraints/#key-properties_text">Constraint 24 (key-properties)</a><a href="http://www.w3.org/TR/prov-constraints/#impossible-object-property-overlap_text"></a></td>
+ <td class="feature"><a href="http://www.w3.org/TR/prov-constraints/#key-properties_text">Constraint 24 (key-properties)</a></td>
<td class="implemented"> </td>
<td class="notused"> </td>
<td class="notused"> </td>
</tr>
<tr>
- <td class="feature"><a href="http://www.w3.org/TR/prov-constraints/#unique-generation_text">Constraint 25 (unique-generation)</a><a href="http://www.w3.org/TR/prov-constraints/#key-properties_text"></a></td>
+ <td class="feature"><a href="http://www.w3.org/TR/prov-constraints/#unique-generation_text">Constraint 25 (unique-generation)</a></td>
<td class="implemented"> </td>
<td class="notused"> </td>
<td class="notused"> </td>
@@ -774,7 +774,7 @@
<td class="notused"> </td>
</tr>
<tr>
- <td class="feature"><a href="http://www.w3.org/TR/prov-constraints/#start-start-ordering_text">Constraint 33 (start-start-ordering)</a><a href="http://www.w3.org/TR/prov-constraints/#generation-use-communication-inference_text"></a></td>
+ <td class="feature"><a href="http://www.w3.org/TR/prov-constraints/#start-start-ordering_text">Constraint 33 (start-start-ordering)</a></td>
<td class="implemented"> </td>
<td class="notused"> </td>
<td class="notused"> </td>
@@ -792,13 +792,13 @@
<td class="notused"> </td>
</tr>
<tr>
- <td class="feature"><a href="http://www.w3.org/TR/prov-constraints/#generation-within-activity_text">Constraint 36 (generation-within-activity)</a><a href="http://www.w3.org/TR/prov-constraints/#unique-generation_text"></a></td>
+ <td class="feature"><a href="http://www.w3.org/TR/prov-constraints/#generation-within-activity_text">Constraint 36 (generation-within-activity)</a></td>
<td class="implemented"> </td>
<td class="notused"> </td>
<td class="notused"> </td>
</tr>
<tr>
- <td class="feature"><a href="http://www.w3.org/TR/prov-constraints/#wasInformedBy-ordering_text">Constraint 37 (wasInformedBy-ordering)</a><a href="http://www.w3.org/TR/prov-constraints/#generation-within-activity_text"></a></td>
+ <td class="feature"><a href="http://www.w3.org/TR/prov-constraints/#wasInformedBy-ordering_text">Constraint 37 (wasInformedBy-ordering)</a></td>
<td class="implemented"> </td>
<td class="notused"> </td>
<td class="notused"> </td>
@@ -912,13 +912,13 @@
<td class="notused"> </td>
</tr>
<tr>
- <td class="feature"><a href="http://www.w3.org/TR/prov-constraints/#impossible-object-property-overlap_text">Constraint 56 (impossible-object-property-overlap)</a><a href="http://www.w3.org/TR/prov-constraints/#entity-activity-disjoint_text"></a></td>
+ <td class="feature"><a href="http://www.w3.org/TR/prov-constraints/#impossible-object-property-overlap_text">Constraint 56 (impossible-object-property-overlap)</a></td>
<td class="implemented"> </td>
<td class="notused"> </td>
<td class="notused"> </td>
</tr>
<tr>
- <td class="feature"><a href="http://www.w3.org/TR/prov-constraints/#entity-activity-disjoint_text">Constraint 57 (entity-activity-disjoint)</a><a href="http://www.w3.org/TR/prov-constraints/#activity-start-end-inference_text"></a></td>
+ <td class="feature"><a href="http://www.w3.org/TR/prov-constraints/#entity-activity-disjoint_text">Constraint 57 (entity-activity-disjoint)</a></td>
<td class="implemented"> </td>
<td class="notused"> </td>
<td class="notused"> </td>
--- a/testcases/constraints/process.html Wed Oct 31 13:09:26 2012 +0000
+++ b/testcases/constraints/process.html Wed Oct 31 13:10:51 2012 +0000
@@ -61,9 +61,9 @@
editors: [
{ name: "Trung Dong Huynh", url: "http://www.ecs.soton.ac.uk/~tdh/",
company: "University of Southampton" },
- { name: "Paul Groth", url: "http://www.few.vu.nl/~pgroth/",
+ { name: "Paul Groth", url: "http://www.few.vu.nl/~pgroth/",
company: "VU University of Amsterdam" },
- { name: "Stephan Zednik", url: "http://tw.rpi.edu/web/person/StephanZednik",
+ { name: "Stephan Zednik", url: "http://tw.rpi.edu/web/person/StephanZednik",
company: "Rensselaer Polytechnic Institute" },
],
@@ -97,7 +97,7 @@
<body>
<section id="abstract">
-<p>This document describes the process for generating the implementation report for PROV-CONSTRAINTS.
+<p>This document describes the process for generating the implementation report for [[PROV-CONSTRAINTS]].
It provides the instructions for implementers on running PROV-CONSTRAINTS test cases and reporting their results.
It also outlines the organization of test cases and results by the Prov Working Group.</p>
</section>
@@ -108,7 +108,9 @@
<section id="test-cases">
<h3>Test cases</h3>
<p>The test cases will be made available online at: <URI><br />
- Every test case has an identifier, e.g. <strong>entity10</strong>. The provenance document for the test case will be provided in the following representations:</p>
+ Every test case has an identifier, e.g. <strong>entity10-c23-c56-c57</strong>.
+ The numberings of the constraints covered by a test case are included with its identifier, e.g. c23, c56, and c57.
+ The provenance document for each test case will be provided in the following representations:</p>
<table border="1" cellspacing="0" cellpadding="0" width="623">
<caption>Table 1. File representations provided for test cases.</caption>
@@ -140,7 +142,9 @@
</tr>
</table>
-<p>For example, the files <strong>entity10.xml</strong>, <strong>entity10.trig</strong>, <strong>entity10.json</strong>, and <strong>entity10.provn</strong> for the test case <strong>entity10</strong> are made available at <URI>.</p>
+<p>For example, the files <strong>entity10-c23-c56-c57.xml</strong>, <strong>entity10-c23-c56-c57.trig</strong>,
+<strong>entity10-c23-c56-c57.json</strong>, and <strong>entity10-c23-c56-c57.provn</strong> for the test case
+<strong>entity10-c23-c56-c57</strong> can be found at <URI>.</p>
<p>Each test case is designed to test particular constraints, an overview of which is provided in Table 2 below.</p>
</section>
@@ -148,12 +152,14 @@
<section id="test-results">
<h3>Test Results</h3>
-<p>Implementers are asked to validate each test case with their implementation and recorded the validation results <em>two plain text files</em>: <strong>success.txt</strong> and <strong>fail.txt</strong>. These files should contain the identifiers (one on each line) of the test cases that have been successfully validated in the former and those that fail validation in the latter. Test cases that are not supported by the implementation <strong>should not</strong> be included in either of the files.</p>
+<p>Implementers are asked to validate each test case with their implementation and recorded the validation results <em>two plain text files</em>: <strong>success.txt</strong> and <strong>fail.txt</strong>.
+These files MUST contain the identifiers (one on each line) of the test cases that have been successfully validated in the former and those that fail validation in the latter.
+Test cases that are not supported by the implementation SHOULD NOT be included in either of the files.</p>
<p>The test result files will need to be <emailed to|uploaded at>. </p>
-<p class="note">Dong: What else the implementer should provide us with? With the test results, I think they won't need to fill in the questionnaire. Therefore, we
-might need to ask them to provide some basic information about their
+<p class="note">Dong: What else the implementer should provide us with? Having provided the test results, I think they won't need to fill in the questionnaire.
+Therefore, we might need to ask them to provide some basic information about their
implementations (i.e. the questionnaire 1<sup>st</sup> page).</p>
</section>
@@ -167,8 +173,8 @@
<p>All test cases need to be checked for the constraints they cover and their expected validation results (i.e. Success or Fail).</p>
-<p class="note">Dong: These test cases are from Luc’s ProvToolbox. We need to check whether all the constraints are sufficiently covered and curate from the WG or generate ourselves the test cases for constraints that haven’t been covered by these.</p>
-
+<p class="note">Dong: We need to check whether all the constraints are sufficiently covered and curate from the WG or generate ourselves the test cases for constraints that haven’t been covered by these.</p>
+
<table border="1" cellspacing="0" cellpadding="0">
<caption>Table 2. Available test cases (127 in total)</caption>
<tr>
@@ -178,768 +184,59 @@
<td><b>Notes</b></p></td>
</tr>
<tr>
- <td><b>activity1</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>activity2</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>activity3</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>activity4</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>activity5</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>activity6</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>activity7</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>activity8</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>activity9</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>agent1</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>agent2</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>agent3</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>agent4</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>agent5</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>agent6</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>agent7</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>agent8</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>alternate1</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>association1</b></p></td>
- <td> </td>
- <td>Fail</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>association2</b></p></td>
- <td> </td>
- <td>Fail</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>association3</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>association4</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>association5</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>association6</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>association7</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>association8</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>association9</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>attribution1</b></p></td>
- <td> </td>
- <td>Fail</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>attribution2</b></p></td>
- <td> </td>
- <td>Fail</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>attribution3</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>attribution4</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>attribution5</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>attribution6</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>attribution7</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>attribution8</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>communication1</b></p></td>
- <td> </td>
- <td>Fail</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>communication2</b></p></td>
- <td> </td>
- <td>Fail</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>communication3</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>communication4</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>communication5</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>communication6</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>communication7</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>delegation1</b></p></td>
- <td> </td>
- <td>Fail</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>delegation2</b></p></td>
- <td> </td>
- <td>Fail</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>delegation3</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>delegation4</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>delegation5</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>delegation6</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>delegation7</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>delegation8</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>derivation10</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>derivation11</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>derivation12</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>derivation13</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>derivation1</b></p></td>
- <td> </td>
- <td>Fail</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>derivation2</b></p></td>
- <td> </td>
- <td>Fail</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>derivation3</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>derivation4</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>derivation5</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>derivation6</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>derivation7</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>derivation8</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>derivation9</b></p></td>
- <td> </td>
+ <td><b>activity1-c23-c56-c57</b></p></td>
+ <td><a href="http://www.w3.org/TR/prov-constraints/#key-object_text">Constraint 23 (key-object)</a> <br />
+ <a href="http://www.w3.org/TR/prov-constraints/#impossible-object-property-overlap_text">Constraint 56 (impossible-object-property-overlap)</a><br />
+ <a href="http://www.w3.org/TR/prov-constraints/#entity-activity-disjoint_text">Constraint 57 (entity-activity-disjoint)</a>
+ </td>
<td>Success</p></td>
<td> </td>
</tr>
<tr>
- <td><b>end10</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>end1</b></p></td>
- <td> </td>
- <td>Fail</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>end2</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>end3</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>end4</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>end5</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>end6</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>end7</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>end8</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>end9</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>entity10</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>entity1</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>entity2</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>entity3</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>entity4</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>entity5</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>entity6</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>entity7</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>entity8</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>entity9</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>generation1</b></p></td>
- <td> </td>
- <td>Fail</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>generation2</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>generation3</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>generation4</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>generation5</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>generation6</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>generation7</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>influence1</b></p></td>
- <td> </td>
- <td>Fail</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>influence2</b></p></td>
- <td> </td>
- <td>Fail</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>influence3</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>influence4</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>influence5</b></p></td>
- <td> </td>
+ <td><b>activity2-c23-c56-c57</b></p></td>
+ <td><a href="http://www.w3.org/TR/prov-constraints/#key-object_text">Constraint 23 (key-object)</a> <br />
+ <a href="http://www.w3.org/TR/prov-constraints/#impossible-object-property-overlap_text">Constraint 56 (impossible-object-property-overlap)</a><br />
+ <a href="http://www.w3.org/TR/prov-constraints/#entity-activity-disjoint_text">Constraint 57 (entity-activity-disjoint)</a>
+ </td>
<td>Success</p></td>
<td> </td>
</tr>
<tr>
- <td><b>influence6</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>influence7</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>invalidation1</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>invalidation2</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>invalidation3</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>invalidation4</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>invalidation5</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>invalidation6</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>invalidation7</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>member1</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>member2</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>member3</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>mention1</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>mention2</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>specialization1</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>start10</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>start1</b></p></td>
- <td> </td>
+ <td><b>association1-c24-c52</b></p></td>
+ <td><a href="http://www.w3.org/TR/prov-constraints/#key-properties_text">Constraint 24 (key-properties)</a><br />
+ <a href="http://www.w3.org/TR/prov-constraints/#typing_text"><b>Constraint 52 (typing)</b></a>
+ </td>
<td>Fail</p></td>
<td> </td>
</tr>
<tr>
- <td><b>start2</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>start3</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>start4</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>start5</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>start6</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>start7</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>start8</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>start9</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>usage1</b></p></td>
- <td> </td>
+ <td><b>association2-c24-c52</b></p></td>
+ <td><a href="http://www.w3.org/TR/prov-constraints/#key-properties_text">Constraint 24 (key-properties)</a><br />
+ <a href="http://www.w3.org/TR/prov-constraints/#typing_text"><b>Constraint 52 (typing)</b></a>
+ </td>
<td>Fail</p></td>
<td> </td>
</tr>
<tr>
- <td><b>usage2</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>usage3</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>usage4</b></p></td>
- <td> </td>
- <td>Success</p></td>
+ <td><b>delegation1-c24-c52-c55</b></p></td>
+ <td><a href="http://www.w3.org/TR/prov-constraints/#key-properties_text">Constraint 24 (key-properties)</a><br />
+ <a href="http://www.w3.org/TR/prov-constraints/#typing_text"><b>Constraint 52 (typing)</b></a><br />
+ <a href="http://www.w3.org/TR/prov-constraints/#impossible-property-overlap_text">Constraint 55 (impossible-property-overlap)</a>
+ </td>
+ <td>Fail</p></td>
<td> </td>
</tr>
<tr>
- <td><b>usage5</b></p></td>
- <td> </td>
- <td>Success</p></td>
+ <td><b>delegation2-c24-c52-c55</b></p></td>
+ <td><a href="http://www.w3.org/TR/prov-constraints/#key-properties_text">Constraint 24 (key-properties)</a><br />
+ <a href="http://www.w3.org/TR/prov-constraints/#typing_text"><b>Constraint 52 (typing)</b></a><br />
+ <a href="http://www.w3.org/TR/prov-constraints/#impossible-property-overlap_text">Constraint 55 (impossible-property-overlap)</a>
+ </td>
+ <td>Fail</p></td>
<td> </td>
</tr>
- <tr>
- <td><b>usage6</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
- <tr>
- <td><b>usage7</b></p></td>
- <td> </td>
- <td>Success</p></td>
- <td> </td>
- </tr>
-</table>
+</table>
+<p class="note">The constraints in bold above (in the second column) are the ones that SHOULD fail to validate.</p>
<p>For each report, the successful and failed
validations will need to be checked against the expected validation results in Table 2 above . A
test case is considered to be successful if its validation result is the same
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/xml/ReSpec.js/bibref/biblio.js Wed Oct 31 13:10:51 2012 +0000
@@ -0,0 +1,1022 @@
+
+/*
+I8, 8 ,8I db 88888888ba 888b 88 88 888b 88 ,ad8888ba, 88
+`8b d8b d8' d88b 88 "8b 8888b 88 88 8888b 88 d8"' `"8b 88
+ "8, ,8"8, ,8" d8'`8b 88 ,8P 88 `8b 88 88 88 `8b 88 d8' 88
+ Y8 8P Y8 8P d8' `8b 88aaaaaa8P' 88 `8b 88 88 88 `8b 88 88 88
+ `8b d8' `8b d8' d8YaaaaY8b 88""""88' 88 `8b 88 88 88 `8b 88 88 88888 88
+ `8a a8' `8a a8' d8""""""""8b 88 `8b 88 `8b 88 88 88 `8b 88 Y8, 88 ""
+ `8a8' `8a8' d8' `8b 88 `8b 88 `8888 88 88 `8888 Y8a. .a88 aa
+ `8' `8' d8' `8b 88 `8b 88 `888 88 88 `888 `"Y88888P" 88
+
+
+
+
+
+
+
+
+
+
+88888888ba, db 888b 88 ,ad8888ba, 88888888888 88888888ba 88
+88 `"8b d88b 8888b 88 d8"' `"8b 88 88 "8b 88
+88 `8b d8'`8b 88 `8b 88 d8' 88 88 ,8P 88
+88 88 d8' `8b 88 `8b 88 88 88aaaaa 88aaaaaa8P' 88
+88 88 d8YaaaaY8b 88 `8b 88 88 88888 88""""" 88""""88' 88
+88 8P d8""""""""8b 88 `8b 88 Y8, 88 88 88 `8b ""
+88 .a8P d8' `8b 88 `8888 Y8a. .a88 88 88 `8b aa
+88888888Y"' d8' `8b 88 `888 `"Y88888P" 88888888888 88 `8b 88
+
+
+
+
+
+ Got your attention? Good. Please read the following carefully.
+
+ You are currently editing the bibliographical database for ReSpec version 1.
+
+ The version of ReSpec, as of this writing, is 3.1. That should raise a red flag.
+
+ The code behind ReSpec v1 is no longer supported. It is still in this repository, and
+ the plan is that it will stay there. You can use it, and you can patch it. But it
+ isn't officially supported, so you have to understand that you're essentially on your
+ own.
+
+ For the time being, at regular intervals I take the edits that people make in this
+ file, and push them to the new version (note that I don't do the reverse though, so
+ you're not getting the collectively-gathered bibliographical updates that others
+ are). As of TPAC 2012, I will stop doing even just that, and the v1 codeline will be
+ entirely extinct. You can keep on using it anyway, so long as you are aware of the
+ consquences.
+
+ Why would you switch to v3? Well, unless you've been doing something really naughty,
+ it's completely backwards compatible. It's 5x smaller (and that's going to improve
+ even more soon) and makes 10x fewer HTTP requests to load. Dozens of bugs have been
+ fixed since maintenance stopped on the v1 line, and a number of features have been
+ added. People have spontaneously written in to say how much faster it is. The code is
+ modular, can easily be extended, and ReSpec can now be used to process other types of
+ technical documents just by rearranging the modules differently. It's test suite
+ and new development cycle should also help ensure that it doesn't break live.
+
+ Wow, that's increadibly sexy! How do I upgrade?
+ You replace:
+ <script src='http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js' class='remove'></script>
+ with:
+ <script src='http://www.w3.org/Tools/respec/respec-w3c-common' class='remove' async></script>
+
+ And normally you should be done. If you see issues: robin@berjon.com.
+
+ I still want to contribute to the biblio DB, what do I do?
+ Until TPAC 2012, if you're still using v1 you can just edit here and at some point I
+ will reflect the change in the v3 DB.
+ If you've switched to v3, you can edit the DB by forking the repository at
+ https://github.com/darobin/respec/ and making a pull request (that can entirely be
+ done online if you're in a hurry).
+ Managing the DB in this way is not wonderful, it is only kept around for now while
+ in the transition period (which is to say, until TPAC 2012). After that, there will
+ just be a Web-based system that will progressively become easier to use.
+
+
+ Brought to you with care and loving from Robin Berjon <robin@berjon.com>
+
+*/
+
+berjon.biblio = {
+ "ABA-DSIG-GUIDELINES" : "<a href=\"http://www.signelec.com/content/download/digital_signature_guidelines.pdf\"><cite>Digital Signature Guidelines.</cite></a> 1 August 1996. Information Security Committee, American Bar Association. URL: <a href=\"http://www.signelec.com/content/download/digital_signature_guidelines.pdf\">http://www.signelec.com/content/download/digital_signature_guidelines.pdf</a>",
+ "ABC" : "Leo Geurts; Lambert Meertens; Steven Pemberton. <a href=\"http://www.cwi.nl/~steven/abc\"><cite>The ABC Programmer's Handbook.</cite></a> Prentice-Hall. ISBN: 0-13-000027-2. URL: <a href=\"http://www.cwi.nl/~steven/abc\">http://www.cwi.nl/~steven/abc</a>",
+ "ABNF" : "D. Crocker and P. Overell. <a href='http://www.ietf.org/rfc/rfc5234.txt'><cite>Augmented BNF for Syntax Specifications: ABNF.</cite></a> January 2008. Internet RFC 5234. URL: <a href='http://www.ietf.org/rfc/rfc5234.txt'>http://www.ietf.org/rfc/rfc5234.txt</a>",
+ "ACCESS-CONTROL" : "Anne van Kesteren. <a href=\"http://www.w3.org/TR/2008/WD-access-control-20080912\"><cite>Access Control for Cross-Site Requests.</cite></a> 12 September 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-access-control-20080912\">http://www.w3.org/TR/2008/WD-access-control-20080912</a> ",
+ "ACDI" : "Rhys Lewis. <a href=\"http://www.w3.org/TR/2003/NOTE-acdi-20030901\"><cite>Authoring Challenges for Device Independence.</cite></a> 1 September 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-acdi-20030901\">http://www.w3.org/TR/2003/NOTE-acdi-20030901</a> ",
+ "ACSS" : "Chris Lilley; T. V. Raman. <a href=\"http://www.w3.org/TR/1999/WD-acss-19990902\"><cite>Aural Cascading Style Sheets (ACSS) Specification.</cite></a> 2 September 1999. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/1999/WD-acss-19990902\">http://www.w3.org/TR/1999/WD-acss-19990902</a> ",
+ "AD-INDUSTRY" : "American Association of Advertising Industries, et al. <a href=\"http://www.iab.net/media/file/ven-principles-07-01-09.pdf\"><cite>Self-Regulatory Principles for Online Behavioral Advertising</cite></a> July 2009. URL: http://www.iab.net/media/file/ven-principles-07-01-09.pdf ",
+ "AERT" : "Chris Ridpath; Wendy Chisholm. <a href=\"http://www.w3.org/TR/2000/WD-AERT-20000426\"><cite>Techniques For Accessibility Evaluation And Repair Tools.</cite></a> 26 April 2000. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2000/WD-AERT-20000426\">http://www.w3.org/TR/2000/WD-AERT-20000426</a> ",
+ "AES" : "<a href=\"http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf\"><cite>NIST FIPS 197: Advanced Encryption Standard (AES)</cite></a>. November 2001. URL: <a href=\"http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf\">http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf</a>",
+ "AES-WRAP" : "J. Schaad and R. Housley. <a href=\"http://www.ietf.org/rfc/rfc3394.txt\"><cite>RFC3394: Advanced Encryption Standard (AES) Key Wrap Algorithm</cite></a>. IETF Informational RFC, September 2002. URL: <a href=\"http://www.rfc-editor.org/rfc/rfc3394.txt\">http://www.rfc-editor.org/rfc/rfc3394.txt</a>",
+ "AES-WRAP-PAD" : "R. Housley, M. Dworkin. <a href=\"http://www.ietf.org/rfc/rfc5649.txt\"><cite>RFC 5649: Advanced Encryption Standard (AES) Key Wrap with Padding Algorithm</cite></a>. IETF Informational RFC, August 2009. URL: <a href=\"http://www.ietf.org/rfc/rfc5649.txt\"> http://www.ietf.org/rfc/rfc5649.txt</a>. ",
+ "AGBDL" : "Charles Jacobs; et al. <a href=\"http://grail.cs.washington.edu/pub/papers/Jacobs2003.pdf\">“Adaptive Grid Based Document Layout”</a> in: <cite>ACM Transactions on Graphics.</cite> 22. 3. pp. 838–847. July 2003. URL: <a href=\"http://grail.cs.washington.edu/pub/papers/Jacobs2003.pdf\">http://grail.cs.washington.edu/pub/papers/Jacobs2003.pdf</a> ",
+ "ANSI-X9-44-2007" : "<a href=\"http://webstore.ansi.org/RecordDetail.aspx?sku=ANSI+X9.44-2007\"><cite>ANSI X9.44-2007: Key Establishment Using Integer Factorization Cryptography.</cite></a> URL: <a href=\"http://webstore.ansi.org/RecordDetail.aspx?sku=ANSI+X9.44-2007\">http://webstore.ansi.org/RecordDetail.aspx?sku=ANSI+X9.44-2007</a>",
+ "ARABIC-MATH" : "Azzeddine Lazrek; Bruce R. Miller. <a href=\"http://www.w3.org/TR/2006/NOTE-arabic-math-20060131\"><cite>Arabic mathematical notation.</cite></a> 31 January 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-arabic-math-20060131\">http://www.w3.org/TR/2006/NOTE-arabic-math-20060131</a> ",
+ "ARABIC-TYPO" : "Huda Smitshuijzen AbiFares. <cite>Arabic Typography: A Comprehensive Sourcebook.</cite> Saqi Books. 2001. ISBN 0-86356-347-3.",
+ "ATAG-WOMBAT" : "Jan Richards; Charles McCathieNevile; Jutta Treviranus. <a href=\"http://www.w3.org/TR/2001/WD-ATAG-wombat-20011221\"><cite>Authoring Tool Accessibility Guidelines "Wombat".</cite></a> 21 December 2001. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2001/WD-ATAG-wombat-20011221\">http://www.w3.org/TR/2001/WD-ATAG-wombat-20011221</a> ",
+ "ATAG10" : "Jutta Treviranus; et al. <a href=\"http://www.w3.org/TR/2000/REC-ATAG10-20000203\"><cite>Authoring Tool Accessibility Guidelines 1.0.</cite></a> 3 February 2000. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2000/REC-ATAG10-20000203\">http://www.w3.org/TR/2000/REC-ATAG10-20000203</a> ",
+ "ATAG10-TECHS" : "Gregory Rosmaita; et al. <a href=\"http://www.w3.org/TR/2002/NOTE-ATAG10-TECHS-20021029\"><cite>Techniques for Authoring Tool Accessibility Guidelines 1.0.</cite></a> 29 October 2002. W3C Note. URL: <a href=\"http://www.w3.org/TR/2002/NOTE-ATAG10-TECHS-20021029\">http://www.w3.org/TR/2002/NOTE-ATAG10-TECHS-20021029</a> ",
+ "ATAG20" : "Jan Richards; Jutta Treviranus; Jeanne Spellman. <a href=\"http://www.w3.org/TR/2009/WD-ATAG20-20090217\"><cite>Authoring Tool Accessibility Guidelines (ATAG) 2.0.</cite></a> 17 February 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-ATAG20-20090217\">http://www.w3.org/TR/2009/WD-ATAG20-20090217</a> ",
+ "ATAG20-TECHS" : "Jan Richards; Jutta Treviranus; Tim Boland. <a href=\"http://www.w3.org/TR/2008/WD-ATAG20-TECHS-20080310\"><cite>Implementation Techniques for Authoring Tool Accessibility Guidelines 2.0.</cite></a> 10 March 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-ATAG20-TECHS-20080310\">http://www.w3.org/TR/2008/WD-ATAG20-TECHS-20080310</a> ",
+ "BACKPLANE" : "Steven Pemberton; et al. <a href=\"http://www.w3.org/TR/2006/NOTE-backplane-20061116\"><cite>Rich Web Application Backplane.</cite></a> 16 November 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-backplane-20061116\">http://www.w3.org/TR/2006/NOTE-backplane-20061116</a> ",
+ "BBC-WP193" : "J.P. Barrett; M.E. Hammond; S.J.E Jolly. <a href=\"http://www.bbc.co.uk/rd/publications/whitepaper193.shtml\"><cite>White Paper 193 : The Universal Control API version 0.6.0 - An Overview</cite></a>. June 2011. URL: <a href=\"http://www.bbc.co.uk/rd/publications/whitepaper193.shtml\">http://www.bbc.co.uk/rd/publications/whitepaper193.shtml</a>",
+ "BBC-WP194" : "J.P. Barrett; M.E. Hammond; S.J.E Jolly. <a href=\"http://www.bbc.co.uk/rd/publications/whitepaper194.shtml\"><cite>White Paper 194 : The Universal Control API v.0.6.0 - Specification for the behaviour of a universal control server running on a set-top box, and the clients that connect to it</cite></a>. June 2011. URL: <a href=\"http://www.bbc.co.uk/rd/publications/whitepaper194.shtml\">http://www.bbc.co.uk/rd/publications/whitepaper194.shtml</a>",
+ "BCP47" : "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> ",
+ "BECSS" : "Ian Hickson. <a href=\"http://www.w3.org/TR/2007/WD-becss-20071019\"><cite>Behavioral Extensions to CSS.</cite></a> 19 October 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-becss-20071019\">http://www.w3.org/TR/2007/WD-becss-20071019</a> ",
+ "BLOB" : "Arun Ranganathan. <a href=\"http://www.w3.org/TR/2009/WD-FileAPI-20091117/#dfn-Blob\"><cite>Blob.</cite></a> 17 November 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-FileAPI-20091117/\">http://www.w3.org/TR/2009/WD-FileAPI-20091117/#dfn-Blob</a> ",
+ "BONDI-ARCH-SECURITY-11" : "<a href=\"http://bondi.omtp.org/1.11/security/BONDI_Architecture_and_Security_v1.1.pdf\"><cite>BONDI Architecture & Security Requirements v1.1</cite></a> 27 January 2010. URL: <a href=\"http://bondi.omtp.org/1.11/security/BONDI_Architecture_and_Security_v1.1.pdf\">http://bondi.omtp.org/1.11/security/BONDI_Architecture_and_Security_v1.1.pdf</a> ",
+ "BONDI-FEATURES1-11" : "<a href=\"http://bondi.omtp.org/1.11/apis/apifeatures.html\"><cite>BONDI API Features v1.11</cite></a> 2 June 2010. URL: <a href=\"http://bondi.omtp.org/1.11/apis/apifeatures.html\">http://bondi.omtp.org/1.11/apis/apifeatures.html</a> ",
+ "C14N-ISSUES" : "Konrad Lanz; José Kahan. <a href=\"http://www.w3.org/TR/2006/NOTE-C14N-issues-20061220\"><cite>Known Issues with Canonical XML 1.0 (C14N/1.0).</cite></a> 20 December 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-C14N-issues-20061220\">http://www.w3.org/TR/2006/NOTE-C14N-issues-20061220</a> ",
+ "C14N2-TestCases" : "Pratik Datta, Frederick Hirsch, <a href=\"http://www.w3.org/2008/xmlsec/Drafts/c14n-20/test-cases/\"><cite>Test Cases for Canonical XML 2.0</cite></a> 5 January 2012. W3C First Public Working Draft (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/WD-xml-c14n2-testcases-20120105/\">http://www.w3.org/TR/2012/WD-xml-c14n2-testcases-20120105/</a>",
+ "CALL-CONTROL-REQS" : "Brad Porter. <a href=\"http://www.w3.org/TR/2001/WD-call-control-reqs-20010413\"><cite>Call Control Requirements in a Voice Browser Framework.</cite></a> 13 April 2001. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2001/WD-call-control-reqs-20010413\">http://www.w3.org/TR/2001/WD-call-control-reqs-20010413</a> ",
+ "CEA-2014" : "<a href=\"http://www.ce.org/Standards/browseByCommittee_2757.asp\"><cite>Web-based Protocol and Framework for Remote User Interface on UPnP Networks and the Internet (Web4CE)</cite></a>. January 2011. ANSI/CEA Standard. URL: <a href=\"http://www.ce.org/Standards/browseByCommittee_2757.asp\">http://www.ce.org/Standards/browseByCommittee_2757.asp</a>",
+ "CLABS-HNAPI": "<a href=\"http://www.w3.org/2011/webtv/HNTF/CableLabs_Revised_API_20110727-2.pdf\"><cite>CableLabs Revised Home Networking API</cite></a>. 26 July 2011. Draft proposal. URL: <a href=\"http://www.w3.org/2011/webtv/HNTF/CableLabs_Revised_API_20110727-2.pdf\">http://www.w3.org/2011/webtv/HNTF/CableLabs_Revised_API_20110727-2.pdf</a>",
+ "CANVAS-2D" : "Ian Hickson. <a href=\"http://www.w3.org/TR/2dcontext/\"><cite>HTML Canvas 2D Context.</cite></a> 25 May 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2dcontext/\">http://www.w3.org/TR/2dcontext/</a> ",
+ "CC-ABOUT" : "<a href = 'http://creativecommons.org/about/licenses/'><cite>Creative Commons: About Licenses</cite></a> URL: http://creativecommons.org/about/licenses/ ",
+ "CC-CHOOSE" : "<a href = 'http://creativecommons.org/choose/'><cite>Creative Commons: License Your Work</cite></a> URL: http://creativecommons.org/choose/ ",
+ "CCPP" : "Franklin Reynolds; et al. <a href=\"http://www.w3.org/TR/2004/REC-CCPP-struct-vocab-20040115\"><cite>Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 1.0.</cite></a> 15 January 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-CCPP-struct-vocab-20040115\">http://www.w3.org/TR/2004/REC-CCPP-struct-vocab-20040115</a> ",
+ "CCPP-COORDINATION" : "Johan Hjelm; Lalitha Suryanarayana. <a href=\"http://www.w3.org/TR/2001/NOTE-CCPP-COORDINATION-20011220\"><cite>CC/PP Implementors Guide: Harmonization with Existing Vocabularies and Content Transformation Heuristics.</cite></a> 20 December 2001. W3C Note. URL: <a href=\"http://www.w3.org/TR/2001/NOTE-CCPP-COORDINATION-20011220\">http://www.w3.org/TR/2001/NOTE-CCPP-COORDINATION-20011220</a> ",
+ "CCPP-RA" : "Johan Hjelm; Mikael Nilsson; Hidetaka Ohto. <a href=\"http://www.w3.org/TR/2000/WD-CCPP-ra-20000721\"><cite>Composite Capabilities/Preference Profiles: Requirements and Architecture.</cite></a> 21 July 2000. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2000/WD-CCPP-ra-20000721\">http://www.w3.org/TR/2000/WD-CCPP-ra-20000721</a> ",
+ "CCPP-STRUCT-VOCAB2" : "Cédric Kiss. <a href=\"http://www.w3.org/TR/2007/WD-CCPP-struct-vocab2-20070430\"><cite>Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 2.0.</cite></a> 30 April 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-CCPP-struct-vocab2-20070430\">http://www.w3.org/TR/2007/WD-CCPP-struct-vocab2-20070430</a> ",
+ "CCPP-TA" : "Mikael Nilsson. <a href=\"http://www.w3.org/TR/2000/WD-CCPP-ta-20000721\"><cite>Composite Capabilities/Preference Profiles: Terminology and Abbreviations.</cite></a> 21 July 2000. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2000/WD-CCPP-ta-20000721\">http://www.w3.org/TR/2000/WD-CCPP-ta-20000721</a> ",
+ "CCPP-TRUST" : "Johan Hjelm; Hidetaka Ohto; Lalitha Suryanarayana. <a href=\"http://www.w3.org/TR/2001/WD-CCPP-trust-20011220\"><cite>CC/PP Implementors Guide: Privacy and Protocols.</cite></a> 20 December 2001. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2001/WD-CCPP-trust-20011220\">http://www.w3.org/TR/2001/WD-CCPP-trust-20011220</a> ",
+ "CCXML" : "RJ Auburn. <a href=\"http://www.w3.org/TR/2007/WD-ccxml-20070119\"><cite>Voice Browser Call Control: CCXML Version 1.0.</cite></a> 19 January 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-ccxml-20070119\">http://www.w3.org/TR/2007/WD-ccxml-20070119</a> ",
+ "CDFREQS" : "Steve Speicher; Petri Vuorimaa. <a href=\"http://www.w3.org/TR/2005/WD-CDFReqs-20051219\"><cite>Compound Document Use Cases and Requirements Version 2.0.</cite></a> 19 December 2005. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2005/WD-CDFReqs-20051219\">http://www.w3.org/TR/2005/WD-CDFReqs-20051219</a> ",
+ "CDR" : "Lasse Pajunen; et al. <a href=\"http://www.w3.org/TR/2007/CR-CDR-20070718\"><cite>Compound Document by Reference Framework 1.0.</cite></a> 18 July 2007. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/CR-CDR-20070718\">http://www.w3.org/TR/2007/CR-CDR-20070718</a> ",
+ "CDRREQS" : "Daniel Appelquist; Antoine Quint; Timur Mehrvarz. <a href=\"http://www.w3.org/TR/2005/NOTE-CDRReqs-20051219\"><cite>Compound Document by Reference Use Cases and Requirements Version 1.0.</cite></a> 19 December 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-CDRReqs-20051219\">http://www.w3.org/TR/2005/NOTE-CDRReqs-20051219</a> ",
+ "CGM" : "Roy Platon; Chris Lilley. <a href=\"http://www.w3.org/TR/NOTE-cgm-970618\"><cite>Use of CGM as a Scalable Graphics Format.</cite></a> 18 June 1997. W3C Note. URL: <a href=\"http://www.w3.org/TR/NOTE-cgm-970618\">http://www.w3.org/TR/NOTE-cgm-970618</a> ",
+ "CHARMOD" : "Martin J. Dürst; et al. <a href=\"http://www.w3.org/TR/2005/REC-charmod-20050215\"><cite>Character Model for the World Wide Web 1.0: Fundamentals.</cite></a> 15 February 2005. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2005/REC-charmod-20050215\">http://www.w3.org/TR/2005/REC-charmod-20050215</a> ",
+ "CHARMOD-NORM" : "Martin J. Dürst; et al. <a href=\"http://www.w3.org/TR/2005/WD-charmod-norm-20051027\"><cite>Character Model for the World Wide Web 1.0: Normalization.</cite></a> 27 October 2005. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2005/WD-charmod-norm-20051027\">http://www.w3.org/TR/2005/WD-charmod-norm-20051027</a> ",
+ "CHARMOD-RESID" : "François Yergeau; et al. <a href=\"http://www.w3.org/TR/2004/CR-charmod-resid-20041122\"><cite>Character Model for the World Wide Web 1.0: Resource Identifiers.</cite></a> 22 November 2004. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2004/CR-charmod-resid-20041122\">http://www.w3.org/TR/2004/CR-charmod-resid-20041122</a> ",
+ "CHARREQ" : "Martin J. Dürst. <a href=\"http://www.w3.org/TR/1998/WD-charreq-19980710\"><cite>Requirements for String Identity Matching and String Indexing.</cite></a> 10 July 1998. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/1998/WD-charreq-19980710\">http://www.w3.org/TR/1998/WD-charreq-19980710</a> ",
+ "CHARSETS" : "<a href=\"http://www.iana.org/assignments/character-sets\"><cite>Characters sets.</cite></a> These are the official names for character sets that may be used in the Internet and may be referred to in Internet documentation URL: <a href=\"http://www.iana.org/assignments/character-sets\">http://www.iana.org/assignments/character-sets</a> ",
+ "CLIPBOARD-APIS" : "Doug Schepers; Charles McCathieNevile. <a href=\"http://www.w3.org/TR/2006/WD-clipboard-apis-20061115\"><cite>Clipboard Operations for the Web 1.0: Copy, Paste, Drag and Drop.</cite></a> 15 November 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-clipboard-apis-20061115\">http://www.w3.org/TR/2006/WD-clipboard-apis-20061115</a> ",
+ "CMS-Algorithms" : "R. Housley. <a href=\"http://www.ietf.org/rfc/rfc3370.txt\"><cite>RFC3370: Cryptographic Message Syntax (CMS) Algorithms</cite></a>. IETF Informational RFC, February 2002. URL: <a href=\"http://www.ietf.org/rfc/rfc3370.txt\">http://www.ietf.org/rfc/rfc3370.txt</a>",
+ "CMS-WRAP" : "R. Housley. <a href=\"http://www.ietf.org/rfc/rfc3217.txt\"><cite>RFC3217: Triple-DES and R2 Key Wrapping</cite></a>. IETF Informational RFC, December 2001. URL: <a href=\"http://www.ietf.org/rfc/rfc3217.txt\">http://www.ietf.org/rfc/rfc3217.txt</a>",
+ "COLORIMETRY" : "<cite>Colorimetry, Second Edition.</cite> CIE Publication 15.2-1986. ISBN 3-900-734-00-3",
+ "CONSENT-EU-WP187" : "WP189, <a href=\"http://ec.europa.eu/justice/policies/privacy/docs/wpdocs/2011/wp187_en.pdf\"><cite>Opinion 15/2011 on the definition of consent</cite></a>. EU Article 29 Data Protection Working Party, 01197/11/EN WP187. 13 July 2011. URL: <a href=\"http://ec.europa.eu/justice/policies/privacy/docs/wpdocs/2011/wp187_en.pdf\">http://ec.europa.eu/justice/policies/privacy/docs/wpdocs/2011/wp187_en.pdf</a>",
+ "CONTACTS-API" : "R. Tibbett. <a href=\"http://dev.w3.org/2009/dap/contacts/Overview.html\"><cite>Contacts API</cite></a>. 3rd August 2010. W3C Latest Editor's Draft. (Work in progress.) URL: <a href=\"http://dev.w3.org/2009/dap/contacts/Overview.html\">http://dev.w3.org/2009/dap/contacts/Overview.html</a> ",
+ "CONTACTS-WRITER-API" : "R. Tibbett. <a href=\"http://dev.w3.org/2009/dap/contacts/Writer.html\"><cite>Contacts Writer API</cite></a>. 3rd August 2010. W3C Latest Editor's Draft. (Work in progress.) URL: <a href=\"http://dev.w3.org/2009/dap/contacts/Writer.html\">http://dev.w3.org/2009/dap/contacts/Writer.html</a> ",
+ "CONTENT-IN-RDF" : "Carlos A Velasco; Johannes Koch. <a href=\"http://www.w3.org/TR/2008/WD-Content-in-RDF-20080908\"><cite>Representing Content in RDF.</cite></a> 8 September 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-Content-in-RDF-20080908\">http://www.w3.org/TR/2008/WD-Content-in-RDF-20080908</a> ",
+ "COOKIES": "Adam Barth. <cite><a href=\"http://www.rfc-editor.org/rfc/rfc6265.txt\">HTTP State Management Mechanism</a>.</cite> April 2011. Internet Proposed Standard RFC 6265. URL: <a href=\"http://www.rfc-editor.org/rfc/rfc6265.txt\">http://www.rfc-editor.org/rfc/rfc6265.txt</a> ",
+ "COOLURIS" : "Richard Cyganiak; Leo Sauermann. <a href=\"http://www.w3.org/TR/2008/NOTE-cooluris-20081203\"><cite>Cool URIs for the Semantic Web.</cite></a> 3 December 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-cooluris-20081203\">http://www.w3.org/TR/2008/NOTE-cooluris-20081203</a> ",
+ "CORS" : "Anne van Kesteren. <a href=\"http://www.w3.org/TR/2009/WD-cors-20090317\"><cite>Cross-Origin Resource Sharing.</cite></a> 17 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-cors-20090317\">http://www.w3.org/TR/2009/WD-cors-20090317</a> ",
+ "CORE-DEVICE" : "Robin Berjon. <a href=\"http://dev.w3.org/2009/dap/device/\"><cite>Core Device Interfaces.</cite></a> 02 December 2009. W3C Editor's Draft. (Work in progress.) URL: <a href=\"http://dev.w3.org/2009/dap/device/\">http://dev.w3.org/2009/dap/device/</a> ",
+ "Coloring-RDF" : "Giorgos Flouris; Irini Fundulaki; Panagiotis Pediaditis; Yannis Theoharis; Vassilis Christophides. <a href=\"http://data.semanticweb.org/conference/iswc/2009/paper/research/165/html\"><cite>Coloring RDF Triples to Capture Provenance</cite></a> 2009. The Semantic Web - ISWC 2009, Washington DC, Springer-Verlag,. URL: <a href='http://data.semanticweb.org/conference/iswc/2009/paper/research/165/html'>http://data.semanticweb.org/conference/iswc/2009/paper/research/165/html</a> ",
+ "Context-SW" : "R.M.R. Guha; R. Fikes. <cite>Contexts for the Semantic Web</cite>. 2005. The Semantic Web — ISWC2004. Yokohama, Japan: Springer-Verlag",
+ "CPC-REQ" : "Markus Lauff; Amy Yu. <a href=\"http://www.w3.org/TR/2003/WD-cpc-req-20030510\"><cite>Core Presentation Characteristics: Requirements and Use Cases.</cite></a> 10 May 2003. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2003/WD-cpc-req-20030510\">http://www.w3.org/TR/2003/WD-cpc-req-20030510</a> ",
+ "CSELECTION" : "Rhys Lewis; Max Froumentin; Roland Merrick. <a href=\"http://www.w3.org/TR/2007/CR-cselection-20070725\"><cite>Content Selection for Device Independence (DISelect) 1.0.</cite></a> 25 July 2007. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/CR-cselection-20070725\">http://www.w3.org/TR/2007/CR-cselection-20070725</a> ",
+ "CSELECTION-PRIMER" : "Roland Merrick; Rhys Lewis. <a href=\"http://www.w3.org/TR/2007/WD-cselection-primer-20070109\"><cite>Content Selection Primer 1.0.</cite></a> 9 January 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-cselection-primer-20070109\">http://www.w3.org/TR/2007/WD-cselection-primer-20070109</a> ",
+ "CSELECTION-XAF" : "Rhys Lewis; Roland Merrick. <a href=\"http://www.w3.org/TR/2007/CR-cselection-xaf-20070725\"><cite>Delivery Context: XPath Access Functions 1.0.</cite></a> 25 July 2007. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/CR-cselection-xaf-20070725\">http://www.w3.org/TR/2007/CR-cselection-xaf-20070725</a> ",
+ "CSS-MOBILE" : "Svante Schubert. <a href=\"http://www.w3.org/TR/2008/CR-css-mobile-20081210\"><cite>CSS Mobile Profile 2.0.</cite></a> 10 December 2008. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/CR-css-mobile-20081210\">http://www.w3.org/TR/2008/CR-css-mobile-20081210</a> ",
+ "CSS-POTENTIAL" : "Bert Bos. <a href=\"http://www.w3.org/TR/1998/NOTE-CSS-potential-19981210\"><cite>List of suggested extensions to CSS.</cite></a> 10 December 1998. W3C Note. URL: <a href=\"http://www.w3.org/TR/1998/NOTE-CSS-potential-19981210\">http://www.w3.org/TR/1998/NOTE-CSS-potential-19981210</a> ",
+ "CSS-PRINT" : "Melinda Grant. <a href=\"http://www.w3.org/TR/2006/WD-css-print-20061013\"><cite>CSS Print Profile.</cite></a> 13 October 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-css-print-20061013\">http://www.w3.org/TR/2006/WD-css-print-20061013</a> ",
+ "CSS-TV" : "Sean Hayes; et al. <a href=\"http://www.w3.org/TR/2003/CR-css-tv-20030514\"><cite>CSS TV Profile 1.0.</cite></a> 14 May 2003. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2003/CR-css-tv-20030514\">http://www.w3.org/TR/2003/CR-css-tv-20030514</a> ",
+ "CSS1" : "Håkon Wium Lie; Bert Bos. <a href=\"http://www.w3.org/TR/2008/REC-CSS1-20080411\"><cite>Cascading Style Sheets (CSS1) Level 1 Specification.</cite></a> 11 April 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-CSS1-20080411\">http://www.w3.org/TR/2008/REC-CSS1-20080411</a> ",
+ "CSS2" : "Ian Jacobs; et al. <a href=\"http://www.w3.org/TR/CSS21/\"><cite>Cascading Style Sheets, level 2 (CSS2) Specification.</cite></a> 07 June 2011. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-CSS2-20080411\">http://www.w3.org/TR/2008/REC-CSS2-20080411</a> ",
+ "CSS21" : "Bert Bos; et al. <a href=\"http://www.w3.org/TR/CSS21/\"><cite>Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification.</cite></a>. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/CSS21\">http://www.w3.org/TR/CSS21/</a> ",
+ "CSS3-2D-TRANSFORMS" : "Simon Fraser; Dean Jackson; David Hyatt; Chris Marrin; Edward O'Connor. <a href=\"http://www.w3.org/TR/css3-2d-transforms/\"><cite>CSS 2D Transforms Module Level 3.</cite></a> URL: <a href=\"http://www.w3.org/TR/css3-2d-transforms/\">http://www.w3.org/TR/css3-2d-transforms/</a> ",
+ "CSS3-3D-TRANSFORMS" : "Dean Jackson; David Hyatt; Chris Marrin. <a href=\"http://www.w3.org/TR/css3-3d-transforms/\"><cite>CSS 3D Transforms Module Level 3.</cite></a> URL: <a href=\"http://www.w3.org/TR/css3-3d-transforms/\">http://www.w3.org/TR/css3-3d-transforms</a> ",
+ "CSS3-ANIMATIONS" : "Dean Jackson (Apple Inc); David Hyatt (Apple Inc); Chris Marrin (Apple Inc). <a href=\"http://www.w3.org/TR/css3-animations/\"><cite>CSS Animations Module Level 3.</cite></a> URL: <a href=\"http://www.w3.org/TR/css3-animations/\">http://www.w3.org/TR/css3-animations/</a> ",
+ "CSS3-HYPERLINKS" : "Daniel Glazman; Bert Bos; Tantek Çelik. <a href=\"http://www.w3.org/TR/2004/WD-css3-hyperlinks-20040224\"><cite>CSS3 Hyperlink Presentation Module.</cite></a> 24 February 2004. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2004/WD-css3-hyperlinks-20040224\">http://www.w3.org/TR/2004/WD-css3-hyperlinks-20040224</a> ",
+ "CSS3-MARQUEE" : "Bert Bos. <a href=\"http://www.w3.org/TR/2008/CR-css3-marquee-20081205\"><cite>CSS Marquee Module Level 3.</cite></a> 5 December 2008. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/CR-css3-marquee-20081205\">http://www.w3.org/TR/2008/CR-css3-marquee-20081205</a> ",
+ "CSS3-PRESLEV" : "Ian Hickson; Håkon Wium Lie. <a href=\"http://www.w3.org/TR/2003/WD-css3-preslev-20030813\"><cite>CSS3 module: Presentation Levels.</cite></a> 13 August 2003. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2003/WD-css3-preslev-20030813\">http://www.w3.org/TR/2003/WD-css3-preslev-20030813</a> ",
+ "CSS3-READER" : "Bert Bos. <a href=\"http://www.w3.org/TR/2004/WD-css3-reader-20040224\"><cite>The CSS 'Reader' Media Type.</cite></a> 24 February 2004. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2004/WD-css3-reader-20040224\">http://www.w3.org/TR/2004/WD-css3-reader-20040224</a> ",
+ "CSS3-TRANSITIONS" : "Dean Jackson; David Hyatt; Chris Marrin. <a href=\"http://www.w3.org/TR/2009/WD-css3-transitions-20090320\"><cite>CSS Transitions Module Level 3.</cite></a> 20 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-css3-transitions-20090320\">http://www.w3.org/TR/2009/WD-css3-transitions-20090320</a> ",
+ "CSS3-WEBFONTS" : "Michel Suignard; Chris Lilley. <a href=\"http://www.w3.org/TR/2002/WD-css3-webfonts-20020802\"><cite>CSS3 module: Web Fonts.</cite></a> 2 August 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-css3-webfonts-20020802\">http://www.w3.org/TR/2002/WD-css3-webfonts-20020802</a> ",
+ "CSS3-BG" : "Elika J. Etemad; Bert Bos; Brad Kemper. <a href=\"http://www.w3.org/TR/css3-background/\"><cite>CSS Backgrounds and Borders Module Level 3.</cite></a> URL: <a href=\"http://www.w3.org/TR/css3-background/\">http://www.w3.org/TR/css3-background/</a> ",
+ "CSS3BORDER" : "Tapas Roy. <a href=\"http://www.w3.org/TR/2002/WD-css3-border-20021107\"><cite>CSS3 module: Border.</cite></a> 7 November 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-css3-border-20021107\">http://www.w3.org/TR/2002/WD-css3-border-20021107</a> ",
+ "CSS3BOX" : "Bert Bos. <a href=\"http://www.w3.org/TR/2007/WD-css3-box-20070809\"><cite>CSS basic box model.</cite></a> 9 August 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-css3-box-20070809\">http://www.w3.org/TR/2007/WD-css3-box-20070809</a> ",
+ "CSS3CASCADE" : "Håkon Wium Lie. <a href=\"http://www.w3.org/TR/2005/WD-css3-cascade-20051215\"><cite>CSS3 module: Cascading and inheritance.</cite></a> 15 December 2005. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2005/WD-css3-cascade-20051215\">http://www.w3.org/TR/2005/WD-css3-cascade-20051215</a> ",
+ "CSS3COL" : "Håkon Wium Lie. <a href=\"http://www.w3.org/TR/2007/WD-css3-multicol-20070606\"><cite>CSS3 module: Multi-column layout.</cite></a> 6 June 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-css3-multicol-20070606\">http://www.w3.org/TR/2007/WD-css3-multicol-20070606</a> ",
+ "CSS3COLOR" : "Chris Lilley; Tantek Çelik; L. David Baron. <a href=\"http://www.w3.org/TR/2008/WD-css3-color-20080721\"><cite>CSS Color Module Level 3.</cite></a> 21 July 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-css3-color-20080721\">http://www.w3.org/TR/2008/WD-css3-color-20080721</a> ",
+ "CSS3-FONTS" : "John Daggett (Mozilla). <a href=\"http://www.w3.org/TR/css3-fonts\"><cite>CSS Fonts Module Level 3</cite></a> URL: <a href=\"http://www.w3.org/TR/css3-fonts\">http://www.w3.org/TR/css3-fonts</a> ",
+ "CSS3-FONTS-20020802" : "Michel Suignard; Chris Lilley. <a href=\"http://www.w3.org/TR/2002/WD-css3-fonts-20020802\"><cite>CSS3 module: Fonts.</cite></a> 2 August 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-css3-fonts-20020802\">http://www.w3.org/TR/2002/WD-css3-fonts-20020802</a> ",
+ "CSS3GCPM" : "Håkon Wium Lie. <a href=\"http://www.w3.org/TR/2007/WD-css3-gcpm-20070504\"><cite>CSS3 module: Generated Content for Paged Media.</cite></a> 4 May 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-css3-gcpm-20070504\">http://www.w3.org/TR/2007/WD-css3-gcpm-20070504</a> ",
+ "CSS3GENCON" : "Ian Hickson. <a href=\"http://www.w3.org/TR/2003/WD-css3-content-20030514\"><cite>CSS3 Generated and Replaced Content Module.</cite></a> 14 May 2003. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2003/WD-css3-content-20030514\">http://www.w3.org/TR/2003/WD-css3-content-20030514</a> ",
+ "CSS3GRID" : "Markus Mielke; Alex Mogilevsky. <a href=\"http://www.w3.org/TR/2007/WD-css3-grid-20070905\"><cite>CSS Grid Positioning Module Level 3.</cite></a> 5 September 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-css3-grid-20070905\">http://www.w3.org/TR/2007/WD-css3-grid-20070905</a> ",
+ "CSS3INTRO" : "Eric A. Meyer; Bert Bos. <a href=\"http://www.w3.org/TR/2001/WD-css3-roadmap-20010523\"><cite>CSS3 introduction.</cite></a> 23 May 2001. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2001/WD-css3-roadmap-20010523\">http://www.w3.org/TR/2001/WD-css3-roadmap-20010523</a> ",
+ "CSS3LAYOUT" : "Bert Bos. <a href=\"http://www.w3.org/TR/2007/WD-css3-layout-20070809\"><cite>CSS Advanced Layout Module.</cite></a> 9 August 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-css3-layout-20070809\">http://www.w3.org/TR/2007/WD-css3-layout-20070809</a> ",
+ "CSS3LINE" : "Michel Suignard; Eric A. Meyer. <a href=\"http://www.w3.org/TR/2002/WD-css3-linebox-20020515\"><cite>CSS3 module: line.</cite></a> 15 May 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-css3-linebox-20020515\">http://www.w3.org/TR/2002/WD-css3-linebox-20020515</a> ",
+ "CSS3LIST" : "Ian Hickson; Tantek Çelik. <a href=\"http://www.w3.org/TR/2002/WD-css3-lists-20021107\"><cite>CSS3 module: Lists.</cite></a> 7 November 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-css3-lists-20021107\">http://www.w3.org/TR/2002/WD-css3-lists-20021107</a> ",
+ "CSS3MARQUEE" : "Bert Bos. <a href=\"http://www.w3.org/TR/2008/CR-css3-marquee-20081205\"><cite>CSS Marquee Module Level 3.</cite></a> 5 December 2008. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/CR-css3-marquee-20081205\">http://www.w3.org/TR/2008/CR-css3-marquee-20081205</a> ",
+ "CSS3-MEDIAQUERIES" : "H. Lie, T. Çelik, D. Glazman, A. van Kesteren. <a href=\"http://www.w3.org/TR/css3-mediaqueries/\"><cite>Media Queries</cite></a> URL: <a href=\"http://www.w3.org/TR/css3-mediaqueries/\">http://www.w3.org/TR/css3-mediaqueries/</a> ",
+ "CSS3NAMESPACE" : "Anne van Kesteren; Elika J. Etemad. <a href=\"http://www.w3.org/TR/2008/CR-css3-namespace-20080523\"><cite>CSS Namespaces Module.</cite></a> 23 May 2008. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/CR-css3-namespace-20080523\">http://www.w3.org/TR/2008/CR-css3-namespace-20080523</a> ",
+ "CSS3PAGE" : "Melinda Grant; Håkon Wium Lie. <a href=\"http://www.w3.org/TR/2006/WD-css3-page-20061010\"><cite>CSS3 Module: Paged Media.</cite></a> 10 October 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-css3-page-20061010\">http://www.w3.org/TR/2006/WD-css3-page-20061010</a> ",
+ "CSS3POS" : "Bert Bos. <cite>CSS3 Positioning Module.</cite> (forthcoming). W3C Working Draft. (Work in progress.)",
+ "CSS3RUBY" : "Michel Suignard. <a href=\"http://www.w3.org/TR/2003/CR-css3-ruby-20030514\"><cite>CSS3 Ruby Module.</cite></a> 14 May 2003. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2003/CR-css3-ruby-20030514\">http://www.w3.org/TR/2003/CR-css3-ruby-20030514</a> ",
+ "CSS3SPEECH" : "David Raggett; Daniel Glazman; Claudio Santambrogio. <a href=\"http://www.w3.org/TR/2004/WD-css3-speech-20041216\"><cite>CSS3 Speech Module.</cite></a> 16 December 2004. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2004/WD-css3-speech-20041216\">http://www.w3.org/TR/2004/WD-css3-speech-20041216</a> ",
+ "CSS3SYN" : "L. David Baron. <a href=\"http://www.w3.org/TR/2003/WD-css3-syntax-20030813\"><cite>CSS3 module: Syntax.</cite></a> 13 August 2003. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2003/WD-css3-syntax-20030813\">http://www.w3.org/TR/2003/WD-css3-syntax-20030813</a> ",
+ "CSS3TBL" : "Bert Bos; David Hyatt. <cite>CSS3 Tables Module.</cite> (forthcoming). W3C Working Draft. (Work in progress.)",
+ "CSS3TEXT" : "Paul Nelson; Elika J. Etemad. <a href=\"http://www.w3.org/TR/2007/WD-css3-text-20070306\"><cite>CSS Text Level 3.</cite></a> 6 March 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-css3-text-20070306\">http://www.w3.org/TR/2007/WD-css3-text-20070306</a> ",
+ "CSS3TEXTLAYOUT" : "Elika J. Etemad; Paul Nelson. <cite>CSS3 Text Layout Module.</cite> (forthcoming). W3C Working Draft. (Work in progress.)",
+ "CSS3UI" : "Tantek Çelik. <a href=\"http://www.w3.org/TR/2004/CR-css3-ui-20040511\"><cite>CSS3 Basic User Interface Module.</cite></a> 11 May 2004. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2004/CR-css3-ui-20040511\">http://www.w3.org/TR/2004/CR-css3-ui-20040511</a> ",
+ "CSS3VAL" : "Chris Lilley; Håkon Wium Lie. <a href=\"http://www.w3.org/TR/2006/WD-css3-values-20060919\"><cite>CSS3 Values and Units.</cite></a> 19 September 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-css3-values-20060919\">http://www.w3.org/TR/2006/WD-css3-values-20060919</a> ",
+ "CSS3WRITINGMODES" : "Elika J. Etemad; Koji Ishii; Shinyu Murakami. <a href=\"http://dev.w3.org/csswg/css3-writing-modes\"><cite>CSS Writing Modes Module Level 3.</cite></a> 17 October 2010. W3C Editor's Draft. (Work in progress.) URL: <a href=\"http://dev.w3.org/csswg/css3-writing-modes\">http://dev.w3.org/csswg/css3-writing-modes</a> ",
+ "CSSBEIJING" : "Elika J. Etemad. <a href=\"http://www.w3.org/TR/2008/WD-css-beijing-20080516\"><cite>Cascading Style Sheets (CSS) Snapshot 2007.</cite></a> 16 May 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-css-beijing-20080516\">http://www.w3.org/TR/2008/WD-css-beijing-20080516</a> ",
+ "CSSOM-VIEW" : "Anne van Kesteren. <a href=\"http://www.w3.org/TR/2008/WD-cssom-view-20080222\"><cite>CSSOM View Module.</cite></a> 22 February 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-cssom-view-20080222\">http://www.w3.org/TR/2008/WD-cssom-view-20080222</a> ",
+ "CSSSTYLEATTR" : "Marc Attinasi; Bert Bos; Tantek Çelik. <a href=\"http://www.w3.org/TR/2002/WD-css-style-attr-20020515\"><cite>Syntax of CSS rules in HTML's "style" attribute.</cite></a> 15 May 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-css-style-attr-20020515\">http://www.w3.org/TR/2002/WD-css-style-attr-20020515</a> ",
+ "CT-GUIDELINES" : "Jo Rabin. <a href=\"http://www.w3.org/TR/2008/WD-ct-guidelines-20080801\"><cite>Content Transformation Guidelines 1.0.</cite></a> 1 August 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-ct-guidelines-20080801\">http://www.w3.org/TR/2008/WD-ct-guidelines-20080801</a> ",
+ "CT-LANDSCAPE" : "Jo Rabin; Andrew Swainston. <a href=\"http://www.w3.org/TR/2007/WD-ct-landscape-20071025\"><cite>Content Transformation Landscape 1.0.</cite></a> 25 October 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-ct-landscape-20071025\">http://www.w3.org/TR/2007/WD-ct-landscape-20071025</a> ",
+ "CURIE" : "Shane McCarron; et al. <a href=\"http://www.w3.org/TR/2012/PR-rdfa-core-20120508/\"><cite>RDFa Core 1.1 - Section 6.</cite></a> 8 May 2012. W3C proposed Recommendation. URL: <a href=\"http://www.w3.org/TR/2012/PR-rdfa-core-20120508/\">http://www.w3.org/TR/2012/PR-rdfa-core-20120508/</a> ",
+ "CVE-2009-0217" : "<a href=\"http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0217\"><cite>Common Vulnerabilities and Exposures List, CVE-2009-0217</cite></a> URL: <a href=\"http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0217\"> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0217</a>",
+ "CX" : "Philippe Le Hégaret; et al. <a href=\"http://www.w3.org/TR/2001/NOTE-CX-20011211\"><cite>Component Extension (CX) API requirements Version 1.0.</cite></a> 11 December 2001. W3C Note. URL: <a href=\"http://www.w3.org/TR/2001/NOTE-CX-20011211\">http://www.w3.org/TR/2001/NOTE-CX-20011211</a> ",
+ "DAHUT": "Robin Berjon; et al. <cite>The Dahut Specification Example From the Higher Circle.</cite> 15 March 1977. Lazy Daft. (Work for progress.) URL: <a href='http://berjon.com/'>http://berjon.com/</a>",
+ "DAP-ACCESS-REQS" : "L. Arribas, P. Byers, M. Hanclik, F Hirsch, D. Rogers. <a href=\"http://dev.w3.org/2009/dap/policy-reqs/\"><cite>Device API Access Control Requirements</cite></a> 17 June 2010. (Work in progress.) URL: <a href=\"http://dev.w3.org/2009/dap/policy-reqs/\">http://dev.w3.org/2009/dap/policy-reqs/</a> ",
+ "DAP-POLICY-FRAMEWORK" : "L. Arribas, P. Byers, M. Hanclik, F Hirsch, D. Rogers. <a href=\"http://dev.w3.org/2009/dap/policy/Framework.html\"><cite>Device API Policy Framework.</cite></a> 17 June 2010. (Work in progress.) URL: <a href=\"http://dev.w3.org/2009/dap/policy/Framework.html\">http://dev.w3.org/2009/dap/policy/Framework.html</a> ",
+ "DAP-PRIVACY-POSITION" : "Frederick Hirsch, Robin Berjon. <a href=\"http://www.w3.org/2010/policy-ws/papers/14-Hirsch-Berjon-DAP.html\"><cite>Position Paper: Privacy and Policy in the DAP WG - A DAP Perspective</cite></a>. 2 September 2010. URL: <a href=\"http://www.w3.org/2010/policy-ws/papers/14-Hirsch-Berjon-DAP.html\">http://www.w3.org/2010/policy-ws/papers/14-Hirsch-Berjon-DAP.html</a> (<a href=\"http://www.w3.org/2010/policy-ws/\">W3C Workshop on Privacy and Data Usage Control</a>.)",
+ "DAP-PRIVACY-REQS" : "Alissa Cooper, Frederick Hirsch, John Morris. <a href=\"http://www.w3.org/TR/2010/NOTE-dap-privacy-reqs-20100629/\"><cite>Device API Privacy Requirements</cite></a> 29 June 2010. W3C Note URL: <a href=\"http://www.w3.org/TR/2010/NOTE-dap-privacy-reqs-20100629/\">http://www.w3.org/TR/2010/NOTE-dap-privacy-reqs-20100629/</a> ",
+ "WEBAPP-PRIVACY-BESTPRACTICES" : "Frederick Hirsch. <a href=\"http://www.w3.org/TR/2012/NOTE-app-privacy-bp-20120703/\"><cite>Web Application Privacy Best Practices</cite></a>. 3 July 2012. W3C Working Group Note. URL: <a href=\"http://www.w3.org/TR/2012/NOTE-app-privacy-bp-20120703/\">http://www.w3.org/TR/2012/NOTE-app-privacy-bp-20120703/</a> ",
+ "DAP-REQS" : "Robin Berjon; et al. <a href=\"http://www.w3.org/TR/2009/NOTE-dap-api-reqs-20091015/\"><cite>Device API Requirementsml</cite></a> 15 October 2009. Working Group Note. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/NOTE-dap-api-reqs-20091015/\">http://www.w3.org/TR/2009/NOTE-dap-api-reqs-20091015/</a> ",
+ "DAP-XACML-POLICY-PROFILE" : "L. Arribas, P. Byers, M. Hanclik, F Hirsch, D. Rogers. <a href=\"http://dev.w3.org/2009/dap/policy/Profile.html\"><cite>XACML Policy Profile for Device APIs.</cite></a> 17 June 2010. (Work in progress.) URL: <a href=\"http://dev.w3.org/2009/dap/policy/Profile.html\">http://dev.w3.org/2009/dap/policy/Profile.html</a> ",
+ "Davis" : "<a href=\"http://www.usenix.org/publications/library/proceedings/usenix01/davis.html\"><cite>Defective Sign & Encrypt in S/MIME, PKCS#7, MOSS, PEM, PGP, and XML.</cite></a> D. Davis. USENIX Annual Technical Conference. 2001. URL: <a href=\"http://www.usenix.org/publications/library/proceedings/usenix01/davis.html\">http://www.usenix.org/publications/library/proceedings/usenix01/davis.html</a>",
+ "DC11" : "Dublin Core metadata initiative. <a href=\"http://dublincore.org/documents/dcmi-terms/\"><cite>Dublin Core metadata element set, version 1.1.</cite></a> July 1999. Dublin Core recommendation. URL: <a href=\"http://dublincore.org/documents/dcmi-terms/\">http://dublincore.org/documents/dcmi-terms/</a> ",
+ "DCONTOLOGY" : "José Manuel Cantera Fonseca; Rhys Lewis. <a href=\"http://www.w3.org/TR/2009/WD-dcontology-20090616\"><cite>Delivery Context Ontology.</cite></a> 16 June 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-dcontology-20090616/\">http://www.w3.org/TR/2009/WD-dcontology-20090616/</a> ",
+ "DD-ECOSYSTEM" : "Rotan Hanrahan. <a href=\"http://www.w3.org/TR/2007/NOTE-dd-ecosystem-20071031\"><cite>Device Description Ecosystem 1.0.</cite></a> 31 October 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-dd-ecosystem-20071031\">http://www.w3.org/TR/2007/NOTE-dd-ecosystem-20071031</a> ",
+ "DD-LANDSCAPE" : "Matt Womer; Eman Nkeze; James Pearce. <a href=\"http://www.w3.org/TR/2007/NOTE-dd-landscape-20071031\"><cite>Device Description Landscape 1.0.</cite></a> 31 October 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-dd-landscape-20071031\">http://www.w3.org/TR/2007/NOTE-dd-landscape-20071031</a> ",
+ "DD-STRUCTURES" : "José Manuel Cantera Fonseca. <a href=\"http://www.w3.org/TR/2008/WD-dd-structures-20081205\"><cite>Device Description Structures.</cite></a> 5 December 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-dd-structures-20081205\">http://www.w3.org/TR/2008/WD-dd-structures-20081205</a> ",
+ "DDR-CORE-VOCABULARY" : "Andrea Trasatti; Jo Rabin; Rotan Hanrahan. <a href=\"http://www.w3.org/TR/2008/NOTE-ddr-core-vocabulary-20080414\"><cite>Device Description Repository Core Vocabulary.</cite></a> 14 April 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-ddr-core-vocabulary-20080414\">http://www.w3.org/TR/2008/NOTE-ddr-core-vocabulary-20080414</a> ",
+ "DDR-REQUIREMENTS" : "Kevin Smith; David Sanders. <a href=\"http://www.w3.org/TR/2007/NOTE-DDR-requirements-20071217\"><cite>Device Description Repository Requirements 1.0.</cite></a> 17 December 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-DDR-requirements-20071217\">http://www.w3.org/TR/2007/NOTE-DDR-requirements-20071217</a> ",
+ "DDR-SIMPLE-API" : "José Manuel Cantera Fonseca; et al. <a href=\"http://www.w3.org/TR/2008/REC-DDR-Simple-API-20081205\"><cite>Device Description Repository Simple API.</cite></a> 5 December 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-DDR-Simple-API-20081205\">http://www.w3.org/TR/2008/REC-DDR-Simple-API-20081205</a> ",
+ "DES" : "<a href=\"http://csrc.nist.gov/publications/fips/fips46-3/fips46-3.pdf\"><cite>NIST FIPS 46-3: Data Encryption Standard (DES)</cite></a> . October 1999. URL: <a href=\"http://csrc.nist.gov/publications/fips/fips46-3/fips46-3.pdf\">http://csrc.nist.gov/publications/fips/fips46-3/fips46-3.pdf</a>",
+ "DFAUI" : "Arthur Barstow. <a href=\"http://www.w3.org/TR/2007/NOTE-dfaui-20070912\"><cite>Declarative Formats for Applications and User Interfaces.</cite></a> 12 September 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-dfaui-20070912\">http://www.w3.org/TR/2007/NOTE-dfaui-20070912</a> ",
+ "DI-ATDI" : "Roland Merrick; Rotan Hanrahan. <a href=\"http://www.w3.org/TR/2004/NOTE-di-atdi-20040218\"><cite>Authoring Techniques for Device Independence.</cite></a> 18 February 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-di-atdi-20040218\">http://www.w3.org/TR/2004/NOTE-di-atdi-20040218</a> ",
+ "DI-DCO" : "Sailesh Sathish; Rhys Lewis; Roger Gimson. <a href=\"http://www.w3.org/TR/2006/NOTE-di-dco-20060320\"><cite>Delivery Context Overview for Device Independence.</cite></a> 20 March 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-di-dco-20060320\">http://www.w3.org/TR/2006/NOTE-di-dco-20060320</a> ",
+ "DI-GLOSS" : "Rhys Lewis. <a href=\"http://www.w3.org/TR/2005/WD-di-gloss-20050118\"><cite>Glossary of Terms for Device Independence.</cite></a> 18 January 2005. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2005/WD-di-gloss-20050118\">http://www.w3.org/TR/2005/WD-di-gloss-20050118</a> ",
+ "DI-PRINC" : "Roger Gimson. <a href=\"http://www.w3.org/TR/2003/NOTE-di-princ-20030901\"><cite>Device Independence Principles.</cite></a> 1 September 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-di-princ-20030901\">http://www.w3.org/TR/2003/NOTE-di-princ-20030901</a> ",
+ "DIAL" : "Kevin Smith. <a href=\"http://www.w3.org/TR/2007/WD-dial-20070727\"><cite>Device Independent Authoring Language (DIAL).</cite></a> 27 July 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-dial-20070727\">http://www.w3.org/TR/2007/WD-dial-20070727</a> ",
+ "DIAL-PRIMER" : "Kevin Smith; Kevin Smith. <a href=\"http://www.w3.org/TR/2007/WD-dial-primer-20071101\"><cite>DIAL Part 0: Primer.</cite></a> 1 November 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-dial-primer-20071101\">http://www.w3.org/TR/2007/WD-dial-primer-20071101</a> ",
+ "DIG2000" : "Digital Imaging Group. <a href=\"http://www.digitalimaging.org/pdf/wg1n1017.pdf\"><cite>DIG2000 file format proposal.</cite></a> Oct 1998. Report (draft) ISO/IEC JTC1/SG29/WG1 N1017. URL: <a href=\"http://www.digitalimaging.org/pdf/wg1n1017.pdf\">http://www.digitalimaging.org/pdf/wg1n1017.pdf</a> ",
+ "DISCO-PROP" : "Rich Tibbett, Clarke Stevens. <a href=\"http://people.opera.com/richt/release/specs/discovery/Overview.html\"><cite>Networked Service Discovery and Messaging</cite></a>. 22 September 2011. Draft proposal (no official standing). URL: <a href=\"http://people.opera.com/richt/release/specs/discovery/Overview.html\">http://people.opera.com/richt/release/specs/discovery/Overview.html</a>",
+ "DOM-BINDINGS" : "Cameron McCormack. <a href=\"http://www.w3.org/TR/2008/WD-WebIDL-20081219\"><cite>Web IDL.</cite></a> 19 December 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-WebIDL-20081219\">http://www.w3.org/TR/2008/WD-WebIDL-20081219</a> ",
+ "DOM4" : "Anne van Kesteren; Aryeh Gregor; Ms2ger. <a href=\"http://www.w3.org/TR/2012/WD-dom-20120105/\"><cite>DOM4.</cite></a> 5 January 2012. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/WD-dom-20120105/\">http://www.w3.org/TR/2012/WD-dom-20120105/</a> ",
+ "DOM-LEVEL-1" : "Vidur Apparao; et al. <a href=\"http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/\"><cite>Document Object Model (DOM) Level 1.</cite></a> 1 October 1998. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/\">http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/</a> ",
+ "DOM-LEVEL-1-2e" : "Jonathan Robie; et al. <a href=\"http://www.w3.org/TR/2000/WD-DOM-Level-1-20000929\"><cite>Document Object Model (DOM) Level 1 Specification (Second Edition).</cite></a> 29 September 2000. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2000/WD-DOM-Level-1-20000929\">http://www.w3.org/TR/2000/WD-DOM-Level-1-20000929</a> ",
+ "DOM-LEVEL-2-CORE" : "Arnaud Le Hors; et al. <a href=\"http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/\"><cite>Document Object Model (DOM) Level 2 Core Specification.</cite></a> 13 November 2000. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/\">http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/</a> ",
+ "DOM-LEVEL-2-EVENTS" : "Tom Pixley. <a href=\"http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113\"><cite>Document Object Model (DOM) Level 2 Events Specification.</cite></a> 13 November 2000. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113\">http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113</a> ",
+ "DOM-LEVEL-2-HTML" : "Arnaud Le Hors; Johnny Stenback; Philippe Le Hégaret. <a href=\"http://www.w3.org/TR/2003/REC-DOM-Level-2-HTML-20030109\"><cite>Document Object Model (DOM) Level 2 HTML Specification.</cite></a> 9 January 2003. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2003/REC-DOM-Level-2-HTML-20030109\">http://www.w3.org/TR/2003/REC-DOM-Level-2-HTML-20030109</a> ",
+ "DOM-LEVEL-2-STYLE" : "Vidur Apparao; Philippe Le Hégaret; Chris Wilson. <a href=\"http://www.w3.org/TR/2000/REC-DOM-Level-2-Style-20001113\"><cite>Document Object Model (DOM) Level 2 Style Specification.</cite></a> 13 November 2000. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2000/REC-DOM-Level-2-Style-20001113\">http://www.w3.org/TR/2000/REC-DOM-Level-2-Style-20001113</a> ",
+ "DOM-LEVEL-2-TRAVERSAL-RANGE" : "Vidur Apparao; et al. <a href=\"http://www.w3.org/TR/2000/REC-DOM-Level-2-Traversal-Range-20001113\"><cite>Document Object Model (DOM) Level 2 Traversal and Range Specification.</cite></a> 13 November 2000. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2000/REC-DOM-Level-2-Traversal-Range-20001113\">http://www.w3.org/TR/2000/REC-DOM-Level-2-Traversal-Range-20001113</a> ",
+ "DOM-LEVEL-2-VIEWS" : "Laurence Cable; Arnaud Le Hors. <a href=\"http://www.w3.org/TR/2000/REC-DOM-Level-2-Views-20001113\"><cite>Document Object Model (DOM) Level 2 Views Specification.</cite></a> 13 November 2000. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2000/REC-DOM-Level-2-Views-20001113\">http://www.w3.org/TR/2000/REC-DOM-Level-2-Views-20001113</a> ",
+ "DOM-LEVEL-3-AS" : "Ben Chang; et al. <a href=\"http://www.w3.org/TR/2002/NOTE-DOM-Level-3-AS-20020725\"><cite>Document Object Model (DOM) Level 3 Abstract Schemas Specification.</cite></a> 25 July 2002. W3C Note. URL: <a href=\"http://www.w3.org/TR/2002/NOTE-DOM-Level-3-AS-20020725\">http://www.w3.org/TR/2002/NOTE-DOM-Level-3-AS-20020725</a> ",
+ "DOM-LEVEL-3-CORE" : "Gavin Nicol; et al. <a href=\"http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407\"><cite>Document Object Model (DOM) Level 3 Core Specification.</cite></a> 7 April 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407\">http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407</a> ",
+ "DOM-LEVEL-3-EVENTS" : "Björn Höhrmann; Tom Pixley; Philippe Le Hégaret. <a href=\"http://www.w3.org/TR/2011/WD-DOM-Level-3-Events-20110531/\"><cite>Document Object Model (DOM) Level 3 Events Specification.</cite></a> 31 May 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-DOM-Level-3-Events-20110531/\">http://www.w3.org/TR/2011/WD-DOM-Level-3-Events-20110531/</a> ",
+ "DOM-LEVEL-3-LS" : "Johnny Stenback; Andy Heninger. <a href=\"http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407\"><cite>Document Object Model (DOM) Level 3 Load and Save Specification.</cite></a> 7 April 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407\">http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407</a> ",
+ "DOM-LEVEL-3-VAL" : "Ben Chang; Rezaur Rahman; Joe Kesselman. <a href=\"http://www.w3.org/TR/2004/REC-DOM-Level-3-Val-20040127\"><cite>Document Object Model (DOM) Level 3 Validation Specification.</cite></a> 27 January 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-DOM-Level-3-Val-20040127\">http://www.w3.org/TR/2004/REC-DOM-Level-3-Val-20040127</a> ",
+ "DOM-LEVEL-3-VIEWS" : "Ray Whitmer. <a href=\"http://www.w3.org/TR/2004/NOTE-DOM-Level-3-Views-20040226\"><cite>Document Object Model (DOM) Level 3 Views and Formatting Specification.</cite></a> 26 February 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-DOM-Level-3-Views-20040226\">http://www.w3.org/TR/2004/NOTE-DOM-Level-3-Views-20040226</a> ",
+ "DOM-LEVEL-3-XPATH" : "Ray Whitmer. <a href=\"http://www.w3.org/TR/2004/NOTE-DOM-Level-3-XPath-20040226\"><cite>Document Object Model (DOM) Level 3 XPath Specification.</cite></a> 26 February 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-DOM-Level-3-XPath-20040226\">http://www.w3.org/TR/2004/NOTE-DOM-Level-3-XPath-20040226</a> ",
+ "DOM-REQUIREMENTS" : "Arnaud Le Hors; et al. <a href=\"http://www.w3.org/TR/2004/NOTE-DOM-Requirements-20040226\"><cite>Document Object Model (DOM) Requirements.</cite></a> 26 February 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-DOM-Requirements-20040226\">http://www.w3.org/TR/2004/NOTE-DOM-Requirements-20040226</a> ",
+ "DPF" : "Max Froumentin; et al. <a href=\"http://www.w3.org/TR/2007/CR-DPF-20071221\"><cite>Delivery Context: Client Interfaces (DCCI) 1.0.</cite></a> 21 December 2007. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/CR-DPF-20071221\">http://www.w3.org/TR/2007/CR-DPF-20071221</a> ",
+ "DSIG-LABEL" : "Philip DesAutels; et al. <a href=\"http://www.w3.org/TR/1998/REC-DSig-label-19980527\"><cite>PICS Signed Labels (DSig) 1.0 Specification.</cite></a> 27 May 1998. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/1998/REC-DSig-label-19980527\">http://www.w3.org/TR/1998/REC-DSig-label-19980527</a> ",
+ "DSIG-USAGE" : "Thomas Roessler. <a href=\"http://www.w3.org/TR/2006/NOTE-DSig-usage-20061220\"><cite>Using XML Digital Signatures in the 2006 XML Environment.</cite></a> 20 December 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-DSig-usage-20061220\">http://www.w3.org/TR/2006/NOTE-DSig-usage-20061220</a> ",
+ "DSS" : "<a href=\"http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf\"><cite>FIPS PUB 186-3: Digital Signature Standard (DSS)</cite></a>. June 2009. U.S. Department of Commerce/National Institute of Standards and Technology. URL: <a href=\"http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf\">http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf</a>",
+ "EARL10-REQUIREMENTS" : "Shadi Abou-Zahra; Jim Ley. <a href=\"http://www.w3.org/TR/2005/WD-EARL10-Requirements-20050711\"><cite>Requirements for the Evaluation and Report Language (EARL) 1.0.</cite></a> 11 July 2005. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2005/WD-EARL10-Requirements-20050711\">http://www.w3.org/TR/2005/WD-EARL10-Requirements-20050711</a> ",
+ "EARL10-SCHEMA" : "Shadi Abou-Zahra. <a href=\"http://www.w3.org/TR/2007/WD-EARL10-Schema-20070323\"><cite>Evaluation and Report Language (EARL) 1.0 Schema.</cite></a> 23 March 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-EARL10-Schema-20070323\">http://www.w3.org/TR/2007/WD-EARL10-Schema-20070323</a> ",
+ "EBXML-MSG" : "Ian Jones; Brian Gibb; David Fischer. <a href=\"http://www.oasis-open.org/committees/download.php/272/ebMS_v2_0.pdf\"><cite> OASIS ebXML Message Service Specification</cite></a> 1 April 2002. URL: <a href=\"http://www.oasis-open.org/committees/download.php/272/ebMS_v2_0.pdf\">http://www.oasis-open.org/committees/download.php/272/ebMS_v2_0.pdf</a>",
+ "ECC-ALGS" : "D. McGrew, K. Igoe, M. Salter. <a href=\"http://www.rfc-editor.org/rfc/rfc6090.txt\"><cite>RFC 6090: Fundamental Elliptic Curve Cryptography Algorithms.</cite></a> February 2011. IETF Informational RFC. URL: <a href=\"http://www.rfc-editor.org/rfc/rfc6090.txt\">http://www.rfc-editor.org/rfc/rfc6090.txt</a>",
+ "EC-RELATED-ACTIVITIES" : "Thierry Michel. <a href=\"http://www.w3.org/TR/2000/NOTE-EC-related-activities-20000107\"><cite>W3C and Electronic Commerce.</cite></a> 7 January 2000. W3C Note. URL: <a href=\"http://www.w3.org/TR/2000/NOTE-EC-related-activities-20000107\">http://www.w3.org/TR/2000/NOTE-EC-related-activities-20000107</a> ",
+ "ECMA-262" : "<a href=\"http://www.ecma-international.org/publications/standards/Ecma-262.htm\"><cite>ECMAScript Language Specification.</cite></a> June 2011. URL: <a href=\"http://www.ecma-international.org/publications/standards/Ecma-262.htm\">http://www.ecma-international.org/publications/standards/Ecma-262.htm</a> ",
+ "EGOV-IMPROVING" : "Kevin Novak; José M. Alonso. <a href=\"http://www.w3.org/TR/2009/WD-egov-improving-20090310\"><cite>Improving Access to Government through Better Use of the Web.</cite></a> 10 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-egov-improving-20090310\">http://www.w3.org/TR/2009/WD-egov-improving-20090310</a> ",
+ "ELEMENTTRAVERSAL" : "Robin Berjon; Doug Schepers. <a href=\"http://www.w3.org/TR/2008/REC-ElementTraversal-20081222\"><cite>Element Traversal Specification.</cite></a> 22 December 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-ElementTraversal-20081222\">http://www.w3.org/TR/2008/REC-ElementTraversal-20081222</a> ",
+ "ELEMTYPO" : "Robert Bringhurst. <cite>The Elements of Typographic Style, Version 3.1.</cite> Hartley & Marks. 2005. ISBN 0-88179-206-3.",
+ "EMAIL": "P. Resnick. <a href='http://tools.ietf.org/html/rfc5322'><cite>RFC 5322: Internet Message Format</cite></a>. October 2008. IETF draft standard. URL: <a href='http://tools.ietf.org/html/rfc5322'>http://tools.ietf.org/html/rfc5322</a> ",
+ "EMMA" : "Michael Johnston. <a href=\"http://www.w3.org/TR/2009/REC-emma-20090210\"><cite>EMMA: Extensible MultiModal Annotation markup language.</cite></a> 10 February 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-emma-20090210\">http://www.w3.org/TR/2009/REC-emma-20090210</a> ",
+ "EMMAREQS" : "Stéphane H. Maes; Stephen Potter. <a href=\"http://www.w3.org/TR/2003/NOTE-EMMAreqs-20030113\"><cite>Requirements for EMMA.</cite></a> 13 January 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-EMMAreqs-20030113\">http://www.w3.org/TR/2003/NOTE-EMMAreqs-20030113</a> ",
+ "ERICSSON-WDC" : "<a href=\"https://labs.ericsson.com/apis/web-device-connectivity/\"><cite>Web Device Connectivity</cite></a>. 18 October 2010. Ericsson Labs. URL: <a href=\"https://labs.ericsson.com/apis/web-device-connectivity/\"></a>",
+ "ESDH" : "E. Rescorla. <a href=\"http://www.ietf.org/rfc/rfc2631.txt\"><cite> Diffie-Hellman Key Agreement Method.</cite></a>. IETF RFC 2631 Standards Track, 1999. URL: <a href=\"http://www.ietf.org/rfc/rfc2631.txt\">http://www.ietf.org/rfc/rfc2631.txt</a>",
+ "EXI" : "Takuki Kamiya; John Schneider. <a href=\"http://www.w3.org/TR/2009/CR-exi-20091208/\"><cite>Efficient XML Interchange (EXI) Format 1.0.</cite></a> 8 December 2009. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/CR-exi-20091208/\">http://www.w3.org/TR/2009/CR-exi-20091208/</a> ",
+ "EXI-BEST-PRACTICES" : "Mike Cokus; Daniel Vogelheim. <a href=\"http://www.w3.org/TR/2007/WD-exi-best-practices-20071219\"><cite>Efficient XML Interchange (EXI) Best Practices.</cite></a> 19 December 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-exi-best-practices-20071219\">http://www.w3.org/TR/2007/WD-exi-best-practices-20071219</a> ",
+ "EXI-EVALUATION" : "Carine Bournez. <a href=\"http://www.w3.org/TR/2008/WD-exi-evaluation-20080728\"><cite>Efficient XML Interchange Evaluation.</cite></a> 28 July 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-exi-evaluation-20080728\">http://www.w3.org/TR/2008/WD-exi-evaluation-20080728</a> ",
+ "EXI-IMPACTS" : "Jaakko Kangasharju. <a href=\"http://www.w3.org/TR/2008/WD-exi-impacts-20080903\"><cite>Efficient XML Interchange (EXI) Impacts.</cite></a> 3 September 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-exi-impacts-20080903\">http://www.w3.org/TR/2008/WD-exi-impacts-20080903</a> ",
+ "EXI-MEASUREMENTS" : "Jaakko Kangasharju; et al. <a href=\"http://www.w3.org/TR/2007/WD-exi-measurements-20070725\"><cite>Efficient XML Interchange Measurements Note.</cite></a> 25 July 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-exi-measurements-20070725\">http://www.w3.org/TR/2007/WD-exi-measurements-20070725</a> ",
+ "EXI-PRIMER" : "Daniel Peintner; Santiago Pericas-Geertsen. <a href=\"http://www.w3.org/TR/2007/WD-exi-primer-20071219\"><cite>Efficient XML Interchange (EXI) Primer.</cite></a> 19 December 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-exi-primer-20071219\">http://www.w3.org/TR/2007/WD-exi-primer-20071219</a> ",
+ "FILE-UPLOAD" : "Robin Berjon. <a href=\"http://www.w3.org/TR/2006/WD-file-upload-20061018\"><cite>File Upload.</cite></a> 18 October 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-file-upload-20061018\">http://www.w3.org/TR/2006/WD-file-upload-20061018</a> ",
+ "FILE-API" : "Arun Ranganathan; Jonas Sicking. <a href=\"http://www.w3.org/TR/2011/WD-FileAPI-20111020/\"><cite>File API.</cite></a> 20 October 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-FileAPI-20111020/\">http://www.w3.org/TR/2011/WD-FileAPI-20111020/</a> ",
+ "FILE-WRITER" : "Eric Uhrhane. <a href=\"http://www.w3.org/TR/2011/WD-file-writer-api-20110419/\"><cite>File Writer API.</cite></a> 19 April 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-file-writer-api-20110419/\">http://www.w3.org/TR/2011/WD-file-writer-api-20110419/</a> ",
+ "FIN-PRIV-NOTICE": "Kleimann Communications Group, Inc. <a href='http://www.ftc.gov/privacy/privacyinitiatives/ftcfinalreport060228.pdf'><cite>Evolution of a Prototype Financial Privacy Notice </cite></a> 28 February 2006. URL: http://www.ftc.gov/privacy/privacyinitiatives/ftcfinalreport060228.pdf ",
+ "FIPS-180-3" : "<a href=\"http://csrc.nist.gov/publications/fips/fips180-3/fips180-3_final.pdf\"><cite>FIPS PUB 180-3 Secure Hash Standard</cite></a>. U.S. Department of Commerce/National Institute of Standards and Technology. URL: <a href=\"http://csrc.nist.gov/publications/fips/fips180-3/fips180-3_final.pdf\">http://csrc.nist.gov/publications/fips/fips180-3/fips180-3_final.pdf</a>",
+ "FIPS-186-3" : "<a href=\"http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf\"><cite>FIPS PUB 186-3: Digital Signature Standard (DSS)</cite></a>. June 2009. U.S. Department of Commerce/National Institute of Standards and Technology. URL: <a href=\"http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf\">http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf</a>",
+ "FIR" : "Joe Clark. <a href=\"http://www.alistapart.com/articles/fir\">“Facts and Opinion About Fahrner Image Replacement”</a> in: <cite>A List Apart.</cite> Issue No. 160. 20 October 2003. URL: <a href=\"http://www.alistapart.com/articles/fir\">http://www.alistapart.com/articles/fir</a> ",
+ "FLEX" : "<cite>Flex: The Lexical Scanner Generator.</cite> Version 2.3.7, ISBN 1882114213",
+ "FLEXBOX" : "L. David Baron. <a href=\"http://www.w3.org/TR/css3-flexbox/\"><cite>Flexible Box Layout Module.</cite></a> 23 July 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/css3-flexbox/\">http://www.w3.org/TR/css3-flexbox/</a> ",
+ "FOAF" : "Dan Brickley, Libby Miller. <a href=\"http://xmlns.com/foaf/spec/\"><cite>FOAF Vocabulary Specification 0.98.</cite></a> 9 August 2010. URL: <a href=\"http://xmlns.com/foaf/spec/\">http://xmlns.com/foaf/spec/</a>",
+ "FULLSCREEN" : "Anne van Kesteren. <a href=\"http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html\"><cite>The Fullscreen API.</cite></a> 4 January 2012. W3C Editor's Draft. (Work in progress.) URL: <a href=\"http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html\">http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html</a> ",
+ "GEOLOCATION-API" : "Andrei Popescu. <a href=\"http://www.w3.org/TR/2008/WD-geolocation-API-20081222/\"><cite>Geolocation API Specification.</cite></a> 22 December 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-geolocation-API-20081222/\">http://www.w3.org/TR/2008/WD-geolocation-API-20081222/</a> ",
+ "GEOPRIV-ARCH" : "Barnes, R. Lepinski, M. Cooper, A. Morris, J. Tschofenig, H. Schulzrinne, H. <a href = 'http://tools.ietf.org/html/draft-ietf-geopriv-arch-01'><cite>An Architecture for Location and Location Privacy in Internet Applications</cite></a> 29 October 2009. URL: <a href=\"http://tools.ietf.org/html/draft-ietf-geopriv-arch-01\">http://tools.ietf.org/html/draft-ietf-geopriv-arch-01</a>",
+ "GEOLOCATION-PRIVACY" : "Marcos Cáceres <a href=\"http://www.w3.org/2010/api-privacy-ws/papers/privacy-ws-21.pdf\"><cite>Privacy of Geolocation Implementations</cite></a>, \"W3C Workshop on Privacy for Advanced Web APIs\" paper, 12/13 July 2010. URL: <a href=\"http://www.w3.org/2010/api-privacy-ws/papers/privacy-ws-21.pdf\">http://www.w3.org/2010/api-privacy-ws/papers/privacy-ws-21.pdf</a>",
+ "GETUSERMEDIA": "D. Burnett, A. Narayanan. <a href=\"http://dev.w3.org/2011/webrtc/editor/getusermedia.html\"><cite>getusermedia: Getting access to local devices that can generate multimedia streams</cite></a> 22 December 2011. W3C Editors draft (Work in progress.) URL: <a href=\"http://dev.w3.org/2011/webrtc/editor/getusermedia.html\">http://dev.w3.org/2011/webrtc/editor/getusermedia.html</a> ",
+ "GRDDL" : "Dan Connolly. <a href=\"http://www.w3.org/TR/2007/REC-grddl-20070911\"><cite>Gleaning Resource Descriptions from Dialects of Languages (GRDDL).</cite></a> 11 September 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-grddl-20070911\">http://www.w3.org/TR/2007/REC-grddl-20070911</a> ",
+ "GRDDL-PRIMER" : "Harry Halpin; Ian Davis. <a href=\"http://www.w3.org/TR/2007/NOTE-grddl-primer-20070628\"><cite>GRDDL Primer.</cite></a> 28 June 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-grddl-primer-20070628\">http://www.w3.org/TR/2007/NOTE-grddl-primer-20070628</a> ",
+ "GRDDL-SCENARIOS" : "Fabien Gandon. <a href=\"http://www.w3.org/TR/2007/NOTE-grddl-scenarios-20070406\"><cite>GRDDL Use Cases: Scenarios of extracting RDF data from XML documents.</cite></a> 6 April 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-grddl-scenarios-20070406\">http://www.w3.org/TR/2007/NOTE-grddl-scenarios-20070406</a> ",
+ "GRDDL-TESTS" : "Chimezie Ogbuji. <a href=\"http://www.w3.org/TR/2007/REC-grddl-tests-20070911\"><cite>GRDDL Test Cases.</cite></a> 11 September 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-grddl-tests-20070911\">http://www.w3.org/TR/2007/REC-grddl-tests-20070911</a> ",
+ "HASH-IN-URI": "T.V. Raman; Ashok Malhotra. <a href=\"http://www.w3.org/2001/tag/2011/01/HashInURI-20110115\"><cite>Repurposing the Hash Sign for the New Web.</cite></a> 15 January 2011. Putative TAG Finding. URL: <a href=\"http://www.w3.org/2001/tag/2011/01/HashInURI-20110115\">http://www.w3.org/2001/tag/2011/01/HashInURI-20110115</a> ",
+ "HCLS-KB" : "Eric Prud'hommeaux; M. Scott Marshall. <a href=\"http://www.w3.org/TR/2008/NOTE-hcls-kb-20080604\"><cite>A Prototype Knowledge Base for the Life Sciences.</cite></a> 4 June 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-hcls-kb-20080604\">http://www.w3.org/TR/2008/NOTE-hcls-kb-20080604</a> ",
+ "HCLS-SENSELAB" : "Kei-Hoi Cheung; Matthias Samwald. <a href=\"http://www.w3.org/TR/2008/NOTE-hcls-senselab-20080604\"><cite>Experiences with the conversion of SenseLab databases to RDF/OWL.</cite></a> 4 June 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-hcls-senselab-20080604\">http://www.w3.org/TR/2008/NOTE-hcls-senselab-20080604</a> ",
+ "HLINK" : "Steven Pemberton; Masayasu Ishikawa. <a href=\"http://www.w3.org/TR/2002/WD-hlink-20020913\"><cite>HLink: Link recognition for the XHTML Family.</cite></a> 13 September 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-hlink-20020913\">http://www.w3.org/TR/2002/WD-hlink-20020913</a> ",
+ "HMAC" : "H. Krawczyk, M. Bellare, R. Canetti. <a href=\"http://www.ietf.org/rfc/rfc2104.txt\"><cite>HMAC: Keyed-Hashing for Message Authentication</cite></a>. February 1997. IETF RFC 2104. URL: <a href=\"http://www.ietf.org/rfc/rfc2104.txt\">http://www.ietf.org/rfc/rfc2104.txt</a>",
+ "HMAC-Security" : "C. Rechberger, V. Rijmen. <a href=\"http://www.jucs.org/jucs_14_3/new_results_on_nmac/jucs_14_3_0347_0376_rechberger.pdf\"><cite>New Results on NMAC/HMAC when Instantiated with Popular Hash Functions</cite></a>. 2 January 2008. Journal of Universal Computer Science, vol. 14, no. 3 (2008), 347-376. URL: <a href=\"http://www.jucs.org/jucs_14_3/new_results_on_nmac/jucs_14_3_0347_0376_rechberger.pdf\">http://www.jucs.org/jucs_14_3/new_results_on_nmac/jucs_14_3_0347_0376_rechberger.pdf</a>",
+ "HMRMC" : "<a href=\"http://www.hmrc.gov.uk/softwaredevelopers/index.htm\"><cite>HM Revenue and customs</cite></a> Her Majesty's Revenue and Customs. URL: <a href=\"http://www.hmrc.gov.uk/softwaredevelopers/index.htm\">http://www.hmrc.gov.uk/softwaredevelopers/index.htm</a> <br> Sample response message with XML signature: <a href=\"http://www.hmrc.gov.uk/ebu/responsemessages.pdf\">http://www.hmrc.gov.uk/ebu/responsemessages.pdf</a>",
+ "HSL" : "Steven Pemberton. <a href=\"http://www.cwi.nl/~steven/css/hsl.html\"><cite>HSL: light vs saturation.</cite></a> 19 November 1998. URL: <a href=\"http://www.cwi.nl/~steven/css/hsl.html\">http://www.cwi.nl/~steven/css/hsl.html</a> ",
+ "HTML-DESIGN-PRINCIPLES" : "Anne van Kesteren; Maciej Stachowiak. <a href=\"http://www.w3.org/TR/2007/WD-html-design-principles-20071126\"><cite>HTML Design Principles.</cite></a> 26 November 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-html-design-principles-20071126\">http://www.w3.org/TR/2007/WD-html-design-principles-20071126</a> ",
+ "HTML-LAN" : "M. T. Carrasco Benitez. <a href=\"http://www.w3.org/TR/1998/NOTE-html-lan-19980313\"><cite>Primary Language in HTML.</cite></a> 13 March 1998. W3C Note. URL: <a href=\"http://www.w3.org/TR/1998/NOTE-html-lan-19980313\">http://www.w3.org/TR/1998/NOTE-html-lan-19980313</a> ",
+ "HTML32" : "David Raggett. <a href=\"http://www.w3.org/TR/REC-html32-19970114\"><cite>HTML 3.2 Reference Specification.</cite></a> 14 January 1997. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/REC-html32-19970114\">http://www.w3.org/TR/REC-html32-19970114</a> ",
+ "HTML40" : "Ian Jacobs; David Raggett; Arnaud Le Hors. <a href=\"http://www.w3.org/TR/1998/REC-html40-19980424\"><cite>HTML 4.0 Specification.</cite></a> 24 April 1998. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/1998/REC-html40-19980424\">http://www.w3.org/TR/1998/REC-html40-19980424</a> ",
+ "HTML40-MOBILE" : "Shin'ichi Matsui; et al. <a href=\"http://www.w3.org/TR/1999/NOTE-html40-mobile-19990315\"><cite>HTML 4.0 Guidelines for Mobile Access.</cite></a> 15 March 1999. W3C Note. URL: <a href=\"http://www.w3.org/TR/1999/NOTE-html40-mobile-19990315\">http://www.w3.org/TR/1999/NOTE-html40-mobile-19990315</a> ",
+ "HTML401" : "David Raggett; Ian Jacobs; Arnaud Le Hors. <a href=\"http://www.w3.org/TR/1999/REC-html401-19991224\"><cite>HTML 4.01 Specification.</cite></a> 24 December 1999. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/1999/REC-html401-19991224\">http://www.w3.org/TR/1999/REC-html401-19991224</a> ",
+ "HTML5" : "Ian Hickson; David Hyatt. <a href=\"http://www.w3.org/TR/html5\"><cite>HTML5.</cite></a> 29 March 2012. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/html5\">http://www.w3.org/TR/html5</a> ",
+ "HTML5-DIFF" : "Anne van Kesteren. <a href=\"http://www.w3.org/TR/2009/WD-html5-diff-20090212\"><cite>HTML 5 differences from HTML 4.</cite></a> 12 February 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-html5-diff-20090212\">http://www.w3.org/TR/2009/WD-html5-diff-20090212</a> ",
+ "HTML5-PUBNOTES" : "Michael Smith. <a href=\"http://www.w3.org/TR/2008/NOTE-html5-pubnotes-20080610\"><cite>HTML 5 Publication Notes.</cite></a> 10 June 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-html5-pubnotes-20080610\">http://www.w3.org/TR/2008/NOTE-html5-pubnotes-20080610</a> ",
+ "HTML-DEVICE" : "Ian Hickson. <a href=\"http://dev.w3.org/html5/html-device/\"><cite>HTML Device</cite></a> 9th September 2010. W3C Editor's Draft. (Work in progress.) URL: <a href=\"http://dev.w3.org/html5/html-device/\">http://dev.w3.org/html5/html-device/</a>",
+ "HTMLICCPROF" : "Apple Computer with input from Microsoft Corporation. <a href=\"http://www.apple.com/colorsync/benefits/web/icc-profiles.html\"><cite>Proposal for HTML support of ICC profiles.</cite></a> URL: <a href=\"http://www.apple.com/colorsync/benefits/web/icc-profiles.html\">http://www.apple.com/colorsync/benefits/web/icc-profiles.html</a> ",
+ "HTTP-IN-RDF" : "Carlos A Velasco; Johannes Koch; Shadi Abou-Zahra. <a href=\"http://www.w3.org/TR/2008/WD-HTTP-in-RDF-20080908\"><cite>HTTP Vocabulary in RDF.</cite></a> 8 September 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-HTTP-in-RDF-20080908\">http://www.w3.org/TR/2008/WD-HTTP-in-RDF-20080908</a> ",
+ "HTTP-NG-TESTBED" : "Daniel Veillard. <a href=\"http://www.w3.org/TR/1998/NOTE-HTTP-NG-testbed-19980710\"><cite>Design of HTTP-ng Testbed.</cite></a> 10 July 1998. W3C Note. URL: <a href=\"http://www.w3.org/TR/1998/NOTE-HTTP-NG-testbed-19980710\">http://www.w3.org/TR/1998/NOTE-HTTP-NG-testbed-19980710</a> ",
+ "HTTP11" : "R. Fielding; et al. <a href=\"http://www.ietf.org/rfc/rfc2616.txt\"><cite>Hypertext Transfer Protocol - HTTP/1.1.</cite></a> June 1999. Internet RFC 2616. URL: <a href=\"http://www.ietf.org/rfc/rfc2616.txt\">http://www.ietf.org/rfc/rfc2616.txt</a> ",
+ "HTTP-TLS" : "E. Rescorla. <a href=\"http://www.ietf.org/rfc/rfc2818.txt\"><cite>HTTP Over TLS.</cite></a> May 2000. Internet RFC 2818. URL: <a href=\"http://www.ietf.org/rfc/rfc2818.txt\">http://www.ietf.org/rfc/rfc2818.txt</a> ",
+ "HunterZhan" : "Hunter, Jane; Zhan, Zhimin. <a href=\"http://archive.dstc.edu.au/RDU/staff/jane-hunter/PNG/paper.html\">“An Indexing and Querying System for Online Images Based on the PNG Format and Embedded Metadata”</a> in: <cite>ARLIS/ANZ Conference.</cite> Sep 1999. Brisbane, Australia. URL: <a href=\"http://archive.dstc.edu.au/RDU/staff/jane-hunter/PNG/paper.html\">http://archive.dstc.edu.au/RDU/staff/jane-hunter/PNG/paper.html</a> ",
+ "HTML-RDFA" : "Manu Sporny; et al. <a href=\"http://www.w3.org/TR/2011/WD-rdfa-in-html-20110525/\"><cite>HTML+RDFa 1.1</cite></a> 25 May 2011. W3C Working Draft. URL: <a href=\"http://www.w3.org/TR/2011/WD-rdfa-in-html-20110525/\">http://www.w3.org/TR/2011/WD-rdfa-in-html-20110525/</a> ",
+ "I18N-GUIDE-FRAMEWORK" : "Richard Ishida. <a href=\"http://www.w3.org/TR/2003/WD-i18n-guide-framework-20030417\"><cite>Framework Document for i18n Guidelines 1.0.</cite></a> 17 April 2003. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2003/WD-i18n-guide-framework-20030417\">http://www.w3.org/TR/2003/WD-i18n-guide-framework-20030417</a> ",
+ "ID-MGM" : "Rundle, M. <a href = 'http://identityproject.lse.ac.uk/mary.pdf'><cite>International Data Protection and Digitial Identity Management Tools</cite></a> Internet Governance Forum 2006 - Athens, Privacy Workshop I. 31 October 2006. URL: http://identityproject.lse.ac.uk/mary.pdf ",
+ "IEEE1363" : "<a href=\"http://grouper.ieee.org/groups/1363/\"><cite>IEEE 1363: Standard Specifications for Public Key Cryptography</cite></a>. August 2000. URL: <a href=\"http://grouper.ieee.org/groups/1363/\">http://grouper.ieee.org/groups/1363/</a>",
+ "IEEE1588" : "<a href=\"http://grouper.ieee.org/groups/1588/\"><cite>IEEE 1588-2008: A Precision Clock Synchronization Protocol for Networked Measurement and Control Systems</cite></a>. 24 July 2008. URL: <a href=\"http://grouper.ieee.org/groups/1588/\">http://grouper.ieee.org/groups/1588/</a>",
+ "IEEE802-1AS" : "Geoff Garner. <a href=\"http://ieee802.org/1/pages/802.1as.html\"><cite>IEEE 802.1AS - Timing and Synchronization</cite></a>. 30 March 2011. IEEE Standard. URL: <a href=\"http://ieee802.org/1/pages/802.1as.html\">http://ieee802.org/1/pages/802.1as.html</a>",
+ "IEEE802-3" : "<cite>IEEE 802.3: Carrier sense multiple access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications</cite>. December 2008.",
+ "I18N-HTML-TECH-BIDI" : "Richard Ishida. <a href=\"http://www.w3.org/TR/2007/WD-i18n-html-tech-bidi-20070606\"><cite>Internationalization Best Practices: Handling Right-to-left Scripts in XHTML and HTML Content.</cite></a> 6 June 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-i18n-html-tech-bidi-20070606\">http://www.w3.org/TR/2007/WD-i18n-html-tech-bidi-20070606</a> ",
+ "I18N-HTML-TECH-CHAR" : "Richard Ishida. <a href=\"http://www.w3.org/TR/2004/WD-i18n-html-tech-char-20040509\"><cite>Authoring Techniques for XHTML & HTML Internationalization: Characters and Encodings 1.0.</cite></a> 9 May 2004. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2004/WD-i18n-html-tech-char-20040509\">http://www.w3.org/TR/2004/WD-i18n-html-tech-char-20040509</a> ",
+ "I18N-HTML-TECH-LANG" : "Richard Ishida. <a href=\"http://www.w3.org/TR/2007/NOTE-i18n-html-tech-lang-20070412\"><cite>Internationalization Best Practices: Specifying Language in XHTML & HTML Content.</cite></a> 12 April 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-i18n-html-tech-lang-20070412\">http://www.w3.org/TR/2007/NOTE-i18n-html-tech-lang-20070412</a> ",
+ "IANA-TSV" : "Paul Lindner. <a href=\"http://www.iana.org/assignments/media-types/text/tab-separated-values\"><cite>Definition of tab-separated-values (tsv)</cite></a> June 1993. IANA Media Type Registration. URL: <a href=\"http://www.iana.org/assignments/media-types/text/tab-separated-values\">http://www.iana.org/assignments/media-types/text/tab-separated-values</a>",
+ "ICC32" : "<a href=\"http://www.color.org/icc32.pdf\"><cite>ICC Profile Format Specification, version 3.2.</cite></a> 1995. URL: <a href=\"http://www.color.org/icc32.pdf\">http://www.color.org/icc32.pdf</a>",
+ "ICC42" : "<a href=\"http://color.org/ICC1v42_2006-05.pdf\"><cite>Image technology colour management — Architecture, profile format, and data structure.</cite></a> International Color Consortium. Specification ICC.1:2004-10 (Profile version 4.2.0.0) With errata incorporated, 5/22/2006. URL: <a href=\"http://color.org/ICC1v42_2006-05.pdf\">http://color.org/ICC1v42_2006-05.pdf</a> ",
+ "ICE" : "J. Rosenberg. <a href=\"http://tools.ietf.org/html/rfc5245\"><cite>Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols.</cite></a> April 2010. Internet RFC 5245. URL: <a href=\"http://tools.ietf.org/html/rfc5245\">http://tools.ietf.org/html/rfc5245</a>",
+ "ILU-REQUESTOR" : "Paul Everitt. <a href=\"http://www.w3.org/TR/WD-ilu-requestor-960307\"><cite>The ILU Requester: Object Services in HTTP Servers.</cite></a> 7 March 1996. W3C Note. URL: <a href=\"http://www.w3.org/TR/WD-ilu-requestor-960307\">http://www.w3.org/TR/WD-ilu-requestor-960307</a> ",
+ "IMAGEMAP" : "Ian Graham. <a href=\"http://www.w3.org/TR/NOTE-imagemap\"><cite>Imagemapped Images and Image-Incapable User Agents.</cite></a> 27 November 1996. W3C Note. URL: <a href=\"http://www.w3.org/TR/NOTE-imagemap\">http://www.w3.org/TR/NOTE-imagemap</a> ",
+ "INKML" : "Stephen M. Watt; Max Froumentin; Yi-Min Chee. <a href=\"http://www.w3.org/TR/2006/WD-InkML-20061023\"><cite>Ink Markup Language (InkML).</cite></a> 23 October 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-InkML-20061023\">http://www.w3.org/TR/2006/WD-InkML-20061023</a> ",
+ "INKREQS" : "Yi-Min Chee; Sai Prasad. <a href=\"http://www.w3.org/TR/2003/NOTE-inkreqs-20030122\"><cite>Requirements for the Ink Markup Language.</cite></a> 22 January 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-inkreqs-20030122\">http://www.w3.org/TR/2003/NOTE-inkreqs-20030122</a> ",
+ "IRI" : "M. Duerst, M. Suignard. <a href=\"http://www.ietf.org/rfc/rfc3987.txt\"><cite>Internationalized Resource Identifiers (IRI).</cite></a> January 2005. Internet RFC 3987. URL: <a href=\"http://www.ietf.org/rfc/rfc3986.txt\">http://www.ietf.org/rfc/rfc3987.txt</a> ",
+ "ISO10646" : "<cite>Information Technology - Universal Multiple- Octet Coded CharacterSet (UCS) - Part 1: Architecture and Basic Multilingual Plane.</cite> ISO/IEC10646-1:1993. The current specification also takes into consideration the first five amendments to ISO/IEC 10646-1:1993. Useful <a href="http://www.egt.ie/standards/iso10646/ucs-roadmap.html">roadmaps</a>show which scripts sit at which numeric ranges.",
+ "ISO15924" : "<cite>Code for the representation of names of scripts.</cite> International Organization for Standardization. 1998. ISO 15924:1998. Draft International Standard",
+ "ISO18033-2": "<cite>Information technology -- Security techniques -- Encryption algorithms -- Part 2: Asymmetric ciphers</cite>, International Organization for Standardization. 18033-2:2006. May 2006. URL: <a href=\"http://www.iso.org/iso/home.htm\">http://www.iso.org/iso/home.htm</a>.",
+ "ISO8601" : "<cite>Representation of dates and times.</cite> International Organization for Standardization. 2004. ISO 8601:2004. URL: <a href=\"http://www.iso.org/iso/catalogue_detail?csnumber=40874\">http://www.iso.org/iso/catalogue_detail?csnumber=40874</a> ",
+ "ISO9070" : "<cite>Registration procedures for public text owner identifiers.</cite> International Organization for Standardization. 1990. ISO 9070:1990. URL: <a href=\"http://www.iso.org/iso/catalogue_detail.htm?csnumber=16644\">http://www.iso.org/iso/catalogue_detail.htm?csnumber=16644</a> ",
+ "ISO8879" : "<a href=\"http://www.iso.ch/cate/d16387.html\"><cite>Information Processing -- Text and Office Systems -- Standard Generalized Markup Language (SGML).</cite></a> ISO 8879:1986. URL: <a href=\"http://www.iso.ch/cate/d16387.html\">http://www.iso.ch/cate/d16387.html</a> ",
+ "ITS" : "Felix Sasaki; Christian Lieske. <a href=\"http://www.w3.org/TR/2007/REC-its-20070403\"><cite>Internationalization Tag Set (ITS) Version 1.0.</cite></a> 3 April 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-its-20070403\">http://www.w3.org/TR/2007/REC-its-20070403</a> ",
+ "ITSREQ" : "Yves Savourel. <a href=\"http://www.w3.org/TR/2006/WD-itsreq-20060518\"><cite>Internationalization and Localization Markup Requirements.</cite></a> 18 May 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-itsreq-20060518\">http://www.w3.org/TR/2006/WD-itsreq-20060518</a> ",
+ "ITUMCC" : "<cite>List of Mobile Countries or Geographical Region Codes.</cite> International Telecommunication Union. 2007. URL: <a href='http://www.itu.int/publ/T-SP-E.212A-2007/en'>http://www.itu.int/publ/T-SP-E.212A-2007/en</a>",
+ "ITUMNC" : "<cite>Mobile Network Codes (MNC) for The International Identification Plan for Public Networks and Subscriptions.</cite> International Telecommunication Union. 2009. URL: <a href='http://www.itu.int/publ/T-SP-E.212B-2009/en'>http://www.itu.int/publ/T-SP-E.212B-2009/en</a>",
+ "JIGSAW" : "Jigsaw Team (Yves Lafon & Benoit Mahe). <a href=\"http://www.w3.org/Jigsaw/Doc/Programmer/design.html\"><cite>Jigsaw 2.0 internal design.</cite></a> July 1999. URL: <a href=\"http://www.w3.org/Jigsaw/Doc/Programmer/design.html\">http://www.w3.org/Jigsaw/Doc/Programmer/design.html</a> ",
+ "JIS4051" : "<cite>Formatting rules for Japanese documents (『日本語文書の組版方法』).</cite> Japanese Standards Association. 2004. JIS X 4051:2004. In Japanese",
+ "JISX4051" : "<cite>Line composition rules for Japanese documents.</cite> Japanese Standards Association. 1995. JIS X 4051-1995. In Japanese",
+ "JLREQ" : "Kenzou Onozawa; et al. <a href=\"http://www.w3.org/TR/2008/WD-jlreq-20081015\"><cite>Requirements of Japanese Text Layout.</cite></a> 15 October 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-jlreq-20081015\">http://www.w3.org/TR/2008/WD-jlreq-20081015</a> ",
+ "JPEG" : "Hamilton, Eric. <a href=\"http://www.w3.org/Graphics/JPEG/jfif3.pdf\"><cite>JPEG File Interchange Format.</cite></a> Sep 1992. URL: <a href=\"http://www.w3.org/Graphics/JPEG/jfif3.pdf\">http://www.w3.org/Graphics/JPEG/jfif3.pdf</a> C-Cube Microsystems. Milpitas, CA, USA.",
+ "JPEG2000" : "Joint Photographers Expert Group (JPEG). <a href=\"http://www.jpeg.org/cd15444-1.pdf\"><cite>Jpeg 2000 image coding system.</cite></a> 9 Dec 1999. Report (draft) ISO/IEC CD15444-1:1999. URL: <a href=\"http://www.jpeg.org/cd15444-1.pdf\">http://www.jpeg.org/cd15444-1.pdf</a> ",
+ "JSON-LD" : "Manu Sporny, et al. <a href=\"http://json-ld.org/spec/latest/\"><cite>JSON-LD - Linked Data Expression in JSON</cite></a> 15 October 2010. Unofficial Draft. URL: <a href=\"http://json-ld.org/spec/latest/\">http://json-ld.org/spec/latest/</a> ",
+ "KnowPrivacy" : "Joshua Gomez; Travis Pinnick; Ashkan Soltani. <a href=\"http://www.knowprivacy.org/report/KnowPrivacy_Final_Report.pdf\"><cite>KnowPrivacy.</cite></a> 1 June 2009. URL: <a href=\"http://www.knowprivacy.org/report/KnowPrivacy_Final_Report.pdf\">http://www.knowprivacy.org/report/KnowPrivacy_Final_Report.pdf</a> ",
+ "KUIL" : "Kormann, Thierry. <a href=\"http://www.inria.fr/koala/kuil/index.html\"><cite>KUIL, the Koala User Interface Language.</cite></a> Sep 1999. Software package URL: <a href=\"http://www.inria.fr/koala/kuil/index.html\">http://www.inria.fr/koala/kuil/index.html</a> ",
+ "LANGCULTTYPE" : "John D. Berry, Ed. <cite>Language Culture Type.</cite> Graphis. 2001. ISBN 1-932026-01-0.",
+ "LBASE" : "Ramanathan V. Guha; Patrick Hayes. <a href=\"http://www.w3.org/TR/2003/NOTE-lbase-20031010\"><cite>LBase: Semantics for Languages of the Semantic Web.</cite></a> 10 October 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-lbase-20031010\">http://www.w3.org/TR/2003/NOTE-lbase-20031010</a> ",
+ "LDAP-DN" : "K. Zeilenga. <a href=\"http://www.ietf.org/rfc/rfc4514.txt\"><cite>Lightweight Directory Access Protocol : String Representation of Distinguished Names</cite></a>. June 2006. IETF RFC 4514. URL: <a href=\"http://www.ietf.org/rfc/rfc4514.txt\">http://www.ietf.org/rfc/rfc4514.txt</a>",
+ "LEIRI" : "Richard Tobin; Norman Walsh; Henry S. Thompson. <a href=\"http://www.w3.org/TR/2008/NOTE-leiri-20081103\"><cite>Legacy extended IRIs for XML resource identification.</cite></a> 3 November 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-leiri-20081103\">http://www.w3.org/TR/2008/NOTE-leiri-20081103</a> ",
+ "LEXICON-REQS" : "Paolo Baggia; Frank Scahill. <a href=\"http://www.w3.org/TR/2004/WD-lexicon-reqs-20041029\"><cite>Pronunciation Lexicon Specification (PLS) Version 1.0 Requirements.</cite></a> 29 October 2004. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2004/WD-lexicon-reqs-20041029\">http://www.w3.org/TR/2004/WD-lexicon-reqs-20041029</a> ",
+ "LIC-PRIV" : "Robin Berjon. <a href='http://dev.w3.org/2009/dap/docs/privacy-license.html'><cite>License-based Privacy: Technical Aspects.</cite></a> 19 April 2010. W3C-Internal Document. URL: <a href='http://dev.w3.org/2009/dap/docs/privacy-license.html'>http://dev.w3.org/2009/dap/docs/privacy-license.html</a> ",
+ "LTLI" : "Felix Sasaki. <a href=\"http://www.w3.org/TR/2006/WD-ltli-20060612\"><cite>Language Tags and Locale Identifiers for the World Wide Web.</cite></a> 12 June 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-ltli-20060612\">http://www.w3.org/TR/2006/WD-ltli-20060612</a> ",
+ "MATHML" : "Patrick Ion; Robert Miner. <a href=\"http://www.w3.org/1999/07/REC-MathML-19990707\"><cite>Mathematical Markup Language (MathML) 1.01 Specification.</cite></a> 7 July 1999. W3C Recommendation. URL: <a href=\"http://www.w3.org/1999/07/REC-MathML-19990707\">http://www.w3.org/1999/07/REC-MathML-19990707</a> ",
+ "MATHML-BVAR" : "Stan Devitt; Michael Kohlhase. <a href=\"http://www.w3.org/TR/2003/NOTE-mathml-bvar-20031110\"><cite>Bound Variables in MathML.</cite></a> 10 November 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-mathml-bvar-20031110\">http://www.w3.org/TR/2003/NOTE-mathml-bvar-20031110</a> ",
+ "MATHML-FOR-CSS" : "David Carlisle; et al. <a href=\"http://www.w3.org/TR/2007/WD-mathml-for-css-20071214\"><cite>A MathML for CSS profile.</cite></a> 14 December 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-mathml-for-css-20071214\">http://www.w3.org/TR/2007/WD-mathml-for-css-20071214</a> ",
+ "MATHML-TYPES" : "Stan Devitt; Michael Kohlhase; Max Froumentin. <a href=\"http://www.w3.org/TR/2003/NOTE-mathml-types-20031110\"><cite>Structured Types in MathML 2.0.</cite></a> 10 November 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-mathml-types-20031110\">http://www.w3.org/TR/2003/NOTE-mathml-types-20031110</a> ",
+ "MATHML-UNITS" : "Douglas Wilhelm Harder; Stan Devitt. <a href=\"http://www.w3.org/TR/2003/NOTE-mathml-units-20031110\"><cite>Units in MathML.</cite></a> 10 November 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-mathml-units-20031110\">http://www.w3.org/TR/2003/NOTE-mathml-units-20031110</a> ",
+ "MATHML2" : "Nico Poppelier; et al. <a href=\"http://www.w3.org/TR/2003/REC-MathML2-20031021\"><cite>Mathematical Markup Language (MathML) Version 2.0 (Second Edition).</cite></a> 21 October 2003. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2003/REC-MathML2-20031021\">http://www.w3.org/TR/2003/REC-MathML2-20031021</a> ",
+ "MATHML3" : "Patrick Ion; David Carlisle; Robert Miner. <a href=\"http://www.w3.org/TR/2008/WD-MathML3-20081117\"><cite>Mathematical Markup Language (MathML) Version 3.0.</cite></a> 17 November 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-MathML3-20081117\">http://www.w3.org/TR/2008/WD-MathML3-20081117</a> ",
+ "MCINTOSH-WRAP" : " Michael McIntosh; Paula Austel. <cite>XML signature element wrapping attacks and countermeasures.</cite> In Workshop on Secure Web Services, 2005",
+ "MDN-SETCAPTURE" : "Shepherd, Eric; et. al. <a href='https://developer.mozilla.org/en/DOM/element.setCapture'><cite>element.setCapture</cite></a> 12 Nov 2010. Mozilla Developer Network. URL: <a href='https://developer.mozilla.org/en/DOM/element.setCapture'>https://developer.mozilla.org/en/DOM/element.setCapture</a>",
+ "MEDIA-ANNOT-REQS" : "WonSuk Lee; Felix Sasaki; Tobias Bürger; Véronique Malaisé. <a href=\"http://www.w3.org/TR/2010/WD-media-annot-reqs-20100121/\"><cite>Use Cases and Requirements for Ontology and API for Media Object 1.0.</cite></a>W3C Working Draft 21 January 2010. URL: <a href=\"http://www.w3.org/TR/2010/WD-media-annot-reqs-20100121/\">http://www.w3.org/TR/2010/WD-media-annot-reqs-20100121/</a> ",
+ "MEDIA-FRAGMENT" : "R. Troncy; E. Mannens; Silvia Pfeiffer and Davy Van Deursen. <a href=\"http://www.w3.org/TR/2010/WD-media-frags-20100624\"><cite>Media Fragments URI 1.0.</cite></a> 18 November 2010. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2010/WD-media-frags-20100624\">http://www.w3.org/TR/2010/WD-media-frags-20100624</a> ",
+ "MEDIA-FRAGMENTS" : "Raphael Troncy; Erik Mannens; Silvia Pfeiffer and Davy Van Deursen. <a href=\"http://www.w3.org/TR/2011/WD-media-frags-20110317/\"><cite>Media Fragments URI 1.0</a>. W3C Working Draft 17 March 2011.</cite> URL: <a href=\"http://www.w3.org/TR/2011/WD-media-frags-20110317/\">http://www.w3.org/TR/2011/WD-media-frags-20110317/</a> ",
+ "MEDIAACCESSEVENTS" : "Ola Andersson; Jean-Claude Dufourd; Roland Lundblad. <a href=\"http://www.w3.org/TR/2006/WD-MediaAccessEvents-20061013\"><cite>Media Access Events.</cite></a> 13 October 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-MediaAccessEvents-20061013\">http://www.w3.org/TR/2006/WD-MediaAccessEvents-20061013</a> ",
+ "MEDIACAPTURE-API": "Dzung D Tran; Ilkka Oksanen; Ingmar Kliche. <a href='http://dev.w3.org/2009/dap/camera/Overview-API.html'><cite>The Media Capture API</cite></a> 3 September 2010. W3C Editors Draft. (Work in progress.) URL: <a href='http://dev.w3.org/2009/dap/camera/Overview-API.html'>http://dev.w3.org/2009/dap/camera/Overview-API.html</a> ",
+ "MEDIAONT-API": "WonSuk Lee; Florian Stegmaier; Chris Poppe. <a href=\"http://www.w3.org/TR/2010/WD-mediaont-api-1.0-20100608\"><cite>API for Media Resource 1.0.</cite></a> 8 June 2010. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2010/WD-mediaont-api-1.0-20100608\">http://www.w3.org/TR/2010/WD-mediaont-api-1.0-20100608</a> ",
+ "MEDIAQ" : "Håkon Wium Lie; et al. <a href=\"http://www.w3.org/TR/2009/CR-css3-mediaqueries-20090915/\"><cite>Media Queries.</cite></a>. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/CR-css3-mediaqueries-20090915/\">http://www.w3.org/TR/2009/CR-css3-mediaqueries-20090915/</a> ",
+ "MESSAGING-API": "Suresh Chitturi, Daniel Coloma, Max Froumentin, Maria Angeles Oteo, Niklas Widell. <a href='http://dev.w3.org/2009/dap/messaging/'><cite>The Messaging API.</cite></a> 23 August 2010. W3C Editors' Draft. (Work in progress.) URL: <a href='http://dev.w3.org/2009/dap/messaging/'>http://dev.w3.org/2009/dap/messaging/</a>",
+ "MICROFORMATS" : "<a href='http://microformats.org'><cite>Microformats</cite></a>. URL: <a href='http://microformats.org'>http://microformats.org</a> ",
+ "MIME-REG" : "N. Freed, J. Klensin. <a href=\"http://www.ietf.org/rfc/rfc4289.txt\"><cite>RFC 4289: Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures</cite></a>. December 2005. Best Current Practice. URL: <a href=\"http://www.ietf.org/rfc/rfc4289.txt\">http://www.ietf.org/rfc/rfc4289.txt</a>",
+ "MMI-ARCH" : "Jim Barnett. <a href=\"http://www.w3.org/TR/2008/WD-mmi-arch-20081016\"><cite>Multimodal Architecture and Interfaces.</cite></a> 16 October 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-mmi-arch-20081016\">http://www.w3.org/TR/2008/WD-mmi-arch-20081016</a> ",
+ "MMI-AUTH" : "Ingmar Kliche. <a href=\"http://www.w3.org/TR/2008/NOTE-mmi-auth-20080702\"><cite>Authoring Applications for the Multimodal Architecture.</cite></a> 2 July 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-mmi-auth-20080702\">http://www.w3.org/TR/2008/NOTE-mmi-auth-20080702</a> ",
+ "MMI-DEV-FEEDBACK" : "Gerald McCobb; et al. <a href=\"http://www.w3.org/TR/2006/NOTE-mmi-dev-feedback-20060414\"><cite>Multimodal Application Developer Feedback.</cite></a> 14 April 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-mmi-dev-feedback-20060414\">http://www.w3.org/TR/2006/NOTE-mmi-dev-feedback-20060414</a> ",
+ "MMI-FRAMEWORK" : "T.V. Raman; James A. Larson; David Raggett. <a href=\"http://www.w3.org/TR/2003/NOTE-mmi-framework-20030506\"><cite>W3C Multimodal Interaction Framework.</cite></a> 6 May 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-mmi-framework-20030506\">http://www.w3.org/TR/2003/NOTE-mmi-framework-20030506</a> ",
+ "MMI-REQS" : "Stéphane H. Maes; Vijay Saraswat. <a href=\"http://www.w3.org/TR/2003/NOTE-mmi-reqs-20030108\"><cite>Multimodal Interaction Requirements.</cite></a> 8 January 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-mmi-reqs-20030108\">http://www.w3.org/TR/2003/NOTE-mmi-reqs-20030108</a> ",
+ "MMI-SUGGESTIONS" : "Jim Larson. <a href=\"http://www.w3.org/TR/2006/NOTE-mmi-suggestions-20060911\"><cite>Common Sense Suggestions for Developing Multimodal User Interfaces.</cite></a> 11 September 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-mmi-suggestions-20060911\">http://www.w3.org/TR/2006/NOTE-mmi-suggestions-20060911</a> ",
+ "MMI-USE-CASES" : "David Raggett; Emily Candell. <a href=\"http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204\"><cite>Multimodal Interaction Use Cases.</cite></a> 4 December 2002. W3C Note. URL: <a href=\"http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204\">http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204</a> ",
+ "MOBILE-BP" : "Charles McCathieNevile; Jo Rabin. <a href=\"http://www.w3.org/TR/2008/REC-mobile-bp-20080729\"><cite>Mobile Web Best Practices 1.0.</cite></a> 29 July 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-mobile-bp-20080729\">http://www.w3.org/TR/2008/REC-mobile-bp-20080729</a> ",
+ "MOBILE-BP-SCOPE" : "Phil Archer; Ed Mitukiewicz. <a href=\"http://www.w3.org/TR/2005/NOTE-mobile-bp-scope-20051220\"><cite>Scope of Mobile Web Best Practices.</cite></a> 20 December 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-mobile-bp-scope-20051220\">http://www.w3.org/TR/2005/NOTE-mobile-bp-scope-20051220</a> ",
+ "MOBILEOK" : "Jo Rabin; Phil Archer. <a href=\"http://www.w3.org/TR/2008/WD-mobileOK-20081117\"><cite>W3C mobileOK Scheme 1.0.</cite></a> 17 November 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-mobileOK-20081117\">http://www.w3.org/TR/2008/WD-mobileOK-20081117</a> ",
+ "MOBILEOK-BASIC10-TESTS" : "Jo Rabin; Sean Owen. <a href=\"http://www.w3.org/TR/2008/REC-mobileOK-basic10-tests-20081208\"><cite>W3C mobileOK Basic Tests 1.0.</cite></a> 8 December 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-mobileOK-basic10-tests-20081208\">http://www.w3.org/TR/2008/REC-mobileOK-basic10-tests-20081208</a> ",
+ "MODALITY-INTERFACE" : "Brad Porter. <a href=\"http://www.w3.org/TR/2004/NOTE-modality-interface-20040510\"><cite>Modality Component to Host Environment DOM Requirements and Capabilities Assessment.</cite></a> 10 May 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-modality-interface-20040510\">http://www.w3.org/TR/2004/NOTE-modality-interface-20040510</a> ",
+ "MOZ-ICONS" : "Martin, J. Raskin, A. Gelman, L. Rood, D. Surman, M. Hadfield, G. Greant, Z. <a href = 'https://wiki.mozilla.org/Drumbeat/Challenges/Privacy_Icons'<cite>Privacy Icons</cite></a> 6 March 2010. Mozilla Wiki. URL: https://wiki.mozilla.org/Drumbeat/Challenges/Privacy_Icons ",
+ "MRCPv2" : "Burnett, D. Shanmugham, S. <a href = 'http://tools.ietf.org/html/draft-ietf-speechsc-mrcpv2-27'><cite>Media Resource Control Protocol Version 2</cite></a> 15 November 2011. URL: <a href=\"http://tools.ietf.org/html/draft-ietf-speechsc-mrcpv2-27\">http://tools.ietf.org/html/draft-ietf-speechsc-mrcpv2-27</a>",
+ "MULTIMODAL-REQS" : "Marianne Hickey. <a href=\"http://www.w3.org/TR/2000/WD-multimodal-reqs-20000710\"><cite>Multimodal Requirements for Voice Markup Languages.</cite></a> 10 July 2000. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2000/WD-multimodal-reqs-20000710\">http://www.w3.org/TR/2000/WD-multimodal-reqs-20000710</a> ",
+ "MWABP" : "Adam Connors; Bryan Sullivan. <a href=\"http://www.w3.org/TR/2010/REC-mwabp-20101214/\">Mobile Web Application Best Practices.</cite></a> 14 December 2010. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2010/REC-mwabp-20101214/\">http://www.w3.org/TR/2010/REC-mwabp-20101214/</a> ",
+ "MWBP-WCAG" : "Yeliz Yesilada; Alan Chuter. <a href=\"http://www.w3.org/TR/2008/WD-mwbp-wcag-20080703\"><cite>Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG).</cite></a> 3 July 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-mwbp-wcag-20080703\">http://www.w3.org/TR/2008/WD-mwbp-wcag-20080703</a> ",
+ "NAMES" : "Lilley, Chris. <a href=\"http://lists.w3.org/Archives/Member/w3c-ui-tech/2001Mar/0002.html\"><cite>Restrictions on identifiers.</cite></a> (forthcoming). W3C Note. URL: <a href=\"http://lists.w3.org/Archives/Member/w3c-ui-tech/2001Mar/0002.html\">http://lists.w3.org/Archives/Member/w3c-ui-tech/2001Mar/0002.html</a> ",
+ "NAMESPACESTATE" : "Norman Walsh. <a href=\"http://www.w3.org/TR/2006/WD-namespaceState-20060329\"><cite>The Disposition of Names in an XML Namespace.</cite></a> 29 March 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-namespaceState-20060329\">http://www.w3.org/TR/2006/WD-namespaceState-20060329</a> ",
+ "NAMED-GRAPHS" : "Jeremy J. Carroll; Chris Bizer; Pat Hayes; Patrick Stickler. <a href=\"http://sites.wiwiss.fu-berlin.de/suhl/bizer/SWTSGuide/carroll-ISWC2004.pdf\"><cite>Named Graphs, Provenance and Trust</cite></a>. The Semantic Web — ISWC2004, Yokohama, Springer–Verlag, 2005. URL: <a href='http://sites.wiwiss.fu-berlin.de/suhl/bizer/SWTSGuide/carroll-ISWC2004.pdf'>http://sites.wiwiss.fu-berlin.de/suhl/bizer/SWTSGuide/carroll-ISWC2004.pdf</a>.",
+ "NAVIGATOR" : "Robin Berjon; Travis Leithead; Silvia Pfeiffer; Erika Doyle Navara; Edward O'Connor; Ian Hickson. <a href=\"http://dev.w3.org/html5/spec/system-state-and-capabilities.html#the-navigator-object\"><cite>The Navigator object - System state and capabilities - HTML5.</cite></a> 28 September 2012. Editors' draft. (Work in progress.) URL: <a href=\"http://dev.w3.org/html5/spec/system-state-and-capabilities.html#the-navigator-object\">http://dev.w3.org/html5/spec/system-state-and-capabilities.html#the-navigator-object</a> ",
+ "NFC" : "M. Davis, Ken Whistler. <a href=\"http://www.unicode.org/reports/tr15/\"><cite>TR15, Unicode Normalization Forms.</cite></a>. 17 September 2010, URL: <a href=\"http://www.unicode.org/reports/tr15/\">http://www.unicode.org/reports/tr15/</a>",
+ "NGRAM-SPEC" : "David Raggett; Michael K. Brown; Andreas Kellner. <a href=\"http://www.w3.org/TR/2001/WD-ngram-spec-20010103\"><cite>Stochastic Language Models (N-Gram) Specification.</cite></a> 3 January 2001. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2001/WD-ngram-spec-20010103\">http://www.w3.org/TR/2001/WD-ngram-spec-20010103</a> ",
+ "NL-SPEC" : "Deborah A. Dahl. <a href=\"http://www.w3.org/TR/2000/WD-nl-spec-20001120\"><cite>Natural Language Semantics Markup Language for the Speech Interface Framework.</cite></a> 20 November 2000. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2000/WD-nl-spec-20001120\">http://www.w3.org/TR/2000/WD-nl-spec-20001120</a> ",
+ "NOTE-CCPP" : "Franklin Reynolds; et al. <a href=\"http://www.w3.org/1999/07/NOTE-CCPP-19990727\"><cite>Composite Capability/Preference Profiles (CC/PP): A user side framework for content negotiation.</cite></a> 27 July 1999. W3C Note. URL: <a href=\"http://www.w3.org/1999/07/NOTE-CCPP-19990727\">http://www.w3.org/1999/07/NOTE-CCPP-19990727</a> ",
+ "N3" : "Tim Berners-Lee; Dan Connolly. <a href=\"http://www.w3.org/TeamSubmission/2008/SUBM-n3-20080114/\"><cite>Notation3 (N3): A readable RDF syntax.</cite></a> 14 January 2008. W3C Team Submission. URL: <a href=\"http://www.w3.org/TeamSubmission/2008/SUBM-n3-20080114/\">http://www.w3.org/TeamSubmission/2008/SUBM-n3-20080114/</a> ",
+ "NTP" : "D. Mills. <a href=\"http://www.ietf.org/rfc/rfc1305.txt\"><cite>Network Time Protocol (Version 3)</cite></a>. March 1992. IETF RFC 1305. URL: <a href=\"http://www.ietf.org/rfc/rfc1305.txt\">http://www.ietf.org/rfc/rfc1305.txt</a>",
+ "OAEP-ATTACK" : "Manger, James. <a href=\"http://archiv.infsec.ethz.ch/education/fs08/secsem/Manger01.pdf\"><cite> A Chosen Ciphertext Attack on RSA Optimal Asymmetric Encryption Padding (OAEP) as Standardized in PKCS #1 v2.0</cite></a>. URL: <a href=\"http://archiv.infsec.ethz.ch/education/fs08/secsem/Manger01.pdf\">http://archiv.infsec.ethz.ch/education/fs08/secsem/Manger01.pdf</a>",
+ "OASIS-TAG": "Stephen D. Green, Dmitry Kostovarov. <a href=\"http://docs.oasis-open.org/tag/guidelines/v1.0/testassertionsguidelines.html\"><cite>Test Assertions Guidelines</cite></a>. OASIS Committee Draft (Work in progress) .URL: <a href=\"http://docs.oasis-open.org/tag/guidelines/v1.0/testassertionsguidelines.html\">http://docs.oasis-open.org/tag/guidelines/v1.0/testassertionsguidelines.html</a>",
+ "OGP" : "<a href=\"http://ogp.me\"> <cite>The Open Graph Protocol</cite></a>. December 2010. URL: <a href=\"http://ogp.me\">http://ogp.me</a>",
+ "OCSP" : "M. Myers, R. Ankney, A. Malpani, S. Galperin. <a href=\"http://www.ietf.org/rfc/rfc2560.txt\"><cite>X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP</cite></a>. June 1999. IETF RFC 2560. URL: <a href=\"http://www.ietf.org/rfc/rfc2560.txt\">http://www.ietf.org/rfc/rfc2560.txt</a>",
+ "ODRL11" : "Renato Iannella. <a href=\"http://www.w3.org/TR/odrl\"><cite>Open Digital Rights Language (ODRL) Version 1.1.</cite></a> W3C Note. 19 September 2002. URL: <a href=\"http://www.w3.org/TR/odrl\">http://www.w3.org/TR/odrl</a> ",
+ "OEB101" : "<a href=\"http://www.openebook.org/oebps/oebps1.0.1/download/oeb101-xhtml.htm\"><cite>Open eBook(tm) Publication Structure 1.0.1.</cite></a> Open eBook Forum(tm). 02 July 2001. URL: <a href=\"http://www.openebook.org/oebps/oebps1.0.1/download/oeb101-xhtml.htm\">http://www.openebook.org/oebps/oebps1.0.1/download/oeb101-xhtml.htm</a> ",
+ "OFFLINE-WEBAPPS" : "Ian Hickson; Anne van Kesteren. <a href=\"http://www.w3.org/TR/2008/NOTE-offline-webapps-20080530\"><cite>Offline Web Applications.</cite></a> 30 May 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-offline-webapps-20080530\">http://www.w3.org/TR/2008/NOTE-offline-webapps-20080530</a> ",
+ "OIPF-DAE-2": "Open IPTV Forum. Release 2 volume 5 (v2.1). URL:<a href='http://www.oipf.tv/docs/Release2/V2.1/OIPF-T1-R2-Specification-Volume-5-Declarative-Application-Environment-v2_1-2011-06-21.pdf'>http://www.oipf.tv/docs/Release2/V2.1/OIPF-T1-R2-Specification-Volume-5-Declarative-Application-Environment-v2_1-2011-06-21.pdf</a>",
+ "OIPF-SERV-2": "Open IPTV Forum. Services and Functions for Release 2 - v1.0”. URL:<a href='http://www.oipf.tv/docs/OIPF-T1-R2-Services_and_Functions-V1_0-2008-10-20.pdf'>http://www.oipf.tv/docs/OIPF-T1-R2-Services_and_Functions-V1_0-2008-10-20.pdf</a>",
+ "OIPF-REQS-2": "Open IPTV Forum. Open IPTV Forum Service and Platform Requirements v2.0”. URL:<a href='http://www.oipf.tv/docs/OIPF-T1-R2-Service-and-Platform-RequirementsV2_0-2008-12-12.pdf'>http://www.oipf.tv/docs/OIPF-T1-R2-Service-and-Platform-RequirementsV2_0-2008-12-12.pdf</a>",
+ "OIPF-ARCH-2": "Open IPTV Forum. Functional Architecture - V2.1”. URL:<a href='http://www.oipf.tv/docs/OIPF-T1-R2-Functional_Architecture-v2_1-2011-03-15.pdf'>http://www.oipf.tv/docs/OIPF-T1-R2-Functional_Architecture-v2_1-2011-03-15.pdf</a>",
+ "OIPF-PROT-2": "Open IPTV Forum. Release 2 volume 4 (v2.1). URL:<a href='http://www.oipf.tv/docs/Release2/V2.1/OIPF-T1-R2-Specification-Volume-4-Protocols-v2_1-2011-06-21.pdf'>http://www.oipf.tv/docs/Release2/V2.1/OIPF-T1-R2-Specification-Volume-4-Protocols-v2_1-2011-06-21.pdf</a>",
+ "OMA-CAB": "Converged Address Book Enabler, Version 1.0, Open Mobile Alliance, URL: http://www.openmobilealliance.org/",
+ "OMA-DM" : "<a href=\"http://www.openmobilealliance.org/Technical/release_program/dm_v1_2.aspx\"><cite>OMA Device Management V1.2 </cite></a> 17 June 2008. URL: <a href=\"http://www.openmobilealliance.org/Technical/release_program/dm_v1_2.aspx\">http://www.openmobilealliance.org/Technical/release_program/dm_v1_2.aspx</a> ",
+ "ORIGIN" : "<a href='http://tools.ietf.org/html/rfc6454'>The Web Origin Concept</a>, A. Barth. IETF.",
+ "OWL-FEATURES" : "Deborah L. McGuinness; Frank van Harmelen. <a href=\"http://www.w3.org/TR/2004/REC-owl-features-20040210\"><cite>OWL Web Ontology Language Overview.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-owl-features-20040210\">http://www.w3.org/TR/2004/REC-owl-features-20040210</a> ",
+ "OWL-GUIDE" : "Deborah L. McGuinness; Michael K. Smith; Chris Welty. <a href=\"http://www.w3.org/TR/2004/REC-owl-guide-20040210\"><cite>OWL Web Ontology Language Guide.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-owl-guide-20040210\">http://www.w3.org/TR/2004/REC-owl-guide-20040210</a> ",
+ "OWL-PARSING" : "Sean Bechhofer. <a href=\"http://www.w3.org/TR/2004/NOTE-owl-parsing-20040121\"><cite>OWL Web Ontology Language Parsing OWL in RDF/XML.</cite></a> 21 January 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-owl-parsing-20040121\">http://www.w3.org/TR/2004/NOTE-owl-parsing-20040121</a> ",
+ "OWL-REF" : "Guus Schreiber; Mike Dean. <a href=\"http://www.w3.org/TR/2004/REC-owl-ref-20040210\"><cite>OWL Web Ontology Language Reference.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-owl-ref-20040210\">http://www.w3.org/TR/2004/REC-owl-ref-20040210</a> ",
+ "OWL-SEMANTICS" : "Patrick Hayes; Peter F. Patel-Schneider; Ian Horrocks. <a href=\"http://www.w3.org/TR/2004/REC-owl-semantics-20040210\"><cite>OWL Web Ontology Language Semantics and Abstract Syntax.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-owl-semantics-20040210\">http://www.w3.org/TR/2004/REC-owl-semantics-20040210</a> ",
+ "OWL-TEST" : "Jeremy J. Carroll; Jos De Roo. <a href=\"http://www.w3.org/TR/2004/REC-owl-test-20040210\"><cite>OWL Web Ontology Language Test Cases.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-owl-test-20040210\">http://www.w3.org/TR/2004/REC-owl-test-20040210</a> ",
+ "OWL-TIME" : "Feng Pan; Jerry R. Hobbs. <a href=\"http://www.w3.org/TR/2006/WD-owl-time-20060927\"><cite>Time Ontology in OWL.</cite></a> 27 September 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-owl-time-20060927\">http://www.w3.org/TR/2006/WD-owl-time-20060927</a> ",
+ "OWL-XMLSYNTAX" : "Masahiro Hori; Peter F. Patel-Schneider; Jérôme Euzenat. <a href=\"http://www.w3.org/TR/2003/NOTE-owl-xmlsyntax-20030611\"><cite>OWL Web Ontology Language XML Presentation Syntax.</cite></a> 11 June 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-owl-xmlsyntax-20030611\">http://www.w3.org/TR/2003/NOTE-owl-xmlsyntax-20030611</a> ",
+ "OWL2-MANCHESTER-SYNTAX" : "Peter F. Patel-Schneider; Matthew Horridge. <a href=\"http://www.w3.org/TR/2009/NOTE-owl2-manchester-syntax-20091027/\"><cite>OWL 2 Web Ontology Language:Manchester Syntax.</cite></a> 27 October 2009. W3C Note. URL: <a href=\"http://www.w3.org/TR/2009/NOTE-owl2-manchester-syntax-20091027/\">http://www.w3.org/TR/2009/NOTE-owl2-manchester-syntax-20091027/</a> ",
+ "OWL2-MAPPING-TO-RDF" : "Boris Motik; Peter F. Patel-Schneider. <a href=\"http://www.w3.org/TR/2009/REC-owl2-mapping-to-rdf-20091027/\"><cite>OWL 2 Web Ontology Language:Mapping to RDF Graphs.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-owl2-mapping-to-rdf-20091027/\">http://www.w3.org/TR/2009/REC-owl2-mapping-to-rdf-20091027/</a> ",
+ "OWL2-NEW-FEATURES" : "Evan K. Wallace; Christine Golbreich. <a href=\"http://www.w3.org/TR/2009/REC-owl2-new-features-20091027\"><cite>OWL 2 Web Ontology Language:New Features and Rationale.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-owl2-new-features-20091027\">http://www.w3.org/TR/2009/REC-owl2-new-features-20091027</a> ",
+ "OWL2-PRIMER" : "Pascal Hitzler; Markus Krötzsch; Bijan Parsia; Peter F. Patel-Schneider; Sebastian Rudolph. <a href=\"http://www.w3.org/TR/2009/REC-owl2-primer-20091027/\"><cite>OWL 2 Web Ontology Language:Primer.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-owl2-primer-20091027/\">http://www.w3.org/TR/2009/REC-owl2-primer-20091027/</a> ",
+ "OWL2-PROFILES" : "Boris Motik; Bernardo Cuenca Grau; Ian Horrocks; Zhe Wu; Achille Fokoue; Carsten Lutz. <a href=\"http://www.w3.org/TR/2009/REC-owl2-profiles-20091027/\"><cite>OWL 2 Web Ontology Language:Profiles.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-owl2-profiles-20091027/\">http://www.w3.org/TR/2009/REC-owl2-profiles-20091027/</a> ",
+ "OWL2-QUICK-REFERENCE" : "Jie Bao; Elisa F. Kendall; Deborah L. McGuinness, Peter F. Patel-Schneider. <a href=\"http://www.w3.org/TR/2009/REC-owl2-quick-reference-20091027/\"><cite>OWL 2 Web Ontology Language:Quick Reference Guide.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-owl2-quick-reference-20091027/\">http://www.w3.org/TR/2009/REC-owl2-quick-reference-20091027/</a> ",
+ "OWL2-RDF-BASED-SEMANTICS" : "Michael Schneider. <a href=\"http://www.w3.org/TR/2009/REC-owl2-rdf-based-semantics-20091027/\"><cite>OWL 2 Web Ontology Language:RDF-Based Semantics.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-owl2-rdf-based-semantics-20091027/\">http://www.w3.org/TR/2009/REC-owl2-rdf-based-semantics-20091027/</a> ",
+ "OWL-RL-in-RIF" : "Dave Reynolds. <a href=\"http://www.w3.org/TR/2010/NOTE-rif-owl-rl-20100622/\"><cite>OWL 2 RL in RIF.</cite></a> 22 June 2010. W3C Working Group Note. URL: <a href=\"http://www.w3.org/TR/2010/NOTE-rif-owl-rl-20100622/\">http://www.w3.org/TR/2010/NOTE-rif-owl-rl-20100622/</a> ",
+ "OWL2-DIRECT-SEMANTICS" : "Boris Motik; Peter F. Patel-Schneider; Bernardo Cuenca Grau. <a href=\"http://www.w3.org/TR/2009/REC-owl2-direct-semantics-20091027/\"><cite>OWL 2 Web Ontology Language:Direct Semantics.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-owl2-direct-semantics-20091027/\">http://www.w3.org/TR/2009/REC-owl2-direct-semantics-20091027/</a> ",
+ "OWL2-SYNTAX" : "Boris Motik; Peter F. Patel-Schneider; Bijan Parsia. <a href=\"http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/\"><cite>OWL 2 Web Ontology Language:Structural Specification and Functional-Style Syntax.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/\">http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/</a> ",
+ "OWL2-CONFORMANCE" : "Michael Smith; Ian Horrocks; Markus Krötzsch; Birte Glimm. <a href=\"http://www.w3.org/TR/2009/REC-owl2-conformance-20091027/\"><cite>OWL 2 Web Ontology Language:Conformance.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-owl2-conformance-20091027/\">http://www.w3.org/TR/2009/REC-owl2-conformance-20091027/</a> ",
+ "OWL2-XML-SERIALIZATION" : "Boris Motik; Bijan Parsia; Peter Patel-Schneider; . <a href=\"http://www.w3.org/TR/2009/REC-owl2-xml-serialization-20091027/\"><cite>OWL 2 Web Ontology Language: XML Serialization.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-owl2-xml-serialization-20091027/\">http://www.w3.org/TR/2009/REC-owl2-xml-serialization-20091027/</a> ",
+ "OWL2-OVERVIEW" : "W3C OWL Working Group. <a href=\"http://www.w3.org/TR/2009/REC-owl2-overview-20091027/\"><cite>OWL 2 Web Ontology Language: Overview.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-owl2-overview-20091027/\">http://www.w3.org/TR/2009/REC-owl2-overview-20091027/</a> ",
+ "P3P-PREFERENCES" : "Marc Langheinrich. <a href=\"http://www.w3.org/TR/2002/WD-P3P-preferences-20020415\"><cite>A P3P Preference Exchange Language 1.0 (APPEL1.0).</cite></a> 15 April 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-P3P-preferences-20020415\">http://www.w3.org/TR/2002/WD-P3P-preferences-20020415</a> ",
+ "P3P-RDFSCHEMA" : "Rigo Wenning; Lorrie Cranor; Brian McBride. <a href=\"http://www.w3.org/TR/2002/NOTE-p3p-rdfschema-20020125\"><cite>An RDF Schema for P3P.</cite></a> 25 January 2002. W3C Note. URL: <a href=\"http://www.w3.org/TR/2002/NOTE-p3p-rdfschema-20020125\">http://www.w3.org/TR/2002/NOTE-p3p-rdfschema-20020125</a> ",
+ "P3P1.0" : "Massimo Marchiori. <a href=\"http://www.w3.org/TR/2002/REC-P3P-20020416\"><cite>The Platform for Privacy Preferences 1.0 (P3P1.0) Specification.</cite></a> 16 April 2002. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2002/REC-P3P-20020416\">http://www.w3.org/TR/2002/REC-P3P-20020416</a> ",
+ "P3P10-PRINCIPLES" : "Lorrie Faith Cranor. <a href=\"http://www.w3.org/TR/1998/NOTE-P3P10-principles-19980721\"><cite>P3P Guiding Principles.</cite></a> 21 July 1998. W3C Note. URL: <a href=\"http://www.w3.org/TR/1998/NOTE-P3P10-principles-19980721\">http://www.w3.org/TR/1998/NOTE-P3P10-principles-19980721</a> ",
+ "P3P10-PROTOCOLS" : "Joseph Reagle; Philip DesAutels; Steve Lucas. <a href=\"http://www.w3.org/TR/1998/NOTE-P3P10-Protocols-19980324\"><cite>P3P Protocol and Data Transport Working Group Draft White Paper.</cite></a> 24 March 1998. W3C Note. URL: <a href=\"http://www.w3.org/TR/1998/NOTE-P3P10-Protocols-19980324\">http://www.w3.org/TR/1998/NOTE-P3P10-Protocols-19980324</a> ",
+ "P3P11" : "Matthias Schunter; Rigo Wenning. <a href=\"http://www.w3.org/TR/2006/NOTE-P3P11-20061113\"><cite>The Platform for Privacy Preferences 1.1 (P3P1.1) Specification.</cite></a> 13 November 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-P3P11-20061113\">http://www.w3.org/TR/2006/NOTE-P3P11-20061113</a> ",
+ "P3PDEPLOYMENT" : "Martin Presler-Marshall. <a href=\"http://www.w3.org/TR/2002/NOTE-p3pdeployment-20020211\"><cite>The Platform for Privacy Preferences 1.0 Deployment Guide.</cite></a> 11 February 2002. W3C Note. URL: <a href=\"http://www.w3.org/TR/2002/NOTE-p3pdeployment-20020211\">http://www.w3.org/TR/2002/NOTE-p3pdeployment-20020211</a> ",
+ "PAGE-VISIBILITY" : "J. Mann; A. Jain. <a href=\"http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/PageVisibility/Overview.html\"><cite>Page Visibility</cite></a>. 26 September 2011. W3C Editor's Draft. (Work in progress.) URL: <a href=\"http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/PageVisibility/Overview.html\">http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/PageVisibility/Overview.html</a> ",
+ "PGP" : "J. Callas, L. Donnerhacke, H. Finney, D. Shaw, R. Thayer. <a href=\"http://www.ietf.org/rfc/rfc4880.txt\"><cite>OpenPGP Message Format</cite></a>. IETF RFC 4880. November 2007. URL: <a href=\"http://www.ietf.org/rfc/rfc4880.txt\">http://www.ietf.org/rfc/rfc4880.txt</a>",
+ "PICS-LABELS" : "Win Treese; et al. <a href=\"http://www.w3.org/TR/REC-PICS-labels-961031\"><cite>PICS 1.1 Label Distribution -- Label Syntax and Communication Protocols.</cite></a> 31 October 1996. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/REC-PICS-labels-961031\">http://www.w3.org/TR/REC-PICS-labels-961031</a> ",
+ "PICS-SERVICES" : "David Singer; Paul Resnick; Jim Miller. <a href=\"http://www.w3.org/TR/REC-PICS-services-961031\"><cite>PICS 1.1 Rating Services and Rating Systems -- and Their Machine Readable Descriptions.</cite></a> 31 October 1996. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/REC-PICS-services-961031\">http://www.w3.org/TR/REC-PICS-services-961031</a> ",
+ "PICSRULES" : "Clive D.W. Feather; et al. <a href=\"http://www.w3.org/TR/REC-PICSRules-971229\"><cite>PICSRules 1.1 Specification.</cite></a> 29 December 1997. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/REC-PICSRules-971229\">http://www.w3.org/TR/REC-PICSRules-971229</a> ",
+ "PKCS1" : "J. Jonsson and B. Kaliski. <a href=\"http://www.ietf.org/rfc/rfc3447.txt\"><cite>Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1.</cite></a> RFC 3447 (Informational), February 2003. URL: <a href=\"http://www.ietf.org/rfc/rfc3447.txt\">http://www.ietf.org/rfc/rfc3447.txt</a> ",
+ "PKCS5" : "B. Kaliski. <a href=\"http://www.ietf.org/rfc/rfc2898.txt\"><cite>PKCS #5 v2.0: Password-Based Cryptography Standard</cite></a> IETF RFC 2898. September 2000. URL: <a href=\"http://www.ietf.org/rfc/rfc2898.txt\">http://www.ietf.org/rfc/rfc2898.txt</a>",
+ "PKCS5Amd1" : "<a href=\"ftp://ftp.rsasecurity.com/pub/pkcs/pkcs-5v2/pkcs-5v2-0a1.pdf\"><cite>PKCS #5 v2.0 Amendment 1: XML Schema for Password-Based Cryptography</cite></a> RSA Laboratories, March 2007. URL: <a href=\"ftp://ftp.rsasecurity.com/pub/pkcs/pkcs-5v2/pkcs-5v2-0a1.pdf\">ftp://ftp.rsasecurity.com/pub/pkcs/pkcs-5v2/pkcs-5v2-0a1.pdf</a>",
+ "PLING-WIKI" : "Policy Languages Interest Group (PLING). <a href=\"http://www.w3.org/Policy/pling/\"><cite>PLING Wiki.</cite></a> URL: <a href=\"http://www.w3.org/Policy/pling/\">http://www.w3.org/Policy/pling/</a> ",
+ "PNG2e" : "David Duce. <a href=\"http://www.w3.org/TR/2003/REC-PNG-20031110\"><cite>Portable Network Graphics (PNG) Specification (Second Edition).</cite></a> 10 November 2003. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2003/REC-PNG-20031110\">http://www.w3.org/TR/2003/REC-PNG-20031110</a> ",
+ "POCO-SCHEMA" : "Joseph Smarr. <a href=\"http://portablecontacts.net/draft-spec.html#schema\"><cite>Portable Contacts 1.0 Draft C: Contact Schema</cite></a> 5 August 2008. URL: <a href=\"http://portablecontacts.net/draft-spec.html#schema\">http://portablecontacts.net/draft-spec.html#schema</a> ",
+ "POINTERS-IN-RDF" : "Mike Squillace; Carlos Iglesias. <a href=\"http://www.w3.org/TR/2009/WD-Pointers-in-RDF-20090310\"><cite>Pointer Methods in RDF.</cite></a> 10 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-Pointers-in-RDF-20090310\">http://www.w3.org/TR/2009/WD-Pointers-in-RDF-20090310</a> ",
+ "POLICY-REQS" : "Laura Arribas; Paddy Byers; Marcin Hanclik; Frederick Hirsch; David Rogers. <a href=\"http://dev.w3.org/2009/dap/policy-reqs\"><cite>Device API Policy Requirements.</cite></a> 13 April 2010. W3C Editor's Draft. (Work in progress.) URL: <a href=\"http://dev.w3.org/2009/dap/policy-reqs/\">http://dev.w3.org/2009/dap/policy-reqs/</a> ",
+ "POSITIONING" : "Robert Stevahn; Scott Furman; Scott Isaacs. <a href=\"http://www.w3.org/TR/1999/WD-positioning-19990902\"><cite>Positioning HTML Elements with Cascading Style Sheets.</cite></a> 2 September 1999. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/1999/WD-positioning-19990902\">http://www.w3.org/TR/1999/WD-positioning-19990902</a> ",
+ "POSTMSG": "Ian Hickson. <a href='http://www.w3.org/TR/webmessaging/'><cite>HTML5 Web Messaging.</cite></a> 13 March 2012. W3C Working Draft. (Work In Progress.) URL: <a href='http://www.w3.org/TR/webmessaging/'>http://www.w3.org/TR/webmessaging/</a>",
+ "POWDER-DR" : "Kevin Smith; Phil Archer; Andrea Perego. <a href=\"http://www.w3.org/TR/2008/WD-powder-dr-20081114\"><cite>Protocol for Web Description Resources (POWDER): Description Resources.</cite></a> 14 November 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-powder-dr-20081114\">http://www.w3.org/TR/2008/WD-powder-dr-20081114</a> ",
+ "POWDER-FORMAL" : "Phil Archer; Stasinos Konstantopoulos. <a href=\"http://www.w3.org/TR/2008/WD-powder-formal-20081114\"><cite>Protocol for Web Description Resources (POWDER): Formal Semantics.</cite></a> 14 November 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-powder-formal-20081114\">http://www.w3.org/TR/2008/WD-powder-formal-20081114</a> ",
+ "POWDER-GROUPING" : "Andrea Perego; Kevin Smith; Phil Archer. <a href=\"http://www.w3.org/TR/2008/WD-powder-grouping-20081114\"><cite>Protocol for Web Description Resources (POWDER): Grouping of Resources.</cite></a> 14 November 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-powder-grouping-20081114\">http://www.w3.org/TR/2008/WD-powder-grouping-20081114</a> ",
+ "POWDER-PRIMER" : "Kai Scheppe. <a href=\"http://www.w3.org/TR/2008/WD-powder-primer-20081114\"><cite>Protocol for Web Description Resources (POWDER): Primer.</cite></a> 14 November 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-powder-primer-20081114\">http://www.w3.org/TR/2008/WD-powder-primer-20081114</a> ",
+ "POWDER-TEST" : "Antonis Kukurikos. <a href=\"http://www.w3.org/TR/2008/WD-powder-test-20080815\"><cite>Protocol for Web Description Resources (POWDER): Test Suite.</cite></a> 15 August 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-powder-test-20080815\">http://www.w3.org/TR/2008/WD-powder-test-20080815</a> ",
+ "POWDER-USE-CASES" : "Phil Archer. <a href=\"http://www.w3.org/TR/2007/NOTE-powder-use-cases-20071031\"><cite>POWDER: Use Cases and Requirements.</cite></a> 31 October 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-powder-use-cases-20071031\">http://www.w3.org/TR/2007/NOTE-powder-use-cases-20071031</a> ",
+ "POWDER-VOC" : "Andrea Perego; Phil Archer. <a href=\"http://www.w3.org/TR/2007/WD-powder-voc-20070925\"><cite>Protocol for Web Description Resources (POWDER): Web Description Resources (WDR) Vocabulary.</cite></a> 25 September 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-powder-voc-20070925\">http://www.w3.org/TR/2007/WD-powder-voc-20070925</a> ",
+ "POWDER-XSD" : "Kevin Smith; Andrea Perego; Phil Archer. <a href=\"http://www.w3.org/TR/2007/WD-powder-xsd-20070925\"><cite>Protocol for Web Description Resources (POWDER): Web Description Resources Datatypes (WDRD).</cite></a> 25 September 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-powder-xsd-20070925\">http://www.w3.org/TR/2007/WD-powder-xsd-20070925</a> ",
+ "PRINT" : "Håkon Wium Lie; Robert Stevahn; Stephen Waters. <a href=\"http://www.w3.org/TR/1999/WD-print-19990902\"><cite>CSS Printing Extensions.</cite></a> 2 September 1999. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/1999/WD-print-19990902\">http://www.w3.org/TR/1999/WD-print-19990902</a> ",
+ "PRIV-ICONS": "Raskin, A. <a href ='http://www.azarask.in/blog/post/what-should-matter-in-privacy'><cite>The 7 Things that Mater Most in Privacy</cite></a> 31 March 2010. URL: http://www.azarask.in/blog/post/what-should-matter-in-privacy ",
+ "PRIV-ICONSET" : "Mehldau, M. <a href = 'http://asset.netzpolitik.org/wp-upload/data-privacy-icons-v01.pdf'><cite>Iconset for Data-Privacy Declarations v0.1</cite></a> URL: http://www.netzpolitik.org/wp-upload/data-privacy-icons-v01.pdf ",
+ "PRIV-LABEL": "Kelley, P. Bresse, J. Cranor, L. Reeder, R. <a href ='http://cups.cs.cmu.edu/soups/2009/proceedings/a4-kelley.pdf'><cite>A 'Nutrition Label' for Privacy</cite></a> 10 November 2009. Carnegie Mellon University. URL: http://cups.cs.cmu.edu/soups/2009/proceedings/a4-kelley.pdf ",
+ "PRIVACY-BY-DESIGN": "Ann Cavoukian, PhD. <a href='http://www.ipc.on.ca/images/Resources/7foundationalprinciples.pdf'><cite>Privacy By Design: The 7 Foundational Principles</cite></a>. August 2009, revised January 2011. URL: <a href='http://www.ipc.on.ca/images/Resources/7foundationalprinciples.pdf'>http://www.ipc.on.ca/images/Resources/7foundationalprinciples.pdf</a>",
+ "PRIVACY-ISSUES-GEO": "Doty, N. Mulligan, D. Wilde, E. <a href='http://escholarship.org/uc/item/0rp834wf'><cite>Privacy Issues of the W3C Geolocation API</cite></a>. UC Berkeley School of Information. 24 February 2010. URL: http://escholarship.org/uc/item/0rp834wf ",
+ "PRIVACY-TERMINOLOGY" : "A. Pfitzmann, M. Hansen, H Tschofenig. <a href=\"http://tools.ietf.org/id/draft-hansen-privacy-terminology-00.html\"><cite>Terminology for Talking about Privacy by Data Minimization: Anonymity, Unlinkability, Undetectability, Unobservability, Pseudonymity, and Identity Management</cite></a> IETF Internet Draft. URL: <a hre\"http://tools.ietf.org/id/draft-hansen-privacy-terminology-00.html\">http://tools.ietf.org/id/draft-hansen-privacy-terminology-00.html</a>",
+ "PROC-MODEL-REQ" : "Dmitry Lenkov; Norman Walsh. <a href=\"http://www.w3.org/TR/2004/NOTE-proc-model-req-20040405\"><cite>XML Processing Model Requirements.</cite></a> 5 April 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-proc-model-req-20040405\">http://www.w3.org/TR/2004/NOTE-proc-model-req-20040405</a> ",
+ "PROGRESS-EVENTS" : "Charles McCathieNevile. <a href=\"http://www.w3.org/TR/2011/CR-progress-events-20110922/\"><cite>Progress Events 1.0.</cite></a> 22 September 2011. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/CR-progress-events-20110922/\">http://www.w3.org/TR/2011/CR-progress-events-20110922/</a> ",
+ "PROV-RDF-S" : "Panagiotis Pediaditis; Giorgos Flouris; Irini Fundulaki; Vassilis Christophides. <a href=\"http://www.usenix.org/events/tapp09/tech/full_papers/pediaditis/pediaditis_html/\"><cite>On Explicit Provenance Management in RDF/S Graphs</cite></a> 2009. First Workshop on the Theory and Practice of Provenance (TaPP'09), ed. James Cheney. San Francisco, CA. URL: <a href='http://www.usenix.org/events/tapp09/tech/full_papers/pediaditis/pediaditis_html/'>http://www.usenix.org/events/tapp09/tech/full_papers/pediaditis/pediaditis_html/</a> ",
+ "PROV-QUERY" : "Renata Dividino; Sergey Sizov; Steffen Staab; Bernhard Schueler. <a href=\"http://linkinghub.elsevier.com/retrieve/pii/S1570826809000237\"><cite>Querying for provenance, trust, uncertainty and other meta knowledge in RDF</cite></a>. 2009. Web Semantics: Science, Services and Agents on the World Wide Web, vol. 7, 2009, p. 204-219. URL: <a href='http://linkinghub.elsevier.com/retrieve/pii/S1570826809000237'>http://linkinghub.elsevier.com/retrieve/pii/S1570826809000237</a> ",
+ "PRONUNCIATION-LEXICON" : "Paolo Baggia. <a href=\"http://www.w3.org/TR/2008/REC-pronunciation-lexicon-20081014\"><cite>Pronunciation Lexicon Specification (PLS) Version 1.0.</cite></a> 14 October 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-pronunciation-lexicon-20081014\">http://www.w3.org/TR/2008/REC-pronunciation-lexicon-20081014</a> ",
+ "PTECH-DECL" : "C. Concolato; J. Le Feuvre; J. C. Dufourd. <a href=\"http://biblio.telecom-paristech.fr/cgi-bin/download.cgi?id=9917\"><cite>Declarative Interfaces for Dynamic Widgets Communications</cite></a>. September 2009. Document Engineering, Munich, Germany, September 2009, pp. 241-244. PDF Document. URL: <a href=\"http://biblio.telecom-paristech.fr/cgi-bin/download.cgi?id=9917\">http://biblio.telecom-paristech.fr/cgi-bin/download.cgi?id=9917</a>",
+ "PTECH-MIGRATE" : "C. Concolato; J. C. Dufourd; J. Le Feuvre; K. Parkl J. Song. <a href=\"http://biblio.telecom-paristech.fr/cgi-bin/download.cgi?id=11187\"><cite>Communicating and migratable interactive multimedia documents</cite></a>. May 2011. Multimedia Tools and Applications. PDF document. URL: <a href=\"http://biblio.telecom-paristech.fr/cgi-bin/download.cgi?id=11187\">http://biblio.telecom-paristech.fr/cgi-bin/download.cgi?id=11187</a>",
+ "PTECH-SCW" : "J. C. Dufourd; C. Concolato; J. Le Feuvre. <a href=\"http://www.svgopen.org/2009/papers/28-SVG_Communicating_Widgets/\"><cite>SVG Communicating Widgets</cite></a>. October 2009. SVG Open, Mountain View, CA, USA. URL: <a href=\"http://www.svgopen.org/2009/papers/28-SVG_Communicating_Widgets/\">http://www.svgopen.org/2009/papers/28-SVG_Communicating_Widgets/</a>",
+ "PTECH-WM" : "J. Le Feuvre; C. Concolato; J. C. Dufourd. <a href=\"http://biblio.telecom-paristech.fr/cgi-bin/download.cgi?id=9919\"><cite>Widgets Mobility</cite></a>. September 2009. International Conference on Mobile Technology, Applications and Systems, Nice, France. PDF document. URL: <a href=\"http://biblio.telecom-paristech.fr/cgi-bin/download.cgi?id=9919\">http://biblio.telecom-paristech.fr/cgi-bin/download.cgi?id=9919</a>",
+ "PWGMSN" : "Ron Bergman; Tom Hastings. <a href=\"ftp://ftp.pwg.org/pub/pwg/candidates/cs-pwgmsn10-20020226-5101.1.pdf\"><cite>Media Standardized Names.</cite></a> 26 February 2002. IEEE ISTO Printer Working Group 5101.1-2002. URL: <a href=\"ftp://ftp.pwg.org/pub/pwg/candidates/cs-pwgmsn10-20020226-5101.1.pdf\">ftp://ftp.pwg.org/pub/pwg/candidates/cs-pwgmsn10-20020226-5101.1.pdf</a> ",
+ "QA-HANDBOOK" : "Lofton Henderson. <a href=\"http://www.w3.org/TR/2005/NOTE-qa-handbook-20050906\"><cite>The QA Handbook.</cite></a> 6 September 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-qa-handbook-20050906\">http://www.w3.org/TR/2005/NOTE-qa-handbook-20050906</a> ",
+ "QAFRAME-OPS-EXTECH" : "Dimitris Dimitriadis; et al. <a href=\"http://www.w3.org/TR/2002/NOTE-qaframe-ops-extech-20021202\"><cite>QA Framework: Operational Examples & Techniques.</cite></a> 2 December 2002. W3C Note. URL: <a href=\"http://www.w3.org/TR/2002/NOTE-qaframe-ops-extech-20021202\">http://www.w3.org/TR/2002/NOTE-qaframe-ops-extech-20021202</a> ",
+ "QAFRAME-SPEC" : "Lynne Rosenthal; et al. <a href=\"http://www.w3.org/TR/2005/REC-qaframe-spec-20050817\"><cite>QA Framework: Specification Guidelines.</cite></a> 17 August 2005. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2005/REC-qaframe-spec-20050817\">http://www.w3.org/TR/2005/REC-qaframe-spec-20050817</a> ",
+ "QAFRAME-TEST" : "Patrick Curran; Dimitris Dimitriadis. <a href=\"http://www.w3.org/TR/2004/WD-qaframe-test-20040820\"><cite>QA Framework: Test Guidelines.</cite></a> 20 August 2004. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2004/WD-qaframe-test-20040820\">http://www.w3.org/TR/2004/WD-qaframe-test-20040820</a> ",
+ "QNAMES" : "N. Walsh. <a href=\"http://www.w3.org/2001/tag/doc/qnameids-2004-03-17\"><cite>Using Qualified Names (QNames) as Identifiers in XML Content</cite></a> 17 March, 2004. TAG Finding. URL: <a href=\"http://www.w3.org/2001/tag/doc/qnameids-2004-03-17\">http://www.w3.org/2001/tag/doc/qnameids-2004-03-17</a> ",
+ "RANDOM" : "D. Eastlake, S. Crocker, J. Schiller. <a href=\"http://www.ietf.org/rfc/rfc4086.txt\"><cite>Randomness Recommendations for Security.</cite></a>. IETF RFC 4086. June 2005. URL: <a href=\"http://www.ietf.org/rfc/rfc4086.txt\">http://www.ietf.org/rfc/rfc4086.txt</a>",
+ "RDF-CONCEPTS" : "Graham Klyne; Jeremy J. Carroll. <a href=\"http://www.w3.org/TR/2004/REC-rdf-concepts-20040210\"><cite>Resource Description Framework (RDF): Concepts and Abstract Syntax.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-rdf-concepts-20040210\">http://www.w3.org/TR/2004/REC-rdf-concepts-20040210</a> ",
+ "RDF-DAWG-UC" : "Kendall Grant Clark. <a href=\"http://www.w3.org/TR/2005/WD-rdf-dawg-uc-20050325\"><cite>RDF Data Access Use Cases and Requirements.</cite></a> 25 March 2005. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2005/WD-rdf-dawg-uc-20050325\">http://www.w3.org/TR/2005/WD-rdf-dawg-uc-20050325</a> ",
+ "RDF-MT" : "Patrick Hayes. <a href=\"http://www.w3.org/TR/2004/REC-rdf-mt-20040210\"><cite>RDF Semantics.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-rdf-mt-20040210\">http://www.w3.org/TR/2004/REC-rdf-mt-20040210</a> ",
+ "RDF-PRIMER" : "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> ",
+ "RDF-SCHEMA" : "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> ",
+ "RDF-SPARQL-JSON-RES" : "Kendall Grant Clark; Elias Torres; Lee Feigenbaum. <a href=\"http://www.w3.org/TR/2007/NOTE-rdf-sparql-json-res-20070618\"><cite>Serializing SPARQL Query Results in JSON.</cite></a> 18 June 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-rdf-sparql-json-res-20070618\">http://www.w3.org/TR/2007/NOTE-rdf-sparql-json-res-20070618</a> ",
+ "RDF-SPARQL-PROTOCOL" : "Lee Feigenbaum; Kendall Grant Clark; Elias Torres. <a href=\"http://www.w3.org/TR/2008/REC-rdf-sparql-protocol-20080115\"><cite>SPARQL Protocol for RDF.</cite></a> 15 January 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-rdf-sparql-protocol-20080115\">http://www.w3.org/TR/2008/REC-rdf-sparql-protocol-20080115</a> ",
+ "RDF-SPARQL-QUERY" : "Andy Seaborne; Eric Prud'hommeaux. <a href=\"http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115\"><cite>SPARQL Query Language for RDF.</cite></a> 15 January 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115\">http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115</a> ",
+ "RDF-SPARQL-XMLRES" : "Jeen Broekstra; Dave Beckett. <a href=\"http://www.w3.org/TR/2008/REC-rdf-sparql-XMLres-20080115\"><cite>SPARQL Query Results XML Format.</cite></a> 15 January 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-rdf-sparql-XMLres-20080115\">http://www.w3.org/TR/2008/REC-rdf-sparql-XMLres-20080115</a> ",
+ "RDF-SYNTAX" : "Ora Lassila; Ralph R. Swick. <a href=\"http://www.w3.org/TR/1999/REC-rdf-syntax-19990222\"><cite>Resource Description Framework (RDF) Model and Syntax Specification.</cite></a> 22 February 1999. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/1999/REC-rdf-syntax-19990222\">http://www.w3.org/TR/1999/REC-rdf-syntax-19990222</a> ",
+ "RDF-SYNTAX-GRAMMAR" : "Dave Beckett. <a href=\"http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210\"><cite>RDF/XML Syntax Specification (Revised).</cite></a> 10 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210\">http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210</a> ",
+ "RDF-TESTCASES" : "Jan Grant; Dave Beckett. <a href=\"http://www.w3.org/TR/2004/REC-rdf-testcases-20040210\"><cite>RDF Test Cases.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-rdf-testcases-20040210\">http://www.w3.org/TR/2004/REC-rdf-testcases-20040210</a> ",
+ "RDF-UML" : "Walter W. Chang. <a href=\"http://www.w3.org/TR/1998/NOTE-rdf-uml-19980804\"><cite>A Discussion of the Relationship Between RDF-Schema and UML.</cite></a> 4 August 1998. W3C Note. URL: <a href=\"http://www.w3.org/TR/1998/NOTE-rdf-uml-19980804\">http://www.w3.org/TR/1998/NOTE-rdf-uml-19980804</a> ",
+ "RDFA-CORE" : "Shane McCarron; et al. <a href=\"http://www.w3.org/TR/2012/REC-rdfa-core-20120607/\"><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> ",
+ "RDFA-LITE" : "Manu Sporny. <a href=\"http://www.w3.org/TR/2012/REC-rdfa-lite-20120607/\"><cite>RDFa Lite 1.1.</cite></a> 7 June 2012. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2012/REC-rdfa-lite-20120607/\">http://www.w3.org/TR/2012/REC-rdfa-lite-20120607/</a> ",
+ "RDFA-PRIMER" : "Ben Adida, Ivan Herman, Manu Sporny. <a href=\"http://www.w3.org/TR/2012/NOTE-rdfa-primer-20120607\"><cite>RDFa Primer.</cite></a> 07 June 2012. W3C Note. URL: <a href=\"http://www.w3.org/TR/2012/NOTE-rdfa-primer-20120607\">http://www.w3.org/TR/2012/NOTE-rdfa-primer-20120607</a> ",
+ "RDFA-SYNTAX" : "Ben Adida, et al. <a href=\"http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014\"><cite>RDFa in XHTML: Syntax and Processing.</cite></a> 14 October 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014\">http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014</a> ",
+ "RDFCAL" : "Dan Connolly; Libby Miller. <a href=\"http://www.w3.org/TR/2005/NOTE-rdfcal-20050929\"><cite>RDF Calendar - an application of the Resource Description Framework to iCalendar Data.</cite></a> 29 September 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-rdfcal-20050929\">http://www.w3.org/TR/2005/NOTE-rdfcal-20050929</a> ",
+ "RDFTM-SURVEY" : "Fabio Vitali; et al. <a href=\"http://www.w3.org/TR/2006/NOTE-rdftm-survey-20060210\"><cite>A Survey of RDF/Topic Maps Interoperability Proposals.</cite></a> 10 February 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-rdftm-survey-20060210\">http://www.w3.org/TR/2006/NOTE-rdftm-survey-20060210</a> ",
+ "RELAXNG-SCHEMA" : "<a href=\"http://standards.iso.org/ittf/PubliclyAvailableStandards/c052348_ISO_IEC_19757-2_2008(E).zip\"><cite>Information technology -- Document Schema Definition Language (DSDL) -- Part 2: Regular-grammar-based validation -- RELAX NG</cite></a>. ISO/IEC 19757-2:2008. URL: <a href=\"http://standards.iso.org/ittf/PubliclyAvailableStandards/c052348_ISO_IEC_19757-2_2008(E).zip\">http://standards.iso.org/ittf/PubliclyAvailableStandards/c052348_ISO_IEC_19757-2_2008(E).zip</a>",
+ "REUSABLE-DIALOG-REQS" : "Daniel C. Burnett. <a href=\"http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426\"><cite>Reusable Dialog Requirements for Voice Markup Language.</cite></a> 26 April 2000. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426\">http://www.w3.org/TR/2000/WD-reusable-dialog-reqs-20000426</a> ",
+ "REX" : "Robin Berjon. <a href=\"http://www.w3.org/TR/2006/WD-rex-20061013\"><cite>Remote Events for XML (REX) 1.0.</cite></a> 13 October 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-rex-20061013\">http://www.w3.org/TR/2006/WD-rex-20061013</a> ",
+ "REX-REQS" : "Robin Berjon. <a href=\"http://www.w3.org/TR/2006/NOTE-rex-reqs-20060202\"><cite>Remote Events for XML (REX) Requirements.</cite></a> 2 February 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-rex-reqs-20060202\">http://www.w3.org/TR/2006/NOTE-rex-reqs-20060202</a> ",
+ "RFC1034" : "P. Mockapetris. <a href=\"http://www.ietf.org/rfc/rfc1034.txt\"><cite>DOMAIN NAMES - CONCEPTS AND FACILITIES.</cite></a> November 1987. Internet RFC 1034. URL: <a href=\"http://www.ietf.org/rfc/rfc1034.txt\">http://www.ietf.org/rfc/rfc1034.txt</a> ",
+ "RFC1738" : "T. Berners-Lee; L. Masinter; M. McCahill. <a href=\"http://www.ietf.org/rfc/rfc1738.txt\"><cite>Uniform Resource Locators (URL).</cite></a> December 1994. Internet RFC 1738. URL: <a href=\"http://www.ietf.org/rfc/rfc1738.txt\">http://www.ietf.org/rfc/rfc1738.txt</a> ",
+ "RFC1808" : "R. Fielding. <a href=\"http://www.ietf.org/rfc/rfc1808.txt\"><cite>Relative Uniform Resource Locators.</cite></a> June 1995. Internet RFC 1808 (Obsoleted by RFC 3986). URL: <a href=\"http://www.ietf.org/rfc/rfc1808.txt\">http://www.ietf.org/rfc/rfc1808.txt</a> ",
+ "RFC2045" : "N. Freed and N. Borenstein. <a href=\"http://www.ietf.org/rfc/rfc2045.txt\"><cite>Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies.</cite></a> November 1996. URL: <a href=\"http://www.ietf.org/rfc/rfc2045.txt\">http://www.ietf.org/rfc/rfc2045.txt</a> ",
+ "RFC2046" : "N. Freed; N. Borenstein. <a href=\"http://www.ietf.org/rfc/rfc2046.txt\"><cite>Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types.</cite></a> November 1996. Internet RFC 2046. URL: <a href=\"http://www.ietf.org/rfc/rfc2046.txt\">http://www.ietf.org/rfc/rfc2046.txt</a> ",
+ "RFC2119" : "S. Bradner. <a href=\"http://www.ietf.org/rfc/rfc2119.txt\"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119. URL: <a href=\"http://www.ietf.org/rfc/rfc2119.txt\">http://www.ietf.org/rfc/rfc2119.txt</a> ",
+ "RFC2231" : "N. Freed, K. Moore. <a href=\"http://www.ietf.org/rfc/rfc2231.txt\"><cite>MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations.</cite></a> November 1997. IETF RFC 2231. URL: <a href=\"http://www.ietf.org/rfc/rfc2231.txt\">http://www.ietf.org/rfc/rfc2231.txt</a> ",
+ "RFC2318" : "H. Lie, B. Bos, C. Lilley. <a href=\"http://www.ietf.org/rfc/rfc2318.txt\"><cite>The text/css Media Type.</cite></a> March 1998. URL: <a href=\"http://www.ietf.org/rfc/rfc2318.txt\">http://www.ietf.org/rfc/rfc2318.txt</a> ",
+ "RFC2397" : "L. Masinter. <a href=\"http://www.ietf.org/rfc/rfc2397.txt\"><cite>The "data" URL scheme.</cite></a> August 1998. Internet RFC 2397. URL: <a href=\"http://www.ietf.org/rfc/rfc2397.txt\">http://www.ietf.org/rfc/rfc2397.txt</a> ",
+ "RFC2426" : "F. Dawson, T. Howes. <a href=\"http://www.ietf.org/rfc/rfc2426.txt\"><cite>vCard MIME Directory Profile.</cite></a> September 1998. URL: <a href=\"http://www.ietf.org/rfc/rfc2426.txt\">http://www.ietf.org/rfc/rfc2426.txt</a> ",
+ "RFC2531" : "G. Klyne; L. McIntyre. <a href=\"http://www.ietf.org/rfc/rfc2531.txt\"><cite>Content Feature Schema for Internet Fax.</cite></a> March 1999. Internet RFC 2531. URL: <a href=\"http://www.ietf.org/rfc/rfc2531.txt\">http://www.ietf.org/rfc/rfc2531.txt</a> ",
+ "RFC2533" : "G. Klyne. <a href=\"http://www.ietf.org/rfc/rfc2533\"><cite>A Syntax for Describing Media Feature Sets.</cite></a> March 1999. Internet RFC 2533. URL: <a href=\"http://www.ietf.org/rfc/rfc2533\">http://www.ietf.org/rfc/rfc2533</a> ",
+ "RFC2534" : "L. Masinter; D. Wing; et al. <a href=\"http://www.ietf.org/rfc/rfc2534\"><cite>Media Features for Display, Print, and Fax.</cite></a> March 1999. Internet RFC 2534. URL: <a href=\"http://www.ietf.org/rfc/rfc2534\">http://www.ietf.org/rfc/rfc2534</a> ",
+ "RFC3406" : "L. Daigle, D. van Gulik, R. Iannella, P. Faltstrom. <a href=\"http://www.ietf.org/rfc/rfc3406.txt\"><cite> URN Namespace Definition Mechanisms.</cite></a>. IETF RFC 3406 October 2002. URL: <a href=\"http://www.ietf.org/rfc/rfc3406.txt\"> http://www.ietf.org/rfc/rfc3406.txt</a>",
+ "RFC2854" : "D. Connolly; L. Masinter. <a href=\"http://www.rfc-editor.org/rfc/rfc2854.txt\"><cite>The 'text/html' Media Type.</cite></a> June 2000. Internet RFC 2854. URL: <a href=\"http://www.rfc-editor.org/rfc/rfc2854.txt\">http://www.rfc-editor.org/rfc/rfc2854.txt</a> ",
+ "RFC2978" : "N. Freed; J. Postel. <a href=\"http://www.ietf.org/rfc/rfc2978.txt\"><cite>IANA Charset Registration Procedures.</cite></a> October 2000. Internet RFC 2978. URL: <a href=\"http://www.ietf.org/rfc/rfc2978.txt\">http://www.ietf.org/rfc/rfc2978.txt</a> ",
+ "RFC3023" : "M. Murata; S. St.Laurent; D. Kohn. <a href=\"http://www.ietf.org/rfc/rfc3023.txt\"><cite>XML Media Types</cite></a> January 2001. Internet RFC 3023. URL: <a href=\"http://www.ietf.org/rfc/rfc3023.txt\">http://www.ietf.org/rfc/rfc3023.txt</a> ",
+ "RFC3161" : "C. Adams, P. Cain, D. Pinkas, R. Zuccherato. <a href=\"http://www.rfc-editor.org/rfc/rfc3161.txt\"><cite>Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)</cite></a> August 2001. Internet RFC 3161. URL: <a href=\"http://www.rfc-editor.org/rfc/rfc3161.txt\">http://www.rfc-editor.org/rfc/rfc3161.txt</a> ",
+ "RFC3161-PKIX-UPDATE-9" : "Stefan Santesson, Nick Pope. <a href=\"http://tools.ietf.org/id/draft-ietf-pkix-rfc3161-update-09.txt\"><cite> ESSCertIDv2 update for RFC 3161</cite></a> 29 April 2010, IETF Internet Draft. URL: <a href=\"http://tools.ietf.org/id/draft-ietf-pkix-rfc3161-update-09.txt\"> http://tools.ietf.org/id/draft-ietf-pkix-rfc3161-update-09.txt</a> ",
+ "RFC3218" : "Rescorla, E. <a href=\"http://tools.ietf.org/html/rfc3218\"><cite>Preventing the Million Message Attack on Cryptographic Message Syntax.</cite></a>January 2002. Informational RFC 3218. URL: <a href=\"http://tools.ietf.org/html/rfc3218\">http://tools.ietf.org/html/rfc3218</a>",
+ "RFC3236" : "P. Stark; M. Baker. <a href=\"http://www.rfc-editor.org/rfc/rfc3236.txt\"><cite>The 'application/xhtml+xml' Media Type.</cite></a> January 2002. Internet RFC 3236. URL: <a href=\"http://www.rfc-editor.org/rfc/rfc3236.txt\">http://www.rfc-editor.org/rfc/rfc3236.txt</a> ",
+ "RFC3264" : " J. Rosenberg; H. Schulzrinne. <a href=\"http://www.rfc-editor.org/rfc/rfc3264.txt\"><cite>An Offer/Answer Model with the Session Description Protocol (SDP).</cite></a> June 2002. Internet RFC 3264. URL: <a href=\"http://www.rfc-editor.org/rfc/rfc3264.txt\">http://www.rfc-editor.org/rfc/rfc3264.txt</a> ",
+ "RFC3279" : "W. Polk, R. Housley, L. Bassham. <a href=\"http://www.ietf.org/rfc/rfc3279.txt\"><cite>Algorithmupdates and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile</cite></a>. April 2002. Internet RFC 3279. URL: <a href=\"http://www.ietf.org/rfc/rfc3279.txt\">http://www.ietf.org/rfc/rfc3279.txt</a>",
+ "RFC3339" : "G. Klyne, C. Newman. <a href=\"http://www.ietf.org/rfc/rfc3339.txt\"><cite>Date and Time on the Internet: Timestamps</cite></a>. July 2002. Internet RFC 3339. URL: <a href=\"http://www.ietf.org/rfc/rfc3339.txt\">http://www.ietf.org/rfc/rfc3339.txt</a>",
+ "RFC3490" : "P. Faltstrom; P. Hoffman; A. Costello. <a href='http://www.rfc-editor.org/rfc/rfc3490.txt'><cite>Internationalizing Domain Names in Applications (IDNA).</cite></a> March 2003. Internet RFC 3490. URL: <a href='http://www.rfc-editor.org/rfc/rfc3490.txt'>http://www.rfc-editor.org/rfc/rfc3490.txt</a>",
+ "RFC3555" : "S. Casner; P. Hoschka. <a href='http://www.rfc-editor.org/rfc/rfc3555.txt'><cite>MIME Type Registration of RTP Payload Formats</cite></a>. July 2003. Internet RFC 3555. URL: <a href='http://www.rfc-editor.org/rfc/rfc3555.txt'>http://www.rfc-editor.org/rfc/rfc3555.txt</a>",
+ "RFC3986" : "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> ",
+ "RFC3987" : "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> ",
+ "RFC4050" : "S. Blake-Wilson, G. Karlinger, T. Kobayashi, Y. Wang. <a href=\"http://www.ietf.org/rfc/rfc4050.txt\"><cite>Using the Elliptic Curve Signature Algorithm (ECDSA) for XML Digital Signatures.</cite></a> IETF RFC 4050. April 2005. URL: <a href=\"http://www.ietf.org/rfc/rfc4050.txt\">http://www.ietf.org/rfc/rfc4050.txt</a>",
+ "RFC4051" : "D. Eastlake 3rd. <a href=\"http://www.ietf.org/rfc/rfc4051.txt\"><cite>Additional XML Security Uniform Resource Identifiers</cite></a>. RFC 4051 April 2005. URL: <a href=\"http://www.ietf.org/rfc/rfc4051.txt\">http://www.ietf.org/rfc/rfc4051.txt</a>",
+ "RFC4055" : "J. Schaad, B. Kaliski, R. Housley. <a href=\"http://www.ietf.org/rfc/rfc4055.txt\"><cite>Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile</cite></a>. June 2005. IETF RFC 4055. URL: <a href=\"http://www.ietf.org/rfc/rfc4055.txt\">http://www.ietf.org/rfc/rfc4055.txt</a>",
+ "RFC4122" : "P. Leach; M. Mealling; R. Salz. <a href=\"http://www.ietf.org/rfc/rfc4122.txt\"><cite>A Universally Unique IDentifier (UUID) URN Namespace</cite></a> July 2005. Internet RFC 4122. URL: <a href=\"http://www.ietf.org/rfc/rfc4122.txt\">http://www.ietf.org/rfc/rfc4122.txt</a> ",
+ "RFC4180" : "Y. Shafranovich. <a href=\"http://www.ietf.org/rfc/rfc4180.txt\"> <cite>Common Format and MIME Type for Comma-Separated Values (CSV) Files</cite></a> October 2005. Internet RFC 3987. URL: <a href=\"http://www.ietf.org/rfc/rfc4180.txt\">http://www.ietf.org/rfc/rfc4180.txt</a>",
+ "RFC4281" : "R. Gellens, D. Singer, P. Frojdh. <a href=\"http://www.ietf.org/rfc/rfc4281.txt\"><cite>The Codecs Parameter for "Bucket" Media Types</cite></a> November 2005. Internet RFC 4281. URL: <a href=\"http://www.ietf.org/rfc/rfc4281.txt\">http://www.ietf.org/rfc/rfc4281.txt</a> ",
+ "RFC4572" : "J. Lennox. <a href=\"http://www.ietf.org/rfc/rfc4572.txt\"><cite> Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP).</cite></a> July 2006. Internet RFC 4572. URL: <a href=\"http://www.ietf.org/rfc/rfc4572.txt\">http://www.ietf.org/rfc/rfc4572.txt</a>",
+ "RFC4627" : "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>",
+ "RFC4770" : "C. Jennings; J. Reschke. <a href=\"http://www.ietf.org/rfc/rfc4770.txt\"><cite>vCard Extensions for Instant Messaging (IM)</cite></a> January 2007. Internet RFC 4770. URL: <a href=\"http://www.ietf.org/rfc/rfc4770.txt\">http://www.ietf.org/rfc/rfc4770.txt</a> ",
+ "RFC4868" : "S. Kelly, S. Frankel. <a href=\"http://www.ietf.org/rfc/rfc4868.txt\"><cite>Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 with IPsec</cite></a> IETF RFC 4868. May 2007. URL: <a href=\"http://www.ietf.org/rfc/rfc4868.txt\">http://www.ietf.org/rfc/rfc4868.txt</a>",
+ "RFC4949" : "R. Shirey. <a href=\"http://www.ietf.org/rfc/rfc4949.txt\"><cite>Internet Security Glossary, Version 2.</cite></a>. IETF RFC 4949. August 2007. URL: <a href=\"http://www.ietf.org/rfc/rfc4949.txt\">http://www.ietf.org/rfc/rfc4949.txt</a>",
+ "RFC5280" : "D. Cooper, et. al. <a href=\"http://www.ietf.org/rfc/rfc5280.txt\"><cite> Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile. </cite></a>. IETF RFC 5280 May 2008. URL: <a href=\"http://www.ietf.org/rfc/rfc5280.txt\">http://www.ietf.org/rfc/rfc5280.txt</a>",
+ "RFC5480" : "S. Turner, et. al. <a href=\"http://www.ietf.org/rfc/rfc5480.txt\"><cite> Elliptic Curve Cryptography Subject Public Key Information.</cite></a>. IETF RFC 5480 March 2009. URL: <a href=\"http://www.ietf.org/rfc/rfc5480.txt\">http://www.ietf.org/rfc/rfc5480.txt</a>",
+ "RFC5545" : "B. Desruisseaux. <a href=\"http://www.rfc-editor.org/rfc/rfc5545.txt\"><cite>Internet Calendaring and Scheduling Core Object Specification (iCalendar).</cite></a> September 2009. Internet RFC 5545. URL: <a href=\"http://www.rfc-editor.org/rfc/rfc5545.txt\">http://www.rfc-editor.org/rfc/rfc5545.txt</a> ",
+ "RFC5646" : "A. Phillips, M. Davis. <a href=\"http://www.rfc-editor.org/rfc/rfc5646.txt\"><cite>Tags for Identifying Languages.</cite></a> September 2009. Internet RFC 5646. URL: <a href=\"http://www.rfc-editor.org/rfc/rfc5646.txt\">http://www.rfc-editor.org/rfc/rfc5646.txt</a> ",
+ "RFC5785" : "Mark Nottingham; Eran Hammer-Lahav. <a href=\"http://www.rfc-editor.org/rfc/rfc5785.txt\"><cite>Defining Well-Known Uniform Resource Identifiers (URIs).</cite></a> April 2010. Internet Proposed Standard RFC 5785. URL: <a href=\"http://www.rfc-editor.org/rfc/rfc5785.txt\">http://www.rfc-editor.org/rfc/rfc5785.txt</a> ",
+ "RichSnippets" : "<a href=\"http://googlewebmastercentral.blogspot.com/2009/05/introducing-rich-snippets.html/\"><cite>Introducing Rich Snippets.</cite></a> 12 May 2009. Google Webmaster Central Blog. URL: <a href=\"http://googlewebmastercentral.blogspot.com/2009/05/introducing-rich-snippets.html/\">http://googlewebmastercentral.blogspot.com/2009/05/introducing-rich-snippets.html/</a> ",
+ "RIF-BLD" : "Harold Boley, Michael Kifer; . <a href=\"http://www.w3.org/TR/2010/REC-rif-bld-20100622/\"><cite>RIF Basic Logic Dialect.</cite></a> 22 June 2010. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2010/REC-rif-bld-20100622/\">http://www.w3.org/TR/2010/REC-rif-bld-20100622/</a> ",
+ "RIF-CORE": "Harold Boley, et al. <a href=\"http://www.w3.org/TR/2010/REC-rif-core-20100622/\"><cite>RIF Core.</cite></a> 22 June 2010. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2010/REC-rif-core-20100622/\">http://www.w3.org/TR/2010/REC-rif-core-20100622/</a> ",
+ "RIF-DTB" : "Axel Polleres, Harold Boley, Michael Kifer. <a href=\"http://www.w3.org/TR/2010/REC-rif-dtb-20100622/\"><cite>RIF Datatypes and Built-Ins 1.0.</cite></a> 22 June 2010. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2010/REC-rif-dtb-20100622/\">http://www.w3.org/TR/2010/REC-rif-dtb-20100622/</a> ",
+ "RIF-FLD" : "Harold Boley, Michael Kifer. <a href=\"http://www.w3.org/TR/2010/REC-rif-fld-20100622/\"><cite>RIF Framework for Logic Dialects.</cite></a> 22 June 2010. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2010/REC-rif-fld-20100622/\">http://www.w3.org/TR/2010/REC-rif-fld-20100622/</a> ",
+ "RIF-PRD" : "Christian de Sainte Marie, Gary Hallmark, Adrian Paschke; . <a href=\"http://www.w3.org/TR/2010/REC-rif-prd-20100622/\"><cite>RIF Production Rule Dialect.</cite></a> 22 June 2010. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2010/REC-rif-prd-20100622/\">http://www.w3.org/TR/2010/REC-rif-prd-20100622/</a> ",
+ "RIF-RDF-OWL" : "Jos de Bruijn. <a href=\"http://www.w3.org/TR/2010/REC-rif-rdf-owl-20100622/\"><cite>RIF RDF and OWL Compatibility.</cite></a> 22 June 2010. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2010/REC-rif-rdf-owl-20100622/\">http://www.w3.org/TR/2010/REC-rif-rdf-owl-20100622/</a> ",
+ "RIF-TEST" : "Stella Mitchell, Leora Morgenstern, Adrian Paschke. <a href=\"http://www.w3.org/TR/2010/WD-rif-test-20100622/\"><cite>RIF Test Cases.</cite></a> 1 October 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2010/WD-rif-test-20100622/\">http://www.w3.org/TR/2010/WD-rif-test-20100622/</a> ",
+ "RIF-OVERVIEW" : "Michael Kifer; Harold Boley. <a href=\"http://www.w3.org/TR/2010/NOTE-rif-overview-20100622/\"><cite>RIF Overview.</cite></a> 22 June 2010. W3C Working Group Note. URL: <a href=\"http://www.w3.org/TR/2010/NOTE-rif-overview-20100622/\">http://www.w3.org/TR/2010/NOTE-rif-overview-20100622/</a> ",
+ "RIF-UCR" : "David Hirtle; et al. <a href=\"http://www.w3.org/TR/2008/WD-rif-ucr-20081218\"><cite>RIF Use Cases and Requirements.</cite></a> 18 December 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-rif-ucr-20081218\">http://www.w3.org/TR/2008/WD-rif-ucr-20081218</a> ",
+ "RIPEMD-160" : "B. Preneel, A. Bosselaers, and H. Dobbertin. <a href=\"http://www.cosic.esat.kuleuven.be/publications/article-317.pdf\"><cite>The Cryptographic Hash Function RIPEMD-160</cite></a>. CryptoBytes, Volume 3, Number 2. pp. 9-14, RSA Laboratories 1997. URL: <a href=\"http://www.cosic.esat.kuleuven.be/publications/article-317.pdf\">http://www.cosic.esat.kuleuven.be/publications/article-317.pdf</a>",
+ "RTCWEB-JSEP" : "J. Uberti, C. Jennings. <a href=\"http://datatracker.ietf.org/doc/draft-ietf-rtcweb-jsep/\"><cite>Javascript Session Establishment Protocol.</cite></a> URL: <a href=\"http://datatracker.ietf.org/doc/draft-ietf-rtcweb-jsep/\">http://datatracker.ietf.org/doc/draft-ietf-rtcweb-jsep/</a> ",
+ "RTCWEB-CONSTRAINTS" : "D. Burnett. <a href=\"http://datatracker.ietf.org/doc/draft-burnett-rtcweb-constraints-registry/\"><cite>IANA Registry for RTCWeb Media Constraints.</cite></a> URL: <a href=\"http://datatracker.ietf.org/doc/draft-burnett-rtcweb-constraints-registry/\">http://datatracker.ietf.org/doc/draft-burnett-rtcweb-constraints-registry/</a> ",
+ "RTCWEB-USECAS" : "C. Holmberg, S. Hakansson, G. Eriksson. <a href=\"http://datatracker.ietf.org/doc/draft-ietf-rtcweb-use-cases-and-requirements/\"><cite>Web Real-Time Communication Use-cases and Requirements.</cite></a> URL: <a href=\"http://datatracker.ietf.org/doc/draft-ietf-rtcweb-use-cases-and-requirements/\">http://datatracker.ietf.org/doc/draft-ietf-rtcweb-use-cases-and-requirements/</a> ",
+ "RUBY" : "Masayasu Ishikawa; et al. <a href=\"http://www.w3.org/TR/2001/REC-ruby-20010531\"><cite>Ruby Annotation.</cite></a> 31 May 2001. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2001/REC-ruby-20010531\">http://www.w3.org/TR/2001/REC-ruby-20010531</a> ",
+ "S6GROUP2" : "Stuart Weibel. <a href=\"http://www.w3.org/Search/9605-Indexing-Workshop/ReportOutcomes/S6Group2\"><cite>A Proposed Convention for Embedding Metadata in HTML.</cite></a> 2 June 1996. W3C Note. URL: <a href=\"http://www.w3.org/Search/9605-Indexing-Workshop/ReportOutcomes/S6Group2\">http://www.w3.org/Search/9605-Indexing-Workshop/ReportOutcomes/S6Group2</a> ",
+ "SAML2-CORE" : "Scott Cantor; John Kemp; Rob Philpott; Eve Maler. <a href=\"http://docs.oasis-open.org/security/saml/v2.0/saml-core-2.0-os.pdf\"><cite>Assertions and Protocols for SAML V2.0</cite></a> 15 March 2005. URL: <a href=\"http://docs.oasis-open.org/security/saml/v2.0/saml-core-2.0-os.pdf\">http://docs.oasis-open.org/security/saml/v2.0/saml-core-2.0-os.pdf</a>",
+ "SAWSDL" : "Joel Farrell; Holger Lausen. <a href=\"http://www.w3.org/TR/2007/REC-sawsdl-20070828\"><cite>Semantic Annotations for WSDL and XML Schema.</cite></a> 28 August 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-sawsdl-20070828\">http://www.w3.org/TR/2007/REC-sawsdl-20070828</a> ",
+ "SAWSDL-GUIDE" : "Rama Akkiraju; Brahmananda Sapkota. <a href=\"http://www.w3.org/TR/2007/NOTE-sawsdl-guide-20070828\"><cite>Semantic Annotations for WSDL and XML Schema — Usage Guide.</cite></a> 28 August 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-sawsdl-guide-20070828\">http://www.w3.org/TR/2007/NOTE-sawsdl-guide-20070828</a> ",
+ "SAX" : "D. Megginson, et al. <a href=\"http://www.megginson.com/downloads/SAX/\"><cite>SAX: The Simple API for XML</cite></a>. May 1998. URL: <a href=\"http://www.megginson.com/downloads/SAX/\"> http://www.megginson.com/downloads/SAX/</a>",
+ "SCHEMA-ARCH" : "Ralph R. Swick; Henry S. Thompson. <a href=\"http://www.w3.org/TR/1999/NOTE-schema-arch-19991007\"><cite>The Cambridge Communiqué.</cite></a> 7 October 1999. W3C Note. URL: <a href=\"http://www.w3.org/TR/1999/NOTE-schema-arch-19991007\">http://www.w3.org/TR/1999/NOTE-schema-arch-19991007</a> ",
+ "SCXML" : "Torbjörn Lage; et al. <a href=\"http://www.w3.org/TR/2008/WD-scxml-20080516\"><cite>State Chart XML (SCXML): State Machine Notation for Control Abstraction.</cite></a> 16 May 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-scxml-20080516\">http://www.w3.org/TR/2008/WD-scxml-20080516</a> ",
+ "SDP" : "J. Rosenberg, H. Schulzrinne. <a href=\"http://tools.ietf.org/html/rfc3264\"><cite>An Offer/Answer Model with the Session Description Protocol (SDP).</cite></a> June 2002. Internet RFC 3264. URL: <a href=\"http://tools.ietf.org/html/rfc3264\">http://tools.ietf.org/html/rfc3264</a>",
+ "SDPLABEL" : "O. Levin, G. Camarillo. <a href=\"http://tools.ietf.org/html/rfc4574\"><cite>The Session Description Protocol (SDP) Label Attribute.</cite></a> August 2006. Internet RFC 4574. URL: <a href=\"http://tools.ietf.org/html/rfc4574\">http://tools.ietf.org/html/rfc4574</a>",
+ "SECG1" : "<a href=\"http://www.secg.org/download/aid-780/sec1-v2.pdf\"><cite>SEC1: Elliptic Curve Cryptography, Version 2.0, Standards for Efficient Cryptography Group</cite></a>. May 2009. URL: <a href=\"http://www.secg.org/download/aid-780/sec1-v2.pdf\">http://www.secg.org/download/aid-780/sec1-v2.pdf</a> ",
+ "SELECT" : "Daniel Glazman; et al. <a href=\"http://www.w3.org/TR/2009/WD-css3-selectors-20090310\"><cite>Selectors Level 3.</cite></a> 10 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-css3-selectors-20090310\">http://www.w3.org/TR/2009/WD-css3-selectors-20090310</a> ",
+ "SELECTORS-API" : "Lachlan Hunt; Anne van Kesteren. <a href=\"http://www.w3.org/TR/2008/WD-selectors-api-20081114\"><cite>Selectors API.</cite></a> 14 November 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-selectors-api-20081114\">http://www.w3.org/TR/2008/WD-selectors-api-20081114</a> ",
+ "SEMANTIC-INTERPRETATION" : "David Burke; Luc Van Tichelen. <a href=\"http://www.w3.org/TR/2007/REC-semantic-interpretation-20070405\"><cite>Semantic Interpretation for Speech Recognition (SISR) Version 1.0.</cite></a> 5 April 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-semantic-interpretation-20070405\">http://www.w3.org/TR/2007/REC-semantic-interpretation-20070405</a> ",
+ "SGML-CATALOG" : "Paul Grosso. <cite><a href='http://www.oasis-open.org/html/a401.htm'>Entity Management: OASIS Technical Resolution 9401:1997 (Amendment 2 to TR 9401)</cite></a> 10 september 1007. Entity Management Subcommittee, SGML Open. URL: <a href='http://www.oasis-open.org/html/a401.htm'>http://www.oasis-open.org/html/a401.htm</a> ",
+ "SGML-XML" : "James Clark. <a href=\"http://www.w3.org/TR/NOTE-sgml-xml-971215\"><cite>Comparison of SGML and XML.</cite></a> 15 December 1997. W3C Note. URL: <a href=\"http://www.w3.org/TR/NOTE-sgml-xml-971215\">http://www.w3.org/TR/NOTE-sgml-xml-971215</a> ",
+ "SHA-1-Analysis" : "McDonald, C., Hawkes, P., and J. Pieprzyk. <a href=\"http://eurocrypt2009rump.cr.yp.to/837a0a8086fa6ca714249409ddfae43d.pdf\"><cite>SHA-1 collisions now 2<sup>52</sup> </cite></a>. EuroCrypt 2009 Rump session. URL: <a href=\"http://eurocrypt2009rump.cr.yp.to/837a0a8086fa6ca714249409ddfae43d.pdf\">http://eurocrypt2009rump.cr.yp.to/837a0a8086fa6ca714249409ddfae43d.pdf</a>",
+ "SHA-1-Collisions" : "X. Wang, Y.L. Yin, H. Yu. <a href=\"http://people.csail.mit.edu/yiqun/SHA1AttackProceedingVersion.pdf\"><cite>Finding Collisions in the Full SHA-1</cite></a>. In Shoup, V., editor, Advances in Cryptology - CRYPTO 2005, 25th Annual International Cryptology Conference, Santa Barbara, California, USA, August 14-18, 2005, Proceedings, volume 3621 of LNCS, pages 17–36. Springer, 2005. URL: <a href=\"http://people.csail.mit.edu/yiqun/SHA1AttackProceedingVersion.pdf\">http://people.csail.mit.edu/yiqun/SHA1AttackProceedingVersion.pdf</a> (also published in <a href=\"http://www.springerlink.com/content/26vljj3xhc28ux5m/\">http://www.springerlink.com/content/26vljj3xhc28ux5m/</a>)",
+ "SKOS-PRIMER" : "Antoine Isaac; Ed Summers. <a href=\"http://www.w3.org/TR/2009/NOTE-skos-primer-20090818/\"><cite>SKOS Simple Knowledge Organization System Primer.</cite></a> 18 August 2009. W3C Note. URL: <a href=\"http://www.w3.org/TR/2009/NOTE-skos-primer-20090818/\">http://www.w3.org/TR/2009/NOTE-skos-primer-20090818/</a> ",
+ "SKOS-REFERENCE" : "Sean Bechhofer; Alistair Miles. <a href=\"http://www.w3.org/TR/2009/REC-skos-reference-20090818/\"><cite>SKOS Simple Knowledge Organization System Reference.</cite></a> 18 August 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-skos-reference-20090818/\">http://www.w3.org/TR/2009/REC-skos-reference-20090818/</a> ",
+ "SKOS-UCR" : "Jon Phipps; Daniel Rubin; Antoine Isaac. <a href=\"http://www.w3.org/TR/2007/WD-skos-ucr-20070516\"><cite>SKOS Use Cases and Requirements.</cite></a> 16 May 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-skos-ucr-20070516\">http://www.w3.org/TR/2007/WD-skos-ucr-20070516</a> ",
+ "SMIL-ANIMATION" : "Patrick Schmitz; Aaron Cohen. <a href=\"http://www.w3.org/TR/2001/REC-smil-animation-20010904\"><cite>SMIL Animation.</cite></a> 4 September 2001. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2001/REC-smil-animation-20010904\">http://www.w3.org/TR/2001/REC-smil-animation-20010904</a> ",
+ "SMIL10" : "Philipp Hoschka. <a href=\"http://www.w3.org/TR/1998/REC-smil-19980615\"><cite>Synchronized Multimedia Integration Language (SMIL) 1.0 Specification.</cite></a> 15 June 1998. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/1998/REC-smil-19980615\">http://www.w3.org/TR/1998/REC-smil-19980615</a> ",
+ "SMIL2" : "Dick Bulterman; et al. <a href=\"http://www.w3.org/TR/2005/REC-SMIL2-20051213\"><cite>Synchronized Multimedia Integration Language (SMIL 2.1).</cite></a> 13 December 2005. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2005/REC-SMIL2-20051213\">http://www.w3.org/TR/2005/REC-SMIL2-20051213</a> ",
+ "SMIL20" : "Jack Jansen; et al. <a href=\"http://www.w3.org/TR/2005/REC-SMIL2-20051213\"><cite>Synchronized Multimedia Integration Language (SMIL 2.1).</cite></a> 13 December 2005. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2005/REC-SMIL2-20051213\">http://www.w3.org/TR/2005/REC-SMIL2-20051213</a> ",
+ "SMIL3" : "Dick Bulterman. <a href=\"http://www.w3.org/TR/2008/REC-SMIL3-20081201\"><cite>Synchronized Multimedia Integration Language (SMIL 3.0).</cite></a> 1 December 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-SMIL3-20081201\">http://www.w3.org/TR/2008/REC-SMIL3-20081201</a> ",
+ "SMIME" : "B. Ramsdell. <a href=\"http://www.ietf.org/rfc/rfc3851.txt\"><cite>S/MIME Version 3.1 Message Specification.</cite></a> July 2004. Internet RFC 3851. URL: <a href=\"http://www.ietf.org/rfc/rfc3851.txt\">http://www.ietf.org/rfc/rfc3851.txt</a> ",
+ "SML" : "Valentina Popescu; Virginia Smith; Bhalchandra Pandit. <a href=\"http://www.w3.org/TR/2009/PR-sml-20090212\"><cite>Service Modeling Language, Version 1.1.</cite></a> 12 February 2009. W3C Proposed Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/PR-sml-20090212\">http://www.w3.org/TR/2009/PR-sml-20090212</a> ",
+ "SML-IF" : "Valentina Popescu; Bhalchandra Pandit; Virginia Smith. <a href=\"http://www.w3.org/TR/2009/PR-sml-if-20090212\"><cite>Service Modeling Language Interchange Format Version 1.1.</cite></a> 12 February 2009. W3C Proposed Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/PR-sml-if-20090212\">http://www.w3.org/TR/2009/PR-sml-if-20090212</a> ",
+ "SOAP11-ROR-HTTPBINDING" : "David Orchard. <a href=\"http://www.w3.org/TR/2006/NOTE-soap11-ror-httpbinding-20060321\"><cite>SOAP 1.1 Request Optional Response HTTP Binding.</cite></a> 21 March 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-soap11-ror-httpbinding-20060321\">http://www.w3.org/TR/2006/NOTE-soap11-ror-httpbinding-20060321</a> ",
+ "SOAP12-AF" : "Henrik Frystyk Nielsen; Hervé Ruellan. <a href=\"http://www.w3.org/TR/2004/NOTE-soap12-af-20040608\"><cite>SOAP 1.2 Attachment Feature.</cite></a> 8 June 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-soap12-af-20040608\">http://www.w3.org/TR/2004/NOTE-soap12-af-20040608</a> ",
+ "SOAP12-EMAIL" : "Highland Mary Mountain; et al. <a href=\"http://www.w3.org/TR/2002/NOTE-soap12-email-20020703\"><cite>SOAP Version 1.2 Email Binding.</cite></a> 3 July 2002. W3C Note. URL: <a href=\"http://www.w3.org/TR/2002/NOTE-soap12-email-20020703\">http://www.w3.org/TR/2002/NOTE-soap12-email-20020703</a> ",
+ "SOAP12-MTOM" : "Mark Nottingham; et al. <a href=\"http://www.w3.org/TR/2005/REC-soap12-mtom-20050125\"><cite>SOAP Message Transmission Optimization Mechanism.</cite></a> 25 January 2005. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2005/REC-soap12-mtom-20050125\">http://www.w3.org/TR/2005/REC-soap12-mtom-20050125</a> ",
+ "SOAP12-MTOM-POLICY" : "Christopher Ferris; Yves Lafon. <a href=\"http://www.w3.org/TR/2007/WD-soap12-mtom-policy-20070918\"><cite>MTOM Serialization Policy Assertion 1.1.</cite></a> 18 September 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-soap12-mtom-policy-20070918\">http://www.w3.org/TR/2007/WD-soap12-mtom-policy-20070918</a> ",
+ "SOAP12-N11N" : "Martin Gudgin; Marc Hadley. <a href=\"http://www.w3.org/TR/2003/NOTE-soap12-n11n-20031008\"><cite>SOAP Version 1.2 Message Normalization.</cite></a> 8 October 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-soap12-n11n-20031008\">http://www.w3.org/TR/2003/NOTE-soap12-n11n-20031008</a> ",
+ "SOAP12-OS-UCR" : "Mark Jones; Tony Graham; Anish Karmarkar. <a href=\"http://www.w3.org/TR/2004/WD-soap12-os-ucr-20040608\"><cite>SOAP Optimized Serialization Use Cases and Requirements.</cite></a> 8 June 2004. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2004/WD-soap12-os-ucr-20040608\">http://www.w3.org/TR/2004/WD-soap12-os-ucr-20040608</a> ",
+ "SOAP12-PART0" : "Yves Lafon; Nilo Mitra. <a href=\"http://www.w3.org/TR/2007/REC-soap12-part0-20070427\"><cite>SOAP Version 1.2 Part 0: Primer (Second Edition).</cite></a> 27 April 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-soap12-part0-20070427\">http://www.w3.org/TR/2007/REC-soap12-part0-20070427</a> ",
+ "SOAP12-PART1" : "Noah Mendelsohn; et al. <a href=\"http://www.w3.org/TR/2007/REC-soap12-part1-20070427/\"><cite>SOAP Version 1.2 Part 1: Messaging Framework (Second Edition).</cite></a> 27 April 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-soap12-part1-20070427/\">http://www.w3.org/TR/2007/REC-soap12-part1-20070427/</a> ",
+ "SOAP12-PART2" : "Jean-Jacques Moreau; et al. <a href=\"http://www.w3.org/TR/2007/REC-soap12-part2-20070427\"><cite>SOAP Version 1.2 Part 2: Adjuncts (Second Edition).</cite></a> 27 April 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-soap12-part2-20070427\">http://www.w3.org/TR/2007/REC-soap12-part2-20070427</a> ",
+ "SOAP12-PART3" : "David Orchard. <a href=\"http://www.w3.org/TR/2007/NOTE-soap12-part3-20070702\"><cite>SOAP 1.2 Part 3: One-Way MEP.</cite></a> 2 July 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-soap12-part3-20070702\">http://www.w3.org/TR/2007/NOTE-soap12-part3-20070702</a> ",
+ "SOAP12-REP" : "Yves Lafon; Anish Karmarkar; Martin Gudgin. <a href=\"http://www.w3.org/TR/2005/REC-soap12-rep-20050125\"><cite>Resource Representation SOAP Header Block.</cite></a> 25 January 2005. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2005/REC-soap12-rep-20050125\">http://www.w3.org/TR/2005/REC-soap12-rep-20050125</a> ",
+ "SOAP12-TESTCOLLECTION" : "Hugo Haas; et al. <a href=\"http://www.w3.org/TR/2007/REC-soap12-testcollection-20070427\"><cite>SOAP Version 1.2 Specification Assertions and Test Collection (Second Edition).</cite></a> 27 April 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-soap12-testcollection-20070427\">http://www.w3.org/TR/2007/REC-soap12-testcollection-20070427</a> ",
+ "SOAPJMS" : "Bhakti Mehta; Roland Merrick; Peter Easton. <a href=\"http://www.w3.org/TR/2008/WD-soapjms-20081121\"><cite>SOAP over Java Message Service 1.0.</cite></a> 21 November 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-soapjms-20081121\">http://www.w3.org/TR/2008/WD-soapjms-20081121</a> ",
+ "SP800-38D" : "M. Dworkin. <a href=\"http://csrc.nist.gov/publications/nistpubs/800-38D/SP-800-38D.pdf\"><cite> NIST Special Publication 800-38D: Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC</cite></a>. November 2007 URL: <a href=\"http://csrc.nist.gov/publications/nistpubs/800-38D/SP-800-38D.pdf\">http://csrc.nist.gov/publications/nistpubs/800-38D/SP-800-38D.pdf</a>",
+ "SP800-56A" : "<a href=\"http://csrc.nist.gov/publications/nistpubs/800-56A/SP800-56A_Revision1_Mar08-2007.pdf\"><cite> NIST Special Publication 800-56A: Recommendation for Pair-Wise Key Establishment Schemes Using Discrete Logarithm Cryptography (Revised)</cite></a>. March 2007 URL: <a href=\"http://csrc.nist.gov/publications/nistpubs/800-56A/SP800-56A_Revision1_Mar08-2007.pdf\">http://csrc.nist.gov/publications/nistpubs/800-56A/SP800-56A_Revision1_Mar08-2007.pdf</a>",
+ "SP800-57" : "<a href=\"http://csrc.nist.gov/publications/nistpubs/800-57/sp800-57-Part1-revised2_Mar08-2007.pdf\"><cite> Recommendation for Key Management – Part 1: General (Revised).</cite></a> SP800-57. U.S. Department of Commerce/National Institute of Standards and Technology. URL: <a href=\"http://csrc.nist.gov/publications/nistpubs/800-57/sp800-57-Part1-revised2_Mar08-2007.pdf\" > http://csrc.nist.gov/publications/nistpubs/800-57/sp800-57-Part1-revised2_Mar08-2007.pdf</a>",
+ "SP800-67" : "<a href=\"http://csrc.nist.gov/publications/nistpubs/800-67-Rev1/SP-800-67-Rev1.pdf\"><cite> Recommendation for the Triple Data Encryption Algorithm (TDEA) Block Cipher, Revised January 2012.</cite></a> SP-800-67 Revision 1. U.S. Department of Commerce/National Institute of Standards and Technology. URL: <a href=\"http://csrc.nist.gov/publications/nistpubs/800-67-Rev1/SP-800-67-Rev1.pdf\">http://csrc.nist.gov/publications/nistpubs/800-67-Rev1/SP-800-67-Rev1.pdf</a>",
+ "SPEC-VARIABILITY" : "Dominique Hazaël-Massieux; Lynne Rosenthal. <a href=\"http://www.w3.org/TR/2005/NOTE-spec-variability-20050831\"><cite>Variability in Specifications.</cite></a> 31 August 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-spec-variability-20050831\">http://www.w3.org/TR/2005/NOTE-spec-variability-20050831</a> ",
+ "SPEECH-GRAMMAR" : "Andrew Hunt; Scott McGlashan. <a href=\"http://www.w3.org/TR/2004/REC-speech-grammar-20040316\"><cite>Speech Recognition Grammar Specification Version 1.0.</cite></a> 16 March 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-speech-grammar-20040316\">http://www.w3.org/TR/2004/REC-speech-grammar-20040316</a> ",
+ "SPEECH-SYNTHESIS" : "Daniel C. Burnett; Mark R. Walker; Andrew Hunt. <a href=\"http://www.w3.org/TR/2004/REC-speech-synthesis-20040907\"><cite>Speech Synthesis Markup Language (SSML) Version 1.0.</cite></a> 7 September 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-speech-synthesis-20040907\">http://www.w3.org/TR/2004/REC-speech-synthesis-20040907</a> ",
+ "SPEECH-SYNTHESIS11" : "Zhi Wei Shuang (双志伟); Daniel C. Burnett. <a href=\"http://www.w3.org/TR/2008/CR-speech-synthesis11-20081107\"><cite>Speech Synthesis Markup Language (SSML) Version 1.1.</cite></a> 7 November 2008. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/CR-speech-synthesis11-20081107\">http://www.w3.org/TR/2008/CR-speech-synthesis11-20081107</a> ",
+ "SPROT11" : "Andy Seaborne; Lee Feigenbaum; Elias Torres. <a href=\"http://www.w3.org/TR/2005/WD-sprot11-20051024\"><cite>SPARQL Protocol for RDF Using WSDL 1.1.</cite></a> 24 October 2005. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2005/WD-sprot11-20051024\">http://www.w3.org/TR/2005/WD-sprot11-20051024</a> ",
+ "SRGB" : "<a href=\"http://www.iec.ch/nr1899.htm\"><cite>Multimedia systems and equipment - Colour measurement and management - Part 2-1: Colour management - Default RGB colour space - sRGB.</cite></a> IEC 61966-2-1 (1999-10). ISBN: 2-8318-4989-6 - ICS codes: 33.160.60, 37.080 - TC 100 - 51 pp. URL: <a href=\"http://www.iec.ch/nr1899.htm\">http://www.iec.ch/nr1899.htm</a>",
+ "SSE" : "Ian Hickson; <a href=\"http://www.w3.org/TR/eventsource/\"><cite>Server-Sent Events.</cite></a>W3C Editor Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/eventsource/\">http://www.w3.org/TR/eventsource/</a> ",
+ "SSE-ed" : "Ian Hickson; <a href=\"http://dev.w3.org/html5/eventsource/\"><cite>Server-Sent Events.</cite></a>W3C Editor Draft. (Work in progress.) URL: <a href=\"http://dev.w3.org/html5/eventsource/\">http://dev.w3.org/html5/eventsource/</a> ",
+ "SSML-SAYAS" : "Daniel C. Burnett; et al. <a href=\"http://www.w3.org/TR/2005/NOTE-ssml-sayas-20050526\"><cite>SSML 1.0 say-as attribute values.</cite></a> 26 May 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-ssml-sayas-20050526\">http://www.w3.org/TR/2005/NOTE-ssml-sayas-20050526</a> ",
+ "SSML11REQS" : "Daniel C. Burnett; Zhi Wei Shuang. <a href=\"http://www.w3.org/TR/2007/WD-ssml11reqs-20070611\"><cite>Speech Synthesis Markup Language Version 1.1 Requirements.</cite></a> 11 June 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-ssml11reqs-20070611\">http://www.w3.org/TR/2007/WD-ssml11reqs-20070611</a> ",
+ "STUN" : "J. Rosenberg, R. Mahy, P. Matthews, D. Wing. <a href=\"http://tools.ietf.org/html/rfc5389\"><cite>Session Traversal Utilities for NAT (STUN).</cite></a> October 2008. Internet RFC 5389. URL: <a href=\"http://tools.ietf.org/html/rfc5389\">http://tools.ietf.org/html/rfc5389</a>",
+ "STUN-URI" : "S. Nandakumar, G. Salgueiro, P. Jones, and M. Petit-Huguenin. <a href=\"http://tools.ietf.org/html/draft-nandakumar-rtcweb-stun-uri\"><cite>URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol.</cite></a> 12 March 2012. Internet Draft (work in progress). URL: <a href=\"http://tools.ietf.org/html/draft-nandakumar-rtcweb-stun-uri\">http://tools.ietf.org/html/draft-nandakumar-rtcweb-stun-uri</a> ",
+ "SUITEB" : "<a href=\"http://www.nsa.gov/ia/programs/suiteb_cryptography/\"><cite>NSA Suite B Cryptography</cite></a>. URL: <a href=\"http://www.nsa.gov/ia/programs/suiteb_cryptography/\">http://www.nsa.gov/ia/programs/suiteb_cryptography/</a> ",
+ "SUS3" : "Cathy Hughes. <a href=\"http://www.unix.org/single_unix_specification/\"><cite>The Single UNIX Specification, Version 3</cite></a>. 2004 URL: <a href=\"http://www.unix.org/single_unix_specification/\">http://www.unix.org/single_unix_specification/</a>",
+ "SVG10" : "Jon Ferraiolo. <a href=\"http://www.w3.org/TR/2001/REC-SVG-20010904\"><cite>Scalable Vector Graphics (SVG) 1.0 Specification.</cite></a> 4 September 2001. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2001/REC-SVG-20010904\">http://www.w3.org/TR/2001/REC-SVG-20010904</a> ",
+ "SVG11" : "Erik Dahlström; et al. <a href=\"http://www.w3.org/TR/2011/REC-SVG11-20110816/\"><cite>Scalable Vector Graphics (SVG) 1.1 (Second Edition).</cite></a> 16 August 2011. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2011/REC-SVG11-20110816/\">http://www.w3.org/TR/2011/REC-SVG11-20110816/</a> ",
+ "SVG112" : "Erik Dahlström; et al. <a href=\"http://www.w3.org/TR/2010/WD-SVG11-20100622\"><cite>Scalable Vector Graphics (SVG) 1.1 (Second Edition).</cite></a> 22 June 2010. W3C Working Draft. (Work in progress). URL: <a href=\"http://www.w3.org/TR/2010/WD-SVG11-20100622\">http://www.w3.org/TR/2010/WD-SVG11-20100622</a> ",
+ "SVG12" : "Craig Northway; Dean Jackson. <a href=\"http://www.w3.org/TR/2005/WD-SVG12-20050413\"><cite>Scalable Vector Graphics (SVG) Full 1.2 Specification.</cite></a> 13 April 2005. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2005/WD-SVG12-20050413\">http://www.w3.org/TR/2005/WD-SVG12-20050413</a> ",
+ "SVG2REQS" : "Dean Jackson. <a href=\"http://www.w3.org/TR/2002/WD-SVG2Reqs-20020422\"><cite>SVG 1.1/1.2/2.0 Requirements.</cite></a> 22 April 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-SVG2Reqs-20020422\">http://www.w3.org/TR/2002/WD-SVG2Reqs-20020422</a> ",
+ "SVGFILTER12" : "Erik Dahlström. <a href=\"http://www.w3.org/TR/2007/WD-SVGFilter12-20070501\"><cite>SVG Filters 1.2, Part 2: Language.</cite></a> 1 May 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-SVGFilter12-20070501\">http://www.w3.org/TR/2007/WD-SVGFilter12-20070501</a> ",
+ "SVGFILTERPRIMER12" : "Erik Dahlström. <a href=\"http://www.w3.org/TR/2007/WD-SVGFilterPrimer12-20070501\"><cite>SVG Filters 1.2, Part 1: Primer.</cite></a> 1 May 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-SVGFilterPrimer12-20070501\">http://www.w3.org/TR/2007/WD-SVGFilterPrimer12-20070501</a> ",
+ "SVGFILTERREQS12" : "Erik Dahlström. <a href=\"http://www.w3.org/TR/2007/WD-SVGFilterReqs12-20070501\"><cite>SVG Filter Requirements.</cite></a> 1 May 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-SVGFilterReqs12-20070501\">http://www.w3.org/TR/2007/WD-SVGFilterReqs12-20070501</a> ",
+ "SVGMOBILE" : "Tolga Capin. <a href=\"http://www.w3.org/TR/2003/REC-SVGMobile-20030114\"><cite>Mobile SVG Profiles: SVG Tiny and SVG Basic.</cite></a> 14 January 2003. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2003/REC-SVGMobile-20030114\">http://www.w3.org/TR/2003/REC-SVGMobile-20030114</a> ",
+ "SVGMOBILE12" : "Chris Lilley; et al. <a href=\"http://www.w3.org/TR/2006/CR-SVGMobile12-20060810\"><cite>Scalable Vector Graphics (SVG) Tiny 1.2 Specification.</cite></a> 10 August 2006. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/CR-SVGMobile12-20060810\">http://www.w3.org/TR/2006/CR-SVGMobile12-20060810</a> ",
+ "SVGMOBILEREQS" : "Rick Graham; Tolga Capin. <a href=\"http://www.w3.org/TR/2001/WD-SVGMobileReqs-20010803\"><cite>SVG Mobile Requirements.</cite></a> 3 August 2001. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2001/WD-SVGMobileReqs-20010803\">http://www.w3.org/TR/2001/WD-SVGMobileReqs-20010803</a> ",
+ "SVGPRINT12" : "Craig Northway; et al. <a href=\"http://www.w3.org/TR/2007/WD-SVGPrint12-20071221\"><cite>SVG Print 1.2, Part 2: Language.</cite></a> 21 December 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-SVGPrint12-20071221\">http://www.w3.org/TR/2007/WD-SVGPrint12-20071221</a> ",
+ "SVGPRINTPRIMER12" : "Anthony Grasso; Chris Lilley; Andrew Shellshear. <a href=\"http://www.w3.org/TR/2007/WD-SVGPrintPrimer12-20071221\"><cite>SVG Print 1.2, Part 1: Primer.</cite></a> 21 December 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-SVGPrintPrimer12-20071221\">http://www.w3.org/TR/2007/WD-SVGPrintPrimer12-20071221</a> ",
+ "SVGPRINTREQS" : "Lee Klosterman; et al. <a href=\"http://www.w3.org/TR/2003/WD-SVGPrintReqs-20030218\"><cite>SVG Printing Requirements.</cite></a> 18 February 2003. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2003/WD-SVGPrintReqs-20030218\">http://www.w3.org/TR/2003/WD-SVGPrintReqs-20030218</a> ",
+ "SVGREQ" : "Jon Ferraiolo. <a href=\"http://www.w3.org/TR/1998/WD-SVGReq-19981029\"><cite>Scalable Vector Graphics (SVG) Requirements.</cite></a> 29 October 1998. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/1998/WD-SVGReq-19981029\">http://www.w3.org/TR/1998/WD-SVGReq-19981029</a> ",
+ "SVGTINY12" : "Scott Hayman; et al. <a href=\"http://www.w3.org/TR/2008/REC-SVGTiny12-20081222\"><cite>Scalable Vector Graphics (SVG) Tiny 1.2 Specification.</cite></a> 22 December 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-SVGTiny12-20081222\">http://www.w3.org/TR/2008/REC-SVGTiny12-20081222</a> ",
+ "SVGTINY12REQS" : "Andrew Emmons. <a href=\"http://www.w3.org/TR/2006/WD-SVGTiny12Reqs-20060810\"><cite>SVGT 1.2 Requirements.</cite></a> 10 August 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-SVGTiny12Reqs-20060810\">http://www.w3.org/TR/2006/WD-SVGTiny12Reqs-20060810</a> ",
+ "SW-OOSD-PRIMER" : "Phil Tetlow; et al. <a href=\"http://www.w3.org/TR/2006/NOTE-sw-oosd-primer-20060309\"><cite>A Semantic Web Primer for Object-Oriented Software Developers.</cite></a> 9 March 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-sw-oosd-primer-20060309\">http://www.w3.org/TR/2006/NOTE-sw-oosd-primer-20060309</a> ",
+ "SWBP-CLASSES-AS-VALUES" : "Natasha Noy. <a href=\"http://www.w3.org/TR/2005/NOTE-swbp-classes-as-values-20050405\"><cite>Representing Classes As Property Values on the Semantic Web.</cite></a> 5 April 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-swbp-classes-as-values-20050405\">http://www.w3.org/TR/2005/NOTE-swbp-classes-as-values-20050405</a> ",
+ "SWBP-N-ARYRELATIONS" : "Natasha Noy; Alan Rector. <a href=\"http://www.w3.org/TR/2006/NOTE-swbp-n-aryRelations-20060412\"><cite>Defining N-ary Relations on the Semantic Web.</cite></a> 12 April 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-swbp-n-aryRelations-20060412\">http://www.w3.org/TR/2006/NOTE-swbp-n-aryRelations-20060412</a> ",
+ "SWBP-SKOS-CORE-GUIDE" : "Alistair Miles; Dan Brickley. <a href=\"http://www.w3.org/TR/2005/WD-swbp-skos-core-guide-20051102\"><cite>SKOS Core Guide.</cite></a> 2 November 2005. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2005/WD-swbp-skos-core-guide-20051102\">http://www.w3.org/TR/2005/WD-swbp-skos-core-guide-20051102</a> ",
+ "SWBP-SKOS-CORE-SPEC" : "Alistair Miles; Dan Brickley. <a href=\"http://www.w3.org/TR/2005/WD-swbp-skos-core-spec-20051102\"><cite>SKOS Core Vocabulary Specification.</cite></a> 2 November 2005. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2005/WD-swbp-skos-core-spec-20051102\">http://www.w3.org/TR/2005/WD-swbp-skos-core-spec-20051102</a> ",
+ "SWBP-SPECIFIED-VALUES" : "Alan Rector. <a href=\"http://www.w3.org/TR/2005/NOTE-swbp-specified-values-20050517\"><cite>Representing Specified Values in OWL: "value partitions" and "value sets".</cite></a> 17 May 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-swbp-specified-values-20050517\">http://www.w3.org/TR/2005/NOTE-swbp-specified-values-20050517</a> ",
+ "SWBP-THESAURUS-PUBGUIDE" : "Alistair Miles. <a href=\"http://www.w3.org/TR/2005/WD-swbp-thesaurus-pubguide-20050517\"><cite>Quick Guide to Publishing a Thesaurus on the Semantic Web.</cite></a> 17 May 2005. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2005/WD-swbp-thesaurus-pubguide-20050517\">http://www.w3.org/TR/2005/WD-swbp-thesaurus-pubguide-20050517</a> ",
+ "SWBP-VOCAB-PUB" : "Jon Phipps; Diego Berrueta. <a href=\"http://www.w3.org/TR/2008/NOTE-swbp-vocab-pub-20080828\"><cite>Best Practice Recipes for Publishing RDF Vocabularies.</cite></a> 28 August 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-swbp-vocab-pub-20080828\">http://www.w3.org/TR/2008/NOTE-swbp-vocab-pub-20080828</a> ",
+ "SWBP-XSCH-DATATYPES" : "Jeremy J. Carroll; Jeff Z. Pan. <a href=\"http://www.w3.org/TR/2006/NOTE-swbp-xsch-datatypes-20060314\"><cite>XML Schema Datatypes in RDF and OWL.</cite></a> 14 March 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-swbp-xsch-datatypes-20060314\">http://www.w3.org/TR/2006/NOTE-swbp-xsch-datatypes-20060314</a> ",
+ "SXBL" : "Ian Hickson; Jon Ferraiolo; David Hyatt. <a href=\"http://www.w3.org/TR/2005/WD-sXBL-20050815\"><cite>SVG's XML Binding Language (sXBL).</cite></a> 15 August 2005. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2005/WD-sXBL-20050815\">http://www.w3.org/TR/2005/WD-sXBL-20050815</a> ",
+ "SXSWGRIDS" : "Khoi Vinh; Mark Boulton. <a href=\"http://www.subtraction.com/pics/0703/grids_are_good.pdf\"><cite>Grids Are Good.</cite></a> March 2007. SXSW Interactive, Austin, TX. URL: <a href=\"http://www.subtraction.com/pics/0703/grids_are_good.pdf\">http://www.subtraction.com/pics/0703/grids_are_good.pdf</a> ",
+ "SYMM-MODULES" : "Ted Wugofski; Patrick Schmitz; Warner ten Kate. <a href=\"http://www.w3.org/TR/1999/NOTE-SYMM-modules-19990223\"><cite>Synchronized Multimedia Modules based upon SMIL 1.0.</cite></a> 23 February 1999. W3C Note. URL: <a href=\"http://www.w3.org/TR/1999/NOTE-SYMM-modules-19990223\">http://www.w3.org/TR/1999/NOTE-SYMM-modules-19990223</a> ",
+ "SYSINFOAPI" : "Dzung Tran, Max Froumentin, et al. <a href=\"http://www.w3.org/TR/2010/WD-system-info-api-20100202/\"><cite>The System Information API.</cite></a> 2 February 2010. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2010/WD-system-info-api-20100202/\">http://www.w3.org/TR/2010/WD-system-info-api-20100202/</a>",
+ "HTMLMEDIACAPTURE" : "Anssi Kostiainen; Ilkka Oksanen; Dominique Hazaël-Massieux. <a href=\"http://www.w3.org/TR/2012/WD-html-media-capture-20120529/\"><cite>HTML Media Capture.</cite></a> 29 May 2012. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/WD-html-media-capture-20120529/\">http://www.w3.org/TR/2012/WD-html-media-capture-20120529/</a>",
+ "TAGLINK20030116" : "Ian Jacobs (Scribe). <a href=\"http://www.w3.org/2003/01/16-tag-xlink\"><cite>Minutes of 16 Jan 2003 discussion on Linking in XML Documents.</cite></a> 2003. W3C TAG archives. URL: <a href=\"http://www.w3.org/2003/01/16-tag-xlink\">http://www.w3.org/2003/01/16-tag-xlink</a> ",
+ "TEST-METADATA" : "Patrick Curran; Karl Dubost. <a href=\"http://www.w3.org/TR/2005/NOTE-test-metadata-20050914\"><cite>Test Metadata.</cite></a> 14 September 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-test-metadata-20050914\">http://www.w3.org/TR/2005/NOTE-test-metadata-20050914</a> ",
+ "THEGRID" : "Allen Hurlburt. <cite>Grid: A Modular System for the Design and Production of Newpapers, Magazines, and Books.</cite> Wiley. 1982. ISBN 0-471-28923-X.",
+ "TIMESHEETS" : "Pablo Cesar; Dick Bulterman; Petri Vuorimaa. <a href=\"http://www.w3.org/TR/2008/WD-timesheets-20080110\"><cite>SMIL Timesheets 1.0.</cite></a> 10 January 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-timesheets-20080110\">http://www.w3.org/TR/2008/WD-timesheets-20080110</a> ",
+ "TIMEZONE" : "Martin Dürst; et al. <a href=\"http://www.w3.org/TR/2005/NOTE-timezone-20051013\"><cite>Working with Time Zones.</cite></a> 13 October 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-timezone-20051013\">http://www.w3.org/TR/2005/NOTE-timezone-20051013</a> ",
+ "TLS" : "T. Dierks, E. Rescorla. <a href=\"http://tools.ietf.org/html/rfc5246\"><cite>The Transport Layer Security (TLS) Protocol, Version 1.2.</cite></a> August 2008. Internet RFC 5246. URL: <a href=\"http://tools.ietf.org/html/rfc5246\">http://tools.ietf.org/html/rfc5246</a>",
+ "Tobin" : "R. Tobin. <a href=\"http://lists.w3.org/Archives/Member/w3c-xml-core-wg/2000OctDec/0054\"><cite>Infoset for external entities.</cite></a> 2000. URL: <a href=\"http://lists.w3.org/Archives/Member/w3c-xml-core-wg/2000OctDec/0054\">http://lists.w3.org/Archives/Member/w3c-xml-core-wg/2000OctDec/0054</a> [XML Core mailing list, <a href=\"http://cgi.w3.org/MemberAccess/AccessRequest\">W3C Member Only</a>].",
+ "TOUCH-EVENTS": "Matt Brubeck; Sangwhan Moon; Doug Schepers; <a href=\"http://www.w3.org/TR/touch-events/\"><cite>Touch Events version 1</cite></a> URL: <a href=\"http://www.w3.org/TR/touch-events/\">http://www.w3.org/TR/touch-events</a>",
+ "TRACKING-COMPLIANCE" : "Justin Brookman; Sean Harvey; Erica Newland; Heather West. <a href=\"http://www.w3.org/TR/tracking-compliance/\"><cite>Tracking Compliance and Scope.</cite></a> 2 October 2012. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/WD-tracking-compliance-20121002/\">http://www.w3.org/TR/2012/WD-tracking-compliance-20121002/</a> ",
+ "TRACKING-DNT" : "Roy T. Fielding; David Singer. <a href=\"http://www.w3.org/TR/tracking-dnt/\"><cite>Tracking Preference Expression (DNT).</cite></a> 2 October 2012. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/WD-tracking-dnt-20121002/\">http://www.w3.org/TR/2012/WD-tracking-dnt-20121002/</a> ",
+ "TRIPLEDES" : "<a href=\"http://www.ansi.org/\"><cite>ANSI X9.52: Triple Data Encryption Algorithm Modes of Operation. 1998</cite></a>. URL: <a href=\"http://www.ansi.org/\">http://www.ansi.org/</a>",
+ "TTAF1-DFXP" : "Glenn Adams. <a href=\"http://www.w3.org/TR/2006/CR-ttaf1-dfxp-20061116\"><cite>Timed Text (TT) Authoring Format 1.0 – Distribution Format Exchange Profile (DFXP).</cite></a> 16 November 2006. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/CR-ttaf1-dfxp-20061116\">http://www.w3.org/TR/2006/CR-ttaf1-dfxp-20061116</a> ",
+ "TTAF1-REQ" : "Glenn Adams. <a href=\"http://www.w3.org/TR/2006/NOTE-ttaf1-req-20060427\"><cite>Timed Text (TT) Authoring Format 1.0 Use Cases and Requirements.</cite></a> 27 April 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-ttaf1-req-20060427\">http://www.w3.org/TR/2006/NOTE-ttaf1-req-20060427</a> ",
+ "TURINGTEST" : "Matt May. <a href=\"http://www.w3.org/TR/2005/NOTE-turingtest-20051123\"><cite>Inaccessibility of CAPTCHA.</cite></a> 23 November 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-turingtest-20051123\">http://www.w3.org/TR/2005/NOTE-turingtest-20051123</a> ",
+ "TURN" : "P. Mahy, P. Matthews, J. Rosenberg. <a href=\"http://tools.ietf.org/html/rfc5766\"><cite>Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN).</cite></a> April 2010. Internet RFC 5766. URL: <a href=\"http://tools.ietf.org/html/rfc5766\">http://tools.ietf.org/html/rfc5766</a>",
+ "TURN-URI" : "M. Petit-Huguenin, S. Nandakumar, G. Salgueiro, and P. Jones. <a href=\"http://tools.ietf.org/html/draft-petithuguenin-behave-turn-uris\"><cite>Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers.</cite></a> 12 March 2012. Internet Draft (work in progress). URL: <a href=\"http://tools.ietf.org/html/draft-petithuguenin-behave-turn-uris\">http://tools.ietf.org/html/draft-petithuguenin-behave-turn-uris</a> ",
+ "TURTLE" : "David Beckett, Tim Berners-Lee. <a href=\"http://www.w3.org/TeamSubmission/turtle/\"><cite>Turtle: Terse RDF Triple Language.</cite></a> January 2008. W3C Team Submission. URL: <a href=\"http://www.w3.org/TeamSubmission/turtle/\">http://www.w3.org/TeamSubmission/turtle/</a> ",
+ "TVWEB-URI-REQUIREMENTS" : "Gomar Thomas; Warner ten Kate; Craig Finseth. <a href=\"http://www.w3.org/TR/1999/NOTE-TVWeb-URI-Requirements-19991021\"><cite>TV Broadcast URI Schemes Requirements.</cite></a> 21 October 1999. W3C Note. URL: <a href=\"http://www.w3.org/TR/1999/NOTE-TVWeb-URI-Requirements-19991021\">http://www.w3.org/TR/1999/NOTE-TVWeb-URI-Requirements-19991021</a> ",
+ "TYPED-ARRAYS" : "David Herman, Kenneth Russell. <a href=\"https://www.khronos.org/registry/typedarray/specs/latest/\"><cite>Typed Arrays</cite></a> Khronos Working Draft. (Work in progress.) URL: <a href=\"https://www.khronos.org/registry/typedarray/specs/latest/\">https://www.khronos.org/registry/typedarray/specs/latest/</a> ",
+ "TZDB" : "<a href='http://www.twinsun.com/tz/tz-link.htm'><cite>Time Zone Information Database.</cite></a> URL: <a href='http://www.twinsun.com/tz/tz-link.htm'>http://www.twinsun.com/tz/tz-link.htm</a>",
+ "UAAG10" : "Jon Gunderson; Ian Jacobs; Eric Hansen. <a href=\"http://www.w3.org/TR/2002/REC-UAAG10-20021217\"><cite>User Agent Accessibility Guidelines 1.0.</cite></a> 17 December 2002. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2002/REC-UAAG10-20021217\">http://www.w3.org/TR/2002/REC-UAAG10-20021217</a> ",
+ "UAAG10-TECHS" : "Ian Jacobs; Jon Gunderson; Eric Hansen. <a href=\"http://www.w3.org/TR/2002/NOTE-UAAG10-TECHS-20021217\"><cite>Techniques for User Agent Accessibility Guidelines 1.0.</cite></a> 17 December 2002. W3C Note. URL: <a href=\"http://www.w3.org/TR/2002/NOTE-UAAG10-TECHS-20021217\">http://www.w3.org/TR/2002/NOTE-UAAG10-TECHS-20021217</a> ",
+ "UAAG20" : "Jan Richards; James Allan. <a href=\"http://www.w3.org/TR/2009/WD-UAAG20-20090311\"><cite>User Agent Accessibility Guidelines (UAAG) 2.0.</cite></a> 11 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-UAAG20-20090311\">http://www.w3.org/TR/2009/WD-UAAG20-20090311</a> ",
+ "UAAG20-REQUIREMENTS" : "Jim Allan; Jan Richards. <a href=\"http://www.w3.org/TR/2007/WD-UAAG20-requirements-20071031\"><cite>User Agent Accessibility Guidelines 2.0 Requirements.</cite></a> 31 October 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-UAAG20-requirements-20071031\">http://www.w3.org/TR/2007/WD-UAAG20-requirements-20071031</a> ",
+ "UAX11" : "Asmus Freytag. <a href=\"http://www.unicode.org/unicode/reports/tr11/tr11-8.html\"><cite>East Asian Width.</cite></a> 23 March 2001. Unicode Standard Annex #11. URL: <a href=\"http://www.unicode.org/unicode/reports/tr11/tr11-8.html\">http://www.unicode.org/unicode/reports/tr11/tr11-8.html</a> ",
+ "UAX14" : "Asmus Freytag. <a href=\"http://www.unicode.org/unicode/reports/tr14/tr14-17.html\"><cite>Line Breaking Properties.</cite></a> 29 March 2005. Unicode Standard Annex #14. URL: <a href=\"http://www.unicode.org/unicode/reports/tr14/tr14-17.html\">http://www.unicode.org/unicode/reports/tr14/tr14-17.html</a> ",
+ "UAX21" : "Mark Davis. <a href=\"http://www.unicode.org/reports/tr21/tr21-5.html\"><cite>Case Mappings.</cite></a> 26 March 2001. Unicode Standard Annex #21. URL: <a href=\"http://www.unicode.org/reports/tr21/tr21-5.html\">http://www.unicode.org/reports/tr21/tr21-5.html</a> ",
+ "UAX24" : "Mark Davis. <a href=\"http://www.unicode.org/unicode/reports/tr24/tr24-7.html\"><cite>Script Names.</cite></a> 28 March 2005. Unicode Standard Annex #24. URL: <a href=\"http://www.unicode.org/unicode/reports/tr24/tr24-7.html\">http://www.unicode.org/unicode/reports/tr24/tr24-7.html</a> ",
+ "UAX27" : "Mark Davis; Michael Everson; et al. <a href=\"http://www.unicode.org/unicode/reports/tr27/tr27-4.html\"><cite>Unicode 3.1.0.</cite></a> 16 May 2001. Unicode Standard Annex #27. URL: <a href=\"http://www.unicode.org/unicode/reports/tr27/tr27-4.html\">http://www.unicode.org/unicode/reports/tr27/tr27-4.html</a> ",
+ "UAX29" : "Mark Davis. <a href=\"http://www.unicode.org/unicode/reports/tr29/tr29-9.html\"><cite>Text Boundaries.</cite></a> 25 March 2005. Unicode Standard Annex #29. URL: <a href=\"http://www.unicode.org/unicode/reports/tr29/tr29-9.html\">http://www.unicode.org/unicode/reports/tr29/tr29-9.html</a> ",
+ "UNDERSTANDING-WCAG20" : "Gregg Vanderheiden; et al. <a href=\"http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211\"><cite>Understanding WCAG 2.0.</cite></a> 11 December 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211\">http://www.w3.org/TR/2008/NOTE-UNDERSTANDING-WCAG20-20081211</a> ",
+ "UNICODE" : "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> ",
+ "UNICODE-XML" : "Asmus Freytag; Martin Dürst. <a href=\"http://www.w3.org/TR/2007/NOTE-unicode-xml-20070516\"><cite>Unicode in XML and other Markup Languages.</cite></a> 16 May 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-unicode-xml-20070516\">http://www.w3.org/TR/2007/NOTE-unicode-xml-20070516</a> ",
+ "UNICODE310" : "The Unicode Consortium. <a href=\"http://www.unicode.org/unicode/standard/versions/enumeratedversions.html#Unicode_3_1_0\"><cite>The Unicode Standard: Version 3.1.0.</cite></a> Addison Wesley Longman. 2000. ISBN 0-201-61633-5. For more information, consult the Unicode Consortium's home page at <a href="http://www.unicode.org/">http://www.unicode.org/</a> URL: <a href=\"http://www.unicode.org/unicode/standard/versions/enumeratedversions.html#Unicode_3_1_0\">http://www.unicode.org/unicode/standard/versions/enumeratedversions.html#Unicode_3_1_0</a> ",
+ "UNICODE4" : "The Unicode Consortium. <a href=\"http://www.unicode.org/versions/Unicode4.1.0/\"><cite>The Unicode Standard, Version 4.1.0.</cite></a> Defined by: The Unicode Standard, Version 4.0 (Boston, MA, Addison-Wesley, 2003. ISBN 0-321-18578-1), as amended by Unicode 4.0.1 (http://www.unicode.org/versions/Unicode4.0.1) and by Unicode 4.1.0 (http://www.unicode.org/versions/Unicode4.1.0) URL: <a href=\"http://www.unicode.org/versions/Unicode4.1.0/\">http://www.unicode.org/versions/Unicode4.1.0/</a> ",
+ "UNICODE5" : "The Unicode Consortium. <a href=\"http://www.unicode.org/versions/Unicode5.1.0/\"><cite>The Unicode Standard, Version 5.1.0.</cite></a> Addison-Wesley. 2007. ISBN 0-321-48091-0. URL: <a href=\"http://www.unicode.org/versions/Unicode5.1.0/\">http://www.unicode.org/versions/Unicode5.1.0/</a> ",
+ "UPNP-AVARCH2" : "John Ritchie, Thomas Kuehnel, Wouter van der Beek, Jeffrey Kang. <a href=\"http://www.upnp.org/specs/av/UPnP-av-AVArchitecture-v2-20101231.pdf\"><cite>UPnP AV Architecture:2</cite></a>. 31 December 2010. UPnP Forum. Standardized DCP. For UPnP Version 1.0. PDF document. URL: <a href=\"http://www.upnp.org/specs/av/UPnP-av-AVArchitecture-v2-20101231.pdf\">http://www.upnp.org/specs/av/UPnP-av-AVArchitecture-v2-20101231.pdf</a>",
+ "UPNP-AVT3" : "<a href=\"http://www.upnp.org/specs/av/UPnP-av-AVTransport-v3-Service-20101231.pdf\"><cite>AVTransport:3 Service</cite></a>. 31 December 2010. UPnP Forum. Standardized DCP. For UPnP Version 1.0. PDF document. URL: <a href=\"http://www.upnp.org/specs/av/UPnP-av-AVTransport-v3-Service-20101231.pdf\">http://www.upnp.org/specs/av/UPnP-av-AVTransport-v3-Service-20101231.pdf</a>",
+ "UPNP-CD4" : "<a href=\"http://www.upnp.org/specs/av/UPnP-av-ContentDirectory-v4-Service-20101231.pdf\"><cite>ContentDirectory:4 Service</cite></a>. 31 December 2010. UPnP Forum. Standardized DCP. For UPnP Version 1.0. URL: <a href=\"http://www.upnp.org/specs/av/UPnP-av-ContentDirectory-v4-Service-20101231.pdf\">http://www.upnp.org/specs/av/UPnP-av-ContentDirectory-v4-Service-20101231.pdf</a>",
+ "UPNP-CM3" : "<a href=\"http://www.upnp.org/specs/av/UPnP-av-ConnectionManager-v3-Service-20101231.pdf\"><cite>ConnectionManager:3 Service</cite></a>. 31 December 2010. UPnP Forum. Standardized DCP. For UPnP Version 1.0. URL: <a href=\"http://www.upnp.org/specs/av/UPnP-av-ConnectionManager-v3-Service-20101231.pdf\">http://www.upnp.org/specs/av/UPnP-av-ConnectionManager-v3-Service-20101231.pdf</a>",
+ "UPNP-DEVICEARCH" : "<a href=\"http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0-20081015.pdf\"><cite>UPnP Device Architecture 1.0</cite></a>. 15 October 2008. UPnP Forum. For UPnP Version 1.0. PDF document. URL: <a href=\"http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0-20081015.pdf\">http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0-20081015.pdf</a>",
+ "UPNP-DP1" : "<a href=\"http://www.upnp.org/specs/gw/UPnP-gw-DeviceProtection-v1-Service-20110224.pdf\"><cite>DeviceProtection:1 Service</cite></a>. 24 February 2011. UPnP Forum. Standardized DCP. For UPnP Version 1.0. URL: <a href=\"http://www.upnp.org/specs/gw/UPnP-gw-DeviceProtection-v1-Service-20110224.pdf\">http://www.upnp.org/specs/gw/UPnP-gw-DeviceProtection-v1-Service-20110224.pdf</a>",
+ "UPNP-MR3" : "<a href=\"http://www.upnp.org/specs/av/UPnP-av-MediaRenderer-v3-Device-20101231.pdf\"><cite>MediaRenderer:3 Device</cite></a>. 31 December 2010. UPnP Forum. Standardized DCP. For UPnP Version 1.0. PDF document. URL: <a href=\"http://www.upnp.org/specs/av/UPnP-av-MediaRenderer-v3-Device-20101231.pdf\">http://www.upnp.org/specs/av/UPnP-av-MediaRenderer-v3-Device-20101231.pdf</a>",
+ "UPNP-MS4" : "<a href=\"http://upnp.org/specs/av/UPnP-av-MediaServer-v4-Device.pdf\"><cite>MediaServer:4 Device</cite></a>. 31 December 2010. UPnP Forum. Standardized DCP. For UPnP Version 1.0. PDF document. URL: <a href=\"http://upnp.org/specs/av/UPnP-av-MediaServer-v4-Device.pdf\">http://upnp.org/specs/av/UPnP-av-MediaServer-v4-Device.pdf</a>",
+ "UPNP-RC3" : "<a href=\"http://www.upnp.org/specs/av/UPnP-av-RenderingControl-v3-Service-20101231.pdf\"><cite>RenderingControl:3 Service</cite></a>. 31 December 2010. UPnP Forum. Standardized DCP. For UPnP Version 1.0. PDF document. URL: <a href=\"http://www.upnp.org/specs/av/UPnP-av-RenderingControl-v3-Service-20101231.pdf\">http://www.upnp.org/specs/av/UPnP-av-RenderingControl-v3-Service-20101231.pdf</a>",
+ "UPNP-SR2" : "<a href=\"http://www.upnp.org/specs/av/UPnP-av-ScheduledRecording-v2-Service-20101231.pdf\"><cite>ScheduledRecording:2 Service</cite></a>. 31 December 2010. UPnP Forum. Standardized DCP. For UPnP Version 1.0. URL: <a href=\"http://www.upnp.org/specs/av/UPnP-av-ScheduledRecording-v2-Service-20101231.pdf\">http://www.upnp.org/specs/av/UPnP-av-ScheduledRecording-v2-Service-20101231.pdf</a>",
+ "URI" : "T. Berners-Lee; R. Fielding; L. Masinter. <a href=\"http://www.ietf.org/rfc/rfc3986.txt\"><cite>Uniform Resource Identifiers (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> ",
+ "URI-CLARIFICATION" : "URI Planning Interest Group. <a href=\"http://www.w3.org/TR/2001/NOTE-uri-clarification-20010921\"><cite>URIs, URLs, and URNs: Clarifications and Recommendations 1.0.</cite></a> 21 September 2001. W3C Note. URL: <a href=\"http://www.w3.org/TR/2001/NOTE-uri-clarification-20010921\">http://www.w3.org/TR/2001/NOTE-uri-clarification-20010921</a> ",
+ "URI-TEMPLATE" : "Joe Gregorio; Roy T. Fielding; Marc Hadley; Mark Nottingham; David Orchard. <a href=\"http://www.rfc-editor.org/rfc/rfc6570.txt\"><cite>URI Template.</cite></a> March 2012. Internet RFC 6570. URL: <a href=\"http://www.rfc-editor.org/rfc/rfc6570.txt\">http://www.rfc-editor.org/rfc/rfc6570.txt</a> ",
+ "URN" : "R. Moats. <a href=\"http://www.ietf.org/rfc/rfc2141.txt\"><cite>URN Syntax.</cite></a> IETF RFC 2141. May 1997. URL: <a href=\"http://www.ietf.org/rfc/rfc2141.txt\">http://www.ietf.org/rfc/rfc2141.txt</a>",
+ "URN-OID" : "M. Mealling. <a href=\"http://www.ietf.org/rfc/rfc3061.txt\"><cite>A URN Namespace of Object Identifiers. </cite></a>. IETF RFC 3061. February 2001. URL: <a href=\"http://www.ietf.org/rfc/rfc3061.txt\">http://www.ietf.org/rfc/rfc3061.txt</a>",
+ "UTF-8" : "F. Yergeau. <a href=\"http://www.ietf.org/rfc/rfc3629.txt\"><cite>UTF-8, a transformation format of ISO 10646</cite></a>. IETF RFC 3629. November 2003. URL: <a href=\"http://www.ietf.org/rfc/rfc3629.txt\">http://www.ietf.org/rfc/rfc3629.txt</a>",
+ "UTF-16" : "P. Hoffman , F. Yergeau. <a href=\"http://www.ietf.org/rfc/rfc2781.txt\"><cite>UTF-16, an encoding of ISO 10646.</cite></a> IETF RFC 2781. February 2000. URL: <a href=\"http://www.ietf.org/rfc/rfc2781.txt\">http://www.ietf.org/rfc/rfc2781.txt</a>",
+ "UTR24" : "Mark Davis. <a href=\"http://www.unicode.org/unicode/reports/tr24/tr24-3.html\"><cite>Script Names.</cite></a> 27 September 2001. Unicode Technical Report #24. URL: <a href=\"http://www.unicode.org/unicode/reports/tr24/tr24-3.html\">http://www.unicode.org/unicode/reports/tr24/tr24-3.html</a> ",
+ "VBI-REQS" : "Kenneth G. Rehor. <a href=\"http://www.w3.org/TR/2002/WD-vbi-reqs-20020808\"><cite>Voice Browser Interoperation: Requirements.</cite></a> 8 August 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-vbi-reqs-20020808\">http://www.w3.org/TR/2002/WD-vbi-reqs-20020808</a> ",
+ "VOICE" : "David Raggett; Or Ben-Nattan. <a href=\"http://www.w3.org/TR/1998/NOTE-voice-0128\"><cite>Voice Browsers.</cite></a> 28 January 1998. W3C Note. URL: <a href=\"http://www.w3.org/TR/1998/NOTE-voice-0128\">http://www.w3.org/TR/1998/NOTE-voice-0128</a> ",
+ "VOICE-ARCHITECTURE" : "Michael K. Brown; D. A. Dahl. <a href=\"http://www.w3.org/TR/1999/WD-voice-architecture-19991223\"><cite>Model Architecture for Voice Browser Systems.</cite></a> 23 December 1999. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/1999/WD-voice-architecture-19991223\">http://www.w3.org/TR/1999/WD-voice-architecture-19991223</a> ",
+ "VOICE-DIALOG-REQS" : "Scott McGlashan. <a href=\"http://www.w3.org/TR/1999/WD-voice-dialog-reqs-19991223\"><cite>Dialog Requirements for Voice Markup Languages.</cite></a> 23 December 1999. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/1999/WD-voice-dialog-reqs-19991223\">http://www.w3.org/TR/1999/WD-voice-dialog-reqs-19991223</a> ",
+ "VOICE-GRAMMAR-REQS" : "Michael K. Brown. <a href=\"http://www.w3.org/TR/1999/WD-voice-grammar-reqs-19991223\"><cite>Grammar Representation Requirements for Voice Markup Languages.</cite></a> 23 December 1999. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/1999/WD-voice-grammar-reqs-19991223\">http://www.w3.org/TR/1999/WD-voice-grammar-reqs-19991223</a> ",
+ "VOICE-INTRO" : "Jim Larson. <a href=\"http://www.w3.org/TR/2000/WD-voice-intro-20001204\"><cite>Voice Browsers, Introduction.</cite></a> 4 December 2000. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2000/WD-voice-intro-20001204\">http://www.w3.org/TR/2000/WD-voice-intro-20001204</a> ",
+ "VOICE-NLU-REQS" : "Deborah Dahl. <a href=\"http://www.w3.org/TR/1999/WD-voice-nlu-reqs-19991223\"><cite>Natural Language Processing Requirements for Voice Markup Languages.</cite></a> 23 December 1999. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/1999/WD-voice-nlu-reqs-19991223\">http://www.w3.org/TR/1999/WD-voice-nlu-reqs-19991223</a> ",
+ "VOICE-TTS-REQS" : "Andrew Hunt. <a href=\"http://www.w3.org/TR/1999/WD-voice-tts-reqs-19991223\"><cite>Speech Synthesis Markup Requirements for Voice Markup Languages.</cite></a> 23 December 1999. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/1999/WD-voice-tts-reqs-19991223\">http://www.w3.org/TR/1999/WD-voice-tts-reqs-19991223</a> ",
+ "VOICEXML20" : "Brad Porter; et al. <a href=\"http://www.w3.org/TR/2004/REC-voicexml20-20040316\"><cite>Voice Extensible Markup Language (VoiceXML) Version 2.0.</cite></a> 16 March 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-voicexml20-20040316\">http://www.w3.org/TR/2004/REC-voicexml20-20040316</a> ",
+ "VOICEXML21" : "Scott McGlashan; et al. <a href=\"http://www.w3.org/TR/2007/REC-voicexml21-20070619\"><cite>Voice Extensible Markup Language (VoiceXML) 2.1.</cite></a> 19 June 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-voicexml21-20070619\">http://www.w3.org/TR/2007/REC-voicexml21-20070619</a> ",
+ "VOICEXML30" : "Paolo Baggia; et al. <a href=\"http://www.w3.org/TR/2008/WD-voicexml30-20081219\"><cite>Voice Extensible Markup Language (VoiceXML) 3.0.</cite></a> 19 December 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-voicexml30-20081219\">http://www.w3.org/TR/2008/WD-voicexml30-20081219</a> ",
+ "VXML30REQS" : "Emily Candell; Jeff Hoepfinger. <a href=\"http://www.w3.org/TR/2008/WD-vxml30reqs-20080808\"><cite>Voice Extensible Markup Language (VoiceXML) 3.0 Requirements.</cite></a> 8 August 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-vxml30reqs-20080808\">http://www.w3.org/TR/2008/WD-vxml30reqs-20080808</a> ",
+ "WAC-ORIENTATION-API" : "WAC Application Services Ltd. <a href=\"http://specs.wacapps.net/2.0/jun2011/deviceapis/orientation.html\"><cite>Device APIs: The orientation module</cite></a> 28 January 2011. WAC 2.0 Proposed Release Version (PRV) URL: <a href=\"http://specs.wacapps.net/2.0/jun2011/deviceapis/orientation.html\">http://specs.wacapps.net/2.0/jun2011/deviceapis/orientation.html</a> ",
+ "WAC-SENSOR-API" : "WAC Application Services Ltd. <a href=\"http://specs.wacapps.net/2.0/jun2011/deviceapis/sensors.html\"><cite>Device APIs: The sensor module</cite></a> July 2011. WAC Ipanema Editor's Draft. URL: <a href=\"http://specs.wacapps.net/2.0/jun2011/deviceapis/sensors.html\">http://specs.wacapps.net/2.0/jun2011/deviceapis/sensors.html</a> ",
+ "WAI-AGE-LITERATURE" : "Andrew Arch. <a href=\"http://www.w3.org/TR/2008/WD-wai-age-literature-20080514\"><cite>Web Accessibility for Older Users: A Literature Review.</cite></a> 14 May 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-wai-age-literature-20080514\">http://www.w3.org/TR/2008/WD-wai-age-literature-20080514</a> ",
+ "WAI-ARIA" : "Lisa Pappas; et al. <a href=\"http://www.w3.org/TR/2009/WD-wai-aria-20090224\"><cite>Accessible Rich Internet Applications (WAI-ARIA) 1.0.</cite></a> 24 February 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-wai-aria-20090224\">http://www.w3.org/TR/2009/WD-wai-aria-20090224</a> ",
+ "WAI-ARIA-IMPLEMENTATION" : "Michael Cooper; Aaron Leventhal. <a href=\"http://www.w3.org/TR/2009/WD-wai-aria-implementation-20090224\"><cite>WAI-ARIA 1.0 User Agent Implementation Guide.</cite></a> 24 February 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-wai-aria-implementation-20090224\">http://www.w3.org/TR/2009/WD-wai-aria-implementation-20090224</a> ",
+ "WAI-ARIA-PRACTICES" : "Michael Cooper; Richard Schwerdtfeger; Lisa Pappas. <a href=\"http://www.w3.org/TR/2009/WD-wai-aria-practices-20090224\"><cite>WAI-ARIA Best Practices.</cite></a> 24 February 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-wai-aria-practices-20090224\">http://www.w3.org/TR/2009/WD-wai-aria-practices-20090224</a> ",
+ "WAI-ARIA-PRIMER" : "Richard Schwerdtfeger; Michael Cooper; Lisa Pappas. <a href=\"http://www.w3.org/TR/2008/WD-wai-aria-primer-20080204\"><cite>WAI-ARIA Primer.</cite></a> 4 February 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-wai-aria-primer-20080204\">http://www.w3.org/TR/2008/WD-wai-aria-primer-20080204</a> ",
+ "WAI-ARIA-ROADMAP" : "Richard Schwerdtfeger. <a href=\"http://www.w3.org/TR/2008/WD-wai-aria-roadmap-20080204\"><cite>Roadmap for Accessible Rich Internet Applications (WAI-ARIA Roadmap).</cite></a> 4 February 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-wai-aria-roadmap-20080204\">http://www.w3.org/TR/2008/WD-wai-aria-roadmap-20080204</a> ",
+ "WCA" : "Johan Hjelm; Jim Pitkow; Henrik Frystyk Nielsen. <a href=\"http://www.w3.org/TR/1999/NOTE-WCA-19990319\"><cite>Web Characterization: From working group to activity.</cite></a> 19 March 1999. W3C Note. URL: <a href=\"http://www.w3.org/TR/1999/NOTE-WCA-19990319\">http://www.w3.org/TR/1999/NOTE-WCA-19990319</a> ",
+ "WCAG" : "Wendy Chisholm; Gregg Vanderheiden; Ian Jacobs. <a href=\"http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505\"><cite>Web Content Accessibility Guidelines 1.0.</cite></a> 5 May 1999. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505\">http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505</a> ",
+ "WCAG10-CORE-TECHS" : "Gregg Vanderheiden; Ian Jacobs; Wendy Chisholm. <a href=\"http://www.w3.org/TR/2000/NOTE-WCAG10-CORE-TECHS-20001106\"><cite>Core Techniques for Web Content Accessibility Guidelines 1.0.</cite></a> 6 November 2000. W3C Note. URL: <a href=\"http://www.w3.org/TR/2000/NOTE-WCAG10-CORE-TECHS-20001106\">http://www.w3.org/TR/2000/NOTE-WCAG10-CORE-TECHS-20001106</a> ",
+ "WCAG10-CSS-TECHS" : "Gregg Vanderheiden; Ian Jacobs; Wendy Chisholm. <a href=\"http://www.w3.org/TR/2000/NOTE-WCAG10-CSS-TECHS-20001106\"><cite>CSS Techniques for Web Content Accessibility Guidelines 1.0.</cite></a> 6 November 2000. W3C Note. URL: <a href=\"http://www.w3.org/TR/2000/NOTE-WCAG10-CSS-TECHS-20001106\">http://www.w3.org/TR/2000/NOTE-WCAG10-CSS-TECHS-20001106</a> ",
+ "WCAG10-HTML-TECHS" : "Wendy Chisholm; Gregg Vanderheiden; Ian Jacobs. <a href=\"http://www.w3.org/TR/2000/NOTE-WCAG10-HTML-TECHS-20001106\"><cite>HTML Techniques for Web Content Accessibility Guidelines 1.0.</cite></a> 6 November 2000. W3C Note. URL: <a href=\"http://www.w3.org/TR/2000/NOTE-WCAG10-HTML-TECHS-20001106\">http://www.w3.org/TR/2000/NOTE-WCAG10-HTML-TECHS-20001106</a> ",
+ "WCAG10-TECHS" : "Gregg Vanderheiden; Ian Jacobs; Wendy Chisholm. <a href=\"http://www.w3.org/TR/2000/NOTE-WCAG10-TECHS-20001106\"><cite>Techniques for Web Content Accessibility Guidelines 1.0.</cite></a> 6 November 2000. W3C Note. URL: <a href=\"http://www.w3.org/TR/2000/NOTE-WCAG10-TECHS-20001106\">http://www.w3.org/TR/2000/NOTE-WCAG10-TECHS-20001106</a> ",
+ "WCAG2-REQ" : "Gregg Vanderheiden; Wendy Chisholm; John Slatin. <a href=\"http://www.w3.org/TR/2006/NOTE-wcag2-req-20060425\"><cite>Requirements for WCAG 2.0.</cite></a> 25 April 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-wcag2-req-20060425\">http://www.w3.org/TR/2006/NOTE-wcag2-req-20060425</a> ",
+ "WCAG2-TECH-REQ" : "Michael Cooper. <a href=\"http://www.w3.org/TR/2003/WD-wcag2-tech-req-20030207\"><cite>Requirements for WCAG 2.0 Checklists and Techniques.</cite></a> 7 February 2003. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2003/WD-wcag2-tech-req-20030207\">http://www.w3.org/TR/2003/WD-wcag2-tech-req-20030207</a> ",
+ "WCAG20" : "Michael Cooper; et al. <a href=\"http://www.w3.org/TR/2008/REC-WCAG20-20081211\"><cite>Web Content Accessibility Guidelines (WCAG) 2.0.</cite></a> 11 December 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-WCAG20-20081211\">http://www.w3.org/TR/2008/REC-WCAG20-20081211</a> ",
+ "WCAG20-TECHS" : "Michael Cooper; et al. <a href=\"http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211\"><cite>Techniques for WCAG 2.0.</cite></a> 11 December 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211\">http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211</a> ",
+ "WCSS11" : "Open Mobile Alliance. <a href=\"http://www.openmobilealliance.org/technical/release_program/docs/Browsing/V2_3-20080331-A/OMA-WAP-WCSS-V1_1-20061020-A.pdf\"><cite>Wireless CSS Specification.</cite></a> October 2006. Approved Version 1.1. URL: <a href=\"http://www.openmobilealliance.org/technical/release_program/docs/Browsing/V2_3-20080331-A/OMA-WAP-WCSS-V1_1-20061020-A.pdf\">http://www.openmobilealliance.org/technical/release_program/docs/Browsing/V2_3-20080331-A/OMA-WAP-WCSS-V1_1-20061020-A.pdf</a> ",
+ "WCSS12" : "Open Mobile Alliance. <a href=\"http://www.openmobilealliance.org/ftp/Public_documents/MCE/MAE/Permanent_documents/OMA-TS-WCSS-V1_2-20070921-D.zip\"><cite>Wireless CSS Specification Version 1.2.</cite></a> 21 September 2007. (Work in progress.) URL: <a href=\"http://www.openmobilealliance.org/ftp/Public_documents/MCE/MAE/Permanent_documents/OMA-TS-WCSS-V1_2-20070921-D.zip\">http://www.openmobilealliance.org/ftp/Public_documents/MCE/MAE/Permanent_documents/OMA-TS-WCSS-V1_2-20070921-D.zip</a> ",
+ "WEB-FORMS-2" : "Ian Hickson. <a href=\"http://www.w3.org/TR/2006/WD-web-forms-2-20060821\"><cite>Web Forms 2.0.</cite></a> 21 August 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-web-forms-2-20060821\">http://www.w3.org/TR/2006/WD-web-forms-2-20060821</a> ",
+ "WEBARCH" : "Norman Walsh; Ian Jacobs. <a href=\"http://www.w3.org/TR/2004/REC-webarch-20041215/\"><cite>Architecture of the World Wide Web, Volume One.</cite></a> 15 December 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-webarch-20041215/\">http://www.w3.org/TR/2004/REC-webarch-20041215/</a> ",
+ "WEBCGM" : "Lofton Henderson; et al. <a href=\"http://www.w3.org/TR/2001/REC-WebCGM-20011217\"><cite>WebCGM 1.0 Second Release.</cite></a> 17 December 2001. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2001/REC-WebCGM-20011217\">http://www.w3.org/TR/2001/REC-WebCGM-20011217</a> ",
+ "WEBCGM20" : "Benoit Bezaire; Lofton Henderson; David Cruikshank. <a href=\"http://www.w3.org/TR/2007/REC-webcgm20-20070130\"><cite>WebCGM 2.0.</cite></a> 30 January 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-webcgm20-20070130\">http://www.w3.org/TR/2007/REC-webcgm20-20070130</a> ",
+ "WEBCGM21" : "Lofton Henderson; Benoit Bezaire. <a href=\"http://www.w3.org/TR/2009/WD-webcgm21-20090130\"><cite>WebCGM 2.1.</cite></a> 30 January 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-webcgm21-20090130\">http://www.w3.org/TR/2009/WD-webcgm21-20090130</a> ",
+ "WEBIDL" : "Cameron McCormack. <a href=\"http://www.w3.org/TR/2011/WD-WebIDL-20110927/\"><cite>Web IDL.</cite></a> 27 September 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-WebIDL-20110927/\">http://www.w3.org/TR/2011/WD-WebIDL-20110927/</a> ",
+ "WEBONT-REQ" : "Jeff Heflin. <a href=\"http://www.w3.org/TR/2004/REC-webont-req-20040210\"><cite>OWL Web Ontology Language Use Cases and Requirements.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-webont-req-20040210\">http://www.w3.org/TR/2004/REC-webont-req-20040210</a> ",
+ "WebBug-Wikipedia" : "<a href=\"http://en.wikipedia.org/wiki/Web_bug\"><cite>Wikipedia Web Bug definition</cite></a> URL: <a href=\"http://en.wikipedia.org/wiki/Web_bug\"> http://en.wikipedia.org/wiki/Web_bug</a> ",
+ "WEBRTC10" : "A Bergkvist; D Burnett; C Jennings; A Narayanan. <a href=\"http://www.w3.org/TR/2011/WD-webrtc-20111027/\"><cite>WebRTC 1.0.</cite></a> 27 October 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-webrtc-20111027/\">http://www.w3.org/TR/2011/WD-webrtc-20111027/</a> ",
+ "WEBSOCKETS-API" : "I. Hickson. <a href=\"http://www.w3.org/TR/2011/WD-websockets-20110929/\"><cite>The WebSocket API.</cite></a> 29 September 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-websockets-20110929/\">http://www.w3.org/TR/2011/WD-websockets-20110929/</a> ",
+ "WEBSOCKETS-PROTOCOL" : "C. Holmberg, S. Hakansson, G. Eriksson. <a href=\"http://tools.ietf.org/id/draft-ietf-hybi-thewebsocketprotocol-09.txt\"><cite>The WebSocket protocol.</cite></a> URL: <a href=\"http://tools.ietf.org/id/draft-ietf-hybi-thewebsocketprotocol-09.txt\">http://tools.ietf.org/id/draft-ietf-hybi-thewebsocketprotocol-09.txt</a> ",
+ "WEBSTORAGE" : "Ian Hickson. <a href=\"http://www.w3.org/TR/2009/WD-webstorage-20090910/\"><cite>Web Storage.</cite></a> 10 September 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-webstorage-20090910/\">http://www.w3.org/TR/2009/WD-webstorage-20090910/</a> ",
+ "WEBVTT" : "Ian Hickson. <a href=\"http://dev.w3.org/html5/webvtt/\"><cite>WebVTT.</cite></a> 21 August 2012. W3C Working Draft. (Work in progress.) URL: <a href=\"http://dev.w3.org/html5/webvtt/\">http://dev.w3.org/html5/webvtt/</a> ",
+ "WEBWORKERS" : "Ian Hickson. <a href=\"http://www.w3.org/TR/2011/WD-workers-20110901/\"><cite>Web Workers.</cite></a> 1 September 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-workers-20110901/\">http://www.w3.org/TR/2011/WD-workers-20110901/</a> ",
+ "WICD" : "Daniel Appelquist; et al. <a href=\"http://www.w3.org/TR/2007/CR-WICD-20070718\"><cite>WICD Core 1.0.</cite></a> 18 July 2007. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/CR-WICD-20070718\">http://www.w3.org/TR/2007/CR-WICD-20070718</a> ",
+ "WICDFULL" : "Timur Mehrvarz; et al. <a href=\"http://www.w3.org/TR/2007/CR-WICDFull-20070718\"><cite>WICD Full 1.0.</cite></a> 18 July 2007. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/CR-WICDFull-20070718\">http://www.w3.org/TR/2007/CR-WICDFull-20070718</a> ",
+ "WICDMobile10" : "Timur Mehrvarz; et al. <a href=\"http://www.w3.org/TR/2007/CR-WICDMobile-20070718\"><cite>WICD Mobile 1.0.</cite></a> 18 July 2007. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/CR-WICDMobile-20070718\">http://www.w3.org/TR/2007/CR-WICDMobile-20070718</a> ",
+ "WIDGETS" : "Marcos Cáceres. <a href=\"http://www.w3.org/TR/widgets/\"><cite>Widget Packaging and XML Configuration</cite></a>. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/widgets/\">http://www.w3.org/TR/widgets/</a> ",
+ "WIDGETS-APIS" : "Marcos Cáceres <a href=\"http://www.w3.org/TR/widgets-api/\"><cite>Widget Interface.</cite></a> W3C Proposed Recommendation. URL: <a href=\"http://www.w3.org/TR/widgets-api/\">http://www.w3.org/TR/widgets-api/</a> ",
+ "WIDGETS-DIGSIG" : "M. Cáceres; P. Bayers; Stuart Knightley; F. Hirsch; M Priestley. <a href=\"http://www.w3.org/TR/widgets-digsig\"><cite>Digital Signatures for Widgets.</cite></a> (Work in progress.) URL: <a href=\"http://www.w3.org/TR/widgets-digsig\">http://www.w3.org/TR/2010/CR-widgets-digsig-20100624</a> ",
+ "WIDGETS-LAND" : "Marcos Cáceres. <a href=\"http://www.w3.org/TR/2008/WD-widgets-land-20080414\"><cite>The Widget Landscape (Q1 2008).</cite></a> 14 April 2008. W3C Working Group Note. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-widgets-land-20080414\">http://www.w3.org/TR/2008/WD-widgets-land-20080414</a> ",
+ "WIDGETS-PC-TESTS" : "Marcos Cáceres <a href=\"http://dev.w3.org/2006/waf/widgets/test-suite/\"><cite>Test Suite for Packaging and XML Configuration.</cite></a> W3C Test Suite. URL: <a href=\"http://dev.w3.org/2006/waf/widgets/test-suite/\">http://dev.w3.org/2006/waf/widgets/test-suite/</a> ",
+ "WIDGETS-PC-INTEROP" : "Marcos Cáceres <a href=\"http://dev.w3.org/2006/waf/widgets/imp-report/\"><cite>Implementation Report for Widgets Packaging and XML Configuration.</cite></a>. URL: <a href=\"http://dev.w3.org/2006/waf/widgets/imp-report/\">http://dev.w3.org/2006/waf/widgets/imp-report/</a> ",
+ "WIDGETS-REQS" : "Marcos Cáceres. <a href=\"http://www.w3.org/TR/widgets-reqs/\"><cite> Requirements For Standardizing Widgets.</cite></a>. W3C Working Group Note. URL: <a href=\"http://www.w3.org/TR/widgets-reqs/\">http://www.w3.org/TR/widgets-reqs/</a> ",
+ "WIDGETS-UPDATES" : "Marcos Cáceres. <a href=\"http://www.w3.org/TR/2008/WD-widgets-updates-20081007\"><cite>Widget Updates.</cite></a> 7 October 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-widgets-updates-20081007\">http://www.w3.org/TR/2008/WD-widgets-updates-20081007</a> ",
+ "WIDGETS-URI" : "Marcos Cáceres. <a href=\"http://www.w3.org/TR/2011/WD-widgets-uri-20110927\"><cite>Widget URI Scheme.</cite></a>. W3C Note. URL: <a href=\"http://www.w3.org/TR/2011/WD-widgets-uri-20110927\">http://www.w3.org/TR/2011/WD-widgets-uri-20110927</a> ",
+ "WINDOW" : "Ian Davis; Maciej Stachowiak. <a href=\"http://www.w3.org/TR/2006/WD-Window-20060407\"><cite>Window Object 1.0.</cite></a> 7 April 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-Window-20060407\">http://www.w3.org/TR/2006/WD-Window-20060407</a> ",
+ "WORDNET-RDF" : "Aldo Gangemi; Guus Schreiber; Mark van Assem. <a href=\"http://www.w3.org/TR/2006/WD-wordnet-rdf-20060619\"><cite>RDF/OWL Representation of WordNet.</cite></a> 19 June 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-wordnet-rdf-20060619\">http://www.w3.org/TR/2006/WD-wordnet-rdf-20060619</a> ",
+ "WS-ADDR-CORE" : "Martin Gudgin; Marc Hadley; Tony Rogers. <a href=\"http://www.w3.org/TR/2006/REC-ws-addr-core-20060509\"><cite>Web Services Addressing 1.0 - Core.</cite></a> 9 May 2006. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2006/REC-ws-addr-core-20060509\">http://www.w3.org/TR/2006/REC-ws-addr-core-20060509</a> ",
+ "WS-ADDR-METADATA" : "Martin Gudgin; et al. <a href=\"http://www.w3.org/TR/2007/REC-ws-addr-metadata-20070904\"><cite>Web Services Addressing 1.0 - Metadata.</cite></a> 4 September 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-ws-addr-metadata-20070904\">http://www.w3.org/TR/2007/REC-ws-addr-metadata-20070904</a> ",
+ "WS-ADDR-SOAP" : "Tony Rogers; et al. <a href=\"http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509\"><cite>Web Services Addressing 1.0 - SOAP Binding.</cite></a> 9 May 2006. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509\">http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509</a> ",
+ "WS-ARCH" : "Francis McCabe; et al. <a href=\"http://www.w3.org/TR/2004/NOTE-ws-arch-20040211\"><cite>Web Services Architecture.</cite></a> 11 February 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-ws-arch-20040211\">http://www.w3.org/TR/2004/NOTE-ws-arch-20040211</a> ",
+ "WS-ARCH-SCENARIOS" : "David Orchard; Hugo Haas; Hao He. <a href=\"http://www.w3.org/TR/2004/NOTE-ws-arch-scenarios-20040211\"><cite>Web Services Architecture Usage Scenarios.</cite></a> 11 February 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-ws-arch-scenarios-20040211\">http://www.w3.org/TR/2004/NOTE-ws-arch-scenarios-20040211</a> ",
+ "WS-CDL-10" : "Yves Lafon; et al. <a href=\"http://www.w3.org/TR/2005/CR-ws-cdl-10-20051109\"><cite>Web Services Choreography Description Language Version 1.0.</cite></a> 9 November 2005. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2005/CR-ws-cdl-10-20051109\">http://www.w3.org/TR/2005/CR-ws-cdl-10-20051109</a> ",
+ "WS-CDL-10-PRIMER" : "Steve Ross-Talbot; Tony Fletcher. <a href=\"http://www.w3.org/TR/2006/WD-ws-cdl-10-primer-20060619\"><cite>Web Services Choreography Description Language: Primer.</cite></a> 19 June 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-ws-cdl-10-primer-20060619\">http://www.w3.org/TR/2006/WD-ws-cdl-10-primer-20060619</a> ",
+ "WS-CHOR-MODEL" : "David Burdett; Nickolas Kavantzas. <a href=\"http://www.w3.org/TR/2004/WD-ws-chor-model-20040324\"><cite>WS Choreography Model Overview.</cite></a> 24 March 2004. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2004/WD-ws-chor-model-20040324\">http://www.w3.org/TR/2004/WD-ws-chor-model-20040324</a> ",
+ "WS-CHOR-REQS" : "Ed Peters; et al. <a href=\"http://www.w3.org/TR/2004/WD-ws-chor-reqs-20040311\"><cite>Web Services Choreography Requirements.</cite></a> 11 March 2004. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2004/WD-ws-chor-reqs-20040311\">http://www.w3.org/TR/2004/WD-ws-chor-reqs-20040311</a> ",
+ "WS-DESC-REQS" : "Jeffrey C. Schlimmer. <a href=\"http://www.w3.org/TR/2002/WD-ws-desc-reqs-20021028\"><cite>Web Services Description Requirements.</cite></a> 28 October 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-ws-desc-reqs-20021028\">http://www.w3.org/TR/2002/WD-ws-desc-reqs-20021028</a> ",
+ "WS-DESC-USECASES" : "Waqar Sadiq; Sandeep Kumar. <a href=\"http://www.w3.org/TR/2002/WD-ws-desc-usecases-20020604\"><cite>Web Service Description Usage Scenarios.</cite></a> 4 June 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-ws-desc-usecases-20020604\">http://www.w3.org/TR/2002/WD-ws-desc-usecases-20020604</a> ",
+ "WS-ENUMERATION" : "Ashok Malhotra; et al. <a href=\"http://www.w3.org/TR/2009/WD-ws-enumeration-20090317\"><cite>Web Services Enumeration (WS-Enumeration).</cite></a> 17 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-ws-enumeration-20090317\">http://www.w3.org/TR/2009/WD-ws-enumeration-20090317</a> ",
+ "WS-EVENTING" : "Ashok Malhotra; et al. <a href=\"http://www.w3.org/TR/2009/WD-ws-eventing-20090317\"><cite>Web Services Eventing (WS-Eventing).</cite></a> 17 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-ws-eventing-20090317\">http://www.w3.org/TR/2009/WD-ws-eventing-20090317</a> ",
+ "WS-FRAGMENT" : "D. Davis; A. Malhotra; K. Warr; W. Chou. <a href=\"http://www.w3.org/TR/2010/WD-ws-fragment-20100330\"><cite>Web Services Fragment (WS-Fragment).</cite></a> 30 March 2010. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2010/WD-ws-fragment-20100330\">http://www.w3.org/TR/2010/WD-ws-fragment-20100330</a> ",
+ "WS-GLOSS" : "Hugo Haas; Allen Brown. <a href=\"http://www.w3.org/TR/2004/NOTE-ws-gloss-20040211\"><cite>Web Services Glossary.</cite></a> 11 February 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-ws-gloss-20040211\">http://www.w3.org/TR/2004/NOTE-ws-gloss-20040211</a> ",
+ "WS-I18N" : "Mary Trumble; Addison Phillips; Felix Sasaki. <a href=\"http://www.w3.org/TR/2008/WD-ws-i18n-20080415\"><cite>Web Services Internationalization (WS-I18N).</cite></a> 15 April 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-ws-i18n-20080415\">http://www.w3.org/TR/2008/WD-ws-i18n-20080415</a> ",
+ "WS-I18N-REQ" : "Addison Phillips. <a href=\"http://www.w3.org/TR/2004/NOTE-ws-i18n-req-20041116\"><cite>Requirements for the Internationalization of Web Services.</cite></a> 16 November 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-ws-i18n-req-20041116\">http://www.w3.org/TR/2004/NOTE-ws-i18n-req-20041116</a> ",
+ "WS-I18N-SCENARIOS" : "Takao Suzuki; et al. <a href=\"http://www.w3.org/TR/2004/NOTE-ws-i18n-scenarios-20040730\"><cite>Web Services Internationalization Usage Scenarios.</cite></a> 30 July 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-ws-i18n-scenarios-20040730\">http://www.w3.org/TR/2004/NOTE-ws-i18n-scenarios-20040730</a> ",
+ "WS-METADATA-EXCHANGE" : "Katy Warr; et al. <a href=\"http://www.w3.org/TR/2009/WD-ws-metadata-exchange-20090317\"><cite>Web Services Metadata Exchange (WS-MetadataExchange).</cite></a> 17 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-ws-metadata-exchange-20090317\">http://www.w3.org/TR/2009/WD-ws-metadata-exchange-20090317</a> ",
+ "WS-POLICY" : "Ümit Yalçinalp; et al. <a href=\"http://www.w3.org/TR/2007/REC-ws-policy-20070904\"><cite>Web Services Policy 1.5 - Framework.</cite></a> 4 September 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-ws-policy-20070904\">http://www.w3.org/TR/2007/REC-ws-policy-20070904</a> ",
+ "WS-POLICY-ATTACH" : "Ümit Yalçinalp; et al. <a href=\"http://www.w3.org/TR/2007/REC-ws-policy-attach-20070904\"><cite>Web Services Policy 1.5 - Attachment.</cite></a> 4 September 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-ws-policy-attach-20070904\">http://www.w3.org/TR/2007/REC-ws-policy-attach-20070904</a> ",
+ "WS-POLICY-GUIDELINES" : "Maryann Hondo; et al. <a href=\"http://www.w3.org/TR/2007/NOTE-ws-policy-guidelines-20071112\"><cite>Web Services Policy 1.5 - Guidelines for Policy Assertion Authors.</cite></a> 12 November 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-ws-policy-guidelines-20071112\">http://www.w3.org/TR/2007/NOTE-ws-policy-guidelines-20071112</a> ",
+ "WS-POLICY-PRIMER" : "Asir S Vedamuthu; et al. <a href=\"http://www.w3.org/TR/2007/NOTE-ws-policy-primer-20071112\"><cite>Web Services Policy 1.5 - Primer.</cite></a> 12 November 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-ws-policy-primer-20071112\">http://www.w3.org/TR/2007/NOTE-ws-policy-primer-20071112</a> ",
+ "WS-RESOURCE-TRANSFER" : "Ashok Malhotra; et al. <a href=\"http://www.w3.org/TR/2009/WD-ws-resource-transfer-20090317\"><cite>Web Services Resource Transfer (WS-RT).</cite></a> 17 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-ws-resource-transfer-20090317\">http://www.w3.org/TR/2009/WD-ws-resource-transfer-20090317</a> ",
+ "WS-SECURITY11" : "A. Nadalin, C. Kaler, R. Monzillo, P. Hallam-Baker. <a href=\"https://www.oasis-open.org/standards#wssv1.1\"><cite>Web Services Security: SOAP Message Security 1.1 (WS-Security 2004)</cite></a>. OASIS Standard, 1 February 2006. URL: <a href=\"https://www.oasis-open.org/standards#wssv1.1\">https://www.oasis-open.org/standards#wssv1.1</a> ",
+ "WS-SECURECONVERSATION13" : "A. Nadalin, M. Goodner, M. Gudgin, A. Barbir, H. Granqvist. <a href=\"https://www.oasis-open.org/standards#wssecconv1.3\"><cite>WS-SecureConversation 1.3</cite></a>. OASIS Standard, 1 March 2007. URL: <a href=\"https://www.oasis-open.org/standards#wssecconv1.3\">https://www.oasis-open.org/standards#wssecconv1.3</a> ",
+ "WS-SECURITYPOLICY12" : "A. Nadalin, M. Goodner, M. Gudgin, A. Barbir, H. Granqvist. <a href=\"https://www.oasis-open.org/standards#wssecpolv1.2\"><cite>WS-SecurityPolicy 1.2, OASIS Standard</cite></a>. 1 July 2007. URL: <a href=\"https://www.oasis-open.org/standards#wssecpolv1.2\">https://www.oasis-open.org/standards#wssecpolv1.2</a> ",
+ "WS-TRANSFER" : "Ashok Malhotra; et al. <a href=\"http://www.w3.org/TR/2009/WD-ws-transfer-20090317\"><cite>Web Services Transfer (WS-Transfer).</cite></a> 17 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-ws-transfer-20090317\">http://www.w3.org/TR/2009/WD-ws-transfer-20090317</a> ",
+ "WS-TRUST13" : "A. Nadalin, M. Goodner, M. Gudgin, A. Barbir, H. Granqvist. <a href=\"https://www.oasis-open.org/standards#wstrustv1.3\"><cite>WS-Trust 1.3</cite></a>. OASIS Standard, 19 March 2007. URL: <a href=\"https://www.oasis-open.org/standards#wstrustv1.3\">https://www.oasis-open.org/standards#wstrustv1.3</a> ",
+ "WSS-USERNAME11" : "A. Nadalin, C. Kaler, R. Monzillo, P. Hallam-Baker. <a href=\"http://www.oasis-open.org/committees/download.php/16782/wss-v1.1-spec-os-UsernameTokenProfile.pdf\"><cite>Web Services Security UsernameToken Profile 1.1</cite></a>. OASIS Standard Specification, 1 February 2006. URL: <a href=\"http://www.oasis-open.org/committees/download.php/16782/wss-v1.1-spec-os-UsernameTokenProfile.pdf\">http://www.oasis-open.org/committees/download.php/16782/wss-v1.1-spec-os-UsernameTokenProfile.pdf</a> ",
+ "WSA-REQS" : "Sharad Garg; et al. <a href=\"http://www.w3.org/TR/2004/NOTE-wsa-reqs-20040211\"><cite>Web Services Architecture Requirements.</cite></a> 11 February 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-wsa-reqs-20040211\">http://www.w3.org/TR/2004/NOTE-wsa-reqs-20040211</a> ",
+ "WSC-THREATS" : "Thomas Roessler. <a href=\"http://www.w3.org/TR/2007/NOTE-wsc-threats-20071101\"><cite>Web User Interaction: Threat Trees.</cite></a> 1 November 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-wsc-threats-20071101\">http://www.w3.org/TR/2007/NOTE-wsc-threats-20071101</a> ",
+ "WSC-UI" : "Anil Saldhana; Thomas Roessler. <a href=\"http://www.w3.org/TR/2009/WD-wsc-ui-20090226\"><cite>Web Security Context: User Interface Guidelines.</cite></a> 26 February 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-wsc-ui-20090226\">http://www.w3.org/TR/2009/WD-wsc-ui-20090226</a> ",
+ "WSC-USECASES" : "Tyler Close. <a href=\"http://www.w3.org/TR/2008/NOTE-wsc-usecases-20080306\"><cite>Web Security Experience, Indicators and Trust: Scope and Use Cases.</cite></a> 6 March 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-wsc-usecases-20080306\">http://www.w3.org/TR/2008/NOTE-wsc-usecases-20080306</a> ",
+ "WSC-XIT" : "Anil Saldhana; Thomas Roessler. <a href=\"http://www.w3.org/TR/2008/WD-wsc-xit-20080403\"><cite>Web Security Context: Experience, Indicators, and Trust.</cite></a> 3 April 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-wsc-xit-20080403\">http://www.w3.org/TR/2008/WD-wsc-xit-20080403</a> ",
+ "WSDL11ELEMENTIDENTIFIERS" : "Asir S. Vedamuthu; et al. <a href=\"http://www.w3.org/TR/2007/NOTE-wsdl11elementidentifiers-20070720\"><cite>WSDL 1.1 Element Identifiers.</cite></a> 20 July 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-wsdl11elementidentifiers-20070720\">http://www.w3.org/TR/2007/NOTE-wsdl11elementidentifiers-20070720</a> ",
+ "WSDL20" : "Sanjiva Weerawarana; et al. <a href=\"http://www.w3.org/TR/2007/REC-wsdl20-20070626\"><cite>Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language.</cite></a> 26 June 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-wsdl20-20070626\">http://www.w3.org/TR/2007/REC-wsdl20-20070626</a> ",
+ "WSDL20-ADDITIONAL-MEPS" : "Amelia A. Lewis. <a href=\"http://www.w3.org/TR/2007/NOTE-wsdl20-additional-meps-20070626\"><cite>Web Services Description Language (WSDL) Version 2.0: Additional MEPs.</cite></a> 26 June 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-wsdl20-additional-meps-20070626\">http://www.w3.org/TR/2007/NOTE-wsdl20-additional-meps-20070626</a> ",
+ "WSDL20-ADJUNCTS" : "Amelia A. Lewis; et al. <a href=\"http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626\"><cite>Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts.</cite></a> 26 June 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626\">http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626</a> ",
+ "WSDL20-ALTSCHEMALANGS" : "Amelia A. Lewis; Bijan Parsia. <a href=\"http://www.w3.org/TR/2005/NOTE-wsdl20-altschemalangs-20050817\"><cite>Discussion of Alternative Schema Languages and Type System Support in WSDL 2.0.</cite></a> 17 August 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-wsdl20-altschemalangs-20050817\">http://www.w3.org/TR/2005/NOTE-wsdl20-altschemalangs-20050817</a> ",
+ "WSDL20-PRIMER" : "David Booth; Canyang Kevin Liu. <a href=\"http://www.w3.org/TR/2007/REC-wsdl20-primer-20070626\"><cite>Web Services Description Language (WSDL) Version 2.0 Part 0: Primer.</cite></a> 26 June 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-wsdl20-primer-20070626\">http://www.w3.org/TR/2007/REC-wsdl20-primer-20070626</a> ",
+ "WSDL20-RDF" : "Jacek Kopecky. <a href=\"http://www.w3.org/TR/2007/NOTE-wsdl20-rdf-20070626\"><cite>Web Services Description Language (WSDL) Version 2.0: RDF Mapping.</cite></a> 26 June 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-wsdl20-rdf-20070626\">http://www.w3.org/TR/2007/NOTE-wsdl20-rdf-20070626</a> ",
+ "WSDL20-SOAP11-BINDING" : "Asir S. Vedamuthu. <a href=\"http://www.w3.org/TR/2007/NOTE-wsdl20-soap11-binding-20070626\"><cite>Web Services Description Language (WSDL) Version 2.0 SOAP 1.1 Binding.</cite></a> 26 June 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-wsdl20-soap11-binding-20070626\">http://www.w3.org/TR/2007/NOTE-wsdl20-soap11-binding-20070626</a> ",
+ "WSI-BSP10" : "M. McIntosh, M. Gudgin, K. S. Morrison, A. Barbir. <a href=\"http://www.ws-i.org/Profiles/BasicSecurityProfile-1.0.html\"><cite>Basic Security Profile Version 1.0</cite></a>. WS-I Final Material, 30 March 2007. URL: <a href=\"http://www.ws-i.org/Profiles/BasicSecurityProfile-1.0.html\">http://www.ws-i.org/Profiles/BasicSecurityProfile-1.0.html</a> ",
+ "WSLC" : "Hao He; Igor Sedukhin; Mark Potts. <a href=\"http://www.w3.org/TR/2004/NOTE-wslc-20040211\"><cite>Web Service Management: Service Life Cycle.</cite></a> 11 February 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-wslc-20040211\">http://www.w3.org/TR/2004/NOTE-wslc-20040211</a> ",
+ "X11COLORS" : "Robert B. Hess. <a href=\"http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwebgen/html/X11_names.asp\"><cite>Colors By Name.</cite></a> MSDN Online Web Workshop. 02 November 1996. URL: <a href=\"http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwebgen/html/X11_names.asp\">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwebgen/html/X11_names.asp</a> ",
+ "X509V3" : "<cite>ITU-T Recommendation X.509 version 3 (1997). \"Information Technology - Open Systems Interconnection - The Directory Authentication Framework\" ISO/IEC 9594-8:1997</cite>.",
+ "XACML20" : "Tim Moses. <a href=\"http://docs.oasis-open.org/xacml/2.0/access_control-xacml-2.0-core-spec-os.pdf\"><cite>OASIS eXtensible Access Control Markup Language (XACML) Version 2.0</cite></a>. 01 Feb 2005 URL: <a href=\"http://docs.oasis-open.org/xacml/2.0/access_control-xacml-2.0-core-spec-os.pdf\">http://docs.oasis-open.org/xacml/2.0/access_control-xacml-2.0-core-spec-os.pdf</a>",
+ "XACML-INTRO" : "<a href=\"http://www.oasis-open.org/committees/download.php/2713/Brief_Introduction_to_XACML.html\"><cite>A Brief Introduction to XACML</cite></a>. 14 March 2003. URL: <a href=\"http://www.oasis-open.org/committees/download.php/2713/Brief_Introduction_to_XACML.html\"> http://www.oasis-open.org/committees/download.php/2713/Brief_Introduction_to_XACML.html</a>",
+ "XADES" : "<a href=\"http://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.01_60/ts_101903v010401p.pdf\"><cite>XML Advanced Electronic Signatures (XAdES)</cite></a>. ETSI TS 101 903 V1.4.1 (2009-06) URL: <a href=\"http://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.01_60/ts_101903v010401p.pdf\">http://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.01_60/ts_101903v010401p.pdf</a>",
+ "XAG" : "Charles McCathieNevile; Sean B. Palmer; Daniel Dardailler. <a href=\"http://www.w3.org/TR/2002/WD-xag-20021003\"><cite>XML Accessibility Guidelines.</cite></a> 3 October 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-xag-20021003\">http://www.w3.org/TR/2002/WD-xag-20021003</a> ",
+ "XBC-CHARACTERIZATION" : "Dmitry Lenkov; Oliver Goldman. <a href=\"http://www.w3.org/TR/2005/NOTE-xbc-characterization-20050331\"><cite>XML Binary Characterization.</cite></a> 31 March 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-xbc-characterization-20050331\">http://www.w3.org/TR/2005/NOTE-xbc-characterization-20050331</a> ",
+ "XBC-MEASUREMENT" : "Peter Haggar; Stephen D. Williams. <a href=\"http://www.w3.org/TR/2005/NOTE-xbc-measurement-20050331\"><cite>XML Binary Characterization Measurement Methodologies.</cite></a> 31 March 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-xbc-measurement-20050331\">http://www.w3.org/TR/2005/NOTE-xbc-measurement-20050331</a> ",
+ "XBC-PROPERTIES" : "Santiago Pericas-Geertsen; Mike Cokus. <a href=\"http://www.w3.org/TR/2005/NOTE-xbc-properties-20050331\"><cite>XML Binary Characterization Properties.</cite></a> 31 March 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-xbc-properties-20050331\">http://www.w3.org/TR/2005/NOTE-xbc-properties-20050331</a> ",
+ "XBC-USE-CASES" : "Santiago Pericas-Geertsen; Mike Cokus. <a href=\"http://www.w3.org/TR/2005/NOTE-xbc-use-cases-20050331\"><cite>XML Binary Characterization Use Cases.</cite></a> 31 March 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-xbc-use-cases-20050331\">http://www.w3.org/TR/2005/NOTE-xbc-use-cases-20050331</a> ",
+ "XBL" : "Ian Hickson. <a href=\"http://www.w3.org/TR/2007/CR-xbl-20070316\"><cite>XML Binding Language (XBL) 2.0.</cite></a> 16 March 2007. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/CR-xbl-20070316\">http://www.w3.org/TR/2007/CR-xbl-20070316</a> ",
+ "XBL-PRIMER" : "Lachlan Hunt; Marcos Cáceres. <a href=\"http://www.w3.org/TR/2007/WD-xbl-primer-20070718\"><cite>XBL 2.0 Primer: An Introduction for Developers.</cite></a> 18 July 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-xbl-primer-20070718\">http://www.w3.org/TR/2007/WD-xbl-primer-20070718</a> ",
+ "XFORMS-11-REQ" : "John Boyer; Roland Merrick. <a href=\"http://www.w3.org/TR/2004/NOTE-xforms-11-req-20040831\"><cite>XForms 1.1 Requirements.</cite></a> 31 August 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-xforms-11-req-20040831\">http://www.w3.org/TR/2004/NOTE-xforms-11-req-20040831</a> ",
+ "XFORMS-BASIC" : "T. V. Raman; Micah Dubinko. <a href=\"http://www.w3.org/TR/2003/CR-xforms-basic-20031014\"><cite>XForms 1.0 Basic Profile.</cite></a> 14 October 2003. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2003/CR-xforms-basic-20031014\">http://www.w3.org/TR/2003/CR-xforms-basic-20031014</a> ",
+ "XFORMS-FOR-HTML" : "John M. Boyer. <a href=\"http://www.w3.org/TR/2008/WD-XForms-for-HTML-20081219\"><cite>XForms for HTML.</cite></a> 19 December 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-XForms-for-HTML-20081219\">http://www.w3.org/TR/2008/WD-XForms-for-HTML-20081219</a> ",
+ "XFORMS10" : "John M. Boyer. <a href=\"http://www.w3.org/TR/2007/REC-xforms-20071029\"><cite>XForms 1.0 (Third Edition).</cite></a> 29 October 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-xforms-20071029\">http://www.w3.org/TR/2007/REC-xforms-20071029</a> ",
+ "XFORMS11" : "John M. Boyer. <a href=\"http://www.w3.org/TR/2007/CR-xforms11-20071129\"><cite>XForms 1.1.</cite></a> 29 November 2007. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/CR-xforms11-20071129\">http://www.w3.org/TR/2007/CR-xforms11-20071129</a> ",
+ "XFRAMES" : "Steven Pemberton; Masayasu Ishikawa. <a href=\"http://www.w3.org/TR/2005/WD-xframes-20051012\"><cite>XFrames.</cite></a> 12 October 2005. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2005/WD-xframes-20051012\">http://www.w3.org/TR/2005/WD-xframes-20051012</a> ",
+ "XH" : "Dan Connolly; Lauren Wood. <a href=\"http://www.w3.org/TR/1998/NOTE-xh-19980511\"><cite>XML in HTML Meeting Report.</cite></a> 11 May 1998. W3C Note. URL: <a href=\"http://www.w3.org/TR/1998/NOTE-xh-19980511\">http://www.w3.org/TR/1998/NOTE-xh-19980511</a> ",
+ "XHTML-ACCESS" : "T. V. Raman; et al. <a href=\"http://www.w3.org/TR/2008/WD-xhtml-access-20080526\"><cite>XHTML Access Module.</cite></a> 26 May 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xhtml-access-20080526\">http://www.w3.org/TR/2008/WD-xhtml-access-20080526</a> ",
+ "XHTML-BASIC" : "Mark Baker; et al. <a href=\"http://www.w3.org/TR/2000/REC-xhtml-basic-20001219\"><cite>XHTML™ Basic.</cite></a> 19 December 2000. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2000/REC-xhtml-basic-20001219\">http://www.w3.org/TR/2000/REC-xhtml-basic-20001219</a> ",
+ "XHTML-BASIC11" : "Mark Baker; et al. <a href=\"http://www.w3.org/TR/2008/REC-xhtml-basic-20080729\"><cite>XHTML™ Basic 1.1.</cite></a> 29 July 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-xhtml-basic-20080729\">http://www.w3.org/TR/2008/REC-xhtml-basic-20080729</a> ",
+ "XHTML-FORMS-REQ" : "Malte Wedel; et al. <a href=\"http://www.w3.org/TR/2001/WD-xhtml-forms-req-20010404\"><cite>XForms Requirements.</cite></a> 4 April 2001. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2001/WD-xhtml-forms-req-20010404\">http://www.w3.org/TR/2001/WD-xhtml-forms-req-20010404</a> ",
+ "XHTML-MEDIA-TYPES" : "Shane McCarron. <a href=\"http://www.w3.org/TR/2009/NOTE-xhtml-media-types-20090116\"><cite>XHTML Media Types - Second Edition.</cite></a> 16 January 2009. W3C Note. URL: <a href=\"http://www.w3.org/TR/2009/NOTE-xhtml-media-types-20090116\">http://www.w3.org/TR/2009/NOTE-xhtml-media-types-20090116</a> ",
+ "XHTML-MODULARIZATION" : "Shane McCarron; et al. <a href=\"http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218\"><cite>Modularization of XHTML™ 1.0 - Second Edition.</cite></a> 18 February 2004. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218\">http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218</a> ",
+ "XHTML-MODULARIZATION11" : "Shane McCarron; et al. <a href=\"http://www.w3.org/TR/2008/REC-xhtml-modularization-20081008\"><cite>XHTML™ Modularization 1.1.</cite></a> 8 October 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-xhtml-modularization-20081008\">http://www.w3.org/TR/2008/REC-xhtml-modularization-20081008</a> ",
+ "XHTML-MODULARIZATION11-2e" : "Shane McCarron. <a href=\"http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729\"><cite>XHTML™ Modularization 1.1 Second Edition.</cite></a> 29 July 2010. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729\">http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729</a> ",
+ "XHTML-PRINT" : "Jim Bigelow; Melinda Grant. <a href=\"http://www.w3.org/TR/2006/REC-xhtml-print-20060920\"><cite>XHTML-Print.</cite></a> 20 September 2006. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2006/REC-xhtml-print-20060920\">http://www.w3.org/TR/2006/REC-xhtml-print-20060920</a> ",
+ "XHTML-PROF-REQ" : "David Raggett; Ted Wugofski; Peter Stark. <a href=\"http://www.w3.org/TR/1999/WD-xhtml-prof-req-19990906\"><cite>XHTML™ Document Profile Requirements.</cite></a> 6 September 1999. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/1999/WD-xhtml-prof-req-19990906\">http://www.w3.org/TR/1999/WD-xhtml-prof-req-19990906</a> ",
+ "XHTML-RDFA" : "Shane McCarron; et. al. <a href=\"http://www.w3.org/TR/2012/REC-xhtml-rdfa-20120607/\"><cite>XHTML+RDFa 1.1.</cite></a> 7 June 2012. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2012/REC-xhtml-rdfa-20120607/\">http://www.w3.org/TR/2012/REC-xhtml-rdfa-20120607/</a> ",
+ "XHTML-RDFA-PRIMER" : "Mark Birbeck; Ben Adida. <a href=\"http://www.w3.org/TR/2008/NOTE-xhtml-rdfa-primer-20081014\"><cite>RDFa Primer.</cite></a> 14 October 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-xhtml-rdfa-primer-20081014\">http://www.w3.org/TR/2008/NOTE-xhtml-rdfa-primer-20081014</a> ",
+ "XHTML-RDFA-SCENARIOS" : "Michael Hausenblas; Ben Adida. <a href=\"http://www.w3.org/TR/2007/WD-xhtml-rdfa-scenarios-20070330\"><cite>RDFa Use Cases: Scenarios for Embedding RDF in HTML.</cite></a> 30 March 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-xhtml-rdfa-scenarios-20070330\">http://www.w3.org/TR/2007/WD-xhtml-rdfa-scenarios-20070330</a> ",
+ "XHTML-ROADMAP" : "Steven Pemberton; David Raggett; Masayasu Ishikawa. <a href=\"http://www.w3.org/TR/2000/NOTE-xhtml-roadmap-20001108\"><cite>HTML Working Group Roadmap.</cite></a> 8 November 2000. W3C Note. URL: <a href=\"http://www.w3.org/TR/2000/NOTE-xhtml-roadmap-20001108\">http://www.w3.org/TR/2000/NOTE-xhtml-roadmap-20001108</a> ",
+ "XHTML-ROLE" : "Shane McCarron; et al. <a href=\"http://www.w3.org/TR/2008/WD-xhtml-role-20080407\"><cite>XHTML Role Attribute Module.</cite></a> 7 April 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xhtml-role-20080407\">http://www.w3.org/TR/2008/WD-xhtml-role-20080407</a> ",
+ "XHTML-VOCAB" : "XHTML 2 Working Group. <a href=\"http://www.w3.org/1999/xhtml/vocab\"><cite>XHTML Vocabulary</cite></a>. URL: <a href='http://www.w3.org/1999/xhtml/vocab'>http://www.w3.org/1999/xhtml/vocab</a> ",
+ "XHTML1-SCHEMA" : "Masayasu Ishikawa. <a href=\"http://www.w3.org/TR/2002/NOTE-xhtml1-schema-20020902\"><cite>XHTML 1.0 in XML Schema.</cite></a> 2 September 2002. W3C Note. URL: <a href=\"http://www.w3.org/TR/2002/NOTE-xhtml1-schema-20020902\">http://www.w3.org/TR/2002/NOTE-xhtml1-schema-20020902</a> ",
+ "XHTML10" : "Steven Pemberton. <a href=\"http://www.w3.org/TR/2002/REC-xhtml1-20020801/\"><cite>XHTML™ 1.0 The Extensible HyperText Markup Language (Second Edition).</cite></a> 1 August 2002. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2002/REC-xhtml1-20020801/\">http://www.w3.org/TR/2002/REC-xhtml1-20020801/</a> ",
+ "XHTML11" : "Murray Altheim; Shane McCarron. <a href=\"http://www.w3.org/TR/2001/REC-xhtml11-20010531\"><cite>XHTML™ 1.1 - Module-based XHTML.</cite></a> 31 May 2001. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2001/REC-xhtml11-20010531\">http://www.w3.org/TR/2001/REC-xhtml11-20010531</a> ",
+ "XHTML11-2e" : "Masayasu Ishikawa; Shane McCarron. <a href=\"http://www.w3.org/TR/2007/WD-xhtml11-20070216\"><cite>XHTML™ 1.1 - Module-based XHTML - Second Edition.</cite></a> 16 February 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-xhtml11-20070216\">http://www.w3.org/TR/2007/WD-xhtml11-20070216</a> ",
+ "XHTML2" : "Micah Dubinko; et al. <a href=\"http://www.w3.org/TR/2006/WD-xhtml2-20060726\"><cite>XHTML™ 2.0.</cite></a> 26 July 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-xhtml2-20060726\">http://www.w3.org/TR/2006/WD-xhtml2-20060726</a> ",
+ "XHTMLPLUSMATHMLPLUSSVG" : "Masayasu Ishikawa. <a href=\"http://www.w3.org/TR/2002/WD-XHTMLplusMathMLplusSVG-20020809\"><cite>An XHTML + MathML + SVG Profile.</cite></a> 9 August 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-XHTMLplusMathMLplusSVG-20020809\">http://www.w3.org/TR/2002/WD-XHTMLplusMathMLplusSVG-20020809</a> ",
+ "XHTMLPLUSSMIL" : "Aaron Patterson; Patrick Schmitz; Debbie Newman. <a href=\"http://www.w3.org/TR/2002/NOTE-XHTMLplusSMIL-20020131\"><cite>XHTML+SMIL Profile.</cite></a> 31 January 2002. W3C Note. URL: <a href=\"http://www.w3.org/TR/2002/NOTE-XHTMLplusSMIL-20020131\">http://www.w3.org/TR/2002/NOTE-XHTMLplusSMIL-20020131</a> ",
+ "XINCLUDE" : "Jonathan Marsh; David Orchard; Daniel Veillard. <a href=\"http://www.w3.org/TR/2006/REC-xinclude-20061115\"><cite>XML Inclusions (XInclude) Version 1.0 (Second Edition).</cite></a> 15 November 2006. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2006/REC-xinclude-20061115\">http://www.w3.org/TR/2006/REC-xinclude-20061115</a> ",
+ "XKMS-PGP" : "Tommy Lindberg; José Kahan. <a href=\"http://www.w3.org/TR/2005/NOTE-xkms-pgp-20051219\"><cite>Using XKMS with PGP.</cite></a> 19 December 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-xkms-pgp-20051219\">http://www.w3.org/TR/2005/NOTE-xkms-pgp-20051219</a> ",
+ "XKMS-WSDL" : "Rich Salz; Yunhao Zhang. <a href=\"http://www.w3.org/TR/2005/NOTE-xkms-wsdl-20051118\"><cite>A WSDL 1.1 description for XKMS.</cite></a> 18 November 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-xkms-wsdl-20051118\">http://www.w3.org/TR/2005/NOTE-xkms-wsdl-20051118</a> ",
+ "XKMS2" : "Shivaram H. Mysore; Phillip Hallam-Baker. <a href=\"http://www.w3.org/TR/2005/REC-xkms2-20050628/\"><cite>XML Key Management Specification (XKMS 2.0).</cite></a> 28 June 2005. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2005/REC-xkms2-20050628/\">http://www.w3.org/TR/2005/REC-xkms2-20050628/</a> ",
+ "XKMS2-BINDINGS" : "Shivaram H. Mysore; Phillip Hallam-Baker. <a href=\"http://www.w3.org/TR/2005/REC-xkms2-bindings-20050628\"><cite>XML Key Management Specification (XKMS 2.0) Bindings.</cite></a> 28 June 2005. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2005/REC-xkms2-bindings-20050628\">http://www.w3.org/TR/2005/REC-xkms2-bindings-20050628</a> ",
+ "XKMS2-REQ" : "Frederick Hirsch; Mike Just. <a href=\"http://www.w3.org/TR/2003/NOTE-xkms2-req-20030505\"><cite>XML Key Management (XKMS 2.0) Requirements.</cite></a> 5 May 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-xkms2-req-20030505\">http://www.w3.org/TR/2003/NOTE-xkms2-req-20030505</a> ",
+ "XLINK-PRINCIPLES" : "Eve Maler; Steven DeRose. <a href=\"http://www.w3.org/TR/1998/NOTE-xlink-principles-19980303\"><cite>XML Linking Language (XLink) Design Principles.</cite></a> 3 March 1998. W3C Note. URL: <a href=\"http://www.w3.org/TR/1998/NOTE-xlink-principles-19980303\">http://www.w3.org/TR/1998/NOTE-xlink-principles-19980303</a> ",
+ "XLINK-REQ" : "Steven J. DeRose. <a href=\"http://www.w3.org/TR/1999/NOTE-xlink-req-19990224\"><cite>XML XLink Requirements Version 1.0.</cite></a> 24 February 1999. W3C Note. URL: <a href=\"http://www.w3.org/TR/1999/NOTE-xlink-req-19990224\">http://www.w3.org/TR/1999/NOTE-xlink-req-19990224</a> ",
+ "XLINK10" : "David Orchard; Eve Maler; Steven DeRose. <a href=\"http://www.w3.org/TR/2001/REC-xlink-20010627\"><cite>XML Linking Language (XLink) Version 1.0.</cite></a> 27 June 2001. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2001/REC-xlink-20010627\">http://www.w3.org/TR/2001/REC-xlink-20010627</a> ",
+ "XLINK10-EXT" : "Norman Walsh. <a href=\"http://www.w3.org/TR/2005/NOTE-xlink10-ext-20050127\"><cite>Extending XLink 1.0.</cite></a> 27 January 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-xlink10-ext-20050127\">http://www.w3.org/TR/2005/NOTE-xlink10-ext-20050127</a> ",
+ "XLINK11" : "Eve Maler; et al. <a href=\"http://www.w3.org/TR/2008/WD-xlink11-20080331\"><cite>XML Linking Language (XLink) Version 1.1.</cite></a> 31 March 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xlink11-20080331\">http://www.w3.org/TR/2008/WD-xlink11-20080331</a> ",
+ "XLINK2RDF" : "Ron Daniel Jr. <a href=\"http://www.w3.org/TR/2000/NOTE-xlink2rdf-20000929\"><cite>Harvesting RDF Statements from XLinks.</cite></a> 29 September 2000. W3C Note. URL: <a href=\"http://www.w3.org/TR/2000/NOTE-xlink2rdf-20000929\">http://www.w3.org/TR/2000/NOTE-xlink2rdf-20000929</a> ",
+ "XML-BLUEBERRY-REQ" : "John Cowan. <a href=\"http://www.w3.org/TR/2001/WD-xml-blueberry-req-20010921\"><cite>XML Blueberry Requirements.</cite></a> 21 September 2001. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2001/WD-xml-blueberry-req-20010921\">http://www.w3.org/TR/2001/WD-xml-blueberry-req-20010921</a> ",
+ "XML-C14N" : "John Boyer. <a href=\"http://www.w3.org/TR/2001/REC-xml-c14n-20010315\"><cite>Canonical XML Version 1.0.</cite></a> 15 March 2001. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2001/REC-xml-c14n-20010315\">http://www.w3.org/TR/2001/REC-xml-c14n-20010315</a> ",
+ "XML-C14N11" : "John Boyer, Glenn Marcy. <a href=\"http://www.w3.org/TR/2008/REC-xml-c14n11-20080502/\"><cite>Canonical XML Version 1.1.</cite></a> 2 May 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-xml-c14n11-20080502/\">http://www.w3.org/TR/2008/REC-xml-c14n11-20080502/</a> ",
+ "XML-C14N20" : "John Boyer; Glen Marcy; Pratik Datta; Frederick Hirsch. <a href=\"http://www.w3.org/TR/2012/CR-xml-c14n2-20120124/\"><cite>Canonical XML Version 2.0.</cite></a> 24 January 2012. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/CR-xml-c14n2-20120124/\">http://www.w3.org/TR/2012/CR-xml-c14n2-20120124/</a>",
+ "XML-CANONICAL-REQ" : "James Tauber; Joel Nava. <a href=\"http://www.w3.org/TR/1999/NOTE-xml-canonical-req-19990605\"><cite>XML Canonicalization Requirements.</cite></a> 5 June 1999. W3C Note. URL: <a href=\"http://www.w3.org/TR/1999/NOTE-xml-canonical-req-19990605\">http://www.w3.org/TR/1999/NOTE-xml-canonical-req-19990605</a> ",
+ "XML-ENCRYPTION-REQ" : "Joseph Reagle. <a href=\"http://www.w3.org/TR/2002/NOTE-xml-encryption-req-20020304\"><cite>XML Encryption Requirements.</cite></a> 4 March 2002. W3C Note. URL: <a href=\"http://www.w3.org/TR/2002/NOTE-xml-encryption-req-20020304\">http://www.w3.org/TR/2002/NOTE-xml-encryption-req-20020304</a> ",
+ "XML-ENTITY-NAMES" : "Patrick Ion; David Carlisle. <a href=\"http://www.w3.org/TR/2008/WD-xml-entity-names-20080721\"><cite>XML Entity definitions for Characters.</cite></a> 21 July 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xml-entity-names-20080721\">http://www.w3.org/TR/2008/WD-xml-entity-names-20080721</a> ",
+ "XML-EVENTS" : "Mark Birbeck; Shane McCarron. <a href=\"http://www.w3.org/TR/2007/WD-xml-events-20070216\"><cite>XML Events 2.</cite></a> 16 February 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-xml-events-20070216\">http://www.w3.org/TR/2007/WD-xml-events-20070216</a> ",
+ "XML-EXC-C14N" : "Donald E. Eastlake 3rd; Joseph Reagle; John Boyer. <a href=\"http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/\"><cite>Exclusive XML Canonicalization Version 1.0.</cite></a> 18 July 2002. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/\">http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/</a> ",
+ "XML-FRAG-REQ" : "Paul Grosso. <a href=\"http://www.w3.org/TR/1998/NOTE-XML-FRAG-REQ-19981123\"><cite>XML Fragment Interchange Requirements, Version 1.0.</cite></a> 23 November 1998. W3C Note. URL: <a href=\"http://www.w3.org/TR/1998/NOTE-XML-FRAG-REQ-19981123\">http://www.w3.org/TR/1998/NOTE-XML-FRAG-REQ-19981123</a> ",
+ "XML-FRAGID" : "Paul Grosso. <a href=\"http://www.w3.org/TR/2003/NOTE-xml-fragid-20030912\"><cite>Proposal for XML Fragment Identifier Syntax 0.9.</cite></a> 12 September 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-xml-fragid-20030912\">http://www.w3.org/TR/2003/NOTE-xml-fragid-20030912</a> ",
+ "XML-FRAGMENT" : "Paul Grosso; Daniel Veillard. <a href=\"http://www.w3.org/TR/2001/CR-xml-fragment-20010212\"><cite>XML Fragment Interchange.</cite></a> 12 February 2001. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2001/CR-xml-fragment-20010212\">http://www.w3.org/TR/2001/CR-xml-fragment-20010212</a> ",
+ "XML-I18N-BP" : "Jirka Kosek; Yves Savourel; Richard Ishida. <a href=\"http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213\"><cite>Best Practices for XML Internationalization.</cite></a> 13 February 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213\">http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213</a> ",
+ "XML-ID" : "Daniel Veillard; Jonathan Marsh; Norman Walsh. <a href=\"http://www.w3.org/TR/2005/REC-xml-id-20050909\"><cite>xml:id Version 1.0.</cite></a> 9 September 2005. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2005/REC-xml-id-20050909\">http://www.w3.org/TR/2005/REC-xml-id-20050909</a> ",
+ "XML-ID-REQ" : "Jonathan Marsh. <a href=\"http://www.w3.org/TR/2003/WD-xml-id-req-20030806\"><cite>xml:id Requirements.</cite></a> 6 August 2003. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2003/WD-xml-id-req-20030806\">http://www.w3.org/TR/2003/WD-xml-id-req-20030806</a> ",
+ "XML-INFOSET" : "John Cowan; Richard Tobin. <a href=\"http://www.w3.org/TR/2004/REC-xml-infoset-20040204/\"><cite>XML Information Set (Second Edition).</cite></a> 4 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-xml-infoset-20040204/\">http://www.w3.org/TR/2004/REC-xml-infoset-20040204/</a> ",
+ "XML-INFOSET-RDFS" : "Richard Tobin. <a href=\"http://www.w3.org/TR/2001/NOTE-xml-infoset-rdfs-20010406\"><cite>An RDF Schema for the XML Information Set.</cite></a> 6 April 2001. W3C Note. URL: <a href=\"http://www.w3.org/TR/2001/NOTE-xml-infoset-rdfs-20010406\">http://www.w3.org/TR/2001/NOTE-xml-infoset-rdfs-20010406</a> ",
+ "XML-INFOSET-REQ" : "David Megginson. <a href=\"http://www.w3.org/TR/1999/NOTE-xml-infoset-req-19990218\"><cite>XML Information Set Requirements.</cite></a> 18 February 1999. W3C Note. URL: <a href=\"http://www.w3.org/TR/1999/NOTE-xml-infoset-req-19990218\">http://www.w3.org/TR/1999/NOTE-xml-infoset-req-19990218</a> ",
+ "XML-Japanese" : "M. Murata. <a href=\"http://www.w3.org/Submission/2005/SUBM-japanese-xml-20050324/\"><cite>XML Japanese Profile (2nd Edition)</cite></a>. March 2005. W3C Member Submission. URL: <a href=\"http://www.w3.org/Submission/2005/SUBM-japanese-xml-20050324/\"> http://www.w3.org/Submission/2005/SUBM-japanese-xml-20050324/</a>",
+ "XML-LINK-STYLE" : "Norman Walsh. <a href=\"http://www.w3.org/TR/2001/NOTE-xml-link-style-20010605\"><cite>XML Linking and Style.</cite></a> 5 June 2001. W3C Note. URL: <a href=\"http://www.w3.org/TR/2001/NOTE-xml-link-style-20010605\">http://www.w3.org/TR/2001/NOTE-xml-link-style-20010605</a> ",
+ "XML-MEDIA-TYPES" : "Ümit Yalçınalp; Anish Karmarkar. <a href=\"http://www.w3.org/TR/2005/NOTE-xml-media-types-20050504/\"><cite>Describing Media Content of Binary Data in XML.</cite></a> 4 May 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-xml-media-types-20050504/\">http://www.w3.org/TR/2005/NOTE-xml-media-types-20050504/</a> ",
+ "XML-MT" : "M. Murata, S. St.Laurent, D. Kohn. <a href=\"http://www.ietf.org/rfc/rfc3023.txt\"><cite>XML Media Types</cite></a>. IETF RFC 3023. URL: <a href=\"http://www.ietf.org/rfc/rfc3023.txt\"> http://www.ietf.org/rfc/rfc3023.txt</a>.",
+ "XML-NAMES" : "Richard Tobin; et al. <a href=\"http://www.w3.org/TR/2009/REC-xml-names-20091208/\"><cite>Namespaces in XML 1.0 (Third Edition).</cite></a> 8 December 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-xml-names-20091208/\">http://www.w3.org/TR/2009/REC-xml-names-20091208/</a> ",
+ "XML-NAMES11" : "Andrew Layman; et al. <a href=\"http://www.w3.org/TR/2006/REC-xml-names11-20060816\"><cite>Namespaces in XML 1.1 (Second Edition).</cite></a> 16 August 2006. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2006/REC-xml-names11-20060816\">http://www.w3.org/TR/2006/REC-xml-names11-20060816</a> ",
+ "XML-NAMES11-REQ" : "Jonathan Marsh. <a href=\"http://www.w3.org/TR/2002/WD-xml-names11-req-20020403\"><cite>Namespaces in XML 1.1 Requirements.</cite></a> 3 April 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-xml-names11-req-20020403\">http://www.w3.org/TR/2002/WD-xml-names11-req-20020403</a> ",
+ "XML-SCHEMA-REQ" : "Ashok Malhotra; Murray Maloney. <a href=\"http://www.w3.org/TR/1999/NOTE-xml-schema-req-19990215\"><cite>XML Schema Requirements.</cite></a> 15 February 1999. W3C Note. URL: <a href=\"http://www.w3.org/TR/1999/NOTE-xml-schema-req-19990215\">http://www.w3.org/TR/1999/NOTE-xml-schema-req-19990215</a> ",
+ "XML-STYLESHEET" : "James Clark. <a href=\"http://www.w3.org/1999/06/REC-xml-stylesheet-19990629\"><cite>Associating Style Sheets with XML documents.</cite></a> 29 June 1999. W3C Recommendation. URL: <a href=\"http://www.w3.org/1999/06/REC-xml-stylesheet-19990629\">http://www.w3.org/1999/06/REC-xml-stylesheet-19990629</a> ",
+ "XML10" : "C. M. Sperberg-McQueen; et al. <a href=\"http://www.w3.org/TR/2008/REC-xml-20081126/\"><cite>Extensible Markup Language (XML) 1.0 (Fifth Edition).</cite></a> 26 November 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-xml-20081126/\">http://www.w3.org/TR/2008/REC-xml-20081126/</a> ",
+ "XML10-4e" : "C. M. Sperberg-McQueen; et al. <a href=\"http://www.w3.org/TR/2006/REC-xml-20060816/\"><cite>Extensible Markup Language (XML) 1.0 (Fourth Edition).</cite></a> 16 August 2006. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2006/REC-xml-20060816/\">http://www.w3.org/TR/2006/REC-xml-20060816/</a> ",
+ "XML11" : "Eve Maler; et al. <a href=\"http://www.w3.org/TR/2006/REC-xml11-20060816\"><cite>Extensible Markup Language (XML) 1.1 (Second Edition).</cite></a> 16 August 2006. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2006/REC-xml11-20060816\">http://www.w3.org/TR/2006/REC-xml11-20060816</a> ",
+ "XML11SCHEMA10" : "Henry S. Thompson. <a href=\"http://www.w3.org/TR/2005/NOTE-xml11schema10-20050511\"><cite>Processing XML 1.1 documents with XML Schema 1.0 processors.</cite></a> 11 May 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-xml11schema10-20050511\">http://www.w3.org/TR/2005/NOTE-xml11schema10-20050511</a> ",
+ "XMLBASE" : "Jonathan Marsh, Richard Tobin. <a href=\"http://www.w3.org/TR/2009/REC-xmlbase-20090128/\"><cite>XML Base (Second Edition).</cite></a> 28 January 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-xmlbase-20090128/\">http://www.w3.org/TR/2009/REC-xmlbase-20090128/</a> ",
+ "XMLDSIG-BESTPRACTICES" : "Pratik Datta; Frederick Hirsch. <a href=\"http://www.w3.org/TR/2012/NOTE-xmldsig-bestpractices-20120710/\"><cite>XML Signature Best Practices.</cite></a> 10 July 2012. W3C Working Group Note. URL: <a href=\"http://www.w3.org/TR/2012/NOTE-xmldsig-bestpractices-20120710/\">http://www.w3.org/TR/2012/NOTE-xmldsig-bestpractices-20120710/</a> ",
+ "XMLDSIG-CORE2002" : "Joseph Reagle; et al. <a href=\"http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/\"><cite>XML Signature Syntax and Processing.</cite></a> 12 February 2002. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/\">http://www.w3.org/TR/2002/REC-xmldsig-core-20020212</a> ",
+ "XMLDSIG-CORE" : "Joseph Reagle; et al. <a href=\"http://www.w3.org/TR/2008/REC-xmldsig-core-20080610/\"><cite>XML Signature Syntax and Processing (Second Edition).</cite></a> 10 June 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-xmldsig-core-20080610/\">http://www.w3.org/TR/2008/REC-xmldsig-core-20080610</a> ",
+ "XMLDSIG-CORE1" : "D. Eastlake, J. Reagle, D. Solo, F. Hirsch, T. Roessler, K. Yiu. <a href=\"http://www.w3.org/TR/2011/CR-xmldsig-core1-20110303/\"><cite>XML Signature Syntax and Processing Version 1.1.</cite></a> 3 March 2011. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/CR-xmldsig-core1-20110303/\">http://www.w3.org/TR/2011/CR-xmldsig-core1-20110303/</a> ",
+ "XMLDSIG-CORE1-CHGS" : "Frederick Hirsch. <a href=\"http://www.w3.org/2008/xmlsec/Drafts/xmldsig-core1-explain/Overview.html\"><cite>Functional explanation of changes in XML Signature 1.1</cite></a>. W3C Editors Draft (Note Track - Work in Progress). URL: <a href=\"http://www.w3.org/2008/xmlsec/Drafts/xmldisg-core1-explain/Overview.html\">http://www.w3.org/2008/xmlsec/Drafts/xmldsig-core1-explain/Overview.html</a> ",
+ "XMLDSIG-CORE1-INTEROP" : "Frederick Hirsch <a href=\"http://www.w3.org/2008/xmlsec/Drafts/xmldsig-core1-interop/Overview.src.html\"><cite>XML Signature 1.1 Interop Test Report</cite></a>. 23 July 2012. W3C Editors Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/2008/xmlsec/Drafts/xmldsig-core1-interop/Overview.src.html\">http://www.w3.org/2008/xmlsec/Drafts/xmldsig-core1-interop/Overview.src.html</a> ",
+ "XMLDSIG-CORE2" : "Mark Bartel; John Boyer; Barb Fox et al. <a href=\"http://www.w3.org/TR/2012/CR-xmldsig-core2-20120124/\"><cite>XML Signature Syntax and Processing Version 2.0</cite></a>. 24 January 2012. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/CR-xmldsig-core2-20120124/\">http://www.w3.org/TR/2012/CR-xmldsig-core2-20120124/</a>",
+ "XMLDSIG-GARCIA" : "Raúl Benito García. <a href=\"http://www.w3.org/2008/xmlsec/papers/TFCFirmasdigitalesenXML-11-10-2007.pdf\"><cite>Verificación De Firmas Digitales En Documentos XML De Tamaño Arbitrario.</cite></a> December 2006. URL: <a href=\"http://www.w3.org/2008/xmlsec/papers/TFCFirmasdigitalesenXML-11-10-2007.pdf\">http://www.w3.org/2008/xmlsec/papers/TFCFirmasdigitalesenXML-11-10-2007.pdf</a>",
+ "XMLDSIG-COMPLEXITY" : "Brad Hill. <a href=\"http://www.w3.org/2007/xmlsec/ws/papers/04-hill-isecpartners/\"><cite>Complexity as the Enemy of Security: Position Paper for W3C Workshop on Next Steps for XML Signature and XML Encryption.</cite></a>. 25-26 September 2007. W3C Workshop. URL: <a href=\"http://www.w3.org/2007/xmlsec/ws/papers/04-hill-isecpartners/\">http://www.w3.org/2007/xmlsec/ws/papers/04-hill-isecpartners/</a> ",
+ "XMLDSIG-SEMANTICS" : "Sebastian Gajek, Lijun Liao, and Jörg Schwenk. <a href=\"http://www.w3.org/2007/xmlsec/ws/papers/07-gajek-rub/\"><cite> Towards a Semantic of XML Signature: Position Paper for W3C Workshop on Next Steps for XML Signature and XML Encryption </cite></a> 25-26 September 2007. W3C Workshop. URL: <a href=\"http://www.w3.org/2007/xmlsec/ws/papers/07-gajek-rub/\">http://www.w3.org/2007/xmlsec/ws/papers/07-gajek-rub/</a> ",
+ "XMLDSIG-THOMPSON": "Henry Thompson. <a href=\"http://www.w3.org/2007/xmlsec/ws/papers/20-thompson/\"><cite>Radical proposal for Vnext of XML Signature: Position Paper for W3C Workshop on Next Steps for XML Signature and XML Encryption</cite></a> 26 September 2007. W3C Workshop. URL: <a href=\"http://www.w3.org/2007/xmlsec/ws/papers/20-thompson/\"> http://www.w3.org/2007/xmlsec/ws/papers/20-thompson/</a> ",
+ "XMLDSIG-XPATH" : "Pratik Datta. Frederick Hirsch, Meiko Jensen <a href=\"http://www.w3.org/TR/2012/CR-xmldsig-xpath-20120124/\"><cite>XML Signature Streaming Profile of XPath 1.0</cite>.</a> 24 January 2012. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/CR-xmldsig-xpath-20120124/\">http://www.w3.org/TR/2012/CR-xmldsig-xpath-20120124/</a>",
+ "XMLDSIG-XPATH-FILTER2" : "Merlin Hughes; John Boyer; Joseph Reagle. <a href=\"http://www.w3.org/TR/2002/REC-xmldsig-filter2-20021108/\"><cite>XML-Signature XPath Filter 2.0.</cite></a> 8 November 2002. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2002/REC-xmldsig-filter2-20021108/\">http://www.w3.org/TR/2002/REC-xmldsig-filter2-20021108/</a> ",
+ "XMLDSIG-PROPERTIES" : "Frederick Hirsch. <a href=\"http://www.w3.org/TR/2011/CR-xmldsig-properties-20110303/\"><cite>XML Signature Properties.</cite></a> 3 March 2011. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/CR-xmldsig-properties-20110303/\">http://www.w3.org/TR/2011/CR-xmldsig-properties-20110303/</a> ",
+ "XMLDSIG-REQUIREMENTS" : "Joseph Reagle Jr. <a href=\"http://www.w3.org/TR/1999/WD-xmldsig-requirements-19991014\"><cite>XML-Signature Requirements.</cite></a> 14 October 1999. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/1999/WD-xmldsig-requirements-19991014\">http://www.w3.org/TR/1999/WD-xmldsig-requirements-19991014</a> ",
+ "XMLDSIG-SIMPLIFY" : "Pratik Datta; Frederick Hirsch. <a href=\"http://www.w3.org/TR/2009/WD-xmldsig-simplify-20090226\"><cite>XML Signature Transform Simplification: Requirements and Design.</cite></a> 26 February 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-xmldsig-simplify-20090226\">http://www.w3.org/TR/2009/WD-xmldsig-simplify-20090226</a> ",
+ "XMLDSIG2ED-TESTS" : "Konrad Lanz; Sean Mullan; Juan Carlos Cruellas. <a href=\"http://www.w3.org/TR/2008/NOTE-xmldsig2ed-tests-20080610\"><cite>Test Cases for C14N 1.1 and XMLDSig Interoperability.</cite></a> 10 June 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-xmldsig2ed-tests-20080610\">http://www.w3.org/TR/2008/NOTE-xmldsig2ed-tests-20080610</a> ",
+ "XMLENC-PKCS15-ATTACK" : "Tibor Jager; Sebastian Schinzel, Juraj Somorovsky. <a href=\"http://www.nds.rub.de/media/nds/veroeffentlichungen/2012/07/11/XMLencBleichenbacher.pdf\"><cite>Bleichenbacher's Attack Strikes Again: Breaking PKCS#1.5 in XML Encryption</cite></a> . 2012. In Proceedings of the 17th European Symposium on Research in Computer Security (ESO RICS). URL: <a href=\"http://www.nds.rub.de/media/nds/veroeffentlichungen/2012/07/11/XMLencBleichenbacher.pdf\">http://www.nds.rub.de/media/nds/veroeffentlichungen/2012/07/11/XMLencBleichenbacher.pdf</a> ",
+ "XMLENC-CBC-ATTACK" : "Tibor Jager; Juraj Somorovsky. <a href=\"http://www.nds.rub.de/media/nds/veroeffentlichungen/2011/10/22/HowToBreakXMLenc.pdf\"><cite>How to Break XML Encryption</cite></a> 17-21 October 2011. CCS' 11, ACM. URL: <a href=\"http://www.nds.rub.de/media/nds/veroeffentlichungen/2011/10/22/HowToBreakXMLenc.pdf\">http://www.nds.rub.de/media/nds/veroeffentlichungen/2011/10/22/HowToBreakXMLenc.pdf</a> ",
+ "XMLENC-CBC-ATTACK-COUNTERMEASURES" : "Juraj Somorovsky, Jörg Schwenk. <a href=\"http://www.w3.org/2008/xmlsec/papers/xmlEncCountermeasuresW3C.pdf\"><cite>Technical Analysis of Countermeasures against Attack on XML Encryption - or - Just Another Motivation for Authenticated Encryption</cite.></a>. 2011. URL: <a href=\"http://www.w3.org/2008/xmlsec/papers/xmlEncCountermeasuresW3C.pdf\">http://www.w3.org/2008/xmlsec/papers/xmlEncCountermeasuresW3C.pdf</a>",
+ "XMLENC-CREF2" : "Frederick Hirsch. <a href=\"http://www.w3.org/TR/2012/CR-xmlenc-transform20-20120313/\">Encryption 1.1 CipherReference Processing Using 2.0 Transforms</cite></a> 13 March 2012. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\" http://www.w3.org/TR/2012/CR-xmlenc-transform20-20120313/\">http://www.w3.org/TR/2012/CR-xmlenc-transform20-20120313/</a>",
+ "XMLENC-CORE" : "Donald Eastlake; Joseph Reagle. <a href=\"http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/\"><cite>XML Encryption Syntax and Processing.</cite></a> 10 December 2002. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/\">http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/</a> ",
+ "XMLENC-CORE1" : "J. Reagle; D. Eastlake; F. Hirsch; T. Roessler. <a href=\"http://www.w3.org/TR/2012/CR-xmlenc-core1-20120313/\"><cite>XML Encryption Syntax and Processing Version 1.1.</cite></a> 13 March 2012. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/CR-xmlenc-core1-20120313/\">http://www.w3.org/TR/2012/CR-xmlenc-core1-20120313/</a> ",
+ "XMLENC-CORE1-CHGS" : "Frederick Hirsch. <a href=\"http://www.w3.org/2008/xmlsec/Drafts/xmlenc-core1-explain/Overview.html\"><cite>Functional explanation of changes in XML Encryption 1.1</cite></a>. W3C Editors Draft (Note Track - Work in Progress). URL: <a href=\"http://www.w3.org/2008/xmlsec/Drafts/xmlenc-core1-explain/Overview.html\">http://www.w3.org/2008/xmlsec/Drafts/xmlenc-core1-explain/Overview.html</a> ",
+ "XMLENC-CORE1-INTEROP" : "Frederick Hirsch <a href=\"http://www.w3.org/2008/xmlsec/Drafts/xmlenc-core1-interop/Overview.src.html\"><cite>XML Encryption 1.1 Interop Test Report</cite></a>. 6 August 2012. W3C Editors Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/2008/xmlsec/Drafts/xmlenc-core1-interop/Overview.src.html\">http://www.w3.org/2008/xmlsec/Drafts/xmlenc-core1-interop/Overview.src.html</a> ",
+ "XMLENC-DECRYPT" : "Takeshi Imamura; Merlin Hughes; Hiroshi Maruyama. <a href=\"http://www.w3.org/TR/2002/REC-xmlenc-decrypt-20021210\"><cite>Decryption Transform for XML Signature.</cite></a> 10 December 2002. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2002/REC-xmlenc-decrypt-20021210\">http://www.w3.org/TR/2002/REC-xmlenc-decrypt-20021210</a> ",
+ "XMLENC11-TESTCASES" : "Pratik Datta, Frederick Hirsch. <a href=\"http://www.w3.org/TR/2012/WD-xmlenc-core1-testcases-20120105/\"><cite>Test Cases for XML Encryption 1.1.</cite></a> 5 January 2012. W3C First Public Working Draft (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/WD-xmlenc-core1-testcases-20120105/\">http://www.w3.org/TR/2012/WD-xmlenc-core1-testcases-20120105/</a>",
+ "XHR" : "Anne van Kesteren. <a href='http://www.w3.org/TR/XMLHttpRequest/'>XMLHttpRequest</a>",
+ "XMLHTTPREQUEST" : "Anne van Kesteren. <a href=\"http://www.w3.org/TR/2008/WD-XMLHttpRequest-20080415\"><cite>The XMLHttpRequest Object.</cite></a> 15 April 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-XMLHttpRequest-20080415\">http://www.w3.org/TR/2008/WD-XMLHttpRequest-20080415</a> ",
+ "XMLHTTPREQUEST2" : "Anne van Kesteren. <a href=\"http://www.w3.org/TR/2008/WD-XMLHttpRequest2-20080930\"><cite>XMLHttpRequest Level 2.</cite></a> 30 September 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-XMLHttpRequest2-20080930\">http://www.w3.org/TR/2008/WD-XMLHttpRequest2-20080930</a> ",
+ "XMLHTTPREQUEST3" : "Anne van Kesteren. <a href=\"http://www.w3.org/TR/2010/CR-XMLHttpRequest-20100803\"><cite>XMLHttpRequest</cite></a> 3 August 2010. W3C Candidate Recommendation. URL: <a href=\"http://www.w3.org/TR/2010/CR-XMLHttpRequest-20100803\">http://www.w3.org/TR/2010/CR-XMLHttpRequest-20100803</a> ",
+ "XMLP-REQS" : "Oisin Hurley; et al. <a href=\"http://www.w3.org/TR/2003/NOTE-xmlp-reqs-20030728\"><cite>XML Protocol (XMLP) Requirements.</cite></a> 28 July 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-xmlp-reqs-20030728\">http://www.w3.org/TR/2003/NOTE-xmlp-reqs-20030728</a> ",
+ "XMLP-SCENARIOS" : "John Ibbotson. <a href=\"http://www.w3.org/TR/2003/NOTE-xmlp-scenarios-20030730\"><cite>SOAP Version 1.2 Usage Scenarios.</cite></a> 30 July 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-xmlp-scenarios-20030730\">http://www.w3.org/TR/2003/NOTE-xmlp-scenarios-20030730</a> ",
+ "XMLSCHEMA-0" : "David C. Fallside; Priscilla Walmsley. <a href=\"http://www.w3.org/TR/2004/REC-xmlschema-0-20041028/\"><cite>XML Schema Part 0: Primer Second Edition.</cite></a> 28 October 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-xmlschema-0-20041028/\">http://www.w3.org/TR/2004/REC-xmlschema-0-20041028/</a> ",
+ "XMLSCHEMA-1" : "Henry S. Thompson; et al. <a href=\"http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/\"><cite>XML Schema Part 1: Structures Second Edition.</cite></a> 28 October 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/\">http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/</a> ",
+ "XMLSCHEMA-11-REQ" : "Priscilla Walmsley; Ashok Malhotra; Charles Campbell. <a href=\"http://www.w3.org/TR/2003/WD-xmlschema-11-req-20030121\"><cite>Requirements for XML Schema 1.1.</cite></a> 21 January 2003. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2003/WD-xmlschema-11-req-20030121\">http://www.w3.org/TR/2003/WD-xmlschema-11-req-20030121</a> ",
+ "XMLSCHEMA-2" : "Paul V. Biron; Ashok Malhotra. <a href=\"http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/\"><cite>XML Schema Part 2: Datatypes Second Edition.</cite></a> 28 October 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/\">http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/</a> ",
+ "XMLSCHEMA-FORMAL" : "Philip Wadler; et al. <a href=\"http://www.w3.org/TR/2001/WD-xmlschema-formal-20010925\"><cite>XML Schema: Formal Description.</cite></a> 25 September 2001. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2001/WD-xmlschema-formal-20010925\">http://www.w3.org/TR/2001/WD-xmlschema-formal-20010925</a> ",
+ "XMLSCHEMA-GUIDE2VERSIONING" : "David Orchard. <a href=\"http://www.w3.org/TR/2007/WD-xmlschema-guide2versioning-20070720\"><cite>Guide to Versioning XML Languages using new XML Schema 1.1 features.</cite></a> 20 July 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-xmlschema-guide2versioning-20070720\">http://www.w3.org/TR/2007/WD-xmlschema-guide2versioning-20070720</a> ",
+ "XMLSCHEMA-PATTERNS" : "Jonathan Calladine; et al. <a href=\"http://www.w3.org/TR/2008/WD-xmlschema-patterns-20080328\"><cite>Basic XML Schema Patterns for Databinding Version 1.0.</cite></a> 28 March 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xmlschema-patterns-20080328\">http://www.w3.org/TR/2008/WD-xmlschema-patterns-20080328</a> ",
+ "XMLSCHEMA-PATTERNS-ADVANCED" : "George Cowe; et al. <a href=\"http://www.w3.org/TR/2008/WD-xmlschema-patterns-advanced-20080328\"><cite>Advanced XML Schema Patterns for Databinding Version 1.0.</cite></a> 28 March 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xmlschema-patterns-advanced-20080328\">http://www.w3.org/TR/2008/WD-xmlschema-patterns-advanced-20080328</a> ",
+ "XMLSCHEMA-REF" : "Asir S. Vedamuthu; Mary Holstege. <a href=\"http://www.w3.org/TR/2008/WD-xmlschema-ref-20081117\"><cite>W3C XML Schema Definition Language (XSD): Component Designators.</cite></a> 17 November 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xmlschema-ref-20081117\">http://www.w3.org/TR/2008/WD-xmlschema-ref-20081117</a> ",
+ "XMLSCHEMA11-1" : "C. M. Sperberg-McQueen; Henry S. Thompson; Shudi Gao. <a href=\"http://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/\"><cite>W3C XML Schema Definition Language (XSD) 1.1 Part 1: Structures.</cite></a> 5 April 2012. W3C Recommendation URL: <a href=\"http://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/\">http://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/</a> ",
+ "XMLSCHEMA11-2" : "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> ",
+ "XMLSEC-ALGORITHMS" : "Thomas Roessler; Frederick Hirsch; Kelvin Yiu. <a href=\"http://www.w3.org/TR/2012/WD-xmlsec-algorithms-20120105/\"><cite>XML Security Algorithm Cross-Reference.</cite></a> 5 January 2012. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/WD-xmlsec-algorithms-20120105/\">http://www.w3.org/TR/2012/WD-xmlsec-algorithms-20120105/</a> ",
+ "XMLSEC-DERIVEDKEYS" : "Magnus Nyström. <a href=\"http://www.w3.org/TR/2009/WD-xmlsec-derivedkeys-20090226/\"><cite>XML Security Derived Keys.</cite></a> 26 February 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-xmlsec-derivedkeys-20090226\">http://www.w3.org/TR/2009/WD-xmlsec-derivedkeys-20090226</a> ",
+ "XMLSEC-GHCIPHERS" : "Magnus Nyström; Frederick Hirsch. <a href=\"http://www.w3.org/TR/2011/CR-xmlsec-generic-hybrid-20110303/\"><cite>XML Security Generic Hybrid Ciphers.</cite></a> 3 March 2011. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/CR-xmlsec-generic-hybrid-20110303/\">http://www.w3.org/TR/2011/CR-xmlsec-generic-hybrid-20110303/</a> ",
+ "XMLSEC-NEXTSTEPS-2007" : "Frederick Hirsch; Thomas Roessler. <a href=\"http://www.w3.org/2007/xmlsec/ws/report.html\"><cite>Workshop Report W3C Workshop on Next Steps for XML Signature and XML Encryption</cite></a> 25-26 September 2007. W3C Workshop Report. URL: <a href=\"http://www.w3.org/2007/xmlsec/ws/report.html\">http://www.w3.org/2007/xmlsec/ws/report.html</a>",
+ "XMLSEC-RELAXNG" : "Makoto Murata, Frederick Hirsch. <a href=\"http://www.w3.org/TR/2012/NOTE-xmlsec-rngschema-20120124/\"><cite>XML Security RELAX NG Schemas.</cite></a> 24 January 2012. W3C Working Group Note. URL: <a href=\"http://www.w3.org/TR/2012/NOTE-xmlsec-rngschema-20120124/\">http://www.w3.org/TR/2012/NOTE-xmlsec-rngschema-20120124/</a>",
+ "XMLSEC11-REQS" : "Frederick Hirsch, Thomas Roessler. <a href=\"http://www.w3.org/TR/2011/WD-xmlsec-reqs-20110303/\"><cite>XML Security 1.1 Requirements and Design Considerations.</cite></a> 3 March 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-xmlsec-reqs-20110303/\">http://www.w3.org/TR/2011/WD-xmlsec-reqs-20110303/</a> ",
+ "XMLSEC2-REQS" : "Frederick Hirsch, Pratik Datta. <a href=\"http://www.w3.org/TR/2011/WD-xmlsec-reqs2-20110421/\"><cite>XML Security 2.0 Requirements and Design Considerations.</cite></a> 21 April 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-xmlsec-reqs2-20110421/\">http://www.w3.org/TR/2011/WD-xmlsec-reqs2-20110421/</a> ",
+ "XMLSTYLE" : "James Clark. <a href=\"http://www.w3.org/1999/06/REC-xml-stylesheet-19990629\"><cite>Associating Style Sheets with XML documents.</cite></a> 29 June 1999. W3C Recommendation. URL: <a href=\"http://www.w3.org/1999/06/REC-xml-stylesheet-19990629\">http://www.w3.org/1999/06/REC-xml-stylesheet-19990629</a> ",
+ "XML-PARSER-STAX" : "Christopher Fry. <a href=\"http://jcp.org/en/jsr/detail?id=173\"><cite>JSR 173: Streaming API for XML for Java Specification</cite></a> 8th October 2003. v1.0 URL: <a href=\"http://jcp.org/en/jsr/detail?id=173\">http://jcp.org/en/jsr/detail?id=173</a>",
+ "XOP10" : "Martin Gudgin; et al. <a href=\"http://www.w3.org/TR/2005/REC-xop10-20050125\"><cite>XML-binary Optimized Packaging.</cite></a> 25 January 2005. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2005/REC-xop10-20050125\">http://www.w3.org/TR/2005/REC-xop10-20050125</a> ",
+ "XOPINC-FAQ" : "Michael Mahan. <a href=\"http://www.w3.org/TR/2004/NOTE-xopinc-FAQ-20040608\"><cite>XOP Inclusion Mechanism - Frequently Asked Questions.</cite></a> 8 June 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-xopinc-FAQ-20040608\">http://www.w3.org/TR/2004/NOTE-xopinc-FAQ-20040608</a> ",
+ "XPATH" : "James Clark; Steven DeRose. <a href=\"http://www.w3.org/TR/1999/REC-xpath-19991116/\"><cite>XML Path Language (XPath) Version 1.0.</cite></a> 16 November 1999. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/1999/REC-xpath-19991116/\">http://www.w3.org/TR/1999/REC-xpath-19991116/</a> ",
+ "XPATH-DATAMODEL" : "Norman Walsh; et al. <a href=\"http://www.w3.org/TR/2007/REC-xpath-datamodel-20070123\"><cite>XQuery 1.0 and XPath 2.0 Data Model (XDM).</cite></a> 23 January 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-xpath-datamodel-20070123\">http://www.w3.org/TR/2007/REC-xpath-datamodel-20070123</a> ",
+ "XPATH-FULL-TEXT-10" : "Stephen Buxton; et al. <a href=\"http://www.w3.org/TR/2008/CR-xpath-full-text-10-20080516\"><cite>XQuery and XPath Full Text 1.0.</cite></a> 16 May 2008. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/CR-xpath-full-text-10-20080516\">http://www.w3.org/TR/2008/CR-xpath-full-text-10-20080516</a> ",
+ "XPATH-FULL-TEXT-10-REQUIREMENTS" : "Pat Case; Stephen Buxton; Michael Rys. <a href=\"http://www.w3.org/TR/2008/WD-xpath-full-text-10-requirements-20080516\"><cite>XQuery and XPath Full Text 1.0 Requirements.</cite></a> 16 May 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xpath-full-text-10-requirements-20080516\">http://www.w3.org/TR/2008/WD-xpath-full-text-10-requirements-20080516</a> ",
+ "XPATH-FULL-TEXT-10-USE-CASES" : "Pat Case; Sihem Amer-Yahia. <a href=\"http://www.w3.org/TR/2008/WD-xpath-full-text-10-use-cases-20080516\"><cite>XQuery and XPath Full Text 1.0 Use Cases.</cite></a> 16 May 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xpath-full-text-10-use-cases-20080516\">http://www.w3.org/TR/2008/WD-xpath-full-text-10-use-cases-20080516</a> ",
+ "XPATH-FUNCTIONS" : "Jim Melton; Ashok Malhotra; Norman Walsh. <a href=\"http://www.w3.org/TR/2007/REC-xpath-functions-20070123\"><cite>XQuery 1.0 and XPath 2.0 Functions and Operators.</cite></a> 23 January 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-xpath-functions-20070123\">http://www.w3.org/TR/2007/REC-xpath-functions-20070123</a> ",
+ "XPATH20" : "Anders Berglund; et al. <a href=\"http://www.w3.org/TR/2007/REC-xpath20-20070123\"><cite>XML Path Language (XPath) 2.0.</cite></a> 23 January 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-xpath20-20070123\">http://www.w3.org/TR/2007/REC-xpath20-20070123</a> ",
+ "XPATH20REQ" : "K. Karun; Mary F. Fernández; Mark Scardina. <a href=\"http://www.w3.org/TR/2005/WD-xpath20req-20050603\"><cite>XPath Requirements Version 2.0.</cite></a> 3 June 2005. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2005/WD-xpath20req-20050603\">http://www.w3.org/TR/2005/WD-xpath20req-20050603</a> ",
+ "XPROC" : "Alex Milowski; Henry S. Thompson; Norman Walsh. <a href=\"http://www.w3.org/TR/2008/CR-xproc-20081126/\"><cite>XProc: An XML Pipeline Language.</cite></a> 26 November 2008. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/CR-xproc-20081126/\">http://www.w3.org/TR/2008/CR-xproc-20081126/</a> ",
+ "XPROC-REQUIREMENTS" : "Alex Milowski. <a href=\"http://www.w3.org/TR/2006/WD-xproc-requirements-20060411\"><cite>XML Processing Model Requirements and Use Cases.</cite></a> 11 April 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-xproc-requirements-20060411\">http://www.w3.org/TR/2006/WD-xproc-requirements-20060411</a> ",
+ "XPTR-ELEMENT" : "Norman Walsh; et al. <a href=\"http://www.w3.org/TR/2003/REC-xptr-element-20030325/\"><cite>XPointer element() Scheme.</cite></a> 25 March 2003. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2003/REC-xptr-element-20030325/\">http://www.w3.org/TR/2003/REC-xptr-element-20030325/</a> ",
+ "XPTR-FRAMEWORK" : "Paul Grosso; et al. <a href=\"http://www.w3.org/TR/2003/REC-xptr-framework-20030325/\"><cite>XPointer Framework.</cite></a> 25 March 2003. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2003/REC-xptr-framework-20030325/\">http://www.w3.org/TR/2003/REC-xptr-framework-20030325/</a> ",
+ "XPTR-INFOSET-LIAISON" : "Steven J. DeRose. <a href=\"http://www.w3.org/TR/1999/NOTE-xptr-infoset-liaison-19990224\"><cite>XPointer-Information Set Liaison Statement Version 1.0.</cite></a> 24 February 1999. W3C Note. URL: <a href=\"http://www.w3.org/TR/1999/NOTE-xptr-infoset-liaison-19990224\">http://www.w3.org/TR/1999/NOTE-xptr-infoset-liaison-19990224</a> ",
+ "XPTR-POLICY" : "Henry Thompson. <a href=\"http://www.w3.org/2005/04/xpointer-policy.html\"><cite>XPointer Scheme Name Registry Policy.</cite></a>. URL: <a href=\"http://www.w3.org/2005/04/xpointer-policy.html\">http://www.w3.org/2005/04/xpointer-policy.html</a>",
+ "XPTR-REQ" : "Steven J. DeRose. <a href=\"http://www.w3.org/TR/1999/NOTE-xptr-req-19990224\"><cite>XML XPointer Requirements Version 1.0.</cite></a> 24 February 1999. W3C Note. URL: <a href=\"http://www.w3.org/TR/1999/NOTE-xptr-req-19990224\">http://www.w3.org/TR/1999/NOTE-xptr-req-19990224</a> ",
+ "XPTR-XMLNS" : "Jonathan Marsh; et al. <a href=\"http://www.w3.org/TR/2003/REC-xptr-xmlns-20030325/\"><cite>XPointer xmlns() Scheme.</cite></a> 25 March 2003. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2003/REC-xptr-xmlns-20030325/\">http://www.w3.org/TR/2003/REC-xptr-xmlns-20030325/</a> ",
+ "XPTR-XPOINTER-CR2001" : "Ron Daniel Jr.; Eve Maler; Steven DeRose. <a href=\"http://www.w3.org/TR/2001/CR-xptr-20010911/\"><cite>XPointer xpointer() Scheme.</cite></a> September 2001. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2001/CR-xptr-20010911/\">http://www.w3.org/TR/2001/CR-xptr-20010911/</a> ",
+ "XPTR-XPOINTER" : "Ron Daniel Jr.; Eve Maler; Steven DeRose. <a href=\"http://www.w3.org/TR/2002/WD-xptr-xpointer-20021219/\"><cite>XPointer xpointer() Scheme.</cite></a> 19 December 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-xptr-xpointer-20021219/\">http://www.w3.org/TR/2002/WD-xptr-xpointer-20021219/</a> ",
+ "XQUERY" : "Don Chamberlin; et al. <a href=\"http://www.w3.org/TR/2007/REC-xquery-20070123\"><cite>XQuery 1.0: An XML Query Language.</cite></a> 23 January 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-xquery-20070123\">http://www.w3.org/TR/2007/REC-xquery-20070123</a> ",
+ "XQUERY-11" : "Jonathan Robie; Don Chamberlin. <a href=\"http://www.w3.org/TR/2008/WD-xquery-11-20081203\"><cite>XQuery 1.1.</cite></a> 3 December 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xquery-11-20081203\">http://www.w3.org/TR/2008/WD-xquery-11-20081203</a> ",
+ "XQUERY-11-REQUIREMENTS" : "Daniel Engovatov; Daniel Engovatov. <a href=\"http://www.w3.org/TR/2007/WD-xquery-11-requirements-20070323\"><cite>XML Query (XQuery) 1.1 Requirements.</cite></a> 23 March 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-xquery-11-requirements-20070323\">http://www.w3.org/TR/2007/WD-xquery-11-requirements-20070323</a> ",
+ "XQUERY-11-USE-CASES" : "Tim Kraska. <a href=\"http://www.w3.org/TR/2008/WD-xquery-11-use-cases-20081203\"><cite>XQuery 1.1 Use Cases.</cite></a> 3 December 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xquery-11-use-cases-20081203\">http://www.w3.org/TR/2008/WD-xquery-11-use-cases-20081203</a> ",
+ "XQUERY-REQUIREMENTS" : "Massimo Marchiori; et al. <a href=\"http://www.w3.org/TR/2007/NOTE-xquery-requirements-20070323\"><cite>XML Query (XQuery) Requirements.</cite></a> 23 March 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-xquery-requirements-20070323\">http://www.w3.org/TR/2007/NOTE-xquery-requirements-20070323</a> ",
+ "XQUERY-SEMANTICS" : "Michael Rys; et al. <a href=\"http://www.w3.org/TR/2007/REC-xquery-semantics-20070123\"><cite>XQuery 1.0 and XPath 2.0 Formal Semantics.</cite></a> 23 January 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-xquery-semantics-20070123\">http://www.w3.org/TR/2007/REC-xquery-semantics-20070123</a> ",
+ "XQUERY-SX-10" : "Giorgio Ghelli; et al. <a href=\"http://www.w3.org/TR/2008/WD-xquery-sx-10-20081203\"><cite>XQuery Scripting Extension 1.0.</cite></a> 3 December 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xquery-sx-10-20081203\">http://www.w3.org/TR/2008/WD-xquery-sx-10-20081203</a> ",
+ "XQUERY-SX-10-REQUIREMENTS" : "Giorgio Ghelli; et al. <a href=\"http://www.w3.org/TR/2007/WD-xquery-sx-10-requirements-20070323\"><cite>XQuery Scripting Extension 1.0 Requirements.</cite></a> 23 March 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-xquery-sx-10-requirements-20070323\">http://www.w3.org/TR/2007/WD-xquery-sx-10-requirements-20070323</a> ",
+ "XQUERY-SX-10-USE-CASES" : "John Snelson. <a href=\"http://www.w3.org/TR/2008/WD-xquery-sx-10-use-cases-20081203\"><cite>XQuery Scripting Extension 1.0 Use Cases.</cite></a> 3 December 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xquery-sx-10-use-cases-20081203\">http://www.w3.org/TR/2008/WD-xquery-sx-10-use-cases-20081203</a> ",
+ "XQUERY-UPDATE-10" : "Daniela Florescu; et al. <a href=\"http://www.w3.org/TR/2008/CR-xquery-update-10-20080801\"><cite>XQuery Update Facility 1.0.</cite></a> 1 August 2008. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/CR-xquery-update-10-20080801\">http://www.w3.org/TR/2008/CR-xquery-update-10-20080801</a> ",
+ "XQUERY-UPDATE-10-REQUIREMENTS" : "Jonathan Robie; Don Chamberlin. <a href=\"http://www.w3.org/TR/2008/CR-xquery-update-10-requirements-20080314\"><cite>XQuery Update Facility 1.0 Requirements.</cite></a> 14 March 2008. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/CR-xquery-update-10-requirements-20080314\">http://www.w3.org/TR/2008/CR-xquery-update-10-requirements-20080314</a> ",
+ "XQUERY-UPDATE-10-USE-CASES" : "Jonathan Robie; Ioana Manolescu. <a href=\"http://www.w3.org/TR/2008/CR-xquery-update-10-use-cases-20080314\"><cite>XQuery Update Facility 1.0 Use Cases.</cite></a> 14 March 2008. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/CR-xquery-update-10-use-cases-20080314\">http://www.w3.org/TR/2008/CR-xquery-update-10-use-cases-20080314</a> ",
+ "XQUERY-USE-CASES" : "Daniela Florescu; et al. <a href=\"http://www.w3.org/TR/2007/NOTE-xquery-use-cases-20070323\"><cite>XML Query Use Cases.</cite></a> 23 March 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-xquery-use-cases-20070323\">http://www.w3.org/TR/2007/NOTE-xquery-use-cases-20070323</a> ",
+ "XQUERY-XPATH-PARSING" : "Scott Boag. <a href=\"http://www.w3.org/TR/2005/WD-xquery-xpath-parsing-20050404\"><cite>Building a Tokenizer for XPath or XQuery.</cite></a> 4 April 2005. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2005/WD-xquery-xpath-parsing-20050404\">http://www.w3.org/TR/2005/WD-xquery-xpath-parsing-20050404</a> ",
+ "XQUERYX" : "Subramanian Muralidhar; Jim Melton. <a href=\"http://www.w3.org/TR/2007/REC-xqueryx-20070123\"><cite>XML Syntax for XQuery 1.0 (XQueryX).</cite></a> 23 January 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-xqueryx-20070123\">http://www.w3.org/TR/2007/REC-xqueryx-20070123</a> ",
+ "XQUERYX-11" : "Jim Melton. <a href=\"http://www.w3.org/TR/2008/WD-xqueryx-11-20081203\"><cite>XQueryX 1.1.</cite></a> 3 December 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xqueryx-11-20081203\">http://www.w3.org/TR/2008/WD-xqueryx-11-20081203</a> ",
+ "XQUPDATEUSECASES" : "Ioana Manolescu; Jonathan Robie. <a href=\"http://www.w3.org/TR/2006/WD-xqupdateusecases-20060508\"><cite>XQuery Update Facility Use Cases.</cite></a> 8 May 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-xqupdateusecases-20060508\">http://www.w3.org/TR/2006/WD-xqupdateusecases-20060508</a> ",
+ "XSL10" : "Jeremy Richman; et al. <a href=\"http://www.w3.org/TR/2001/REC-xsl-20011015/\"><cite>Extensible Stylesheet Language (XSL) Version 1.0.</cite></a> 15 October 2001. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2001/REC-xsl-20011015/\">http://www.w3.org/TR/2001/REC-xsl-20011015/</a> ",
+ "XSL11" : "Anders Berglund. <a href=\"http://www.w3.org/TR/2006/REC-xsl11-20061205\"><cite>Extensible Stylesheet Language (XSL) Version 1.1.</cite></a> 5 December 2006. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2006/REC-xsl11-20061205\">http://www.w3.org/TR/2006/REC-xsl11-20061205</a> ",
+ "XSL11-REQ" : "Paul Grosso. <a href=\"http://www.w3.org/TR/2003/WD-xsl11-req-20031217\"><cite>Extensible Stylesheet Language (XSL) Version 1.1 Requirements.</cite></a> 17 December 2003. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2003/WD-xsl11-req-20031217\">http://www.w3.org/TR/2003/WD-xsl11-req-20031217</a> ",
+ "XSLFO20-REQ" : "Klaas Bals. <a href=\"http://www.w3.org/TR/2008/WD-xslfo20-req-20080326\"><cite>Extensible Stylesheet Language (XSL) Requirements Version 2.0.</cite></a> 26 March 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xslfo20-req-20080326\">http://www.w3.org/TR/2008/WD-xslfo20-req-20080326</a> ",
+ "XSLREQ" : "Norman Walsh. <a href=\"http://www.w3.org/TR/1998/WD-XSLReq-19980511\"><cite>XSL Requirements Summary.</cite></a> 11 May 1998. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/1998/WD-XSLReq-19980511\">http://www.w3.org/TR/1998/WD-XSLReq-19980511</a> ",
+ "XSLT" : "James Clark. <a href=\"http://www.w3.org/TR/1999/REC-xslt-19991116\"><cite>XSL Transformations (XSLT) Version 1.0.</cite></a> 16 November 1999. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/1999/REC-xslt-19991116\">http://www.w3.org/TR/1999/REC-xslt-19991116</a> ",
+ "XSLT-XQUERY-SERIALIZATION" : "Michael Kay; et al. <a href=\"http://www.w3.org/TR/2007/REC-xslt-xquery-serialization-20070123\"><cite>XSLT 2.0 and XQuery 1.0 Serialization.</cite></a> 23 January 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-xslt-xquery-serialization-20070123\">http://www.w3.org/TR/2007/REC-xslt-xquery-serialization-20070123</a> ",
+ "XSLT11" : "James Clark. <a href=\"http://www.w3.org/TR/2001/WD-xslt11-20010824\"><cite>XSL Transformations (XSLT) Version 1.1.</cite></a> 24 August 2001. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2001/WD-xslt11-20010824\">http://www.w3.org/TR/2001/WD-xslt11-20010824</a> ",
+ "XSLT11REQ" : "Steve Muench. <a href=\"http://www.w3.org/TR/2000/WD-xslt11req-20000825\"><cite>XSL Transformations Requirements Version 1.1.</cite></a> 25 August 2000. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2000/WD-xslt11req-20000825\">http://www.w3.org/TR/2000/WD-xslt11req-20000825</a> ",
+ "XSLT20" : "Michael Kay. <a href=\"http://www.w3.org/TR/2007/REC-xslt20-20070123\"><cite>XSL Transformations (XSLT) Version 2.0.</cite></a> 23 January 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-xslt20-20070123\">http://www.w3.org/TR/2007/REC-xslt20-20070123</a> ",
+ "XSLT21" : "Michael Kay. <a href=\"http://www.w3.org/TR/2010/WD-xslt-21-20100511/\"><cite>XSL Transformations (XSLT) Version 2.1.</cite></a> 11 May 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2010/WD-xslt-21-20100511/\">http://www.w3.org/TR/2010/WD-xslt-21-20100511/</a> ",
+ "XSLT20REQ" : "Steve Muench; Mark Scardina. <a href=\"http://www.w3.org/TR/2001/WD-xslt20req-20010214\"><cite>XSLT Requirements Version 2.0.</cite></a> 14 February 2001. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2001/WD-xslt20req-20010214\">http://www.w3.org/TR/2001/WD-xslt20req-20010214</a> ",
+ "YACC" : "S. C. Johnson. <cite>YACC - Yet another compiler compiler.</cite> Murray Hill. 1975. Technical Report.",
+ "ZHMARK" : "<cite>标点符号用法 (Punctuation Mark Usage).</cite> 1995. 中华人民共和国国家标准 "
+};
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/xml/ReSpec.js/js/respec.js Wed Oct 31 13:10:51 2012 +0000
@@ -0,0 +1,2817 @@
+
+// ------------------------------------------------------------------------------------------ //
+// ReSpec.js -- a specification-writing tool
+// Robin Berjon, http://berjon.com/
+// ----------------------------------------------------------------------------------------- //
+// Documentation: http://dev.w3.org/2009/dap/ReSpec.js/documentation.html
+// License: http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
+// ------------------------------------------------------------------------------------------ //
+
+// SUPPORT
+// The official support channel for ReSpec is spec-prod@w3.org.
+// The archives are available at http://lists.w3.org/Archives/Public/spec-prod/
+// You can subscribe by sending email to spec-prod-request@w3.org with "subscribe" as the
+// subject line.
+// Please use that instead of emailing me (Robin) directly as the chances are that questions
+// or enhancement ideas will be shared by others. Thanks!
+
+// XXX TODO
+// - move to the top of dev. hierarchy
+// - add autolinking to headers in the output (like WebIDL)
+// - better inline dependent CSS
+// - add typographical conventions section
+// - WebIDL
+// . make it so that extended attributes on members and attributes are only wrapped if needed
+// . make processor aware of some extended attributes (e.g. Constructor)
+// . support variadic params
+// . support arrays
+// . support special operations: getter, setter, creator, deleter, caller, omittable
+// . support stringifiers
+// - add support for a test variant of the specification, based on the ideas in P+C
+// - some refactoring is in order
+// - make a widget that can save using the FS API, and inject the API without it being in the template,
+// inline CSS without hassle, etc.
+// - make a list of links to issues appear on a key combination
+// - warn on empty links to no dfn (perhaps in a special debug mode?)
+// - make everything that uses "::before" actually generate the real content instead
+
+(function () {
+if (typeof(berjon) == "undefined") berjon = {};
+var sn;
+function _errEl () {
+ var err = document.getElementById("respec-err");
+ if (err) return err.firstElementChild;
+ err = sn.element("div",
+ { id: "respec-err",
+ style: "position: fixed; width: 350px; top: 10px; right: 10px; border: 3px double #f00; background: #fff",
+ "class": "removeOnSave" },
+ document.body);
+ return sn.element("ul", {}, err);
+}
+function error (str) {
+ sn.element("li", { style: "color: #c00" }, _errEl(), str);
+}
+function warning (str) {
+ sn.element("li", { style: "color: #666" }, _errEl(), str);
+}
+function isArray (obj) {
+ return Object.prototype.toString.call(obj) == '[object Array]'
+}
+function joinAnd (arr) {
+ var last = arr.pop();
+ arr[arr.length - 1] += " and " + last;
+ return arr.join(", ");
+}
+berjon.respec = function () {
+ for (var k in this.status2text) {
+ if (this.status2long[k]) continue;
+ this.status2long[k] = this.status2text[k];
+ }
+};
+berjon.respec.prototype = {
+ title: null,
+ additionalCopyrightHolders: null,
+ overrideCopyright: null,
+ editors: [],
+ authors: [],
+
+ recTrackStatus: ["FPWD", "WD", "LC", "CR", "PR", "PER", "REC"],
+ noTrackStatus: ["MO", "unofficial", "base"],
+ status2text: {
+ NOTE: "Note",
+ "WG-NOTE": "Working Group Note",
+ "CG-NOTE": "Co-ordination Group Note",
+ "IG-NOTE": "Interest Group Note",
+ "Member-SUBM": "Member Submission",
+ "Team-SUBM": "Team Submission",
+ XGR: "Incubator Group Report",
+ MO: "Member-Only Document",
+ ED: "Editor's Draft",
+ FPWD: "Working Draft",
+ WD: "Working Draft",
+ "FPWD-NOTE": "Working Draft",
+ "WD-NOTE": "Working Draft",
+ "LC-NOTE": "Working Draft",
+ LC: "Working Draft",
+ CR: "Candidate Recommendation",
+ PR: "Proposed Recommendation",
+ PER: "Proposed Edited Recommendation",
+ REC: "Recommendation",
+ RSCND: "Rescinded Recommendation",
+ unofficial: "Unofficial Draft",
+ base: "Document",
+ "draft-finding": "Draft TAG Finding",
+ "finding": "TAG Finding"
+ },
+ status2long: {
+ FPWD: "First Public Working Draft",
+ "FPWD-NOTE": "First Public Working Draft",
+ LC: "Last Call Working Draft",
+ "LC-NOTE": "Last Call Working Draft"
+ },
+ status2maturity: {
+ FPWD: "WD",
+ LC: "WD",
+ "FPWD-NOTE": "WD",
+ "WD-NOTE": "WD",
+ "LC-NOTE": "LC",
+ "IG-NOTE": "NOTE",
+ "WG-NOTE": "NOTE"
+ },
+
+ isLocal: false,
+
+ loadAndRun: function () {
+ var scripts = document.querySelectorAll("script[src]");
+ var rs, base;
+ for (var i = 0; i < scripts.length; i++) {
+ var src = scripts[i].src;
+ if (/\/js\/respec\.js$/.test(src)) {
+ rs = scripts[i];
+ base = src.replace(/js\/respec\.js$/, "");
+ }
+ }
+ this.base = base;
+ if (base.indexOf("file://") == 0) this.isLocal = true;
+
+ var loaded = [];
+ var deps = ["js/simple-node.js", "js/shortcut.js", "bibref/biblio.js", "js/sh_main.min.js"];
+ var head = document.getElementsByTagName('head')[0];
+ var obj = this;
+ for (var i = 0; i < deps.length; i++) {
+ var dep = deps[i];
+ var sel = document.createElement('script');
+ sel.type = 'text/javascript';
+ sel.src = base + dep;
+ sel.setAttribute("class", "remove");
+ sel.onload = function (ev) {
+ loaded.push(ev.target.src);
+ if (obj.isLocal && ev.target.src.indexOf("sh_main") > 0) {
+ // dirty hack to fix local loading of SHJS
+ this.oldSHLoad = window.sh_load;
+ window.sh_load = function (language, element, prefix, suffix) {
+ if (language in sh_requests) {
+ sh_requests[language].push(element);
+ return;
+ }
+ sh_requests[language] = [element];
+ var url = prefix + 'sh_' + language + suffix;
+ var shLang = document.createElement('script');
+ shLang.type = 'text/javascript';
+ shLang.src = url;
+ shLang.setAttribute("class", "remove");
+ shLang.onload = function (ev) {
+ var elements = sh_requests[language];
+ for (var i = 0; i < elements.length; i++) {
+ sh_highlightElement(elements[i], sh_languages[language]);
+ }
+ };
+ head.appendChild(shLang);
+ };
+ }
+ if (loaded.length == deps.length) {
+ sn = new berjon.simpleNode({
+ "": "http://www.w3.org/1999/xhtml",
+ "x": "http://www.w3.org/1999/xhtml"
+ }, document);
+ obj.run();
+ }
+ };
+ head.appendChild(sel);
+ }
+ },
+
+ run: function () {
+ document.body.style.display = "none";
+ try {
+ this.extractConfig();
+ if (respecConfig.preProcess) {
+ for (var i = 0; i < respecConfig.preProcess.length; i++) respecConfig.preProcess[i].apply(this);
+ }
+ this.makeTemplate();
+
+ // This is done REALLY early in case the transform ends up
+ // needing to include something
+ this.doTransforms() ;
+
+ // This is done early so that if other data gets embedded it will be
+ // processed
+ this.includeFiles();
+
+ this.dfn();
+ this.inlines();
+
+ this.webIDL();
+ this.examples();
+
+ // only process best practices if element with class
+ // practicelab found, do not slow down non best-practice
+ // docs.
+ // doBestPractices must be called before makeTOC, fjh
+ // this might not work with old browsers like IE 8
+
+ var bpnode = document.getElementsByClassName("practicelab");
+ if(bpnode.length > 0) this.doBestPractices();
+
+ this.informative();
+ this.fixHeaders();
+
+ this.makeTOC();
+ this.idHeaders();
+
+ if (respecConfig.postProcess) {
+ for (var i = 0; i < respecConfig.postProcess.length; i++) respecConfig.postProcess[i].apply(this);
+ }
+
+ // if (this.doMicroData) this.makeMicroData();
+ if (this.doRDFa) this.makeRDFa();
+ this.makeSectionRefs(); // allow references to sections using name for text, fjh
+ this.unHTML5();
+ this.removeRespec();
+
+ // shortcuts
+ var obj = this;
+ // shortcut.add("Alt+H", function () { obj.toHTML(); });
+ // shortcut.add("Shift+Alt+H", function () { obj.toHTMLSource(); });
+ shortcut.add("Ctrl+Shift+Alt+S", function () { obj.showSaveOptions(); });
+ shortcut.add("Esc", function () { obj.hideSaveOptions(); });
+ }
+ catch (e) {
+ document.body.style.display = "inherit";
+ error("Processing error: " + e);
+ if (typeof(console) != "undefined" && console.log) console.log(e);
+ }
+ document.body.style.display = "inherit";
+ },
+
+ makeRDFa: function () {
+ var abs = document.getElementById("abstract");
+ if (abs) {
+ var rel = 'dcterms:abstract' ;
+ var ref = abs.getAttribute('property') ;
+ if (ref) {
+ rel = ref + ' ' + rel ;
+ }
+ abs.setAttribute('property', rel) ;
+ abs.setAttribute('datatype', '') ;
+ }
+ // annotate sections with Section data
+ var secs = document.querySelectorAll("section");
+ for (var i = 0; i < secs.length; i++) {
+ // if the section has an id, use that. if not, look at the first child for an id
+ var about = '' ;
+ // the first child should be a header - that's what we will annotate
+ var fc = secs[i].firstElementChild;
+ var ref = secs[i].getAttribute('id') ;
+ if ( ref ) {
+ about = '#' + ref ;
+ } else {
+ if (fc) {
+ ref = fc.getAttribute('id') ;
+ if (ref) {
+ about = '#' + ref;
+ }
+ }
+ }
+ if (about != '') {
+ secs[i].setAttribute('typeof', 'bibo:Chapter') ;
+ secs[i].setAttribute('resource', about) ;
+ secs[i].setAttribute('rel', "bibo:chapter" ) ;
+ }
+ }
+ },
+
+ saveMenu: null,
+ showSaveOptions: function () {
+ var obj = this;
+ this.saveMenu = sn.element("div",
+ { style: "position: fixed; width: 400px; top: 10px; padding: 1em; border: 5px solid #90b8de; background: #fff" },
+ document.body);
+ sn.element("h4", {}, this.saveMenu, "Save Options");
+ var butH = sn.element("button", {}, this.saveMenu, "Save as HTML");
+ butH.onclick = function () { obj.hideSaveOptions(); obj.toHTML(); };
+ var butS = sn.element("button", {}, this.saveMenu, "Save as HTML (Source)");
+ butS.onclick = function () { obj.hideSaveOptions(); obj.toHTMLSource(); };
+ var butS = sn.element("button", {}, this.saveMenu, "Save as XHTML");
+ butS.onclick = function () { obj.hideSaveOptions(); obj.toXHTML(); };
+ var butS = sn.element("button", {}, this.saveMenu, "Save as XHTML (Source)");
+ butS.onclick = function () { obj.hideSaveOptions(); obj.toXHTMLSource(); };
+ if (this.diffTool && (this.previousDiffURI || this.previousURI) ) {
+ var butD = sn.element("button", {}, this.saveMenu, "Diffmark");
+ butD.onclick = function () { obj.hideSaveOptions(); obj.toDiffHTML(); };
+ }
+
+ },
+
+ hideSaveOptions: function () {
+ if (!this.saveMenu) return;
+ this.saveMenu.parentNode.removeChild(this.saveMenu);
+ },
+
+ toString: function () {
+ var str = "<!DOCTYPE html";
+ var dt = document.doctype;
+ if (dt && dt.publicId) {
+ str += " PUBLIC '" + dt.publicId + "' '" + dt.systemId + "'";
+ }
+ else { // when HTML5 is allowed we can remove this
+ str += " PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'";
+ }
+ str += ">\n";
+ str += "<html";
+ var ats = document.documentElement.attributes;
+ var prefixAtr = '' ;
+
+ for (var i = 0; i < ats.length; i++) {
+ var an = ats[i].name;
+ if (an == "xmlns" || an == "xml:lang") continue;
+ if (an == "prefix") {
+ prefixAtr = ats[i].value;
+ continue;
+ }
+ str += " " + an + "=\"" + this._esc(ats[i].value) + "\"";
+ }
+ if (this.doRDFa) {
+ if (prefixAtr != '') prefixAtr += ' ';
+ if (this.doRDFa != "1.1") {
+ prefixAtr += "dcterms: http://purl.org/dc/terms/ bibo: http://purl.org/ontology/bibo/ foaf: http://xmlns.com/foaf/0.1/ xsd: http://www.w3.org/2001/XMLSchema#";
+ } else {
+ prefixAtr += "bibo: http://purl.org/ontology/bibo/";
+ }
+ str += " prefix=\"" + this._esc(prefixAtr) + "\"";
+ str += " typeof=\"bibo:Document\"";
+ }
+
+ str += ">\n";
+ str += document.documentElement.innerHTML;
+ str += "</html>";
+ return str;
+ },
+
+ toXML: function () {
+ var str = "<?xml version='1.0' encoding='UTF-8'?>\n<!DOCTYPE html";
+ var dt = document.doctype;
+ if (dt && dt.publicId) {
+ str += " PUBLIC '" + dt.publicId + "' '" + dt.systemId + "'";
+ }
+ else {
+ if (this.doRDFa) {
+ if (this.doRDFa == "1.1") {
+ // use the standard RDFa 1.1 doctype
+ str += " PUBLIC '-//W3C//DTD XHTML+RDFa 1.1//EN' 'http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd'";
+ } else {
+ // use the standard RDFa doctype
+ str += " PUBLIC '-//W3C//DTD XHTML+RDFa 1.0//EN' 'http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd'";
+ }
+ } else {
+ str += " PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'";
+ }
+ }
+ str += ">\n";
+ str += "<html";
+ var ats = document.documentElement.attributes;
+ var prefixAtr = '' ;
+
+ var hasxmlns = false;
+ for (var i = 0; i < ats.length; i++) {
+ var an = ats[i].name;
+ if (an == "lang") continue;
+ if (an == "xmlns") hasxmlns = true;
+ if (an == "prefix") {
+ prefixAtr = ats[i].value;
+ continue;
+ }
+ str += " " + an + "=\"" + this._esc(ats[i].value) + "\"";
+ }
+ if (!hasxmlns) str += ' xmlns="http://www.w3.org/1999/xhtml"';
+ if (this.doRDFa) {
+ if (this.doRDFa != "1.1") {
+ str += " xmlns:dcterms='http://purl.org/dc/terms/' xmlns:bibo='http://purl.org/ontology/bibo/' xmlns:foaf='http://xmlns.com/foaf/0.1/' xmlns:xsd='http://www.w3.org/2001/XMLSchema#'";
+ // there was already some prefix information
+ if (prefixAtr != '') {
+ var list = prefixAtr.split(/\s+/) ;
+ for (var i = 0; i < list.length; i += 2) {
+ var n = list[i] ;
+ n = n.replace(/:$/,'');
+ str += ' xmlns:'+n+'="' + list[i+1] + '"';
+ }
+ }
+ str += ' version="XHTML+RDFa 1.0"';
+ } else {
+ if (prefixAtr != '') {
+ str += " prefix='" + prefixAtr + " bibo: http://purl.org/ontology/bibo/'" ;
+ } else {
+ str += " prefix='bibo: http://purl.org/ontology/bibo/'" ;
+ }
+ }
+ }
+ str += " typeof=\"bibo:Document\"";
+ str += ">\n";
+ // walk the entire DOM tree grabbing nodes and emitting them - possibly modifying them
+ // if they need the funny closing tag
+ var pRef = this ;
+ var selfClosing = {};
+ "br img input area base basefont col isindex link meta param hr".split(" ").forEach(function (n) {
+ selfClosing[n] = true;
+ });
+ var noEsc = [false];
+ var dumpNode = function (node) {
+ var out = '';
+ // if the node is the document node.. process the children
+ if ( node.nodeType == 9 || ( node.nodeType == 1 && node.nodeName.toLowerCase() == 'html' ) ) {
+ for (var i = 0; i < node.childNodes.length; i++) out += dumpNode(node.childNodes[i]) ;
+ }
+ // element
+ else if (1 === node.nodeType) {
+ var ename = node.nodeName.toLowerCase() ;
+ out += '<' + ename ;
+ for (var i = 0; i < node.attributes.length; i++) {
+ var atn = node.attributes[i]
+ out += " " + atn.name + "=\"" + pRef._esc(atn.value) + "\"";
+ }
+ if (selfClosing[ename]) {
+ out += ' />';
+ }
+ else {
+ out += '>';
+ // XXX removing this, as it does not seem correct at all
+ // if ( ename == 'pre' ) {
+ // out += "\n" + node.innerHTML;
+ // }
+ // else {
+ // console.log("NAME: " + ename);
+ noEsc.push(ename === "style" || ename === "script");
+ // console.log(noEsc);
+ for (var i = 0; i < node.childNodes.length; i++) out += dumpNode(node.childNodes[i]);
+ noEsc.pop();
+ // }
+ out += '</' + ename + '>';
+ }
+ }
+ // comments
+ else if (8 === node.nodeType) {
+ out += "\n<!-- " + node.nodeValue + " -->\n";
+ }
+ // text or cdata
+ else if (3 === node.nodeType || 4 === node.nodeType) {
+ // console.log("TEXT: " + noEsc[noEsc.length - 1]);
+ out += noEsc[noEsc.length - 1] ? node.nodeValue : pRef._esc(node.nodeValue);
+ }
+ // we don't handle other types for the time being
+ else {
+ warning("Cannot handle serialising nodes of type: " + node.nodeType);
+ }
+ return out;
+ };
+ var node = document.documentElement;
+ str += dumpNode(document.documentElement) ;
+ str += "</html>";
+ return str;
+ },
+
+ toDiffHTMLSource: function () {
+
+ },
+
+ toDiffHTML: function () {
+ // create a diff marked version against the previousURI
+ // strategy - open a window in which there is a form with the
+ // data needed for diff marking - submit the form so that the response populates
+ // page with the diff marked version
+ var base = window.location.href;
+ base = base.replace(/\/[^\/]*$/, "/");
+ var str = "<!DOCTYPE html>\n";
+ str += "<html";
+ var ats = document.documentElement.attributes;
+ for (var i = 0; i < ats.length; i++) {
+ str += " " + ats[i].name + "=\"" + this._esc(ats[i].value) + "\"";
+ }
+ str += ">\n";
+ str += "<head><title>diff form</title></head>\n";
+ str += "<body><form name='form' method='POST' action='" + this.diffTool + "'>\n";
+ str += "<input type='hidden' name='base' value='" + base + "'>\n";
+ if (this.previousDiffURI) {
+ str += "<input type='hidden' name='oldfile' value='" + this.previousDiffURI + "'>\n";
+ } else {
+ str += "<input type='hidden' name='oldfile' value='" + this.previousURI + "'>\n";
+ }
+ str += '<input type="hidden" name="newcontent" value="' + this._esc(this.toString()) + '">\n';
+ str += '<p>Please wait...</p>';
+ str += "</form></body></html>\n";
+
+
+ var x = window.open() ;
+ x.document.write(str) ;
+ x.document.close() ;
+ x.document.form.submit() ;
+ },
+
+ toHTML: function () {
+ var x = window.open();
+ x.document.write(this.toString());
+ x.document.close();
+ },
+
+ toHTMLSource: function () {
+ var x = window.open();
+ x.document.write("<pre>" + this._esc(this.toString()) + "</pre>");
+ x.document.close();
+ },
+
+ toXHTML: function () {
+ var x = window.open();
+ x.document.write(this.toXML()) ;
+ x.document.close();
+ },
+
+ toXHTMLSource: function () {
+ var x = window.open();
+ x.document.write("<pre>" + this._esc(this.toXML()) + "</pre>");
+ x.document.close();
+ },
+
+ // --- METADATA -------------------------------------------------------
+ extractConfig: function () {
+ this.title = document.title;
+ var cfg;
+ if (respecConfig) cfg = respecConfig;
+ else cfg = {};
+ // defaulting
+ if (!cfg.specStatus) cfg.specStatus = "ED";
+ // the below is experimental, use this if it fails:
+ // cfg.publishDate = new Date();
+ if (!cfg.publishDate) {
+ cfg.publishDate = this._parseLastModified(document.lastModified);
+ }
+ else {
+ cfg.publishDate = this._parseDate(cfg.publishDate);
+ }
+ if (cfg.previousPublishDate) cfg.previousPublishDate = this._parseDate(cfg.previousPublishDate);
+ if (cfg.previousPublishDate && ! cfg.previousMaturity && cfg.specStatus.indexOf("finding") === -1)
+ error("Previous date is set, but not previousMaturity");
+ if (cfg.lcEnd) cfg.lcEnd = this._parseDate(cfg.lcEnd);
+ if (cfg.crEnd) cfg.crEnd = this._parseDate(cfg.crEnd);
+ if (cfg.specStatus == "LC" && !cfg.lcEnd) error("If specStatus is set to LC, then lcEnd must be defined");
+ if (cfg.specStatus == "CR" && !cfg.crEnd) error("If specStatus is set to CR, then crEnd must be defined");
+ if (!cfg.editors) cfg.editors = [];
+ if (!cfg.authors) cfg.authors = [];
+ if (!cfg.alternateFormats) cfg.alternateFormats = [];
+ if (cfg.inlineCSS === undefined) cfg.inlineCSS = true;
+ if (!cfg.noIDLSorting) cfg.noIDLSorting = false;
+ if (cfg.noIDLIn === undefined) cfg.noIDLIn = true;
+ if (cfg.tocIntroductory === undefined) cfg.tocIntroductory = false;
+ if (!cfg.maxTocLevel) cfg.maxTocLevel = 0;
+ if (!cfg.diffTool) cfg.diffTool = 'http://www5.aptest.com/standards/htmldiff/htmldiff.pl';
+ if (!cfg.noRecTrack) cfg.noRecTrack = false;
+ if (!cfg.doRDFa) cfg.doRDFa = false;
+ for (var k in cfg) this[k] = cfg[k];
+ this.isRecTrack = cfg.noRecTrack ? false : this.recTrackStatus.indexOf(this.specStatus) >= 0;
+ this.isNoTrack = this.noTrackStatus.indexOf(this.specStatus) >= 0;
+ // this.specStatus = this._getMetaFor("http://berjon.com/prop/spec-status", "ED");
+ // this.shortName = this._getMetaFor("http://berjon.com/prop/short-name", "xxx-xxx");
+ // this.publishDate = this._getDateFor("head > time[itemprop='http://berjon.com/prop/publish-date']");
+ // this.prevPublishDate = this._getDateFor("head > time[itemprop='http://berjon.com/prop/previous-publish-date']");
+ },
+
+ _getMetaFor: function (iProp, def) {
+ var meta = document.querySelector("head > meta[itemprop='" + iProp + "']");
+ if (meta) return meta.getAttribute("content");
+ else return def;
+ },
+
+ _getDateFor: function (sel) {
+ var el = document.querySelector(sel);
+ if (el) {
+ var val = el.getAttribute('datetime');
+ return new Date(val.substr(0, 4), val.substr(5, 2), val.substr(8, 2));
+ }
+ else {
+ return new Date();
+ }
+ },
+
+ // --- W3C BASICS -----------------------------------------------------------------------------------------
+ makeTemplate: function () {
+ this.rootAttr();
+ this.addCSS();
+ this.makeHeaders();
+ this.makeAbstract();
+ this.makeSotD();
+ this.makeConformance();
+ },
+
+ rootAttr: function () {
+ document.documentElement.setAttribute("lang", "en");
+ document.documentElement.setAttribute("dir", "ltr");
+ if (this.doRDFa) {
+ document.documentElement.setAttribute("about", "");
+ document.documentElement.setAttribute("property", "dcterms:language");
+ document.documentElement.setAttribute("content", "en");
+ }
+ },
+
+ addCSS: function () {
+ if (this.extraCSS) {
+ for (var i = 0; i < this.extraCSS.length; i++) this._insertCSS(this.extraCSS[i], this.inlineCSS);
+ }
+ var statStyle = this.specStatus;
+ if (statStyle == "FPWD" || statStyle == "LC" || statStyle == "WD-NOTE" || statStyle == "LC-NOTE" || statStyle == "FPWD-NOTE") {
+ statStyle = "WD";
+ }
+ else if (statStyle === "finding" || statStyle === "draft-finding") statStyle = "base";
+// else if ( statStyle == "WD-NOTE" || statStyle == "LC-NOTE"
+// || statStyle == "FPWD-NOTE") {
+// statStyle = "WG-NOTE";
+// }
+ var css;
+ if (statStyle == "unofficial") {
+ css = "http://www.w3.org/StyleSheets/TR/w3c-unofficial";
+ }
+ else if (statStyle == "base") {
+ css = "http://www.w3.org/StyleSheets/TR/base";
+ }
+ else {
+ css = "http://www.w3.org/StyleSheets/TR/W3C-" + statStyle;// + ".css";
+ }
+ this._insertCSS(css, false);
+ },
+
+ doTransforms: function() {
+ var divs = document.querySelectorAll("[data-transform]");
+ for (var i = 0; i < divs.length; i++) {
+ var div = divs[i];
+ var content = div.innerHTML ;
+ var flist = div.getAttribute('data-transform');
+ if (flist) {
+ var methods = flist.split(/\s+/) ;
+ for (var j = 0; j < methods.length; j++) {
+ var call = 'content = ' + methods[j] + '(this,content)' ;
+ try {
+ eval(call) ;
+ } catch (e) {
+ warning('call to ' + call + ' failed with ' + e) ;
+ }
+ }
+ div.removeAttribute('data-transform') ;
+ }
+ if (content) {
+ div.innerHTML = content ;
+ }
+ }
+ },
+
+ includeFiles: function() {
+ var divs = document.querySelectorAll("[data-include]");
+ for (var i = 0; i < divs.length; i++) {
+ var div = divs[i];
+ var URI = div.getAttribute('data-include');
+ var content = this._readFile(URI) ;
+ if (content) {
+ var flist = div.getAttribute('data-oninclude');
+ if (flist) {
+ var methods = flist.split(/\s+/) ;
+ for (var j = 0; j < methods.length; j++) {
+ var call = 'content = ' + methods[j] + '(this,content,URI)' ;
+ try {
+ eval(call) ;
+ } catch (e) {
+ warning('call to ' + call + ' failed with ' + e) ;
+ }
+ }
+ div.removeAttribute('data-oninclude') ;
+ }
+ div.removeAttribute('data-include') ;
+ div.innerHTML = content ;
+ }
+ }
+ },
+
+ // single function used to display people information for editors,
+ // authors, etc (fjh 2009-12-04)
+
+ showPeople: function(name, people) {
+ var header = "";
+
+ if (people.length == 0) return header;
+ var re = '' ;
+ var rp = '' ;
+ var rl = '' ;
+ var rt = '' ;
+ var rm = '' ;
+ var rn = '' ;
+ var rwu = '' ;
+ var rpu = '' ;
+ if ( this.doRDFa ) {
+ if ( name == 'Editor' ) {
+ re = " rel='bibo:editor'";
+ if (this.doRDFa == "1.1") {
+ re += " inlist=''" ;
+ }
+ rn = " property='foaf:name'";
+ rm = " rel='foaf:mbox'";
+ rp = " typeof='foaf:Person'";
+ rwu = " rel='foaf:workplaceHomepage'";
+ rpu = " rel='foaf:homepage'";
+ } else if (name == 'Author' ) {
+ re = " rel='dcterms:contributor'";
+ rn = " property='foaf:name'";
+ rm = " rel='foaf:mbox'";
+ rp = " typeof='foaf:Person'";
+ rwu = " rel='foaf:workplaceHomepage'";
+ rpu = " rel='foaf:homepage'";
+ }
+ }
+
+ if (people.length > 1) {
+ header += "<dt" + rl + ">" + name + "s:</dt>";
+ } else {
+ header += "<dt>" + name + ":</dt>";
+ }
+
+
+ for (var i = 0; i < people.length; i++) {
+ var pers = people[i];
+ if (this.doRDFa) {
+ header += "<dd" + re +"><span" + rp + ">";
+ } else {
+ header += "<dd>";
+ }
+ if (pers.url) {
+ if (this.doRDFa) {
+ header += "<a" + rpu + rn + " content='" + pers.name + "' href='" + pers.url + "'>" + pers.name + "</a>";
+ } else {
+ header += "<a href='" + pers.url + "'>"+ pers.name + "</a>";
+ }
+ } else {
+ header += "<span" + rn + ">" + pers.name + "</span>";
+ }
+ if (pers.company) {
+ header += ", ";
+ if (pers.companyURL) {
+ header += "<a" + rwu + " href='" + pers.companyURL + "'>" + pers.company + "</a>";
+ } else {
+ header += pers.company;
+ }
+ }
+ if (pers.mailto) {
+ header += ", ";
+ header += " <span class='ed_mailto'><a" + rm + " href='mailto:" + pers.mailto + "'>" + pers.mailto + "</a></span> ";
+ }
+ if (pers.note) {
+ header += " ( " + pers.note + " )";
+ }
+ if (this.doRDFa) {
+ header += "</span>\n";
+ }
+ header += "</dd>\n";
+ }
+ return header;
+ },
+
+ makeTAGHeaders: function () {
+ var base = "http://www.w3.org/2001/tag/doc/",
+ latestVersion = base + this.shortName,
+ thisVersion = latestVersion + "-" + this._concatDate(this.publishDate, "-"),
+ header = "<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>";
+ header += "<h1 class='title' id='title'>" + this.title + "</h1>";
+ if (this.subtitle) header += "<h2 id='subtitle'>" + this.subtitle + "</h2>";
+ header += "<h2>" + this.status2text[this.specStatus] + " " + this._humanDate(this.publishDate) + "</h2><dl>";
+ header += "<dt>This version:</dt><dd><a href='" + thisVersion + "'>" + thisVersion + "</a></dd>\n" +
+ "<dt>Latest published version:</dt><dd><a href='" + latestVersion + "'>" + latestVersion + "</a></dd>";
+ if (this.edDraftURI) {
+ header += "<dt>Latest editor's draft:</dt><dd><a href='" + this.edDraftURI + "'>" + this.edDraftURI + "</a></dd>";
+ }
+ if (this.previousPublishDate) {
+ var prevVersion = latestVersion + "-" + this._concatDate(this.previousPublishDate, "-");
+ header += "<dt>Previous version:</dt><dd><a href='" + prevVersion + "'>" + prevVersion + "</a></dd>";
+ }
+ if(this.editors.length == 0) {
+ header += "<dt>" + "Editor" + ":</dt>";
+ error("There must be at least one editor.");
+ }
+ header += this.showPeople("Editor", this.editors);
+ header += this.showPeople("Author", this.authors);
+ header += "</dl><p class='copyright'>";
+ header +=
+ "<a href='http://www.w3.org/Consortium/Legal/ipr-notice#Copyright'>Copyright</a> © " ;
+ if (this.copyrightStart && this.copyrightStart != this.publishDate.getFullYear()) header += this.copyrightStart + '-';
+ header += this.publishDate.getFullYear();
+ header += " <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. " +
+ "W3C <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>";
+ return header;
+ },
+
+ makeNormalHeaders: function () {
+ var mat = (this.status2maturity[this.specStatus]) ? this.status2maturity[this.specStatus] : this.specStatus;
+ var thisVersion = "http://www.w3.org/TR/" + this.publishDate.getFullYear() + "/" + mat + "-" +
+ this.shortName + "-" + this._concatDate(this.publishDate) + "/";
+ if (this.specStatus == "ED") thisVersion = this.edDraftURI;
+ var latestVersion, prevVersion;
+ if (this.previousPublishDate) {
+ var pmat = (this.status2maturity[this.previousMaturity]) ? this.status2maturity[this.previousMaturity] : this.previousMaturity;
+ if (!this.previousURI) {
+ this.previousURI = "http://www.w3.org/TR/" + this.previousPublishDate.getFullYear() + "/" + pmat + "-" + this.shortName + "-" + this._concatDate(this.previousPublishDate) + "/";
+ }
+ if (this.doRDFa) {
+ prevVersion = "<a rel='dcterms:replaces' href='" + this.previousURI + "'>" + this.previousURI + "</a>";
+ } else {
+ prevVersion = "<a href='" + this.previousURI + "'>" + this.previousURI + "</a>";
+ }
+ // var latestURI = "http://www.w3.org/TR/" + this.shortName + "/";
+ // latestVersion = "<a href='" + latestURI + "'>" + latestURI + "</a>";
+ }
+ else {
+ prevVersion = "none";
+ // latestVersion = "none";
+ }
+ var latestURI = "http://www.w3.org/TR/" + this.shortName + "/";
+ latestVersion = "<a href='" + latestURI + "'>" + latestURI + "</a>";
+ var header = "<div class='head'><p>";
+ if (this.specStatus != "unofficial")
+ header += "<a href='http://www.w3.org/'><img width='72' height='48' src='http://www.w3.org/Icons/w3c_home' alt='W3C'/></a>";
+ if (this.specStatus == 'XGR')
+ header += "<a href='http://www.w3.org/2005/Incubator/XGR/'><img alt='W3C Incubator Report' src='http://www.w3.org/2005/Incubator/images/XGR' height='48' width='160'/></a>";
+ if ( this.doRDFa ) {
+ header +=
+ "<h1 property='dcterms:title' class='title' id='title'>" + this.title + "</h1>" ;
+ if (this.subtitle) {
+ header += "<h2 property='bibo:subtitle' id='subtitle'>" + this.subtitle + "</h2>" ;
+ }
+ header +=
+ "<h2 property='dcterms:issued' datatype='xsd:dateTime' content='" + this._ISODate(this.publishDate) + "'>" + (this.specStatus == "unofficial" ? "" : "W3C ") +
+ this.status2text[this.specStatus] + " " + this._humanDate(this.publishDate) + "</h2><dl>";
+ } else {
+ header +=
+ "<h1 class='title' id='title'>" + this.title + "</h1>" ;
+ if (this.subtitle) {
+ header += "<h2 id='subtitle'>" + this.subtitle + "</h2>" ;
+ }
+ header +=
+ "<h2>" + (this.specStatus == "unofficial" ? "" : "W3C ") +
+ this.status2text[this.specStatus] + " " + this._humanDate(this.publishDate) + "</h2><dl>";
+ }
+ if (!this.isNoTrack) {
+ header += "<dt>This version:</dt><dd><a href='" + thisVersion + "'>" + thisVersion + "</a></dd>" +
+ "<dt>Latest published version:</dt><dd>" + latestVersion + "</dd>";
+ if (this.edDraftURI) {
+ header += "<dt>Latest editor's draft:</dt><dd><a href='" + this.edDraftURI + "'>" + this.edDraftURI + "</a></dd>";
+ }
+ }
+ if (this.testSuiteURI) {
+ header += "<dt>Test suite:</dt><dd><a href='" + this.testSuiteURI + "'>" + this.testSuiteURI + "</a></dd>";
+ }
+ if (this.implementationReportURI) {
+ header += "<dt>Implementation report:</dt><dd><a href='" + this.implementationReportURI + "'>" + this.implementationReportURI + "</a></dd>";
+ }
+ if (this.specStatus != "FPWD" && this.specStatus != "FPWD-NOTE" &&
+ !this.isNoTrack) {
+ if (!this.prevED) {
+ header += "<dt>Previous version:</dt><dd>" + prevVersion + "</dd>";
+ } else {
+ header += "<dt>Previous editor's draft:</dt><dd>" + prevED + "</dd>";
+ }
+ }
+
+ if (this.prevRecShortname) {
+ var prevRecURI = this.prevRecURI ? this.prevRecURI : "http://www.w3.org/TR/" + this.prevRecShortname + "/";
+ if (this.prevRecHeader) {
+ header += "<dt>" + this.prevRecHeader;
+ } else {
+ header += "<dt>Latest recommendation" ;
+ }
+ header += ":</dt><dd>" +
+ '<a href="' + prevRecURI + '">' + prevRecURI + "</a></dd>";
+ }
+
+ if(this.editors.length == 0) {
+ header += "<dt>" + "Editor" + ":</dt>";
+ error("There must be at least one editor.");
+ }
+ header += this.showPeople("Editor", this.editors);
+ header += this.showPeople("Author", this.authors);
+ header += "</dl>";
+
+ if (this.errata) {
+ header += '<p>Please refer to the <a href="' + this.errata + '">errata</a> for this document, which may include some normative corrections.</p>';
+ }
+
+ if (this.alternateFormats.length > 0) {
+ var len = this.alternateFormats.length ;
+ if (len == 1) {
+ header += '<p>This document is also available in this non-normative format: ';
+ } else {
+ header += '<p>This document is also available in these non-normative formats: ';
+ }
+ for (var f = 0; f < len; f++) {
+ if (f > 0) {
+ if ( len == 2) {
+ header += ' ';
+ } else {
+ header += ', ' ;
+ }
+ if (f == len - 1) {
+ header += 'and ';
+ }
+ }
+ var ref = this.alternateFormats[f] ;
+ header += "<a href='" + ref.uri + "'>" + ref.label + "</a>" ;
+ }
+ header += '.</p>';
+ }
+
+ if (this.specStatus == "REC")
+ header += '<p>The English version of this specification is the only normative version. Non-normative <a href="http://www.w3.org/Consortium/Translation/">translations</a> may also be available.</p>';
+
+ if (this.specStatus == "unofficial") {
+ var copyright;
+ if (this.additionalCopyrightHolders) copyright = "<p class='copyright'>" + this.additionalCopyrightHolders + "</p>";
+ else if (this.overrideCopyright) copyright = this.overrideCopyright;
+ else copyright = "<p class='copyright'>This document is licensed under a <a class='subfoot' href='http://creativecommons.org/licenses/by/3.0/' rel='license'>Creative Commons Attribution 3.0 License</a>.</p>";
+ header += copyright;
+ }
+ else {
+ if (this.overrideCopyright) {
+ header += this.overrideCopyright;
+ }
+ else {
+ header += "<p class='copyright'>";
+ if (this.doRDFa) {
+ header += "<a rel='license' href='http://www.w3.org/Consortium/Legal/ipr-notice#Copyright'>Copyright</a> © ";
+ }
+ else {
+ header += "<a href='http://www.w3.org/Consortium/Legal/ipr-notice#Copyright'>Copyright</a> © ";
+ }
+ if (this.copyrightStart) {
+ header += this.copyrightStart + '-';
+ }
+ header += this.publishDate.getFullYear();
+ if (this.additionalCopyrightHolders) header += " " + this.additionalCopyrightHolders + " &";
+ if (this.doRDFa) {
+ header += " <span rel='dcterms:publisher'><span typeof='foaf:Organization'><a rel='foaf:homepage' property='foaf:name' content='World Wide Web Consortium' href='http://www.w3.org/'><acronym title='World Wide Web Consortium'>W3C</acronym></a><sup>®</sup></span></span> ";
+ } else {
+ header += " <a href='http://www.w3.org/'><acronym title='World Wide Web Consortium'>W3C</acronym></a><sup>®</sup> ";
+ }
+ header +=
+ "(<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. " +
+ "W3C <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>";
+
+ }
+ }
+ header += "<hr/></div>";
+ return header;
+ },
+
+ makeHeaders: function () {
+ var header;
+ if (this.specStatus === "finding" || this.specStatus === "draft-finding") header = this.makeTAGHeaders();
+ else header = this.makeNormalHeaders();
+ var tmp = sn.element("div");
+ tmp.innerHTML = header;
+ document.body.insertBefore(tmp.firstChild, document.body.firstChild);
+ },
+
+ makeAbstract: function () {
+ var abs = document.getElementById("abstract");
+ if (!abs) error("Document must have one element with ID 'abstract'");
+ if (abs.getElementsByTagName("p").length === 0) {
+ // warning("The abstract section should contain a <p> element rather than text directly. Attempting to insert one.");
+ var p = sn.element("p");
+ sn.copyChildren(abs, p);
+ abs.appendChild(p);
+ }
+ var h2 = sn.element("h2", {}, null, "Abstract");
+ abs.insertBefore(h2, abs.firstChild);
+ sn.addClass(abs, "introductory");
+ },
+
+ makeSotD: function () {
+ var sotd;
+ var mat = (this.status2maturity[this.specStatus]) ? this.status2maturity[this.specStatus] : this.specStatus;
+ var custom = document.getElementById("sotd");
+
+ if (this.specStatus == "unofficial") {
+ sotd = "<section id='sotd' class='introductory'><h2>Status of This Document</h2>" +
+ "<p>This document is merely a public working draft of a potential specification. It has " +
+ "no official standing of any kind and does not represent the support or consensus of any " +
+ "standards organisation.</p>";
+ if (custom) sotd += custom.innerHTML;
+ sotd += "</section>";
+ }
+ else if (this.specStatus === "finding" || this.specStatus === "draft-finding") {
+ sotd = "<section id='sotd' class='introductory'><h2>Status of This Document</h2>";
+ if (custom) sotd += custom.innerHTML;
+ else sotd += "<p style='color: red'>ReSpec does not support automated SotD generation for TAG findings, please specify one using a <section> element with ID=sotd.</p>";
+ sotd += "</section>";
+ }
+ else if (this.isNoTrack) {
+ var mc = (this.specStatus == "MO") ? " member-confidential" : "";
+ sotd = "<section id='sotd' class='introductory'><h2>Status of This Document</h2>" +
+ "<p>This document is merely a W3C-internal" + mc + " document. It has no "+
+ "official standing of any kind and does not represent consensus of the W3C Membership.</p>";
+ if (custom) sotd += custom.innerHTML;
+ sotd += "</section>";
+ }
+ else {
+ var art = "a ";
+ if (this.specStatus == "ED" || this.specStatus == "XGR" || this.specStatus == "IG-NOTE") art = "an ";
+ sotd = "<section id='sotd' class='introductory'><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 W3C publications and the latest revision " +
+ "of this technical report can be found in the <a href='http://www.w3.org/TR/'>W3C technical reports " +
+ "index</a> at http://www.w3.org/TR/.</em></p>";
+ if (custom) sotd += custom.innerHTML;
+ sotd += "<p>This document was published by the ";
+ if (isArray(this.wg)) {
+ var wgs = [];
+ for (var i = 0, n = this.wg.length; i < n; i++) {
+ wgs.push("<a href='" + this.wgURI[i] + "'>" + this.wg[i] + "</a>")
+ }
+ sotd += joinAnd(wgs);
+ }
+ else {
+ sotd += "<a href='" + this.wgURI + "'>" + this.wg + "</a>";
+ }
+ sotd += " as " + art + this.status2long[this.specStatus] + ".";
+ if (this.isRecTrack && this.specStatus != "REC") sotd += " This document is intended to become a W3C Recommendation.";
+ sotd +=
+ " If you wish to make comments regarding this document, please send them to <a href='mailto:" + this.wgPublicList + "@w3.org'>" +
+ this.wgPublicList + "@w3.org</a> (<a href='mailto:" + this.wgPublicList + "-request@w3.org?subject=subscribe'>subscribe</a>, " +
+ "<a href='http://lists.w3.org/Archives/Public/" + this.wgPublicList + "/'>archives</a>).";
+ if (this.specStatus == "LC") sotd += " The Last Call period ends " + this._humanDate(this.lcEnd) + ".";
+ if (this.specStatus == "CR") sotd += " W3C publishes a Candidate Recommendation to indicate that the document is believed" +
+ " to be stable and to encourage implementation by the developer community. This" +
+ " Candidate Recommendation is expected to advance to Proposed Recommendation no earlier than " +
+ this._humanDate(this.crEnd) + ".";
+ sotd += " All feedback is welcome.</p>";
+ if (this.specStatus != "REC") {
+ sotd += "<p>Publication as " + art + this.status2text[this.specStatus] + " does not imply endorsement by the W3C 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>";
+ }
+ if (this.specStatus == "LC")
+ sotd += "<p>This is a Last Call Working Draft and thus the Working Group has determined that this document has satisfied the " +
+ "relevant technical requirements and is sufficiently stable to advance through the Technical Recommendation process.</p>";
+ if (this.specStatus != "IG-NOTE") {
+ sotd +=
+ "<p>This document was produced by a group operating under the <a href='http://www.w3.org/Consortium/Patent-Policy-20040205/'>5 February " +
+ "2004 W3C Patent Policy</a>.";
+ }
+
+ if (!this.isRecTrack && mat == "WD")
+ sotd += " The group does not expect this document to become a W3C Recommendation.";
+
+ if (this.specStatus != "IG-NOTE") {
+ if (isArray(this.wgPatentURI)) {
+ sotd += " W3C maintains a public list of any patent disclosures (";
+ var wgs = [];
+ for (var i = 0, n = this.wg.length; i < n; i++) {
+ wgs.push("<a href='" + this.wgPatentURI[i] + "' rel='disclosure'>" + this.wg[i] + "</a>")
+ }
+ sotd += wgs.join(", ") + ") ";
+ }
+ else {
+ sotd += " W3C maintains a <a href='" + this.wgPatentURI + "' rel='disclosure'>public list of any patent disclosures</a> ";
+ }
+ sotd +=
+ "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 W3C Patent Policy</a>.</p>";
+ }
+ else {
+ // XXX
+ if (!this.charterDisclosureURI) error("IG-NOTEs must link to charter's disclosure section using charterDisclosureURI");
+ else {
+ sotd += "<p>The disclosure obligations of the Participants of this group are described in the <a href='" + this.charterDisclosureURI + "'>charter</a>. </p>";
+ }
+ }
+ if (this.addPatentNote) sotd += "<p>" + this.addPatentNote + "</p>";
+ sotd += "</section>";
+ }
+ if (custom) custom.parentNode.removeChild(custom);
+
+ var tmp = sn.element("div");
+ tmp.innerHTML = sotd;
+ var abs = document.getElementById("abstract");
+ abs.parentNode.insertBefore(tmp.firstChild, abs.nextSibling);
+ },
+
+ makeConformance: function () {
+ var confo = document.getElementById("conformance");
+ if (!confo) return;
+ var dummy = sn.element("div");
+ if (confo.childNodes.length > 0) sn.copyChildren(confo, dummy);
+ sn.element("h2", {}, confo, "Conformance");
+ confo.innerHTML += "<p>As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, " +
+ "and notes in this specification are non-normative. Everything else in this specification is " +
+ "normative.</p>\n<p>The key words MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, RECOMMENDED, MAY, " +
+ "and OPTIONAL in this specification are to be interpreted as described in [[!RFC2119]].</p>\n";
+ sn.copyChildren(dummy, confo);
+ },
+
+ informative: function () {
+ var secs = document.querySelectorAll("section.informative");
+ for (var i = 0; i < secs.length; i++) {
+ var sec = secs[i];
+ var p = sn.element("p");
+ sn.element("em", {}, p, "This section is non-normative.");
+ sec.insertBefore(p, sec.firstElementChild.nextSibling);
+ }
+ },
+
+ examples: function () {
+ // reindent
+ var exes = document.querySelectorAll("pre.example");
+ for (var i = 0; i < exes.length; i++) {
+ var ex = exes[i];
+ var lines = ex.innerHTML.split("\n");
+ while (lines.length && /^\s*$/.test(lines[0])) lines.shift();
+ while (/^\s*$/.test(lines[lines.length - 1])) lines.pop();
+ var matches = /^(\s+)/.exec(lines[0]);
+ if (matches) {
+ var rep = new RegExp("^" + matches[1]);
+ for (var j = 0; j < lines.length; j++) {
+ lines[j] = lines[j].replace(rep, "");
+ }
+ }
+ ex.innerHTML = lines.join("\n");
+ }
+ // highlight
+ sh_highlightDocument(this.base + "js/lang/", ".min.js");
+ },
+
+ fixHeaders: function () {
+ var secs = document.querySelectorAll("section > h1:first-child, section > h2:first-child, section > h3:first-child, section > h4:first-child, section > h5:first-child, section > h6:first-child");
+ for (var i = 0; i < secs.length; i++) {
+ var sec = secs[i];
+ var depth = sn.findNodes("ancestor::x:section|ancestor::section", sec).length + 1;
+ if (depth > 6) depth = 6;
+ var h = "h" + depth;
+ if (sec.localName.toLowerCase() != h) sn.renameEl(sec, h);
+ }
+ },
+
+ makeTOC: function () {
+ var ul = this.makeTOCAtLevel(document.body, [0], 1);
+ if (!ul) return;
+ var sec = sn.element("section", { id: "toc" });
+ sn.element("h2", { "class": "introductory" }, sec, "Table of Contents");
+ sec.appendChild(ul);
+ document.body.insertBefore(sec, document.getElementById("sotd").nextSibling);
+ },
+
+ appendixMode: false,
+ lastNonAppendix: 0,
+ alphabet: "ABCDEFGHIJKLMNOPQRSTUVWXYZ",
+ makeTOCAtLevel: function (parent, current, level) {
+ var xpath = this.tocIntroductory ? "./x:section|./section" :
+ "./x:section[not(@class='introductory')]|./section[not(@class='introductory')]"
+ var secs = sn.findNodes(xpath, parent);
+ if (secs.length == 0) return null;
+ var ul = sn.element("ul", { "class": "toc" });
+ for (var i = 0; i < secs.length; i++) {
+ var sec = secs[i],
+ isIntro = sn.hasClass(sec, "introductory");
+ if (!sec.childNodes.length) continue;
+ var h = sec.firstElementChild;
+ if (!h) continue;
+ var ln = h.localName.toLowerCase();
+ if (ln != "h2" && ln != "h3" && ln != "h4" && ln != "h5" && ln != "h6") continue;
+ var title = h.textContent;
+ var hKids = sn.documentFragment();
+ for (var j = 0; j < h.childNodes.length; j++) {
+ var node = h.childNodes[j].cloneNode(true);
+ hKids.appendChild(node);
+ if (node.nodeType == Node.ELEMENT_NODE) {
+ var ln = node.localName.toLowerCase();
+ if (ln == "a") {
+ node = sn.renameEl(node, "span");
+ var cl = node.getAttribute("class");
+ if (!cl) cl = "";
+ else cl = " " + cl;
+ // node.setAttribute("class", "formerLink" + cl);
+ sn.addClass(node, "formerLink" + cl);
+ node.removeAttribute("href");
+ }
+ else if (ln == "dfn") {
+ node = sn.renameEl(node, "span");
+ node.removeAttribute("id");
+ }
+ }
+ }
+ var id = sn.makeID(sec, null, title);
+ if (!isIntro) current[current.length-1]++;
+ var secnos = current.slice();
+ if (sn.hasClass(sec, "appendix") && current.length == 1 && !this.appendixMode) {
+ this.lastNonAppendix = current[0];
+ this.appendixMode = true;
+ }
+ if (this.appendixMode) secnos[0] = this.alphabet.charAt(current[0] - this.lastNonAppendix);
+ var secno = secnos.join(".");
+ if (!/\./.test(secno)) secno = secno + ".";
+ var df = sn.documentFragment();
+ if (!isIntro) sn.element("span", { "class": "secno" }, df, secno + " ");
+ // sn.text(" ", df);
+ var df2 = df.cloneNode(true);
+ h.insertBefore(df, h.firstChild);
+ // if this is a top level item, insert
+ // an OddPage comment so html2ps will correctly
+ // paginate the output
+ if (/\.$/.test(secno)) {
+ var com = document.createComment('OddPage') ;
+ h.parentNode.insertBefore(com, h) ;
+ }
+ // sn.text(title, df2);
+ df2.appendChild(hKids);
+ var a = sn.element("a", { href: "#" + id, 'class' : 'tocxref' }, null, [df2]);
+ var item = sn.element("li", { "class":"tocline" }, ul, [a]);
+
+ if (this.maxTocLevel && level >= this.maxTocLevel) continue;
+ current.push(0);
+ var sub = this.makeTOCAtLevel(sec, current, level + 1);
+ if (sub) item.appendChild(sub) ;
+ current.pop();
+ }
+
+ return ul;
+ },
+
+ idHeaders: function () {
+ var heads = document.querySelectorAll("h2, h3, h4, h5, h6");
+ for (var i = 0; i < heads.length; i++) {
+ var h = heads[i];
+ if (h.hasAttribute("id")) continue;
+ var par = h.parentNode;
+ if (par.localName.toLowerCase() == "section" && par.hasAttribute("id") && !h.previousElementSibling) continue;
+ sn.makeID(h, null);
+ }
+ },
+
+ // --- INLINE PROCESSING ----------------------------------------------------------------------------------
+ inlines: function () {
+ document.normalize();
+
+ // PRE-PROCESSING
+ var norms = {}, informs = {}, abbrMap = {}, acroMap = {}, badrefs = {};
+ var badrefcount = 0;
+ var abbrs = document.querySelectorAll("abbr[title]");
+ for (var i = 0; i < abbrs.length; i++) abbrMap[abbrs[i].textContent] = abbrs[i].getAttribute("title");
+ var acros = document.querySelectorAll("acronym[title]");
+ for (var i = 0; i < acros.length; i++) acroMap[acros[i].textContent] = acros[i].getAttribute("title");
+ var aKeys = [];
+ for (var k in abbrMap) aKeys.push(k);
+ for (var k in acroMap) aKeys.push(k);
+ aKeys.sort(function (a, b) {
+ if (b.length < a.length) return -1;
+ if (a.length < b.length) return 1;
+ return 0;
+ });
+ var abbrRx = aKeys.length ? "|(?:\\b" + aKeys.join("\\b)|(?:\\b") + "\\b)" : "";
+ var rx = new RegExp("(\\bMUST(?:\\s+NOT)?\\b|\\bSHOULD(?:\\s+NOT)?\\b|\\bSHALL(?:\\s+NOT)?\\b|" +
+ "\\bMAY\\b|\\b(?:NOT\\s+)?REQUIRED\\b|\\b(?:NOT\\s+)?RECOMMENDED\\b|\\bOPTIONAL\\b|" +
+ "(?:\\[\\[(?:!)?[A-Za-z0-9-]+\\]\\])" +
+ abbrRx + ")");
+ // PROCESSING
+ var txts = sn.findNodes(".//text()", document.body);
+ for (var i = 0; i < txts.length; i++) {
+ var txt = txts[i];
+ var subtxt = txt.data.split(rx);
+ var df = sn.documentFragment();
+ while (subtxt.length) {
+ var t = subtxt.shift();
+ var matched = null;
+ if (subtxt.length) matched = subtxt.shift();
+ sn.text(t, df);
+ if (matched) {
+ // RFC 2129
+ if (/MUST(?:\s+NOT)?|SHOULD(?:\s+NOT)?|SHALL(?:\s+NOT)?|MAY|(?:NOT\s+)?REQUIRED|(?:NOT\s+)?RECOMMENDED|OPTIONAL/.test(matched)) {
+ matched = matched.toLowerCase();
+ sn.element("em", { "class": "rfc2119", title: matched }, df, matched);
+ }
+ // BIBREF
+ else if (/^\[\[/.test(matched)) {
+ var ref = matched;
+ ref = ref.replace(/^\[\[/, "");
+ ref = ref.replace(/]]$/, "");
+ var norm = false;
+ if (ref.indexOf("!") == 0) {
+ norm = true;
+ ref = ref.replace(/^!/, "");
+ }
+ if (berjon.biblio[ref]) {
+ if (norm) norms[ref] = true;
+ else informs[ref] = true;
+ sn.text("[", df);
+ // embed a cite with an a inside of it
+ var el = sn.element("cite", {} , df);
+ sn.element("a", { "class": "bibref", rel: "biblioentry", href: "#bib-" + ref }, el, ref);
+ sn.text("]", df);
+ }
+ else {
+ badrefcount++;
+ if ( badrefs[ref] ) {
+ badrefs[ref] = badrefs[ref] + 1 ;
+ } else {
+ badrefs[ref] = 1 ;
+ }
+ }
+ }
+ // ABBR
+ else if (abbrMap[matched]) {
+ if (sn.findNodes("ancestor::abbr", txt).length) sn.text(matched, df);
+ else sn.element("abbr", { title: abbrMap[matched] }, df, matched);
+ }
+ // ACRO
+ else if (acroMap[matched]) {
+ if (sn.findNodes("ancestor::acronym", txt).length) sn.text(matched, df);
+ else sn.element("acronym", { title: acroMap[matched] }, df, matched);
+ }
+ // FAIL
+ else {
+ error("Found token '" + matched + "' but it does not correspond to anything");
+ }
+ }
+ }
+ txt.parentNode.replaceChild(df, txt);
+ }
+
+ // POST-PROCESSING
+ // bibref
+ if(badrefcount > 0) {
+ error("Got " + badrefcount + " tokens looking like a reference, not in biblio DB: ");
+ for (var item in badrefs) {
+ error("Bad ref: " + item + ", count = " + badrefs[item]);
+ }
+ }
+
+ var del = [];
+ for (var k in informs) {
+ if (norms[k]) del.push(k);
+ }
+ for (var i = 0; i < del.length; i++) delete informs[del[i]];
+
+ var refsec = sn.element("section", { id: "references", "class": "appendix" }, document.body);
+ sn.element("h2", {}, refsec, "References");
+ if (this.refNote) {
+ var refnote = sn.element("p", {}, refsec);
+ refnote.innerHTML= this.refNote;
+ }
+
+ var types = ["Normative", "Informative"];
+ for (var i = 0; i < types.length; i++) {
+ var type = types[i];
+ var refMap = (type == "Normative") ? norms : informs;
+ var sec = sn.element("section", {}, refsec);
+ sn.makeID(sec, null, type + " references");
+ sn.element("h3", {}, sec, type + " references");
+ var refs = [];
+ for (var k in refMap) refs.push(k);
+ refs.sort();
+ if (refs.length) {
+ var dl = sn.element("dl", { "class": "bibliography" }, sec);
+ if (this.doRDFa) {
+ dl.setAttribute('about', '') ;
+ }
+ for (var j = 0; j < refs.length; j++) {
+ var ref = refs[j];
+ sn.element("dt", { id: "bib-" + ref }, dl, "[" + ref + "]");
+ var dd = sn.element("dd", {}, dl);
+ if (this.doRDFa) {
+ if (type == 'Normative') {
+ dd.setAttribute('rel','dcterms:requires');
+ } else {
+ dd.setAttribute('rel','dcterms:references');
+ }
+ }
+ if (berjon.biblio[ref]) dd.innerHTML = berjon.biblio[ref] + "\n";
+ }
+ }
+ else {
+ sn.element("p", {}, sec, "No " + type.toLowerCase() + " references.");
+ }
+ }
+
+ },
+
+ dfn: function () {
+ document.normalize();
+ var dfnMap = {};
+ var dfns = document.querySelectorAll("dfn");
+ for (var i = 0; i < dfns.length; i++) {
+ var dfn = dfns[i];
+ var title = this._getDfnTitle(dfn);
+ dfnMap[title.toLowerCase()] = sn.makeID(dfn, "dfn", title);
+ }
+
+ var ants = document.querySelectorAll("a:not([href])");
+ for (var i = 0; i < ants.length; i++) {
+ var ant = ants[i];
+ // if (ant.getAttribute("class") == "externalDFN") continue;
+ if (sn.hasClass(ant, "externalDFN")) continue;
+ var title = this._getDfnTitle(ant).toLowerCase();
+ if (dfnMap[title] && !(dfnMap[title] instanceof Function)) {
+ ant.setAttribute("href", "#" + dfnMap[title]);
+ // ant.setAttribute("class", "internalDFN");
+ sn.addClass(ant, "internalDFN");
+ }
+ else {
+ // we want to use these for other links too
+ // error("No definition for title: " + title);
+ }
+ }
+ },
+
+ doBestPractices: function () {
+ this.practiceNum = 1;
+ var spans = document.querySelectorAll("span.practicelab");
+ var contents = "<h2>Best Practices Summary</h2><ul>"
+ // scan all the best practices to number them and add handle
+ // at same time generate summary section contents if section
+ // is provided in source, using links if possible
+ //
+ // probably not the most efficient here but only used for best
+ // practices document
+ for (var i = 0; i < spans.length; i++) {
+ var span = spans[i];
+ var label = span.innerHTML;
+ var ref = span.getAttribute("id");
+ var handle = "Best Practice " + this.practiceNum;
+ var content = ": " + label;
+ var item = handle + content;
+ if(!ref) {
+ contents += "<li>" + handle + content + "</li>";
+ } else {
+ contents += "<li><a href='#" + ref + "'>" + handle +
+ "</a>" + content + "</li>";
+ }
+ span.innerHTML = item;
+ this.practiceNum++;
+ }
+ contents += "</ul>";
+
+ var sec = document.getElementById("bp-summary");
+ if(!sec) {
+// alert("no bp-summary section");
+ return;
+ }
+ sec.innerHTML = contents;
+ },
+
+ // <link href="section id" class="sectionRef" />
+
+// returnObjById: function( id )
+// {
+// if (document.getElementById)
+// var returnVar = document.getElementById(id);
+// else if (document.all)
+// var returnVar = document.all[id];
+// else if (document.layers)
+// var returnVar = document.layers[id];
+// return returnVar;
+// },
+
+ makeSectionRefs: function () {
+ var secrefs = document.querySelectorAll("a.sectionRef");
+ for (var i = 0; i < secrefs.length; i++) {
+ var secref = secrefs[i];
+
+ // get the link href and section title
+ var h = secref.getAttribute('href');
+ var id = h.substring(1);
+
+ var sec = document.getElementById(id);
+ var secno = "Not found"+ id;
+
+ if(sec) {
+ var span = sec.firstElementChild;
+
+ if(span) {
+ secno = span.textContent;
+ }
+ }
+
+ title = "section " + secno;
+
+ // create new a reference to section using section title
+ secref.innerHTML = title;
+ }
+ },
+
+ // --- WEB IDL --------------------------------------------------------------------------------------------
+ webIDL: function () {
+ var idls = document.querySelectorAll(".idl"); // should probably check that it's not inside one
+ var infNames = [];
+ for (var i = 0; i < idls.length; i++) {
+ var idl = idls[i];
+ var w = new berjon.WebIDLProcessor({ noIDLSorting: this.noIDLSorting, noIDLIn: this.noIDLIn });
+ var inf = w.definition(idl);
+ var df = w.makeMarkup();
+ idl.parentNode.replaceChild(df, idl);
+ if (inf.type == "interface" || inf.type == "exception" || inf.type == "dictionary" || inf.type == "typedef") infNames.push(inf.id);
+ }
+ document.normalize();
+ var ants = document.querySelectorAll("a:not([href])");
+ for (var i = 0; i < ants.length; i++) {
+ var ant = ants[i];
+ if (sn.hasClass(ant, "externalDFN")) continue;
+ var name = ant.textContent;
+ if (infNames.indexOf(name) >= 0) {
+ ant.setAttribute("href", "#idl-def-" + name);
+ // ant.setAttribute("class", "idlType");
+ sn.addClass(ant, "idlType");
+ ant.innerHTML = "<code>" + name + "</code>";
+ }
+ }
+ },
+
+ // --- CLEANUP --------------------------------------------------------------------------------------------
+ removeRespec: function () {
+ var rs = document.querySelectorAll(".remove");
+ for (var i = 0; i < rs.length; i++) rs[i].parentNode.removeChild(rs[i]);
+ },
+
+ unHTML5: function () {
+ var secs = document.querySelectorAll("section");
+ for (var i = 0; i < secs.length; i++) {
+ var sec = secs[i];
+ var div = sn.renameEl(sec, "div");
+ // div.setAttribute("class", "section"); // XXX that kills previous class, may not be a problem
+ sn.addClass(div, "section");
+ }
+ },
+
+ // --- HELPERS --------------------------------------------------------------------------------------------
+ _insertCSS: function (css, inlined) {
+ // if (document.createStyleSheet) return document.createStyleSheet(css);
+ if (inlined) {
+ try {
+ // this is synchronous because order of the CSS matters (if though PubRules doesn't detect this
+ // correctly :-) If it's slow, turn off inlineCSS during development
+ var xhr = new XMLHttpRequest();
+ xhr.open("GET", css, false);
+ // xhr.onreadystatechange = function () {
+ // if (this.readyState == 4) {
+ // if (this.status == 200) {
+ // sn.element("style", { type: "text/css" }, document.documentElement.firstElementChild, this.responseText);
+ // }
+ // else {
+ // error("There appear to have been a problem fetching the style sheet; status=" + this.status);
+ // }
+ // }
+ // };
+ xhr.send(null);
+ if (xhr.status == 200) {
+ sn.element("style", { type: "text/css" }, document.documentElement.firstElementChild, xhr.responseText);
+ }
+ else {
+ error("There appears to have been a problem fetching the style sheet; status=" + xhr.status);
+ }
+ }
+ catch (e) {
+ // warning("There was an error with the request, probably that you're working from disk.");
+ this._insertCSS(css, false);
+ }
+ }
+ else {
+ sn.element("link", {
+ href: css,
+ rel: "stylesheet",
+ type: "text/css",
+ charset: "utf-8"
+ }, document.documentElement.firstElementChild);
+ }
+ },
+
+ _readFile: function (URI) {
+ try {
+ var xhr = new XMLHttpRequest();
+ xhr.open("GET", URI, false);
+ xhr.send(null);
+ if (xhr.status == 200 || xhr.status == 0) {
+ return xhr.responseText ;
+ } else {
+ error("There appears to have been a problem fetching the file " + URI + "; status=" + xhr.status);
+ }
+ }
+ catch (e) {
+ warning("There was an error with the request to load " + URI + ", probably that you're working from disk.");
+ }
+ },
+
+ _humanMonths: ["January", "February", "March", "April", "May", "June", "July",
+ "August", "September", "October", "November", "December"],
+ _humanDate: function (date) {
+ return this._lead0(date.getDate()) + " " + this._humanMonths[date.getMonth()] + " " + date.getFullYear();
+ },
+
+ _concatDate: function (date, sep) {
+ if (!sep) sep = "";
+ return "" + date.getFullYear() + sep + this._lead0(date.getMonth() + 1) + sep + this._lead0(date.getDate());
+ },
+
+ _ISODate: function (date) {
+ return "" + date.getUTCFullYear() +'-'+ this._lead0(date.getUTCMonth() + 1)+'-' + this._lead0(date.getUTCDate()) +'T'+this._lead0(date.getUTCHours())+':'+this._lead0(date.getUTCMinutes()) +":"+this._lead0(date.getUTCSeconds())+'+0000';
+ },
+
+ _parseDate: function (str) {
+ return new Date(str.substr(0, 4), (str.substr(5, 2) - 1), str.substr(8, 2));
+ },
+
+ _parseLastModified: function (str) {
+ if (!str) return new Date();
+ return new Date(Date.parse(str));
+ // return new Date(str.substr(6, 4), (str.substr(0, 2) - 1), str.substr(3, 2));
+ },
+
+
+ _lead0: function (str) {
+ str = "" + str;
+ return (str.length == 1) ? "0" + str : str;
+ },
+
+ _getDfnTitle: function (dfn) {
+ var title;
+ if (dfn.hasAttribute("title")) title = dfn.getAttribute("title");
+ else if (dfn.childNodes.length == 1 && dfn.firstChild.nodeType == Node.ELEMENT_NODE &&
+ (dfn.firstChild.localName.toLowerCase() == "abbr" || dfn.firstChild.localName.toLowerCase() == "acronym") &&
+ dfn.firstChild.hasAttribute("title")) title = dfn.firstChild.getAttribute("title");
+ else title = dfn.textContent;
+ title = this._norm(title);
+ return title;
+ },
+
+ _norm: function (str) {
+ str = str.replace(/^\s+/, "").replace(/\s+$/, "");
+ return str.split(/\s+/).join(" ");
+ },
+
+ _esc: function (s) {
+ s = s.replace(/&/g,'&');
+ s = s.replace(/>/g,'>');
+ s = s.replace(/"/g,'"');
+ s = s.replace(/</g,'<');
+ return s;
+ }
+};
+
+berjon.WebIDLProcessor = function (cfg) {
+ this.parent = { type: "module", id: "outermost", children: [] };
+ if (!cfg) cfg = {};
+ for (var k in cfg) this[k] = cfg[k];
+};
+berjon.WebIDLProcessor.prototype = {
+ definition: function (idl) {
+ var def = { children: [] };
+ var str = idl.getAttribute("title");
+ str = this.parseExtendedAttributes(str, def);
+ if (str.indexOf("interface") == 0 || str.indexOf("partial") === 0) this.interface(def, str, idl);
+ else if (str.indexOf("exception") == 0) this.exception(def, str, idl);
+ else if (str.indexOf("dictionary") == 0) this.dictionary(def, str, idl);
+ else if (str.indexOf("typedef") == 0) this.typedef(def, str, idl);
+ else if (/\bimplements\b/.test(str)) this.implements(def, str, idl);
+ else error("Expected definition, got: " + str);
+ this.parent.children.push(def); // this should be done at the caller level
+ this.processMembers(def, idl);
+ return def;
+ },
+
+ interface: function (inf, str, idl) {
+ inf.type = "interface";
+ var match = /^\s*(partial\s+)?interface\s+([A-Za-z][A-Za-z0-9]*)(?:\s+:\s*([^{]+)\s*)?/.exec(str);
+ if (match) {
+ inf.partial = !!match[1];
+ inf.id = match[2];
+ inf.refId = this._id(inf.id);
+ if (idl.getAttribute('data-merge')) {
+ inf.merge = [];
+ var merge = idl.getAttribute('data-merge').split(' ');
+ for (var i = 0; i < merge.length; i++) inf.merge.push(merge[i]);
+ }
+ if (match[3]) inf.superclasses = match[3].split(/\s*,\s*/);
+ }
+ else {
+ error("Expected interface, got: " + str);
+ }
+ return inf;
+ },
+
+ dictionary: function (inf, str, idl) {
+ inf.type = "dictionary";
+ var match = /^\s*dictionary\s+([A-Za-z][A-Za-z0-9]*)(?:\s+:\s*([^{]+)\s*)?/.exec(str);
+ if (match) {
+ inf.id = match[1];
+ inf.refId = this._id(inf.id);
+ if (match[2]) inf.superclasses = match[2].split(/\s*,\s*/);
+ }
+ else {
+ error("Expected dictionary, got: " + str);
+ }
+ return inf;
+ },
+
+ exception: function (exc, str, idl) {
+ exc.type = "exception";
+ var match = /^\s*exception\s+([A-Za-z][A-Za-z0-9]*)\s*/.exec(str);
+ if (match) {
+ exc.id = match[1];
+ exc.refId = this._id(exc.id);
+ }
+ else error("Expected exception, got: " + str);
+ return exc;
+ },
+
+ typedef: function (tdf, str, idl) {
+ tdf.type = "typedef";
+ tdf.extendedAttributes = null; // remove them in case some were there by mistake
+ var match = /^\s*typedef\s+(.+)\s+(\S+)\s*$/.exec(str);
+ if (match) {
+ var type = match[1];
+ tdf.nullable = false;
+ if (/\?$/.test(type)) {
+ type = type.replace(/\?$/, "");
+ tdf.nullable = true;
+ }
+ tdf.array = false;
+ if (/\[\]$/.test(type)) {
+ type = type.replace(/\[\]$/, "");
+ tdf.array = true;
+ }
+ tdf.datatype = type;
+ tdf.id = match[2];
+ tdf.refId = this._id(tdf.id);
+ tdf.description = sn.documentFragment();
+ sn.copyChildren(idl, tdf.description);
+ }
+ else {
+ error("Expected typedef, got: " + str);
+ }
+ return tdf;
+ },
+
+ implements: function (imp, str, idl) {
+ imp.type = "implements";
+ imp.extendedAttributes = null; // remove them in case some were there by mistake
+ var match = /^\s*(.+?)\s+implements\s+(.+)\s*$/.exec(str);
+ if (match) {
+ imp.id = match[1];
+ imp.refId = this._id(imp.id);
+ imp.datatype = match[2];
+ imp.description = sn.documentFragment();
+ sn.copyChildren(idl, imp.description);
+ }
+ else {
+ error("Expected implements, got: " + str);
+ }
+ return imp;
+ },
+
+ processMembers: function (obj, el) {
+ var exParent = this.parent;
+ this.parent = obj;
+ var dts = sn.findNodes("./dt", el);
+ for (var i = 0; i < dts.length; i++) {
+ var dt = dts[i];
+ var dd = dt.nextElementSibling; // we take a simple road
+ var mem;
+ if (obj.type == "exception") {
+ mem = this.exceptionMember(dt, dd);
+ }
+ else if (obj.type == "dictionary") {
+ mem = this.dictionaryMember(dt, dd);
+ }
+ else {
+ mem = this.interfaceMember(dt, dd);
+ }
+ obj.children.push(mem);
+ }
+ this.parent = exParent;
+ },
+
+ parseConst: function (mem, str) {
+ // CONST
+ var match = /^\s*const\s+\b([^=]+\??)\s+([^=\s]+)\s*=\s*(.*)$/.exec(str);
+ if (match) {
+ mem.type = "constant";
+ var type = match[1];
+ mem.nullable = false;
+ if (/\?$/.test(type)) {
+ type = type.replace(/\?$/, "");
+ mem.nullable = true;
+ }
+ mem.datatype = type;
+ mem.id = match[2];
+ mem.refId = this._id(mem.id);
+ mem.value = match[3];
+ return true;
+ }
+ return false;
+ },
+
+ exceptionMember: function (dt, dd) {
+ var mem = { children: [] };
+ var str = this._norm(dt.textContent);
+ mem.description = sn.documentFragment();
+ sn.copyChildren(dd, mem.description);
+ str = this.parseExtendedAttributes(str, mem);
+
+ if (this.parseConst(mem, str)) return mem;
+
+ // FIELD
+ var match = /^\s*(.*?)\s+(\S+)\s*$/.exec(str);
+ if (match) {
+ mem.type = "field";
+ var type = match[1];
+ mem.nullable = false;
+ if (/\?$/.test(type)) {
+ type = type.replace(/\?$/, "");
+ mem.nullable = true;
+ }
+ mem.array = false;
+ if (/\[\]$/.test(type)) {
+ type = type.replace(/\[\]$/, "");
+ mem.array = true;
+ }
+ mem.datatype = type;
+ mem.id = match[2];
+ mem.refId = this._id(mem.id);
+ return mem;
+ }
+
+ // NOTHING MATCHED
+ error("Expected exception member, got: " + str);
+ },
+
+ dictionaryMember: function (dt, dd) {
+ var mem = { children: [] };
+ var str = this._norm(dt.textContent);
+ mem.description = sn.documentFragment();
+ sn.copyChildren(dd, mem.description);
+ str = this.parseExtendedAttributes(str, mem);
+
+ // MEMBER
+ var match = /^\s*([^=]+\??)\s+([^=\s]+)(?:\s*=\s*(.*))?$/.exec(str);
+ // var match = /^\s*(.*?)\s+(\S+)\s*$/.exec(str);
+ if (match) {
+ mem.type = "member";
+ var type = match[1];
+ mem.id = match[2];
+ mem.refId = this._id(mem.id);
+ mem.defaultValue = match[3];
+ mem.nullable = false;
+ if (/\?$/.test(type)) {
+ type = type.replace(/\?$/, "");
+ mem.nullable = true;
+ }
+ mem.array = false;
+ if (/\[\]$/.test(type)) {
+ type = type.replace(/\[\]$/, "");
+ mem.array = true;
+ }
+ mem.datatype = type;
+ return mem;
+ }
+
+ // NOTHING MATCHED
+ error("Expected dictionary member, got: " + str);
+ },
+
+ interfaceMember: function (dt, dd) {
+ var mem = { children: [] };
+ var str = this._norm(dt.textContent);
+ var extPrm = (sn.findNodes("dl[@class='parameters']", dd))[0];
+ var excepts = sn.findNodes("*[@class='exception']", dd);
+ var hadId = false;
+ if (dd.id) hadId = true;
+ else dd.id = "temporaryIDJustForCSS";
+ dd.refId = this._id(dd.id);
+ // var sgrs = sn.findNodes("*[@class='setraises' or @class='getraises' or]", dd);
+ var sgrs = document.querySelectorAll("#" + dd.id + " .getraises, #" + dd.id + " .setraises");
+ if (!hadId) dd.removeAttribute("id");
+ mem.description = sn.documentFragment();
+ sn.copyChildren(dd, mem.description);
+ str = this.parseExtendedAttributes(str, mem);
+ var match;
+
+ // ATTRIBUTE
+ match = /^\s*(?:(readonly)\s+)?attribute\s+\b(.*?)\s+(\S+)\s*$/.exec(str);
+ if (match) {
+ mem.type = "attribute";
+ mem.readonly = (match[1] == "readonly");
+ var type = match[2];
+ mem.nullable = false;
+ if (/\?$/.test(type)) {
+ type = type.replace(/\?$/, "");
+ mem.nullable = true;
+ }
+ mem.array = false;
+ if (/\[\]$/.test(type)) {
+ type = type.replace(/\[\]$/, "");
+ mem.array = true;
+ }
+ mem.datatype = type;
+ mem.id = match[3];
+ mem.refId = this._id(mem.id);
+ mem.raises = [];
+ if (sgrs.length) {
+ for (var i = 0; i < sgrs.length; i++) {
+ var el = sgrs[i];
+ var exc = {
+ id: el.getAttribute("title"),
+ onSet: sn.hasClass(el, "setraises"),
+ onGet: sn.hasClass(el, "getraises"),
+ };
+ if (el.localName.toLowerCase() == "dl") {
+ exc.type = "codelist";
+ exc.description = [];
+ var dts = sn.findNodes("./dt", el);
+ for (var j = 0; j < dts.length; j++) {
+ var dt = dts[j];
+ var dd = dt.nextElementSibling;
+ var c = { id: dt.textContent, description: sn.documentFragment() };
+ sn.copyChildren(dd, c.description);
+ exc.description.push(c);
+ }
+ }
+ else if (el.localName.toLowerCase() == "div") {
+ exc.type = "simple";
+ exc.description = sn.documentFragment();
+ sn.copyChildren(el, exc.description);
+ }
+ else {
+ error("Do not know what to do with exceptions being raised defined outside of a div or dl.");
+ }
+ el.parentNode.removeChild(el);
+ mem.raises.push(exc);
+ }
+ }
+
+ return mem;
+ }
+
+ if (this.parseConst(mem, str)) return mem;
+
+ // METHOD
+ match = /^\s*\b(.*?)\s+\b(\S+)\s*\(\s*(.*)\s*\)\s*$/.exec(str);
+ if (match) {
+ mem.type = "method";
+ var type = match[1];
+ mem.nullable = false;
+ if (/\?$/.test(type)) {
+ type = type.replace(/\?$/, "");
+ mem.nullable = true;
+ }
+ mem.array = false;
+ if (/\[\]$/.test(type)) {
+ type = type.replace(/\[\]$/, "");
+ mem.array = true;
+ }
+ mem.datatype = type;
+ mem.id = match[2];
+ mem.refId = this._id(mem.id);
+ mem.params = [];
+ var prm = match[3];
+ mem.raises = [];
+
+ if (excepts.length) {
+ for (var i = 0; i < excepts.length; i++) {
+ var el = excepts[i];
+ var exc = { id: el.getAttribute("title") };
+ if (el.localName.toLowerCase() == "dl") {
+ exc.type = "codelist";
+ exc.description = [];
+ var dts = sn.findNodes("./dt", el);
+ for (var j = 0; j < dts.length; j++) {
+ var dt = dts[j];
+ var dd = dt.nextElementSibling;
+ var c = { id: dt.textContent, description: sn.documentFragment() };
+ sn.copyChildren(dd, c.description);
+ exc.description.push(c);
+ }
+ }
+ else if (el.localName.toLowerCase() == "div") {
+ exc.type = "simple";
+ exc.description = sn.documentFragment();
+ sn.copyChildren(el, exc.description);
+ }
+ else {
+ error("Do not know what to do with exceptions being raised defined outside of a div or dl.");
+ }
+ el.parentNode.removeChild(el);
+ mem.raises.push(exc);
+ }
+ }
+
+ if (extPrm) {
+ extPrm.parentNode.removeChild(extPrm);
+ var dts = sn.findNodes("./dt", extPrm);
+ for (var i = 0; i < dts.length; i++) {
+ var dt = dts[i];
+ var dd = dt.nextElementSibling; // we take a simple road
+ var prm = dt.textContent;
+ var p = {};
+ prm = this.parseExtendedAttributes(prm, p);
+ var match = /^\s*\b(.+?)\s+([^\s]+)\s*$/.exec(prm);
+ if (match) {
+ var type = match[1];
+ p.nullable = false;
+ if (/\?$/.test(type)) {
+ type = type.replace(/\?$/, "");
+ p.nullable = true;
+ }
+ p.array = false;
+ if (/\[\]$/.test(type)) {
+ type = type.replace(/\[\]$/, "");
+ p.array = true;
+ }
+ p.datatype = type;
+ p.id = match[2];
+ p.refId = this._id(p.id);
+ p.description = sn.documentFragment();
+ sn.copyChildren(dd, p.description);
+ mem.params.push(p);
+ }
+ else {
+ error("Expected parameter definition, got: " + prm);
+ break;
+ }
+ }
+ }
+ else {
+ while (prm.length) {
+ var p = {};
+ prm = this.parseExtendedAttributes(prm, p);
+ // either up to end of string, or up to ,
+ var re = /^\s*(?:in\s+)?\b([^,]+)\s+\b([^,\s]+)\s*(?:,)?\s*/;
+ var match = re.exec(prm);
+ if (match) {
+ prm = prm.replace(re, "");
+ var type = match[1];
+ p.nullable = false;
+ if (/\?$/.test(type)) {
+ type = type.replace(/\?$/, "");
+ p.nullable = true;
+ }
+ p.array = false;
+ if (/\[\]$/.test(type)) {
+ type = type.replace(/\[\]$/, "");
+ p.array = true;
+ }
+ p.datatype = type;
+ p.id = match[2];
+ p.refId = this._id(p.id);
+ mem.params.push(p);
+ }
+ else {
+ error("Expected parameter list, got: " + prm);
+ break;
+ }
+ }
+ }
+
+ // apply optional
+ var isOptional = false;
+ for (var i = 0; i < mem.params.length; i++) {
+ var p = mem.params[i];
+ var pkw = p.datatype.split(/\s+/);
+ var idx = pkw.indexOf("optional");
+ if (idx > -1) {
+ isOptional = true;
+ pkw.splice(idx, 1);
+ p.datatype = pkw.join(" ");
+ }
+ p.optional = isOptional;
+ }
+
+ return mem;
+ }
+
+ // NOTHING MATCHED
+ error("Expected interface member, got: " + str);
+ },
+
+ parseExtendedAttributes: function (str, obj) {
+ str = str.replace(/^\s*\[([^\]]+)\]\s+/, function (x, m1) { obj.extendedAttributes = m1; return ""; });
+ return str;
+ },
+
+ makeMarkup: function () {
+ var df = sn.documentFragment();
+ var pre = sn.element("pre", { "class": "idl" }, df);
+ pre.innerHTML = this.writeAsWebIDL(this.parent, 0);
+ df.appendChild(this.writeAsHTML(this.parent));
+ return df;
+ },
+
+ writeAsHTML: function (obj) {
+ if (obj.type == "module") {
+ if (obj.id == "outermost") {
+ if (obj.children.length > 1) error("We currently only support one structural level per IDL fragment");
+ return this.writeAsHTML(obj.children[0]);
+ }
+ else {
+ warning("No HTML can be generated for module definitions.");
+ return sn.element("span");
+ }
+ }
+ else if (obj.type == "typedef") {
+ var cnt;
+ if (obj.description && obj.description.childNodes.length) {
+ cnt = [obj.description];
+ }
+ else {
+ // yuck -- should use a single model...
+ var tdt = sn.element("span", { "class": "idlTypedefType" }, null);
+ tdt.innerHTML = this.writeDatatype(obj.datatype);
+ cnt = [ sn.text("Throughout this specification, the identifier "),
+ sn.element("span", { "class": "idlTypedefID" }, null, obj.id),
+ sn.text(" is used to refer to the "),
+ sn.text(obj.array ? "array of " : ""),
+ tdt,
+ sn.text(obj.nullable ? " (nullable)" : ""),
+ sn.text(" type.")];
+ }
+ return sn.element("div", { "class": "idlTypedefDesc" }, null, cnt);
+ }
+ else if (obj.type == "implements") {
+ var cnt;
+ if (obj.description && obj.description.childNodes.length) {
+ cnt = [obj.description];
+ }
+ else {
+ cnt = [ sn.text("All instances of the "),
+ sn.element("code", {}, null, [sn.element("a", {}, null, obj.id)]),
+ sn.text(" type are defined to also implement the "),
+ sn.element("a", {}, null, obj.datatype),
+ sn.text(" interface.")];
+ cnt = [sn.element("p", {}, null, cnt)];
+ }
+ return sn.element("div", { "class": "idlImplementsDesc" }, null, cnt);
+ }
+
+ else if (obj.type == "exception") {
+ var df = sn.documentFragment();
+ var curLnk = "widl-" + obj.refId + "-";
+ var types = ["field", "constant"];
+ for (var i = 0; i < types.length; i++) {
+ var type = types[i];
+ var things = obj.children.filter(function (it) { return it.type == type });
+ if (things.length == 0) continue;
+ if (!this.noIDLSorting) {
+ things.sort(function (a, b) {
+ if (a.id < b.id) return -1;
+ if (a.id > b.id) return 1;
+ return 0;
+ });
+ }
+
+ var sec = sn.element("section", {}, df);
+ var secTitle = type;
+ secTitle = secTitle.substr(0, 1).toUpperCase() + secTitle.substr(1) + "s";
+ sn.element("h2", {}, sec, secTitle);
+ var dl = sn.element("dl", { "class": type + "s" }, sec);
+ for (var j = 0; j < things.length; j++) {
+ var it = things[j];
+ var dt = sn.element("dt", { id: curLnk + it.refId }, dl);
+ sn.element("code", {}, dt, it.id);
+ var desc = sn.element("dd", {}, dl, [it.description]);
+ if (type == "field") {
+ sn.text(" of type ", dt);
+ if (it.array) sn.text("array of ", dt);
+ var span = sn.element("span", { "class": "idlFieldType" }, dt);
+ var matched = /^sequence<(.+)>$/.exec(it.datatype);
+ if (matched) {
+ sn.text("sequence<", span);
+ sn.element("a", {}, span, matched[1]);
+ sn.text(">", span);
+ }
+ else {
+ sn.element("a", {}, span, it.datatype);
+ }
+ if (it.nullable) sn.text(", nullable", dt);
+ }
+ else if (type == "constant") {
+ sn.text(" of type ", dt);
+ sn.element("span", { "class": "idlConstType" }, dt, [sn.element("a", {}, null, it.datatype)]);
+ if (it.nullable) sn.text(", nullable", dt);
+ }
+ }
+ }
+ return df;
+ }
+
+ else if (obj.type == "dictionary") {
+ var df = sn.documentFragment();
+ var curLnk = "widl-" + obj.refId + "-";
+ var things = obj.children;
+ if (things.length == 0) return df;
+ if (!this.noIDLSorting) {
+ things.sort(function (a, b) {
+ if (a.id < b.id) return -1;
+ if (a.id > b.id) return 1;
+ return 0;
+ });
+ }
+
+ var sec = sn.element("section", {}, df);
+ cnt = [sn.text("Dictionary "),
+ sn.element("a", { "class": "idlType" }, null, obj.id),
+ sn.text(" Members")];
+ sn.element("h2", {}, sec, cnt);
+ var dl = sn.element("dl", { "class": "dictionary-members" }, sec);
+ for (var j = 0; j < things.length; j++) {
+ var it = things[j];
+ var dt = sn.element("dt", { id: curLnk + it.refId }, dl);
+ sn.element("code", {}, dt, it.id);
+ var desc = sn.element("dd", {}, dl, [it.description]);
+ sn.text(" of type ", dt);
+ if (it.array) sn.text("array of ", dt);
+ var span = sn.element("span", { "class": "idlMemberType" }, dt);
+ var matched = /^sequence<(.+)>$/.exec(it.datatype);
+ if (matched) {
+ sn.text("sequence<", span);
+ sn.element("a", {}, span, matched[1]);
+ sn.text(">", span);
+ }
+ else {
+ sn.element("a", {}, span, it.datatype);
+ }
+ if (it.nullable) sn.text(", nullable", dt);
+ if (it.defaultValue) {
+ sn.text(", defaulting to ", dt);
+ sn.element("code", {}, dt, [sn.text(it.defaultValue)]);
+ }
+ }
+ return df;
+ }
+
+ else if (obj.type == "interface") {
+ var df = sn.documentFragment();
+ var curLnk = "widl-" + obj.refId + "-";
+ var types = ["attribute", "method", "constant"];
+ for (var i = 0; i < types.length; i++) {
+ var type = types[i];
+ var things = obj.children.filter(function (it) { return it.type == type });
+ if (things.length == 0) continue;
+ if (!this.noIDLSorting) {
+ things.sort(function (a, b) {
+ if (a.id < b.id) return -1;
+ if (a.id > b.id) return 1;
+ return 0;
+ });
+ }
+
+ var sec = sn.element("section", {}, df);
+ var secTitle = type;
+ secTitle = secTitle.substr(0, 1).toUpperCase() + secTitle.substr(1) + "s";
+ sn.element("h2", {}, sec, secTitle);
+ var dl = sn.element("dl", { "class": type + "s" }, sec);
+ for (var j = 0; j < things.length; j++) {
+ var it = things[j];
+ var id = (type == "method") ? this.makeMethodID(curLnk, it) : sn.idThatDoesNotExist(curLnk + it.refId);
+ var dt = sn.element("dt", { id: id }, dl);
+ sn.element("code", {}, dt, it.id);
+ var desc = sn.element("dd", {}, dl, [it.description]);
+ if (type == "method") {
+ if (it.params.length) {
+ var table = sn.element("table", { "class": "parameters" }, desc);
+ var tr = sn.element("tr", {}, table);
+ ["Parameter", "Type", "Nullable", "Optional", "Description"].forEach(function (tit) { sn.element("th", {}, tr, tit); });
+ for (var k = 0; k < it.params.length; k++) {
+ var prm = it.params[k];
+ var tr = sn.element("tr", {}, table);
+ sn.element("td", { "class": "prmName" }, tr, prm.id);
+ var tyTD = sn.element("td", { "class": "prmType" }, tr);
+ var matched = /^sequence<(.+)>$/.exec(prm.datatype);
+ if (matched) {
+ sn.element("code", {}, tyTD, [ sn.text("sequence<"),
+ sn.element("a", {}, null, matched[1]),
+ sn.text(">")]);
+ }
+ else {
+ var cnt = [sn.element("a", {}, null, prm.datatype)];
+ if (prm.array) cnt.push(sn.text("[]"));
+ sn.element("code", {}, tyTD, cnt);
+ }
+ if (prm.nullable) sn.element("td", { "class": "prmNullTrue" }, tr, "\u2714");
+ else sn.element("td", { "class": "prmNullFalse" }, tr, "\u2718");
+ if (prm.optional) sn.element("td", { "class": "prmOptTrue" }, tr, "\u2714");
+ else sn.element("td", { "class": "prmOptFalse" }, tr, "\u2718");
+ var cnt = prm.description ? [prm.description] : "";
+ sn.element("td", { "class": "prmDesc" }, tr, cnt);
+ }
+ }
+ else {
+ sn.element("div", {}, desc, [sn.element("em", {}, null, "No parameters.")]);
+ }
+ // if (it.raises.length) {
+ // var table = sn.element("table", { "class": "exceptions" }, desc);
+ // var tr = sn.element("tr", {}, table);
+ // ["Exception", "Description"].forEach(function (tit) { sn.element("th", {}, tr, tit); });
+ // for (var k = 0; k < it.raises.length; k++) {
+ // var exc = it.raises[k];
+ // var tr = sn.element("tr", {}, table);
+ // sn.element("td", { "class": "excName" }, tr, [sn.element("a", {}, null, exc.id)]);
+ // var dtd = sn.element("td", { "class": "excDesc" }, tr);
+ // if (exc.type == "simple") {
+ // dtd.appendChild(exc.description);
+ // }
+ // else {
+ // var ctab = sn.element("table", { "class": "exceptionCodes" }, dtd );
+ // for (var m = 0; m < exc.description.length; m++) {
+ // var cd = exc.description[m];
+ // var tr = sn.element("tr", {}, ctab);
+ // sn.element("td", { "class": "excCodeName" }, tr, [sn.element("code", {}, null, cd.id)]);
+ // sn.element("td", { "class": "excCodeDesc" }, tr, [cd.description]);
+ // }
+ // }
+ // }
+ // }
+ // else {
+ // sn.element("div", {}, desc, [sn.element("em", {}, null, "No exceptions.")]);
+ // }
+ var reDiv = sn.element("div", {}, desc);
+ sn.element("em", {}, reDiv, "Return type: ");
+ var matched = /^sequence<(.+)>$/.exec(it.datatype);
+ if (matched) {
+ sn.element("code", {}, reDiv, [ sn.text("sequence<"),
+ sn.element("a", {}, null, matched[1]),
+ sn.text(">")]);
+ }
+ else {
+ var cnt = [sn.element("a", {}, null, it.datatype)];
+ if (it.array) cnt.push(sn.text("[]"));
+ sn.element("code", {}, reDiv, cnt);
+ }
+ if (it.nullable) sn.text(", nullable", reDiv);
+ }
+ else if (type == "attribute") {
+ sn.text(" of type ", dt);
+ if (it.array) sn.text("array of ", dt);
+ var span = sn.element("span", { "class": "idlAttrType" }, dt);
+ var matched = /^sequence<(.+)>$/.exec(it.datatype);
+ if (matched) {
+ sn.text("sequence<", span);
+ sn.element("a", {}, span, matched[1]);
+ sn.text(">", span);
+ }
+ else {
+ sn.element("a", {}, span, it.datatype);
+ }
+ if (it.readonly) sn.text(", readonly", dt);
+ if (it.nullable) sn.text(", nullable", dt);
+
+ // if (it.raises.length) {
+ // var table = sn.element("table", { "class": "exceptions" }, desc);
+ // var tr = sn.element("tr", {}, table);
+ // ["Exception", "On Get", "On Set", "Description"].forEach(function (tit) { sn.element("th", {}, tr, tit); });
+ // for (var k = 0; k < it.raises.length; k++) {
+ // var exc = it.raises[k];
+ // var tr = sn.element("tr", {}, table);
+ // sn.element("td", { "class": "excName" }, tr, [sn.element("a", {}, null, exc.id)]);
+ // ["onGet", "onSet"].forEach(function (gs) {
+ // if (exc[gs]) sn.element("td", { "class": "excGetSetTrue" }, tr, "\u2714");
+ // else sn.element("td", { "class": "excGetSetFalse" }, tr, "\u2718");
+ // });
+ // var dtd = sn.element("td", { "class": "excDesc" }, tr);
+ // if (exc.type == "simple") {
+ // dtd.appendChild(exc.description);
+ // }
+ // else {
+ // var ctab = sn.element("table", { "class": "exceptionCodes" }, dtd );
+ // for (var m = 0; m < exc.description.length; m++) {
+ // var cd = exc.description[m];
+ // var tr = sn.element("tr", {}, ctab);
+ // sn.element("td", { "class": "excCodeName" }, tr, [sn.element("code", {}, null, cd.id)]);
+ // sn.element("td", { "class": "excCodeDesc" }, tr, [cd.description]);
+ // }
+ // }
+ // }
+ // }
+ // else {
+ // sn.element("div", {}, desc, [sn.element("em", {}, null, "No exceptions.")]);
+ // }
+ }
+ else if (type == "constant") {
+ sn.text(" of type ", dt);
+ sn.element("span", { "class": "idlConstType" }, dt, [sn.element("a", {}, null, it.datatype)]);
+ if (it.nullable) sn.text(", nullable", dt);
+ }
+ }
+ }
+ if (typeof obj.merge !== "undefined" && obj.merge.length > 0) {
+ // hackish: delay the execution until the DOM has been initialized, then merge
+ setTimeout(function () {
+ for (var i = 0; i < obj.merge.length; i++) {
+ var idlInterface = document.querySelector("#idl-def-" + obj.refId),
+ idlDictionary = document.querySelector("#idl-def-" + obj.merge[i]);
+ idlDictionary.parentNode.parentNode.removeChild(idlDictionary.parentNode);
+ idlInterface.appendChild(document.createElement("br"));
+ idlInterface.appendChild(idlDictionary);
+ }
+ }, 0);
+ }
+ return df;
+ }
+ },
+
+ makeMethodID: function (cur, obj) {
+ var id = cur + obj.refId + "-" + obj.datatype + "-";
+ var params = [];
+ for (var i = 0, n = obj.params.length; i < n; i++) {
+ var prm = obj.params[i];
+ params.push(prm.datatype + (prm.array ? "Array" : "") + "-" + prm.id)
+ }
+ id += params.join("-");
+ return sn.sanitiseID(id);
+ // return sn.idThatDoesNotExist(id);
+ },
+
+ writeAsWebIDL: function (obj, indent) {
+ if (obj.type == "module") {
+ if (obj.id == "outermost") {
+ var str = "";
+ for (var i = 0; i < obj.children.length; i++) str += this.writeAsWebIDL(obj.children[i], indent);
+ return str;
+ }
+ else {
+ var str = "<span class='idlModule'>";
+ if (obj.extendedAttributes) str += this._idn(indent) + "[<span class='extAttr'>" + obj.extendedAttributes + "</span>]\n";
+ str += this._idn(indent) + "module <span class='idlModuleID'>" + obj.id + "</span> {\n";
+ for (var i = 0; i < obj.children.length; i++) str += this.writeAsWebIDL(obj.children[i], indent + 1);
+ str += this._idn(indent) + "};</span>\n";
+ return str;
+ }
+ }
+ else if (obj.type == "typedef") {
+ var nullable = obj.nullable ? "?" : "";
+ var arr = obj.array ? "[]" : "";
+ return "<span class='idlTypedef' id='idl-def-" + obj.refId + "'>typedef <span class='idlTypedefType'>" +
+ this.writeDatatype(obj.datatype) +
+ "</span>" + arr + nullable + " <span class='idlTypedefID'>" + obj.id + "</span>;</span>";
+ }
+ else if (obj.type == "implements") {
+ return "<span class='idlImplements'><a>" + obj.id + "</a> implements <a>" + obj.datatype + "</a>;";
+ }
+ else if (obj.type == "interface") {
+ var str = "<span class='idlInterface' id='idl-def-" + obj.refId + "'>";
+ if (obj.extendedAttributes) str += this._idn(indent) + "[<span class='extAttr'>" + obj.extendedAttributes + "</span>]\n";
+ str += this._idn(indent);
+ if (obj.partial) str += "partial ";
+ str += "interface <span class='idlInterfaceID'>" + obj.id + "</span>";
+ if (obj.superclasses && obj.superclasses.length) str += " : " +
+ obj.superclasses.map(function (it) {
+ return "<span class='idlSuperclass'><a>" + it + "</a></span>"
+ })
+ .join(", ");
+ str += " {\n";
+ // we process attributes and methods in place
+ var maxAttr = 0, maxMeth = 0, maxConst = 0, hasRO = false;
+ obj.children.forEach(function (it, idx) {
+ var len = it.datatype.length;
+ if (it.nullable) len = len + 1;
+ if (it.array) len = len + 2;
+ if (it.type == "attribute") maxAttr = (len > maxAttr) ? len : maxAttr;
+ else if (it.type == "method") maxMeth = (len > maxMeth) ? len : maxMeth;
+ else if (it.type == "constant") maxConst = (len > maxConst) ? len : maxConst;
+ if (it.type == "attribute" && it.readonly) hasRO = true;
+ });
+ var curLnk = "widl-" + obj.refId + "-";
+ for (var i = 0; i < obj.children.length; i++) {
+ var ch = obj.children[i];
+ if (ch.type == "attribute") str += this.writeAttribute(ch, maxAttr, indent + 1, curLnk, hasRO);
+ else if (ch.type == "method") str += this.writeMethod(ch, maxMeth, indent + 1, curLnk);
+ else if (ch.type == "constant") str += this.writeConst(ch, maxConst, indent + 1, curLnk);
+ }
+ str += this._idn(indent) + "};</span>\n";
+ return str;
+ }
+ else if (obj.type == "exception") {
+ var str = "<span class='idlException' id='idl-def-" + obj.refId + "'>";
+ if (obj.extendedAttributes) str += this._idn(indent) + "[<span class='extAttr'>" + obj.extendedAttributes + "</span>]\n";
+ str += this._idn(indent) + "exception <span class='idlExceptionID'>" + obj.id + "</span> {\n";
+ var maxAttr = 0, maxConst = 0, hasRO = false;
+ obj.children.forEach(function (it, idx) {
+ var len = it.datatype.length;
+ if (it.nullable) len = len + 1;
+ if (it.array) len = len + 2;
+ if (it.type == "field") maxAttr = (len > maxAttr) ? len : maxAttr;
+ else if (it.type == "constant") maxConst = (len > maxConst) ? len : maxConst;
+ });
+ var curLnk = "widl-" + obj.refId + "-";
+ for (var i = 0; i < obj.children.length; i++) {
+ var ch = obj.children[i];
+ if (ch.type == "field") str += this.writeField(ch, maxAttr, indent + 1, curLnk);
+ else if (ch.type == "constant") str += this.writeConst(ch, maxConst, indent + 1, curLnk);
+ }
+ str += this._idn(indent) + "};</span>\n";
+ return str;
+ }
+ else if (obj.type == "dictionary") {
+ var str = "<span class='idlDictionary' id='idl-def-" + obj.refId + "'>";
+ if (obj.extendedAttributes) str += this._idn(indent) + "[<span class='extAttr'>" + obj.extendedAttributes + "</span>]\n";
+ str += this._idn(indent) + "dictionary <span class='idlDictionaryID'>" + obj.id + "</span>";
+ if (obj.superclasses && obj.superclasses.length) str += " : " +
+ obj.superclasses.map(function (it) {
+ return "<span class='idlSuperclass'><a>" + it + "</a></span>"
+ })
+ .join(", ");
+ str += " {\n";
+ var max = 0;
+ obj.children.forEach(function (it, idx) {
+ var len = it.datatype.length;
+ if (it.nullable) len = len + 1;
+ if (it.array) len = len + 2;
+ max = (len > max) ? len : max;
+ });
+ var curLnk = "widl-" + obj.refId + "-";
+ for (var i = 0; i < obj.children.length; i++) {
+ var ch = obj.children[i];
+ str += this.writeMember(ch, max, indent + 1, curLnk);
+ }
+ str += this._idn(indent) + "};</span>\n";
+ return str;
+ }
+ },
+
+ writeField: function (attr, max, indent, curLnk) {
+ var str = "<span class='idlField'>";
+ if (attr.extendedAttributes) str += this._idn(indent) + "[<span class='extAttr'>" + attr.extendedAttributes + "</span>]\n";
+ str += this._idn(indent);
+ var pad = max - attr.datatype.length;
+ if (attr.nullable) pad = pad - 1;
+ if (attr.array) pad = pad - 2;
+ var nullable = attr.nullable ? "?" : "";
+ var arr = attr.array ? "[]" : "";
+ str += "<span class='idlFieldType'>" + this.writeDatatype(attr.datatype) + arr + nullable + "</span> ";
+ for (var i = 0; i < pad; i++) str += " ";
+ str += "<span class='idlFieldName'><a href='#" + curLnk + attr.refId + "'>" + attr.id + "</a></span>";
+ str += ";</span>\n";
+ return str;
+ },
+
+ writeAttribute: function (attr, max, indent, curLnk, hasRO) {
+ var sets = [], gets = [];
+ if (attr.raises.length) {
+ for (var i = 0; i < attr.raises.length; i++) {
+ var exc = attr.raises[i];
+ if (exc.onGet) gets.push(exc);
+ if (exc.onSet) sets.push(exc);
+ }
+ }
+
+ var str = "<span class='idlAttribute'>";
+ if (attr.extendedAttributes) str += this._idn(indent) + "[<span class='extAttr'>" + attr.extendedAttributes + "</span>]\n";
+ str += this._idn(indent);
+ if (hasRO) {
+ if (attr.readonly) str += "readonly ";
+ else str += " ";
+ }
+ str += "attribute ";
+ var pad = max - attr.datatype.length;
+ if (attr.nullable) pad = pad - 1;
+ if (attr.array) pad = pad - 2;
+ var nullable = attr.nullable ? "?" : "";
+ var arr = attr.array ? "[]" : "";
+ str += "<span class='idlAttrType'>" + this.writeDatatype(attr.datatype) + arr + nullable + "</span> ";
+ for (var i = 0; i < pad; i++) str += " ";
+ str += "<span class='idlAttrName'><a href='#" + curLnk + attr.refId + "'>" + attr.id + "</a></span>";
+ // if (gets.length) {
+ // str += " getraises (" +
+ // gets.map(function (it) { return "<span class='idlRaises'><a>" + it.id + "</a></span>"; }).join(", ") +
+ // ")";
+ // }
+ // if (sets.length) {
+ // str += " setraises (" +
+ // sets.map(function (it) { return "<span class='idlRaises'><a>" + it.id + "</a></span>"; }).join(", ") +
+ // ")";
+ // }
+ str += ";</span>\n";
+ return str;
+ },
+
+ writeMethod: function (meth, max, indent, curLnk) {
+ var str = "<span class='idlMethod'>";
+ if (meth.extendedAttributes) str += this._idn(indent) + "[<span class='extAttr'>" + meth.extendedAttributes + "</span>]\n";
+ str += this._idn(indent);
+ var pad = max - meth.datatype.length;
+ if (meth.nullable) pad = pad - 1;
+ if (meth.array) pad = pad - 2;
+ var nullable = meth.nullable ? "?" : "";
+ var arr = meth.array ? "[]" : "";
+ str += "<span class='idlMethType'>" + this.writeDatatype(meth.datatype) + arr + nullable + "</span> ";
+ for (var i = 0; i < pad; i++) str += " ";
+ var id = this.makeMethodID(curLnk, meth);
+ // str += "<span class='idlMethName'><a href='#" + curLnk + meth.refId + "'>" + meth.id + "</a></span> (";
+ str += "<span class='idlMethName'><a href='#" + id + "'>" + meth.id + "</a></span> (";
+ var obj = this;
+ str += meth.params.map(function (it) {
+ var nullable = it.nullable ? "?" : "";
+ var optional = it.optional ? "optional " : "";
+ var arr = it.array ? "[]" : "";
+ var inp = obj.noIDLIn ? "" : "in ";
+ var prm = "<span class='idlParam'>";
+ if (it.extendedAttributes) prm += "[<span class='extAttr'>" + it.extendedAttributes + "</span>] ";
+ prm += inp + optional + "<span class='idlParamType'>" + obj.writeDatatype(it.datatype) + arr + nullable + "</span> " +
+ "<span class='idlParamName'>" + it.id + "</span>" +
+ "</span>";
+ return prm;
+ })
+ .join(", ");
+ str += ")";
+ // if (meth.raises.length) {
+ // str += " raises ("
+ // str += meth.raises.map(function (it) { return "<span class='idlRaises'><a>" + it.id + "</a></span>"; })
+ // .join(", ");
+ // str += ")";
+ // }
+ str += ";</span>\n";
+ return str;
+ },
+
+ writeConst: function (cons, max, indent, curLnk) {
+ var str = "<span class='idlConst'>";
+ str += this._idn(indent);
+ str += "const ";
+ var pad = max - cons.datatype.length;
+ if (cons.nullable) pad = pad - 1;
+ var nullable = cons.nullable ? "?" : "";
+ str += "<span class='idlConstType'><a>" + cons.datatype + "</a>" + nullable + "</span> ";
+ for (var i = 0; i < pad; i++) str += " ";
+ str += "<span class='idlConstName'><a href='#" + curLnk + cons.refId + "'>" + cons.id + "</a></span> = " +
+ "<span class='idlConstValue'>" + cons.value + "</span>;</span>\n";
+ return str;
+ },
+
+ writeMember: function (memb, max, indent, curLnk) {
+ var str = "<span class='idlMember'>";
+ str += this._idn(indent);
+ var pad = max - memb.datatype.length;
+ if (memb.nullable) pad = pad - 1;
+ var nullable = memb.nullable ? "?" : "";
+ str += "<span class='idlMemberType'>" + this.writeDatatype(memb.datatype) + nullable + "</span> ";
+ for (var i = 0; i < pad; i++) str += " ";
+ str += "<span class='idlMemberName'><a href='#" + curLnk + memb.refId + "'>" + memb.id + "</a></span>";
+ if (memb.defaultValue) str += " = <span class='idlMemberValue'>" + memb.defaultValue + "</span>"
+ str += ";</span>\n";
+ return str;
+ },
+
+ writeDatatype: function (dt) {
+ // if (/sequence/.test(dt) || /dict/.test(dt)) {
+ // [tleithea - fix for IE<10 (which does not have the console object present by default)]
+ if (typeof (console) != "undefined" && console.log) console.log(dt);
+ // }
+ var matched = /^sequence<(.+)>$/.exec(dt);
+ if (matched) {
+ // [tleithea - similar fix as noted just above]
+ if (typeof (console) != "undefined" && console.log) console.log("MATCHED!", matched[1]);
+ return "sequence<<a>" + matched[1] + "</a>>";
+ }
+ else {
+ return "<a>" + dt + "</a>";
+ }
+ },
+
+ _idn: function (lvl) {
+ var str = "";
+ for (var i = 0; i < lvl; i++) str += " ";
+ return str;
+ },
+
+ // XXX make this generally available (refactoring)
+ _norm: function (str) {
+ str = str.replace(/^\s+/, "").replace(/\s+$/, "");
+ return str.split(/\s+/).join(" ");
+ },
+
+ _id: function (id) {
+ return id.replace(/[^a-zA-Z_-]/g, "");
+ }
+};
+
+// hackish, but who cares?
+window.onload = function () {
+ // (new berjon.respec()).run();
+ (new berjon.respec()).loadAndRun();
+};
+
+function dbg (obj) {
+ var str = "";
+ for (var k in obj) str += k + "=" + obj[k] + "\n";
+ alert("DUMP\n" + str);
+}
+})();
+
+// ReSpec XPath substitute JS workaround for UA's without DOM L3 XPath support
+// By Travis Leithead (travil AT microsoft dotcom)
+// (select APIs and behaviors specifically for ReSpec's usage of DOM L3 XPath; no more an no less)
+// For IE, requires v.9+
+(function () {
+ if (!document.evaluate) {
+ //////////////////////////////////////
+ // interface XPathResult
+ //////////////////////////////////////
+ // Augments a generic JS Array to appear to be an XPathResult (thus allowing [] notation to work)
+ window.XPathResult = function (list) {
+ list.snapshotLength = list.length;
+ list.snapshotItem = function (index) { return this[index]; };
+ return list;
+ }
+ window.XPathResult.prototype.ORDERED_NODE_SNAPSHOT_TYPE = 7;
+ window.XPathResult.ORDERED_NODE_SNAPSHOT_TYPE = 7;
+
+ //////////////////////////////////////
+ // interface XPathEvaluator
+ //////////////////////////////////////
+ // Not exposed to the window (not needed)
+ function XPathEvaluator(assignee) {
+ var findElementsContainingContextNode = function (element, contextNode) {
+ var allUpList = document.querySelectorAll(element);
+ var resultSet = [];
+ for (var i = 0, len = allUpList.length; i < len; i++) {
+ if (allUpList[i].compareDocumentPosition(contextNode) & 16)
+ resultSet.push(allUpList[i]);
+ }
+ return resultSet;
+ }
+ var allTextCache = null;
+ var buildTextCacheUnderBody = function () {
+ if (allTextCache == null) {
+ var iter = document.createNodeIterator(document.body, 4, function () { return 1; }, false);
+ allTextCache = [];
+ while (n = iter.nextNode()) {
+ allTextCache.push(n);
+ }
+ }
+ // Note: no cache invalidation for dynamic updates...
+ }
+ var getAllTextNodesUnderContext = function (contextNode) {
+ buildTextCacheUnderBody();
+ var candidates = [];
+ for (var i = 0, len = allTextCache.length; i < len; i++) {
+ if (allTextCache[i].compareDocumentPosition(contextNode) & 8)
+ candidates.push(allTextCache[i]);
+ }
+ return candidates;
+ }
+ var findAncestorsOfContextNode = function (element, contextNode) {
+ var allUpList = document.querySelectorAll(element);
+ var candidates = [];
+ for (var i = 0, len = allUpList.length; i < len; i++) {
+ if (allUpList[i].compareDocumentPosition(contextNode) & 16)
+ candidates.push(allUpList[i]);
+ }
+ return candidates;
+ }
+ var findSpecificChildrenOfContextNode = function (contextNode, selector) { // element.querySelectorAll(":scope > "+elementType)
+ var allUpList = contextNode.querySelectorAll(selector);
+ // Limit to children only...
+ var candidates = [];
+ for (var i = 0, len = allUpList.length; i < len; i++) {
+ if (allUpList[i].parentNode == contextNode)
+ candidates.push(allUpList[i]);
+ }
+ return candidates;
+ }
+ assignee.evaluate = function (xPathExpression, contextNode, resolverCallback, type, result) {
+ // "ancestor::x:section|ancestor::section", sec
+ if (xPathExpression == "ancestor::x:section|ancestor::section") // e.g., "section :scope" (but matching section)
+ return XPathResult(findElementsContainingContextNode("section", contextNode));
+ else if (xPathExpression == "./x:section|./section") // e.g., ":scope > section"
+ return XPathResult(findSpecificChildrenOfContextNode(contextNode, "section"));
+ else if (xPathExpression == "./x:section[not(@class='introductory')]|./section[not(@class='introductory')]") // e.g., ":scope > section:not([class='introductory'])"
+ return XPathResult(findSpecificChildrenOfContextNode(contextNode, "section:not([class='introductory'])"));
+ else if (xPathExpression == ".//text()") // Not possible via Selectors API. Note that ":contains("...") can be used to find particular element containers of text
+ return XPathResult(getAllTextNodesUnderContext(contextNode));
+ else if ((xPathExpression == "ancestor::abbr") || (xPathExpression == "ancestor::acronym")) // e.g., "abbr :scope, acronym :scope" (but match the element, not the scope)
+ return XPathResult(findAncestorsOfContextNode((xPathExpression == "ancestor::abbr") ? "abbr" : "acronym", contextNode));
+ else if (xPathExpression == "./dt") // e.g., ":scope > dt"
+ return XPathResult(findSpecificChildrenOfContextNode(contextNode, "dt"));
+ else if (xPathExpression == "dl[@class='parameters']")
+ return XPathResult(contextNode.querySelectorAll("dl[class='parameters']"));
+ else if (xPathExpression == "*[@class='exception']")
+ return XPathResult(contextNode.querySelectorAll("[class='exception']"));
+ else // Anything else (not supported)
+ return XPathResult([]);
+ };
+ }
+ // Document implements XPathExpression
+ if (window.Document) {
+ XPathEvaluator(Document.prototype);
+ }
+ else // no prototype hierarchy support (or Document doesn't exist)
+ XPathEvaluator(window.document);
+ }
+})();
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/xml/ReSpec.js/js/sh_main.min.js Wed Oct 31 13:10:51 2012 +0000
@@ -0,0 +1,4 @@
+/* Copyright (C) 2007, 2008 gnombat@users.sourceforge.net */
+/* License: http://shjs.sourceforge.net/doc/gplv3.html */
+
+if(!this.sh_languages){this.sh_languages={}}var sh_requests={};function sh_isEmailAddress(a){if(/^mailto:/.test(a)){return false}return a.indexOf("@")!==-1}function sh_setHref(b,c,d){var a=d.substring(b[c-2].pos,b[c-1].pos);if(a.length>=2&&a.charAt(0)==="<"&&a.charAt(a.length-1)===">"){a=a.substr(1,a.length-2)}if(sh_isEmailAddress(a)){a="mailto:"+a}b[c-2].node.href=a}function sh_konquerorExec(b){var a=[""];a.index=b.length;a.input=b;return a}function sh_highlightString(B,o){if(/Konqueror/.test(navigator.userAgent)){if(!o.konquered){for(var F=0;F<o.length;F++){for(var H=0;H<o[F].length;H++){var G=o[F][H][0];if(G.source==="$"){G.exec=sh_konquerorExec}}}o.konquered=true}}var N=document.createElement("a");var q=document.createElement("span");var A=[];var j=0;var n=[];var C=0;var k=null;var x=function(i,a){var p=i.length;if(p===0){return}if(!a){var Q=n.length;if(Q!==0){var r=n[Q-1];if(!r[3]){a=r[1]}}}if(k!==a){if(k){A[j++]={pos:C};if(false && k==="sh_url"){sh_setHref(A,j,B)}}if(a){var P;if(false && a==="sh_url"){P=N.cloneNode(false)}else{P=q.cloneNode(false)}P.className=a;A[j++]={node:P,pos:C}}}C+=p;k=a};var t=/\r\n|\r|\n/g;t.lastIndex=0;var d=B.length;while(C<d){var v=C;var l;var w;var h=t.exec(B);if(h===null){l=d;w=d}else{l=h.index;w=t.lastIndex}var g=B.substring(v,l);var M=[];for(;;){var I=C-v;var D;var y=n.length;if(y===0){D=0}else{D=n[y-1][2]}var O=o[D];var z=O.length;var m=M[D];if(!m){m=M[D]=[]}var E=null;var u=-1;for(var K=0;K<z;K++){var f;if(K<m.length&&(m[K]===null||I<=m[K].index)){f=m[K]}else{var c=O[K][0];c.lastIndex=I;f=c.exec(g);m[K]=f}if(f!==null&&(E===null||f.index<E.index)){E=f;u=K;if(f.index===I){break}}}if(E===null){x(g.substring(I),null);break}else{if(E.index>I){x(g.substring(I,E.index),null)}var e=O[u];var J=e[1];var b;if(J instanceof Array){for(var L=0;L<J.length;L++){b=E[L+1];x(b,J[L])}}else{b=E[0];x(b,J)}switch(e[2]){case -1:break;case -2:n.pop();break;case -3:n.length=0;break;default:n.push(e);break}}}if(k){A[j++]={pos:C};if(false && k==="sh_url"){sh_setHref(A,j,B)}k=null}C=w}return A}function sh_getClasses(d){var a=[];var b=d.className;if(b&&b.length>0){var e=b.split(" ");for(var c=0;c<e.length;c++){if(e[c].length>0){a.push(e[c])}}}return a}function sh_addClass(c,a){var d=sh_getClasses(c);for(var b=0;b<d.length;b++){if(a.toLowerCase()===d[b].toLowerCase()){return}}d.push(a);c.className=d.join(" ")}function sh_extractTagsFromNodeList(c,a){var f=c.length;for(var d=0;d<f;d++){var e=c.item(d);switch(e.nodeType){case 1:if(e.nodeName.toLowerCase()==="br"){var b;if(/MSIE/.test(navigator.userAgent)){b="\r"}else{b="\n"}a.text.push(b);a.pos++}else{a.tags.push({node:e.cloneNode(false),pos:a.pos});sh_extractTagsFromNodeList(e.childNodes,a);a.tags.push({pos:a.pos})}break;case 3:case 4:a.text.push(e.data);a.pos+=e.length;break}}}function sh_extractTags(c,b){var a={};a.text=[];a.tags=b;a.pos=0;sh_extractTagsFromNodeList(c.childNodes,a);return a.text.join("")}function sh_mergeTags(d,f){var a=d.length;if(a===0){return f}var c=f.length;if(c===0){return d}var i=[];var e=0;var b=0;while(e<a&&b<c){var h=d[e];var g=f[b];if(h.pos<=g.pos){i.push(h);e++}else{i.push(g);if(f[b+1].pos<=h.pos){b++;i.push(f[b]);b++}else{i.push({pos:h.pos});f[b]={node:g.node.cloneNode(false),pos:h.pos}}}}while(e<a){i.push(d[e]);e++}while(b<c){i.push(f[b]);b++}return i}function sh_insertTags(k,h){var g=document;var l=document.createDocumentFragment();var e=0;var d=k.length;var b=0;var j=h.length;var c=l;while(b<j||e<d){var i;var a;if(e<d){i=k[e];a=i.pos}else{a=j}if(a<=b){if(i.node){var f=i.node;c.appendChild(f);c=f}else{c=c.parentNode}e++}else{c.appendChild(g.createTextNode(h.substring(b,a)));b=a}}return l}function sh_highlightElement(d,g){sh_addClass(d,"sh_sourceCode");var c=[];var e=sh_extractTags(d,c);var f=sh_highlightString(e,g);var b=sh_mergeTags(c,f);var a=sh_insertTags(b,e);while(d.hasChildNodes()){d.removeChild(d.firstChild)}d.appendChild(a)}function sh_getXMLHttpRequest(){if(window.XMLHttpRequest){return new XMLHttpRequest()}else{if(window.ActiveXObject){return new ActiveXObject("Msxml2.XMLHTTP")}}throw"No XMLHttpRequest implementation available"}function sh_load(language,element,prefix,suffix){if(language in sh_requests){sh_requests[language].push(element);return}sh_requests[language]=[element];var request=sh_getXMLHttpRequest();var url=prefix+"sh_"+language+suffix;request.open("GET",url,true);request.onreadystatechange=function(){if(request.readyState===4){try{if(!request.status||request.status===200){eval(request.responseText);var elements=sh_requests[language];for(var i=0;i<elements.length;i++){sh_highlightElement(elements[i],sh_languages[language])}}else{throw"HTTP error: status "+request.status}}finally{request=null}}};request.send(null)}function sh_highlightDocument(g,k){var b=document.getElementsByTagName("pre");for(var e=0;e<b.length;e++){var f=b.item(e);var a=sh_getClasses(f);for(var c=0;c<a.length;c++){var h=a[c].toLowerCase();if(h==="sh_sourcecode"){continue}if(h.substr(0,3)==="sh_"){var d=h.substring(3);if(d in sh_languages){sh_highlightElement(f,sh_languages[d])}else{if(typeof(g)==="string"&&typeof(k)==="string"){sh_load(d,f,g,k)}else{throw'Found <pre> element with class="'+h+'", but no such language exists'}}break}}}};
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/xml/ReSpec.js/js/shortcut.js Wed Oct 31 13:10:51 2012 +0000
@@ -0,0 +1,223 @@
+/**
+ * http://www.openjs.com/scripts/events/keyboard_shortcuts/
+ * Version : 2.01.B
+ * By Binny V A
+ * License : BSD
+ */
+shortcut = {
+ 'all_shortcuts':{},//All the shortcuts are stored in this array
+ 'add': function(shortcut_combination,callback,opt) {
+ //Provide a set of default options
+ var default_options = {
+ 'type':'keydown',
+ 'propagate':false,
+ 'disable_in_input':false,
+ 'target':document,
+ 'keycode':false
+ }
+ if(!opt) opt = default_options;
+ else {
+ for(var dfo in default_options) {
+ if(typeof opt[dfo] == 'undefined') opt[dfo] = default_options[dfo];
+ }
+ }
+
+ var ele = opt.target;
+ if(typeof opt.target == 'string') ele = document.getElementById(opt.target);
+ var ths = this;
+ shortcut_combination = shortcut_combination.toLowerCase();
+
+ //The function to be called at keypress
+ var func = function(e) {
+ e = e || window.event;
+
+ if(opt['disable_in_input']) { //Don't enable shortcut keys in Input, Textarea fields
+ var element;
+ if(e.target) element=e.target;
+ else if(e.srcElement) element=e.srcElement;
+ if(element.nodeType==3) element=element.parentNode;
+
+ if(element.tagName == 'INPUT' || element.tagName == 'TEXTAREA') return;
+ }
+
+ //Find Which key is pressed
+ if (e.keyCode) code = e.keyCode;
+ else if (e.which) code = e.which;
+ var character = String.fromCharCode(code).toLowerCase();
+
+ if(code == 188) character=","; //If the user presses , when the type is onkeydown
+ if(code == 190) character="."; //If the user presses , when the type is onkeydown
+
+ var keys = shortcut_combination.split("+");
+ //Key Pressed - counts the number of valid keypresses - if it is same as the number of keys, the shortcut function is invoked
+ var kp = 0;
+
+ //Work around for stupid Shift key bug created by using lowercase - as a result the shift+num combination was broken
+ var shift_nums = {
+ "`":"~",
+ "1":"!",
+ "2":"@",
+ "3":"#",
+ "4":"$",
+ "5":"%",
+ "6":"^",
+ "7":"&",
+ "8":"*",
+ "9":"(",
+ "0":")",
+ "-":"_",
+ "=":"+",
+ ";":":",
+ "'":"\"",
+ ",":"<",
+ ".":">",
+ "/":"?",
+ "\\":"|"
+ }
+ //Special Keys - and their codes
+ var special_keys = {
+ 'esc':27,
+ 'escape':27,
+ 'tab':9,
+ 'space':32,
+ 'return':13,
+ 'enter':13,
+ 'backspace':8,
+
+ 'scrolllock':145,
+ 'scroll_lock':145,
+ 'scroll':145,
+ 'capslock':20,
+ 'caps_lock':20,
+ 'caps':20,
+ 'numlock':144,
+ 'num_lock':144,
+ 'num':144,
+
+ 'pause':19,
+ 'break':19,
+
+ 'insert':45,
+ 'home':36,
+ 'delete':46,
+ 'end':35,
+
+ 'pageup':33,
+ 'page_up':33,
+ 'pu':33,
+
+ 'pagedown':34,
+ 'page_down':34,
+ 'pd':34,
+
+ 'left':37,
+ 'up':38,
+ 'right':39,
+ 'down':40,
+
+ 'f1':112,
+ 'f2':113,
+ 'f3':114,
+ 'f4':115,
+ 'f5':116,
+ 'f6':117,
+ 'f7':118,
+ 'f8':119,
+ 'f9':120,
+ 'f10':121,
+ 'f11':122,
+ 'f12':123
+ }
+
+ var modifiers = {
+ shift: { wanted:false, pressed:false},
+ ctrl : { wanted:false, pressed:false},
+ alt : { wanted:false, pressed:false},
+ meta : { wanted:false, pressed:false} //Meta is Mac specific
+ };
+
+ if(e.ctrlKey) modifiers.ctrl.pressed = true;
+ if(e.shiftKey) modifiers.shift.pressed = true;
+ if(e.altKey) modifiers.alt.pressed = true;
+ if(e.metaKey) modifiers.meta.pressed = true;
+
+ for(var i=0; k=keys[i],i<keys.length; i++) {
+ //Modifiers
+ if(k == 'ctrl' || k == 'control') {
+ kp++;
+ modifiers.ctrl.wanted = true;
+
+ } else if(k == 'shift') {
+ kp++;
+ modifiers.shift.wanted = true;
+
+ } else if(k == 'alt') {
+ kp++;
+ modifiers.alt.wanted = true;
+ } else if(k == 'meta') {
+ kp++;
+ modifiers.meta.wanted = true;
+ } else if(k.length > 1) { //If it is a special key
+ if(special_keys[k] == code) kp++;
+
+ } else if(opt['keycode']) {
+ if(opt['keycode'] == code) kp++;
+
+ } else { //The special keys did not match
+ if(character == k) kp++;
+ else {
+ if(shift_nums[character] && e.shiftKey) { //Stupid Shift key bug created by using lowercase
+ character = shift_nums[character];
+ if(character == k) kp++;
+ }
+ }
+ }
+ }
+
+ if(kp == keys.length &&
+ modifiers.ctrl.pressed == modifiers.ctrl.wanted &&
+ modifiers.shift.pressed == modifiers.shift.wanted &&
+ modifiers.alt.pressed == modifiers.alt.wanted &&
+ modifiers.meta.pressed == modifiers.meta.wanted) {
+ callback(e);
+
+ if(!opt['propagate']) { //Stop the event
+ //e.cancelBubble is supported by IE - this will kill the bubbling process.
+ e.cancelBubble = true;
+ e.returnValue = false;
+
+ //e.stopPropagation works in Firefox.
+ if (e.stopPropagation) {
+ e.stopPropagation();
+ e.preventDefault();
+ }
+ return false;
+ }
+ }
+ }
+ this.all_shortcuts[shortcut_combination] = {
+ 'callback':func,
+ 'target':ele,
+ 'event': opt['type']
+ };
+ //Attach the function with the event
+ if(ele.addEventListener) ele.addEventListener(opt['type'], func, false);
+ else if(ele.attachEvent) ele.attachEvent('on'+opt['type'], func);
+ else ele['on'+opt['type']] = func;
+ },
+
+ //Remove the shortcut - just specify the shortcut and I will remove the binding
+ 'remove':function(shortcut_combination) {
+ shortcut_combination = shortcut_combination.toLowerCase();
+ var binding = this.all_shortcuts[shortcut_combination];
+ delete(this.all_shortcuts[shortcut_combination])
+ if(!binding) return;
+ var type = binding['event'];
+ var ele = binding['target'];
+ var callback = binding['callback'];
+
+ if(ele.detachEvent) ele.detachEvent('on'+type, callback);
+ else if(ele.removeEventListener) ele.removeEventListener(type, callback, false);
+ else ele['on'+type] = false;
+ }
+}
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/xml/ReSpec.js/js/simple-node.js Wed Oct 31 13:10:51 2012 +0000
@@ -0,0 +1,196 @@
+
+// ------------------------------------------------------------------------------------------ //
+// simple-node.js -- simplified elements creations (based on XML::SimpleNode)
+// Robin Berjon, <robin at berjon dot org>
+// v0.01 - 2009-07-29
+// ------------------------------------------------------------------------------------------ //
+
+
+if (typeof(berjon) == "undefined") berjon = {};
+berjon.simpleNode = function (ns, doc) {
+ // XXX need to default the xml prefix
+ if (!ns) ns = {};
+ if (!doc) doc = document;
+ this.ns = ns;
+ this.doc = doc;
+};
+berjon.calls = {};
+berjon.simpleNode.prototype = {
+
+ // --- NODE CREATION ---
+ element: function (name, attr, parent, content) {
+ if (!attr) attr = {};
+ var nmSt = this._nameToQName(name, false);
+ var el = this.doc.createElementNS(nmSt.ns, name);
+ for (var k in attr) this._setAttr(el, k, attr[k]);
+ if (parent) parent.appendChild(el);
+ if (content) {
+ if (content instanceof Array) for (var i = 0; i < content.length; i++) el.appendChild(content[i]);
+ else this.text(content, el);
+ }
+ return el;
+ },
+
+ text: function (txt, parent) {
+ var tn = this.doc.createTextNode(txt);
+ if (parent) parent.appendChild(tn);
+ return tn;
+ },
+
+ comment: function (txt, parent) {
+ var cmt = this.doc.createComment(txt);
+ if (parent) parent.appendChild(cmt);
+ return cmt;
+ },
+
+ pi: function (target, data, parent) {
+ var pi = this.doc.createProcessingInstruction(target, data);
+ if (parent) parent.appendChild(pi);
+ return pi;
+ },
+
+ documentFragment: function (parent, content) {
+ var df = this.doc.createDocumentFragment();
+ if (content) {
+ if (content instanceof Array) for (var i = 0; i < content.length; i++) df.appendChild(content[i]);
+ else this.text(content, df);
+ }
+ if (parent) parent.appendChild(df);
+ return df;
+ },
+
+ // --- FINDING STUFF ---
+ findNodes: function (xpath, context) {
+ if (!context) context = this.doc;
+ var ns = this.ns;
+ var snap = this.doc.evaluate(xpath,
+ context,
+ function (pfx) { return ns[pfx] || null; },
+ XPathResult.ORDERED_NODE_SNAPSHOT_TYPE,
+ null);
+ var res = [];
+ for (var i = 0; i < snap.snapshotLength; i++) res.push(snap.snapshotItem(i));
+ return res;
+ },
+
+ // --- MANIPULATION ---
+ copyChildren: function (from, to) {
+ while (from.childNodes.length) to.appendChild(from.firstChild);
+ },
+
+ copyAttr: function (from, to) {
+ for (var i = 0; i < from.attributes.length; i++) {
+ var at = from.attributes[i];
+ to.setAttributeNS(at.namespaceURI, at.name, at.value);
+ }
+ },
+
+ renameEl: function (el, name) {
+ // we remove, copy, then insert instead of just replacing because it's a *lot*
+ // faster if the copyChildren operation is done while the node is not being displayed
+ var folSib = el.nextSibling;
+ var par = el.parentNode;
+ if (par) par.removeChild(el);
+ var newEl = this.element(name);
+ this.copyAttr(el, newEl);
+ this.copyChildren(el, newEl);
+ // if (el.parentNode) el.parentNode.replaceChild(newEl, el);
+ if (par) par.insertBefore(newEl, folSib);
+ return newEl;
+ },
+
+ // --- ID MANAGEMENT ---
+ makeID: function (el, pfx, txt) {
+ if (el.hasAttribute("id")) return el.getAttribute("id");
+ var id = "";
+ if (!txt) {
+ if (el.hasAttribute("title")) txt = el.getAttribute("title");
+ else txt = el.textContent;
+ }
+ txt = txt.replace(/^\s+/, "");
+ txt = txt.replace(/\s+$/, "");
+ id += txt;
+ id = id.toLowerCase();
+ if (id.length == 0) id = "generatedID";
+ id = this.sanitiseID(id);
+ if (pfx) id = pfx + "-" + id;
+ id = this.idThatDoesNotExist(id);
+ el.setAttribute("id", id);
+ return id;
+ },
+
+ sanitiseID: function (id) {
+ id = id.split(/[^-.0-9a-zA-Z_]/).join("-");
+ id = id.replace(/^-+/g, "");
+ id = id.replace(/-+$/, "");
+ if (id.length > 0 && /^[^a-z]/.test(id)) id = "x" + id;
+ if (id.length == 0) id = "generatedID";
+ return id;
+ },
+
+ idCache: {},
+ idThatDoesNotExist: function (id) {
+ var inc = 1;
+ if (this.doc.getElementById(id) || this.idCache[id]) {
+ while (this.doc.getElementById(id + "-" + inc) || this.idCache[id + "-" + inc]) inc++;
+ id = id + "-" + inc;
+ }
+ // XXX disable caching for now
+ // this.idCache[id] = true;
+ return id;
+ },
+
+ // --- CLASS HANDLING ---
+ hasClass: function (el, cl) {
+ return this.listClasses(el).indexOf(cl) >= 0;
+ },
+
+ addClass: function (el, cl) {
+ var ls = this.listClasses(el);
+ if (ls.indexOf(cl) >= 0) return;
+ ls.push(cl);
+ this.setClassList(el, ls);
+ },
+
+ removeClass: function (el, cl) {
+ var ls = this.listClasses(el);
+ var idx = ls.indexOf(cl);
+ if (idx < 0) return;
+ ls.splice(idx, 1);
+ this.setClassList(el, ls);
+ },
+
+ listClasses: function (el) {
+ if (el.hasAttribute("class")) {
+ return el.getAttribute("class").split(/\s+/);
+ }
+ else return [];
+ },
+
+ setClassList: function (el, ls) {
+ el.setAttribute("class", ls.join(" "));
+ },
+
+ // --- HELPERS ---
+ _nameToQName: function (name, isAttr) {
+ var matches = /^(.+):(.+)$/.exec(name);
+ var pfx, ns, ln;
+ if (matches) {
+ pfx = matches[1];
+ ln = matches[2];
+ if (!this.ns[pfx]) throw "No namespace declared for prefix '" + pfx + "'";
+ ns = this.ns[pfx];
+ }
+ else {
+ if (isAttr) ns = null;
+ else ns = this.ns[""];
+ ln = name;
+ }
+ return { ns: ns, ln: ln };
+ },
+
+ _setAttr: function (el, name, value) {
+ var nmSt = this._nameToQName(name, true);
+ el.setAttributeNS(nmSt.ns, nmSt.ln, value);
+ }
+};
--- a/xml/prov-xml.html Wed Oct 31 13:09:26 2012 +0000
+++ b/xml/prov-xml.html Wed Oct 31 13:10:51 2012 +0000
@@ -10,19 +10,47 @@
out in the same tree and use relative links so that they'll work offline,
-->
<!-- PM -->
- <style type="text/css">
- .note { font-size:small; margin-left:50px }
- </style>
+ <style type="text/css">
+
+ .note { font-size:small; margin-left:50px }
+
+ table.thinborder {
+ border-width: 1px;
+ border-spacing: 0px;
+ border-style: none;
+ border-color: gray;
+ border-collapse: collapse;
+ }
+
+ table.thinborder th {
+ border-width: 1px;
+ padding: 0px;
+ border-style: solid;
+ border-color: gray;
+ -moz-border-radius: ;
+ }
+
+ table.thinborder td {
+ border-width: 1px;
+ padding: 2px;
+ border-style: solid;
+ border-color: gray;
+ -moz-border-radius: ;
+ }
+
+ </style>
- <script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
+ <!-- TODO, pull down respec.js and fix status=0 bug -->
+ <script type="text/javascript" src="ReSpec.js/js/respec.js" class="remove"></script>
+ <!--<script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>-->
+
<script src="http://www.w3.org/2007/OWL/toggles.js" class="remove"></script>
<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js" class="remove"></script>
<script src="../model/glossary.js" class="remove"></script>
-
+<!--
<script class="remove">
-
function insertSchema(doc, content) {
// return '<code class="language-xml"> ' + doc._esc(content) + '</code>';
return doc._esc(content);
@@ -99,6 +127,115 @@
});
</script>
+ -->
+
+ <!-- This is a test to see if the respec data-oninclude is working -->
+ <script>
+ function insertSchemaComplexType(doc, content, name) {
+ var xml = $.parseXML(content);
+ var segment = $(xml).find('complexType[name~="' + name + '"]')[0];
+ return "<pre>"+doc._esc((new XMLSerializer()).serializeToString(segment))+"</pre>";
+ }
+
+ function insertSchemaElement(doc, content, name) {
+ var xml = $.parseXML(content);
+ var segment = $(xml).find('element[name~="' + name + '"]').not('[type*="Ref"]')[0];
+ return "<pre>"+doc._esc((new XMLSerializer()).serializeToString(segment))+"</pre>";
+ }
+
+ function formatExample(doc, content) {
+ var xml = $.parseXML(content);
+ return "<pre>"+doc._esc((new XMLSerializer()).serializeToString(xml))+"</pre>";
+ }
+
+ function insertSchema_Entity(doc, content) { return insertSchemaComplexType(doc, content, "Entity"); }
+ function insertSchema_entity(doc, content) { return insertSchemaElement(doc, content, "entity"); }
+
+ function insertSchema_Activity(doc, content) { return insertSchemaComplexType(doc, content, "Activity"); }
+ function insertSchema_activity(doc, content) { return insertSchemaElement(doc, content, "activity"); }
+
+ function insertSchema_Agent(doc, content) { return insertSchemaComplexType(doc, content, "Agent"); }
+ function insertSchema_agent(doc, content) { return insertSchemaElement(doc, content, "agent"); }
+
+ function insertSchema_Generation(doc, content) { return insertSchemaComplexType(doc, content, "Generation"); }
+ function insertSchema_wasGeneratedBy(doc, content) { return insertSchemaElement(doc, content, "wasGeneratedBy"); }
+
+ function insertSchema_Usage(doc, content) { return insertSchemaComplexType(doc, content, "Usage"); }
+ function insertSchema_used(doc, content) { return insertSchemaElement(doc, content, "used"); }
+
+ function insertSchema_Communication(doc, content) { return insertSchemaComplexType(doc, content, "Communication"); }
+ function insertSchema_wasInformedBy(doc, content) { return insertSchemaElement(doc, content, "wasInformedBy"); }
+
+ function insertSchema_Start(doc, content) { return insertSchemaComplexType(doc, content, "Start"); }
+ function insertSchema_wasStartedBy(doc, content) { return insertSchemaElement(doc, content, "wasStartedBy"); }
+
+ function insertSchema_End(doc, content) { return insertSchemaComplexType(doc, content, "End"); }
+ function insertSchema_wasEndedBy(doc, content) { return insertSchemaElement(doc, content, "wasEndedBy"); }
+
+ function insertSchema_Invalidation(doc, content) { return insertSchemaComplexType(doc, content, "Invalidation"); }
+ function insertSchema_wasInvalidatedBy(doc, content) { return insertSchemaElement(doc, content, "wasInvalidatedBy"); }
+
+ function insertSchema_Derivation(doc, content) { return insertSchemaComplexType(doc, content, "Derivation"); }
+ function insertSchema_wasDerivedFrom(doc, content) { return insertSchemaElement(doc, content, "wasDerivedFrom"); }
+
+ function insertSchema_Attribution(doc, content) { return insertSchemaComplexType(doc, content, "Attribution"); }
+ function insertSchema_wasAttributedTo(doc, content) { return insertSchemaElement(doc, content, "wasAttributedTo"); }
+
+ function insertSchema_Association(doc, content) { return insertSchemaComplexType(doc, content, "Association"); }
+ function insertSchema_wasAssociatedWith(doc, content) { return insertSchemaElement(doc, content, "wasAssociatedWith"); }
+
+ function insertSchema_Delegation(doc, content) { return insertSchemaComplexType(doc, content, "Delegation"); }
+ function insertSchema_actedOnBehalfOf(doc, content) { return insertSchemaElement(doc, content, "actedOnBehalfOf"); }
+
+ function insertSchema_Influence(doc, content) { return insertSchemaComplexType(doc, content, "Influence"); }
+ function insertSchema_wasInfluencedBy(doc, content) { return insertSchemaElement(doc, content, "wasInfluencedBy"); }
+
+ function insertSchema_Specialization(doc, content) { return insertSchemaComplexType(doc, content, "Specialization"); }
+ function insertSchema_specializationOf(doc, content) { return insertSchemaElement(doc, content, "specializationOf"); }
+
+ function insertSchema_Alternate(doc, content) { return insertSchemaComplexType(doc, content, "Alternate"); }
+ function insertSchema_alternateOf(doc, content) { return insertSchemaElement(doc, content, "alternateOf"); }
+
+ function insertSchema_Mention(doc, content) { return insertSchemaComplexType(doc, content, "Mention"); }
+ function insertSchema_mentionOf(doc, content) { return insertSchemaElement(doc, content, "mentionOf"); }
+
+ function insertSchema_Membership(doc, content) { return insertSchemaComplexType(doc, content, "Membership"); }
+ function insertSchema_hadMember(doc, content) { return insertSchemaElement(doc, content, "hadMember"); }
+
+ function insertSchema_label(doc, content) { return insertSchemaElement(doc, content, "label"); }
+ function insertSchema_role(doc, content) { return insertSchemaElement(doc, content, "role"); }
+ function insertSchema_type(doc, content) { return insertSchemaElement(doc, content, "type"); }
+ function insertSchema_location(doc, content) { return insertSchemaElement(doc, content, "location"); }
+ function insertSchema_value(doc, content) { return insertSchemaElement(doc, content, "value"); }
+
+ </script>
+
+ <script>
+ $(function() {
+ $("pre.schema-type").before("<p>Type definition in XML Schema:</p>");
+ $("pre.schema-usage").before("<p>Usage in XML:</p>");
+ });
+ </script>
+
+ <script class="remove">
+ $(function(){
+ // if glossary is in a string:
+ $('#glossary_div').html(glossary_string).hide()
+ //updateGlossaryRefs();
+
+ $('.glossary-ref').each(function(index) {
+ var ref=$(this).attr('data-ref');
+ var span=$(this).attr('data-withspan');
+ $(this).removeAttr('data-withspan');
+ $(this).removeAttr('data-ref');
+
+ $('#'+ref+'.glossary').contents().clone().appendTo($(this));
+ if (span) {
+ $(this).children('dfn').replaceWith(function(){return $('<span>').addClass('dfn').append($(this).contents())});
+ }
+ });
+ });
+ </script>
<script class="remove">
var addExtraReferences = function() {
@@ -198,24 +335,29 @@
// if you want to have extra CSS, append them to this list
// it is recommended that the respec.css stylesheet be kept
- extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css", "./extra.css"],
+ //extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css", "./extra.css"],
+ extraCSS: [ "http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css" ],
// editors, add as many as you like
// only "name" is required
editors: [
- { name: "TBD" },
-// { name: "Luc Moreau", url: "http://www.ecs.soton.ac.uk/~lavm/",
-// company: "University of Southampton" },
-
+ { name: "(In alphabetical order)" },
+ { name: "Hook Hua",
+ company: "Jet Propulsion Laboratory / California Institute of Technology" },
+ { name: "Curt Tilmes",
+ company: "National Aeronautics and Space Administration" },
+ { name: "Stephan Zednik",
+ url:"http://tw.rpi.edu/web/person/StephanZednik",
+ company: "Rensselaer Polytechnic Institute" },
],
// authors, add as many as you like.
// This is optional, uncomment if you have authors as well as editors.
// only "name" is required. Same format as editors.
-// authors: [
-// { },
-// ],
+ // authors: [
+ // { },
+ // ],
// name of the WG
wg: "Provenance Working Group",
@@ -224,7 +366,7 @@
wgURI: "http://www.w3.org/2011/prov/",
// name (with the @w3c.org) of the public mailing to which comments are due
- wgPublicList: "public-prov-wg",
+ wgPublicList: "public-prov-comments",
// URI of the patent status for this WG, for Rec-track documents
// !!!! IMPORTANT !!!!
@@ -235,29 +377,35 @@
// Add extraReferences to bibliography database
preProcess: [addExtraReferences],
+
+ // will we have a postProcess?
};
</script>
</head>
<body>
- <section id="abstract">
+<section id="abstract">
<p>
-PROV-DM, the PROV data model, is a data model for provenance that describes
-the entities, people and activities involved in
-producing a piece of data or thing.
-PROV-DM is structured in six components, dealing with:
+Provenance is information about entities, activities, and people
+involved in producing a piece of data or thing, which can be used
+ to form assessments about its quality, reliability or trustworthiness.
+PROV-DM is the conceptual data model that forms a basis for the W3C
+provenance (PROV) family of specifications.
+PROV-DM distinguishes core structures, forming the essence of provenance information, from
+extended structures catering for more specific uses of provenance.
+PROV-DM is organized in six components, respectively dealing with:
(1) entities and activities, and the time at which they were created, used, or ended;
-(2) agents bearing responsibility for entities that were generated and actities that happened;
-(3) derivations between entities;
-(4) properties to link entities that refer to a same thing;
-(5) collections of entities, whose provenance can itself be tracked;
-(6) a simple annotation mechanism.
+(2) derivations of entities from entities;
+(3) agents bearing responsibility for entities that were generated and activities that happened;
+(4) a notion of bundle, a mechanism to support provenance of provenance;
+(5) properties to link entities that refer to the same thing; and,
+(6) collections forming a logical structure for its members.
</p>
-<p>This document introduces an XML schema for the PROV data model,
+<p>This document introduces an XML schema for the PROV data model (PROV-DM),
allowing instances of the PROV data model to be serialized in
-XML. </p>
- </section>
+XML.</p>
+</section> <!-- end abstract -->
<section id="sotd">
<h4>PROV Family of Specifications</h4>
@@ -282,19 +430,10 @@
<li>Readers seeking to implement other PROV serializations
should focus on PROV-DM and PROV-DM-CONSTRAINTS. PROV-O, PROV-N, PROV-XML offer examples of mapping to RDF, text, and XML, respectively.</li>
</ul>
-
-
-</section>
-
-
+</section> <!-- end sotd -->
-
-
-
-
- <section id="introduction">
- <h2>Introduction<br>
-</h2>
+<section id="introduction">
+<h2>Introduction</h2>
<p>
For the purpose of this specification, <dfn>provenance</dfn> is defined as a record that describes the people,
@@ -308,7 +447,6 @@
questionable, provenance can help those users to make trust judgements.
</p>
-
<p>A set of specifications, referred to as the PROV family of specifications, define the various aspects
that are necessary to achieve this vision in an interoperable
way:</p>
@@ -327,7 +465,6 @@
<li>PROV-XML: an XML schema for the PROV data model.</li>
</ul>
-
<p>
PROV-DM is a domain-agnostic model, but with clear extensibility points allowing further domain-specific and
application-specific extensions to be defined.
@@ -341,79 +478,221 @@
<li> component 6: a simple annotation mechanism.
</ol>
-
-
-
- <section id="structure-of-this-document">
+<section id="structure-of-this-document">
<h3>Structure of this Document</h3>
-
-
- </section>
-
-<section id="prov-dm-namespace">
- <h3>PROV Namespace</h3>
+</section> <!-- end structure-of-this-document -->
-
+<section id="prov-namespace">
+<h3>PROV Namespace</h3>
<p>The PROV namespace is <span class="name">http://www.w3.org/ns/prov#</span>.</p>
-
<p> All the concepts, reserved names and attributes introduced in this specification belong to the PROV namespace.</p>
+</section> <!-- end prov-namespace -->
-</section>
-
-
- <section id="conventions">
+<section id="conventions">
<h3>Conventions</h3>
-
-
<p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
[[!RFC2119]].</p>
- </section>
-
-</section>
+</section> <!-- end conventions -->
-
+</section> <!-- end introduction -->
-
-<section id="data-model-components">
+<!-- should we instead break the schema down into complex types and elements? -->
+<section id="schema-components">
<h2>PROV XML Schema</h2>
-<p>PROV-DM concepts are structured according to six components that are introduced in this section.
-Components and their dependencies are illustrated in Figure <a href="#prov-dm-components">prov-dm-components</a>. A component that relies on concepts defined in another also sits above it in this figure.
-PROV-DM consists of the following components.</p>
+<p>Provenance concepts, expressed as PROV-DM types and relations, are organized according to six components that are defined in this section.</p>
-<ol>
-<li><b>Component 1: entities and activities.</b> The first component consists of entities, activities, and all concepts linking them, such as generation, usage, start, end. The first component is the only one comprising time-related concepts. </li>
-<li><b>Component 2: agents and responsibility.</b> The second component consists of agents and concepts ascribing responsibility to agents.</li>
-<li><b>Component 3: derivations.</b> The third component is formed with derivations and its derivation subtypes.</li>
-<li><b>Component 4: alternate.</b> The fourth component consists of relations linking entities somehow referring to a same thing. </li>
-<li><b>Component 5: collections.</b> The fifth component is comprised of collections and operations related to collections. </li>
-<li><b>Component 6: annotations.</b> The sixth component is concerned with annotations to PROV-DM concepts.</li>
-</ol>
-
+<div id="prov-dm-components-ul">
+<ul>
+<li><b>Component 1: entities and activities.</b> The first component consists of entities, activities, and concepts linking them, such as generation, usage, start, end. The first component is the only one comprising time-related concepts. </li>
+<li><b>Component 2: derivations.</b> The second component is formed with derivations and derivation subtypes.</li>
+<li><b>Component 3: agents, responsibility, and influence.</b> The third component consists of agents and concepts ascribing responsibility to agents.</li>
+<li><b>Component 4: bundles.</b> The fourth component is concerned with bundles, a mechanism to support provenance of provenance.</li>
+<li><b>Component 5: alternate.</b> The fifth component consists of relations linking entities referring to the same thing. </li>
+<li><b>Component 6: collections.</b> The sixth component is about collections. </li>
+</ul>
+</div>
<div style="text-align: center;">
-<figure style="max-width: 90%; ">
-<img usemap="#componentMap" src="../model/images/components.png" alt="PROV-DM Components" style="max-width: 90%; " />
+<figure style="max-width: 95%; ">
+<img usemap="#componentMap" src="http://dvcs.w3.org/hg/prov/raw-file/default/model/images/dm/components-dependencies.png" alt="PROV-DM Components" style="max-width: 90%; " />
<map id="componentMap" name="componentMap">
-<area title="collections" href="#component5" coords="220,0,440,70" alt="collections" shape="rect"/>
-<area title="alternate" href="#component4" coords="450,0,510,140" alt="alternate" shape="rect"/>
-<area title="annotations" href="#component6" coords="530,0,590,220" alt="annotations" shape="rect"/>
-<area title="activities/entities" href="#component1" coords="80,150,510,220" alt="activities/entities" shape="rect"/>
-<area title="derivations" href="#component3" coords="80,0,210,70" alt="derivations" shape="rect"/>
-<area title="agents/responsibility" href="#component2" coords="0,0,70,220" alt="agents/responsibility" shape="rect"/>
+<area title="agents/responsibility" href="#component3" coords="0,0,67,268" alt="agents/responsibility" shape="rect"/>
+<area title="agents/responsibility" href="#component3" coords="67,0,134,201" alt="agents/responsibility" shape="rect"/>
+<area title="agents/responsibility" href="#component3" coords="134,0,201,67" alt="agents/responsibility" shape="rect"/>
+<area title="derivations" href="#component2" coords="201,0,268,201" alt="derivations" shape="rect"/>
+<area title="derivations" href="#component2" coords="134,67,201,201" alt="derivations" shape="rect"/>
+<area title="alternate" href="#component5" coords="268,0,335,67" alt="alternate" shape="rect"/>
+<area title="alternate" href="#component5" coords="335,0,402,201" alt="alternate" shape="rect"/>
+<area title="collections" href="#component6" coords="402,0,469,201" alt="collections" shape="rect"/>
+<area title="activities/entities" href="#component1" coords="67,201,469,268" alt="activities/entities" shape="rect"/>
+<area title="bundles" href="#component4" coords="268,67,402,201" alt="bundles" shape="rect"/>
</map>
-<figcaption id="prov-dm-components">PROV-DM Components</figcaption>
+<br>
+<figcaption id="prov-dm-components">PROV-DM Components (Informative)</figcaption> <!-- Figure 4 -->
</figure>
</div>
+<!--
<p>
While not all PROV-DM relations are binary, they all involve two primary elements. Hence, Table <a href="#relations-at-a-glance">relations-at-a-glance</a> indexes all relations according to their two primary elements. The table adopts the same color scheme as Figure <a href="#prov-dm-components">prov-dm-components</a>, allowing components to be readily identified.
Note that for simplicity, this table does not include collection-oriented relations.
</p>
+-->
+
+<!-- TODO add mapping of PROV-DM relations to Schema-->
+
+<p><a href="#prov-schema-mapping">Table X</a></p>
+<div id="prov-schema-mapping" style="text-align: left;">
+<table class="thinborder" style="margin-left: auto; margin-right: auto;">
+<caption id="prov-dm-types-and-relations">PROV-DM Types and Relations to XML Schema Mapping</caption> <!-- Table X-->
+<tr><td><a><b>Type or Relation Name</b></a></td><td><b>XML Schema ComplexType or usage</b></td><td><b>Component</b></td></tr>
+<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
+
+<tr class="component1-color">
+ <td class="essential"><a>Entity</a></td>
+ <td><a title="dfn-Entity" class="essential">prov:Entity</a></td>
+ <td rowspan="8"><a href="#component1">Component 1: Entities/Activities</a></td>
+</tr>
+<tr class="component1-color">
+ <td class="essential"><a>Activity</a></td>
+ <td><a title="dfn-Activity" class="essential">prov:Activity</a></td>
+</tr>
+<tr class="component1-color">
+ <td class="essential"><a>Generation</a></td>
+ <td><a title="wasGeneratedBy"><span class="essential">prov:Generation</a></td>
+</tr>
+<tr class="component1-color">
+ <td class="essential"><a>Usage</a></td>
+ <td><a title="used"><span class="essential">prov:Usage</span></a></td>
+</tr>
+<tr class="component1-color">
+ <td class="essential"><a>Communication</a></td>
+ <td><a title="wasInformedBy"><span class="essential">prov:Communication</span></a></td>
+</tr>
+<tr class="component1-color">
+ <td><a>Start</a></td>
+ <td><a title="wasStartedBy">prov:Start</a></td>
+</tr>
+<tr class="component1-color">
+ <td><a>End</a></td>
+ <td><a title="wasEndedBy">prov:End</a></td>
+</tr>
+<tr class="component1-color">
+ <td><a>Invalidation</a></td>
+ <td><a title="wasInvalidatedBy">prov:Invalidation</a></td>
+</tr>
+<tr>
+ <td colspan="3" style="border-width: 0px; "></td>
+</tr>
+<tr class="component2-color">
+ <td class="essential"><a>Derivation</a></td>
+ <td><a title="wasDerivedFrom"><span class="essential">prov:Derivation</span></a></td>
+ <td rowspan="4"><a href="#component2">Component 2: Derivations</a></td>
+</tr>
+<tr class="component2-color">
+ <td class="provType"><a>Revision</a></td>
+ <td><a title="dfn-revision">use <prov:type>prov:Revision</prov:type> in Derivation</a></td>
+</tr>
+<tr class="component2-color">
+ <td class="provType"><a>Quotation</a></td>
+ <td><a title="dfn-quotation">use <prov:type>prov:Quotation</prov:type> in Derivation</a></td>
+</tr>
+<tr class="component2-color">
+ <td class="provType"><a>Primary Source</a></td>
+ <td><a title="dfn-primary-source">use <prov:type>prov:PrimarySource</prov:type> in Derivation</a></td>
+</tr>
+<tr>
+ <td colspan="3" style="border-width: 0px; "></td>
+</tr>
+<tr class="component3-color" style="border-collapse: collapse; ">
+ <td class="essential"><a>Agent</a></td>
+ <td><a title="dfn-agent" class="essential">prov:Agent</a></td>
+ <td rowspan="9"><a href="#component3">Component 3: Agents, Responsibility, Influence</a></td>
+</tr>
+<tr class="component3-color">
+ <td class="essential"><a>Attribution</a></td>
+ <td><a title="wasAttributedTo"><span class="essential">prov:Attribution</span></a></td>
+</tr>
+<tr class="component3-color">
+ <td class="essential"><a>Association</a></td>
+ <td><a title="wasAssociatedWith"><span class="essential">prov:Association</span></a></td>
+</tr>
+<tr class="component3-color">
+ <td class="essential"><a>Delegation</a></td>
+ <td><a title="actedOnBehalfOf"><span class="essential">prov:Delegation</span></a></td>
+</tr>
+<tr class="component3-color">
+ <td class="provType"><a>Plan</a></td>
+ <td><a title="plan"<pre>use <prov:type>prov:Plan</prov:type> in Entity</pre></a></td>
+</tr>
+<tr class="component3-color">
+ <td class="provType"><a>Person</a></td>
+ <td><a title="person">use <prov:type>prov:Person</prov:type> in Agent</a></td>
+</tr>
+<tr class="component3-color">
+ <td class="provType"><a>Organization</a></td>
+ <td><a title="organization">use <prov:type>prov:Organization</prov:type> in Agent</a></td>
+</tr>
+<tr class="component3-color">
+ <td class="provType"><a title="software-agent">SoftwareAgent</a></td>
+ <td><a title="software-agent">use <prov:type>prov:SoftwareAgent</prov:type> in Agent</a></td>
+</tr>
+<tr class="component3-color">
+ <td><a>Influence</a></td>
+ <td><a title="wasInfluencedBy">prov:Influence</a></td>
+</tr>
+<tr>
+ <td colspan="3" style="border-width: 0px; "></td>
+</tr>
+<tr class="component4-color">
+ <td><a title="bundle">Bundle constructor</a></td>
+ <td><a title="dfn-bundle">???</a></td>
+ <td rowspan="2"><a href="#component5">Component 4: Bundles</a></td>
+</tr>
+<tr class="component4-color">
+ <td class="provType"><a title="bundle">Bundle type</a></td>
+ <td><a title="bundle">use <prov:type>prov:Bundle</prov:type> in Entity</a></td>
+</tr>
+<tr>
+ <td colspan="3" style="border-width: 0px; "></td>
+</tr>
+<tr class="component5-color">
+ <td><a>Alternate</a></td>
+ <td><a title="alternateOf">prov:Alternate</a></td>
+ <td rowspan="3"><a href="#component4">Component 5: Alternate</a></td>
+</tr>
+<tr class="component5-color">
+ <td><a>Specialization</a></td>
+ <td><a title="specializationOf">prov:Specialization</a></td>
+</tr>
+<tr class="component5-color">
+ <td><a>Mention</a></td>
+ <td><a title="mentionOf">prov:Mention</a></td>
+</tr>
+<tr>
+ <td colspan="3" style="border-width: 0px; "></td>
+</tr>
+<tr class="component6-color">
+ <td class="provType"><a>Collection</a></td>
+ <td><a title="collection">use <prov:type>prov:Collection</prov:type> in Entity</a></td>
+ <td rowspan="3"><a href="#component6">Component 6: Collections</a></td>
+</tr>
+<tr class="component6-color">
+ <td class="provType"><a title="empty collection">EmptyCollection</a></td>
+ <td><a title="empty collection">use <prov:type>prov:EmptyCollection</prov:type> in Entity</a></td>
+</tr>
+<tr class="component6-color">
+ <td><a>Membership</a></td>
+ <td><a title="hadMember">prov:Membership</a></td>
+</tr>
+<!-- add section for 'further elements' -->
+</table>
+</div>
<p>In the rest of the section, each type is defined, in English initially, followed by its XML schema definition and some example.</p>
@@ -423,330 +702,1202 @@
<p>The first component of PROV-DM is concerned with <a title="entity">entities</a> and <a title="activity">activities</a>, and their inter-relations: <a>Usage</a>, <a>Generation</a>, <a>Start</a>, <a>End</a>, <a>Communication</a>, and <a>Start by Activity</a>. </p>
-
-
-
- <section id="term-Entity">
-
+<section id="term-Entity">
<h4>Entity</h4>
+<div class="glossary-ref" data-ref="glossary-entity"></div>
+<pre class="schema-type">
+<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Entity">
+ <xs:sequence>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:location"/>
+ <xs:element ref="prov:value"/>
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+</xs:complexType>
+</pre>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="entity" type="prov:Entity"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#"
+ xmlns:tr="http://example.com/ns/tr#">
-
-<div class="glossary-ref" data-ref="glossary-entity"></div>
+ <b><prov:entity prov:id="tr:WD-prov-dm-20111215">
+ <prov:type>document</prov:type>
+ <ex:version>2</ex:version>
+ </prov:entity></b>
-<pre class='schema' data-name='entity' data-include='schema/prov.xsd' data-oninclude='insertSchemaEntity' ></pre>
-
-
-</section>
-
+</prov:document>
+</pre>
+</section> <!-- end term-Entity -->
<section id="term-Activity">
-
<h3>Activity</h3>
-
<div class="glossary-ref" data-ref="glossary-activity"></div>
+<pre class="schema-type">
+<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Activity">
+ <xs:sequence>
+ <xs:element name="startTime" type="xs:dateTime" minOccurs="0"/>
+ <xs:element name="endTime" type="xs:dateTime" minOccurs="0"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:location"/>
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+</xs:complexType>
+</pre>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="activity" type="prov:Activity"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#">
-<pre class='schema' data-name='entity' data-include='schema/prov.xsd' data-oninclude='insertSchemaActivity' ></pre>
+ <b><prov:activity prov:id="a1">
+ <prov:startTime>2011-11-16T16:05:00</prov:startTime>
+ <prov:endTime>2011-11-16T16:06:00</prov:endTime>
+ <prov:type>ex:edit</prov:type>
+ <ex:host>server.example.org</ex:host>
+ </prov:activity></b>
-</section>
-
-
+</prov:document>
+</pre>
+</section> <!-- end term-Activity -->
<section id="term-Generation">
<h4>Generation</h4>
-
<div class="glossary-ref" data-ref="glossary-generation"></div>
+<pre class="schema-type">
+<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Generation">
+ <xs:sequence>
+ <xs:element name="entity" type="prov:EntityRef"/>
+ <xs:element name="activity" type="prov:ActivityRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:location"/>
+ <xs:element ref="prov:role"/>
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+</xs:complexType>
+</pre>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasGeneratedBy" type="prov:Generation"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#">
-<pre class='schema' data-name='wasGeneratedBy' data-include='schema/prov.xsd' data-oninclude='insertSchemaWasGeneratedBy' ></pre>
+ <prov:entity prov:id="e1"/>
-</section>
+ <prov:activity prov:id="a1"/>
+ <b><prov:wasGeneratedBy>
+ <prov:entity prov:ref="e1"/>
+ <prov:activity prov:ref="a1"/>
+ <prov:time>2001-10-26T21:32:52</prov:time>
+ <ex:port>p1</ex:port>
+ </prov:wasGeneratedBy></b>
+
+ <prov:entity prov:id="e2"/>
+
+ <b><prov:wasGeneratedBy>
+ <prov:entity prov:ref="e2"/>
+ <prov:activity prov:ref="a1"/>
+ <prov:time>2001-10-26T10:00:00</prov:time>
+ <ex:port>p2</ex:port>
+ </prov:wasGeneratedBy></b>
+
+</prov:document>
+</pre>
+</section> <!-- end term-Generation -->
<section id="term-Usage">
<h3>Usage</h3>
-
<div class="glossary-ref" data-ref="glossary-usage"></div>
+<pre class="schema-type">
+<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Usage">
+ <xs:sequence>
+ <xs:element name="activity" type="prov:ActivityRef"/>
+ <xs:element name="entity" type="prov:EntityRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:location"/>
+ <xs:element ref="prov:role"/>
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+</xs:complexType>
+</pre>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="used" type="prov:Usage"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#">
-<pre class='schema' data-name='used' data-include='schema/prov.xsd' data-oninclude='insertSchemaUsed' ></pre>
+ <prov:activity prov:id="a1"/>
-</section>
+ <prov:entity prov:id="e1"/>
+ <prov:entity prov:id="e2"/>
+
+ <b><prov:used>
+ <prov:activity prov:ref="a1"/>
+ <prov:entity prov:ref="e1"/>
+ <prov:time≶2011-11-16T16:00:00</prov:time>
+ <ex:parameter>p1</ex:parameter>
+ </prov:used></b>
+
+ <b><prov:used>
+ <prov:activity prov:ref="a1"/>
+ <prov:entity prov:ref="e2"/>
+ <prov:time>2011-11-16T16:00:01</prov:time>
+ <ex:parameter>p2</ex:parameter>
+ </prov:used></b>
+
+</prov:document>
+</pre>
+</section> <!-- end term-Usage -->
+
+<section id="term-Communication">
+<h3>Communication</h3>
+<div class="glossary-ref" data-ref="glossary-communication"></div>
+<pre class="schema-type">
+<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Communication">
+ <xs:sequence>
+ <xs:element name="informed" type="prov:ActivityRef"/>
+ <xs:element name="informant" type="prov:ActivityRef"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+</xs:complexType>
+</pre>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInformedBy" type="prov:Communication"/>
+</pre>
+<pre class="example">
+<prov:document xmlns:prov="http://www.w3.org/ns/prov#">
+
+ <prov:activity prov:id="a1">
+ <prov:type>traffic regulations enforcing<prov:type>
+ </prov:activity>
+
+ <prov:activity prov:id="a2">
+ <prov:type>fine paying, check writing, and mailing</prov:type>
+ </prov:activity>
+
+ <b><prov:wasInformedBy>
+ <prov:informed prov:ref="a2"/>
+ <prov:informant prov:ref="a1"/>
+ </prov:wasInformedBy></b>
+
+</prov:document>
+</pre>
+</section> <!-- end term-Communication -->
<section id="term-Start">
<h4>Start</h4>
-
<div class="glossary-ref" data-ref="glossary-start"></div>
+<pre class="schema-type">
+<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Start">
+ <xs:sequence>
+ <xs:element name="activity" type="prov:ActivityRef"/>
+ <xs:element name="trigger" type="prov:EntityRef" minOccurs="0"/>
+ <xs:element name="starter" type="prov:ActivityRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:location"/>
+ <xs:element ref="prov:role"/>
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+</xs:complexType>
+</pre>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasStartedBy" type="prov:Start"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#">
-<pre class='schema' data-name='wasStartedBy' data-include='schema/prov.xsd' data-oninclude='insertSchemaWasStartedBy' ></pre>
+ <prov:entity prov:id="e1">
+ <prov:type>email message</prov:type>
+ </prov:entity>
-</section>
+ <prov:activity prov:id="a1">
+ <prov:type>Discuss</prov:type>
+ </prov:activity>
+
+ <b><prov:wasStartedBy>
+ <prov:activity prov:ref="a1"/>
+ <prov:trigger prov:ref="e1"/>
+ <prov:time>2011-11-16T16:05:00</prov:time>
+ </prov:wasStartedBy></b>
+
+ <prov:used>
+ <prov:activity prov:ref="a1"/>
+ <prov:entity prov:ref="e1"/>
+ </prov:used>
+
+ <prov:activity prov:id="a0">
+ <prov:type>Write</prov:type>
+ </prov:activity>
+
+ <prov:wasGeneratedBy>
+ <prov:entity prov:ref="e1"/>
+ <prov:activity prov:ref="a0"/>
+ </prov:wasGeneratedBy>
+
+ <b><prov:wasStartedBy>
+ <prov:activity prov:ref="a1"/>
+ <prov:trigger prov:ref="e1"/>
+ <prov:starter prov:ref="a0"/>
+ <prov:time>2011-11-16T16:05:00</prov:time>
+ </prov:wasStartedBy></b>
+
+ <b><prov:wasStartedBy>
+ <prov:activity prov:ref="a1"/>
+ <prov:starter prov:ref="a0"/>
+ <prov:time>2011-11-16T16:05:00</prov:time>
+ </prov:wasStartedBy></b>
+
+</prov:document>
+</pre>
+</section> <!-- end term-Start -->
<section id="term-End">
<h4>End</h4>
-
<div class="glossary-ref" data-ref="glossary-end"></div>
-
-<pre class='schema' data-name='wasEndedBy' data-include='schema/prov.xsd' data-oninclude='insertSchemaWasEndedBy' ></pre>
-
-</section>
-
-<section id="term-wasInformedBy">
-<h3>Communication</h3>
-
-<div class="glossary-ref" data-ref="glossary-communication"></div>
+<pre class="schema-type">
+<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="End">
+ <xs:sequence>
+ <xs:element name="activity" type="prov:ActivityRef"/>
+ <xs:element name="trigger" type="prov:EntityRef" minOccurs="0"/>
+ <xs:element name="ender" type="prov:ActivityRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:location"/>
+ <xs:element ref="prov:role"/>
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+</xs:complexType>
+</pre>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasEndedBy" ype="prov:End"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#">
-<pre class='schema' data-name='wasInformedBy' data-include='schema/prov.xsd' data-oninclude='insertSchemaWasInformedBy' ></pre>
-</section>
-
-<section id="term-wasStartedByActivity">
-<h3>Start by Activity</h3>
+ <prov:entity prov:id="e1">
+ <prov:type>approval document</prov:type>
+ </prov:entity>
-<div class="glossary-ref" data-ref="glossary-startByActivity"></div>
+ <prov:activity prov:id="a1">
+ <prov:type>Editing</prov:type>
+ </prov:activity>
-<pre class='schema' data-name='wasStartedByActivity' data-include='schema/prov.xsd' data-oninclude='insertSchemaWasStartedByActivity' ></pre>
-</section>
+ <b><prov:wasEndedBy>
+ <prov:activity prov:ref="a1"/>
+ <prov:trigger prov:ref="e1"/>
+ </prov:wasEndedBy></b>
+</prov:document>
+</pre>
+</section> <!-- end term-End -->
-</section>
+<section id="term-Invalidation">
+<h3>Invalidation</h3>
+<div class="glossary-ref" data-ref="glossary-invalidation"></div>
+<pre class="schema-type">
+<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Invalidation">
+ <xs:sequence>
+ <xs:element name="entity" type="prov:EntityRef"/>
+ <xs:element name="activity" type="prov:ActivityRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:location"/>
+ <xs:element ref="prov:role"/>
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+</xs:complexType>
+</pre>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInvalidatedBy" type="prov:Invalidation"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#"
+ xmlns:bbc="http://www.bbc.co.uk/news/">
+
+ <prov:entity prov:id="ex:The-Painter"/>
+
+ <prov:agent prov:id="ex:Picasso"/>
+
+ <prov:wasAttributedTo>
+ <prov:entity prov:ref="ex:The-Painter" />
+ <prov:agent prov:ref="ex:Picasso" />
+ </prov:wasAttributedTo>
+
+ <prov:activity prov:id="ex:crash"/>
+
+ <b><prov:wasInvalidatedBy>
+ <prov:entity prov:ref="ex:The-Painter"/>
+ <prov:activity prov:ref="ex:crash"/>
+ <prov:time>1998-09-03T01:31:00</prov:time>
+ <ex:circumstances>plane accident</ex:circumstances>
+ </prov:wasInvalidatedBy></b>
+
+</prov:document>
+</pre>
+</section> <!-- end term-Invalidation -->
+
+</section> <!-- end component1 -->
<section id="component2">
-<h3>Component 2: Agents and Responsibility</h3>
-
-<p>The second component of PROV-DM is concerned with <a title="agent">agents</a> and the notions of
-<a>Attribution</a>, <a>Association</a>, <a>Responsibility</a>, relating agents to entities, activities, and agents, respectively.
-</p>
-
-
-<section id="term-Agent">
-<h3>Agent</h3>
-
-<div class="glossary-ref" data-ref="glossary-agent"></div>
-
-<pre class='schema' data-name='agent' data-include='schema/prov.xsd' data-oninclude='insertSchemaAgent' ></pre>
-
-
-</section>
-
-<section id="term-attribution">
-<h3>Attribution</h3>
-
-<div class="glossary-ref" data-ref="glossary-attribution"></div>
-
-<pre class='schema' data-name='wasAttributedTo' data-include='schema/prov.xsd' data-oninclude='insertSchemaWasAttributedTo' ></pre>
-
-
-</section> <!-- end attribution -->
-
-
-<section id="term-ActivityAssociation">
-<h4>Association</h4>
-
-<div class="glossary-ref" data-ref="glossary-activityAssociation"></div>
-
-<pre class='schema' data-name='wasAssociatedWith' data-include='schema/prov.xsd' data-oninclude='insertSchemaWasAssociatedWith' ></pre>
+<h3>Component 2: Derivations</h3>
-</section> <!-- end wasAssociatedWith -->
-
-<section id="term-responsibility">
-
-<h4>Responsibility</h4>
-
-<div class="glossary-ref" data-ref="glossary-responsibility"></div>
-
-<pre class='schema' data-name='actedOnBehalfOf' data-include='schema/prov.xsd' data-oninclude='insertSchemaActedOnBehalfOf' ></pre>
-
-</section>
-
-
-
-</section>
-
-<section id="component3">
-<h3>Component 3: Derivations</h3>
+<p>The second component of PROV-DM is concerned with: <a title="derivation">derivations</a> of <a title="entity">entities</a> from other entities and derivation subtypes WasRevisionOf (<a>Revision</a>), WasQuotedFrom (<a>Quotation</a>), and HasPrimarySource (<a>Primary Source</a>).</p>
-
-
-<p>The third component of PROV-DM is concerned with <a title="derivation">derivations</a> between <a title="entity">entities</a>, and subtypes of derivations <a>Revision</a>, <a>Quotation</a>, <a>Original Source</a>, and <a>Traceability</a>.
-</p>
-
-
-
-<section id="Derivation-Relation">
+<section id="term-Derivation">
<h4>Derivation</h4>
-
-
-
-
+<div class="glossary-ref" data-ref="glossary-derivation"></div>
+<pre class="schema-type">
+<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Derivation">
+ <xs:sequence>
+ <xs:element name="generatedEntity" type="prov:EntityRef"/>
+ <xs:element name="usedEntity" type="prov:EntityRef"/>
+ <xs:element name="activity" type="prov:ActivityRef" minOccurs="0"/>
+ <xs:element name="generation" type="prov:GenerationRef" minOccurs="0"/>
+ <xs:element name="usage" type="prov:UsageRef" minOccurs="0"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+</xs:complexType>
+</pre>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasDerivedFrom" type="prov:Derivation"/>
+</pre>
+<pre class="example">
+<prov:document xmlns:prov="http://www.w3.org/ns/prov#">
-<div class="glossary-ref" data-ref="glossary-derivation"></div>
+ <prov:entity prov:id="e1"/>
-<pre class='schema' data-name='wasDerivedFrom' data-include='schema/prov.xsd' data-oninclude='insertSchemaWasDerivedFrom' ></pre>
+ <prov:entity prov:id="e2"/>
-</section>
+ <b><prov:wasDerivedFrom>
+ <prov:generatedEntity prov:ref="e2"/>
+ <prov:usedEntity prov:ref="e1"/>
+ </prov:wasDerivedFrom></b>
+
+ <b><prov:wasDerivedFrom>
+ <prov:generatedEntity prov:ref="e2"/>
+ <prov:usedEntity prov:ref="e1"/>
+ <prov:type>physical transform</prov:type>
+ </prov:wasDerivedFrom></b>
+
+</prov:document>
+</pre>
+</section> <!-- end term-Derivation -->
<section id="term-Revision">
<h3>Revision</h3>
-
-<p><span class="glossary-ref" data-ref="glossary-revision"></span></p>
-
-<pre class='schema' data-name='wasRevisionOf' data-include='schema/prov.xsd' data-oninclude='insertSchemaWasRevisionOf' ></pre>
-
-
-
-</section> <!-- end revision -->
-
-<section id="term-quotation">
-<h3>Quotation</h3>
-
-<p>
-<span class="glossary-ref" data-ref="glossary-quotation"></span>
-</p>
-
-<pre class='schema' data-name='wasQuotedFrom' data-include='schema/prov.xsd' data-oninclude='insertSchemaWasQuotedFrom' ></pre>
-
-</section> <!-- end quotation -->
-
-
-<section id="term-original-source">
-<h3>Original Source</h3>
-
-<p>
-<span class="glossary-ref" data-ref="glossary-original-source"></span>
-</p>
-
-<pre class='schema' data-name='hadOriginalSource' data-include='schema/prov.xsd' data-oninclude='insertSchemaHadOriginalSource' ></pre>
-
-</section> <!-- end original source -->
-
-<section id="term-traceability">
-<h3>Traceability</h3>
-
-<p>
-<span class="glossary-ref" data-ref="glossary-traceability"></span>
-</p>
+<div class="glossary-ref" data-ref="glossary-revision"></div>
+<p>To specialize a Derivation relationship as a Revision relationship, include a <code>prov:type</code> with the value "prov:Revision".</p>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:rec54="http://www.w3.org/2001/02pd/rec54#"
+ xmlns:tr="http://example.com/ns/tr#">
-<pre class='schema' data-name='tracedTo' data-include='schema/prov.xsd' data-oninclude='insertSchemaTracedTo' ></pre>
-
-</section>
-
-</section>
-
-<section id="component4">
-<h3>Component 4: Alternate Entities</h3>
-
-
-<p>The fourth component of PROV-DM is concerned with
-relations <a>specialization</a> and <a>alternate</a> between entities.
-</p>
-
-
-<section id="term-specialization">
-
-<h4>Specialization</h4>
+ <prov:entity prov:id="tr:WD-prov-dm-20111215">
+ <prov:type>rec54:WD</prov:type>
+ </prov:entity>
-
-<span class="glossary-ref" data-ref="glossary-specialization"></span>
-
-<pre class='schema' data-name='specializationOf' data-include='schema/prov.xsd' data-oninclude='insertSchemaSpecializationOf' ></pre>
-
-</section>
-
-<section id="term-alternate">
+ <prov:entity prov:id="tr:WD-prov-dm-20111018">
+ <prov:type>rec54:WD</prov:type>
+ </prov:entity>
-<h4>Alternate</h4>
-
-
-<span class="glossary-ref" data-ref="glossary-alternate"></span>
+ <prov:wasDerivedFrom>
+ <prov:generatedEntity prov:ref="tr:WD-prov-dm-20111215"/>
+ <prov:usedEntity prov:ref="tr:WD-prov-dm-20111018"/>
+ <b><prov:type>prov:Revision</prov:type></b>
+ </prov:wasDerivedFrom>
-<pre class='schema' data-name='alternateOf' data-include='schema/prov.xsd' data-oninclude='insertSchemaAlternateOf' ></pre>
-
-</section>
+</prov:document>
+</pre>
+</section> <!-- end term-Revision -->
-</section>
+<section id="term-Quotation">
+<h3>Quotation</h3>
+<div class="glossary-ref" data-ref="glossary-quotation"></div>
+<p>To specialize a Derivation relationship as a Quotation relationship, include a <code>prov:type</code> with the value "prov:Quotation".</p>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:wp="http://thinklinks.wordpress.com/2012/03/07/"
+ xmlns:ex="http://example.com/ns/ex#"
+ xmlns:dm="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html#">
+ <prov:entity prov:id="wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop"/>
+
+ <prov:entity prov:id="dm:bl-dagstuhl"/>
+
+ <prov:agent prov:id="ex:Luc"/>
+
+ <prov:agent prov:id="ex:Paul"/>
+
+ <prov:wasDerivedFrom>
+ <prov:generatedEntity prov:ref="dm:gl-dagstuhl"/>
+ <prov:usedEntity prov:ref="wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop"/>
+ <b><prov:type>prov:Quotation</prov:type></b>
+ </prov:wasDerivedFrom>
+
+ <prov:wasAttributedTo>
+ <prov:entity prov:ref="dm:bl-dagstuhl"/>
+ <prov:agent prov:ref="ex:Luc"/>
+ </prov:wasAttributedTo>
+
+ <prov:wasAttributedTo>
+ <prov:entity prov:ref="wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop"/>
+ <prov:agent prov:ref="ex:Paul"/>
+ </prov:wasAttributedTo>
+
+</prov:document>
+</pre>
+</section> <!-- end term-Quotation -->
+
+<section id="term-Primary-Source">
+<h3>Primary Source</h3>
+<div class="glossary-ref" data-ref="glossary-primary-source"></div>
+<p>To specialize a Derivation relationship as a Primary Source relationship, include a <code>prov:type</code> with the value "prov:PrimarySource".</p>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#">
+
+ <prov:entity prov:id="ex:la-campagne-de-Russie-1812-1813">
+ <prov:type>map</prov:type>
+ </prov:entity>
+
+ <prov:entity prov:id="ex:revue-d-Histoire-de-la-Pharmacie-t-XVIII">
+ <prov:type>journal</prov:type>
+ </prov:entity>
+
+ <prov:wasDerivedFrom>
+ <prov:generatedEntity prov:ref="ex:la-campagne-de-Russie-1812-1813"/>
+ <prov:usedEntity prov:ref="ex:revue-d-Histoire-de-la-Pharmacie-t-XVIII"/>
+ <b><prov:type>prov:PrimarySource</prov:type></b>
+ </prov:wasDerivedFrom>
+
+</prov:document>
+</pre>
+</section> <!-- end term-Primary-Source -->
+
+</section> <!-- end component2 -->
+
+<section id="component3">
+<h3>Component 3: Agents, Responsibility, and Influence</h3>
+
+<p>The second component of PROV-DM, depicted in <a href="#figure-component3">Figure 7</a>, is concerned with <a title="agent">agents</a> and the relations WasAttributedTo
+(<a>Attribution</a>), WasAssociatedWith (<a>Association</a>), ActedOnBehalfOf (<a>Delegation</a>), relating agents to entities, activities, and agents, respectively.</p>
+
+<section id="term-Agent">
+<h3>Agent</h3>
+<div class="glossary-ref" data-ref="glossary-agent"></div>
+<pre class="schema-type">
+<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Agent">
+ <xs:sequence>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:location"/>
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+</xs:complexType>
+</pre>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="agent" type="prov:Agent"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#">
+
+ <b><prov:agent prov:id="e1">
+ <prov:type>prov:Person</prov:type>
+ <ex:name>Alice</ex:name>
+ <ex:employee>1234</ex:employee>
+ </prov:agent></b>
+
+</prov:document>
+</pre>
+</section> <!-- end term-Agent -->
+
+<section id="term-Attribution">
+<h3>Attribution</h3>
+<div class="glossary-ref" data-ref="glossary-attribution"></div>
+<pre class="schema-type">
+<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Attribution">
+ <xs:sequence>
+ <xs:element name="entity" type="prov:EntityRef"/>
+ <xs:element name="agent" type="prov:AgentRef"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+</xs:complexType>
+</pre>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasAttributedTo" type="prov:Attribution"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#"
+ xmlns:tr="http://example.com/ns/tr#"
+ xmlns:rec54="http://example.com/ns/rec54#">
+
+ <prov:agent prov:id="ex:Paolo">
+ <prov:type>prov:Person</prov:type>
+ </prov:agent>
+
+ <prov:agent prov:id="ex:Simon">
+ <prov:type>prov:Person</prov:type>
+ </prov:agent>
+
+ <prov:entity prov:id="tr:WD-prov-dm-20111215">
+ <prov:type>rec54:WD</prov:type>
+ </prov:entity>
+
+ <b><prov:wasAttributedTo>
+ <prov:entity prov:ref="rec54:WD"/>
+ <prov:agent prov:ref="ex:Paolo"/>
+ <prov:type>editorship</prov:type>
+ </prov:wasAttributedTo></b>
+
+ <b><prov:wasAttributedTo>
+ <prov:entity prov:ref="rec54:WD"/>
+ <prov:agent prov:ref="ex:Simon"/>
+ <prov:type>authorship</prov:type>
+ </prov:wasAttributedTo></b>
+
+</prov:document>
+</pre>
+</section> <!-- end term-Attribution -->
+
+<section id="term-Association">
+<h4>Association</h4>
+<div class="glossary-ref" data-ref="glossary-activityAssociation"></div>
+<pre class="schema-type">
+<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Association">
+ <xs:sequence>
+ <xs:element name="activity" type="prov:ActivityRef"/>
+ <xs:element name="agent" type="prov:AgentRef" minOccurs="0"/>
+ <xs:element name="plan" type="prov:EntityRef" minOccurs="0"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:role"/>
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+</xs:complexType>
+</pre>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasAssociatedWith" type="prov:Association"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xmlns:ex="http://example.com/ns/ex#">
+
+ <prov:activity prov:id="a">
+ <prov:type>workflow execution</prov:type>
+ </prov:activity>
+
+ <prov:agent prov:id="ag1">
+ <prov:type>operator</prov:type>
+ </prov:agent>
+
+ <prov:agent prov:id="ag2">
+ <prov:type>designator</prov:type>
+ </prov:agent>
+
+ <b><prov:wasAssociatedWith>
+ <prov:activity prov:ref="a"/>
+ <prov:agent prov:ref="ag1"/>
+ <prov:role>loggedInUser</prov:role>
+ <ex:how>webapp</ex:how>
+ </prov:wasAssociatedWith></b>
+
+ <b><prov:wasAssociatedWith>
+ <prov:activity prov:ref="a"/>
+ <prov:agent prov:ref="ag2"/>
+ <prov:plan prov:ref="ex:wf"/>
+ <prov:role>designer</prov:role>
+ <ex:content>project1</ex:content>
+ </prov:wasAssociatedWith></b>
+
+ <prov:entity prov:id="ex:wf">
+ <prov:type>prov:Plan</prov:type>
+ <ex:label>Workflow 1</ex:label>
+ <prov:location>http://example.org/workflow1.bpel</prov:location>
+ </prov:entity>
+
+</prov:document>
+</pre>
+</section> <!-- end term-Association -->
+
+<section id="term-Delegation">
+<h4>Delegation</h4>
+<div class="glossary-ref" data-ref="glossary-delegation"></div>
+<pre class="schema-type">
+<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Delegation">
+ <xs:sequence>
+ <xs:element name="delegate" type="prov:AgentRef"/>
+ <xs:element name="responsible" type="prov:AgentRef"/>
+ <xs:element name="activity" type="prov:ActivityRef" minOccurs="0"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+</xs:complexType>
+</pre>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="actedOnBehalfOf" type="prov:Delegation"/>
+</pre>
+<pre class="example">
+<prov:document xmlns:prov="http://www.w3.org/ns/prov#">
+
+ <prov:activity prov:id="a">
+ <prov:type>workflow</prov:type>
+ </prov:activity>
+
+ <prov:agent prov:id="ag1">
+ <prov:type>programmer</prov:type>
+ </prov:agent>
+
+ <prov:agent prov:id="ag2">
+ <prov:type>researcher</prov:type>
+ </prov:agent>
+
+ <prov:agent prov:id="ag3">
+ <prov:type>funder</prov:type>
+ </prov:agent>
+
+ <prov:wasAssociatedWith>
+ <prov:activity prov:ref="a"/>
+ <prov:agent prov:ref="ag1"/>
+ <prov:role>loggedInUser</prov:role>
+ </prov:wasAssociatedWith>
+
+ <prov:wasAssociatedWith>
+ <prov:activity prov:ref="a"/>
+ <prov:agent prov:ref="ag2"/>
+ </prov:wasAssociatedWithv
+
+ <prov:wasAssociatedWith>
+ <prov:activity prov:ref="a"/>
+ <prov:agent prov:ref="ag3"/>
+ </prov:wasAssociatedWith>
+
+ <b><prov:actedOnBehalfOf>
+ <prov:delegate prov:ref="ag1"/>
+ <prov:responsible prov:ref="ag2"/>
+ <prov:activity prov:ref="a"/>
+ <prov:type>line-management</prov:type>
+ </prov:actedOnBehalfOf></b>
+
+ <b><prov:actedOnBehalfOf>
+ <prov:delegate prov:ref="ag2"/>
+ <prov:responsible prov:ref="ag3"/>
+ <prov:activity prov:ref="a"/>
+ <prov:type>contract</prov:type>
+ </prov:actedOnBehalfOf></b>
+
+</prov:document>
+</pre>
+</section> <!-- end term-Delegation -->
+
+<section id="term-Influence">
+<h4>Influence</h4>
+<div class="glossary-ref" data-ref="glossary-influence"></div>
+<pre class="schema-type">
+<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Influence">
+ <xs:sequence>
+ <xs:element name="influencee" type="prov:AnyRef"/>
+ <xs:element name="influencer" type="prov:AnyRef"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+</xs:complexType>
+</pre>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="wasInfluencedBy" type="prov:Influence"/>
+</pre>
+<pre class="example" id="example_38">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:tr="http://example.com/ns/tr#"
+ xmlns:w3="http://w3.org/">
+
+ <prov:entity prov:id="tr:WD-prov-dm-20111215"/>
+
+ <prov:agent prov:id="w3:Consortium"/>
+
+ <b><prov:wasInfluencedBy>
+ <prov:influencee prov:ref="tr:WD-prov-dm-20111215"/>
+ <prov:influencer prov:ref="w3:Consortium"/>
+ </prov:wasInfluencedBy></b>
+
+</prov:document>
+</pre>
+</section> <!-- end term-influence -->
+
+</section> <!-- end component3 -->
+
+<section id="component4">
+</section> <!-- end component4 -->
<section id="component5">
-<h3>Component 5: Collections</h3>
-
-<p>The fifth component of PROV-DM is concerned with the notion of collections.
-A collection is an entity that has some members. The members are themselves entities, and therefore their provenance can be expressed. In many applications, it is also of interest to be able to express the provenance of the collection itself: e.g. who maintains the collection, which member it contains at which point in time, and how it was assembled. The purpose of Component 5 is to define the types and relations that are useful to express the provenance of collections. </p>
-
-<div class="note">
-XML Schema not defined for collections yet.
-</div>
-
-
-<section id="term-collection">
-<h3>Collection</h3>
-
-<span class="glossary-ref" data-ref="glossary-collection"></span>
-
-
-
-</section> <!-- end of collection-types -->
-
-
-<section id="term-collection-insertion">
-<h3>Insertion</h3>
+<h3>Component 5: Alternate Entities</h3>
+<p>The fifth component of PROV-DM is concerned with
+relations SpecializationOf (<a>specialization</a>), AlternateOf (<a>alternate</a>), and MentionOf (<a>mention</a>) between entities.</p>
-<span class="glossary-ref" data-ref="glossary-insertion"></span>
-
-</section> <!-- insertion -->
-
-
-<section id="term-collection-removal">
-<h3>Removal</h3>
-
-<span class="glossary-ref" data-ref="glossary-removal"></span>
-
+<section id="term-Specialization">
+<h4>Specialization</h4>
+<div class="glossary-ref" data-ref="glossary-specialization"></div>
+<pre class="schema-type">
+<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Specialization">
+ <xs:sequence>
+ <xs:element name="specificEntity" type="prov:EntityRef"/>
+ <xs:element name="generalEntity" type="prov:EntityRef"/>
+ </xs:sequence>
+</xs:complexType>
+</pre>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="specializationOf" type="prov:Specialization"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#"
+ xmlns:bbc="http://www.bbc.co.uk/">
-</section> <!-- removal -->
-
-
-<section id="term-collection-membership">
-<h3>Membership</h3>
-
+ <prov:entity prov:id="ex:bbcNews2012-03-23"/>
-<span class="glossary-ref" data-ref="glossary-membership"></span>
-
+ <prov:entity prov:id="bbc:news"/>
-</section> <!-- Membership -->
+ <b><prov:specializationOf>
+ <prov:specificEntity prov:ref="ex:bbcNews2012-03-23"/>
+ <prov:generalEntity prov:ref="bbc:news"/>
+ </prov:specializationOf></b>
+</prov:document>
+</pre>
+</section> <!-- end term-Specialization -->
-</section> <!-- end collections-->
+<section id="term-Alternate">
+<h4>Alternate</h4>
+<div class="glossary-ref" data-ref="glossary-alternate"></div>
+<pre class="schema-type">
+<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Alternate">
+ <xs:sequence>
+ <xs:element name="alternate1" type="prov:EntityRef"/>
+ <xs:element name="alternate2" type="prov:EntityRef"/>
+ </xs:sequence>
+</xs:complexType>
+</pre>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="alternateOf" type="prov:Alternate"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:bbc="http://www.bbc.co.uk/news"
+ xmlns:bbcmobile="http://www.bbc.co.uk/news/mobile">
+
+ <prov:entity prov:id="bbc:science-environment-17526723">
+ <prov:type>a news item for desktop</prov:type>
+ </prov:entity>
+
+ <prov:entity prov:id="bbcmobile:science-environment-17526723">
+ <prov:type>a news item for mobile devices</prov:type>
+ </prov:entity>
+
+ <b><prov:alternateOf>
+ <prov:alternate1 prov:ref="bbcmobile:science-environment-17526723"/>
+ <prov:alternate2 prov:ref="bbc:science-environment-17526723"/>
+ </prov:alternateOf></b>
+
+</prov:document>
+</pre>
+</section> <!-- end term-Alternate -->
+
+<section id="term-Mention">
+<h4>Mention</h4>
+<div class="glossary-ref" data-ref="glossary-mention"></div>
+<pre class="schema-type">
+<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Mention">
+ <xs:sequence>
+ <xs:element name="specificEntity" type="prov:EntityRef"/>
+ <xs:element name="generalEntity" type="prov:EntityRef"/>
+ <xs:element name="bundle" type="prov:EntityRef"/>
+ </xs:sequence>
+</xs:complexType>
+</pre>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="mentionOf" type="prov:Mention"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#"
+ xmlns:perf="http://example.com/ns/perf#"
+ xmlns:tool="http://example.com/ns/tool#">
+
+ <prov:bundle prov:id="ex:run1">
+ <prov:activity prov:id="ex:a1">
+ <prov:startTime>2011-11-16T16:00:00</prov:startTime>
+ <prov:endTime>2011-11-16T17:00:00</prov:endTime>
+ </prov:activity>
+
+ <prov:wasAssociatedWith>
+ <prov:activity prov:ref="ex:a1" />
+ <prov:agent prov:ref="ex:Bob" />
+ <prov:role>controller</prov:role>
+ </prov:wasAssociatedWith>
+ </prov:bundle>
+
+ <prov:bundle prov:id="ex:run2">
+ <prov:activity prov:id="ex:a2">
+ <prov:startTime>2011-11-17T10:00:00</prov:startTime>
+ <prov:endTime>2011-11-17T17:00:00</prov:endTime>
+ </prov:activity>
+
+ <prov:wasAssociatedWith>
+ <prov:activity prov:ref="ex:a2" />
+ <prov:agent prov:ref="ex:Bob" />
+ <prov:role>controller</prov:role>
+ </prov:wasAssociatedWith>
+ </prov:bundle>
+
+ <prov:bundle prov:id="tool:analysis01">
+ <prov:agent prov:id="tool:Bob-2011-11-16">
+ <ex:perfrating>good</ex:perfrating>
+ </prov:agent>
+
+ <b><prov:mentionOf>
+ <prov:specificEntity prov:ref="tool:Bob-2011-11-16" />
+ <prov:generalEntity prov:ref="ex:Bob" />
+ <prov:bundle prov:ref="ex:run1" />
+ </prov:mentionOf></b>
+
+ <prov:agent prov:id="tool:Bob-2011-11-17">
+ <ex:perfrating>bad</ex:perfrating>
+ </prov:agent>
+
+ <b><prov:mentionOf>
+ <prov:specificEntity prov:ref="tool:Bob-2011-11-17" />
+ <prov:generalEntity prov:ref="ex:Bob" />
+ <prov:bundle prov:ref="ex:run2" />
+ </prov:mentionOf></b>
+ </prov:bundle>
+
+</prov:document>
+</pre>
+</section> <!-- end term-Mention -->
+
+</section> <!-- end component5 -->
<section id="component6">
-<h3>Component 6: Annotations</h3>
-
-<p>The sixth component of PROV-DM is concerned with <a title="note">notes</a> and <a title="annotation">annotations</a>.
-</p>
-
- <section id="term-note">
-
-<h4>Note</h4>
-
-<span class="glossary-ref" data-ref="glossary-note"></span>
-
-<pre class='schema' data-name='note' data-include='schema/prov.xsd' data-oninclude='insertSchemaNote' ></pre>
-
- </section>
+<h3>Component 6: Collections</h3>
+<p>The sixth component of PROV-DM is concerned with the notion of collections.
+A collection is an entity that has some members. The members are themselves entities, and therefore their provenance can be expressed. Some applications need to be able to express the provenance of the collection itself: e.g. who maintains the collection (attribution), which members it contains as it evolves, and how it was assembled. The purpose of Component 6 is to define the types and relations that are useful to express the provenance of collections. </p>
-<section id="term-annotation">
-<h4>Annotation</h4>
-
-<span class="glossary-ref" data-ref="glossary-annotation"></span>
-
-<pre class='schema' data-name='hasAnnotation' data-include='schema/prov.xsd' data-oninclude='insertSchemaHasAnnotation' ></pre>
-
+<section id="term-Collection">
+<h3>Collection</h3>
+<div class="glossary-ref" data-ref="glossary-collection"></div>
+<p>To specialize an Entity as a Collection, include a <code>prov:type</code> with the value "prov:Collection".</p>
+<p>An EmptyCollection is asserted with the <code>prov:type</code> "prov:EmptyCollection" and denotes a Collection with no members.</p>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#">
-
-
-</section>
+ <!-- c0 is an empty collection -->
+ <b><prov:entity prov:id="c0">
+ <prov:type>prov:EmptyCollection</prov:type>
+ </prov:entity></b>
+ <!-- c1 is a collection, with unknown content -->
+ <b><prov:entity prov:id="c1">
+ <prov:type>prov:Collection</prov:type>
+ </prov:entity></b>
-</section>
+</prov:document>
+</pre>
+</section> <!-- end term-Collection -->
-</section>
+<section id="term-Membership">
+<h3>Membership</h3>
+<div class="glossary-ref" data-ref="glossary-membership"></div>
+<pre class="schema-type">
+<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="Membership">
+ <xs:sequence>
+ <xs:element name="collection" type="prov:EntityRef"/>
+ <xs:element name="entity" type="prov:EntityRef" maxOccurs="unbounded"/>
+ </xs:sequence>
+</xs:complexType>
+</pre>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="hadMember" type="prov:Membership"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#">
+
+ <prov:entity prov:id="e0"/>
+ <prov:entity prov:id="e1"/>
+ <prov:entity prov:id="e2"/>
+
+ <prov:entity prov:id="c">
+ <prov:type>prov:Collection</prov:type>
+ </prov:entity>
+
+ <b><prov:hadMember>
+ <prov:collection prov:ref="c"/>
+ <prov:entity prov:ref="e0"/>
+ <prov:entity prov:ref="e1"/>
+ <prov:entity prov:ref="e2"/>
+ </prov:hadMember></b>
+
+</prov:document>
+</pre>
+</section> <!-- end term-Membership -->
+
+</section> <!-- end component6 -->
+
+<section id="further-elements">
+<h3>Further Elements of PROV</h3>
+
+<p>This section introduces further elements of PROV.</p>
+
+<section id="attribute-Identifier">
+<h4>Identifier</h4>
+<div class="glossary-ref" data-ref="glossary-identifier"></div>
+<p>The identifier attribute is used to identify instances of PROV types or relations.</p>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#">
+
+ <prov:entity <b>prov:id="tr:WD-prov-dm-20111215"</b>>
+ <prov:type>document</prov:type>
+ <ex:version>2</ex:version>
+ </prov:entity>
+
+</prov:document>
+</pre>
+</section> <!-- end attribute-Identifier -->
+
+<section id="element-Label">
+<h4>Label</h4>
+<div class="glossary-ref" data-ref="glossary-label"></div>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="label" type="prov:InternationalizedString"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#">
+
+ <prov:entity prov:id="ex:e1">
+ <b><prov:label>This is a human-readable label</prov:label></b>
+ </prov:entity>
+
+ <prov:entity prov:id="ex:car01">
+ <b><prov:label xml:lang="fr">Voiture 01</prov:label>
+ <prov:label xml:lang="en">Car 01</prov:label></b>
+ </prov:entity>
+
+</prov:document>
+</pre>
+</section> <!-- end element-Label -->
+
+<section id="element-Location">
+<h4>Location</h4>
+<div class="glossary-ref" data-ref="glossary-location"></div>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="location" type="xs:anySimpleType"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#">
+
+ <prov:entity prov:id="ex:MonaLisa">
+ <prov:type>StillImage</prov:type>
+ <b><prov:location>Le Louvre, Paris</prov:location></b>
+ </prov:entity>
+
+ <prov:entity prov:id="ex:cell">
+ <b><prov:location>(5,5)</prov:location></b>
+ <prov:value>10</prov:value>
+ </prov:entity>
+
+</prov:document>
+</pre>
+</section> <!-- end element-Location -->
+
+<section id="element-Role">
+<h4>Role</h4>
+<div class="glossary-ref" data-ref="glossary-role"></div>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="role" type="xs:anySimpleType"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xmlns:ex="http://example.com/ns/ex#">
+
+ <prov:wasAssociatedWith>
+ <prov:activity prov:ref="a"/>
+ <prov:agent prov:ref="ag1"/>
+ <b><prov:role>loggedInUser</prov:role></b>
+ <ex:how>webapp</ex:how>
+ </prov:wasAssociatedWith>
+
+ <prov:wasAssociatedWith>
+ <prov:activity prov:ref="a"/>
+ <prov:agent prov:ref="ag2"/>
+ <prov:plan prov:ref="ex:wf"/>
+ <b><prov:role>designer</prov:role></b>
+ <ex:content>project1</ex:content>
+ </prov:wasAssociatedWith>
+
+</prov:document>
+</pre>
+</section> <!-- end element-Role -->
+
+<section id="element-Type">
+<h4>Type</h4>
+<div class="glossary-ref" data-ref="glossary-type"></div>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="type" type="xs:anySimpleType"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#"
+ xmlns:tr="http://example.com/ns/tr#">
+
+ <prov:entity prov:id="tr:WD-prov-dm-20111215">
+ <b><prov:type>document</prov:type></b>
+ <ex:version>2</ex:version>
+ </prov:entity>
+
+ <prov:agent prov:id="e1">
+ <b><prov:type>prov:Person</prov:type></b>
+ <ex:name>Alice</ex:name>
+ <ex:employee>1234</ex:employee>
+ </prov:agent>
+
+ <prov:activity prov:id="a1">
+ <prov:startTime>2011-11-16T16:05:00</prov:startTime>
+ <prov:endTime>2011-11-16T16:06:00</prov:endTime>
+ <b><prov:type>ex:edit</prov:type></b>
+ <ex:host>server.example.org</ex:host>
+ </prov:activity>
+
+</prov:document>
+</pre>
+</section> <!-- end element-Type -->
+
+<section id="element-Value">
+<h4>Value</h4>
+<div class="glossary-ref" data-ref="glossary-value-attribute"></div>
+<pre class="schema-usage">
+<xs:element xmlns:xs="http://www.w3.org/2001/XMLSchema" name="value" type="xs:anySimpleType"/>
+</pre>
+<pre class="example">
+<prov:document
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:ex="http://example.com/ns/ex#">
+
+ <prov:entity prov:id="ex:in">
+ <b><prov:value>abcd</prov:value></b>
+ </prov:entity>
+
+ <prov:entity prov:id="ex:out">
+ <b><prov:value>4</prov:value></b>
+ </prov:entity>
+
+</prov:document>
+</pre>
+</section> <!-- end element-Value -->
+
+</section> <!-- end further-elements -->
+
+</section> <!-- end -->
@@ -774,13 +1925,403 @@
+<!-- Should this be folded or hid in some way until the user asks to see it? -->
<section class="appendix">
<h2>Full XML Schema</h2>
- <p>
+ <pre class="full-schema">
+<?xml version="1.0" encoding="utf-8"?>
-<pre class='schema' data-include='schema/prov.xsd' data-oninclude='insertSchema'></pre>
+<xs:schema targetNamespace="http://www.w3.org/ns/prov#"
+ xmlns:xs="http://www.w3.org/2001/XMLSchema"
+ xmlns:prov="http://www.w3.org/ns/prov#"
+ xmlns:cu="http://www.w3.org/1999/xhtml/datatypes/"
+ xmlns:xml="http://www.w3.org/XML/1998/namespace"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified">
- </p>
+
+
+ <xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/" />
+ <xs:import namespace="http://www.w3.org/XML/1998/namespace"
+ schemaLocation="http://www.w3.org/2001/xml.xsd"/>
+
+ <!-- Component 1 -->
+
+ <xs:complexType name="Entity">
+ <xs:sequence>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:location"/>
+ <xs:element ref="prov:value"/>
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Activity">
+ <xs:sequence>
+ <xs:element name="startTime" type="xs:dateTime" minOccurs="0"/>
+ <xs:element name="endTime" type="xs:dateTime" minOccurs="0"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:location"/>
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Generation">
+ <xs:sequence>
+ <xs:element name="entity" type="prov:EntityRef"/>
+ <xs:element name="activity" type="prov:ActivityRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:location"/>
+ <xs:element ref="prov:role"/>
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Usage">
+ <xs:sequence>
+ <xs:element name="activity" type="prov:ActivityRef"/>
+ <xs:element name="entity" type="prov:EntityRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:location"/>
+ <xs:element ref="prov:role"/>
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Communication">
+ <xs:sequence>
+ <xs:element name="informed" type="prov:ActivityRef"/>
+ <xs:element name="informant" type="prov:ActivityRef"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Start">
+ <xs:sequence>
+ <xs:element name="activity" type="prov:ActivityRef"/>
+ <xs:element name="trigger" type="prov:EntityRef" minOccurs="0"/>
+ <xs:element name="starter" type="prov:ActivityRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:location"/>
+ <xs:element ref="prov:role"/>
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="End">
+ <xs:sequence>
+ <xs:element name="activity" type="prov:ActivityRef"/>
+ <xs:element name="trigger" type="prov:EntityRef" minOccurs="0"/>
+ <xs:element name="ender" type="prov:ActivityRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:location"/>
+ <xs:element ref="prov:role"/>
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Invalidation">
+ <xs:sequence>
+ <xs:element name="entity" type="prov:EntityRef"/>
+ <xs:element name="activity" type="prov:ActivityRef" minOccurs="0"/>
+ <xs:element name="time" type="xs:dateTime" minOccurs="0"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:location"/>
+ <xs:element ref="prov:role"/>
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <!-- Component 2 -->
+
+ <xs:complexType name="Derivation">
+ <xs:sequence>
+ <xs:element name="generatedEntity" type="prov:EntityRef"/>
+ <xs:element name="usedEntity" type="prov:EntityRef"/>
+ <xs:element name="activity" type="prov:ActivityRef" minOccurs="0"/>
+ <xs:element name="generation" type="prov:GenerationRef" minOccurs="0"/>
+ <xs:element name="usage" type="prov:UsageRef" minOccurs="0"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <!-- Component 3 -->
+
+ <xs:complexType name="Agent">
+ <xs:sequence>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:location"/>
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Attribution">
+ <xs:sequence>
+ <xs:element name="entity" type="prov:EntityRef"/>
+ <xs:element name="agent" type="prov:AgentRef"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Association">
+ <xs:sequence>
+ <xs:element name="activity" type="prov:ActivityRef"/>
+ <xs:element name="agent" type="prov:AgentRef" minOccurs="0"/>
+ <xs:element name="plan" type="prov:EntityRef" minOccurs="0"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:role"/>
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Delegation">
+ <xs:sequence>
+ <xs:element name="delegate" type="prov:AgentRef"/>
+ <xs:element name="responsible" type="prov:AgentRef"/>
+ <xs:element name="activity" type="prov:ActivityRef" minOccurs="0"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <xs:complexType name="Influence">
+ <xs:sequence>
+ <xs:element name="influencee" type="prov:AnyRef"/>
+ <xs:element name="influencer" type="prov:AnyRef"/>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:label"/>
+ <xs:element ref="prov:type"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+ <!-- Component 4 -->
+
+ <!-- Component 5 -->
+
+ <xs:complexType name="Specialization">
+ <xs:sequence>
+ <xs:element name="specificEntity" type="prov:EntityRef"/>
+ <xs:element name="generalEntity" type="prov:EntityRef"/>
+ </xs:sequence>
+ </xs:complexType>
+
+ <xs:complexType name="Alternate">
+ <xs:sequence>
+ <xs:element name="alternate1" type="prov:EntityRef"/>
+ <xs:element name="alternate2" type="prov:EntityRef"/>
+ </xs:sequence>
+ </xs:complexType>
+
+ <xs:complexType name="Mention">
+ <xs:sequence>
+ <xs:element name="specificEntity" type="prov:EntityRef"/>
+ <xs:element name="generalEntity" type="prov:EntityRef"/>
+ <xs:element name="bundle" type="prov:EntityRef"/>
+ </xs:sequence>
+ </xs:complexType>
+
+
+ <!-- Component 6 -->
+
+ <xs:complexType name="Membership">
+ <xs:sequence>
+ <xs:element name="collection" type="prov:EntityRef"/>
+ <xs:element name="entity" type="prov:EntityRef" maxOccurs="unbounded"/>
+ </xs:sequence>
+ </xs:complexType>
+
+ <xs:complexType name="InternationalizedString">
+ <xs:simpleContent>
+ <xs:extension base="xs:string">
+ <xs:attribute ref="xml:lang" use="optional"/>
+ </xs:extension>
+ </xs:simpleContent>
+ </xs:complexType>
+
+
+ <!--
+ Typed literals are encoded by means
+ of xsi:type that represent the prov:datatype.
+
+ -->
+
+ <xs:element name="label" type="prov:InternationalizedString"/>
+ <xs:element name="role" type="xs:anySimpleType"/>
+ <xs:element name="type" type="xs:anySimpleType"/>
+ <xs:element name="location" type="xs:anySimpleType"/>
+ <xs:element name="value" type="xs:anySimpleType"/>
+
+ <!-- See comment in preamble.
+ These should be prov:QualifiedName
+ but instead are xsd:QName for tools to process them -->
+
+ <xs:attribute name="id" type="xs:QName"/>
+ <xs:attribute name="ref" type="xs:QName"/>
+
+ <xs:complexType name="ActivityRef">
+ <xs:attribute ref="prov:ref" use="required" />
+ </xs:complexType>
+ <xs:complexType name="EntityRef">
+ <xs:attribute ref="prov:ref" use="required"/>
+ </xs:complexType>
+ <xs:complexType name="AgentRef">
+ <xs:attribute ref="prov:ref" use="required"/>
+ </xs:complexType>
+ <xs:complexType name="UsageRef">
+ <xs:attribute ref="prov:ref" use="required"/>
+ </xs:complexType>
+ <xs:complexType name="GenerationRef">
+ <xs:attribute ref="prov:ref" use="required"/>
+ </xs:complexType>
+ <xs:complexType name="AnyRef">
+ <xs:attribute ref="prov:ref" use="required"/>
+ </xs:complexType>
+
+ <!--
+ top-level definition of elements following the salami slice XSD design pattern
+ to encourage integration within existing non-prov XML documents.
+ -->
+
+ <!-- Component 1 elements -->
+
+ <xs:element name="entity" type="prov:Entity"/>
+ <xs:element name="activity" type="prov:Activity"/>
+ <xs:element name="wasGeneratedBy" type="prov:Generation"/>
+ <xs:element name="used" type="prov:Usage"/>
+ <xs:element name="wasInformedBy" type="prov:Communication"/>
+ <xs:element name="wasStartedBy" type="prov:Start"/>
+ <xs:element name="wasEndedBy" type="prov:End"/>
+ <xs:element name="wasInvalidatedBy" type="prov:Invalidation"/>
+
+ <!-- Component 2 elements -->
+
+ <xs:element name="wasDerivedFrom" type="prov:Derivation"/>
+
+ <!-- Component 3 elements -->
+
+ <xs:element name="agent" type="prov:Agent"/>
+ <xs:element name="wasAttributedTo" type="prov:Attribution"/>
+ <xs:element name="wasAssociatedWith" type="prov:Association"/>
+ <xs:element name="actedOnBehalfOf" type="prov:Delegation"/>
+ <xs:element name="wasInfluencedBy" type="prov:Influence"/>
+
+ <!-- Component 5 elements -->
+
+ <xs:element name="specializationOf" type="prov:Specialization"/>
+ <xs:element name="alternateOf" type="prov:Alternate"/>
+ <xs:element name="mentionOf" type="prov:Mention"/>
+
+ <!-- Component 6 elements -->
+
+ <xs:element name="hadMember" type="prov:Membership"/>
+
+ <xs:group name="documentElements">
+ <xs:sequence>
+ <xs:choice minOccurs="0" maxOccurs="unbounded">
+ <xs:element ref="prov:entity"/>
+ <xs:element ref="prov:activity"/>
+ <xs:element ref="prov:wasGeneratedBy"/>
+ <xs:element ref="prov:used"/>
+ <xs:element ref="prov:wasInformedBy"/>
+ <xs:element ref="prov:wasStartedBy"/>
+ <xs:element ref="prov:wasEndedBy"/>
+ <xs:element ref="prov:wasInvalidatedBy"/>
+ <xs:element ref="prov:wasDerivedFrom"/>
+ <xs:element ref="prov:agent"/>
+ <xs:element ref="prov:wasAttributedTo"/>
+ <xs:element ref="prov:wasAssociatedWith"/>
+ <xs:element ref="prov:actedOnBehalfOf"/>
+ <xs:element ref="prov:wasInfluencedBy"/>
+ <xs:element ref="prov:specializationOf"/>
+ <xs:element ref="prov:alternateOf"/>
+ <xs:element ref="prov:mentionOf"/>
+ <xs:element ref="prov:hadMember"/>
+ <xs:any namespace="##other"/>
+ </xs:choice>
+ </xs:sequence>
+ </xs:group>
+
+ <xs:element name="document" type="prov:Document" />
+ <xs:complexType name="Document">
+ <xs:sequence>
+ <xs:choice maxOccurs="unbounded">
+ <xs:group ref="prov:documentElements"/>
+ <xs:element name="bundle" type="prov:Bundle"/>
+ </xs:choice>
+ </xs:sequence>
+ </xs:complexType>
+
+ <xs:complexType name="Bundle">
+ <xs:sequence>
+ <xs:group ref="prov:documentElements"/>
+ </xs:sequence>
+ <xs:attribute ref="prov:id"/>
+ </xs:complexType>
+
+</xs:schema>
+ </pre>
</section>
<section class="appendix"> 
