Jor-el <[EMAIL PROTECTED]> writes: > On 14 Jan 2003, Adam DiCarlo wrote: > > > > > Should I include the XML catalog DTD with sgml-data? (Probably along > > with the Relax, XML Schema, and other represntations.) Or should this > > be in it's own package? > > If an XML processor is processing the catalog itself, it would be > beneficial to have a "SYSTEM" mapping specifying the local location of > this DTD.
Well, surely. All XML DTDs and entity files and such will have XML catalog entries with their local file location. That's why we have catalogs. > A logical place to have this would be in /etc/xml/catalog > itself. If the xml-common package is going to install /etc/xml/catalog , > then it would be kind of awkward to have the Catalog DTD in another > package. Unless of course, xml-common doesnt install /etc/xml/catalog and > leaves it up to sgml-data..... It's xml-core btw. That doesn't really follow at all. xml-core would provide means for a package to (de)register catalogs. It may or may not require the XML catalog to function properly. That's the question I'm asking. > > On another note - what about file naming conventions? > /etc/xml/catalog is hardcoded into xsltproc - so we dont have much > flexibility in its naming. SGML catalogs are called either "catalog" or > "<filename>.cat". In order to allow the equivalent XML catalogs to be > present in same directory, I propose a naming convention of "xcatalog" or > "<filename>.xcat" No, these are XML documents and that should be their file ending. I generally use "catalog.xml" for the catalog sitting in the dir along with the entities and DTDs. "Supercatalogs" with the delegate information, if we use those, would be /etc/xml/<pkgname>.xml or /etc/xml/catalogs/<pkgname>.xml or something. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...<URL:http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
