1.1 --- a/docs/multiple.html Tue Feb 05 17:25:31 2008 +0000
1.2 +++ b/docs/multiple.html Tue Feb 05 17:42:28 2008 +0000
1.3 @@ -276,8 +276,25 @@
1.4 </ol>
1.5
1.6 <p>The result of this should be a processed <code>structure</code>
1.7 -document containing the type values for each <code>type</code>
1.8 -element in that document.</p>
1.9 +document containing the type values for each <code>type-enum</code>
1.10 +element in that document found under the <code>type</code> element
1.11 +(as specified in the <code>template:multiple-choice-field</code>
1.12 +attribute).</p>
1.13 +
1.14 +<h3>Specifying a Context Element</h3>
1.15 +
1.16 +<p>Note that the feature of <code>template:multiple-choice-field</code>
1.17 +where the context element is specified as <code>-</code>, meaning the
1.18 +element on which the attribute for the field will be found, has
1.19 +implications for the naming of the root element in the document
1.20 +providing the values for a multiple-choice field: such elements need
1.21 +to be named after this context element, and it is frequently less
1.22 +inconvenient (and more obvious) to explicitly state a context element
1.23 +instead of adopting the name of the current element from the template.
1.24 +One situation where the current element might be more convenient as
1.25 +the context element is where many multiple-choice fields are to be
1.26 +supplied by the same document containing each range of values for all
1.27 +the different fields.</p>
1.28
1.29 <h2>Other Multiple-Choice Data</h2>
1.30