[
Lists Home |
Date Index |
Thread Index
]
Calling something a bug is a pretty strong language.
A design approach that is valid in some contexts but hard to accomplish in others is no different than any other design approach.
A standardized reference model for aggregations of organizations seems to be a valid design approach and not a bug. If the aggregation by ownership or by cooperative vertical market then there can be a benefit.
Using the wrong reference model in the wrong place certainly is a bug. The model existence is not a bug. The use of the wrong tool, as always, is the bug.
-----Original Message-----
From: Elliotte Harold [mailto:elharo@metalab.unc.edu]
Sent: Thursday, October 13, 2005 6:54 AM
To: Greg Alvord
Cc: 'Vladimir Gapeyev'; 'W. E. Perry'; 'XML DEV'
Subject: Re: [xml-dev] XML-with-datatypes (was....)
Greg Alvord wrote:
> · Is the interoperable canonical data model connecting the
> systems of a company a bug or feature. Enterprise Bus design uses the
> approach.
>
Inside one company. if that company isn't too big or diverse, you can
force everyone to use the same software and the same data model. In a
small company or organization, this may even happen naturally. However
the larger and more distributed companies, organizations, and groups
become, the harder it is to enforce a single data model because
different organizations and individuals have different ways of seeing
the world. This is natural, and there's nothing wrong with it. Some of
the techniques that work in single organizations fail when applied to
multiple organizations or on Internet scale.
--
Elliotte Rusty Harold elharo@metalab.unc.edu
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim
smime.p7s
|
