Issue 13726 - OpenOffice output compatibility with XML Spy
Summary: OpenOffice output compatibility with XML Spy
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: xml
Classification: Code
Component: definition (show other issues)
Version: OOo 1.1 Beta
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: ---
Assignee: michael.brauer
QA Contact: issues@xml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-23 03:54 UTC by Unknown
Modified: 2003-05-22 13:14 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2003-04-23 03:54:56 UTC
Several attempts to open OpenOffice output files--either "content.xml" or the 
DTD file for inspection by and editing with XML Spy 5.0 resulting in an XML Spy 
"cannot open" message.




This might be a consequence of an XML standards failure (a) by OpenOffice, or 
(b) by XML Spy, or (c) a detail unspecified in the XML standard, and in fact 
handled differently by OpenOffice and XML Spy.




I have reported the problem also to Altova (the XML Spy vendor).




P.S. I am a "newbie" to both OpenOffice and XML Spy, so there is also a 
possibility (d) that I am doing something incorrectly.  If the last, it can be 
considered somebody's usability bug.
Comment 1 michael.brauer 2003-04-30 07:16:19 UTC
I have no problems opening OOo XML files like content.xml with XMLSpy.
What happens in fact is that the DTD files assigned to the XML file in
the <!DOCTYPE> declaration are not found. The reason for this is that
this the <!DOCTYPE> contains no path for this. The reason for this is
that a local path on to a system (like c:\programs\office61\..) will
be system dependend and a http-path would force a internet connection.
Both is not very useful. 
The recommended way resolve such thing in XML is to evaluate the
public identifier in the <!DOCTYPE> (the "-//OpenOffice.org//DTD
OfficeDocument 1.0//EN"), but this requires a application dependent
repository that matches these public DTD name to a file, and that
seems not to be implemented in XMLSpy.
The workaround is to assign the DTD file manually to the XML file. It
can be found in the installation within the share/dtd folder.
Comment 2 michael.bemmer 2003-05-22 13:13:12 UTC
Closing resolved worksforme.
Comment 3 michael.bemmer 2003-05-22 13:14:44 UTC
Closing resolved worksforme.