1.1 --- a/README.txt Thu Jul 21 18:50:52 2005 +0000
1.2 +++ b/README.txt Thu Jul 21 20:13:45 2005 +0000
1.3 @@ -69,5 +69,21 @@
1.4 server; one workaround is to use real host names or addresses instead of
1.5 'localhost'.
1.6
1.7 -Choosing an element-path.
1.8 -Choosing where to put template:attribute, id and template:id.
1.9 +Choosing an element-path:
1.10 +
1.11 +When specifying the "context" of the in-page update, one must imagine which
1.12 +element the template fragment should operate within. If the template:id
1.13 +attribute marks a particular section, then the element-path should be a path
1.14 +to the applicable context element for that section in the complete template
1.15 +document. Note that if a template:element attribute appears on the same
1.16 +element as the template:id attribute then the element-path should refer to the
1.17 +element specified in the template:element attribute.
1.18 +
1.19 +Choosing where to put template:attribute, template:id and id:
1.20 +
1.21 +When specifying the extent of a template fragment, one must be sure not to put
1.22 +the template:id attribute on the same element as a template:attribute
1.23 +annotation; otherwise, the generated code will be improperly extracted as a
1.24 +fragment producing two versions of the element - one for when the specified
1.25 +attribute is present, and one for when it is not present. Generally,
1.26 +template:id and id can be placed on the same node, however.