Altova Mailing List Archives


Re: expressing DTDs with UML

From: Chris Holmes <cholmes@-------------------------->
To:
Date: 9/13/1999 8:29:00 AM
ISO Technical Committee 211 is defining their data models for Geographic
Information using UML.  TC211 has specified a method for converting a schema
defined in UML into a DTD.  This allows transfer of the data instances via XML
documents.  The approach is inspired by XMI.

An overview presentation on the approach can be found at:
ftp://harp.gsfc.nasa.gov//incoming/encoding/EncodingWalkth.ppt

The draft ISO document can be found at:
ftp://harp.gsfc.nasa.gov//incoming/encoding/211n709.PDF

A tool which accepts an .mdl file and creates a DTD using the rules:
http://www.informatics.sintef.no/UML2XML/

- Chris

"Vun Kannon, David" wrote:

> To your example:
> package - document type
>         I prefer namespace at this point. I'm still working out what nested
> packages imply for namespaces.
>
> class - a tag
> attribute - a tag parameter
>         Heading down the path of "all content in attribute values" here. I
> suppose you could stereotype one class attribute as <<Content>>.
>
> association - hyperlink
>         UML can show navigation, so you can show which end implies an ID
> attribute, which end an IDREF. It is time to start thinking about generating
> XLink link attributes as well, so we need to stereotype the association as
> <<ID/IDREF>> or <<XLINK>>
>
> aggregation - allows expression of tag hierarchy e.g. <car> ... <wheel
> location="left_rear"></wheel></car>
>         UML has a hard time with ordered content. A DTD often expresses a
> content model with sequence constraints "(head,para*)". Notice how easy it
> is to find an example from the XML-as-document space rather than the
> XML-as-data space.
>
> inheritance - a means for sharing / inheriting attributes, relationships
>
>         DTDs as defined today don't need/use methods.
>
>         Overall, though, I think it is less interesting to figure out how to
> model DTDs with UML than it is to map business models developed in UML into
> DTDs, without bending the business model to fit a preconceived notion of
> what a good DTD should look like.
> Cheers,
> David vun Kannon
> *****************************************************************************
> The information in this email is confidential and may be legally privileged.
> It is intended solely for the addressee. Access to this email by anyone else
> is unauthorized.
>
> If you are not the intended recipient, any disclosure, copying, distribution
> or any action taken or omitted to be taken in reliance on it, is prohibited
> and may be unlawful. When addressed to our clients any opinions or advice
> contained in this email are subject to the terms and conditions expressed in
> the governing KPMG client engagement letter.
> *****************************************************************************
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

--
Chris Holmes
cholmes@xxxxxxxxxxxxxxxxxxxxxxxxxx
Office: 703) 827-0638 x246
Cell Phone: 703) 928-5012
Pager: 703) 219-9503
------------------------------------
Blueprint Technologies
Foundations for Successful Software
www.blueprint-technologies.com



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.