--- a/model/ProvenanceModel.html	Tue Nov 29 21:54:29 2011 +0000
+++ b/model/ProvenanceModel.html	Tue Nov 29 22:05:55 2011 +0000
@@ -2228,6 +2228,17 @@
 
 <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>
+
+
+<p>A record container, written <span class="name">recordContainer(decls, ids, exprs)</span> in PROV-ASN, contains:
+<ul>
+<li><em>namespaceDeclarations</em>: 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><em>accounts</em>: a set of identifiers <span class="name">ids</span> for all accounts occurring (at any nesting level) in  <span class="name">exprs</span>;</li>
+<li><em>records</em>:  a non-empty set of records <span class="name">exprs</span>.</li>
+</ul>
+<p>All the records in <span class="name">exprs</span> are implictly wrapped in a default account, scoping all the record identifiers they declare directly, and constituting a toplevel account, in the hierarchy of accounts.  Consequently, every provenance record 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>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>
 
 
@@ -2243,24 +2254,17 @@
 <span class="name">)</span> 
 </div>
 
-<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>
-<li> contains one or more  records <span class="name">exprs</span>.</li>
-</ul>
-<p>All the records 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 record is always expressed in the context of an account, either explicitly in an asserted account, or implicitly in a container's default account.</p>
 
 <div class="anexample">
 <p>
 The following container </p>
 <pre class="codeexample">
-container(x: http://example.org/,
-          [acc1,acc2]
-          account(acc1,http://example.org/asserter1,...)
-          account(acc2,http://example.org/asserter1,...))
+container(ex: http://example.org/,
+          ex:acc1 ex:acc2,
+          account(ex:acc1,http://example.org/asserter1,...)
+          account(ex:acc2,http://example.org/asserter1,...))
 </pre>
-<p> illustrates how two accounts with identifiers <span class="name">acc1</span> and <span class="name">acc2</span> can be returned in a PROV-ASN serialization of the provenance of something.
+<p> illustrates how two accounts with identifiers <span class="name">ex:acc1</span> and <span class="name">ex:acc2</span> can be returned in a PROV-ASN serialization of the provenance of something.
 </p>
 </div>