# HG changeset patch
# User Jeff Hammel <jhammel@mozilla.com>
# Date 1364082640 25200
# Node ID 872f98a484d2aa7777e467c722249c0c56a0cf27
# Parent  c95f1dfed329850308a4cc51911590b62adc9b5e
note about audiences

diff -r c95f1dfed329 -r 872f98a484d2 README.txt
--- a/README.txt	Tue Mar 02 11:44:10 2010 -0500
+++ b/README.txt	Sat Mar 23 16:50:40 2013 -0700
@@ -13,9 +13,9 @@
 
 <URL pattern>#<xpath pattern> -> URL
 
-The URL pattern is a 
+The URL pattern is a
 `python regular expression <ttp://docs.python.org/library/re.html>`_
-to match against the request's PATH_INFO.  
+to match against the request's PATH_INFO.
 
 The xpath pattern is where you want to place the comments on the
 page.  See http://www.w3schools.com/XPath/ for more about xpath
@@ -70,6 +70,23 @@
  * locking pickle files
  * fix couch....not sure what's wrong
  * allow use of CSS classes, not just xpath
+ * tests!
+
+Types of comments:
+
+A generalize comment (stream) is a *discussion* content type.  As
+such, in general you could include the standard *((string)key, value)*
+metadata with each comment.
+
+More actionably, a single field, *audience*, is often sufficient.
+While the general form is out-of-scope (for now) for commentator,
+adding an audience would go some ways towards comment effectivity.
+
+Examples of audiences:
+
+* original author : especially useful for site comments
+* discussion : everyone participating
+
 
 --