# HG changeset patch
# User paulb
# Date 1202233348 0
# Node ID c5da110fbcba9e190c2efb43c34a86ed3243334c
# Parent  185f79ad2450fe6538aefb3198e4fbe58d275ce1
[project @ 2008-02-05 17:42:28 by paulb]
Added a note about specifying a context element for multiple-choice fields.

diff -r 185f79ad2450 -r c5da110fbcba docs/multiple.html
--- a/docs/multiple.html	Tue Feb 05 17:25:31 2008 +0000
+++ b/docs/multiple.html	Tue Feb 05 17:42:28 2008 +0000
@@ -276,8 +276,25 @@
 </ol>
 
 <p>The result of this should be a processed <code>structure</code>
-document containing the type values for each <code>type</code>
-element in that document.</p>
+document containing the type values for each <code>type-enum</code>
+element in that document found under the <code>type</code> element
+(as specified in the <code>template:multiple-choice-field</code>
+attribute).</p>
+
+<h3>Specifying a Context Element</h3>
+
+<p>Note that the feature of <code>template:multiple-choice-field</code>
+where the context element is specified as <code>-</code>, meaning the
+element on which the attribute for the field will be found, has
+implications for the naming of the root element in the document
+providing the values for a multiple-choice field: such elements need
+to be named after this context element, and it is frequently less
+inconvenient (and more obvious) to explicitly state a context element
+instead of adopting the name of the current element from the template.
+One situation where the current element might be more convenient as
+the context element is where many multiple-choice fields are to be
+supplied by the same document containing each range of values for all
+the different fields.</p>
 
 <h2>Other Multiple-Choice Data</h2>