Please check out tests/glob-prefs.xml where the dtd-pref is an info-field for a format in the output-prefs. This may also be customised in src/clisp/base/defaults.lisp before compilation.

When we started developing MusicXML, a DTD (Document Type Definition) was the only official W3C recommendation for defining an XML document. Since that time, XML Schemas have become an official W3C recommendation, and alternative schema languages like RELAX NG have also become available. W3C XML Schemas offer many benefits when using XML in electronic commerce and business database applications. For musical documents, though, the advantages are less compelling.

Yes. Many writers have had at least some experience with HTML as a markup language. Therefore the base DITA DTD incorporates as many HTML elements as are useful for the type of technical information for which topics might be used.

Right here! The original documents that accompany this proposal were authored in XML using the ditabase DTD. For latest information about the ongoing status of the DITA standard and its community of users, see the DITA Focus Area at dita.xml.org. IBM donated DITA to the OASIS standards organization in March of 2004, where it is now managed by the OASIS DITA Technical Committee (http://www.oasis-open.org/committees/dita/). In April of 2005, OASIS approved Version 1.

How could we tweak the code to output the xml schema with with the xml file produced? Some systems demand the schema be present with the data. when i execute the DTS STEP as Standlone Step it executes fine but when i execute it as a package it screws up The script shown works quite well. However, if comments were added about the 'dialect', 'stream' etc it would have been helpful.

Specify the default page size for files for which no page size is specified. Page size in source file overrides the default setting. Specify resolution of output file, and units of measure. Includes an option to emulate an HP printer with a 300/600 dpi toggle switch. This is useful for files with raster logos which were imaged at 600 dpi. It is safe to leave this switch on all the time, although there may be rare encounters with files which convert improperly with this switch enabled.

Since this unit uses a cross-coupled output, it is imperative that pin 3 be grounded to pin 1 and the audio positive connected to pin 2. It is also very important to make sure the unit is earth grounded using a separate wire connected to the chassis ground screw near the red power connector. See Sound System Interconnection for further details. Not having an earth ground connection to the chassis is the number one cause of failure

See SGML for Windows NT: Setting up a free SGML editing and publishing system on Windows NT/Cygwin by Markus Hoenicka.

Not directly, however you can convert your DTD to an XML Schema fairly easily. We provide a tool (org.exolab.castor.xml.dtd.Converter) to do this. You can also use any number of 3rd-party tools such as XML Spy or XML Authority.

Atomik works with almost all DTDs and Schemas that conform to the XML standards defined by the World Wide Web Consortium (W3C). If your DTD or Schema uses external entity references, you will need to make sure these are available to Atomik Roundtrip as it is not possible for QuarkXPress to access these across the Web. Entity locations and other parameters can be defined in the Atomik Roundtrip preferences.

There are two ways. Forrest has a simplifiedDocbook plugin which can transform the DocBook format into the Forrest "xdocs" format on-the-fly and then render that as normal Forrest documents. Be aware that the stylesheet that does this transformation is deliberately very limited and does not attempt to deal with all DocBook elements. The other way is to use the full DocBook stylesheets directly. The DocBook DTDs are shipped with Forrest and automatically handled.

lt;build> ... <pluginManagement> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-eclipse-plugin</artifactId> <configuration> <outputDirectory>target-eclipse</outputDirectory> </configuration> </plugin> </plugins> </pluginManagement> ... </build>

I can kill Cocoon (2.0.4 or 2.1rc3) by pressing the Reload-Button for a while. This also works with some of cocoons Live-Sites (using a DSL-Connection). Why is that?? (I don't think that I will use Cocoon any more...)

You even can use different DTDs according to your situation (production/development), probobly put in a property/configuration file. If the third party XML has no DTD: You can use xslt to transform your xml string to a new one. See complete instructions here: Controlling the DOCTYPE and XML Declaration If you don't want to change the XML file or string, you can set an equivalent schema. Schema can be specified on processing time.

It is not recommended. I made it work once, the major reason was trying to take advantage of DTD entities. It would be easily causing confusion. It would be hard to maintain stuff in the feature.

There is no single answer to this: a lot depends on what you are designing the document type for. The two extremes are best illustrated with examples.

Yes. Atomik Roundtrip does not require the use of a special DTD in order to be able to import the XML into QuarkXPress. Therefore you can use any XML created with your existing company DTD or Schema

Originally, I was very strongly recommending W3C schemas, but now I'm not so sure. I think there are still lots of cases where simple DTD's are enough. And further, there are probably lots of cases where you want to do all your own validation inside your own source code program.