• From: "Don Park" <donpark@q...>
• To: "XML-Dev Mailing list" <xml-dev@i...>
• Date: Fri, 15 Jan 1999 13:41:40 -0800

Correct solution to this problem seems to be a combination approach where
document type information from multiple sources (file extension, HTTP
headers, etc.) are combined and presented to clients using abstracted
interface.  Java Activation Framework does some of this but it doesn't go
far enough.  Idealy clients should be able to specify a list of desired
document types and the degree of document type conversion.

Document type conversion comes into play when a requested document type is
not available directly but can be produced through one or more document type
converters.  For example, if client can handle XSchema files but source
document is in XML-Data format, XML-Data can be converted to pure DTD (with
some information loss) and then converted to XSchema.

Don Park
Docuverse



xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Prev by Date: Re: Identifying XML Document Types (was XML media types revisited)
• Next by Date: Re: Identifying XML Document Types (was XML media types revisited)
• Previous by thread: Identifying XML Document Types (was XML media types revisited)
• Next by thread: specs for Coins 3.1 ?
• Index(es):
  • Date
  • Thread