Translation between DTDs, schemas, UML, and the like

[lauzon at us.ibm.com]

XMI is a submission to the OMG for a way to interchange UML data between
different modeling tools.  For more information on this, you should take a
look at:

http://www.omg.org/archives/orbos/msg00702.html

>From what I've seen it seems pretty complex, but that's because it's
attempting to describe all of UML (class diagrams, state diagrams, etc
etc).  I'm working on a tool for schema mapping between objects and
databases, and looked at this as a way to describe objects using XML.  For
now we are just using a DTD that our team whipped up from scratch that
describes a single class, but for more intelligent schema mapping we are
going to need a more complete model.  XMI may be what we will use in the
future for this.

Shawn Lauzon
Department MMB - San Francisco Database Persistence
http://www.ibm.com/Java/Sanfrancisco/
email: lauzon at us.ibm.com




"A. G. McDowell" <mcdowella at mcdowella.demon.co.uk> on 01/23/99 02:21:35 PM

Please respond to "A. G. McDowell" <mcdowella at mcdowella.demon.co.uk>

To:   xml-dev at ic.ac.uk
cc:    (bcc: Shawn Lauzon/Rochester/IBM)
Subject:  Translation between DTDs, schemas, UML, and the like





There seem to be a large number of languages devoted to listing (for
instance) the fields that make up a customer order and describing their
data types. To comprehend a (hypothetical) ecommerce system I might have
to follow a relational schema for the underlying database, a UML model
of the application classes and logic, and a schema or DTD for the XML
used to exchange data with its customers.

Is there any hope of a product that could be used to automatically
generate some part of this? My chosen format would be UML, but I'm open
to reasons why not. There are already drawing tools out there that can
generate C++ or Java code from suitably annotated diagrams, and keep the
annotations from making the diagrams unreadable: XML DTDs or schemas
should just be one more output format. The work on exchange of UML
between repositories already seems to involve auto-generating some sort
of schema from a description of UML (albeit not couched in UML itself,
but in a simpler metalanguage). Finally, there are a lot of people out
there who have already decided they need to know UML for the application
logic anyway.

On the other hand I don't know anywhere I can go to buy a UML -> DTD
Rational Rose plugin, complete with round trip functionality and a free
mouse mat, so maybe there's some good reason why all this is rubbish. Is
anybody planning to convert all the systems analysts to model in XML
schemas? Is the gap between exchangeable data, open to the world, and
encapsulated objects, observable only via their methods, just too large?
I have to admit that I personally have no great desire to write all my
Java via Rational Rose. Should I also find a burning desire to hand-
craft DTDs?
--
A. G. McDowell

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





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