provo html tweaks
authorTim L <lebot@rpi.edu>
Tue, 17 Jul 2012 11:43:55 -0400
changeset 4097 48db47fa4ffe
parent 4096 c6640f73aeb8
child 4098 bc1b30e53419
provo html tweaks
ontology/prov-o-html-sections/description-qualified-terms.inc.html
--- a/ontology/prov-o-html-sections/description-qualified-terms.inc.html	Tue Jul 17 11:42:35 2012 -0400
+++ b/ontology/prov-o-html-sections/description-qualified-terms.inc.html	Tue Jul 17 11:43:55 2012 -0400
@@ -102,7 +102,7 @@
             It is correct and acceptable for an implementer to use either qualified or unqualified forms as they choose (or both), 
             and a consuming application should be prepared to recognize either form.
             Because the qualification form is more verbose, the unqualified form should be favored in cases where additional properties are not provided.
-            When the qualified form is expressed, including the equivalent unqualified form will facilitate PROV-O consumption.
+            When the qualified form is expressed, including the equivalent unqualified form can facilitate PROV-O consumption, and is thus encouraged.
         </p>
             <!-- To simplify client queries, 
             any qualified relation SHOULD be accompanied by the equivalent unqualified statement.