OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: Keep business-process-specific data separate?

Hi Folks,

This has been, for me, an enlightening discussion. Thanks so much to Jim, Frank, Paul, and Len. Awesome responses!

Here are the lessons I've learned:

1. An XML vocabulary does not exist in a vacuum. It exists in a context. Specifically, it exists for the purpose of enabling a business process.

2. If an XML vocabulary does not support the data needed by the business process then it is not serving the very purpose for which it was created.

3. "Business-process-specific data versus business-process-independent data" is a false distinction. There is only kind of data: data for a business process, and there is only one kind of XML vocabulary: vocabulary that supports a business process.

4. An XML vocabulary must support the data needs of both the data producer and the data receiver.

5. If there is markup (data) needed by the receiver but not the producer then make it optional. Thus the producer can omit the optional markup while the receiver can add it.

6. The conclusion that I came to in my transportation example - keep business-process-specific data separate - is false, for the above reasons.

Do you agree? Have I captured all the lessons?


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS