Issue 28 - OFFICE.DTD does not parse through SP
Summary: OFFICE.DTD does not parse through SP
Status: CLOSED FIXED
Alias: None
Product: xml
Classification: Code
Component: definition (show other issues)
Version: 605
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: ---
Assignee: michael.brauer
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks: 29
  Show dependency tree
 
Reported: 2000-10-21 23:22 UTC by issues@www
Modified: 2007-09-23 20:20 UTC (History)
1 user (show)

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


Attachments
errormessages when parsing office.dtd with SP (12.00 KB, text/plain)
2003-12-06 14:52 UTC, issues@www
no flags Details
fix as described in issue (4.97 KB, text/plain)
2003-12-06 14:52 UTC, issues@www
no flags Details
fix as described in issue (14.96 KB, text/plain)
2003-12-06 14:52 UTC, issues@www
no flags Details
fix as described in issue (8.91 KB, text/plain)
2003-12-06 14:52 UTC, issues@www
no flags Details
fix as described in issue (13.25 KB, text/plain)
2003-12-06 14:52 UTC, issues@www
no flags Details
fix as described in issue (table.mod) (13.25 KB, text/plain)
2003-12-06 14:52 UTC, issues@www
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description issues@www 2000-10-21 23:22:12 UTC
I tried to parse OFFICE.DTD using MetaMorphosis DTD frontend which is based on 
James Clark's SP.

A rather long list of errors appear. Most of them come from ambiguities.

I fixed the files here: 

1. Adding further datatypes in dtypes.mod and using them appropriately within
   drawing.mod

    floatOrPercentage
    coordinatOrPercentage
    lengthOrPercentage  (which was already there)

2. I fixed a whole bunch of ambiguities in table.mod, and datastyl.mod

   In all cases the modelgroup following the pattern
    A | A? B A

   changed to 

    A? (B A?)?

   Both schemes allow

    A
    ABA
    B
    BA

   Currently OOo does not use the DTD for parsing. Nevertheless the
   documents should be valid against the DTD. Which could be checked
   by valid parsing.

pS I wonder if I will be able to submit the changed files somehow.

Note that the DTD also causes warnings and error messages when loaded into 
XMLAuthority.
I will try to analyze these also
Comment 1 issues@www 2000-10-22 20:46:32 UTC
Created attachment 2 [details]
errormessages when parsing office.dtd with SP
Comment 2 issues@www 2000-10-22 20:47:53 UTC
Created attachment 3 [details]
fix as described in issue
Comment 3 issues@www 2000-10-22 20:48:22 UTC
Created attachment 4 [details]
fix as described in issue
Comment 4 issues@www 2000-10-22 20:49:36 UTC
Created attachment 5 [details]
fix as described in issue
Comment 5 issues@www 2000-10-22 20:50:03 UTC
Created attachment 6 [details]
fix as described in issue
Comment 6 issues@www 2000-10-22 20:55:14 UTC
Created attachment 7 [details]
fix as described in issue   (table.mod)
Comment 7 michael.brauer 2000-10-25 12:36:34 UTC
Thank you very much for yor patches. I've used them as a basis for correcting
the DTD. Anyway I didn't had the time to check the DTD with SP.

I sometimes had to use content models that are more complex than your's, because
your's allowed an empty content that is not allowed for the elements in
question.
Comment 8 issues@www 2000-11-18 20:50:24 UTC
I tried it again with SRC613. Now it parsed with SP within MetaMorphsois.

No more error messages:

C:\tmp\OOO\SOURCE\xmloff\dtd>c:\programme\mm3.3a\bin\mmx -A format XML -F dtd -S
 office.dtd

C:\tmp\OOO\SOURCE\xmloff\dtd>
Comment 9 michael.brauer 2001-02-08 16:32:20 UTC
Thank you very much.
Comment 10 Raphael Bircher 2007-09-23 20:20:43 UTC
I think, this issue cen be closed