Stanley Bradbury wrote: > Jean T. Anderson wrote: > >> There was a lengthy discussion on [EMAIL PROTECTED] that I'll summarize >> succinctly as: >> >> 1) Somebody requested a centralized location for Apache DTDs. >> 2) The request was turned down because of the load that resolving DTDs >> puts on Apache resources; DTDs should be accessed locally. >> ... >> The Derby DITA doc builds are set up so that when you run ant to build >> the docs ( see http://db.apache.org/derby/manuals/dita.html for >> details), ant copies the DTDs from the DITA Toolkit into src/dtd in the >> Derby doc repo. The DITA files then include the appropriate DTD with a >> local, relative reference ("../dtd/concept.dtd", "../dtd/reference.dtd", >> or "../dtd/task.dtd") >> ... > Thanks Jean - > I've been using the wrong reference in my DITA source files. I will > update the references in the Dita Source files for the Working With > Derby document. You've saved me some problems down the line. : )
Just in case I confused anyone, the DITA DTDs aren't at Apache so wouldn't be resolved there, but it's still a good practice to resolve them locally. Derby DITA doc source is doing things correctly, and I'll catch up the web site source with DERBY-1199. -jean
