[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Data design methods? (was Re: APIs, messaging)
- From: Michael Champion <firstname.lastname@example.org>
- To: email@example.com
- Date: Thu, 24 May 2001 11:40:45 -0400
----- Original Message -----
From: "Bullard, Claude L (Len)" <firstname.lastname@example.org>
To: <email@example.com>; "Simon St.Laurent" <firstname.lastname@example.org>
Cc: "Al Snell" <email@example.com>; "Jeff Lowery"
<firstname.lastname@example.org>; "'Eric Bohlman'" <email@example.com>;
Sent: Thursday, May 24, 2001 10:42 AM
Subject: RE: APIs, messaging
> The critical question: by what criteria does one choose to create a UML
> description, or an RDF Description, or a Topic Map, or just an XML
I have an even more basic question: by what criteria does one choose between
different DATA designs? OO methodologies provide criteria for choosing between
different designs, but as we've brought out here, a good OO design *hides* data
structures. Are there widely accepted criteria for defining "good" data models
independently of the algorithms used to process them?
The only thing that comes to mind that would be relevant to XML is
Entity-Relationship Modelling. Any thoughts?
I'm aware of David Carlson's website www.xmlmodeling.com (and his recent book),
but from a quick look it seems to focus on the mechanics of using UML to model
various XML schemas rather than the "aesthetics" of what a good design looks
like. Am I missing something?