Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: Impact of XML on Data Modeling

From: "Michael Kay" <mike@--------.--->
To: <abcoatesecure-w3c@-----.--.-->, <xmlschema-dev@--.--->
Date: 1/29/2008 3:58:00 PM
> So, what I should have said is that introducing "Person" as 
> the common superclass of "Employer" and "Employee" is 
> something you would normally do in the logical model, but you 
> would only do that in the conceptual model if the business 
> experts view the world that way.

What I usually find is that after a couple of hours with a whiteboard, you
change the way the business people see things. Suddenly they realize that
they have been using a word like "channel" (as in a broadcasting channel - a
real example) or "retailer" to mean three different things, and that this is
why they were getting confused... 

Similarly, when you start asking questions like "How do you handle a
customer who is also a supplier", you may well find one outpost of the
organization that tells you "we lump them together and call them business
partners", and then other people will say that's a good idea, we could do
that too.

So I don't really buy the idea that abstractions can be classified as
business-oriented or technically-oriented. They arise from designing
IT-enabled business processes, which tends to be a joint activity.


Michael Kay
http://www.saxonica.com/



From rschloss@u... Tue Jan 29 16:39:26 2008
Received: from maggi


transparent
Print
Mail
Like It
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.

.
.

transparent

transparent