Yes, and there is a value add to moving a DTD into a UML model. Perhaps to
integrate with other UML models, to update it with a Common Business Object
(oops!, Core Component), to add operations to reflect system behavior such
as workflow. This is not an bidirectional, isomorphic process.
Scott
-----Original Message-----
From: Cory Casanave [mailto:[email protected]]
Sent: Tuesday, May 30, 2000 1:50 PM
To: David RR Webber; INTERNET:[email protected]
Cc: [email protected]; Martin Bryan
Subject: RE: Announcement from Technical Architecture
We can do that today - take a DTD and reverse it into a UML Model. However,
since the DTD contains less information it is not 100% Reversible.
> -----Original Message-----
> From: David RR Webber [SMTP:[email protected]]
> Sent: Tuesday, May 30, 2000 2:20 PM
> To: INTERNET:[email protected]
> Cc: [email protected]; Martin Bryan
> Subject: RE: Announcement from Technical Architecture
>
> Message text written by INTERNET:[email protected]
> >Deriving an XML syntax from a UML model in a consistent manner
> means you *don't* repeat the modeling process; rather, you use the
> superior
> modeling medium to model the domain and then generate the XML syntax
> according to a well-defined pattern.
>
> David S. Frankel<
>
> >>>>>>>>>>>>
>
> Once upon a time we talked about reversable process.
>
> I'd still like to be able to do that - i.e. import my DTD (aka schema)
> into a UML tool and have it then make those components available.
> Then I can do interesting UML things on top to enhance the documentation.
>
> I've used Visio Professional like this against SQL tables, and this just
> seems such a natural win-win.
>
> Never under estimate the power of simple! Not everyone wants to
> start the process in a UML tool - nor should they need too.
>
> DW.
