[4suite-checkins] In 4Suite/docs/xml/CoreManualSections, files XPointer.xml

[Mike Brown]

Update of /var/local/cvsroot/4Suite/docs/xml/CoreManualSections
In directory gonzaga:/tmp/cvs-serv5487/docs/xml/CoreManualSections

Modified Files:
	XPointer.xml 
Log Message:
further copy edits

ViewCVS diff:
  http://cvs.4suite.org/viewcvs/4Suite/docs/xml/CoreManualSections/XPointer.xml.diff?r1=1.3&r2=1.4
ViewCVS view:
  http://cvs.4suite.org/viewcvs/4Suite/docs/xml/CoreManualSections/XPointer.xml?rev=1.4&content-type=text/vnd.viewcvs-markup

Index: XPointer.xml
===================================================================
RCS file: /var/local/cvsroot/4Suite/docs/xml/CoreManualSections/XPointer.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -U2 -r1.3 -r1.4
--- XPointer.xml	17 Aug 2006 01:02:28 -0000	1.3
+++ XPointer.xml	17 Aug 2006 01:11:41 -0000	1.4
@@ -37,5 +37,5 @@
     since <code>id()</code> is limited to DTD-based data typing.</para>
 
-    <para>A <firstterm>scheme-based</firstterm> XPointer consists of a series
+    <para>A <firstterm>scheme-based XPointer</firstterm> consists of a series
     of one or more <firstterm baseterm="part">parts</firstterm>, separated by
     optional whitespace, with each part looking like a function call. What
@@ -83,20 +83,21 @@
     <para>4Suite's XPointer implementation, sometimes called 4XPointer, has no
     command-line interface, but can be used within Python applications. It
-    supports XPointers in several ways:</para>
+    supports XPointers to different degrees, depending on the circumstances:</para>
 
-    <para>When an XML document is being parsed into a Domlette and XInclude
-    processing is active, any XPointer encountered in an
+    <para>1. When an XML document is being parsed into a Domlette
+    with XInclude processing enabled, any XPointer encountered in an
     <code>xi:include</code> element is automatically evaluated when the
     included document is parsed. Shorthand XPointers are not currently
-    supported, and the XPointer must be "streamable" —which in our case
-    means it must use the <code>xpointer</code> scheme (<code>element</code>
-    is not supported), and must use an XPath LocationPath that only uses
-    steps along the child axis. Furthermore, any predicates must be literal
-    numbers, or must be of the form <code>[@attname='attvalue']</code>.
-    For example, <code>/foo[3]</code> and <code>/foo[@bar='baz']</code> will
-    work, but <code>../foo</code> and <code>foo/[.='bar']</code> will not.
-    Function calls are not allowed.</para>
+    supported in this mode, and the XPointer must be "streamable" &#8212;which
+    in our case means it must use the <code>xpointer</code> scheme
+    (<code>element</code> is not supported), and must use an XPath
+    LocationPath that only uses steps along the child axis. Furthermore, any
+    predicates must be literal numbers, or must be of the specific form
+    <code>[@attname='attvalue']</code>. For example, <code>/foo[3]</code> and
+    <code>/foo[@bar='baz']</code> will work, but <code>../foo</code> and
+    <code>foo/[.='bar']</code> will not. Function calls are not allowed.
+    </para>
 
-    <para>If you have not yet parsed an XML document, but have a URI for it,
+    <para>2. If you have not yet parsed an XML document, but have a URI for it,
     then you can use <methodname>Ft.Xml.XPointer.SelectUri</methodname>() to
     parse the document and evaluate an XPointer embedded in the URI's fragment
@@ -114,5 +115,5 @@
     illegal to use outside of extended XLinks, anyway.</para>
 
-    <para>If you have already parsed the document into a Domlette, then you
+    <para>3. If you have already parsed the document into a Domlette, then you
     can evaluate an arbitrary XPointer against it by using
     <methodname>Ft.Xml.XPointer.SelectNode</methodname>(). The same