# HG changeset patch
# User paulb
# Date 1121976825 0
# Node ID 19d400c3a10127c1b64ec2c24a476ff88c35bdbb
# Parent  af4ceeda46c4f3fb0e0cd33a12ba753bb25f3049
[project @ 2005-07-21 20:13:45 by paulb]
Added reminder texts.

diff -r af4ceeda46c4 -r 19d400c3a101 README.txt
--- a/README.txt	Thu Jul 21 18:50:52 2005 +0000
+++ b/README.txt	Thu Jul 21 20:13:45 2005 +0000
@@ -69,5 +69,21 @@
 server; one workaround is to use real host names or addresses instead of
 'localhost'.
 
-Choosing an element-path.
-Choosing where to put template:attribute, id and template:id.
+Choosing an element-path:
+
+When specifying the "context" of the in-page update, one must imagine which
+element the template fragment should operate within. If the template:id
+attribute marks a particular section, then the element-path should be a path
+to the applicable context element for that section in the complete template
+document. Note that if a template:element attribute appears on the same
+element as the template:id attribute then the element-path should refer to the
+element specified in the template:element attribute.
+
+Choosing where to put template:attribute, template:id and id:
+
+When specifying the extent of a template fragment, one must be sure not to put
+the template:id attribute on the same element as a template:attribute
+annotation; otherwise, the generated code will be improperly extracted as a
+fragment producing two versions of the element - one for when the specified
+attribute is present, and one for when it is not present. Generally,
+template:id and id can be placed on the same node, however.