Skip to main content
1-Visitor
April 2, 2012
Question

DTD to schema question

  • April 2, 2012
  • 11 replies
  • 2051 views
Folks, I've been doing a fair amount of research on this and it seems I have one problem that may keep me in the DTD world a bit longer.

Our DTD has several large referenced files containing general ENTITY replacement text (if anyone has ever parsed the 40051 DTD with 'dtgen' they have encountered those files. You normally will get several 'litlen' errors.) This replacement text contains markup, references to other editable ENTITIES and the text is generic required stuff the authors really don't need to redo for every TM.

My question is this (and I think I already know the answer BUT thought I'd toss it out for verification), can I call those files from a schema? My searches to date have said NO. 😞

If I cannot call those files, then converting to a schema won't work.

Many thanks.


Lynn

    11 replies

    LynnHales1-VisitorAuthor
    1-Visitor
    April 5, 2012
    Folks,

    Again, thanks so much for the input. What I think I am going to attempt to do is include a DTD subset in the schema and HOPE that all the different tools people use will recognize it without problem.

    I like the addition to each document, but because this is a publicly available DTD, there is no guarantee that ENTITY declarations would be put into each file.

    I'll let everyone know how this works out when I get back to it.

    Thanks all.

    Lynn
    ---- "Hintz wrote:
    > Just adding my 2 cents worth. We've been using this approach forever. Even did the transition from DTD to schema without any problems. All of our XML documents have headers similar to this:
    >
    >
    >
    > >
    > %textents;
    > ]>
    >
    > The actual text.ent file is resolved through the magic of catalogs. We've used this with Arbortext, XMetaL (during an evaluation), and oXygen (currently evaluating) without issues. One advantage we have is that the doctype headers are rebuilt when documents are checked back into our CCM.
    >
    > Dave
    > Siemens
    >