# HG changeset patch
# User paulb
# Date 1121989991 0
# Node ID e1a71337517ab7e27b14e99eb3b25231c1867f86
# Parent  c35d6e4c9c89678038f9eff0b478bd9ca6bb68db
[project @ 2005-07-21 23:53:11 by paulb]
Added notes about in-page updates and the potential side-effects of certain
choices of target regions.

diff -r c35d6e4c9c89 -r e1a71337517a README.txt
--- a/README.txt	Thu Jul 21 23:03:29 2005 +0000
+++ b/README.txt	Thu Jul 21 23:53:11 2005 +0000
@@ -87,3 +87,29 @@
 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.
+
+Stable element ordering and element-path:
+
+Within the element-path, the numbering of the elements will start at 1.
+Therefore it is vital to choose a region of the form data structure with the
+element-path which is isolated from surrounding elements whose positions would
+otherwise be dependent on a stable ordering of elements, and whose processing
+would be disrupted if some new elements suddenly appeared claiming the same
+positions in the document. For example:
+
+  <item value="">         .../item$1/value
+    <type value=""/>      .../item$1/type$1/value
+    <comment value=""/>   .../item$1/comment$2/value
+  </item>
+
+  In-page update...
+
+  <comment value=""/>     .../item$1/comment$1/value
+
+Notes on XSL
+------------
+
+libxslt seems to be quite liberal on the definition of runtime parameters, in
+that there is no apparent need to explicitly declare the corresponding global
+variables in stylesheets. Whilst this is nice, we may eventually need to
+detect such variables and add them in the preparation process.