Bruce
Attached is a marked up copy of the specification. I focused on syntax
and made changes in the content only when I thought I was not changing intent.
If I had gotten to this earlier I could have resolved intent issues on the
listserv. I had just finished reading the ppt, the paper applying BCM to the
financial industry and the spec over the weekend prior to our last con call.
I raised the question about the Executive Summary as I was unaware there
was one on Kavi. I was going to suggest writing 3 - 4 pages directed to the
CFO. This is the person who is most responsible for ROI in an organization.
Selling the CFO that BCM is the better approach because BCM focuses on
interoperability from a business perspective with the intent of driving
through to a solution that encompasses the technical issues are the
mutual objectives of the BCM and many CFOs of enterprise orgs.
At least,those CFOs who are future oriented. Interoperability is the big
challenge and the elusive goal.
The BCM provides the roadmap and the mechanisms to define the business
solution and the means to implement the solution. BCM relies on open
standards and work of other authoritative sources to devise the framework that
will produce an operational solution. The other efforts include BPEL, CAM, et
al.
This perspective may provide the view of how the multiple,
on-going efforts, i.e. BCM, BPEL, W3C et al, interlock and
compliment each other. Clearly the many efforts to address interoperability
(from different perspectives) demonstrates the interest. How they fit together
should be spelled out before the "solutions" exacerbate the issue.
Anyway I hope these views help with the exec summary and the cover piece
you are doing to the spec.
Sally