mrglavas 2004/06/15 14:55:56
Modified: java/docs faq-xinclude.xml
Log:
Updating XInclude documentation.
Revision Changes Path
1.9 +9 -12 xml-xerces/java/docs/faq-xinclude.xml
Index: faq-xinclude.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/faq-xinclude.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- faq-xinclude.xml 25 Feb 2004 16:22:44 -0000 1.8
+++ faq-xinclude.xml 15 Jun 2004 21:55:56 -0000 1.9
@@ -66,7 +66,7 @@
Yes. The XInclude specification requires processors to use the base URI
(as specified in the <jump href="http://www.w3.org/TR/xmlbase/";>XML
Base</jump>
recommendation) to resolve relative IRIs to compute the
- <jump
href="http://www.w3.org/TR/2003/WD-xinclude-20031110/#include-location";>include
location</jump>.
+ <jump
href="http://www.w3.org/TR/2004/CR-xinclude-20040413/#include-location";>include
location</jump>.
Support for XML Base was added to the XInclude implementation in Xerces 2.6.0.
</p>
</a>
@@ -77,7 +77,7 @@
<a>
<p>
Currently, our implementation of XInclude is not fully complete, and we do
- not support <jump
href="http://www.w3.org/TR/2003/WD-xinclude-20031110/#XPCore";>XPointer</jump>
+ not support <jump
href="http://www.w3.org/TR/2004/CR-xinclude-20040413/#XPCore";>XPointer</jump>
references. We hope that in the future we will have a
fully compliant XInclude processor that can handle this feature.
</p>
@@ -88,9 +88,8 @@
<q>Are the values of the content negotiation attributes used in an HTTP
request?</q>
<a>
<p>
- Currently, the values of the <code>accept</code>, <code>accept-charset</code>
and
- <code>accept-language</code> attributes from an
- <jump
href="http://www.w3.org/TR/2003/WD-xinclude-20031110/#include_element";>include</jump>
+ Currently, the values of the <code>accept</code> and
<code>accept-language</code> attributes
+ from an <jump
href="http://www.w3.org/TR/2004/CR-xinclude-20040413/#include_element";>include</jump>
element are only included in an HTTP request for included items when
parse="text". We hope
that in the future we will be able to support content negotiation for
included items
when parse="xml".
@@ -98,15 +97,13 @@
</a>
</faq>
- <faq title="The Namespace: 'http://www.w3.org/2001/XInclude'">
- <q>Will the XInclude processor process include elements from the
'http://www.w3.org/2001/XInclude' namespace?</q>
+ <faq title="The Namespace: 'http://www.w3.org/2003/XInclude'">
+ <q>Will the XInclude processor process include elements from the
'http://www.w3.org/2003/XInclude' namespace?</q>
<a>
<p>
- No. The namespace for XInclude was changed during development to
- <code>http://www.w3.org/2003/XInclude</code>. The specification
- recommends that XInclude processors provide a diagnostic for include
- elements in the old namespace. Xerces' XInclude processor will report
- a warning.
+ No. The namespace for XInclude was changed back to
<code>http://www.w3.org/2001/XInclude</code>
+ in the <jump href="http://www.w3.org/TR/2004/CR-xinclude-20040413/";>Candidate
Recommendation (April, 2004)</jump>.
+ The <code>http://www.w3.org/2003/XInclude</code> is no longer recognized.
</p>
</a>
</faq>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
