--- a/model/prov-dm-constraints.html	Thu Mar 08 21:55:07 2012 +0000
+++ b/model/prov-dm-constraints.html	Thu Mar 08 22:12:23 2012 +0000
@@ -821,13 +821,9 @@
 
 
 
-<div class='pending'>Several points were raised about the attribute steps.
-Its name, its default value   <a href="http://www.w3.org/2011/prov/track/issues/180">ISSUE-180</a>.
- <a href="http://www.w3.org/2011/prov/track/issues/179">ISSUE-179</a>.</div>
 
 <div class='issue'> Emphasize the notion of 'affected by'   <a href="http://www.w3.org/2011/prov/track/issues/133">ISSUE-133</a>.</div>
 
-<div class='pending'> Simplify derivation   <a href="http://www.w3.org/2011/prov/track/issues/249">ISSUE-249</a>.</div>
 
 
 
@@ -1026,7 +1022,6 @@
 <li> <span class="name">specializationOf(new,e)</span>;
 <li> <span class="name">specializationOf(old,e)</span>.
 </ul>
-The derivation may be imprecise-1 or imprecise-n.
 </div>
 
 <p><span class="name">wasRevisionOf</span> is a strict sub-relation
@@ -1255,7 +1250,7 @@
 
 <p>If there is a derivation between <span class="name">e2</span> and <span class="name">e1</span>, then 
 this means that the entity <span class="name">e1</span> had some form of influence on the entity <span class="name">e2</span>; for this to be possible, some event ordering must be satisfied.
-First, we consider one-activity derivations. In that case, the <a title="entity usage event">usage</a> of <span class="name">e1</span> has to precede the <a title="entity generation
+First, we consider derivations, where the activity and usage are known. In that case, the <a title="entity usage event">usage</a> of <span class="name">e1</span> has to precede the <a title="entity generation
 event">generation</a> of <span class="name">e2</span>.
 This is
 illustrated by Subfigure <a href="#constraint-summary">constraint-summary</a> (e) and  expressed by constraint <a
@@ -1265,21 +1260,21 @@
 <div class='interpretation' id='derivation-usage-generation-ordering'>Given an activity with identifier <span class="name">a</span>,  entities with identifier <span
 class="name">e1</span> and <span class="name">e2</span>, a generation identified by <span class="name">g2</span>, and a usage identified by <span class="name">u1</span>, <span
 class='conditional'>if</span> <span class="name">wasDerivedFrom(e2,e1,a,g2,u1,attrs)</span>
-or <span class="name">wasDerivedFrom(e2,e1,[prov:steps="single"] &cup; attrs)</span> holds, <span class='conditional'>then</span>
+ holds, <span class='conditional'>then</span>
 the following ordering constraint holds:
 the <a title="entity usage event">usage</a>
 of entity denoted by <span class="name">e1</span> <a>precedes</a> the <a title="entity generation event">generation</a> of
 the entity denoted by <span class="name">e2</span>.
 </div>
 
-<p>For imprecise-n derivations, a similar constraint exists, but in this case, no usage can be inferred for <span class="name">e1</span>. Instead, the constraint refers to its
+<p>When the usage is unknown, a similar constraint exists, except that the constraint refers to its
 generation event, as
 illustrated by Subfigure <a href="#constraint-summary">constraint-summary</a> (f) and  expressed by constraint <a
 href="#derivation-generation-generation-ordering">derivation-generation-generation-ordering</a>.</p>
 
 <div class='interpretation' id='derivation-generation-generation-ordering'>
 Given two entities denoted by <span class="name">e1</span> and <span class="name">e2</span>, <span class='conditional'>if</span> <span
-class="name">wasDerivedFrom(e2,e1,[prov:steps="any"] &cup; attrs)</span>
+class="name">wasDerivedFrom(e2,e1, attrs)</span>
  holds, <span class='conditional'>then</span> the following ordering constraint holds:
 the <a title="entity generation event">generation event</a> of the entity denoted by <span class="name">e1</span> <a>precedes</a> the <a title="entity generation event">generation event</a>
 of
@@ -1287,11 +1282,9 @@
   </div>
 
 <p>Note that event ordering is between generations of <span class="name">e1</span>
-and <span class="name">e2</span>, as opposed to precise-1 derivation,
+and <span class="name">e2</span>, as opposed to derivation where usage is known,
 which implies ordering ordering between the usage of <span class="name">e1</span> and
-generation of <span class="name">e2</span>.  Indeed, in the case of
-imprecise-n derivation, nothing is known about the usage of <span class="name">e1</span>,
-since there is no associated activity.</p>
+generation of <span class="name">e2</span>.  </p>
 
 <p> Information flow ordering between two activities <span class="name">a1</span> and <span class="name">a2</span> also implies ordering of <a
 title="event">events</a> in the world, since some entity must have been generated by the former and used by the later, which implies that the start event of  <span class="name">a1</span>

--- a/model/prov-dm.html	Thu Mar 08 21:55:07 2012 +0000
+++ b/model/prov-dm.html	Thu Mar 08 22:12:23 2012 +0000
@@ -1600,22 +1600,6 @@
 </div>
 </section>
 
-<section id="term-attribute-steps">
-<h4>prov:steps</h4>
-
-<p> The  attribute <dfn title="dfn-steps"><span class="name">prov:steps</span></dfn>  defines the level of precision associated with a derivation. The value associated with a <span
-class="name">prov:steps</span> attribute  MUST be   <span class="name">"single"</span> or <span class="name">"any"</span>. The attribute <span class="name">prov:steps</span> occurs at most
-once in a derivation. A derivation  without attribute <span class="name">prov:steps</span> is considered to be equivalent to the same derivation extended with an extra attribute 
-<span class="name">prov:steps</span> and associated value <span class="name">"any"</span>. </p>
-
-<div class="anexample">
-<p>The following expression declares an imprecise-1 derivation, which is known to involve one activity, though its identity, usage details of <span class="name">ex:e1</span>, and generation
-details of <span class="name">ex:e2</span> are not explicit.</p>
-<pre class="codeexample">
-   wasDerivedFrom(ex:e2, ex:e1, [prov:steps="single"])
-</pre>
-</div>
-</section>
 
 <section id="term-attribute-label">
 <h4>prov:label</h4>

--- a/model/prov-n.html	Thu Mar 08 21:55:07 2012 +0000
+++ b/model/prov-n.html	Thu Mar 08 22:12:23 2012 +0000
@@ -749,29 +749,13 @@
 <span class="name">,</span>
 <span class="nonterminal">uIdentifier</span>
 <span class="nonterminal">optional-attribute-values</span>
-<span class="name">)</span><br/>
-|
-<span class="name">wasDerivedFrom</span>
-<span class="name">(</span>
-<span class="optional"> <span class="nonterminal">identifier</span>,</span>
-<span class="nonterminal">eIdentifier</span>
-<span class="name">,</span>
-<span class="nonterminal">eIdentifier</span>
-<span class="optional"><span class="name">,</span>
-<span class="nonterminal">time</span></span>
-<span class="nonterminal">optional-attribute-values</span>
 <span class="name">)</span>
 </div>
-<p>
-The first clause of the alternative, where the activity, generation and usage record identifiers are present formalizes a derivation record is precise-1. The second clause of the alternative, with optional time formalizes imprecise records. The distinction between imprecise-1 and imprecise-n is made by the 
-attribute <span class="name">prov:steps</span>.  
-</p>
 </div>
 
 <div class="anexample">
 <pre class="codeexample">
 wasDerivedFrom(tr:WD-prov-dm-20111215, tr:WD-prov-dm-20111018)
-wasDerivedFrom(tr:WD-prov-dm-20111215, tr:WD-prov-dm-20111018)
 wasDerivedFrom(e2, e1, a, g2, u1)
 </pre>