provenanceContainer renamed to recordContainer
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Tue, 08 Nov 2011 16:04:40 +0000
changeset 849 b4bb824d3884
parent 848 18461da0324f
child 850 7ef37443dc30
child 851 ab5aa7c910f0
provenanceContainer renamed to recordContainer
model/ProvenanceModel.html
--- a/model/ProvenanceModel.html	Tue Nov 08 15:13:51 2011 +0000
+++ b/model/ProvenanceModel.html	Tue Nov 08 16:04:40 2011 +0000
@@ -643,7 +643,7 @@
 <p>PROV-DM consists of a set of constructs, referred to as <em>records</em>, to formulate representations of the world and constraints that must be satisfied by them.</p>
 
 <p>
-Furthermore,  PROV-DM includes a "house-keeping construct", 
+Furthermore,  PROV-DM includes a "house-keeping construct", a record container,
  used to wrap PROV-DM records and facilitate their interchange.</p>
 
 <p>In PROV-ASN, such representations of the world MUST be conformant with the toplevel production <span class="nonterminal">record</span> of the grammar. These <span class="nonterminal">record</span>s are grouped in three categories:
@@ -680,7 +680,7 @@
 </div>
 
 
-<p>In PROV-ASN, a provenanceContainer is compliant with the production <span class="nonterminal">provenanceContainer</span> (see section <a href="#ProvenanceContainer">Provenance Container</a>). </p>
+<p>In PROV-ASN, a record container is compliant with the production <span class="nonterminal">recordContainer</span> (see section <a href="#RecordContainer">Record Container</a>). </p>
 
 </section>
 
@@ -928,7 +928,7 @@
 <span class="nonterminal">Literal</span>
 </div>
 
-<p>A separate PROV-DM record is used to associate an annotation with an record (see <a href="#record-annotationAssociation">Section on annotation association</a>). A given annotation may be associated with multiple records.
+<p>A separate PROV-DM record is used to associate an annotation with a record (see <a href="#record-annotationAssociation">Section on annotation association</a>). A given annotation may be associated with multiple records.
 </p>
 
 
@@ -1693,7 +1693,7 @@
 
 <div class='constraint' id='wasRevision'>
 Given two identifiers <span class="name">old</span> and <span class="name">new</span> identifying two entities, and an identifier <span class="name">ag</span> identifying an agent,
-<span class='conditional'>if</span> an record <span class="name">wasRevisionOf(new,old,ag)</span> is asserted, <span class='conditional'>then</span> 
+<span class='conditional'>if</span> a record <span class="name">wasRevisionOf(new,old,ag)</span> is asserted, <span class='conditional'>then</span> 
 there exists an entity record identifier <span class="name">e</span> and attribute-values <span class="name">av</span>, such that the following records hold:
 <ul>
 <li> <span class="name">wasEventuallyDerivedFrom(new,old)</span>;
@@ -1838,11 +1838,12 @@
 <section  id="bundle">
 <h3>Bundle</h3>
 
-In this section, two constructs are introduced to group
+<p>In this section, two constructs are introduced to group
 PROV-DM records.  The first
-one, <span class="nonterminal">accountRecord</span> is itself an
+one, <span class="nonterminal">accountRecord</span> is itself a
 record, whereas the second
-one <span class="nonterminal">provenanceContainer</span> is not.
+one <span class="nonterminal">recordContainer</span> is not.
+</p>
 
 
 <section id="record-Account">
@@ -1950,7 +1951,7 @@
 </pre>
 <p>with identifier <span class="name">acc2</span>, containing assertions by asserter by <span class="name">http://example.org/asserter2</span> stating that the entity represented by entity record identified by <span class="name">e0</span> was generated by an activity represented by activity record 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 records violates <a href="#generation-unicity">generation-unicity</a>.</p>
 
-<p>Account records constitue a scope for identifiers. Since accounts can be nested, their scope can also be nested; thus, the scope of identifiers should be understood in the context of such nested scopes.  When an record with an identifier occurs directly within an account, then its identifier denotes this record in the scope of this account, except in sub-accounts where records with the same identifier occur. </p>
+<p>Account records constitue a scope for identifiers. Since accounts can be nested, their scope can also be nested; thus, the scope of identifiers should be understood in the context of such nested scopes.  When a record with an identifier occurs directly within an account, then its identifier denotes this record in the scope of this account, except in sub-accounts where records with the same identifier occur. </p>
 
 <p>
 The following account record is inspired from section <a href="#example-prov-asn-encoding">example-prov-asn-encoding</a>. This account, identified by <span class="name">acc3</span>, declares entity record identified by <span class="name">e0</span>, which is being referred to in the nested account <span class="name">acc4</span>. The scope of identifier <span class="name">e0</span> is account <span class="name">acc3</span>, including subaccount <span class="name">acc4</span>.</p>
@@ -1978,17 +1979,17 @@
 
 </section>
 
-<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 records. A provenance container is not an record, 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>
+<section id="RecordContainer">
+<h4>Record Container</h4>
+
+<p>A <dfn id="dfn-RecordContainer">record container</dfn> is a house-keeping construct of PROV-DM, also capable of bundling PROV-DM records. A record container is not a record, 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 record container's text matches the <span class="nonterminal">recordContainer</span> production of the grammar defined in this specification document.</p>
 
 
 <div class='grammar'>
-<span class="nonterminal">provenanceContainer</span>&nbsp;:=  
-<span class="name">provenanceContainer</span> 
+<span class="nonterminal">recordContainer</span>&nbsp;:=  
+<span class="name">recordContainer</span> 
 <span class="name">(</span> 
 { <span class="nonterminal">namespaceDeclaration</span> }
 <span class="name">,</span> 
@@ -1998,7 +1999,7 @@
 <span class="name">)</span> 
 </div>
 
-<p>A provenance container, written <span class="name">provenanceContainer(decls, ids, exprs)</span> in PROV-ASN:
+<p>A record container, written <span class="name">recordContainer(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>
@@ -2116,7 +2117,7 @@
 <span class="nonterminal">attribute</span>&nbsp;:=  
 <em>a qualified name</em></div>
 
-<p>If a namespace prefix occurs in the qualified name, it refers to a namespace declared in the provenance container.</p>
+<p>If a namespace prefix occurs in the qualified name, it refers to a namespace declared in the record container.</p>
 </section>
 
 
@@ -2129,7 +2130,7 @@
 <div class='grammar'>
 <span class="nonterminal">name</span>&nbsp;:=  
 <em>a qualified name</em></div>
-<p>If a namespace prefix occurs in the qualified name, it refers to a namespace declared in the provenance container.</p>
+<p>If a namespace prefix occurs in the qualified name, it refers to a namespace declared in the record container.</p>
 
 <div class='note'>Proposed to adopt the abbreviatedIRI definition of OWL2 [[!OWL2-SYNTAX]]
 (see section <a href="http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#IRIs">IRIs</a>).
@@ -2710,6 +2711,7 @@
 <section class="appendix"> 
       <h2>Changes Since Previous Version</h2> 
 <ul>
+<li>11/08/11: Renamed 'provenance container' into 'record container'.</li>
 <li>11/07/11: Addressed ISSUE-143 (qualifiers as a set of name value pairs).</li>
 <li>11/07/11: Added a section on Literals (ISSUE-142).</li>
 <li>11/07/11: Aligned terminology 'activity' and 'process execution record'.</li>