I received a query from David Tyree of SAS, Inc., the other day about
making the TEI DTD work with the Arbortext product Adept, and append my
reply to the query, in the hope that someone on this list can help.
On Tue, 31 Jan 1995 10:14:10 -0500 (EST) you said:
> I am trying to get the TEI DTD to load into an SGML Publisher/Editor
> from ArborText called ADEPT.
> My hypothesis of the problem is this:
> ADEPT wants all the tags allowed in the DTD defined up front.
> ADEPT then "compiles" the DTD into a binary file that it uses
> to process the data. (is this ISO correct?).
There are those who dislike the practice of compiling DTDs; I don't
think anyone in sound mind claims it's not conformant, though.
> My question:
> Is there a way to "turn on" every possible tag & attribute
> so ADEPT can "compile" the DTD, without getting tags defined
> more than once?
> If I'm not clear here (and I'm confusing myownself here, too)
> please let me know and I'll try to clarify.
I have recently acquired a copy of Adept, but have not loaded it or
started to use it, so I'm not sure whether the problem is
(a) Adept cannot find the external entities (files) in which
various parts of the DTD are stored, or
(b) Adept, like some other programs, objects to the fact that the
DTD may mention elements which are not declared (since the
tag set in which they appear is not selected)
In case (a), you need help from someone other than me, to find out how
to tell Adept how to find the files.
In case (b), you or I, or both of us, need to file a bug report with
ArborText, since the standard clearly says that references to undeclared
elements are legal (clause 11.2.4, right before clause 184.108.40.206, page
412 of Goldfarb's SGML Handbook).
I am going to cc: this note to TEI-L, in the hopes that someone on
the list with experience using Adept can shed some light on your
In the meantime, you might try looking at the 'pre-processed' DTDs
derived by Greg Murphy at CETH from the TEI DTDs. Each of these DTDs
corresponds to one 'view' of the TEI main DTD, with all of the
declarations in a single file, and with dummy declarations added
for all elements which are mentioned but not declared. (I think a
better approach would be to remove the references to undeclared
elements, but that's harder and no one has yet written a program to
do it. As it is, you have to be careful not to USE any of the
elements for which dummy declarations have been supplied, since if
a dummy declaration has been supplied, that means the element is not
legal in the view you are using.)
The derived DTDs prepared by CETH are available by anonymous ftp
> Thanks in advance for your help!
>David S. Tyree Senior Publishing Programmer/Analyst
> Publications Technology Development Department
> SAS Institute Inc.; SAS Campus Drive R1280; Cary, NC 27513
> [log in to unmask] (919) 677-8000 x7405 (919) 677-7844 FAX
-C. M. Sperberg-McQueen
ACH / ACL / ALLC Text Encoding Initiative
University of Illinois at Chicago
[log in to unmask] / u35395@uicvm