Message:

   The following issue has been resolved as FIXED.

   Resolver: Michael Glavassevich
       Date: Mon, 10 May 2004 6:09 AM

This was updated in CVS several weeks ago. Have a look at the latest build [1].

[1] http://gump.covalent.net/jars/latest/xml-xerces2/
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XERCESJ-958

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XERCESJ-958
    Summary: XInclude namespace change in Candidate Recommendation
       Type: Bug

     Status: Resolved
   Priority: Blocker
 Resolution: FIXED

    Project: Xerces2-J
 Components: 
             XInclude 1.0
   Versions:
             2.6.1

   Assignee: 
   Reporter: Manos Batsis

    Created: Mon, 10 May 2004 4:22 AM
    Updated: Mon, 10 May 2004 6:09 AM

Description:
The XInclude namespace 

http://www.w3.org/2003/XInclude

has changed back to 

http://www.w3.org/2001/XInclude

in Candidate Recommendation 13 April 2004 (http://www.w3.org/TR/xinclude/):

[[[
This document is based upon the XInclude Last Call Working Draft published on 11 
November 2003. Please note that the namespace URI has been reverted back to the URI 
found in earlier drafts of XInclude. This document defines the namespace URI 
http://www.w3.org/2001/XInclude; the http://www.w3.org/2003/XInclude namespace URI 
found in the Last Call is made obsolete by this document. 
]]] 




---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to