--- a/model/ProvenanceModel.html Mon Oct 10 12:23:09 2011 +0100
+++ b/model/ProvenanceModel.html Mon Oct 10 12:23:53 2011 +0100
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<html><head>
- <title>The PROV data model and abstract syntax notation</title>
+ <title>The PROV Data Model and Abstract Syntax Notation</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<!--
=== NOTA BENE ===
@@ -54,7 +54,7 @@
// if your specification has a subtitle that goes below the main
// formal title, define it here
- subtitle : "Initial draft for internal discussion",
+ // subtitle : "Initial draft for internal discussion",
// if you wish the publication date to be other than today, set this
// publishDate: "2009-08-06",
@@ -82,9 +82,9 @@
// only "name" is required
editors: [
{ name: "Luc Moreau", url: "http://www.ecs.soton.ac.uk/~lavm",
- company: "University of Southampton, UK" },
+ company: "University of Southampton" },
{ name: "Paolo Missier", url: "http://www.cs.ncl.ac.uk/people/Paolo.Missier",
- company: "Newcastle University, UK" },
+ company: "Newcastle University" },
],
// authors, add as many as you like.
@@ -92,7 +92,24 @@
// only "name" is required. Same format as editors.
authors: [
- { name: "TBD"},
+ { name: "Khalid Belhajjame", url: "http://semanticweb.org/wiki/Khalid_Belhajjame",
+ company: "University of Manchester" },
+ { name: "Stephen Cresswell",
+ company: "The National Archives"},
+ { name: "Ryan Golden",
+ company: "Oracle Corporation" },
+ { name: "Paul Groth", url: "http://www.few.vu.nl/~pgroth/",
+ company: "VU University of Amsterdam" },
+ { name: "Graham Klyne",
+ company: "University of Oxford" },
+ { name: "Jim McCusker", url: "http://tw.rpi.edu/web/person/JamesMcCusker",
+ company: "Rensselaer Polytechnic Institute" },
+ { name: "Simon Miles",
+ company: "Invited Expert", url:"http://www.inf.kcl.ac.uk/staff/simonm/" },
+ { name: "James Myers", url:"http://www.rpi.edu/research/ccni/",
+ company: "Rensselaer Polytechnic Institute"},
+ { name: "Satya Sahoo", url:"http://cci.case.edu/cci/index.php/Satya_Sahoo",
+ company: "Case Western Reserve University" },
],
// name of the WG
@@ -119,63 +136,146 @@
<body>
<section id="abstract">
<p>
-This document defines PROV-DM, a data model for provenance, and
-PROV-ASN, an abstract syntax, which allows
-serializations of PROV-DM instances to be created in a technology independent manner,
-which facilitates its mapping to concrete syntax, and which is used as the basis for a
+PROV-DM is a core data model for provenance for building
+representations of the entities, people and processes involved in
+producing a piece of data or thing in the world. PROV-DM is
+domain-agnotisc, but with well-defined extensibility points allowing
+further domain-specific and application-specific extensions to be
+defined. It is accompanied by PROV-ASN, a technology-independent
+abstract syntax notation, which allows serializations of PROV-DM
+instances to be created for human consumption, which facilitates its
+mapping to concrete syntax, and which is used as the basis for a
formal semantics.
</p>
-
</section>
+
+<section id="sotd">
+This document is part of a set of specifications aiming to define the various aspects that are necessary to achieve the visition on inter-operable interchange of provenance information in heterogeneous environments such as the Web. This document defines the PROV-DM data model for provenance, accompanied with a notation to express instances of that data model for human consumption. Two other documents, to be released shortly, are: 1) a normative serialization of PROV-DM in RDF, specified by means of a mapping to the OWL2 Web Ontology Language; 2)
+the mechanisms for accessing and querying provenance.
+</section>
<section>
<h2>Introduction<br>
</h2>
-<div class='note'>Introduction needs to be written. It should indicate the aims and scope of this document, and position this document in the family of documents produced by the PROV WG.
-</div>
+<p>
+The term 'provenance' refers to the sources of information, such
+as people, entities, and processes, involved in producing,
+influencing, or delivering a piece of data or a thing in the world.
+In particular, the provenance of information is crucial in deciding
+whether information is to be trusted, how it should be integrated with
+other diverse information sources, and how to give credit to its
+originators when reusing it. In an open and inclusive environment
+such as the Web, users find information that is often contradictory or
+questionable: provenance can help those users to make trust judgments.
+</p>
+
+
+<p>
+The idea that a single way of representing and collecting provenance could be adopted internally by all systems does not seem to be realistic today. Instead, a pragmatic approach is to consider a core data model for provenance that allows domain and application specific representations of provenance to be translated into such a data model and exchanged between systems.
+Heterogeneous systems can then export their provenance into such a core data model, and applications that need to make sense of provenance in heterogeneous systems can then import it, process it, and reason over it.</p>
+
+<p>Thus, the vision is that different provenance-aware systems natively adopt their own model for representing their provenance, but a core provenance data model can be readily adopted as a provenance <em>interchange</em> model across such systems.</p>
+
+<p>A set of specifications define the various aspects
+that are necessary to achieve this vision in an inter-operable
+way:</p>
+<ul>
+<li> This document defines the PROV-DM data model for provenance, accompanied with a notation to express instances of that data model for human consumption; </li>
+<li> A normative serialization of PROV-DM in RDF [[PROV-OWL2]], specified by means of a mapping to the OWL2 Web Ontology Language [[!OWL2-SYNTAX]];</li>
+<li> The mechanisms for accessing and querying provenance [[PROV-PAQ]].</li>
+</ul>
+
+
+<p>
+The PROV-DM data model for provenance consists of a set of core
+concepts, and a few common extensions, based on these core concepts. PROV-DM is a core model, domain-agnotisc, but with well-defined extensibility points allowing further domain-specific and application-specific extensions to be defined.</p>
+
+<p>This specification also introduces
+PROV-ASN, an abstract syntax that is primarily aimed at human consumption. PROV-ASN allows
+serializations of PROV-DM instances to be created in a technology independent manner,
+it facilitates its mapping to concrete syntax, and it is used as the basis for a
+formal semantics.
+</p>
+
+ <section>
+<h3>Structure of this Document</h3>
+
+<p>In <a href="#preliminaries">section 2</a>, a set of preliminaries are introduced, including concepts that underpin PROV-DM and motivations for the PROV-ASN notation.</p>
+
+<p><a href="#prov-dm-overview">Section 3</a> provides an overview of PROV-DM listing its core types and their relations.</p>
+
+<p>In <a href="#prov-dm-example">section 4</a>, the PROV-DM is
+applied to a short scenario, encoded in PROV-ASM, and illustrated
+graphically.</p>
+
+<p><a href="#data-model-concepts">Section 5</a> provides the normative definition of PROV-DM and the notation PROV-ASN.</p>
+
+<p><a href="#extensibility-section">Section 6</a> summarizes PROV-DM extensibility points.</p>
+
+<p><a href="#prov-dm-extensions">Section 7</a> consists of common domain-independent extensions such as collection-related concepts and common relations.</p>
+
+
+ </section>
+
+<section id="prov-dm-namespace">
+ <h3>PROV-DM Namespace</h3>
+
+
+<p>The PROV-DM namespace is <span class="name">http://www.w3.org/2011/prov/</span> (TBD).</p>
+
+<p> All the elements, relations, reserved names and attributes introduced in this specification belong to the PROV-DM namespace.
+</p>
+
+</section>
+
+
+ <section>
+<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>
+
+
+<section id='preliminaries'>
<h2>Preliminaries</h2>
- <section>
+ <section id='conceptualization'>
<h3>A Conceptualization of the World</h3>
<p>This specification is based on a conceptualization of the world
that is described in this section. In the world (whether real or not),
there are things, which can be physical, digital, conceptual, or
-otherwise, and activities involving things. Words such thing or
-activity should be understood with their informal meaning.</p>
+otherwise, and activities involving things. Words such 'thing' or
+'activity' should be understood with their informal meaning.</p>
<p>When we talk about things in the world in natural language and even when we assign identifiers, we are often imprecise in ways that make it difficult to clearly and unambiguously report provenance: a resource with a URL may be understood as referring to a report available at that URL, the version of the report available there today, the report independent of where it is hosted over time, etc.</p>
<!--
-<div class='paolo'>This is the single most important issue IMO: we hit readers with this "characterised thing" which is unexpected. We need to be absolutely clear about it...
+<div class='paolo'>This is the single most important issue IMO: we hit readers with this "characterized thing" which is unexpected. We need to be absolutely clear about it...
<br/>ok, so it seems that characterized thing is introduced to deal with (1) imprecision, (2) disagreement amongst different "observers" of the same data-related events. I don't think this is about "disambiguation". It's about accommmodating different perspectives on the what is the same abstract "thing". This interpretation fits with the example: "different users may take different perspective..."</div>
-->
-<p>Hence, to accommodate different perspectives on things and their situation in the world as perceived by us, we introduce the concept of <dfn id="concept-characterized-thing">characterized thing</dfn>, which refers to a thing and its situation in the world, as characterized by someone. A characterized thing <em>fixes some aspects</em> of a thing and its situation in the world, so that it becomes possible to express its provenance, and what causes these specific aspects to be as such. An alternative characterized thing may fix other aspects, and its provenance may be entirely different.</p>
+<p>Hence, to accommodate different perspectives on things and their situation in the world as perceived by us, we introduce the concept of <dfn id="concept-characterized-thing">characterized thing</dfn>, which refers to a thing and its situation in the world, as characterized by someone. A characterized thing <em>fixes some aspects</em> of a thing and its situation in the world, so that it becomes possible to express its provenance, and what causes these specific aspects to be as such. An alternative characterized thing may fix other aspects, and its provenance may be different.</p>
<div class="xmpl">
-Different users may take different perspectives about a resource with
+Different users may take different perspectives on a resource with
a URL. These perspectives in this conceptualization of the world are
referred to as characterized things. Three such characterized things may be
expressed:
<ul>
<li>a report available at URL: fixes the nature of the thing, i.e. a document, and its location; </li>
<li>the version of the report available there today: fixes its version number, contents, and its date;</li>
-<li>the report independent of where it is hosted over time: fixes the nature of the thing as a concepual artifact.</li></ul>
+<li>the report independent of where it is hosted and of its content over time: fixes the nature of the thing as a conceptual artifact.</li></ul>
The provenance of these three characterized things will differ, and may be along the follow lines:
<ul>
<li>the provenance of a report available at URL may include: the act of publishing it and making it available at a given location, possibly under some license and access control;</li>
@@ -197,9 +297,17 @@
etc.</p>
-<p>In our conceptualization of the world, punctual events, or <dfn id="concept-event">events</dfn> for short, happen in the world, which mark changes in the world, in its activities, and in its things. This specification assumes that a partial order exists between events. How practically such order is realized is beyond the scope of this specification. Possible implementations of that ordering include a single global notion of time and Lamport's style clocks.</p>
+<p>In our conceptualization of the world, instantaneous events, or <dfn id="concept-event">events</dfn> for short, happen in the world, which mark changes in the world, in its activities, and in its things. This specification assumes that a partial order exists between events. How practically such order is realized is beyond the scope of this specification. Possible implementations of that ordering include a single global notion of time and Lamport's style clocks.</p>
<p> In this specification, the qualifier 'identifiable' is implicit whenever a reference is made to an activity or characterized thing.</p>
+
+
+<div class='note'>
+Now that "entity expression" is used to refer to the
+language construct, the term "entity" can unambiguously refer to the thing
+described by that construct; i.e. the characterized thing.
+This is raised in the following <a href="http://lists.w3.org/Archives/Public/public-prov-wg/2011Sep/0315.html">email</a>.</div>
+
</section>
<section>
@@ -230,7 +338,6 @@
-<div class='pending'>Formalism used is not explained, not applied to concepts <a href="http://www.w3.org/2011/prov/track/issues/87">ISSUE-87</a>.</div>
</section>
@@ -248,7 +355,9 @@
<p>
-These representations are relative to an asserter, and in that sense constitute assertions stating properties of the world, as represented by an asserter. Different asserters will normally contribute different representations, and no attempt is made to define a notion of consistency of such different sets of assertions. The data model provides the means to associate attribution to assertions.
+These representations are relative to an asserter, and in that sense constitute assertions stating properties of the world, as represented by an asserter. Different asserters will normally contribute different representations.
+This specification does not define a notion of consistency between different sets of assertions (whether by the same asserter or different asserters).
+The data model provides the means to associate attribution to assertions.
</p>
<div class="note">Suggestion: add "should not attempt to define or ensure the
@@ -284,7 +393,7 @@
</section>
</section>
- <section>
+ <section id="prov-dm-overview">
<h2>PROV-DM Overview </h2>
@@ -308,7 +417,7 @@
<p>The model includes the following fundamental types:</p>
<ul>
<li>An instance of an <strong>Entity</strong> is a representation of a <em>characterized thing</em>, as defined informally above. The specific nature of an entity is specified by means of a set of <strong>characterizing attributes</strong>. The
- <strong>wasComplementOf</strong> relationship is used to denote that two entities <em>complement</em> each other, in the sense that they each represent a partial, but mutually compatible characterization of the same thing.</li>
+ <strong>wasComplementOf</strong> relationship is used to denote that two instances of entities <em>complement</em> each other, in the sense that they each represent a partial, but mutually compatible characterization of the same thing.</li>
<li>An instance of a <strong>Process Execution</strong> represents an activity that has an effect on entities, namely it either <em>generates</em> or <em>uses</em> one or more entities. Use and generation are modelled by means of the <strong>used</strong> and the <strong>wasGeneratedBy</strong> relationships. Additionally, one can use the <strong>hadParticipant</strong> relation to indicate participation of an Entity in a Process Execution. Activities may include not only computations, but also any other type of activity that can be described in terms of their effect on entities.
Note that multiple Process Executions may <em>use</em> the same entity, and each may use multiple entities. Finally, entities can be derived from other entities, and this is specified using the <strong>wasDerivedFrom</strong> relation.</li>
@@ -319,18 +428,21 @@
The model includes two additional types: <strong>qualifiers</strong> and <strong>annotations</strong>. These are both structured as sets of attribute-value pairs.
- <ul><li> Qualifiers can be associated to relations, namely <strong>use</strong> and <strong>wasGeneratedBy</strong>, in order to further characterise their nature. <strong>Role</strong> is a standard qualifier.</li>
+ <ul><li> Qualifiers can be associated to relations, namely <strong>use</strong> and <strong>wasGeneratedBy</strong>, in order to further characterize their nature. <strong>Role</strong> is a pre-defined qualifier.</li>
<li> Annotations are used to provide additional, "free-form" information regarding <strong>any</strong> identifiable construct of the model, with no prescribed meaning. The difference between attributes and annotations is further clarified <a href="#expression-annotation">here</a>. </li>
</ul>
Attributes, qualifiers, and annotation are the main <strong>extensibility points</strong> in the model: individual interest groups are expected to extend PROV-DM by introducing new sets of attributes, qualifiers, and annotations as needed to address applications-specific provenance modelling requirements.
-<div class='pending'>Conceptual model needs a high level overview <a href="http://www.w3.org/2011/prov/track/issues/86">ISSUE-86</a>.</div>
+
+<div class='note'>To simplify the ER diagram in this section, we wrote "Entity" instead of "Entity Expression". This may be confusing. Particularly so, if we define entity as characterized thing.
+</div>
+
</section>
- <section class="informative">
+ <section class="informative" id="prov-dm-example">
<h2>Example</h2>
To illustrate PROV-DM, this section presents an example encoded according to PROV-ASN. For more detailed explanations of how PROV-DM should be used, and for more examples, we refer the reader to the Provenance Primer [[PROV-PRIMER]].
@@ -473,7 +585,7 @@
<p>
-wasComplementOf: (this relation is described in <a href="#expression-complement-of">Section wasComplementOf</a>). The crime statistics file (<span class="name">e0</span>) has various contents over its existence (<span class="name">e1</span>, <span class="name">e2</span>, <span class="name">e3</span>); the entity expressions identified by <span class="name">e1</span>, <span class="name">e2</span>, <span class="name">e3</span> complement <span class="name">e0</span> with an attribute content. Likewise, the one denoted by <span class="name">e6</span> complements the expression denoted by <span class="name">e3</span> with an attribute spellchecked.</p>
+wasComplementOf: (this relation is described in <a href="#expression-complement-of">Section wasComplementOf</a>). The crime statistics file (<span class="name">e0</span>) has various contents over its existence (<span class="name">e1</span>, <span class="name">e2</span>, <span class="name">e3</span>); the entity expressions identified by <span class="name">e1</span>, <span class="name">e2</span>, <span class="name">e3</span> complement <span class="name">e0</span> with an attribute <span class="name">content</span>. Likewise, the one denoted by <span class="name">e6</span> complements the expression denoted by <span class="name">e3</span> with an attribute <span class="name">spellchecked</span>.</p>
<pre>
wasComplementOf(e1,e0)
wasComplementOf(e2,e0)
@@ -505,7 +617,7 @@
<p>
-Control Expressions (described in <a href="#expression-Control">Section Control</a>): the influence of an agent over a process execution is expressed as control, and the nature of this influence is described by qualifier (construct described in <a href="#expression-qualifier">Section Qualifier</a>). Illustrations of such qualifiers include the role of the participating agenr: are creator, author and communicator.</p>
+Control Expressions (described in <a href="#expression-Control">Section Control</a>): the influence of an agent over a process execution is expressed as control, and the nature of this influence is described by qualifier (construct described in <a href="#expression-qualifier">Section Qualifier</a>). Illustrations of such qualifiers include the role of the participating agent, as creator, author and communicator.</p>
<pre>
wasControlledBy(pe0,a1, qualifier(role="creator"))
wasControlledBy(pe1,a2, qualifier(role="author"))
@@ -574,7 +686,8 @@
| <span class="nonterminal">annotationAssociationExpression</span>
</div>
-Furthermore, the PROV data model includes a "house-keeping construct" acting as a wrapper for interchanging PROV-DM expressions, which is compliant with the production <span class="nonterminal">provenanceContainer</span> (see section <a href="#ProvenanceContainer">Provenance Container</a>).
+<p>
+Furthermore, the PROV data model includes a "house-keeping construct", which is compliant with the production <span class="nonterminal">provenanceContainer</span> (see section <a href="#ProvenanceContainer">Provenance Container</a>). This construct is used to wrap PROV-DM expressions and facilitate their interchange.</p>
</section>
@@ -663,11 +776,13 @@
-<div class='pending'>How is domain specific data combined with the provenance model? This is <a href="http://www.w3.org/2011/prov/track/issues/65">ISSUE-65</a>.</div>
-
-
-
-<div class='pending'>Definition of Entity is confusing, maybe over-complex <a href="http://www.w3.org/2011/prov/track/issues/85">ISSUE-85</a>.</div>
+<div class='note'>The group is still discussing the need for characterizing attributes in entity expressions. At heart: when it comes to exchanging provenance information, why do we *need*
+to know exactly what makes one entity a constrained view of another.
+This is raised in the following <a href="http://lists.w3.org/Archives/Public/public-prov-wg/2011Sep/0315.html">email</a>.</div>
+
+<div class='note'>The characterization interval of an entity expression is currently implicit. Making it explicit would allow us to define wasComplementOf more precisely. It would also allow us to address
+<a href="http://www.w3.org/2011/prov/track/issues/108">ISSUE-108</a>.
+Beginning and end of characterization interval could be expressed by attributes (similarly to process executions). </div>
@@ -702,15 +817,15 @@
<p>The activity that a process execution expression is a representation of has a duration, delimited by its start and its end events; hence, it occurs over an interval delimited by two events. However, a process execution expression need not mention time information, nor duration, because they may not be known.</p>
-<p>Such start and end times constitute <em>attributes</em> of an activity, where the meaning of attribute in the context of a process execution expression is similar to the meaning of attribute for entity expression. A process execution expression's attribute remains constant for the duration of the activity it represents. Further characteristics of the activity in the world can be represented by other attribute-value pairs, which MUST also remain unchanged during the activity duration.</p>
-
-<p> An instance of a process execution expression, noted <span class="name">processExecution(id, rl, st, et, [ attr1=val1, ...])</span> in PROV-ASN:</p>
+<p>Such start and end times constitute <em>attributes</em> of an activity, where the interpretation of attribute in the context of a process execution expression is the same as the interpretation of attribute for entity expression: a process execution expression's attribute remains constant for the duration of the activity it represents. Further characteristics of the activity in the world can be represented by other attribute-value pairs, which MUST also remain unchanged during the activity duration.</p>
+
+<p> An instance of a process execution expression, written <span class="name">processExecution(id, rl, st, et, [ attr1=val1, ...])</span> in PROV-ASN:</p>
<ul>
<li> contains an identifier <span class="name">id</span>;</li>
<li> MAY contain a <a href="#expression-RecipeLink">recipe link</a> <span class="name">rl</span>, which consists of a domain specific description of the activity;</li>
<li> MAY contain a start time <span class="name">st</span>;</li>
<li> MAY contain an end time <span class="name">et</span>;</li>
-<li> contains a set of attribute-value pairs <span class="name">[ attr1=val1, ...]</span>, representing other attributes of this activity that hold for its all duration.</li>
+<li> contains a set of attribute-value pairs <span class="name">[ attr1=val1, ...]</span>, representing other attributes of this activity that hold for its whole duration.</li>
</ul>
@@ -743,7 +858,7 @@
-<p>An <dfn id="dfn-Agent">agent expression</dfn> is a representation a characterized thing capable of
+<p>An <dfn id="dfn-Agent">agent expression</dfn> is a representation of a characterized thing capable of
activity.</p>
<p>In PROV-ASN, an agent expression's text matches the <span class="nonterminal">agentExpression</span> production of the grammar defined in this specification document.
@@ -777,7 +892,7 @@
entity(e2) and wasControlledBy(pe,e2,qualifier(role="author"))
</pre>
-<p>the entity expression identified by <span class="name">e1</span> is accompanied by an explicit assertion of an agent expression, and this assertion holds irrespective of process executions it may be involved in. On the contrary, from the entity expression identified by <span class="name">e2</span>, one can inferred an agent expression, as per the following inference.
+<p>the entity expression identified by <span class="name">e1</span> is accompanied by an explicit assertion of an agent expression, and this assertion holds irrespective of process executions it may be involved in. On the other hand, from the entity expression identified by <span class="name">e2</span>, one can infer an agent expression, as per the following inference.
</p>
<div class='constraint' id='control-agent'>
@@ -836,7 +951,7 @@
</p>
<p>
-Name-value pairs occurring in annotations differ from attribute-value pairs (occurring in entity expressions and process execution expressions). Attribute-value pairs MUST be a representation of something in the world, which remain constant for the duration of the characterization interval (for entity expression) or the activity duration (for process execution expressions). It is OPTIONAL for name-value pairs to be representations of something in the world. If they are a representation of something in the world, then it MAY change value for the corresponding duration. If name-value pairs are a representation of something in the world that does not change, they are not regarded as determining characteristics of a characterized thing or activity, for the purpose of provenance. Indeed, it is not expectede that provenance would contain an explanation for these attribute-values.
+Name-value pairs occurring in annotations differ from attribute-value pairs (occurring in entity expressions and process execution expressions). Attribute-value pairs MUST be a representation of something in the world, which remain constant for the duration of the characterization interval (for entity expression) or the activity duration (for process execution expressions). It is OPTIONAL for name-value pairs to be representations of something in the world. If they are a representation of something in the world, then it MAY change value for the corresponding duration. If name-value pairs are a representation of something in the world that does not change, they are not regarded as determining characteristics of a characterized thing or activity, for the purpose of provenance. Indeed, it is not expected that provenance would contain an explanation for these attribute-values.
</p>
@@ -876,7 +991,7 @@
-<p>An instance of a generation expression, noted <span class="name">wasGeneratedBy(e,pe,q,t)</span> in PROV-ASN:</p>
+<p>An instance of a generation expression, written <span class="name">wasGeneratedBy(e,pe,q,t)</span> in PROV-ASN:</p>
<ul>
<li> contains an identifier <span class="name">e</span> identifying an entity expression that represents the characterized thing that is created; </li>
<li> contain an identifier <span class="name">pe</span> identifying a process execution expression that represents the activity that creates the characterized thing;</li>
@@ -913,8 +1028,8 @@
<div class='constraint' id='generation-affects-attributes'>Given an identifier <span class="name">pe</span> for a process execution expression, an identifier <span class="name">e</span> for an entity expression, qualifier <span class="name">q</span>, and optional time <span class="name">t</span>,
-<span class='conditional'>if</span> the assertion <span class="name">wasGeneratedBy(e,pe,r)</span>
-or <span class="name">wasGeneratedBy(e,pe,r,t)</span> holds, <span class='conditional'>then</span> the values of <em>some</em> of <span class="name">e</span>'s
+<span class='conditional'>if</span> the assertion <span class="name">wasGeneratedBy(e,pe,p)</span>
+or <span class="name">wasGeneratedBy(e,pe,q,t)</span> holds, <span class='conditional'>then</span> the values of <em>some</em> of <span class="name">e</span>'s
attributes are determined by the activity represented by process execution expression identified by <span class="name">pe</span> and the
entity expressions used by <span class="name">pe</span>.
Only some (possibly none) of the attributes values may be determined
@@ -925,7 +1040,7 @@
The assertion of a generation event implies ordering of events in the world.
-<div class='constraint' id='generation-pe-ordering'><span class='conditional'>If</span> an assertion <span class="name">wasGeneratedBy(x,pe,r)</span> or <span class="name">wasGeneratedBy(x,pe,r,t)</span>, <span class='conditional'>then</span> generation of the thing denoted by <span class="name">x</span> precedes the end
+<div class='constraint' id='generation-pe-ordering'><span class='conditional'>If</span> an assertion <span class="name">wasGeneratedBy(x,pe,q)</span> or <span class="name">wasGeneratedBy(x,pe,q,t)</span>, <span class='conditional'>then</span> generation of the thing denoted by <span class="name">x</span> precedes the end
of <span class="name">pe</span> and follows the beginning of <span class="name">pe</span>.
</div>
@@ -963,7 +1078,7 @@
</div>
-<p>An instance of a use expression, noted <span class="name">used(pe,e,q,t)</span> in PROV-ASN:</p>
+<p>An instance of a use expression, written <span class="name">used(pe,e,q,t)</span> in PROV-ASN:</p>
<ul>
<li> refers to a process execution expression identified by <span class="name">pe</span>, which represents the consuming activity;</li>
<li> refers to an entity expression identified by <span class="name">e</span>, which represents the characterized thing that is consumed;</li>
@@ -1068,7 +1183,7 @@
<p>A process execution linked derivation expression, which, by definition of a derivation expression, is a representation that some characterized thing is transformed from, created from, or affected by another characterized thing, also entails the existence of a process execution expression that represents an activity that transforms, creates or affects this characterized thing.</p>
-<p>In its full form, a process-execution linked derivation expression, noted <span class="name">wasDerivedFrom(e2,e1,pe,q2,q1)</span> in PROV-ASN:</p>
+<p>In its full form, a process-execution linked derivation expression, written <span class="name">wasDerivedFrom(e2,e1,pe,q2,q1)</span> in PROV-ASN:</p>
<ul>
<li> refers to an entity expression identified by <span class="name">e2</span>, which is a representation of the generated characterized thing;</li>
<li> refers to an entity expression identified by <span class="name">e1</span>, which is a representation of the used characterized thing;</li>
@@ -1091,7 +1206,7 @@
<p>The following derivation assertions</p>
<pre class="example">
-wasDerivedFrom(e5,e3,pe4,qualifier(channel=out),qualifier(channel=in))
+wasDerivedFrom(e5,e3,pe4,qualifier(channel="out"),qualifier(channel="in"))
wasDerivedFrom(e3,e2)
</pre>
<p>
@@ -1109,8 +1224,8 @@
</p>
<div class="constraint" id='derivation-events'>
-<span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1,pe,r2,r1)</span> holds, <span class='conditional'>then</span>
- <span class="name">wasGeneratedBy(e2,pe,r2)</span> and <span class="name">used(pe,e1,r1)</span> also
+<span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1,pe,q2,q1)</span> holds, <span class='conditional'>then</span>
+ <span class="name">wasGeneratedBy(e2,pe,q2)</span> and <span class="name">used(pe,e1,q1)</span> also
hold.
</div>
@@ -1149,10 +1264,10 @@
<p>
Note that inferring derivation from use and generation does not hold
-in general. Indeed, when a generation <span class="name">wasGeneratedBy(e2,pe,r2)</span>
-precedes <span class="name">used(pe,e1,r1)</span>, for
-some <span class="name">e1</span>, <span class="name">e2</span>, <span class="name">r1</span>, <span class="name">r2</span>, and <span class="name">pe</span>, one
-cannot infer derivation <span class="name">wasDerivedFrom(e2,e1,pe,r2,r1)</span>
+in general. Indeed, when a generation <span class="name">wasGeneratedBy(e2,pe,q2)</span>
+precedes <span class="name">used(pe,e1,q1)</span>, for
+some <span class="name">e1</span>, <span class="name">e2</span>, <span class="name">q1</span>, <span class="name">q2</span>, and <span class="name">pe</span>, one
+cannot infer derivation <span class="name">wasDerivedFrom(e2,e1,pe,q2,q1)</span>
or <span class="name">wasDerivedFrom(e2,e1)</span> since the values of attributes
of <span class="name">e2</span> cannot possibly be determined by the values of attributes
of <span class="name">e1</span>, given the creation of <span class="name">e2</span> precedes the use
@@ -1164,7 +1279,7 @@
<div class='constraint' id='derivation-use'>
<p>Given a process execution expression identified by <span class="name">pe</span>, entity expressions identified by <span class="name">e1</span> and <span class="name">e2</span>, and qualifier <span class="name">q2</span>,
<span class='conditional'>if</span> <span class="name">wasDerivedFrom(e2,e1)</span> and <span class="name">wasGeneratedBy(e2,pe,q2)</span> hold, <span class='conditional'>then</span> there exists a qualifier <span class="name">q1</span>,
-such that <span class="name">used(pe,e1,r1)</span> also holds.
+such that <span class="name">used(pe,e1,q1)</span> also holds.
</div>
<p>This inference is justified by the fact that the characterized thing represented by entity expression identified by <span class="name">e2</span> is generated by at most one activity in a given account (see <a href="#generation-unicity">generation-unicity</a>). Hence, this process execution expression is also the one referred to in the use expression of <span class="name">e1</span>.
</p>
@@ -1173,7 +1288,7 @@
<p>We note that the "symmetric" inference, does not hold.
From <span class="name">wasDerivedFrom(e2,e1)</span> and <span class="name">used(pe,e1)</span>, one cannot
-derive <span class="name">wasGeneratedBy(e2,pe,r2)</span> because identifier <span class="name">e1</span> may occur in use expressions referring to
+derive <span class="name">wasGeneratedBy(e2,pe,q2)</span> because identifier <span class="name">e1</span> may occur in use expressions referring to
many process execution expressions, but they may not be referred to in generation expressions containing identifier <span class="name">e2</span>.</p>
@@ -1217,9 +1332,9 @@
contains or implies the existence of a process execution expression. Hence, from
the former, we can infer the latter.</p>
<div class='constraint' id='derivation-linked-independent'>
-Given two entity expressions denoted by <span class="name">e1</span> and <span class="name">e2</span>, <span class='conditional'>if</span> the assertion <span class="name">wasEventuallyDerivedFrom(e2,e1)</span>
+Given two entity expressions denoted by <span class="name">e1</span> and <span class="name">e2</span>, <span class='conditional'>if</span> the assertion <span class="name">wasDerivedFrom(e2,e1)</span> or <span class="name">wasDerivedFrom(e2,e1,pe,q12,q1)</span>
holds, <span class='conditional'>then</span> the
- the assertion <span class="name">wasEventuallyDerivedFrom(e2,e1)</span> also holds.
+ the expression <span class="name">wasEventuallyDerivedFrom(e2,e1)</span> also holds.
</div>
<p>Hence, a process-execution independent derivation expression can be directly asserted or can be inferred (by means of <a href="#derivation-linked-independent">derivation-linked-independent</a>).</p>
@@ -1231,6 +1346,7 @@
+
</section>
<section>
@@ -1249,13 +1365,13 @@
<li> contains an identifier <span class="name">e2</span>, denoting an entity expression, which represents the characterized thing that is the result of the derivation;
<li> contains an identifier <span class="name">e1</span>, denoting an entity expression, which represents the characterized thing that the derivation relies upon.
</ul>
-<p>The expression <span class="name">dependedOn</span> can only be inferred; in other word, it cannot be asserted. It is
+<p>The expression <span class="name">dependedOn</span> can only be inferred; in other words, it cannot be asserted. It is
transitive by definition and relies on the previously defined derivation assertions for its
base case.</p>
<div class='constraint' id='transitive-derivation'>
<ul>
-<li><span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1)</span> or <span class="name">wasDerivedFrom(e2,e1,pe,r2,r1)</span> holds, <span class='conditional'>then</span> <span class="name">dependedOn(e2,e1)</span> holds.</li>
+<li><span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1)</span> or <span class="name">wasDerivedFrom(e2,e1,pe,q2,q1)</span> holds, <span class='conditional'>then</span> <span class="name">dependedOn(e2,e1)</span> holds.</li>
<li><span class='conditional'>If</span> <span class="name">wasEventuallyDerivedFrom(e2,e1)</span> holds, <span class='conditional'>then</span> <span class="name">dependedOn(e2,e1)</span> holds.</li>
<li><span class='conditional'>If</span> <span class="name">dependedOn(e3,e2)</span> and <span class="name">dependedOn(e2,e1)</span> hold, <span class='conditional'>then</span> <span class="name">dependedOn(e3,e1)</span> holds.</li>
</ul>
@@ -1269,6 +1385,18 @@
<div class='issue'>Should derivation have a time? Which time? This is <a href="http://www.w3.org/2011/prov/track/issues/43">ISSUE-43</a>.</div>
+<div class='issue'>Derivations must take into account characterization intervals, otherwise, transitivity
+leads to incorrect conclusion. This is <a href="http://www.w3.org/2011/prov/track/issues/108">ISSUE-108</a>.
+<pre>
+
+ ------------- e1
+ --------------------------------------- e2
+ ------------- e3
+</pre>
+ dependedOn(e2,e1) does not make sense, since e1 began to exist after e2.
+
+</div>
+
</section>
@@ -1297,7 +1425,7 @@
</div>
-<p>An instance of a control expression, noted <span class="name">wasControlledBy(pe,ag,q)</span> in PROV-ASN:</p>
+<p>An instance of a control expression, written <span class="name">wasControlledBy(pe,ag,q)</span> in PROV-ASN:</p>
<ul>
<li> contains an identifier <span class="name">pe</span> denoting a process execution expression, representing the controlled activity;
<li> refers to an agent expression or an entity expression identified by <span class="name">ag</span>, representing the controlling characterized thing;
@@ -1308,9 +1436,9 @@
<p>
The following control assertion</p>
<pre class="example">
-wasControlledBy(pe3,a4,[role=author])
+wasControlledBy(pe3,a4,qualifier[role="author"])
</pre>
-<p>states that the activity, represented by the process execution expression denoted by <span class="name">pe3</span> saw the involvement of a characterized thing, represented by entity expression denoted by <span class="name">a4</span> in the capacity of author. This specification defines the qualifier name <span class="name">role</span> (see Section <a href="#expression-qualifier">Qualifier</a>) to denote the function of a characterized thing with respect to an activity.
+<p>states that the activity, represented by the process execution expression denoted by <span class="name">pe3</span> saw the involvement of a characterized thing, represented by entity expression denoted by <span class="name">a4</span> in the capacity of author. This specification reserves the qualifier name <span class="name">role</span> (see Section <a href="#expression-qualifier">Qualifier</a>) to denote the function of a characterized thing with respect to an activity.
</p>
</section>
@@ -1325,24 +1453,24 @@
<p>
-The rationale for introducing this relationship is that in general, at any given time, for a thing in the world, there may be multiple ways of characterizing it, and hence multiple representations can be asserted by different asserters. In the example that follows, suppose thing "Royal Society" is represented by two asserters, each using a different set of attributes. If the asserters agree that both representations refer to "The Royal Society", the question of whether any correspondence can be established between the two representations arises naturally. This is particularly relevant when (a) the sets of properties used by the two representations overlap partially, or (b) when one set is subsumed by the other. In both these cases, we have a situation where each of the two asserters has a partial view of "The Royal Society", and establishing a correspondence between them on the shared properties is beneficial, as in case (a) each of the two representation <em>complements</em> the other, and in case (b) one of the two (that with the additional properties) complements the other.</p>
-
-<p>This intuition is made more precise by considering the entities that form the representations of characterised things at a certain point in time.
+The rationale for introducing this relationship is that in general, at any given time, for a thing in the world, there may be multiple ways of characterizing it, and hence multiple representations can be asserted by different asserters. In the example that follows, suppose thing "Royal Society" is represented by two asserters, each using a different set of attributes. If the asserters agree that both representations refer to "The Royal Society", the question of whether any correspondence can be established between the two representations arises naturally. This is particularly relevant when (a) the sets of attributes used by the two representations overlap partially, or (b) when one set is subsumed by the other. In both these cases, we have a situation where each of the two asserters has a partial view of "The Royal Society", and establishing a correspondence between them on the shared attributes is beneficial, as in case (a) each of the two representation <em>complements</em> the other, and in case (b) one of the two (that with the additional attributes) complements the other.</p>
+
+<p>This intuition is made more precise by considering the entities that form the representations of characterized things at a certain point in time.
An entity expression represents, by means of attribute-value pairs, a thing and its situation in the world, which remain constant over a characterization interval.
-As soon as the thing's situation changes, this marks the end of the characterization interval for the entity expression representing it. The thing's novel situation is represented by an attribute with a new value, or an entirely different set of attribute-value pairs, embodied in another entity expression, with a new characterization interval. Thus, if we overlap the timelines (or, more generally, the sequences of value-changing events) for the two characterised things, we can hope to establish correspondences amongst the entity expressions that represent them at various points along that events line. The figure below illustrates this intuition.</p>
+As soon as the thing's situation changes, this marks the end of the characterization interval for the entity expression representing it. The thing's novel situation is represented by an attribute with a new value, or an entirely different set of attribute-value pairs, embodied in another entity expression, with a new characterization interval. Thus, if we overlap the timelines (or, more generally, the sequences of value-changing events) for the two characterized things, we can hope to establish correspondences amongst the entity expressions that represent them at various points along that events line. The figure below illustrates this intuition.</p>
<img src="complement-of.png" alt="illustration complementOf"/>
<p>
-Relation <em>complement-of</em> between two entity expressions is intended to capture these correspondences, as follows. Suppose entity expressions A and B share a set P of properties, and each of them has other properties in addition to P. If the values assigned to each property in P are <em>compatible</em> between A and B, then we say that <em>A is-complement-of B</em>, and <em>B is-complement-of A</em>, in a symmetrical fashion. In the particular case where the set P of properties of B is a strict superset of A's properties, then we say that <em>B is-complement-of A</em>, but in this case the opposite does not hold. In this case, the relation is not symmetric. (as a special case, A and B may not share any attributes at all, and yet the asserters may still stipulate that they are representing the same thing "Royal Society". The symmetric relation may hold trivially in this case).</p>
+Relation <em>complement-of</em> between two entity expressions is intended to capture these correspondences, as follows. Suppose entity expressions A and B share a set P of attributes, and each of them has other attributes in addition to P. If the values assigned to each attribute in P are <em>compatible</em> between A and B, then we say that <em>A is-complement-of B</em>, and <em>B is-complement-of A</em>, in a symmetrical fashion. In the particular case where the set P of attributes of B is a strict superset of A's attributes, then we say that <em>B is-complement-of A</em>, but in this case the opposite does not hold. In this case, the relation is not symmetric. (as a special case, A and B may not share any attributes at all, and yet the asserters may still stipulate that they are representing the same thing "Royal Society". The symmetric relation may hold trivially in this case).</p>
<p>The term <em>compatible</em> used above means that a mapping can be established amongst the values of attributes in P and found in the two entity expession. This generalizes to the case where attribute sets P1 and P2 of A, and B, respectively, are not identical but they can be mapped to one another. The simplest case is the identity mapping, in which A and B share attribute set P, and furthermore the values assigned to attributes in P match exactly.</p>
<p>It is important to note that the relation holds only for the characterization intervals of the entity expessions involved As soon as one attribute changes value in one of them, new correspondences need to be found amongst the new entities. Thus, the relation has a validity span that can be expressed in terms of the event lines of the thing.</p>
<!--
-The "IVP of" relationship is designed to represent pairs of entities that correspond to each other. By their own nature, an entity remains valid only as long as all of its attributes do not change their value. It follows that the correspondence "B IVP of A" is only valid within the time interval during which such invariance property holds for both A and B. When any of the property values change in either A or B, those entities are replaced by new ones, and a new correspondence may be established. Thus, "IVP of" is defined relative to the intersection of the temporal intervals for which A and B are valid.
+The "IVP of" relationship is designed to represent pairs of entities that correspond to each other. By their own nature, an entity remains valid only as long as all of its attributes do not change their value. It follows that the correspondence "B IVP of A" is only valid within the time interval during which such invariance attribute holds for both A and B. When any of the attribute values change in either A or B, those entities are replaced by new ones, and a new correspondence may be established. Thus, "IVP of" is defined relative to the intersection of the temporal intervals for which A and B are valid.
-->
@@ -1401,12 +1529,15 @@
<div class='note'>We will allow wasComplementOf to be asserted between entities identified by qualified identifiers. This will allow us to express wasComplementOf between entities asserted in separate accounts (potentially, with the same identifiers).
</div>
-
-<div class='pending'>Mutual ivpOf each other should be agreed. This is <a href="http://www.w3.org/2011/prov/track/issues/29">ISSUE-29</a></div>
-
-<div class='pending'>Do we need a sameAsEntity relation. This is <a href="http://www.w3.org/2011/prov/track/issues/35">ISSUE-35</a></div>
-
-<div class='pending'>Is ivpOf transitive? This is <a href="http://www.w3.org/2011/prov/track/issues/45">ISSUE-45</a></div>
+<div class='note'>It is suggested that the name 'wasComplementOf' does not capture the meaning of this relation adequately. No concrete suggestion has been made so far.
+Furthermore, there is a suggestion that an alternative relation that is transitive may also be useful.
+This is raised in the following <a href="http://lists.w3.org/Archives/Public/public-prov-wg/2011Sep/0315.html">email</a>.</div>
+
+
+
+<div class='issue'>A discussion on alternative definition of wasComplementOf has not reached a satisfactory conclusion yet. This is <a href="http://www.w3.org/2011/prov/track/issues/29">ISSUE-29</a></div>
+
+
<div class='pending'> Comments on ivpof in <a href="http://www.w3.org/2011/prov/track/issues/57">ISSUE-57</a>.</div>
@@ -1551,7 +1682,7 @@
-<p>An instance of a revision expression, noted <span class="name">wasRevisionOf(e2,e1,ag)</span> in PROV-ASN:</p>
+<p>An instance of a revision expression, written <span class="name">wasRevisionOf(e2,e1,ag)</span> in PROV-ASN:</p>
<ul>
<li> contains an identifier <span class="name">e2</span> identifying an entity that represents a newer version of a thing;
<li> contains an identifier <span class="name">e1</span> identifying an entity that represents an older version of a thing;
@@ -1615,7 +1746,7 @@
<p>An instance of a participation expression,
-noted <span class="name">hadParticipant(pe,e)</span> in PROV-ASN:
+written <span class="name">hadParticipant(pe,e)</span> in PROV-ASN:
<ul>
<li> contains to identifier <span class="name">pe</span> identifying a process execution expression representing an activity;
<li> contains an identifier <span class="name">e</span> identifying an entity expression, which is
@@ -1663,9 +1794,22 @@
<span class="nonterminal">identifier</span>
<span class="name">)</span><br/>
<span class="nonterminal">relationIdentification</span> :=
-<span class="nonterminal">identifier</span> <span class="nonterminal">identifier</span> <span class="nonterminal">qualifier</span>
+<span class="name">relation</span>
+<span class="name">(</span>
+<span class="nonterminal">identifier</span>
+<span class="name">,</span>
+<span class="nonterminal">identifier</span>
+<span class="name">,</span>
+<span class="nonterminal">qualifier</span>
+[<span class="name">,</span>
+<span class="nonterminal">qualifier</span>
+]
+<span class="name">)</span>
</div>
+<p>Since relations do not have identifiers but can be annotated, a <span class="nonterminal">relationIdentification</span> mechanism is provided allowing the constituents of relations to be listed so as to identify relations.
+</p>
+
<p>The interpretation of annotations is application-specific. See Section <a href="#expression-annotation">Annotation</a> for a discussion of the difference between attributes and annotations. </p>
<p>
@@ -1673,11 +1817,18 @@
<pre class="example">
entity(e1,[type="document"])
entity(e2,[type="document"])
+processExecution(pe,transform,t1,t2,[])
+used(pe,e1,qualifier(file="stdin"))
+wasGeneratedBy(e2, pe, qualifier(file="stdout"))
+
annotation(ann1,[icon="doc.png"])
hasAnnotation(e1,ann1)
hasAnnotation(e2,ann1)
+
+annotation(ann2,[style="dotted"])
+hasAnnotation(relation(pe,e1,qualifier(file="stdin")),ann2)
</pre>
-<p>assert the existence of two documents in the world (attribute-value pair: <span class="name">type="document"</span>) represented by entity expressions identified by <span class="name">e1</span> and <span class="name">e2</span>, and annotate these expressions with an annotation indicating that the icon (an application specific way of rendering provenance) is <span class="name">doc.png</span>.
+<p>assert the existence of two documents in the world (attribute-value pair: <span class="name">type="document"</span>) represented by entity expressions identified by <span class="name">e1</span> and <span class="name">e2</span>, and annotate these expressions with an annotation indicating that the icon (an application specific way of rendering provenance) is <span class="name">doc.png</span>. It also asserts a process execution, its use of the first entity, and its generation of the second entity. The <span class="name">used</span> relation is annotated with a style (an application specific way of rendering this edge graphically).
</p>
@@ -1720,7 +1871,7 @@
<span class="name">)</span>
</div>
-<p>An instance of an account expression, noted <span class="name">account(id, uri, exprs)</span> in PROV-ASN:</p>
+<p>An instance of an account expression, written <span class="name">account(id, uri, exprs)</span> in PROV-ASN:</p>
<ul>
<li> contains an identifier <span class="name">id</span> to identify this account;</li>
<li> contains an asserter identified by URI denoted by <span class="name">uri</span>;</li>
@@ -1742,7 +1893,7 @@
...
processExecution(pe0,create-file,t)
...
- wasGeneratedBy(e0,pe0,outFile)
+ wasGeneratedBy(e0,pe0,qualifier())
...
wasControlledBy(pe4,a5, qualifier(role="communicator")) )
</pre>
@@ -1795,7 +1946,7 @@
...
processExecution(pe1,create-file,t1)
...
- wasGeneratedBy(e0,pe1,outFile)
+ wasGeneratedBy(e0,pe1,qualifier(fct="create"))
... )
</pre>
<p>with identifier <span class="name">acc2</span>, containing assertions by asserter by <span class="name">http://example.org/asserter2</span> stating that thing represented by entity expression identified by <span class="name">e0</span> was generated by an activity represented by process execution expression identified by <span class="name">pe1</span> instead of <span class="name">pe0</span> in the previous account <span class="name">acc0</span>. If accounts <span class="name">acc0</span> and <span class="name">acc2</span> are merged together, the resulting set of expressions violates <a href="#generation-unicity">generation-unicity</a>.</p>
@@ -1809,12 +1960,12 @@
http://example.org/asserter1,
entity(e0, [ type="File", location="/shared/crime.txt", creator="Alice" ])
processExecution(pe0,create-file,t)
- wasGeneratedBy(e0,pe0,outFile)
+ wasGeneratedBy(e0,pe0,qualifier())
account(acc4,
http://example.org/asserter2,
entity(e1, [ type="File", location="/shared/crime.txt", creator="Alice", content="" ])
processExecution(pe0,copy-file,t)
- wasGeneratedBy(e1,pe0,outFile)
+ wasGeneratedBy(e1,pe0,qualifier(fct="create"))
isComplement(e1,e0)))
</pre>
<p>Alternatively, a process execution expression identified by <span class="name">pe0</span> occurs in each of the two accounts. Therefore, each process execution expression is asserted in a separate scope, and therefore may represent different activities in the world.
@@ -1831,7 +1982,7 @@
<section id="ProvenanceContainer">
<h4>Provenance Container</h4>
-<p>A <dfn id="dfn-ProvenanceContainer">provenance container</dfn> is a house-keeping construct of PROV-DM, also capable of bundling PROV-DM expressions. A provenance container is not an expression, but can be exploited to return all the provenance assertions in response to a request for the provenance of something ([[PROV-PAQ]]). </p>
+<p>A <dfn id="dfn-ProvenanceContainer">provenance container</dfn> is a house-keeping construct of PROV-DM, also capable of bundling PROV-DM expressions. A provenance container is not an expression, but can be exploited to return assertions in response to a request for the provenance of something ([[PROV-PAQ]]). </p>
<p>In PROV-ASN, a provenance container's text matches the <span class="nonterminal">provenanceContainer</span> production of the grammar defined in this specification document.</p>
@@ -1848,13 +1999,13 @@
<span class="name">)</span>
</div>
-<p>An instance of a provenance container, noted <span class="name">provenanceContainer(decls, ids, exprs)</span> in PROV-ASN:
+<p>An instance of a provenance container, written <span class="name">provenanceContainer(decls, ids, exprs)</span> in PROV-ASN:
<ul>
<li> contains a set of namespace declarations <span class="name">decls</span>, declaring namespaces and associated prefixes, which can be used in attributes (conformant to production <span class="nonterminal">attribute</span>) and in names (conformant to production <span class="nonterminal">name</span>) in <span class="name">exprs</span>;</li>
<li> contains a set of identifiers <span class="name">ids</span> naming all accounts occurring (at any nesting level) in <span class="name">exprs</span>;</li>
<li> contains one or more expressions <span class="name">exprs</span>.</li>
</ul>
-<p>All the expressions in <span class="name">exprs</span> are implictly wrapped in a default account, scoping all the identifiers they declare directly, and constituting a toplevel account, in the hierarchy of accounts.</p>
+<p>All the expressions in <span class="name">exprs</span> are implictly wrapped in a default account, scoping all the identifiers they declare directly, and constituting a toplevel account, in the hierarchy of accounts. Consequently, every provenance expression is always expressed in the context of an account, either explicitly in an asserted account, or implicitly in a container's default account.</p>
<p>
The following container </p>
@@ -1943,7 +2094,7 @@
</ul>
-<p>The PROV data model introduces a specific qualifier <span class="name">role</span> to denote the function of a characterized thing with respect to an activity, in the context of a use/generation/control relation. The value associated with a <span class="name">role</span> attribute MUST be conformant with <span class="nonterminal">Literal</span>. </p>
+<p>The PROV data model introduces the qualifier <span class="name">role</span> in the <a href="#prov-dm-namespace">PROV-DM namespace</a> to denote the function of a characterized thing with respect to an activity, in the context of a use/generation/control relation. The value associated with a <span class="name">role</span> attribute MUST be conformant with <span class="nonterminal">Literal</span>. </p>
<p>
@@ -2123,6 +2274,8 @@
</section>
+</section>
+
<section id="extensibility-section">
<h2>PROV-DM Extensibility Points</h2>
@@ -2132,7 +2285,7 @@
<ul>
<li> Attributes are constructs of the data model that allow representations of aspects of the world's things and activities to be expressed. Applications are free to introduce application-specific attributes, according to their perspective on the world. Attributes for a given application can be distinguished by qualifying them with a prefix denoting a namespace declared in a namespace declaration.
-<p>The PROV DM namespace (TBD) declares a set of reserved attributes: <span class="name">type</span>, <span class="name">location</span>.</li>
+<p>The <a href="#prov-dm-namespace">PROV-DM namespace</a> declares a set of reserved attributes: <span class="name">type</span>, <span class="name">location</span>.</li>
<li>Annotation expressions allow arbitrary metadata to be associated with identifiable expressions of PROV-DM. Annotation expressions consist of name-value pairs. Like attributes, names are qualified by a namespace.</li>
@@ -2141,7 +2294,7 @@
They consist of ordered sequence of name-value pairs. Such names
are also qualified by namespaces.
-<p>The PROV DM namespace (TBD) declares a reserved qualifier: <span class="name">role</span>.</p></li>
+<p>The <a href="#prov-dm-namespace">PROV-DM namespace</a> declares a reserved qualifier: <span class="name">role</span>.</p></li>
<li>Namespaces allow attributes and names to be qualified. </li>
@@ -2155,8 +2308,8 @@
</section>
- <section>
-<h2>Standard extensions</h2>
+ <section id="prov-dm-extensions">
+<h2>PROV-DM extensions</h2>
<section id="expression-Collection">
@@ -2278,7 +2431,7 @@
Quotation represents the repeating or copying of some part of a characterized thing.
-<p> An assertion wasQuoteOf, noted <span class="name"> wasQuoteOf(e2,e1,ag,ag2)</span>:</p>
+<p> An assertion wasQuoteOf, written <span class="name"> wasQuoteOf(e2,e1,ag,ag2)</span>:</p>
<ul>
<li>refers to an entity <span class="name">e2</span>, denoting the quote;
<li>refers to an entity <span class="name">e1</span>, denoting the entity being quoted;
@@ -2297,7 +2450,7 @@
Attribution represents that a characterized thing is ascribed to an agent.
-<p> An assertion wasAttributedTo, noted <span class="name"> wasAttributedTo(e1,ag)</span>:</p>
+<p> An assertion wasAttributedTo, written <span class="name"> wasAttributedTo(e1,ag)</span>:</p>
<ul>
<li>refers to an entity <span class="name">e2</span>, denoting the entity;
<li>refers to an agent who the entity is attributed to <span class="name">ag</span>.
@@ -2314,7 +2467,7 @@
<h3>Summary</h3>
Represents a characterized thing that is a synopsis or abbreviation of another entity.
-<p> An assertion wasSummaryOf, noted <span class="name"> wasSummaryOf(e2,e1)</span>:</p>
+<p> An assertion wasSummaryOf, written <span class="name"> wasSummaryOf(e2,e1)</span>:</p>
<ul>
<li>refers to an entity <span class="name">e2</span>, denoting the summary;
<li>refers to an entity <span class="name">e1</span>, denoting the entity being summarized.
@@ -2332,7 +2485,7 @@
Represents a characterized thing in which another characterized thing first appeared.
-<p> An assertion hasOriginalSource, noted <span class="name"> hasOriginalSource(e2,e1)</span>:</p>
+<p> An assertion hasOriginalSource, written <span class="name"> hasOriginalSource(e2,e1)</span>:</p>
<ul>
<li>refers to an entity <span class="name">e2</span>, denoting the entity that first appeared;
<li>refers to an entity <span class="name">e1</span>, denoting the entity where that entity first appeared.
@@ -2344,9 +2497,76 @@
</section>
- </section>
+</section>
</section>
+<section id="resource-section">
+<h2>Resources, URIs, Entities, Identifiers, and Scope</h2>
+
+<p>This specification introduces the notion of an identifiable characterized thing in the world. In PROV-DM, an entity expression is a representation of such an identifiable characterized thing. An entity expression includes an identifier identifying this characterized thing. Identifiers are URIs (TBC). </p>
+
+<p>The term 'resource' is used in a general sense
+ for whatever might be identified by a URI [[!RFC3986]]. On the Web, a URI denotes a resource, without any expectation that the resource is accessed. </p>
+
+<p>The purpose of this section is to clarify the relationship between resource and the notions of characterized thing and entity expression. </p>
+
+<p>A resource is an instance of a thing in the world. One may take multiple perspectives on such a thing and its situation in the world, fixing some its aspects.</p>
+
+<p> We refer to the example of section <a href="#conceptualization">2.1</a> for a resource (at some URL) and three different perspectives, referred to as characterized things. Three different entity expressions can be expressed for this report, which in the PROV-ASN sample below, are expressed within a same account.
+</p>
+
+<pre>
+account(acc1,
+ http://example.org/asserter1,
+
+ entity(urn:demo:0, [ type="Document", location="http://example.org/crime.txt" ])
+ entity(urn:demo:1, [ type="Document", location="http://example.org/crime.txt", version="2.1", content="...", date="2011-10-07" ])
+ entity(urn:demo:2, [ type="Document", author="John" ])
+ ...)
+</pre>
+
+<p>Each entity expression contains an idenfier that identifies the characterized thing it represents.
+In this example, three identifiers were minted using the URN syntax with "demo" namespace.</p>
+
+<p>Given that the report is a resource denoted by the URI <span class="name">http://example.org/crime.txt</span>, we could simply use this URI as the identifier of an entity. This would avoid us minting new URIs. Hence, the report URI would play a double role: as a URI it denotes a resource accessible at that URI, and as a PROV-DM identifier, it identifies a specific characterization of this report. A given identifier identifies a single characterized thing within the scope of an account. Hence, below, all entities expressions have been given the same identifier but appear in the scope of different accounts. </p>
+
+<pre>
+account(acc2,
+ http://example.org/asserter1,
+
+ entity(http://example.org/crime.txt, [ type="Document", location="http://example.org/crime.txt" ])
+ ...)
+
+account(acc3,
+ http://example.org/asserter1,
+
+ entity(http://example.org/crime.txt, [ type="Document", location="http://example.org/crime.txt", version="2.1", content="...", date="2011-10-07" ])
+ ...)
+
+account(acc4,
+ http://example.org/asserter1,
+ entity(http://example.org/crime.txt, [ type="Document", author="John" ])
+ ...)
+</pre>
+
+<p>In this case, the URI <span class="name">http://example.org/crime.txt</span> still denotes the same resource; however, it identifies a different entity in each account. </p>
+
+<p> Alternatively, if we need to assert the existence of two different characterizations of the report within the same account, then alternate identifiers MUST be used, one of them being allowed to be the resource URI.</p>
+
+<pre>
+account(acc5,
+ http://example.org/asserter1,
+
+ entity(http://example.org/crime.txt, [ type="Document", location="http://example.org/crime.txt" ])
+ entity(urn:demo:1, [ type="Document", location="http://example.org/crime.txt", version="2.1", content="...", date="2011-10-07" ])
+
+ ...)
+
+</pre>
+
+
+</section>
+
<section class="appendix">
<h2>Illustration Conventions</h2>
@@ -2375,7 +2595,7 @@
<li>For use, generation, and derivation event, the first argument is the 'effect' (i.e. most recent item) and the second argument is the 'cause' (i.e. least recent item). This order is compatible with the temporal layout of the graphical notation.
-->
- </section>
+
<section class="appendix">
<h2>Acknowledgements</h2>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/model/satya-comments-issue-100.txt Mon Oct 10 12:23:53 2011 +0100
@@ -0,0 +1,127 @@
+
+ > My review comments for Section 5.2.1 Entity in the current version of the conceptual model document:
+ >
+ > 1. In PROV-DM, an entity expression is a representation of an
+ > identifiable characterized thing.
+ >
+ > Issue: Since the section heading is for Entity and the PROV DM
+ > component is Entity, I am confused why we are defining "Entity
+ > Expression" and not "Entity"?
+
+An instance of an entity expression is syntactally written as 'entity',
+but we use the term 'entity expression' to make it clear that we
+refer to a PROV-DM construct (see intro of section 5.1)
+
+PM have the feeling that Satya's point will be echoed by others -- you expect an element of the model and you find an element of the language.
+
+can we make an effort to keep the distinction model/language.
+
+PM how about introducing the entire sec. 2 with:
+
+"In this section, for each element of the model a corresponding ASN expression is introduced, by way of a production in the ASN grammar. "
+
+Then in 5.2.1:
+"In PROV-DM, an entity expression is a representation of an identifiable characterized thing."
+becomes
+"In PROV-DM, an entity is a representation of an identifiable characterized thing." Entities are asserted using entity expressions, according to the following grammar production:
+
+
+
+
+ >
+ > 2. An instance of an entity expression, noted entity(id, [ attr1=val1,
+ > ...]) in PROV-ASN contains an identifier id identifying a
+ > characterized thing; contains a set of attribute-value pairs [
+ > attr1=val1, ...], representing this characterized thing's situation in
+ > the world.
+ >
+ > Issue: When we refer to an entity in provenance assertions (in
+ > different applications), do we use the identifier to refer to it or
+ > both identifier + attribute-value pairs?
+
+Not sure I understand (in different applications).
+
+We refer to it with its identifier.
+
+PM identifier. not an issue
+
+
+ >
+ > 3. The assertion of an instance of an entity expression, entity(id, [
+ > attr1=val1, ...]), states, from a given asserter's viewpoint, the
+ > existence of an identifiable characterized thing, whose situation in
+ > the world is represented by the attribute-value pairs, which remain
+ > unchanged during a characterization interval, i.e. a continuous
+ > interval between two events in the world.
+ >
+ > Issue: Are the terms "characterization interval" and "continuous
+ > interval" defined by time values? What do we mean by "continuous
+ > interval" between two events?
+
+We assumed a partial order between events.
+An interval between events a and b [a,b] is the set of events x such that a<= x and x<=b.
+
+Does it really need to be defined explicitly?
+
+PM there is a hidden issue here though: how do we get agreement on event ordering? isn't this a way to sweep agreement on time under the rug?
+I am not competent enough to see this through I'm afraid but I see this will creep back up on us
+
+Luc: The reference to Lamport is crucial here. There is ordering in
+distributed systems because the receipt of a message always follows
+its sending.
+
+ We have extended that to: the use of an entity, follows its
+ generation. And, the end of a PE follows its start. All event
+ ordering constraints build on those two.
+
+Luc: it would be good to identify the events that delimit a characterization interval.
+ I don't think we have a precise answer for that.
+ Start would be a generation event.
+ End could be the generation of a new entity luc, age=10 terminates luc, age=9
+ End could be the destructive consumption of an entity: egg broken to make a cake
+
+Luc: events are not observable, but time is. Not global time, but local time, found
+on local clocks, more or leass synchronized.
+
+
+
+ > 4. If an asserter wishes to characterize a thing with the same
+ > attribute-value pairs over several intervals, then they are required
+ > to assert multiple entity expressions, each with its own identifier
+ > (so as to allow potential dependencies between the various entity
+ > expressions to be expressed).
+ >
+ > Issue: If a thing with same attribute-value pairs exists over several
+ > time? intervals - what will be the dependencies between the various
+ > entity expressions (since entity expressions = identifier +
+ > attribute-value pairs)? If they are different versions of an entity,
+ > they will have distinguishing attributes other than the simple
+ > occurrence at different points of time. Further, we multiple entity
+ > identifiers are used to refer to the same entity, then how do we
+ > reconcile them later?
+
+The example of "luc in boston" in January and June has been discussed extensively.
+That theroretically, we can find distinguishing attributes, yes (luc with winter clothes
+and summer clothes). But we have no requirements that these attributes are expressed.
+So, if we have just "luc in boston" as a characterization, the constraint makes sense.
+
+PM agreed
+
+ >
+ > I believe this consideration is not required and adds a layer of complexity.
+ >
+ > 5. A characterization interval may collapse into a single instant.
+ >
+ > Issue: Are we referring to time values. We seem to be using terms like
+ > "characterization interval", "continuous interval", "single instant"
+ > etc. as surrogates for time. I suggest that we explicitly use "time"
+ > if all these other terms are not distinguishable from time.
+
+Time is a can of worms, since we can have multiple clocks, not necessarily synchronised.
+
+That's why the whole model is event based.
+
+PM see my earlier comment. Satya has a point when he says events are "surrogates for time".
+Have no solution, but need more discussion goinf forward. This issue will continue
+
+Luc: I think that's the other way round. Observable time is an approximation for events.
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/model/satya-comments-issue-101.txt Mon Oct 10 12:23:53 2011 +0100
@@ -0,0 +1,67 @@
+ > Hi, My review comments for Section 5.2.2 Process Execution in the
+ > current version of the conceptual model document:
+ >
+ > Similar to issue with Entity, why are defining Process Execution
+ > expression?
+
+Same answer as before.
+
+ >
+ > 1. The activity that a process execution expression is a
+ > representation of has a duration, delimited by its start and its end
+ > events; hence, it occurs over an interval delimited by two
+ > events. However, a process execution expression need not mention time
+ > information, nor duration, because they may not be known.
+ >
+ > Issue: Is it possible that event information, similar to time
+ > information, may not be known? Is it possible to define a PE without
+ > having knowledge about its start and end events and also its duration
+ > (delimited by events)?
+
+Yes, in fact, we don't assert the start/end events.
+
+ >
+ > 2. Further characteristics of the activity in the world can be
+ > represented by other attribute-value pairs, which must also remain
+ > unchanged during the activity duration.
+ >
+ > Issue: If we have an attribute value for pe1: status = executing at t1
+ > and status = stopped at t2, would it violate the above constraint? If
+ > yes, we need to rethink the above constraint.
+
+This should not be seen as attribute, since this is an instantaneous status.
+It does not characterize the PE for its whole duration.
+
+ >
+ > 3. contains a set of attribute-value pairs [ attr1=val1, ...],
+ > representing other attributes of this activity that hold for its all
+ > duration.
+ >
+ > Issue: Not sure what the above statement means by "for all its
+ > durations" (typo) - are we referring to characterizing attributes (for
+ > the PE) or any attribute of the PE?
+
+Changed to: For its WHOLE duration
+
+ >
+ > 4. A process execution expression is not an entity expression. Indeed,
+ > an entity expression represents a thing that exists in full at any
+ > point in its characterization interval, persists during this interval,
+ > and preserves the characteristics that makes it
+ > identifiable. Alternatively, an activity in something that happens,
+ > unfolds or develops through time, but is typically not identifiable by
+ > the characteristics it exhibits at any point during its duration.
+ >
+ > Issue: This is a re-phrasing of the "continuant" and "occurrent"
+ > definition from the Basic Formal Ontology [1] (proposed by me in email
+ > thread on PROV-ISSUE-66 [2]). I think we should cite BFO with this.
+
+This is a concept from philosophy, W. E. Johnson, Logic: Part III (1924)
+
+Do we want to cite this book? There are lots of other things we could
+also cite!
+
+ >
+ > [1]BFO: www.ifomis.org/bfo/1.1
+ > [2]http://lists.w3.org/Archives/Public/public-prov-wg/2011Aug/0038.html
+ >
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/model/satya-comments.txt Mon Oct 10 12:23:53 2011 +0100
@@ -0,0 +1,147 @@
+ > Hi all,
+ > I have some review comments on Section 2.1 and Section 3 of the
+ > current version of the conceptual document (these do not include
+ > typos/language and related issues).
+ >
+ > Section 2.1 ===== 1. A characterized thing fixes some aspects of a
+ > thing and its situation in the world, so that it becomes possible to
+ > express its provenance, and what causes these specific aspects to be
+ > as such. An alternative characterized thing may fix other aspects, and
+ > its provenance may be entirely different.
+ >
+ > Issue: A "thing" may be characterized differently, that is viewed in
+ > distinct ways, but they are still the same thing. Does the above
+ > statement refer to the "same" thing characterized differently or
+ > distinct things? If the above statement is referring to different
+ > characterization of the same thing, how can their provenance be
+ > "entirely different"?
+
+The example in section 2.1 illustrates multiple perspectives about a same
+resource with a URL. The provenance is different.
+
+Removed word 'entirely'.
+
+ >
+ > 2. The provenance of these three characterized things will differ, and
+ > may be along the follow lines: a) the provenance of a report available
+ > at URL may include: the act of publishing it and making it available
+ > at a given location, possibly under some license and access control;
+ > b) the provenance of the version of the report available there today
+ > may include: the authorship of the specific content, and reference to
+ > imported content; c) the provenance of the report independent of where
+ > it is hosted over time may include: the motivation for writing the
+ > report, the overall methodology for producing it, and the broad team
+ > involved in it.
+ >
+ > Issue: Not sure about the issue that is being illustrated/described
+ > here - the three "characterized" things may be the same or
+ > different. In case they are the same thing - Report A (version 1.0,
+ > only one version was ever published) located at URL
+ > www.xyz.com/ReportA_V1.0 can be referred to differently by individual
+ > applications according to their requirements: simply as Report A, or
+ > as version 1.0 of Report A, or www.xyz.com/ReportA_v1.0 - in this case
+ > provenance of the three different characterization will be same.
+
+The point is not that a same thing is referred to differently by
+applications. It is that we take different perspectives on it.
+An egg vs a set of molecules.
+
+ > Further, we can associate the provenance information for (b) with (a)
+ > also, for example reference to imported content? Similarly for (c) and
+ > (b), (a), for example the motivation to write the report or broad team
+ > involved. I am confused regarding the criteria used to state the
+ > particular provenance information can be associated with (a), (b), or
+ > (c).
+
+I don't understand this point.
+
+
+ > In case they are referring to different things (different reports
+ > located at same URL, different version of same report etc.), the
+ > provenance will be different.
+
+But that's not the same, we refer to the same report.
+
+ >
+ > 3. This specification assumes that a partial order exists between
+ > events.
+ >
+ > Issue: Are we excluding overlapping events or events that are
+ > "contained" in other events?
+
+Events are instantaneous. Hence, there is no overlap and
+containment. Two events occurs at the same instant or not.
+
+ >
+ > 4. In our conceptualization of the world, punctual events, or events
+ > for short, happen in the world, which mark changes in the world, in
+ > its activities, and in its things.
+ >
+ > Issue: This definition of event seems to be a specialization of a PE?
+ > What are the distinguishing features (if any) of an event vis-a-vis
+ > PE?
+
+I don't see why they seem to be a specialization. Is it because event duration=0?
+We have four types of events, two of which are start and end of PE.
+So, to me they are very distinct from PE.
+
+ >
+ > Section 3 ===== 1. The wasComplementOf relationship is used to denote
+ > that two entities complement each other, in the sense that they each
+ > represent a partial, but mutually compatible characterization of the
+ > same thing.
+ >
+ > Issue: What does "entity" in the above statement refer to? How can two
+ > entities refer to the same thing - assuming that entity is the term we
+ > agreed to use for "thing"?
+
+Entity is introduced in previous sentence.
+An entity (expression here!) does not refer to a thing, but represents a characterized thing.
+
+Entity is not defined here as thing (in this version of the document).
+
+ >
+ > 2. Qualifiers can be associated to relations, namely use and
+ > wasGeneratedBy, in order to further characterise their nature. Role is
+ > a standard qualifier.
+ >
+ > Issue: Are qualifiers associated with relations only - they can be
+ > associated with entities also to further "characterize" it (and
+ > thereby create specialized entities)? What do we mean by "standard
+ > qualifier"?
+
+Qualifiers are for relations.
+Entities have attributes (characterizing them) (and also annotations)
+
+standard replaced by pre-defined
+
+ >
+ > 2. Attributes, qualifiers, and annotation are the main extensibility
+ > points in the model: individual interest groups are expected to extend
+ > PROV-DM by introducing new sets of attributes, qualifiers, and
+ > annotations as needed to address applications-specific provenance
+ > modelling requirements.
+ >
+ > Issue: Since annotation have no prescribed meaning, how can they be
+ > used to extend the model? What is the difference between attributes
+ > and qualifiers? Qualifiers are standard mechanism for specialization
+ > (either entities or relations) - new attributes may or may not be used
+ > to define specialized entities or relations. For example, a new
+ > attribute stating that a Toyota Corolla car hasMileage 100miles does
+ > not necessarily extend the entity Toyota Corolla car?
+
+Annotations: we have given example of use of annotation, where application
+specific annotations give instructions on how to render provenance.
+
+Attributes are for entities and PEs
+Qualifiers are for relations
+
+There is no concept of "specialized entity" in the model. What do you mean?
+Entity expressions can be complement of other entity expressions
+
+
+ >
+ > Thanks.
+ >
+ > Best, Satya
+ >
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/model/simon-comments.txt Mon Oct 10 12:23:53 2011 +0100
@@ -0,0 +1,457 @@
+>Luc, Paolo,
+>
+>Here's my comments on the current data model document, annotated with
+>(T) for typo/text clarity or (C) for content comment/question. I think
+>most/all comments are small enough that an issue need not be raised.
+>
+>Throughout:
+>(T) Sections are referred to in the text by "Section Entity", "Section
+>Process Execution" etc. Shouldn't these be the section numbers?
+
+TODO when stable
+
+>(T) There seems to be inconsistency in symbols following the change
+>from roles to qualifiers. Sometimes "q" is used in constraint
+>definitions, examples etc. and sometimes "r" is used. I suggest it
+>would be clearer to always use "q".
+
+Done (hopefully everywhere)
+
+>(T) There are a few "characterised" in amongst the majority
+>"characterized" spelling.
+
+Done
+
+>(C) At least one standard qualifier name, "role", is used in the
+>document, but it is not clear what namespace this name is in. Does it
+>mean no other "role"s from domain-specific ontologies may be used in
+>Prov data?
+
+Added section 1.2 explicitly declaring PROV-DM namespace.
++ added that role is declared in that namespace.
+
+>
+>Sec 2.1:
+>(T) paragraph 1: "Words such thing or activity" should be "Words such
+>as 'thing' or 'activity'"
+
+Done
+
+>(C) paragraph 2: The first mention of "provenance" in the document
+>proper is in the second paragraph of this section, and is a bit out of
+>the blue ("unambiguously report provenance"). Can we add some
+>intuition about what provenance is (for this data model)?
+
+
+Now, provenance is introduced in section 1.
+
+
+>(T) Example paragraph 1: "perspectives about a resource" should be
+>"perspectives on a resource"
+
+Done
+
+>(C) Example paragraph 1: "the report independent of where it is hosted
+>over time" - I suggest also saying "and of its content over time", to
+>distinguish this entity from the report version entity above it
+
+Done
+
+===================
+>(C) paragraph 6: "punctual events"? "punctual" as most commonly used
+>implies prior planning of when something should occur. I'm not sure
+>what you are intending in this context.
+
+???? I don't understand
+PM "instantaneous"?
+Luc OK
+===================
+
+===================
+>(C) paragraph 6: "a partial order exists between events". I assume you
+>mean a temporal order? What kind of ordering do you mean?
+
+... partial ;-) .... between events...
+What is the issue?
+
+PM agree, statement seems clear to me.
+it's an order amongst events, not instants in time
+it's partial: you can't always say ev1 before ev2
+
+LUC: No change then
+===================
+
+
+
+===================
+>(C) paragraph 6: "global notion of time and Lamport's style clocks" -
+>this seems like a weirdly specific level of detail for this overview
+>section, especially considering that many other aspects of the model
+>are not mentioned at all in the overview.
+
+Given that time is so critical and the object of several issues, it's
+important to state our assumptions.
+
+PM I think you wrote it correctly, but also that we are not stating any assumptions: you say that this is out of scope, and point to a possible frame of reference. I see no problems
+===================
+
+
+>
+>Sec 2.3:
+>(C) Regarding the note (not attempting to ensure consistency of an
+>asserter) - this seems practical. I'm not sure how we could enforce
+>consistency in any circumstance, only define what it means or say it
+>is application specific.
+
+Rephrased.
+
+>
+>Sec 4.1:
+>(T) "We denote this e1." and the same for e2 etc. It is not entirely
+>clear whether "this" refers to the event or the entity.
+>
+
+TODO
+
+>Sec 4.2:
+>(C) The fact that Alice is the creator of e1 seems to be expressed
+>twice, first as an attribute "creator=Alice", and secondly as the
+>"creator" role of an agent in the creation process. I don't think it
+>is a good idea for either clarity of use of the model or for ensuring
+>interoperability for there to be multiple ways to express the same
+>thing, if it can be at all avoided. Even if we cannot stop someone
+>using either method, can't we say which they *should* use to aid
+>interoperability?
+
+TODO
+
+>(T) "Generation expressions... represent the event at which a file is
+>created". The surrounding text is generic rather than specific to the
+>example, implying this should be "entity" rather than "file",
+>Otherwise, readers may assume that all entities are files or that
+>generation only applies to files.
+
+TODO
+
+>(T) Paragraph on wasComplementOf: in "attribute content" and
+>"attribute spellchecked", fixed width font (or another font) should be
+>used for the attribute names to show they are names, else the sentence
+>can be read in strange ways.
+
+Done.
+
+>
+>Sec 4.3:
+>(T) Fig 1: The arrow from pe2 to a3 is a different direction to the
+>other "agent" links. It is also not clear if an "agent" link is the
+>same as a "wasControlledBy" link. If so, the pe2-a3 arrow direction
+>makes most sense, as the others seem to be saying the agent was
+>controlled by the process execution.
+>
+
+TODO
+
+>Sec 5.1:
+>(T) The last sentence, regarding a "house-keeping construct" is rather
+>opaque. I'm not sure what the reader is supposed to understand from
+>this.
+>
+
+Rewritten
+
+>Sec 5.2.1:
+>(C) First sentence: "entity expression" is given exactly the same
+>definition that "entity" was in Section 4. I think having two terms
+>for the same thing will cause confusion. I like addition of
+>"expressions" to the model in general, though, as I think this greatly
+>clarifies what is intended.
+
+TODO: well the issue is that in the ER diagram, we really talk about Entity Expressions, not Entities?
+Given that we are about to define entity as characterized thing, should the ER diagram change?
+
+>(C) "the meaning of attribute in the context of a process execution
+>expression is similar to the meaning of attribute for entity
+>expression" - I think the meaning should be exactly the same, not just
+>similar, else there will be confusion.
+
+Replaced similar by same, and replaced meaning by interpretation.
+
+
+>(C) Following from the above point: "A process execution expression's
+>attribute remains constant for the duration of the activity" - OK, but
+>does it also characterise the process execution, e.g. is the start
+>time part of what distinguishes one execution from others?
+
+TODO: what if we say that remain constant and characterize the activity.
+What's the implication? What if we don't?
+
+>(T) "noted processExecution" - I think you mean "denoted" (or
+>"written" or "expressed")
+
+Done, replaced by written
+
+>
+>Sec 5.2.3:
+>(T) "representation a characterized thing" - missing "of"
+
+Done
+
+>(T) Last sentence, "On the contrary" should be "On the other hand",
+>and "inferred" should be "infer"
+
+Done
+>
+>Sec 5.2.4:
+>(T) Last sentence: "expectede"
+
+Done
+
+===================
+>Sec 5.3.3.1:
+>(C) I suggest that, as accounts are not introduced until later in the
+>document, the generation-unicity constraint will not make sense here.
+>Moreover, I think the constraint is more about accounts and what it
+>means for them to be consistent than it is about generation events or
+>process executions. Therefore, I suggest moving this constraint to the
+>section on accounts.
+
+
+I am not sure I agree. I think it says a lot about generation, since
+provenance assertions are always in accounts (even if it is a default
+account of the provenance container).
+
+PM: the account is mentioned for accuracy of definition here. If you din't know about accounts, then this would just be correct without qualification.
+So I would leave it as is.
+
+Luc: OK
+===================
+
+
+===================
+>(C) Given that constraint derivation-events applies, don't we just
+>have two ways of saying the same thing? Why use the long form of
+>wasDerivedFrom when the same can be expressed using wasGeneratedBy and
+>used? Which variety *should* be used?
+
+
+It's not an equivalence, it's an implication. We don't have two ways
+of saying the same thing.
+
+PM agree with you but also this set of constraints may come across as odd: there is derivation-use but should there be derviation-generation as well?
+
+Luc: the text below derivation-use says that the symmetric inference does not hold.
+
+also can we put derivation-attributes first: it is the one that defines the meaning of derivation.
+
+Luc: does it also hold for wasEventuallyDerivedFrom? If so, it should even be in 5.3.3.
+===================
+
+>
+>Sec 5.3.3.2:
+>(T?) Constraint "derivation-linked-independent" seems to be a
+>tautology. I guess this is a typo?
+
+Fixed
+
+>
+>Sec 5.3.3.3:
+>(T) Paragraph 4: "In other word" should be "In other words"
+>
+
+Done
+
+>Sec 5.3.4:
+>(C) This section seems to be confusingly expressed, implying that
+>non-agent entities can control executions, whereas the control-agent
+>constraint (in the section on agents) contradicts this. It is probably
+>just a matter of clarifying the text, e.g. if you mean that a
+>non-agent entity can be asserted to be controlling an execution but
+>from this inferred to be an agent.
+
+TODO
+
+===================
+>(T) The text may be read to imply that a control link has only one
+>qualifier, role, whereas I guess you mean that, like use/generate, it
+>can have multiple "modalities" as part of the qualifier?
+
+TODO: what other meaningful qualifier could we use for control?
+
+PM don't kow but for consistency I think we should add them
+
+Luc: I was thinking of properties such as synchronous/asynchronous control. Do they make sense?
+===================
+
+
+===================
+>Sec 5.3.5:
+>(C) I can see this section causing some difficulty... While that may
+>just be the nature of the topic, there seems an important thing
+>missing: what has complementarity got to do with provenance? In other
+>words, what value (with regards to provenance) is there in asserting
+>complementarity?
+
+TODO
+
+PM we discussed this for ages. It should be there. to me this is about a formal definition of how entities can be compared across accounts
+PM there was a lot of noise of changing the term "complement-of" have we ever considered that??
+
+Luc: We should put a note for now.
+===================
+
+>(C) The text suddenly starts talking about "properties" from the
+>second paragraph. What are these, and do they have any relation to
+>attributes?
+
+We had agreed it should be 'attribute(s)'. Text udpated.
+
+
+===================
+>(C) Should the justification of why the complementarity relation is
+>not transitive be in this document? I would expect this document to
+>just state that it is not transitive and, for brevity and simplicity,
+>leave justifications to another document.
+
+At this time, there is no such other document. It also brings intuition.
+So, no change.
+
+
+PM agree, you can't just state it's not transitive. We have had a long discussion on this which indicates that readers would be puzzled if there was no justification
+
+===================
+
+
+>
+>Sec 5.3.6:
+>(C) Similarly to above, I'm not sure the justification of why
+>wasInformedBy is not transitive should be in this document.
+
+Same.
+
+===================
+>Sec 5.3.8:
+>(C) Constraint participation: This seems odd to me. In what
+>circumstances would you not know or want to assert which of the three
+>possibilities (used/controlled/complement) applied for a given entity
+>and execution? Is hadParticipant as defined really useful?
+
+I am not a fan of it. This said, it's one of those "extensions" and
+should probably be moved to section 7.
+
+PM yes. it /is/ odd. but keep in mind that the OWL group is including it
+
+Luc: I think it's intresting for complemenetOF. So you can say that e0 participated in pe1, I think, t in the example.
+===================
+
+>
+>Sec 5.3.9:
+>(C) Grammar definition: I don't understand what the
+>"relationIdentification" stuff is about or what all the identifiers
+>identify.
+
+Grammar revisited. Example extended. Explanation provided.
+Not sure the grammar allows for all forms of relations to be captured.
+
+===================
+>Sec 5.4.1:
+>(C) This appears to be yet another way to say the same thing,
+>following the comment on Sec 4.2 above. If A is an "asserter" of
+>expression E, then we can either (i) express E to be an entity and use
+>an attribute "asserter=E"; (ii) express E to be an entity and A to be
+>an agent playing "role=asserter"; or (iii) put A in the "asserter"
+>slot of an "account" expression containing E. Why do we need all three
+>ways? Isn't method (ii) most consistent with the rest of the model?
+
+
+If the WG support the idea that the asserter should be an agent, that
+we'll go for it.
+
+PM just leave the note there
+===================
+
+>
+>Sec 5.4.2:
+>(T) Second sentence: "return all the provenance assertions" - all the
+>assertions? or just "all the assertions in the container"?
+
+.. to return assertions. Changed.
+
+>(C) Under the definition given, you cannot have expressions in a
+>container but not in an account. Does this imply that every Prov
+>expression is made accessible as part of an account? I think this
+>would be a good thing for clarity, but it is not explicit in the
+>document (and also differs from OPM).
+
+Added sentence: Consequently, every provenance expression is always
+expressed in the context of an account, either explicitly in an
+asserted account, or implicitly in a container's default account.
+
+>
+>Section 5.5.1:
+>(C) I agree with the first note. If it is mandatory to say something
+>but that what we say can be nothing, that means that it is not
+>mandatory at all. The "mandatory" thing seems to be just saying
+>something about the ASN, and so is irrelevant as the ASN is just there
+>to make the model concrete and readable.
+
+TODO: should we change to MAY contain a qualifier. A qualifier is a non empty sequence ...
+
+>
+>Sec 5.5.4:
+>(C) Second note: Wouldn't this mean that either account IDs or entity
+>IDs can never be URIs, as a sequence of URIs would itself not be a
+>URI? If so, that seems to make RDF serialisation difficult to achieve.
+
+TODO.
+
+Why do we need to have a URI for a qualified identifier?
+
+Why would this make serialization to RDF difficult. We are proposing for
+a qualified identifier to be only usable in wasComplementOf.
+
+
+>
+>Sec 5.5.6:
+>(C) I don't see the connection between the section's introductory text
+>and the content of the subsections.
+
+TODO. It's unclear where this content should go.
+
+>
+>Sec 5.7.1:
+>(C) I think this section needs something introductory to say why it is
+>relevant to the data model, i.e. what has it to do with provenance,
+>why is it useful in the context of provenance, why is it standardised
+>rather than application-specific?
+
+TODO.(now 7.1)
+
+>(C) If my record of what occurred does not start with an empty
+>container, but one with contents, how do I say that the elements are
+>part of the container? Do I have to model this as a series of
+>wasAddedTo links, even if I know nothing about how the elements were
+>added? Or is it out of scope of the standard?
+
+
+TODO: macro expand ...
+
+>
+>Sec 5.7.2:
+>(C) I don't see how wasQuoteOf is a sub-relation of wasRevisionOf, or
+>wasAttributedTo a sub-relation of wasEventuallyDerivedFrom, when the
+>super-relations do not contain reference to any agents but the
+>sub-relations do. What does it mean?
+
+TODO: all section needs updating.
+
+
+>(T) Last sentence of 5.7.2.2: "wasQuoteOf" should be "wasAttributedTo"
+
+TODO
+
+>
+>Thanks,
+>Simon
+>
+>-- Dr Simon Miles Lecturer, Department of Informatics Kings College London, WC2R 2LS, UK +44 (0)20 7848 1166
+>
--- a/ontology/ProvenanceFormalModel.html Mon Oct 10 12:23:09 2011 +0100
+++ b/ontology/ProvenanceFormalModel.html Mon Oct 10 12:23:53 2011 +0100
@@ -36,14 +36,14 @@
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "ED",
+ specStatus: "FPWD",
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "PROV-FormalModel",
// if your specification has a subtitle that goes below the main
// formal title, define it here
- subtitle : "Initial draft for internal discussion",
+ //subtitle : "",
// if you wish the publication date to be other than today, set this
// publishDate: "2009-08-06",
@@ -58,7 +58,7 @@
// previousMaturity: "WD",
// if there a publicly available Editor's Draft, this is the link
- edDraftURI: "http://www.w3.org/2011/prov/wiki/D1--NOT-YET-AVAILABLE",
+ edDraftURI: "http://www.w3.org/TR/2011/WD-PROV-FormalModel-20111007/", // http://www.w3.org/2011/prov/wiki/D1--NOT-YET-AVAILABLE",
// if this is a LCWD, uncomment and set the end of its review period
// lcEnd: "2009-08-05",
@@ -72,7 +72,7 @@
editors: [
{ name: "Satya Sahoo", url: "http://cci.case.edu/cci/index.php/Satya_Sahoo",
company: "Case Western Reserve University, USA" },
- { name: "Deborah McGuinness", url: "http://www.cs.rpi.edu/~dlm/",
+ { name: "Deborah McGuinness", url: "http://tw.rpi.edu/instances/Deborah_L_McGuinness",
company: "Rensselaer Polytechnic Institute, USA" }
],
@@ -90,8 +90,8 @@
{ name: "Daniel Garijo",
url:"http://www.oeg-upm.net/index.php/en/phdstudents/28-dgarijo",
company: "Universidad Politécnica de Madrid, Spain" },
- { name: "Tim Lebo",
- url:"http://tw.rpi.edu/web/person/TimLebo",
+ { name: "Timothy Lebo",
+ url:"http://tw.rpi.edu/instances/TimLebo",
company: "Rensselaer Polytechnic Institute, USA" },
{ name: "Stian Soiland-Reyes",
url:"http://soiland-reyes.com/stian/",
@@ -120,10 +120,15 @@
</script>
</head>
<body>
+
<section id='abstract'>
<p> The PROV Ontology Model (also PROV ontology) encodes the PROV Data Model [[PROV-DM]] in the OWL2 Web Ontology Language (OWL2). The PROV ontology consists of a set of classes, properties, and restrictions that can be used to represent provenance information. The PROV ontology is specialized to create domain-specific provenance ontologies that model the provenance information specific to different applications. The PROV ontology supports a set of entailments based on OWL2 formal semantics and provenance specific inference rules. The PROV ontology is available for download as a separate OWL2 document.</p>
</section>
-
+
+<section id='sotd'>
+<p>TODO: MUST include at least one customized paragraph. This section SHOULD include the title page date (i.e., the one next to the maturity level at the top of the document). These paragraphs SHOULD explain the publication context, including rationale and relationships to other work. See examples and more discussion in the Manual of Style.<a href="http://www.w3.org/2001/06/manual/#Status">TODO</a></p>
+</section>
+
<section>
<h2>Introduction</h2>
<p>
@@ -139,6 +144,7 @@
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
[[!RFC2119]].</p>
+
<section>
<h3>Guide to this Document</h3>
<p> This document is intended for provide an understanding of the PROV ontology and how it can be used by various applications to represent their provenance information. The intended audience of this document include users who are new to provenance modeling as well experienced users who would like their provenance model compatible with the PROV ontology to facilitate standardization.This document assumes a basic understanding of the W3C OWL2 specification , including modeling of classes, properties, and restrictions in an OWL2 ontology. Readers are referred to the OWL2 documentations, starting with the [[!OWL2-PRIMER]], for the OWL2 specification.
@@ -146,7 +152,11 @@
<p><a href="#prov-ontology--owl-encoding-of-prov-data-model">Section 2</a> describes the mapping of the PROV Data Model [[PROV-DM]] to the PROV ontology. <a href="#specializing-provenance-ontology-for-domain-specific-provenance-applications">Section 3</a> introduces the classes and properties of the PROV ontology. <a href="#specializing-provenance-ontology-for-domain-specific-provenance-applications">Section 4</a> describes the approach used to specialize the PROV ontology create a domain specific ontology for an example <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance scenario</a> introduced in the PROV Data Model [[PROV-DM]]. The PROV ontology supports a set of provenance entailments and these are described in <a href="#entailments-supported-by-the-provenance-model">Section 5</a>.
</p>
</section>
- </section>
+
+ </section> <!-- Introduction -->
+
+
+
<section>
<h2>PROV Ontology</h2>
<p> The PROV Data Model [[PROV-DM]] introduces a minimal set of concepts to represent provenance information in a variety of application domains. This document maps the PROV Data Model to PROV Ontology using the OWL2 ontology language, which facilitates a fixed interpretation and use of the PROV Data Model concepts based on the formal semantics of OWL2 [[!OWL2-DIRECT-SEMANTICS]] [[!OWL2-RDF-BASED-SEMANTICS]].
@@ -155,12 +165,17 @@
</p>
<p>The PROV Data Model document [[PROV-DM]] introduces an example <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> describing the creation of crime statistics file stored on a shared file system and edited by journalists Alice, Bob, Charles, David, and Edith. This scenario is used as a running example in this document to describe the PROV ontology classes and properties, the specialization mechanism and entailments supported by the PROV ontology.
</p>
+
+
+
<section>
<h3>OWL2 Syntax Used in this Document</h3>
<p>We use the RDF/XML syntax, which is the mandatory syntax supported by all OWL2 syntax [[!OWL2-PRIMER]] to represent the PROV ontology. The OWL2 document for the PROV ontology is available at [[PROV-Ontology-Namespace]], which is also the default namespace for PROV ontology and is denoted by "PROV".
</p>
</section>
- </section>
+ </section> <!-- PROV Ontology -->
+
+
<section>
<h2>PROV Ontology: Classes and Properties</h2>
<p> We now introduce the classes and properties that constitute the PROV ontology. We first give a textual description of each ontology term, followed by OWL2 syntax representing the ontology term and an example use of the term in the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance scenario</a>.
@@ -170,8 +185,9 @@
<p>The PROV ontology consists of seven classes that can be organized in a taxonomic structure.
</p>
<img src="diagram-history/khalidDiagrams/Ontology_hierarchy.png"
- style="width: 50%; min-width: 25em; max-width: 37em" /><br>
- <p/>
+ style="width: 50%; min-width: 25em; max-width: 37em"
+ alt="Class hierarchy of the PROV OWL ontology"/>
+ <br>
<p><i>Note: CamelBack notation is used for class names</i></p>
<section>
<h4>Entity</h4>
@@ -194,7 +210,8 @@
<div class='issue'>How is domain specific data combined with the provenance model? This is <a href="http://www.w3.org/2011/prov/track/issues/65">ISSUE-65</a>.</div>
<div class='issue'>Definition of Entity is confusing, maybe over-complex <a href="http://www.w3.org/2011/prov/track/issues/85">ISSUE-85</a>.</div>
- </section>
+ </section> <!-- Classes -->
+
<section>
<h4>ProcessExecution</h4>
<div><b>Class Description</b></div>
@@ -213,6 +230,9 @@
<div class='note'> pe2 is an instance of class EmailProcessExecution, which is defined to be "sub-class" of class ProcessExecution in the CrimeFile ontology. Hence, using standard RDFS entailment allows us to infer that pe2 is also an instance of ProcessExecution.
</div>
</section>
+
+
+
<section>
<h4>Agent</h4>
<div><b>Class Description</b></div>
@@ -231,6 +251,9 @@
<div class='note'> Similar to example for Entity, both Alice and Edith are instances of class Journalist, which is defined to be "sub-class" of class Agent in the CrimeFile ontology. Hence, using standard RDFS entailment allows us to infer that both Alice and Edith are also instances of Agent.
</div>
</section>
+
+
+
<section>
<h4>Recipe</h4>
<div><b>Class Description</b></div>
@@ -240,6 +263,9 @@
<div><b>Example</b></div>
<p> Recipe examples include backing recipes, programs and workflows.
</section>
+
+
+
<section>
<h4>Time</h4>
<div><b>Class Description</b></div>
@@ -256,6 +282,9 @@
</pre>
</div>
</section>
+
+
+
<section>
<h4>Revision</h4>
<div><b>Class Description</b></div>
@@ -264,6 +293,9 @@
<pre>PROV:Revision rdfs:subClassOf owl:Thing.</pre>
<div class='issue'>Revision should be a class not a property. This is <a href="http://www.w3.org/2011/prov/track/issues/48">ISSUE-48</a>.</div>
</section>
+
+
+
<section>
<h4>ProvenanceContainer</h4>
<div><b>Class Description</b></div>
@@ -276,6 +308,9 @@
<div class='issue'>Asserter needs to be defined. This is <a href="http://www.w3.org/2011/prov/track/issues/51">ISSUE-51</a>.</div>
<div class='issue'>Scope and Identifiers. This is <a href="http://www.w3.org/2011/prov/track/issues/81">ISSUE-81</a>.</div>
</section>
+
+
+
<section>
<h4>Location</h4>
<div><b>Class Description</b></div>
@@ -295,6 +330,9 @@
</div>
<div class='note'> Need to clarify whether "geographic" includes "geospatial"?</div>
</section>
+
+
+
<section>
<h4>EntityInRole</h4>
<div><b>Class Description</b></div>
@@ -313,17 +351,25 @@
</pre>
</div>
</section>
+
+
+
<div class='issue'>The PROV-DM defines the term <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-qualifier">Qualifier</a>, which is incorporated implicitly in definition of OWL sub-classes and sub-properties that specialize a parent class or property by defining additional qualifying constraints. Hence, <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-qualifier">Qualifier</a> is not modeled explicitly in PROV ontology.</div>
</section>
+
+
<section>
<h3>Object Properties</h3>
<p>The Provenance Model consists of the following object properties. </p>
<p><i>Note: Names of properties starts with a verb in lower case followed by verb(s) starting with upper case </i></p>
+
+
+
<section>
<h4>wasGeneratedBy</h4>
<p>wasGeneratedBy links Entity with ProcessExecution representing that Entity was generated as a result of ProcessExecution</p>
<p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
- <img src="http://www.w3.org/2011/prov/wiki/images/b/b4/WasGeneratedBy.png" />
+ <img src="http://www.w3.org/2011/prov/wiki/images/b/b4/WasGeneratedBy.png" alt="wasGeneratedBy links Entity to ProcessExecution" />
<div><b>Example</b></div>
<p> Example of wasGeneratedBy property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>e1 wasGeneratedBy pe0</i>. The RDF/XML syntax for asserting this is given below.
<div class="exampleOuter">
@@ -341,10 +387,13 @@
</pre>
</div>
</section>
+
+
+
<section>
<h4>wasDerivedFrom</h4>
<p>wasDerivedFrom links two distinct characterized entities, where "some characterized entity is transformed from, created from, or affected by another characterized entity."</p>
- <img src="http://www.w3.org/2011/prov/wiki/images/3/34/WasDerivedFrom.png" />
+ <img src="http://www.w3.org/2011/prov/wiki/images/3/34/WasDerivedFrom.png" alt="wasDerivedFrom links Entity to Entity"/>
<div><b>Example</b></div>
<p> Example of wasDerivedFrom property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>e3 wasDerivedFrom e2</i>. The RDF/XML syntax for asserting this is given below.
<div class="exampleOuter">
@@ -357,11 +406,14 @@
<div class='issue'>Should derivation have a time? Which time? This is <a href="http://www.w3.org/2011/prov/track/issues/43">ISSUE-43</a>.</div>
<div class='issue'>Should we specifically mention derivation of agents? This is <a href="http://www.w3.org/2011/prov/track/issues/42">ISSUE-42</a>.</div>
</section>
+
+
+
<section>
<h4>Used</h4>
<p>Used links ProcessExecution to Entity, where Entity is consumed by ProcessExecution.</p>
<p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
- <img src="http://www.w3.org/2011/prov/wiki/images/2/2f/Used.png" />
+ <img src="http://www.w3.org/2011/prov/wiki/images/2/2f/Used.png" alt="prov:used links ProcessExecution to Entity"/>
<div class='issue'>Should we define a taxonomy of use? This is <a href="http://www.w3.org/2011/prov/track/issues/23">ISSUE-23</a>.</div>
<div><b>Example</b></div>
<p> Example of Used property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>pe2 Used e2</i>. The RDF/XML syntax for asserting this is given below.</p>
@@ -373,20 +425,30 @@
</pre>
</div>
</section>
+
+
+
+
<section>
<h4>hadParticipant</h4>
<p>hadPariticipant links Entity to ProcessExecution, where Entity used or wasGeneratedBy ProcessExecution.
<p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
<div class='pending'>Suggested definition for participation. This is <a href="http://www.w3.org/2011/prov/track/issues/49">ISSUE-49</a>.</div>
</section>
+
+
+
<section>
<h4>wasComplementOf</h4>
<p>wasComplementOf links two instances of Entity, where "it is relationship between two characterized entities asserted to have compatible characterization over some continuous time interval." <i>(from the Provenance Conceptual Model)</i></p>
</section>
+
+
+
<section>
<h4>wasControlledBy</h4>
<p>wasControlledBy links ProcessExecution to Agent, where "Control represents the involvement of an agent or a Entity in a process execution"<i>(from the Provenance Conceptual Model)</i></p>
- <img src="http://www.w3.org/2011/prov/wiki/images/2/2f/WasControlledBy.png" />
+ <img src="http://www.w3.org/2011/prov/wiki/images/2/2f/WasControlledBy.png" alt="wasControlledBy links ProcessExecution to Agent"/>
<div><b>Example</b></div>
<p> Example of wasControlledBy property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>FileAppending</i> (ProcessExecution) <i>wasControlledBy Bob</i>. The RDF/XML syntax for asserting this is given below.
<div class="exampleOuter">
@@ -405,6 +467,9 @@
<div class='issue'>Is ivpOf transitive? This is <a href="http://www.w3.org/2011/prov/track/issues/45">ISSUE-45</a></div>
<div class='issue'> Comments on ivpof in <a href="http://www.w3.org/2011/prov/track/issues/57">ISSUE-57</a>.</div>
</section>
+
+
+
<section>
<h4>hadRecipe</h4>
<p>The ProcessExecution activity performed can be described as
@@ -413,23 +478,26 @@
might or might not have been followed exactly by the Process
Execution.
</p>
- <img
- src="http://www.w3.org/2011/prov/wiki/images/2/22/HadRecipe.png" />
+ <img src="http://www.w3.org/2011/prov/wiki/images/2/22/HadRecipe.png" alt="prov:hadRecipe links ProcessExecution to Recipe."/>
</section>
- <section>
+
+
+
+ <section>
<h4>wasInformedBy</h4>
<p> This object property links two process executions. It is used to express the fact that a given process execution used an entity that was generated by another process execution.
</p>
- <img
- src="http://www.w3.org/2011/prov/wiki/images/0/08/WasInformedBy.png" />
+ <img src="http://www.w3.org/2011/prov/wiki/images/0/08/WasInformedBy.png" alt="prov:wasInformedBy links ProcessExecution to ProcessExecution"/>
</section>
- <section>
+
+
+
+ <section>
<h4>wasScheduledAfter</h4>
<p>
This object property links two instances of ProcessExecution to specify the order in which they took place. Specifically, it is used to specify that a given process execution starts after the end of another process execution.
</p>
- <img
- src="http://www.w3.org/2011/prov/wiki/images/b/b5/WasScheduledAfter.png" />
+ <img src="http://www.w3.org/2011/prov/wiki/images/b/b5/WasScheduledAfter.png" alt="prov:wasScheduledAfter links ProcessExecution to ProcessExecution"/>
</section>
<section>
<h3>Characteristics of Object Properties </h3>
@@ -479,7 +547,6 @@
</td><td style="border-style: solid; border-width: 0 1px 1px 0">Yes
</td></tr>
<tr>
- <tr>
<td style="border-style: solid; border-width: 0 1px 1px 0"> wasGeneratedBy
</td><td style="border-style: solid; border-width: 0 1px 1px 0">Yes
</td><td style="border-style: solid; border-width: 0 1px 1px 0">No
@@ -524,9 +591,10 @@
</div>
</section>
</section>
+
<section>
<h3>Annotation Properties</h3>
- <p>The PROV ontology uses the OWL2 annotation properties to describe additional information about the PROV ontology classes, properties, individuals, and axioms. OWL2 defines nine annotation properties that are part of the OWL2 structural specification (see OWL2 Syntax document for additional details [[!OWL2-SYNTAX]]):
+ <p>The PROV ontology uses the OWL2 annotation properties to describe additional information about the PROV ontology classes, properties, individuals, and axioms. OWL2 defines nine annotation properties that are part of the OWL2 structural specification (see OWL2 Syntax document for additional details [[!OWL2-SYNTAX]]):</p>
<ul>
<li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>rdfs:label</b></a>- This property is used to associated a "human-readable label" with a term. For example, the class "<a href="#location">Location</a>" can be annotated with "Geo-spatial Location" label using rdfs:label</li>
<li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>rdfs:comment</b></a>- This property is used to annotate ontology terms with a readable comment. For example, the class "<a href="#location">Location</a>" can be annotated with "This class represents an identifiable geographic place (ISO 19112)" comment using the rdfs:comment property</li>
@@ -538,38 +606,44 @@
<li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>owl:backwardCompatibleWith</b></a>- Provenance ontologies can specify previous version of the ontology that are compatible with the current version of the ontology using this property</li>
<li><a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Annotation_Properties"><b>owl:incompatibleWith</b></a>- Similar to the previous property, this property allows provenance applications to identify incompatible version of provenance ontologies.</li>
</ul>
- Additional annotation properties can be defined by provenance ontologies, but unlike the OWL2 annotation properties, these custom annotation properties may not be interpreted in a standard manner across different provenance applications.
+ <p>Additional annotation properties can be defined by provenance ontologies, but unlike the OWL2 annotation properties, these custom annotation properties may not be interpreted in a standard manner across different provenance applications.
</p>
<div class='note'> Is there a need to define standard provenance-specific annotation properties?
</div>
</section>
+
<section>
<h3>Overview of the ontology</h3>
<p>The following diagram illustrates the complete PROV ontology schema along with the cardinality restrictions imposed on the properties. </p>
- <img src="http://www.w3.org/2011/prov/wiki/images/9/9a/Object_Properties_overall_diagram.png" />
-
+ <img src="http://www.w3.org/2011/prov/wiki/images/9/9a/Object_Properties_overall_diagram.png" alt="Object properties among all classes in the PROV OWL ontology"/>
+ <a href="http://dvcs.w3.org/hg/prov/raw-file/34a479f3f5d0/ontology/diagram-history/2011-10-03-tlebo/ProvenanceOntology.owl.pdf"><img src="http://dvcs.w3.org/hg/prov/raw-file/34a479f3f5d0/ontology/diagram-history/2011-10-03-tlebo/ProvenanceOntology.owl.png" alt="Object properties among all classes in the PROV OWL ontology"/></a>
</section>
+
</section>
+
+
<section>
<h2>Specializing Provenance Ontology for Domain-specific Provenance Applications</h2>
- <p>The PROV Ontology is conceived as a reference ontology that can be extended by various domain-specific applications to model the required set of provenance terms. The PROv Ontology classes and properties can be specialized using the following two RDFS properties:
- <ul>
- <li>rdfs:subClassOf: The property rdfs:subClassOf is an instance of rdf:Property that is used to state that all the instances of one class are instances of another. [RDFS-Ref]</li>
- <li>rdfs:subPropertyOf: "A rdfs:subPropertyOf axiom defines that the property is a subproperty of some other property." [OWL-Ref]</li>
- </ul>
- To illustrate the specialization mechanism, the PROV Ontology is extended to create an ontology schema for the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance scenario</a> describing the creation of the crime statistics file. </p>
+ <p>The PROV Ontology is conceived as a reference ontology that can be extended by various domain-specific applications to model the required set of provenance terms. The PROv Ontology classes and properties can be specialized using the following two RDFS properties:</p>
+ <ul>
+ <li>rdfs:subClassOf: The property rdfs:subClassOf is an instance of rdf:Property that is used to state that all the instances of one class are instances of another. [RDFS-Ref]</li>
+ <li>rdfs:subPropertyOf: "A rdfs:subPropertyOf axiom defines that the property is a subproperty of some other property." [OWL-Ref]</li>
+ </ul>
+ <p>To illustrate the specialization mechanism, the PROV Ontology is extended to create an ontology schema for the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario">provenance scenario</a> describing the creation of the crime statistics file. </p>
+
+
+
<section>
<h3>Modeling the Crime File Scenario</h3>
<p>The example scenario can be encoded as a <a href = "http://www.w3.org/TR/rdf-primer/"> Resource Description Framework (RDF) </a> graph in <a href = "">Figure X</a>:</p>
<div class='issue'>insert figure X</div>
- <p><a href = "">Figure X</a> represents the ontology schema that extends the PROV ontology to model the provenance details of the crime file scenario. For example,
+ <p><a href = "">Figure X</a> represents the ontology schema that extends the PROV ontology to model the provenance details of the crime file scenario. For example,</p>
<ul>
<li>specialization of <a href="#agent">Agent</a> to define a class called Journalist, which has individuals such as alice, bob, and edith </li>
<li><a href="#processexecution">ProcessExecution</a>, e.g. FileCreation, FileAppending, and FileEditing </li>
<li>specialization of <a href="#entity">Entity</a> to define a class called CrimeFile, which has individuals such as e1, e2, and e3 </li>
</ul>
- </p>
- <p>Example given below describes the provenance of <a href="#entity">Entity</a> e2 using RDF/XML syntax
+ <p>Example given below describes the provenance of <a href="#entity">Entity</a> e2 using RDF/XML syntax</p>
<div class="exampleOuter">
<pre class="example">
<?xml version="1.0"?>
@@ -609,7 +683,6 @@
</rdf:RDF>
</pre>
</div>
- </p>
<section>
<h4>Specialization of PROV Ontology Classes</h4>
<p> The following new classes were created in the CrimeFile Ontology by extending the PROV ontology classes:</p>
@@ -647,10 +720,10 @@
</pre>
</div>
<p>The following diagram illustrates the above specialization: </p>
- <img src="http://www.w3.org/2011/prov/wiki/images/5/5d/AlternativeSchema.png"/>
+ <img src="http://www.w3.org/2011/prov/wiki/images/5/5d/AlternativeSchema.png" alt="New classes (cf:SpellChecking, cf:FileEditing, cf:FileCreation, cf:FileAppending, cf:EmailProcessExecution, cf:Journalist) extend the classes in the PROV OWL Ontology (Entity, Agent, ProcessExecution)."/>
+ <a href="http://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.classes.pdf"><img src="http://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.classes.png" alt="New classes (cf:SpellChecking, cf:FileEditing, cf:FileCreation, cf:FileAppending, cf:EmailProcessExecution, cf:Journalist) extend the classes in the PROV OWL Ontology (Entity, Agent, ProcessExecution)."/></a>
<br>
<em>Example extension of PROV ontology in order to describe the crime file scenario</em>
- </p>
</section>
</section>
<section>
@@ -668,12 +741,12 @@
</div>
</section>
<p>The following diagram illustrates the above specialization: </p>
- <a href="http://dvcs.w3.org/hg/prov/raw-file/4504a7462bd9/ontology/examples/ontology-extensions/crime-file/crime.owl.pdf">
- <img src="http://dvcs.w3.org/hg/prov/raw-file/4504a7462bd9/ontology/examples/ontology-extensions/crime-file/crime.owl.png"/>
+ <a href="http://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.properties.pdf">
+ <img src="http://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.properties.png"
+ alt="ext:FileCreation, ext:FileAppending, ext:FileEditing, ext:EmailProcessExecution, extSpellChecking extend prov:ProcessExecution; ext:Journalist extends prov:Agent; ext:CrimeFile extends prov:Entity; ext:hadFilePath extends prov:hadLocation and has range prov:Location."/>
</a>
<br>
<em>Example extension of PROV ontology in order to describe the crime file scenario</em>
- </p>
</section>
</section>
<section>
@@ -709,7 +782,9 @@
<p>
<img
src="examples/ontology-extensions/workflow/workflowOntology.png"
- style="width: 60%; min-width: 20em; max-width: 40em" /><br>
+ style="width: 60%; min-width: 20em; max-width: 40em"
+ alt="New classes wf:WorkFlowEngine, wf:Process, wf:ValueAtPort, wf:FileValue, and wf:Value extend prov:Agent, prov:ProcessExecution, prov:EntityInRole. New properties wf:wasLaunchedBy, wf:ranInWorkflowEngine, wf:wasSubProcessExecutionOf, wf:wasReadFrom, wf:sawValue extend prov:wasControlledBy, prov:wasDerivedFrom." />
+ <br>
<em>Example extension of PROV ontology in order to describe
workflow provenance</em>
</p>
@@ -935,7 +1010,8 @@
</section>
<section>
<h4>Example workflow</h4>
- <img src="http://www.w3.org/2011/prov/wiki/images/5/56/Concatsha1.png" />
+ <img src="http://www.w3.org/2011/prov/wiki/images/5/56/Concatsha1.png"
+ alt="An example workflow with input, three processes, and two outputs." />
<p>This is an example workflow which defines a workflow
input <i>input</i>, three processes <i>String_constant</i>,
<i>Concatenate_two_strings</i> and <i>sha1</i>, and finally
@@ -1173,13 +1249,15 @@
</section>
<section>
<h2>Formal Semantics of the PROV Ontology</h2>
- <p>The PROV ontology uses OWL2 as the ontology language, hence it supports a set of entailments based on the standard RDF semantics [[!RDF-MT]] and OWL2 semantics ([[!OWL2-DIRECT-SEMANTICS]], [[!OWL2-RDF-BASED-SEMANTICS]]). In this section, we describe these set of semantics as applied to the PROV ontology along with a set of constraints introduced in the PROV-DM [[PROV-DM]] that are provenance-specific. It is intended that provenance applications can leverage this normative description of the formal semantics of PROV ontology to support:
+ <p>The PROV ontology uses OWL2 as the ontology language, hence it supports a set of entailments based on the standard RDF semantics [[!RDF-MT]] and OWL2 semantics ([[!OWL2-DIRECT-SEMANTICS]], [[!OWL2-RDF-BASED-SEMANTICS]]). In this section, we describe these set of semantics as applied to the PROV ontology along with a set of constraints introduced in the PROV-DM [[PROV-DM]] that are provenance-specific. It is intended that provenance applications can leverage this normative description of the formal semantics of PROV ontology to support:</p>
<ul>
<li><b>Automated consistency checking </b>of provenance assertions (in RDF): Any RDF graph generated to represent provenance information using the PROV ontology as schema can be automatically checked for consistency using reasoning tool, such as FaCT++, Pellet, and Racer among others.</li>
<li><b>Inferencing</b>: Make implicit knowledge explicit from RDF-encoded provenance datasets using valid entailment rules</li>
</ul>
- </p>
- <section>
+
+
+
+ <section>
<h3>RDF Semantics for PROV Ontology</h3>
<p> We briefly summarize the essential features of the RDF Semantics and refer to the RDF semantics [[!RDF-MT]] for the normative specification. The RDF Semantics uses model theory, with a notion of interpretation I defined over RDF (rdf-interpretation) or RDFS (rdfs-interpretation) vocabulary, for specifying the formal semantics of a RDF or RDFS graph [[!RDF-MT]]. The rdf-interpretation is an interpretation that satisfies a set of constraints called "<i>RDF semantic conditions</i>" and a set of "<i>RDF axiomatic triples</i>" (see Section 3.1 of RDF Semantics [[!RDF-MT]]). The rdfs-interpretation is defined over the additional terms in the RDFS vocabulary, including <i>rdfs:domain</i>, <i>rdfs:range</i>, <i>rdfs:Class</i>, <i>rdfs:subClassOf</i>, and <i>rdfs:subPropertyOf</i>. An rdfs-interpretation satisfies a set of constraints called "<i>RDFS semantic conditions</i>" and "<i>RDFS axiomatic triples</i>" (see Section 4.1 of RDFS Semantics [[!RDF-MT]]).
</p>
@@ -1229,6 +1307,9 @@
</pre>
</div>
</section>
+
+
+
<section>
<h3>OWL2 Semantics for PROV Ontology</h3>
<p>In addition to RDF Semantics, the OWL2 semantics as described in [[!OWL2-DIRECT-SEMANTICS]], [[!OWL2-RDF-BASED-SEMANTICS]] are also applicable to PROV ontology. We consider the OWL2 RDF-Based Semantics (since it is a semantics superset of OWL2 Direct Semantics) and specifically the extension of the D-interpretation, which satisfies the constraints for rdf-interpretation, rdfs-interpretation (as defined in previous section), graphs with blank nodes, and interpretation defined for RDF datatypes (see Section 5.1 in RDF Semantics [[!RDF-MT]]). The OWL2 RDF-based semantics introduces the notion of "facets" to constrain datatypes, both the rdf:XMLLiteral defined in the RDF Semantics [[!RDF-MT]] and datatypes defined in the OWL2 Structural Specifications [[!OWL2-SYNTAX]]. The OWL2 RDF-based interpretation, also called <b>D-interpretation with facets</b> is a D-interpretation that also satisfies the OWL2 RDF-based semantics called "semantic constraints" (see Section 5 in OWL2 RDF-Based Semantics [[!OWL2-RDF-BASED-SEMANTICS]]).
@@ -1236,75 +1317,92 @@
</section>
<section>
<h3>Provenance-specific Entailments Supported by PROV Ontology</h3>
- <p>The PROV-DM [[PROV-DM]] introduces a set of specific constraints applicable to PROV ontology. The following is a list of constraints that will be supported by the PROV ontology and any provenance application that uses the PROV ontology.
-<ul><li> <a name="PROV:0001" href="#PROV:0001">PROV:0001</a> "From the
- assertion of a process execution, one can infer that the start
- precedes the end of the represented activity." (<a href="../model/ProvenanceModel.html#PROV:0001">link</a>)
-</li><li> <a name="PROV:0002" href="#PROV:0002">PROV:0002</a> "Given a process execution <b>pe</b>, entity <b>e</b>, role <b>r</b>, and optional time <b>t</b>,
-if the assertion <b>wasGeneratedBy(e,pe,r)</b>
-or <b>wasGeneratedBy(e,pe,r,t)</b> holds, the values of <em>some</em> of <b>e</b>'s
-attributes are determined by the activity denoted by <b>pe</b> and the
-entities used by <b>pe</b>.
-Only some (possibly none) of the attributes values may be determined
-since, in an open world, not all used entities may have been
-asserted."
- (<a href="../model/ProvenanceModel.html#PROV:0002">link</a>)
-</li><li><a name="PROV:0003" href="#PROV:0003">PROV:0003</a> "Given an assertion <b>wasGeneratedBy(x,pe,r)</b> or <b>wasGeneratedBy(x,pe,r,t)</b>, one can
+ <p>The PROV-DM [[PROV-DM]] introduces a set of specific constraints applicable to PROV ontology. The following is a list of constraints that will be supported by the PROV ontology and any provenance application that uses the PROV ontology.</p>
+ <section>
+ <h4>Provenance constraint on ProcessExecution</h4>
+ <p>The PROV-DM describes a constraint on ordering of time (or event) associated with a <a href="#processexecution">ProcessExecution.</a> </p>
+ <div class='issue'>"From a process execution expression, one can infer that the start event precedes the end event of the represented activity." This is <a href="http://www.w3.org/2011/prov/track/issues/121">ISSUE-121</a></div>
+ </section>
+ <section>
+ <h4>Provenance constraint on wasGeneratedBy</h4>
+ <p>The PROV-DM describes a constraint on wasGeneratedBy that associates the values of attributes of an Entity with the ProcessExecution that generated the Entity.</p>
+ <div class='issue'>"Given a process execution pe, entity e, role r, and optional time t, if the assertion wasGeneratedBy(e,pe,r) or wasGeneratedBy(e,pe,r,t) holds, the values of some of e's attributes are determined by the activity denoted by pe and the entities used by pe. Only some (possibly none) of the attributes values may be determined since, in an open world, not all used entities may have been asserted." This is <a href="http://www.w3.org/2011/prov/track/issues/122">ISSUE-122</a></div>
+ </section>
+ <section>
+ <h4>Provenance constraint on wasGeneratedBy (II)</h4>
+ <p></p>
+ <div class='issue'>"Given an assertion wasGeneratedBy(x,pe,r) or wasGeneratedBy(x,pe,r,t), one can infer that the generation of the thing denoted by x precedes the end of pe and follows the beginning of pe." This is <a href="http://www.w3.org/2011/prov/track/issues/122">ISSUE-122</a></div>
+ </section>
+<li><a name="PROV:0003" href="#PROV:0003">PROV:0003</a> "Given an assertion <b>wasGeneratedBy(x,pe,r)</b> or <b>wasGeneratedBy(x,pe,r,t)</b>, one can
infer that the generation of the thing denoted by <b>x</b> precedes the end
of <b>pe</b> and follows the beginning of <b>pe</b> "
(<a href="../model/ProvenanceModel.html#PROV:0003">link</a>)
+</li>
-</li><li><a name="PROV:0004" href="#PROV:0004">PROV:0004</a> "Use
-represents the consumption of a characterized entity by an activity."
-(Defunct.)
-
-</li><li><a name="PROV:0005" href="#PROV:0005">PROV:0005</a> "Given a process execution <b>pe</b>, entity <b>e</b>, role <b>r</b>, and optional time <b>t</b>, if
+<li><a name="PROV:0005" href="#PROV:0005">PROV:0005</a> "Given a process execution <b>pe</b>, entity <b>e</b>, role <b>r</b>, and optional time <b>t</b>, if
assertion <b>used(pe,e,r)</b> or <b>used(pe,e,r,t)</b> holds,
the existence of the value of an attribute of <b>e</b>' is a pre-condition for the activity denoted by <b>pe</b> to terminate." (<a href="../model/ProvenanceModel.html#PROV:0005">link</a>)
-</li><li><a name="PROV:0006" href="#PROV:0006">PROV:0006</a> "Given a process execution <b>pe</b>, entity <b>e</b>, role <b>r</b>, and optional time <b>t</b>, if
+</li>
+
+<li><a name="PROV:0006" href="#PROV:0006">PROV:0006</a> "Given a process execution <b>pe</b>, entity <b>e</b>, role <b>r</b>, and optional time <b>t</b>, if
assertion <b>used(pe,e,r)</b> or <b>used(pe,e,r,t)</b> holds, one can
infer that the use of the thing denoted by <b>e</b> precedes the end
of <b>pe</b> and follows the beginning of <b>pe</b>. Furthermore, we
can infer that the generation of the thing denoted by <b>e</b> always precedes
its use." (<a href="../model/ProvenanceModel.html#PROV:0006">link</a>)
-</li><li> <a name="PROV:0007" href="#PROV:0007">PROV:0007</a> "Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, if the assertion <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
+</li>
+
+<li> <a name="PROV:0007" href="#PROV:0007">PROV:0007</a> "Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, if the assertion <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
or <b>wasDerivedFrom(e2,e1)</b> holds, if and only if:
the values of some attributes
of <b>e2</b> are partly or fully determined by the values of some
attributes of <b>e1</b>." (<a href="../model/ProvenanceModel.html#PROV:0007">link</a>)
-</li><li><a name="PROV:0008" href="#PROV:0008">PROV:0008</a> "Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, if the assertion <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
+</li>
+
+<li><a name="PROV:0008" href="#PROV:0008">PROV:0008</a> "Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, if the assertion <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
or <b>wasDerivedFrom(e2,e1)</b> holds, then
the use
of characterized thing denoted by <b>e1</b> precedes the generation of
the characterized thing denoted by <b>e2</b>." (<a href="../model/ProvenanceModel.html#PROV:0008">link</a>)
-</li><li><a name="PROV:0009" href="#PROV:0009">PROV:0009</a> "If <b>wasDerivedFrom(e2,e1)</b> holds, then there exists a process execution <b>pe</b>, and roles <b>r1</b>,<b>r2</b>,
+</li>
+
+<li><a name="PROV:0009" href="#PROV:0009">PROV:0009</a> "If <b>wasDerivedFrom(e2,e1)</b> holds, then there exists a process execution <b>pe</b>, and roles <b>r1</b>,<b>r2</b>,
such that:
<b>wasGeneratedBy(e2,pe,r2)</b> and <b>used(pe,e1,r1)</b>." (<a href="../model/ProvenanceModel.html#PROV:0009">link</a>)
-</li><li><a name="PROV:0010" href="#PROV:0010">PROV:0010</a> "If <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b> holds, then <b>wasGeneratedBy(e2,pe,r2)</b> and <b>used(pe,e1,r1)</b> also hold." (<a href="../model/ProvenanceModel.html#PROV:0010">link</a>)
-</li><li><a name="PROV:0011" href="#PROV:0011">PROV:0011</a> "Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, and role <b>r2</b>,
+</li>
+
+
+<li><a name="PROV:0010" href="#PROV:0010">PROV:0010</a> "If <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b> holds, then <b>wasGeneratedBy(e2,pe,r2)</b> and <b>used(pe,e1,r1)</b> also hold." (<a href="../model/ProvenanceModel.html#PROV:0010">link</a>)
+</li>
+
+<li><a name="PROV:0011" href="#PROV:0011">PROV:0011</a> "Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, and role <b>r2</b>,
if <b>wasDerivedFrom(e2,e1)</b> and <b>wasGeneratedBy(e2,pe,r2)</b> hold, then there exists a role <b>r1</b>,
such that <b>used(pe,e1,r1)</b> also holds." (<a href="../model/ProvenanceModel.html#PROV:0011">link</a>)
</li>
+
<li><a name="PROV:0012" href="#PROV:0012">PROV:0012</a> "Given two entities <b>e1</b> and <b>e2</b>, if the assertion <b>isEventuallyDerivedFrom(e2,e1)</b>
holds, then:
generation of the characterized thing denoted by <b>e1</b> precedes the generation of
the characterized thing denoted by <b>e2</b>." (<a href="../model/ProvenanceModel.html#PROV:0012">link</a>)
</li>
+
<li><a name="PROV:0013" href="#PROV:0013">PROV:0013</a> "An assertion "wasComplementOf(B,A)" holds over the temporal intersection of A and B, <em>only if</em>:
-<ol>
-<li> if a mapping can be established from an attribute X of B to an attribute Y of A, then the values of A and B must be consistent with that mapping</em> </li>
- <li>B has some attribute that A does not have
-</li></ol>" (<a href="../model/ProvenanceModel.html#PROV:0013">link</a>)
+ <ol>
+ <li> if a mapping can be established from an attribute X of B to an attribute Y of A, then the values of A and B must be consistent with that mapping</li>
+ <li>B has some attribute that A does not have" (<a href="../model/ProvenanceModel.html#PROV:0013">link</a>) </li>
+ </ol>
</li>
+
<li><a name="PROV:0014" href="#PROV:0014">PROV:0014</a> "Given a process execution <b>pe</b> and entity <b>e</b>, <b>hadPariticipant(pe,e)</b> holds if and only if:
-<ul>
-<li> <b>used(pe,e)</b> holds, or</li>
-<li> <b>wasControlledBy(pe,e)</b> holds, or</li>
-<li> <b>wasComplementOf(e1,e)</b> holds for some entities <b>e1</b>, and
- <b>hadPariticipant(pe,e1)</b> some process execution <b>pe</b>.</li>
+ <ul>
+ <li> <b>used(pe,e)</b> holds, or</li>
+ <li> <b>wasControlledBy(pe,e)</b> holds, or</li>
+ <li> <b>wasComplementOf(e1,e)</b> holds for some entities <b>e1</b>, and <b>hadParticipant(pe,e1)</b> some process execution <b>pe</b>.</li>
+ </ul>
+</li>
</ul>
-</p>
-<div class="note">The following constraints are extracted from the
+
+<div class="note">The above constraints are extracted from the
ProvenanceModel document. The text below should be kept consistent
with the other document, with bidirectional links. The plan is to
insert formalizations of these constraints once the OWL
@@ -1317,13 +1415,17 @@
If a constraint is dropped, please mark it as "defunct" - don't
delete it!
</div>
- </section>
</section>
+ </section>
+
+
+
<section class='appendix'>
<h2>Acknowledgements</h2>
<p>
The Provenance Working Group Members.
</p>
</section>
+
</body>
</html>
--- a/ontology/component-aggregations/aggregate.sh Mon Oct 10 12:23:09 2011 +0100
+++ b/ontology/component-aggregations/aggregate.sh Mon Oct 10 12:23:53 2011 +0100
@@ -14,37 +14,72 @@
#3> doap:download-page <http://download.librdf.org/source/raptor2-1.9.1.tar.gz> ];
#3> .
-base="http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/component-aggregations"
+base="https://dvcs.w3.org/hg/prov/raw-file/tip/ontology/component-aggregations"
+
+if [ ! `which md5` ]; then
+ echo "need md5 to proceed"
+ exit 1
+fi
+
+if [ ! `which rapper` ]; then
+ echo "need rapper to proceed; install http://download.librdf.org/source/raptor2-1.9.1.tar.gz "
+ echo "see http://librdf.org/raptor/INSTALL.html "
+ exit 1
+fi
rm -f "_"`basename $0`*.tmp
TEMP="_"`basename $0``date +%s`_$$.tmp
-for aggregation_file in `find . -name "*.ttl" | grep -v ".prov.ttl" | sed 's/^\.\///'`; do
- aggregation_url="${base}/${aggregation_file}"
- echo "$aggregation_url"
+for component_list_file in `find . -name "*.ttl" | grep -v "\.prov.ttl" | sed 's/^\.\///'`; do
rm -f $TEMP
- for component in `rapper -g -o ntriples $aggregation_url 2> /dev/null | awk '$2 == "<http://www.w3.org/2002/07/owl#imports>"{print $3}' | sed 's/<//;s/>//'`; do
+ component_url="${base}/${component_list_file}"
+ echo "$component_url"
+ closure_file=`echo $component_list_file | sed 's/.ttl$/.owl/'`
+
+ if [ "$closure_file" == $component_list_file ]; then
+ echo "skipping $component_list_file because it would be overwritten by its closure."
+ continue
+ fi
+
+ let input_count=0
+ for component in `rapper -g -o ntriples $component_url 2> /dev/null | awk '$2 == "<http://www.w3.org/2002/07/owl#imports>"{print $3}' | sed 's/<//;s/>//'`; do
+ let input_count=$input_count+1
genid=`md5 -s $component | awk '{print $4}'`
echo " += $component"
rapper -q -g -o ntriples $component | sed "s/_:genid/_:genid${genid}/g" >> $TEMP
+ if [ $input_count -eq 1 ]; then
+ echo "@prefix nfo: <http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#> ." >> $closure_file.prov.ttl
+ echo "@prefix prov: <http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/ProvenanceOntology.owl#> ." >> $closure_file.prov.ttl
+ echo "@prefix : <#> ." >> $closure_file.prov.ttl
+ id=""
+ else
+ id="_$input_count"
+ fi
+ echo "" >> $closure_file.prov.ttl
+ echo ":result" >> $closure_file.prov.ttl
+ if [ $input_count -eq 1 ]; then
+ echo " nfo:fileURL <$closure_file>;" >> $closure_file.prov.ttl
+ echo " prov:wasDerivedFrom :component_list;" >> $closure_file.prov.ttl
+ fi
+ echo " prov:wasDerivedFrom :input$id;" >> $closure_file.prov.ttl
+ if [ $input_count -eq 1 ]; then
+ echo " a prov:Entity;" >> $closure_file.prov.ttl
+ fi
+ echo "." >> $closure_file.prov.ttl
+ if [ $input_count -eq 1 ]; then
+ echo "" >> $closure_file.prov.ttl
+ echo ":component_list" >> $closure_file.prov.ttl
+ echo " nfo:fileURL <$component_url>;" >> $closure_file.prov.ttl
+ echo " a prov:Entity;" >> $closure_file.prov.ttl
+ echo "." >> $closure_file.prov.ttl
+ fi
+ echo "" >> $closure_file.prov.ttl
+ echo ":input$id" >> $closure_file.prov.ttl
+ echo " nfo:fileURL <$component>;" >> $closure_file.prov.ttl
+ echo " a prov:Entity;" >> $closure_file.prov.ttl
+ echo "." >> $closure_file.prov.ttl
done
- aggregated=`echo $aggregation_file | sed 's/.ttl$/.owl/'`
- if [[ "$aggregation" != "$aggregated" ]]; then
- rapper -q -i ntriples -o rdfxml-abbrev $TEMP > $aggregated
- echo " ==-> $aggregated"
- echo "@prefix nfo: <http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#> ." >> $aggregated.prov.ttl
- echo "@prefix prov: <http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/ProvenanceOntology.owl#> ." >> $aggregated.prov.ttl
- echo "@prefix : <#> ." >> $aggregated.prov.ttl
- echo "" >> $aggregated.prov.ttl
- echo ":result" >> $aggregated.prov.ttl
- echo " a prov:Entity;" >> $aggregated.prov.ttl
- echo " nfo:fileURL <$aggregated>;" >> $aggregated.prov.ttl
- echo " prov:wasDerivedFrom :input;" >> $aggregated.prov.ttl
- echo "." >> $aggregated.prov.ttl
- echo ":input" >> $aggregated.prov.ttl
- echo " a prov:Entity;" >> $aggregated.prov.ttl
- echo " nfo:fileURL <$aggregation_url>;" >> $aggregated.prov.ttl
- echo "." >> $aggregated.prov.ttl
- fi
+ rapper -q -i ntriples -o rdfxml-abbrev $TEMP > $closure_file
+ echo " ==-> $closure_file"
rm -f $TEMP
done
--- a/ontology/component-aggregations/prov-variant-1.owl.prov.ttl Mon Oct 10 12:23:09 2011 +0100
+++ b/ontology/component-aggregations/prov-variant-1.owl.prov.ttl Mon Oct 10 12:23:53 2011 +0100
@@ -3,11 +3,36 @@
@prefix : <#> .
:result
+ nfo:fileURL <prov-variant-1.owl>;
+ prov:wasDerivedFrom :component_list;
+ prov:wasDerivedFrom :input;
a prov:Entity;
- nfo:fileURL <prov-variant-1.owl>;
- prov:wasDerivedFrom :input;
.
-:input
+
+:component_list
+ nfo:fileURL <https://dvcs.w3.org/hg/prov/raw-file/tip/ontology/component-aggregations/prov-variant-1.ttl>;
a prov:Entity;
- nfo:fileURL <http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/component-aggregations/prov-variant-1.ttl>;
.
+
+:input
+ nfo:fileURL <https://dvcs.w3.org/hg/prov/raw-file/tip/ontology/components/Account.ttl>;
+ a prov:Entity;
+.
+
+:result
+ prov:wasDerivedFrom :input_2;
+.
+
+:input_2
+ nfo:fileURL <https://dvcs.w3.org/hg/prov/raw-file/tip/ontology/components/EntityInRole.ttl>;
+ a prov:Entity;
+.
+
+:result
+ prov:wasDerivedFrom :input_3;
+.
+
+:input_3
+ nfo:fileURL <https://dvcs.w3.org/hg/prov/raw-file/tip/ontology/components/assumedBy.ttl>;
+ a prov:Entity;
+.
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/component-aggregations/prov.owl Mon Oct 10 12:23:53 2011 +0100
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="utf-8"?>
+<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+ <ns1:ObjectProperty xmlns:ns1="http://www.w3.org/2002/07/owl#" rdf:about="http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/ProvenanceOntology.owl#wasDerivedFrom">
+ <ns2:domain xmlns:ns2="http://www.w3.org/2000/01/rdf-schema#" rdf:resource="http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/ProvenanceOntology.owl#Entity"/>
+ <ns3:label xmlns:ns3="http://www.w3.org/2000/01/rdf-schema#">wasDerivedFrom</ns3:label>
+ <ns4:range xmlns:ns4="http://www.w3.org/2000/01/rdf-schema#" rdf:resource="http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/ProvenanceOntology.owl#Entity"/>
+ </ns1:ObjectProperty>
+</rdf:RDF>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/component-aggregations/prov.owl.prov.ttl Mon Oct 10 12:23:53 2011 +0100
@@ -0,0 +1,20 @@
+@prefix nfo: <http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#> .
+@prefix prov: <http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/ProvenanceOntology.owl#> .
+@prefix : <#> .
+
+:result
+ nfo:fileURL <prov.owl>;
+ prov:wasDerivedFrom :component_list;
+ prov:wasDerivedFrom :input;
+ a prov:Entity;
+.
+
+:component_list
+ nfo:fileURL <https://dvcs.w3.org/hg/prov/raw-file/tip/ontology/component-aggregations/prov.ttl>;
+ a prov:Entity;
+.
+
+:input
+ nfo:fileURL <https://dvcs.w3.org/hg/prov/raw-file/tip/ontology/components/wasDerivedFrom.ttl>;
+ a prov:Entity;
+.
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/component-aggregations/prov.ttl Mon Oct 10 12:23:53 2011 +0100
@@ -0,0 +1,18 @@
+@prefix owl: <http://www.w3.org/2002/07/owl#> .
+@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
+@prefix prov: <http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/ProvenanceOntology.owl#> .
+
+#
+# This is the component aggregation that creates the authoritative PROV OWL encoding.
+# (though, it is not authoritative yet)
+#
+# This component aggregation needs to be reconciled with the FPWD OWL encoding
+# http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/ProvenanceOntology.owl
+# which was at version http://dvcs.w3.org/hg/prov/file/a3bfb267402a/ontology/ProvenanceOntology.owl on 2011-10-06
+#
+# tlebo 2011-10-06
+
+<>
+ a owl:Ontology;
+ owl:imports <http://dvcs.w3.org/hg/prov/raw-file/3d6ec214ad01/ontology/components/wasDerivedFrom.ttl>;
+.
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/components/NamedGraph/World_Wide_Web_Consortium.rdf Mon Oct 10 12:23:53 2011 +0100
@@ -0,0 +1,150 @@
+<?xml version="1.0" encoding="utf-8" ?>
+<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
+<rdf:Description rdf:about="http://dbpedia.org/resource/Cascading_Style_Sheets"><dbpprop:owner xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpprop:regionServed xmlns:dbpprop="http://dbpedia.org/property/" xml:lang="en">Worldwide</dbpprop:regionServed></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:motto xmlns:dbpedia-owl="http://dbpedia.org/ontology/" xml:lang="en">Leading the Web to Its Full Potential...</dbpedia-owl:motto></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:abstract xmlns:dbpedia-owl="http://dbpedia.org/ontology/" xml:lang="fr">Le World Wide Web Consortium, abrégé par le sigle W3C, est un organisme de standardisation à but non-lucratif, fondé en Modèle:Date comme un consortium chargé de promouvoir la compatibilité des technologies du World Wide Web telles que HTML, XHTML, XML, RDF, CSS, PNG, SVG et SOAP.</dbpedia-owl:abstract></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdf:type rdf:resource="http://umbel.org/umbel/rc/Organization"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:comment xml:lang="sv">W3C, World Wide Web Consortium, är ett industrikonsortium grundat år 1994 med över 500 medlemmar från ledande industrier, forsknings- och utvecklingsinstitut, standardiseringsorgan och regeringar samt EU. Dessa finansierar verksamheten tillsammans med statliga bidrag. W3C arbetar med att utveckla tekniska protokoll, standarder och programvara för webben med målet att genom ett öppet samarbete leda Internet till dess fulla potential.</rdfs:comment></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Distributed_GIS"><dbpprop:owner xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:abstract xmlns:dbpedia-owl="http://dbpedia.org/ontology/" xml:lang="it">Nell'ottobre del 1994 Tim Berners Lee, padre del Web, fondò al MIT (Massachusetts Institute of Technology), in collaborazione con il CERN (il laboratorio dal quale proveniva), un'associazione di nome World Wide Web Consortium (abbreviato W3C), con lo scopo di migliorare gli esistenti protocolli e linguaggi per il World Wide Web e di aiutare il web a sviluppare tutte le sue potenzialità. Nell'aprile del 1995 l'INRIA (Istituto Nazionale di Ricerca Informatica ed Automatica francese) divenne il primo membro europeo dell'organizzazione. Nel 1996 il W3C approdò in Asia, grazie alla Keio University di Tokio. Nel 2003 l'ERCIM (Il Consorzio Europeo di Ricerca in Informatica e Matematica) prese il ruolo di host europeo del W3C dall'INRIA (che è l'istituzione francese dell'ERCIM).</dbpedia-owl:abstract></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:comment xml:lang="en">The World Wide Web Consortium (W3C) is the main international standards organization for the World Wide Web (abbreviated WWW or W3). Founded and headed by Tim Berners-Lee, the consortium is made up of member organizations which maintain full-time staff for the purpose of working together in the development of standards for the World Wide Web. As of 18 February 2011, the World Wide Web Consortium (W3C) has 322 members.</rdfs:comment></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Scalable_Vector_Graphics"><dbpprop:owner xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:abstract xmlns:dbpedia-owl="http://dbpedia.org/ontology/" xml:lang="es">El World Wide Web Consortium, abreviado W3C, es un consorcio internacional que produce recomendaciones para la World Wide Web. Está dirigida por Tim Berners-Lee, el creador original de URL (Uniform Resource Locator, Localizador Uniforme de Recursos), HTTP (HyperText Transfer Protocol, Protocolo de Transferencia de HiperTexto) y HTML (Lenguaje de Marcado de HiperTexto) que son las principales tecnologías sobre las que se basa la Web.</dbpedia-owl:abstract></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:location xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/Keio_University"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:location xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/MIT_Computer_Science_and_Artificial_Intelligence_Laboratory"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:location xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/France"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/XHTML"><dbpprop:owner xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:comment xml:lang="pl">World Wide Web Consortium, w skrócie W3C, to organizacja, która zajmuje się ustanawianiem standardów pisania i przesyłu stron WWW. Została założona 1 października 1994 roku przez Tima Berners-Lee, twórcę WWW oraz autora pierwszej przeglądarki internetowej i serwera WWW. W3C jest obecnie zrzeszeniem ponad 400 organizacji, firm, agencji rządowych i uczelni z całego świata. Publikowane przez W3C rekomendacje nie mają mocy prawnej, nakazującej ich użycie.</rdfs:comment></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Tantek_%C3%87elik"><dbpedia-owl:knownFor xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Amaya_%28web_browser%29"><dbpedia-owl:developer xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdf:type rdf:resource="http://dbpedia.org/ontology/Organisation"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/CERN_httpd"><dbpedia-owl:developer xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:comment xml:lang="ru">Консо́рциум Всеми́рной паути́ны (англ. World Wide Web Consortium, W3C) — организация, разрабатывающая и внедряющая технологические стандарты для Всемирной паутины. Консорциум возглавляет сэр Тимоти Джон Бернерс-Ли, автор множества разработок в области информационных технологий.</rdfs:comment></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/HTML"><dbpprop:owner xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dcterms:subject xmlns:dcterms="http://purl.org/dc/terms/" rdf:resource="http://dbpedia.org/resource/Category:Organizations_established_in_1994"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpprop:wikiPageUsesTemplate xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/Template:Infobox_organization"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:comment xml:lang="fr">Le World Wide Web Consortium, abrégé par le sigle W3C, est un organisme de standardisation à but non-lucratif, fondé en Modèle:Date comme un consortium chargé de promouvoir la compatibilité des technologies du World Wide Web telles que HTML, XHTML, XML, RDF, CSS, PNG, SVG et SOAP.</rdfs:comment></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:abstract xmlns:dbpedia-owl="http://dbpedia.org/ontology/" xml:lang="nl">Het World Wide Web Consortium (W3C) is een organisatie die de webstandaarden voor het World Wide Web ontwerpt, zoals HTML, XHTML, XML en CSS. Het wordt geleid door Tim Berners-Lee, de originele bedenker van het HTTP protocol en HTML, waar het Web oorspronkelijk en nog steeds grotendeels op gebaseerd is. De organisatie is in 1994 opgericht in samenwerking met CERN, ondersteund door DARPA en de Europese Commissie. W3C telt momenteel meer dan 500 leden en circa 60 fulltime medewerkers over de hele wereld; zij leveren een bijdrage aan het ontwikkelen van specificaties en software voor W3C.</dbpedia-owl:abstract></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Arena_%28web_browser%29"><dbpprop:developer xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdf:type rdf:resource="http://dbpedia.org/class/yago/Consortia"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Acid1"><dbpedia-owl:owner xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dcterms:subject xmlns:dcterms="http://purl.org/dc/terms/" rdf:resource="http://dbpedia.org/resource/Category:Web_services"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:abstract xmlns:dbpedia-owl="http://dbpedia.org/ontology/" xml:lang="ja">World Wide Web Consortium（ワールド・ワイド・ウェブ・コンソーシアム）は、World Wide Webで使用される各種技術の標準化を推進する為に設立された標準化団体、非営利団体。略称はW3C（ダブリュースリーシー）。 ティム・バーナーズ＝リーが創設し、率いている。このコンソーシアムには企業や団体が会員として加入し、専任スタッフと共にWorld Wide Webの標準策定を行っている。2009年9月8日現在、356の組織が会員として加入している。 W3Cはまた教育活動も行っており、ソフトウェアを開発してWebに関するオープンな議論の場を提供している。 HTML、XML、MathML、DOM等の規格を勧告。HTMLは、従来IETFでRFCとして標準化されていたが、HTML 3.2以降はW3Cへと引き継がれた。 XHTMLの規格に不満を持った企業等はW3Cに対抗するWHATWGという対抗団体を立ち上げているが、両団体はHTML5の策定にあたって協力関係にあり、WHATWGによって2004年に定められたWeb Applications 1.0にWeb Forms 2.0を取り入れたものがW3Cの専門委員会に採用され、W3Cより2008年1月22日にドラフト（草案）が発表された。</dbpedia-owl:abstract></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:comment xml:lang="no">World Wide Web Consortium, forkortet W3C, er en organisasjon som ble startet i oktober 1994. Organisasjonens hovedmål er å utvikle protokoller og standarder for teknologien som brukes på World Wide Web. I den sammenheng tilbyr W3Cs nettsted ulike tjenester for testing eller validering av nettsider, stilark og andre, mer avanserte valideringsverktøy.</rdfs:comment></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><foaf:homepage xmlns:foaf="http://xmlns.com/foaf/0.1/" rdf:resource="http://www.w3.org/"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:membership xmlns:dbpedia-owl="http://dbpedia.org/ontology/" xml:lang="en">314 member organizations</dbpedia-owl:membership></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:comment xml:lang="de">Das World Wide Web Consortium ist das Gremium zur Standardisierung der das World Wide Web betreffenden Techniken. Es wurde am 1. Oktober 1994 am MIT Laboratory for Computer Science in Cambridge (Massachusetts) gegründet. Gründer und Vorsitzender des W3C ist Tim Berners-Lee, der auch als der Erfinder des World Wide Web bekannt ist.</rdfs:comment></rdf:Description>
+<rdf:Description rdf:about="http://www4.wiwiss.fu-berlin.de/flickrwrappr/photos/World_Wide_Web_Consortium"><owl:sameAs xmlns:owl="http://www.w3.org/2002/07/owl#" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/MathML"><dbpprop:owner xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdf:type rdf:resource="http://dbpedia.org/class/yago/WebServices"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Resource_Description_Framework"><dbpprop:owner xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://mpii.de/yago/resource/World_Wide_Web_Consortium"><owl:sameAs xmlns:owl="http://www.w3.org/2002/07/owl#" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Web"><dbpedia-owl:wikiPageDisambiguates xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/XQuery"><dbpprop:designer xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:label xml:lang="ja">World Wide Web Consortium</rdfs:label></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:label xml:lang="sv">World Wide Web Consortium</rdfs:label></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:abstract xmlns:dbpedia-owl="http://dbpedia.org/ontology/" xml:lang="ru">Консо́рциум Всеми́рной паути́ны (англ. World Wide Web Consortium, W3C) — организация, разрабатывающая и внедряющая технологические стандарты для Всемирной паутины. Консорциум возглавляет сэр Тимоти Джон Бернерс-Ли, автор множества разработок в области информационных технологий.</dbpedia-owl:abstract></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/XQuery"><dbpedia-owl:designer xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Alan_Kotok"><dbpedia-owl:knownFor xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:location xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/Japan"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Tim_Berners-Lee"><dbpedia-owl:employer xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:numberOfStaff xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:datatype="http://www.w3.org/2001/XMLSchema#integer">62</dbpedia-owl:numberOfStaff></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdf:type rdf:resource="http://dbpedia.org/class/yago/Organization108008335"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:label xml:lang="es">World Wide Web Consortium</rdfs:label></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpprop:size xmlns:dbpprop="http://dbpedia.org/property/" xml:lang="en">frameless</dbpprop:size></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Compound_Document_Format"><dbpprop:owner xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:label xml:lang="zh">万维网联盟</rdfs:label></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/XPath"><dbpprop:developer xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdf:type rdf:resource="http://schema.org/Organization"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:comment xml:lang="zh">万维网联盟（Template:Lang，W3C），又称W3C理事会。1994年10月在麻省理工学院计算机科学实验室成立。建立者是互聯網的发明者蒂姆·伯纳斯-李。 为解决web应用中不同平台、技术和开发者带来的不兼容问题，保障Web信息的顺利和完整流通，万维网联盟制定了一系列标准并督促Web应用开发者和内容提供者遵循这些标准。标准的内容包括使用语言的规范，开发中使用的导则和解释引擎的行为等等。W3C也制定了包括XML和CSS等的众多影响深远的标准规范。 但是，W3C制定的web标准似乎并非强制而只是推荐标准。因此部分网站仍然不能完全实现这些标准。特别是使用早期所见即所得网页编辑软件设计的网页往往会包含大量非标准代码。</rdfs:comment></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:abstract xmlns:dbpedia-owl="http://dbpedia.org/ontology/" xml:lang="zh">万维网联盟（Template:Lang，W3C），又称W3C理事会。1994年10月在麻省理工学院计算机科学实验室成立。建立者是互聯網的发明者蒂姆·伯纳斯-李。 为解决web应用中不同平台、技术和开发者带来的不兼容问题，保障Web信息的顺利和完整流通，万维网联盟制定了一系列标准并督促Web应用开发者和内容提供者遵循这些标准。标准的内容包括使用语言的规范，开发中使用的导则和解释引擎的行为等等。W3C也制定了包括XML和CSS等的众多影响深远的标准规范。 但是，W3C制定的web标准似乎并非强制而只是推荐标准。因此部分网站仍然不能完全实现这些标准。特别是使用早期所见即所得网页编辑软件设计的网页往往会包含大量非标准代码。</dbpedia-owl:abstract></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:purpose xmlns:dbpedia-owl="http://dbpedia.org/ontology/" xml:lang="en">Developing protocols and guidelines that ensure long-term growth for the Web.</dbpedia-owl:purpose></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/XHTML%2BRDFa"><dbpprop:owner xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/XPath"><dbpedia-owl:developer xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/WWWC"><dbpedia-owl:wikiPageRedirects xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dcterms:subject xmlns:dcterms="http://purl.org/dc/terms/" rdf:resource="http://dbpedia.org/resource/Category:International_nongovernmental_organizations"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/W3c"><dbpedia-owl:wikiPageRedirects xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:location xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/ERCIM"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdf:type rdf:resource="http://dbpedia.org/class/yago/InternationalNongovernmentalOrganizations"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Synchronized_Multimedia_Integration_Language"><dbpprop:owner xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Amaya_%28web_browser%29"><dbpprop:developer xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><foaf:page xmlns:foaf="http://xmlns.com/foaf/0.1/" rdf:resource="http://en.wikipedia.org/wiki/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpprop:motto xmlns:dbpprop="http://dbpedia.org/property/" xml:lang="en">Leading the Web to Its Full Potential...</dbpprop:motto></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/N-Triples"><dbpprop:owner xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:thumbnail xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://upload.wikimedia.org/wikipedia/commons/thumb/e/ec/W3C_logo.svg/200px-W3C_logo.svg.png"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Web_Ontology_Language"><dbpprop:owner xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpprop:abbreviation xmlns:dbpprop="http://dbpedia.org/property/" xml:lang="en">W3C</dbpprop:abbreviation></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpprop:formation xmlns:dbpprop="http://dbpedia.org/property/" xml:lang="en">October 1994</dbpprop:formation></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Alan_Kotok"><dbpprop:knownFor xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:comment xml:lang="pt">O World Wide Web Consortium (W3C) é um consórcio internacional com cerca de 300 membros, que agrega empresas, órgãos governamentais e organizações independentes, e que visa desenvolver padrões para a criação e a interpretação de conteúdos para a Web. Foi fundado por Tim Berners-Lee em 1994 para levar a Web ao seu potencial máximo, por meio do desenvolvimento de protocolos comuns e fóruns abertos que promovam a sua evolução e assegurem a sua interoperabilidade.</rdfs:comment></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:wikiPageExternalLink xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://www.alistapart.com/articles/readspec"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/W3C"><dbpedia-owl:wikiPageRedirects xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Budapest_University_of_Technology_and_Economics"><dbpedia-owl:affiliation xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpprop:type xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/Standards_organization"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dcterms:subject xmlns:dcterms="http://purl.org/dc/terms/" rdf:resource="http://dbpedia.org/resource/Category:World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:label xml:lang="it">World Wide Web Consortium</rdfs:label></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:comment xml:lang="es">El World Wide Web Consortium, abreviado W3C, es un consorcio internacional que produce recomendaciones para la World Wide Web. Está dirigida por Tim Berners-Lee, el creador original de URL (Uniform Resource Locator, Localizador Uniforme de Recursos), HTTP (HyperText Transfer Protocol, Protocolo de Transferencia de HiperTexto) y HTML (Lenguaje de Marcado de HiperTexto) que son las principales tecnologías sobre las que se basa la Web.</rdfs:comment></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:abstract xmlns:dbpedia-owl="http://dbpedia.org/ontology/" xml:lang="no">World Wide Web Consortium, forkortet W3C, er en organisasjon som ble startet i oktober 1994. Organisasjonens hovedmål er å utvikle protokoller og standarder for teknologien som brukes på World Wide Web. I den sammenheng tilbyr W3Cs nettsted ulike tjenester for testing eller validering av nettsider, stilark og andre, mer avanserte valideringsverktøy.</dbpedia-owl:abstract></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpprop:leaderTitle xmlns:dbpprop="http://dbpedia.org/property/" xml:lang="en">Director</dbpprop:leaderTitle></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:comment xml:lang="nl">Het World Wide Web Consortium (W3C) is een organisatie die de webstandaarden voor het World Wide Web ontwerpt, zoals HTML, XHTML, XML en CSS. Het wordt geleid door Tim Berners-Lee, de originele bedenker van het HTTP protocol en HTML, waar het Web oorspronkelijk en nog steeds grotendeels op gebaseerd is. De organisatie is in 1994 opgericht in samenwerking met CERN, ondersteund door DARPA en de Europese Commissie.</rdfs:comment></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:abbreviation xmlns:dbpedia-owl="http://dbpedia.org/ontology/" xml:lang="en">W3C</dbpedia-owl:abbreviation></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/W3C_Software_Notice_and_License"><dbpprop:author xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:leaderFunction xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium__2"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:label xml:lang="en">World Wide Web Consortium</rdfs:label></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:label xml:lang="nl">World Wide Web Consortium</rdfs:label></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><foaf:depiction xmlns:foaf="http://xmlns.com/foaf/0.1/" rdf:resource="http://upload.wikimedia.org/wikipedia/commons/e/ec/W3C_logo.svg"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:comment xml:lang="it">Nell'ottobre del 1994 Tim Berners Lee, padre del Web, fondò al MIT (Massachusetts Institute of Technology), in collaborazione con il CERN (il laboratorio dal quale proveniva), un'associazione di nome World Wide Web Consortium (abbreviato W3C), con lo scopo di migliorare gli esistenti protocolli e linguaggi per il World Wide Web e di aiutare il web a sviluppare tutte le sue potenzialità.</rdfs:comment></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:type xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/Standards_organization"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><foaf:name xmlns:foaf="http://xmlns.com/foaf/0.1/" xml:lang="en">World Wide Web Consortium</foaf:name></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:abstract xmlns:dbpedia-owl="http://dbpedia.org/ontology/" xml:lang="pt">O World Wide Web Consortium (W3C) é um consórcio internacional com cerca de 300 membros, que agrega empresas, órgãos governamentais e organizações independentes, e que visa desenvolver padrões para a criação e a interpretação de conteúdos para a Web. Foi fundado por Tim Berners-Lee em 1994 para levar a Web ao seu potencial máximo, por meio do desenvolvimento de protocolos comuns e fóruns abertos que promovam a sua evolução e assegurem a sua interoperabilidade. Sites desenvolvidos segundo esses padrões podem ser acessados e visualizados por qualquer pessoa ou tecnologia, independente dos hardware ou software utilizados, como celulares e PDAs, de maneira rápida e compatível com os novos padrões e tecnologias que possam surgir com a evolução da internet. Para alcançar seus objetivos, o W3C possui diversos comitês que estudam as tecnologias existentes para a apresentação de conteúdo na Internet e criam padrões de recomendação para utilizar essas tecnologias. Com a padronização, os programas conseguem acessar facilmente os códigos e entender onde deve ser aplicado cada conhecimento expresso no documento. Padrões seus como HTML, XHTML e CSS são muito populares, contudo, em muitos casos são usados de forma errônea devido ao desconhecimento da especificação. É um dever de todo o desenvolvedor Web respeitar e seguir os padrões de acessibilidade do W3C, pois de outro modo poderá impor barreiras tecnológicas a diversas pessoas, desestimulando e até mesmo impedindo o acesso a suas páginas.</dbpedia-owl:abstract></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:label xml:lang="pt">W3C</rdfs:label></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/W3.org"><dbpedia-owl:wikiPageRedirects xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Alan_Kotok"><dbpprop:workInstitution xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Agora_%28web_browser%29"><dbpprop:developer xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpprop:website xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://www.w3.org/"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Computer_Graphics_Metafile"><dbpprop:owner xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Thing"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_wide_web_consortium"><dbpedia-owl:wikiPageRedirects xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:abstract xmlns:dbpedia-owl="http://dbpedia.org/ontology/" xml:lang="sv">W3C, World Wide Web Consortium, är ett industrikonsortium grundat år 1994 med över 500 medlemmar från ledande industrier, forsknings- och utvecklingsinstitut, standardiseringsorgan och regeringar samt EU. Dessa finansierar verksamheten tillsammans med statliga bidrag. W3C arbetar med att utveckla tekniska protokoll, standarder och programvara för webben med målet att genom ett öppet samarbete leda Internet till dess fulla potential. Tillsammans med INRIA har de även utvecklat webbläsaren och HTML-redigeringsprogrammet Amaya.</dbpedia-owl:abstract></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpprop:numStaff xmlns:dbpprop="http://dbpedia.org/property/" rdf:datatype="http://www.w3.org/2001/XMLSchema#int">62</dbpprop:numStaff></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdf:type rdf:resource="http://dbpedia.org/class/yago/StandardsOrganizations"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:comment xml:lang="fi">W3C eli World Wide Web Consortium on kansainvälinen yritysten ja yhteisöjen yhteenliittymä, joka ylläpitää ja kehittää WWW:n standardeja tai suosituksia kuten W3C niitä kutsuu. Sen perusti vuonna 1994 WWW:n keksijä Tim Berners-Lee, joka toimii nykyisinkin W3C:n johtajana. Konsortiolla on yli 400 jäsentä. Konsortion päämaja on Massachusetts Institute of Technologyn tiloissa Yhdysvalloissa. Muut instituutit, joissa W3C:llä on tutkimusta, ovat ERCIM Ranskassa ja Keio University Japanissa.</rdfs:comment></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpprop:name xmlns:dbpprop="http://dbpedia.org/property/" xml:lang="en">World Wide Web Consortium</dbpprop:name></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:label xml:lang="pl">World Wide Web Consortium</rdfs:label></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:abstract xmlns:dbpedia-owl="http://dbpedia.org/ontology/" xml:lang="en">The World Wide Web Consortium (W3C) is the main international standards organization for the World Wide Web (abbreviated WWW or W3). Founded and headed by Tim Berners-Lee, the consortium is made up of member organizations which maintain full-time staff for the purpose of working together in the development of standards for the World Wide Web. As of 18 February 2011, the World Wide Web Consortium (W3C) has 322 members. W3C also engages in education and outreach, develops software and serves as an open forum for discussion about the Web.</dbpedia-owl:abstract></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:label xml:lang="ru">Консорциум Всемирной паутины</rdfs:label></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:label xml:lang="fr">World Wide Web Consortium</rdfs:label></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><owl:sameAs xmlns:owl="http://www.w3.org/2002/07/owl#" rdf:resource="http://rdf.freebase.com/ns/m/082bb"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:location xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/Massachusetts_Institute_of_Technology"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dcterms:subject xmlns:dcterms="http://purl.org/dc/terms/" rdf:resource="http://dbpedia.org/resource/Category:Web_development"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:comment xml:lang="ja">World Wide Web Consortium（ワールド・ワイド・ウェブ・コンソーシアム）は、World Wide Webで使用される各種技術の標準化を推進する為に設立された標準化団体、非営利団体。略称はW3C（ダブリュースリーシー）。 ティム・バーナーズ＝リーが創設し、率いている。このコンソーシアムには企業や団体が会員として加入し、専任スタッフと共にWorld Wide Webの標準策定を行っている。2009年9月8日現在、356の組織が会員として加入している。 W3Cはまた教育活動も行っており、ソフトウェアを開発してWebに関するオープンな議論の場を提供している。 HTML、XML、MathML、DOM等の規格を勧告。HTMLは、従来IETFでRFCとして標準化されていたが、HTML 3.2以降はW3Cへと引き継がれた。 XHTMLの規格に不満を持った企業等はW3Cに対抗するWHATWGという対抗団体を立ち上げているが、両団体はHTML5の策定にあたって協力関係にあり、WHATWGによって2004年に定められたWeb Applications 1.0にWeb Forms 2.0を取り入れたものがW3Cの専門委員会に採用され、W3Cより2008年1月22日にドラフト（草案）が発表された。</rdfs:comment></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:abstract xmlns:dbpedia-owl="http://dbpedia.org/ontology/" xml:lang="fi">W3C eli World Wide Web Consortium on kansainvälinen yritysten ja yhteisöjen yhteenliittymä, joka ylläpitää ja kehittää WWW:n standardeja tai suosituksia kuten W3C niitä kutsuu. Sen perusti vuonna 1994 WWW:n keksijä Tim Berners-Lee, joka toimii nykyisinkin W3C:n johtajana. Konsortiolla on yli 400 jäsentä. Konsortion päämaja on Massachusetts Institute of Technologyn tiloissa Yhdysvalloissa. Muut instituutit, joissa W3C:llä on tutkimusta, ovat ERCIM Ranskassa ja Keio University Japanissa. Lisäksi W3C:llä on useita aluetoimistoja eri maissa.</dbpedia-owl:abstract></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:wikiPageExternalLink xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://www.w3.org/TR/"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:wikiPageExternalLink xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://www.w3.org/Consortium/"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/Line_Mode_Browser"><dbpprop:developer xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:abstract xmlns:dbpedia-owl="http://dbpedia.org/ontology/" xml:lang="de">Das World Wide Web Consortium ist das Gremium zur Standardisierung der das World Wide Web betreffenden Techniken. Es wurde am 1. Oktober 1994 am MIT Laboratory for Computer Science in Cambridge (Massachusetts) gegründet. Gründer und Vorsitzender des W3C ist Tim Berners-Lee, der auch als der Erfinder des World Wide Web bekannt ist. Das W3C entwickelt technische Spezifikationen und Richtlinien mittels eines durchgehend entwickelten Prozess, um maximalen Konsens über den Inhalt eines technischen Protokolls, hohe technische und redaktionelle Qualität und Zustimmung durch das W3C und seiner Anhängerschaft zu erzielen. Seit Januar 2011 befindet sich der Sitz des Deutsch-Österreichischen Büros in Berlin am Deutschen Forschungszentrum für Künstliche Intelligenz (DFKI). Beispiele für durch das W3C standardisierte Technologien sind HTML, XHTML, XML, RDF, OWL, CSS, SVG und WCAG.</dbpedia-owl:abstract></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:abstract xmlns:dbpedia-owl="http://dbpedia.org/ontology/" xml:lang="pl">World Wide Web Consortium, w skrócie W3C, to organizacja, która zajmuje się ustanawianiem standardów pisania i przesyłu stron WWW. Została założona 1 października 1994 roku przez Tima Berners-Lee, twórcę WWW oraz autora pierwszej przeglądarki internetowej i serwera WWW. W3C jest obecnie zrzeszeniem ponad 400 organizacji, firm, agencji rządowych i uczelni z całego świata. Publikowane przez W3C rekomendacje nie mają mocy prawnej, nakazującej ich użycie.</dbpedia-owl:abstract></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:wikiPageExternalLink xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://www.w3.org/"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/W3-consortium"><dbpedia-owl:wikiPageRedirects xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:wikiPageExternalLink xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://www.w3.org/Consortium/Process/"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/W3_Consortium"><dbpedia-owl:wikiPageRedirects xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:label xml:lang="no">World Wide Web Consortium</rdfs:label></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:label xml:lang="fi">World Wide Web Consortium</rdfs:label></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpprop:membership xmlns:dbpprop="http://dbpedia.org/property/" rdf:datatype="http://dbpedia.org/datatype/second">18840.0</dbpprop:membership></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:formationYear xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:datatype="http://www.w3.org/2001/XMLSchema#gYear">1994-01-01T00:00:00-04:00</dbpedia-owl:formationYear></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dcterms:subject xmlns:dcterms="http://purl.org/dc/terms/" rdf:resource="http://dbpedia.org/resource/Category:Standards_organizations"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpprop:wordnet_type xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://www.w3.org/2006/03/wn/wn20/instances/synset-company-noun-1"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><rdfs:label xml:lang="de">World Wide Web Consortium</rdfs:label></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><owl:sameAs xmlns:owl="http://www.w3.org/2002/07/owl#" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dcterms:subject xmlns:dcterms="http://purl.org/dc/terms/" rdf:resource="http://dbpedia.org/resource/Category:Consortia"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/CERN_httpd"><dbpprop:developer xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/SCXML"><dbpprop:owner xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpprop:leaderName xmlns:dbpprop="http://dbpedia.org/property/" rdf:resource="http://dbpedia.org/resource/Tim_Berners-Lee"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpprop:location xmlns:dbpprop="http://dbpedia.org/property/" xml:lang="en">MIT/CSAIL in USA, ERCIM in France, Keio University in Japan and many other offices around the world</dbpprop:location></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:wikiPageExternalLink xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://www.w3.org/History/"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpprop:purpose xmlns:dbpprop="http://dbpedia.org/property/" xml:lang="en">Developing protocols and guidelines that ensure long-term growth for the Web.</dbpprop:purpose></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/WWW_Consortium"><dbpedia-owl:wikiPageRedirects xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+<rdf:Description rdf:about="http://dbpedia.org/resource/World_Wide_Web_Consortium"><dbpedia-owl:leaderFunction xmlns:dbpedia-owl="http://dbpedia.org/ontology/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium__1"/></rdf:Description>
+<rdf:Description rdf:about="http://en.wikipedia.org/wiki/World_Wide_Web_Consortium"><foaf:primaryTopic xmlns:foaf="http://xmlns.com/foaf/0.1/" rdf:resource="http://dbpedia.org/resource/World_Wide_Web_Consortium"/></rdf:Description>
+</rdf:RDF>
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/components/NamedGraph/World_Wide_Web_Consortium.trig Mon Oct 10 12:23:53 2011 +0100
@@ -0,0 +1,220 @@
+@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
+@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
+@prefix dbpprop: <http://dbpedia.org/property/> .
+@prefix dbpedia-owl: <http://dbpedia.org/ontology/> .
+@prefix dcterms: <http://purl.org/dc/terms/> .
+@prefix foaf: <http://xmlns.com/foaf/0.1/> .
+@prefix owl: <http://www.w3.org/2002/07/owl#> .
+@prefix sd: <http://www.w3.org/ns/sparql-service-description#> .
+@prefix prov: <http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/ProvenanceOntology.owl#> .
+@prefix : <#> .
+
+:about_that_big_graph_below {
+
+ :what_I_got_from_dbpedia
+ a sd:NamedGraph;
+ sd:name <hash:GRAPH_SHA256-488328c605c2f9532819d4ff8258650d2e03087e00454d25f5a39659f01d0b8307>;
+ prov:hadLocation <>;
+
+ dcterms:subject <http://dbpedia.org/resource/World_Wide_Web_Consortium>;
+ rdfs:comment
+ "The named graph <hash:GRAPH_SHA256-488328c605c2f9532819d4ff8258650d2e03087e00454d25f5a39659f01d0b8307> in this file is about W3C.";
+
+ prov:wasGeneratedBy :the_process_that_created_that_big_graph;
+ rdfs:comment
+ "The named graph <hash:GRAPH_SHA256-488328c605c2f9532819d4ff8258650d2e03087e00454d25f5a39659f01d0b8307> in this file is from DBpedia.";
+ .
+
+ :the_process_that_created_that_big_graph
+ a prov:ProcessExecution;
+ rdfs:seeAlso :download,
+ :reserialize; # How does PROV handle composition of processes?
+ .
+ :download
+ a prov:ProcessExecution;
+ dcterms:description
+ "curl -H 'Accept: application/rdf+xml' -L http://dbpedia.org/resource/World_Wide_Web_Consortium > World_Wide_Web_Consortium.rdf";
+ .
+ :reserialize
+ a prov:ProcessExecution;
+ prov:followed :download;
+ dcterms:description "rapper -g -o turtle World_Wide_Web_Consortium.rdf";
+ .
+}
+
+:about_that_big_graph_in_another_sparql_endpoint
+ :graph_copy_in_logd
+ a sd:NamedGraph; # The endpoint's name does NOT need to match the name in this file.
+ sd:name <hash:GRAPH_SHA256-488328c605c2f9532819d4ff8258650d2e03087e00454d25f5a39659f01d0b8307>;
+ prov:hadLocation <http://logd.tw.rpi.edu/sparql>;
+
+ dcterms:subject <http://dbpedia.org/resource/World_Wide_Web_Consortium>;
+ rdfs:comment
+ "The named graph <hash:GRAPH_SHA256-488328c605c2f9532819d4ff8258650d2e03087e00454d25f5a39659f01d0b8307> is ALSO available on a triple store (not only in this file).";
+ .
+}
+
+<hash:GRAPH_SHA256-488328c605c2f9532819d4ff8258650d2e03087e00454d25f5a39659f01d0b8307> {
+
+ <http://dbpedia.org/resource/Acid1>
+ dbpedia-owl:owner <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/Agora_%28web_browser%29>
+ dbpprop:developer <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/Alan_Kotok>
+ dbpedia-owl:knownFor <http://dbpedia.org/resource/World_Wide_Web_Consortium> ;
+ dbpprop:knownFor <http://dbpedia.org/resource/World_Wide_Web_Consortium> ;
+ dbpprop:workInstitution <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/Amaya_%28web_browser%29>
+ dbpedia-owl:developer <http://dbpedia.org/resource/World_Wide_Web_Consortium> ;
+ dbpprop:developer <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/Arena_%28web_browser%29>
+ dbpprop:developer <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/Budapest_University_of_Technology_and_Economics>
+ dbpedia-owl:affiliation <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/CERN_httpd>
+ dbpedia-owl:developer <http://dbpedia.org/resource/World_Wide_Web_Consortium> ;
+ dbpprop:developer <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/Cascading_Style_Sheets>
+ dbpprop:owner <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/Compound_Document_Format>
+ dbpprop:owner <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/Computer_Graphics_Metafile>
+ dbpprop:owner <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/Distributed_GIS>
+ dbpprop:owner <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/HTML>
+ dbpprop:owner <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/Line_Mode_Browser>
+ dbpprop:developer <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/MathML>
+ dbpprop:owner <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/N-Triples>
+ dbpprop:owner <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/Resource_Description_Framework>
+ dbpprop:owner <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/SCXML>
+ dbpprop:owner <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/Scalable_Vector_Graphics>
+ dbpprop:owner <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/Synchronized_Multimedia_Integration_Language>
+ dbpprop:owner <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/Tantek_%C3%87elik>
+ dbpedia-owl:knownFor <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/Tim_Berners-Lee>
+ dbpedia-owl:employer <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/W3-consortium>
+ dbpedia-owl:wikiPageRedirects <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/W3.org>
+ dbpedia-owl:wikiPageRedirects <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/W3C>
+ dbpedia-owl:wikiPageRedirects <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/W3C_Software_Notice_and_License>
+ dbpprop:author <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/W3_Consortium>
+ dbpedia-owl:wikiPageRedirects <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/W3c>
+ dbpedia-owl:wikiPageRedirects <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/WWWC>
+ dbpedia-owl:wikiPageRedirects <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/WWW_Consortium>
+ dbpedia-owl:wikiPageRedirects <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/Web>
+ dbpedia-owl:wikiPageDisambiguates <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/Web_Ontology_Language>
+ dbpprop:owner <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/World_Wide_Web_Consortium>
+ dbpedia-owl:abbreviation "W3C"@en ;
+ dbpedia-owl:abstract "Das World Wide Web Consortium ist das Gremium zur Standardisierung der das World Wide Web betreffenden Techniken. Es wurde am 1. Oktober 1994 am MIT Laboratory for Computer Science in Cambridge (Massachusetts) gegründet. Gründer und Vorsitzender des W3C ist Tim Berners-Lee, der auch als der Erfinder des World Wide Web bekannt ist. Das W3C entwickelt technische Spezifikationen und Richtlinien mittels eines durchgehend entwickelten Prozess, um maximalen Konsens über den Inhalt eines technischen Protokolls, hohe technische und redaktionelle Qualität und Zustimmung durch das W3C und seiner Anhängerschaft zu erzielen. Seit Januar 2011 befindet sich der Sitz des Deutsch-Österreichischen Büros in Berlin am Deutschen Forschungszentrum für Künstliche Intelligenz (DFKI). Beispiele für durch das W3C standardisierte Technologien sind HTML, XHTML, XML, RDF, OWL, CSS, SVG und WCAG."@de, "El World Wide Web Consortium, abreviado W3C, es un consorcio internacional que produce recomendaciones para la World Wide Web. Está dirigida por Tim Berners-Lee, el creador original de URL (Uniform Resource Locator, Localizador Uniforme de Recursos), HTTP (HyperText Transfer Protocol, Protocolo de Transferencia de HiperTexto) y HTML (Lenguaje de Marcado de HiperTexto) que son las principales tecnologías sobre las que se basa la Web."@es, "Het World Wide Web Consortium (W3C) is een organisatie die de webstandaarden voor het World Wide Web ontwerpt, zoals HTML, XHTML, XML en CSS. Het wordt geleid door Tim Berners-Lee, de originele bedenker van het HTTP protocol en HTML, waar het Web oorspronkelijk en nog steeds grotendeels op gebaseerd is. De organisatie is in 1994 opgericht in samenwerking met CERN, ondersteund door DARPA en de Europese Commissie. W3C telt momenteel meer dan 500 leden en circa 60 fulltime medewerkers over de hele wereld; zij leveren een bijdrage aan het ontwikkelen van specificaties en software voor W3C."@nl, "Le World Wide Web Consortium, abrégé par le sigle W3C, est un organisme de standardisation à but non-lucratif, fondé en Modèle:Date comme un consortium chargé de promouvoir la compatibilité des technologies du World Wide Web telles que HTML, XHTML, XML, RDF, CSS, PNG, SVG et SOAP."@fr, "Nell'ottobre del 1994 Tim Berners Lee, padre del Web, fondò al MIT (Massachusetts Institute of Technology), in collaborazione con il CERN (il laboratorio dal quale proveniva), un'associazione di nome World Wide Web Consortium (abbreviato W3C), con lo scopo di migliorare gli esistenti protocolli e linguaggi per il World Wide Web e di aiutare il web a sviluppare tutte le sue potenzialità. Nell'aprile del 1995 l'INRIA (Istituto Nazionale di Ricerca Informatica ed Automatica francese) divenne il primo membro europeo dell'organizzazione. Nel 1996 il W3C approdò in Asia, grazie alla Keio University di Tokio. Nel 2003 l'ERCIM (Il Consorzio Europeo di Ricerca in Informatica e Matematica) prese il ruolo di host europeo del W3C dall'INRIA (che è l'istituzione francese dell'ERCIM)."@it, "O World Wide Web Consortium (W3C) é um consórcio internacional com cerca de 300 membros, que agrega empresas, órgãos governamentais e organizações independentes, e que visa desenvolver padrões para a criação e a interpretação de conteúdos para a Web. Foi fundado por Tim Berners-Lee em 1994 para levar a Web ao seu potencial máximo, por meio do desenvolvimento de protocolos comuns e fóruns abertos que promovam a sua evolução e assegurem a sua interoperabilidade. Sites desenvolvidos segundo esses padrões podem ser acessados e visualizados por qualquer pessoa ou tecnologia, independente dos hardware ou software utilizados, como celulares e PDAs, de maneira rápida e compatível com os novos padrões e tecnologias que possam surgir com a evolução da internet. Para alcançar seus objetivos, o W3C possui diversos comitês que estudam as tecnologias existentes para a apresentação de conteúdo na Internet e criam padrões de recomendação para utilizar essas tecnologias. Com a padronização, os programas conseguem acessar facilmente os códigos e entender onde deve ser aplicado cada conhecimento expresso no documento. Padrões seus como HTML, XHTML e CSS são muito populares, contudo, em muitos casos são usados de forma errônea devido ao desconhecimento da especificação. É um dever de todo o desenvolvedor Web respeitar e seguir os padrões de acessibilidade do W3C, pois de outro modo poderá impor barreiras tecnológicas a diversas pessoas, desestimulando e até mesmo impedindo o acesso a suas páginas."@pt, "The World Wide Web Consortium (W3C) is the main international standards organization for the World Wide Web (abbreviated WWW or W3). Founded and headed by Tim Berners-Lee, the consortium is made up of member organizations which maintain full-time staff for the purpose of working together in the development of standards for the World Wide Web. As of 18 February 2011, the World Wide Web Consortium (W3C) has 322 members. W3C also engages in education and outreach, develops software and serves as an open forum for discussion about the Web."@en, "W3C eli World Wide Web Consortium on kansainvälinen yritysten ja yhteisöjen yhteenliittymä, joka ylläpitää ja kehittää WWW:n standardeja tai suosituksia kuten W3C niitä kutsuu. Sen perusti vuonna 1994 WWW:n keksijä Tim Berners-Lee, joka toimii nykyisinkin W3C:n johtajana. Konsortiolla on yli 400 jäsentä. Konsortion päämaja on Massachusetts Institute of Technologyn tiloissa Yhdysvalloissa. Muut instituutit, joissa W3C:llä on tutkimusta, ovat ERCIM Ranskassa ja Keio University Japanissa. Lisäksi W3C:llä on useita aluetoimistoja eri maissa."@fi, "W3C, World Wide Web Consortium, är ett industrikonsortium grundat år 1994 med över 500 medlemmar från ledande industrier, forsknings- och utvecklingsinstitut, standardiseringsorgan och regeringar samt EU. Dessa finansierar verksamheten tillsammans med statliga bidrag. W3C arbetar med att utveckla tekniska protokoll, standarder och programvara för webben med målet att genom ett öppet samarbete leda Internet till dess fulla potential. Tillsammans med INRIA har de även utvecklat webbläsaren och HTML-redigeringsprogrammet Amaya."@sv, "World Wide Web Consortium, forkortet W3C, er en organisasjon som ble startet i oktober 1994. Organisasjonens hovedmål er å utvikle protokoller og standarder for teknologien som brukes på World Wide Web. I den sammenheng tilbyr W3Cs nettsted ulike tjenester for testing eller validering av nettsider, stilark og andre, mer avanserte valideringsverktøy."@no, "World Wide Web Consortium, w skrócie W3C, to organizacja, która zajmuje się ustanawianiem standardów pisania i przesyłu stron WWW. Została założona 1 października 1994 roku przez Tima Berners-Lee, twórcę WWW oraz autora pierwszej przeglądarki internetowej i serwera WWW. W3C jest obecnie zrzeszeniem ponad 400 organizacji, firm, agencji rządowych i uczelni z całego świata. Publikowane przez W3C rekomendacje nie mają mocy prawnej, nakazującej ich użycie."@pl, "World Wide Web Consortium（ワールド・ワイド・ウェブ・コンソーシアム）は、World Wide Webで使用される各種技術の標準化を推進する為に設立された標準化団体、非営利団体。略称はW3C（ダブリュースリーシー）。 ティム・バーナーズ＝リーが創設し、率いている。このコンソーシアムには企業や団体が会員として加入し、専任スタッフと共にWorld Wide Webの標準策定を行っている。2009年9月8日現在、356の組織が会員として加入している。 W3Cはまた教育活動も行っており、ソフトウェアを開発してWebに関するオープンな議論の場を提供している。 HTML、XML、MathML、DOM等の規格を勧告。HTMLは、従来IETFでRFCとして標準化されていたが、HTML 3.2以降はW3Cへと引き継がれた。 XHTMLの規格に不満を持った企業等はW3Cに対抗するWHATWGという対抗団体を立ち上げているが、両団体はHTML5の策定にあたって協力関係にあり、WHATWGによって2004年に定められたWeb Applications 1.0にWeb Forms 2.0を取り入れたものがW3Cの専門委員会に採用され、W3Cより2008年1月22日にドラフト（草案）が発表された。"@ja, "Консо́рциум Всеми́рной паути́ны (англ. World Wide Web Consortium, W3C) — организация, разрабатывающая и внедряющая технологические стандарты для Всемирной паутины. Консорциум возглавляет сэр Тимоти Джон Бернерс-Ли, автор множества разработок в области информационных технологий."@ru, "万维网联盟（Template:Lang，W3C），又称W3C理事会。1994年10月在麻省理工学院计算机科学实验室成立。建立者是互聯網的发明者蒂姆·伯纳斯-李。 为解决web应用中不同平台、技术和开发者带来的不兼容问题，保障Web信息的顺利和完整流通，万维网联盟制定了一系列标准并督促Web应用开发者和内容提供者遵循这些标准。标准的内容包括使用语言的规范，开发中使用的导则和解释引擎的行为等等。W3C也制定了包括XML和CSS等的众多影响深远的标准规范。 但是，W3C制定的web标准似乎并非强制而只是推荐标准。因此部分网站仍然不能完全实现这些标准。特别是使用早期所见即所得网页编辑软件设计的网页往往会包含大量非标准代码。"@zh ;
+ dbpedia-owl:formationYear "1994-01-01T00:00:00-04:00"^^<http://www.w3.org/2001/XMLSchema#gYear> ;
+ dbpedia-owl:leaderFunction <http://dbpedia.org/resource/World_Wide_Web_Consortium__1>, <http://dbpedia.org/resource/World_Wide_Web_Consortium__2> ;
+ dbpedia-owl:location <http://dbpedia.org/resource/ERCIM>, <http://dbpedia.org/resource/France>, <http://dbpedia.org/resource/Japan>, <http://dbpedia.org/resource/Keio_University>, <http://dbpedia.org/resource/MIT_Computer_Science_and_Artificial_Intelligence_Laboratory>, <http://dbpedia.org/resource/Massachusetts_Institute_of_Technology> ;
+ dbpedia-owl:membership "314 member organizations"@en ;
+ dbpedia-owl:motto "Leading the Web to Its Full Potential..."@en ;
+ dbpedia-owl:numberOfStaff 62 ;
+ dbpedia-owl:purpose "Developing protocols and guidelines that ensure long-term growth for the Web."@en ;
+ dbpedia-owl:thumbnail <http://upload.wikimedia.org/wikipedia/commons/thumb/e/ec/W3C_logo.svg/200px-W3C_logo.svg.png> ;
+ dbpedia-owl:type <http://dbpedia.org/resource/Standards_organization> ;
+ dbpedia-owl:wikiPageExternalLink <http://www.alistapart.com/articles/readspec>, <http://www.w3.org/>, <http://www.w3.org/Consortium/>, <http://www.w3.org/Consortium/Process/>, <http://www.w3.org/History/>, <http://www.w3.org/TR/> ;
+ dbpprop:abbreviation "W3C"@en ;
+ dbpprop:formation "October 1994"@en ;
+ dbpprop:leaderName <http://dbpedia.org/resource/Tim_Berners-Lee> ;
+ dbpprop:leaderTitle "Director"@en ;
+ dbpprop:location "MIT/CSAIL in USA, ERCIM in France, Keio University in Japan and many other offices around the world"@en ;
+ dbpprop:membership "18840.0"^^<http://dbpedia.org/datatype/second> ;
+ dbpprop:motto "Leading the Web to Its Full Potential..."@en ;
+ dbpprop:name "World Wide Web Consortium"@en ;
+ dbpprop:numStaff "62"^^<http://www.w3.org/2001/XMLSchema#int> ;
+ dbpprop:purpose "Developing protocols and guidelines that ensure long-term growth for the Web."@en ;
+ dbpprop:regionServed "Worldwide"@en ;
+ dbpprop:size "frameless"@en ;
+ dbpprop:type <http://dbpedia.org/resource/Standards_organization> ;
+ dbpprop:website <http://www.w3.org/> ;
+ dbpprop:wikiPageUsesTemplate <http://dbpedia.org/resource/Template:Infobox_organization> ;
+ dbpprop:wordnet_type <http://www.w3.org/2006/03/wn/wn20/instances/synset-company-noun-1> ;
+ dcterms:subject <http://dbpedia.org/resource/Category:Consortia>, <http://dbpedia.org/resource/Category:International_nongovernmental_organizations>, <http://dbpedia.org/resource/Category:Organizations_established_in_1994>, <http://dbpedia.org/resource/Category:Standards_organizations>, <http://dbpedia.org/resource/Category:Web_development>, <http://dbpedia.org/resource/Category:Web_services>, <http://dbpedia.org/resource/Category:World_Wide_Web_Consortium> ;
+ a <http://dbpedia.org/class/yago/Consortia>, <http://dbpedia.org/class/yago/InternationalNongovernmentalOrganizations>, <http://dbpedia.org/class/yago/Organization108008335>, <http://dbpedia.org/class/yago/StandardsOrganizations>, <http://dbpedia.org/class/yago/WebServices>, dbpedia-owl:Organisation, <http://schema.org/Organization>, <http://umbel.org/umbel/rc/Organization>, owl:Thing ;
+ rdfs:comment "Das World Wide Web Consortium ist das Gremium zur Standardisierung der das World Wide Web betreffenden Techniken. Es wurde am 1. Oktober 1994 am MIT Laboratory for Computer Science in Cambridge (Massachusetts) gegründet. Gründer und Vorsitzender des W3C ist Tim Berners-Lee, der auch als der Erfinder des World Wide Web bekannt ist."@de, "El World Wide Web Consortium, abreviado W3C, es un consorcio internacional que produce recomendaciones para la World Wide Web. Está dirigida por Tim Berners-Lee, el creador original de URL (Uniform Resource Locator, Localizador Uniforme de Recursos), HTTP (HyperText Transfer Protocol, Protocolo de Transferencia de HiperTexto) y HTML (Lenguaje de Marcado de HiperTexto) que son las principales tecnologías sobre las que se basa la Web."@es, "Het World Wide Web Consortium (W3C) is een organisatie die de webstandaarden voor het World Wide Web ontwerpt, zoals HTML, XHTML, XML en CSS. Het wordt geleid door Tim Berners-Lee, de originele bedenker van het HTTP protocol en HTML, waar het Web oorspronkelijk en nog steeds grotendeels op gebaseerd is. De organisatie is in 1994 opgericht in samenwerking met CERN, ondersteund door DARPA en de Europese Commissie."@nl, "Le World Wide Web Consortium, abrégé par le sigle W3C, est un organisme de standardisation à but non-lucratif, fondé en Modèle:Date comme un consortium chargé de promouvoir la compatibilité des technologies du World Wide Web telles que HTML, XHTML, XML, RDF, CSS, PNG, SVG et SOAP."@fr, "Nell'ottobre del 1994 Tim Berners Lee, padre del Web, fondò al MIT (Massachusetts Institute of Technology), in collaborazione con il CERN (il laboratorio dal quale proveniva), un'associazione di nome World Wide Web Consortium (abbreviato W3C), con lo scopo di migliorare gli esistenti protocolli e linguaggi per il World Wide Web e di aiutare il web a sviluppare tutte le sue potenzialità."@it, "O World Wide Web Consortium (W3C) é um consórcio internacional com cerca de 300 membros, que agrega empresas, órgãos governamentais e organizações independentes, e que visa desenvolver padrões para a criação e a interpretação de conteúdos para a Web. Foi fundado por Tim Berners-Lee em 1994 para levar a Web ao seu potencial máximo, por meio do desenvolvimento de protocolos comuns e fóruns abertos que promovam a sua evolução e assegurem a sua interoperabilidade."@pt, "The World Wide Web Consortium (W3C) is the main international standards organization for the World Wide Web (abbreviated WWW or W3). Founded and headed by Tim Berners-Lee, the consortium is made up of member organizations which maintain full-time staff for the purpose of working together in the development of standards for the World Wide Web. As of 18 February 2011, the World Wide Web Consortium (W3C) has 322 members."@en, "W3C eli World Wide Web Consortium on kansainvälinen yritysten ja yhteisöjen yhteenliittymä, joka ylläpitää ja kehittää WWW:n standardeja tai suosituksia kuten W3C niitä kutsuu. Sen perusti vuonna 1994 WWW:n keksijä Tim Berners-Lee, joka toimii nykyisinkin W3C:n johtajana. Konsortiolla on yli 400 jäsentä. Konsortion päämaja on Massachusetts Institute of Technologyn tiloissa Yhdysvalloissa. Muut instituutit, joissa W3C:llä on tutkimusta, ovat ERCIM Ranskassa ja Keio University Japanissa."@fi, "W3C, World Wide Web Consortium, är ett industrikonsortium grundat år 1994 med över 500 medlemmar från ledande industrier, forsknings- och utvecklingsinstitut, standardiseringsorgan och regeringar samt EU. Dessa finansierar verksamheten tillsammans med statliga bidrag. W3C arbetar med att utveckla tekniska protokoll, standarder och programvara för webben med målet att genom ett öppet samarbete leda Internet till dess fulla potential."@sv, "World Wide Web Consortium, forkortet W3C, er en organisasjon som ble startet i oktober 1994. Organisasjonens hovedmål er å utvikle protokoller og standarder for teknologien som brukes på World Wide Web. I den sammenheng tilbyr W3Cs nettsted ulike tjenester for testing eller validering av nettsider, stilark og andre, mer avanserte valideringsverktøy."@no, "World Wide Web Consortium, w skrócie W3C, to organizacja, która zajmuje się ustanawianiem standardów pisania i przesyłu stron WWW. Została założona 1 października 1994 roku przez Tima Berners-Lee, twórcę WWW oraz autora pierwszej przeglądarki internetowej i serwera WWW. W3C jest obecnie zrzeszeniem ponad 400 organizacji, firm, agencji rządowych i uczelni z całego świata. Publikowane przez W3C rekomendacje nie mają mocy prawnej, nakazującej ich użycie."@pl, "World Wide Web Consortium（ワールド・ワイド・ウェブ・コンソーシアム）は、World Wide Webで使用される各種技術の標準化を推進する為に設立された標準化団体、非営利団体。略称はW3C（ダブリュースリーシー）。 ティム・バーナーズ＝リーが創設し、率いている。このコンソーシアムには企業や団体が会員として加入し、専任スタッフと共にWorld Wide Webの標準策定を行っている。2009年9月8日現在、356の組織が会員として加入している。 W3Cはまた教育活動も行っており、ソフトウェアを開発してWebに関するオープンな議論の場を提供している。 HTML、XML、MathML、DOM等の規格を勧告。HTMLは、従来IETFでRFCとして標準化されていたが、HTML 3.2以降はW3Cへと引き継がれた。 XHTMLの規格に不満を持った企業等はW3Cに対抗するWHATWGという対抗団体を立ち上げているが、両団体はHTML5の策定にあたって協力関係にあり、WHATWGによって2004年に定められたWeb Applications 1.0にWeb Forms 2.0を取り入れたものがW3Cの専門委員会に採用され、W3Cより2008年1月22日にドラフト（草案）が発表された。"@ja, "Консо́рциум Всеми́рной паути́ны (англ. World Wide Web Consortium, W3C) — организация, разрабатывающая и внедряющая технологические стандарты для Всемирной паутины. Консорциум возглавляет сэр Тимоти Джон Бернерс-Ли, автор множества разработок в области информационных технологий."@ru, "万维网联盟（Template:Lang，W3C），又称W3C理事会。1994年10月在麻省理工学院计算机科学实验室成立。建立者是互聯網的发明者蒂姆·伯纳斯-李。 为解决web应用中不同平台、技术和开发者带来的不兼容问题，保障Web信息的顺利和完整流通，万维网联盟制定了一系列标准并督促Web应用开发者和内容提供者遵循这些标准。标准的内容包括使用语言的规范，开发中使用的导则和解释引擎的行为等等。W3C也制定了包括XML和CSS等的众多影响深远的标准规范。 但是，W3C制定的web标准似乎并非强制而只是推荐标准。因此部分网站仍然不能完全实现这些标准。特别是使用早期所见即所得网页编辑软件设计的网页往往会包含大量非标准代码。"@zh ;
+ rdfs:label "W3C"@pt, "World Wide Web Consortium"@de, "World Wide Web Consortium"@en, "World Wide Web Consortium"@es, "World Wide Web Consortium"@fi, "World Wide Web Consortium"@fr, "World Wide Web Consortium"@it, "World Wide Web Consortium"@ja, "World Wide Web Consortium"@nl, "World Wide Web Consortium"@no, "World Wide Web Consortium"@pl, "World Wide Web Consortium"@sv, "Консорциум Всемирной паутины"@ru, "万维网联盟"@zh ;
+ owl:sameAs <http://dbpedia.org/resource/World_Wide_Web_Consortium>, <http://rdf.freebase.com/ns/m/082bb> ;
+ foaf:depiction <http://upload.wikimedia.org/wikipedia/commons/e/ec/W3C_logo.svg> ;
+ foaf:homepage <http://www.w3.org/> ;
+ foaf:name "World Wide Web Consortium"@en ;
+ foaf:page <http://en.wikipedia.org/wiki/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/World_wide_web_consortium>
+ dbpedia-owl:wikiPageRedirects <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/XHTML>
+ dbpprop:owner <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/XHTML%2BRDFa>
+ dbpprop:owner <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/XPath>
+ dbpedia-owl:developer <http://dbpedia.org/resource/World_Wide_Web_Consortium> ;
+ dbpprop:developer <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://dbpedia.org/resource/XQuery>
+ dbpedia-owl:designer <http://dbpedia.org/resource/World_Wide_Web_Consortium> ;
+ dbpprop:designer <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://en.wikipedia.org/wiki/World_Wide_Web_Consortium>
+ foaf:primaryTopic <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://mpii.de/yago/resource/World_Wide_Web_Consortium>
+ owl:sameAs <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+
+ <http://www4.wiwiss.fu-berlin.de/flickrwrappr/photos/World_Wide_Web_Consortium>
+ owl:sameAs <http://dbpedia.org/resource/World_Wide_Web_Consortium> .
+}
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/components/NamedGraph/named-graph-topics.trig Mon Oct 10 12:23:53 2011 +0100
@@ -0,0 +1,37 @@
+@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
+@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
+@prefix dcterms: <http://purl.org/dc/terms/> .
+@prefix foaf: <http://xmlns.com/foaf/0.1/> .
+@prefix con: <http://www.w3.org/2000/10/swap/pim/contact#> .
+@prefix sd: <http://www.w3.org/ns/sparql-service-description#> .
+@prefix card: <http://www.w3.org/People/Berners-Lee/card#> .
+@prefix prov: <http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/ProvenanceOntology.owl#> .
+@prefix : <#> .
+
+:about_tbl_card {
+ :tbl_card
+ a sd:NamedGraph;
+ sd:name <http://www.w3.org/People/Berners-Lee/card>;
+ prov:hadLocation <>;
+ dcterms:subject card:i;
+ rdfs:comment "The named graph <http://www.w3.org/People/Berners-Lee/card> in this file is about Tim Berners-Lee.";
+ .
+}
+
+<http://www.w3.org/People/Berners-Lee/card> {
+ card:i rdfs:label "Tim Berners-Lee";
+ con:assistant card:amy .
+}
+
+:about_tbl_card {
+ :about_tbl_card
+ a sd:NamedGraph;
+ sd:name :about_tbl_card;
+ prov:hadLocation <>;
+ dcterms:subject :tbl-card,
+ :about_tbl_card;
+ rdfs:comment "The named graph #about_tbl_card in this file is about two named graphs in this file.";
+ .
+}
+
+
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/components/wasDerivedFrom.ttl Mon Oct 10 12:23:53 2011 +0100
@@ -0,0 +1,11 @@
+@prefix owl: <http://www.w3.org/2002/07/owl#> .
+@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
+@prefix time: <http://www.w3.org/2006/time#> .
+@prefix prov: <http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/ProvenanceOntology.owl#> .
+
+prov:wasDerivedFrom
+ a owl:ObjectProperty;
+ rdfs:label "wasDerivedFrom";
+ rdfs:domain prov:Entity;
+ rdfs:range prov:Entity;
+.
Binary file ontology/diagram-history/2011-10-03-tlebo/ProvenanceOntology.owl.png has changed
--- a/ontology/examples/ontology-extensions/crime-file/diagrams/2011-09-14-dGarijo/AlternativeSchema.graphml Mon Oct 10 12:23:09 2011 +0100
+++ b/ontology/examples/ontology-extensions/crime-file/diagrams/2011-09-14-dGarijo/AlternativeSchema.graphml Mon Oct 10 12:23:53 2011 +0100
@@ -20,57 +20,57 @@
<y:Geometry height="55.0" width="121.0" x="266.0" y="-42.0"/>
<y:Fill color="#99CCFF" transparent="false"/>
<y:BorderStyle hasColor="false" type="line" width="1.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="34.01171875" x="43.494140625" y="18.1494140625">Entity</y:NodeLabel>
+ <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="60.689453125" x="30.1552734375" y="18.1494140625">prov:Entity</y:NodeLabel>
</y:GenericNode>
</data>
</node>
<node id="n1">
<data key="d6">
<y:GenericNode configuration="BevelNode3">
- <y:Geometry height="55.0" width="121.0" x="355.0" y="69.0"/>
+ <y:Geometry height="55.0" width="121.0" x="369.0" y="69.0"/>
<y:Fill color="#99CCFF" transparent="false"/>
<y:BorderStyle hasColor="false" type="line" width="1.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="35.359375" x="42.8203125" y="18.1494140625">Agent</y:NodeLabel>
+ <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="62.037109375" x="29.4814453125" y="18.1494140625">prov:Agent</y:NodeLabel>
</y:GenericNode>
</data>
</node>
<node id="n2">
<data key="d6">
<y:GenericNode configuration="BevelNode3">
- <y:Geometry height="55.0" width="121.0" x="125.0" y="69.0"/>
+ <y:Geometry height="55.0" width="132.0" x="110.0" y="69.0"/>
<y:Fill color="#99CCFF" transparent="false"/>
<y:BorderStyle hasColor="false" type="line" width="1.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="103.380859375" x="8.8095703125" y="18.1494140625">Process Execution</y:NodeLabel>
+ <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="126.724609375" x="2.6376953125" y="18.1494140625">prov:ProcessExecution</y:NodeLabel>
</y:GenericNode>
</data>
</node>
<node id="n3">
<data key="d6">
<y:GenericNode configuration="BevelNode3">
- <y:Geometry height="55.0" width="121.0" x="87.0" y="-42.0"/>
+ <y:Geometry height="55.0" width="121.0" x="84.5" y="-42.0"/>
<y:Fill color="#99CCFF" transparent="false"/>
<y:BorderStyle hasColor="false" type="line" width="1.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="28.6796875" x="46.16015625" y="18.1494140625">Role</y:NodeLabel>
+ <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="55.357421875" x="32.8212890625" y="18.1494140625">prov:Role</y:NodeLabel>
</y:GenericNode>
</data>
</node>
<node id="n4">
<data key="d6">
<y:GenericNode configuration="BevelNode3">
- <y:Geometry height="55.0" width="121.0" x="-47.0" y="209.0"/>
+ <y:Geometry height="55.0" width="121.0" x="-52.0" y="209.0"/>
<y:Fill color="#FF9933" transparent="false"/>
<y:BorderStyle hasColor="false" type="line" width="1.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="72.6953125" x="24.15234375" y="18.1494140625">cf:FileEditing</y:NodeLabel>
+ <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="79.369140625" x="20.8154296875" y="18.1494140625">ext:FileEditing</y:NodeLabel>
</y:GenericNode>
</data>
</node>
<node id="n5">
<data key="d6">
<y:GenericNode configuration="BevelNode3">
- <y:Geometry height="55.0" width="121.0" x="87.0" y="209.0"/>
+ <y:Geometry height="55.0" width="121.0" x="84.5" y="209.0"/>
<y:Fill color="#FF9933" transparent="false"/>
<y:BorderStyle hasColor="false" type="line" width="1.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="81.361328125" x="19.8193359375" y="18.1494140625">cf:FileCreation</y:NodeLabel>
+ <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="88.03515625" x="16.482421875" y="18.1494140625">ext:FileCreation</y:NodeLabel>
</y:GenericNode>
</data>
</node>
@@ -80,47 +80,47 @@
<y:Geometry height="55.0" width="121.0" x="221.0" y="209.0"/>
<y:Fill color="#FF9933" transparent="false"/>
<y:BorderStyle hasColor="false" type="line" width="1.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="93.390625" x="13.8046875" y="18.1494140625">cf:FileAppending</y:NodeLabel>
+ <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="100.064453125" x="10.4677734375" y="18.1494140625">ext:FileAppending</y:NodeLabel>
</y:GenericNode>
</data>
</node>
<node id="n7">
<data key="d6">
<y:GenericNode configuration="BevelNode3">
- <y:Geometry height="55.0" width="150.0" x="355.0" y="209.0"/>
+ <y:Geometry height="55.0" width="158.0" x="355.0" y="209.0"/>
<y:Fill color="#FF9933" transparent="false"/>
<y:BorderStyle hasColor="false" type="line" width="1.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="142.720703125" x="3.6396484375" y="18.1494140625">cf:EmailProcessExecution</y:NodeLabel>
+ <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="149.39453125" x="4.302734375" y="18.1494140625">ext:EmailProcessExecution</y:NodeLabel>
</y:GenericNode>
</data>
</node>
<node id="n8">
<data key="d6">
<y:GenericNode configuration="BevelNode3">
- <y:Geometry height="55.0" width="121.0" x="-47.0" y="69.0"/>
+ <y:Geometry height="55.0" width="121.0" x="-52.0" y="69.0"/>
<y:Fill color="#FF9933" transparent="false"/>
<y:BorderStyle hasColor="false" type="line" width="1.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="93.37890625" x="13.810546875" y="18.1494140625">cf:SpellChecking</y:NodeLabel>
+ <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="100.052734375" x="10.4736328125" y="18.1494140625">ext:SpellChecking</y:NodeLabel>
</y:GenericNode>
</data>
</node>
<node id="n9">
<data key="d6">
<y:GenericNode configuration="BevelNode3">
- <y:Geometry height="55.0" width="121.0" x="512.0" y="-42.0"/>
+ <y:Geometry height="55.0" width="121.0" x="526.0" y="-42.0"/>
<y:Fill color="#FF9933" transparent="false"/>
<y:BorderStyle hasColor="false" type="line" width="1.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="93.390625" x="13.8046875" y="18.1494140625">cf:FileAppending</y:NodeLabel>
+ <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="74.67578125" x="23.162109375" y="18.1494140625">ext:CrimeFile</y:NodeLabel>
</y:GenericNode>
</data>
</node>
<node id="n10">
<data key="d6">
<y:GenericNode configuration="BevelNode3">
- <y:Geometry height="55.0" width="121.0" x="512.0" y="69.0"/>
+ <y:Geometry height="55.0" width="121.0" x="526.0" y="69.0"/>
<y:Fill color="#FF9933" transparent="false"/>
<y:BorderStyle hasColor="false" type="line" width="1.0"/>
- <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="68.025390625" x="26.4873046875" y="18.1494140625">cf:Journalist</y:NodeLabel>
+ <y:NodeLabel alignment="center" autoSizePolicy="content" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="internal" modelPosition="c" textColor="#000000" visible="true" width="74.69921875" x="23.150390625" y="18.1494140625">ext:Journalist</y:NodeLabel>
</y:GenericNode>
</data>
</node>
@@ -145,7 +145,6 @@
</data>
</node>
<node id="n13">
- <data key="d5"/>
<data key="d6">
<y:ShapeNode>
<y:Geometry height="30.0" width="121.0" x="44.0" y="290.5"/>
@@ -157,7 +156,6 @@
</data>
</node>
<node id="n14">
- <data key="d5"/>
<data key="d6">
<y:ShapeNode>
<y:Geometry height="30.0" width="121.0" x="55.0" y="326.0"/>
@@ -177,7 +175,7 @@
</y:Path>
<y:LineStyle color="#000000" type="line" width="1.0"/>
<y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="six_pos" modelPosition="tail" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="203.388671875" x="-30.074432373046875" y="-32.67512893676758">wasDerivedFrom, wasComplementOf</y:EdgeLabel>
+ <y:EdgeLabel alignment="center" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="six_pos" modelPosition="tail" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="256.744140625" x="-30.074432373046875" y="-32.67512893676758">prov:wasDerivedFrom, prov:wasComplementOf</y:EdgeLabel>
<y:BendStyle smoothed="false"/>
</y:PolyLineEdge>
</data>
@@ -188,7 +186,7 @@
<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" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="six_pos" modelPosition="tail" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="94.041015625" x="7.475341796875" y="2.0">wasControlledBy</y:EdgeLabel>
+ <y:EdgeLabel alignment="center" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="six_pos" modelPosition="tail" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="120.71875" x="3.13531494140625" y="2.0">prov:wasControlledBy</y:EdgeLabel>
<y:BendStyle smoothed="false"/>
</y:PolyLineEdge>
</data>
@@ -199,7 +197,7 @@
<y:Path sx="0.0" sy="0.0" tx="0.0" ty="-27.50244140625"/>
<y:LineStyle color="#000000" type="line" width="1.0"/>
<y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="six_pos" modelPosition="thead" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="96.05078125" x="-175.5193545424025" y="27.17426586151123">wasGeneratedBy</y:EdgeLabel>
+ <y:EdgeLabel alignment="center" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="six_pos" modelPosition="thead" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="122.728515625" x="-207.4166027207913" y="27.17426586151123">prov:wasGeneratedBy</y:EdgeLabel>
<y:BendStyle smoothed="false"/>
</y:PolyLineEdge>
</data>
@@ -207,10 +205,10 @@
<edge id="e3" source="n2" target="n0">
<data key="d10">
<y:PolyLineEdge>
- <y:Path sx="11.0" sy="-2.5" tx="11.0" ty="-0.5"/>
+ <y:Path sx="11.999999999999998" sy="-2.5" tx="11.0" ty="-0.5"/>
<y:LineStyle color="#000000" type="line" width="1.0"/>
<y:Arrows source="none" target="standard"/>
- <y:EdgeLabel alignment="center" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="six_pos" modelPosition="tail" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="30.021484375" x="50.331370502436926" y="-37.362548828125">used</y:EdgeLabel>
+ <y:EdgeLabel alignment="center" distance="2.0" fontFamily="Dialog" fontSize="12" fontStyle="plain" hasBackgroundColor="false" hasLineColor="false" height="18.701171875" modelName="six_pos" modelPosition="tail" preferredPlacement="anywhere" ratio="0.5" textColor="#000000" visible="true" width="56.69921875" x="53.24496375967607" y="-37.362548828125">prov:used</y:EdgeLabel>
<y:BendStyle smoothed="false"/>
</y:PolyLineEdge>
</data>
Binary file ontology/examples/ontology-extensions/crime-file/diagrams/2011-09-14-dGarijo/AlternativeSchema.png has changed
Binary file ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.classes.pdf has changed
Binary file ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.classes.png has changed
Binary file ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.pdf has changed
Binary file ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.png has changed
Binary file ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.properties.pdf has changed
Binary file ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.properties.png has changed
--- a/primer/Primer.html Mon Oct 10 12:23:09 2011 +0100
+++ b/primer/Primer.html Mon Oct 10 12:23:53 2011 +0100
@@ -123,9 +123,7 @@
<section>
<h3>Provenance as data</h3>
- <p>Describes a common pattern of production of Prov-DM data, e.g. the asserter being software
- enacting the process that it is asserting about, to clarify who might be using the model
- and in what context.</p>
+ <p>Explains the contexts in which the reader may see or create Prov-DM data.</p>
</section>
</section>
@@ -164,7 +162,7 @@
<section>
<h3>Accounts</h3>
- <p>An intuitive overview of how to think about use and generation events in Prov-DM.</p>
+ <p>An intuitive overview of how to think about accounts in Prov-DM.</p>
</section>
<section>