--- a/bestpractices/BestPractices.html	Mon Apr 16 07:54:51 2012 -0400
+++ b/bestpractices/BestPractices.html	Mon Apr 16 09:01:20 2012 -0400
@@ -1122,6 +1122,19 @@
         </section>
 	  </section>	    			
 	</section>
+
+   <section>
+      <h2>Using strings</h2>
+      Issues <a href="http://www.w3.org/2011/prov/track/issues/248">248</a> and <a href="http://www.w3.org/2011/prov/track/issues/222">222</a>.
+      prov:used is defined as an objectproperty. If the parameter to a program is a string, and we want to say that the invocation used the string, how do we model that?
+
+      This is only a concern if you want to be DL compliant. If you don't care about being DL compliant, then just do it.
+      Another concern is that tools will expect a resource instead of a string and will not handle it correctly.
+
+      <a href="http://www.w3.org/TR/Content-in-RDF10/">Content in RDF</a> can be used to model string values while maintaining the datatype/objectproperty distinction and complying with PROV-O.
+      Also,  resource can use the rdf:value property to store the string value. We recommend NOT using a blank node, but to derive the URI from the string itself (using a hash) or just a UUID.
+   </section>
+
     <section class='appendix'>
       <h2>Acknowledgements</h2>
       <p>