You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by mr...@apache.org on 2004/10/03 22:05:21 UTC

cvs commit: xml-xerces/java/docs faq-xinclude.xml releases.xml

mrglavas    2004/10/03 13:05:21

  Modified:    java/docs faq-xinclude.xml releases.xml
  Log:
  Some documentation updates for XInclude 1.0 PR.
  
  Revision  Changes    Path
  1.11      +6 -7      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.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- faq-xinclude.xml	15 Sep 2004 19:57:30 -0000	1.10
  +++ faq-xinclude.xml	3 Oct 2004 20:05:21 -0000	1.11
  @@ -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/2004/CR-xinclude-20040413/#include-location">include location</jump>.
  +      <jump href="http://www.w3.org/TR/2004/PR-xinclude-20040930/#include-location">include location</jump>.
         Support for XML Base was added to the XInclude implementation in Xerces 2.6.0.
        </p>
       </a>
  @@ -88,7 +88,7 @@
       <a>
        <p>
         Currently, our implementation of XInclude is not fully complete, and we do
  -      not support <jump href="http://www.w3.org/TR/2004/CR-xinclude-20040413/#XPCore">XPointer</jump>
  +      not support <jump href="http://www.w3.org/TR/2004/PR-xinclude-20040930/#XPCore">XPointer</jump>
         references.  We hope that in the future we will have a
         fully compliant XInclude processor that can handle this feature.
        </p>
  @@ -99,11 +99,10 @@
       <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> 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".
  +      Yes, the values of the <code>accept</code> and <code>accept-language</code> attributes 
  +      from an <jump href="http://www.w3.org/TR/2004/PR-xinclude-20040930/#include_element">include</jump>
  +      element are included as request properties in an HTTP request. Support for content negotation 
  +      when parse="xml" was added to the XInclude implementation in Xerces 2.7.0.
        </p>
       </a>
     </faq>
  
  
  
  1.186     +3 -3      xml-xerces/java/docs/releases.xml
  
  Index: releases.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/java/docs/releases.xml,v
  retrieving revision 1.185
  retrieving revision 1.186
  diff -u -r1.185 -r1.186
  --- releases.xml	20 Sep 2004 22:54:26 -0000	1.185
  +++ releases.xml	3 Oct 2004 20:05:21 -0000	1.186
  @@ -30,8 +30,8 @@
       </add>
       <update>
        <note>
  -      Implemented the <jump href="http://www.w3.org/TR/2004/CR-xinclude-20040413/">XInclude</jump>
  -      Candidate Recommendation (April 2004), excluding support for XPointer.
  +      Implemented the <jump href="http://www.w3.org/TR/2004/PR-xinclude-20040930/">XInclude</jump>
  +      Proposed Recommendation (September 2004), excluding support for XPointer.
        </note>
        <submitter name='Michael Glavassevich'/>
       </update>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-cvs-help@xml.apache.org