1.1 --- a/README.txt Thu Jul 21 23:03:29 2005 +0000
1.2 +++ b/README.txt Thu Jul 21 23:53:11 2005 +0000
1.3 @@ -87,3 +87,29 @@
1.4 fragment producing two versions of the element - one for when the specified
1.5 attribute is present, and one for when it is not present. Generally,
1.6 template:id and id can be placed on the same node, however.
1.7 +
1.8 +Stable element ordering and element-path:
1.9 +
1.10 +Within the element-path, the numbering of the elements will start at 1.
1.11 +Therefore it is vital to choose a region of the form data structure with the
1.12 +element-path which is isolated from surrounding elements whose positions would
1.13 +otherwise be dependent on a stable ordering of elements, and whose processing
1.14 +would be disrupted if some new elements suddenly appeared claiming the same
1.15 +positions in the document. For example:
1.16 +
1.17 + <item value=""> .../item$1/value
1.18 + <type value=""/> .../item$1/type$1/value
1.19 + <comment value=""/> .../item$1/comment$2/value
1.20 + </item>
1.21 +
1.22 + In-page update...
1.23 +
1.24 + <comment value=""/> .../item$1/comment$1/value
1.25 +
1.26 +Notes on XSL
1.27 +------------
1.28 +
1.29 +libxslt seems to be quite liberal on the definition of runtime parameters, in
1.30 +that there is no apparent need to explicitly declare the corresponding global
1.31 +variables in stylesheets. Whilst this is nice, we may eventually need to
1.32 +detect such variables and add them in the preparation process.