Re: ebXML-BP - CC Context Report
This is a great effort! I'd like an electronic copy, if possible.
I have a few comments:
1) in the summary, I'd incorporate the thoughts
- operating on an exception basis, for handling differences
- brings order to the implementation process
- paragraph 4, each aspect of context has a hierarchical nature to it, but the various elements of context [business process relative to industry, for example] are not hierarchically related
- paragraph 5, context will 1) shape the document at the highest level, 2) extend (+ or -), and specify appropriate code sources at the lowest level
- paragraph 6, I'm not sure at all that we will have a context specification language, but it is clear that if we can write code in advance to produce the desired results, we have a deterministic solution. The deterministic nature of the solution is the point to emphasize here.
- first paragraph, I think I understand what you are trying to say here, how does the following sound to you.
Using context to specify a document is significant.
Instead of thinking of traditional documents, we can think in terms of
events/actions, and information flows. An information flow can be
thought of in terms of the functional composition of that messages, independent
of traditional document boundaries. For example, instead of the point
of focus being concentrated on a Purchase Order document specification,
we are concerned with the Action of Ordering, and the functional elements
for that Order, and specifying the context for which that Order applies.
The Context, combined with the functional elements of the Order, specifies
the exact information set. Moreover, the documnt elements can be
dynamically specified, dependent on context.
lms
Brian Hayes wrote:
I have posted my write-up on the Core Components "Context" concept to
http://www.ebxml.org/working/project_teams/business_process/cc/. File: BH
CC Context Writeup.htmlThis report provides my understanding of the "Context" concept of the
ebXML-Core Components team and how it maps to ebXML-Business Process team's
meta-model. The information in this document is based on the Core Components
Presentation [CCP00], an email message from Lisa Shreve, Project Team Leader
for Core Components, and a discussion with Arofan Gregory, Core Components
team member. Excerpts from these references are provided in this document.
This document has not been reviewed by any member of the Core Components
team prior to distribution. It will be sent to members of the Core
Components team for review.
---
Lisa, Arofan, Lisa and Sue - Unfortunately, I did not have the time to have
you review this document for correctness prior to its posting. I'm looking
forward to your input.
---
Sincerely,
Brian Hayes
XML Cross Product Architect
Document Engineering. Commerce One. +1 (925) 520-4498