[
Lists Home |
Date Index |
Thread Index
]
> -----Original Message-----
> From: Michael Kay [mailto:mike@saxonica.com]
> Sent: Sunday, January 30, 2005 12:26 PM
> To: 'Christian Nentwich'
> Cc: 'Roger L. Costello'; 'XML Developers List'
> Subject: RE: [xml-dev] 3 XML Design Principles - a rebuttal
>
> > The only time they need their data
> > normalised is at the end of a message flow, when it goes into a
> > database, but certainly not in XML transit.
>
> I think that's the key point.
>
> Normalization was invented for databases - persistent shared
> updateable data stores used by many people in different and
> unpredictable ways. Database design and message design have
> quite different requirements and the optimum design for one
> is not generally optimum for the other.
+1
I was trying to make a related point in my earlier post today:
<Quote>
Keep in mind here that, if this is a data exchange scenario, we're
talking about the syntactical representation of the information on the
wire, which may very well be different than the manner in which the
information is ultimately persisted in a receiving system (unless, of
course, the XML document is persisted as-is in a native XML database).
So we should be careful not to mix the notion of tight/loose coupling
for the wire representation with the ultimate persisted representation,
which may have different processing consequences.
</Quote>
Kind Regards,
Joseph Chiusano
Booz Allen Hamilton
Strategy and Technology Consultants to the World
> The post that started this thread failed to say what you were
> trying to optimize.
>
> Michael Kay
> http://www.saxonica.com/
>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org
> <http://www.xml.org>, an initiative of OASIS
> <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>
>
>
|
