- From: Tsao, Scott <scott.tsao@boeing.com>
- Date: Wed, 30 Jan 2008 17:42:06 -0800
- To: <abcoates.work@yahoo.co.uk>, <xmlschema-dev@w3.org>
- Message-ID: <C7A7D8EA54C20744BFF861613617222C06218EAE@XCH-NW-3V1.nw.nos.boeing.com>
Count me in as one of those "large organizations!" Is it ever achievable? Any successful stories? Given that as a goal (and constraint), will XSD still be a good (or best) choice for message design? Thanks, Scott Tsao Associate Technical Fellow The Boeing Company -----Original Message----- From: Anthony B. Coates (Work) [mailto:abcoates.work@yahoo.co.uk] Sent: Wednesday, January 30, 2008 4:02 PM To: xmlschema-dev@w3.org Subject: Re: Impact of XML on Data Modeling Designing in XML (e.g. W3C XML Schema) is an attractive option when you (and/or your group) are only responsible for the messages that are sent between systems. On the other hand, I know a number of large organisations that are busy developing enterprise data models, at a level above XML or relational databases or program code, because they want data consistency everywhere. They are concerned with more than just consistency in the messaging between systems. So whether XML schemas are suitable for your modelling needs depends very much on what your business scope is, and what your company's longer term ambitions are (in terms of having a consistent enterprise data model). The "right" choice depends very much on your particular needs and goals. Cheers, Tony.
Received on Thursday, 31 January 2008 01:42:23 UTC