Lists Home |
Date Index |
- From: email@example.com
- To: firstname.lastname@example.org
- Date: Mon, 29 Nov 1999 15:32:11 -0700
> We are developing an application which will use XML as a syntax for
> communicating data between two parts of that application.
> This XML uses a DTD, both for the (admittedly limited) validation it
> provides, and to supply default values for attributes, so the
> part of the application needs to be able to find the DTD
> before it can make
> sense of the XML.
> What should I do? If I put:
> <!DOCTYPE Linestyle SYSTEM "file://C:/MyApp/MyApp.dtd">
> in the file, the XML will be unusable on any machine which
> happens to have
> installed my application in another directory.
We have run into a similar issue. In our case, we are creating a new MS
Windows Application (not Web based at all), and using an XML based file
format. We are using the MSXML parser to load in and validate documents
according to our schema (or DTD). We wanted to keep our Schemas (or DTDs)
stored in a central location, and have the data files reference them no
matter where our application is installed (or where the OS is installed).
The best answer we've gotten for our case was to create a handler for our
own Asynchronous Pluggable Protocol. In our case, a reference to the schema
(or DTD) would look like
"our-custom-protocol://Some/Path/in/the/Registry/CLSID". We then have a
CLSID to a COM object that delivers the schema (or DTD) to the protocol
handler. Since MSXML uses URL monikers, we can do this. Its not completely
implemented yet, but that's the plan.
I realize that this is very Microsoft/Windows specific, but we haven't found
a better way yet. Does anyone else use an XML based file format for a
normal desktop application? If so, how do you handle centralizing your
schema(s) and DTD(s)?
Evans & Sutherland
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)