David,
What you removed and modified in the document is
more than the "motherhood and apple pie stuff ". I think these are one of the
most important parts that would help readers of the document to better
understand the core of ebSOA TC architectural solution and vision.
You also added
"
- Software development itself is become
open and global and based upon interoperable components that can be adapted and
purposed using particularly XML scripted mechanisms. Providing the roadmap
for using such components in a coherent, reliable and proven way is the value
desired by implementers.
"
paragraph in the "Background" section. I think that
the "XML scripted mechanisms" is too technical stuff for this kind of the
document. For your information, we decided to take out technical details (we had
before) out of the vision document long time ago.
I also do not understand your BCM-related additions
to the document. I think that this TC needs to better understand BCM or any
other related specs before explicitly mentioning it in the document like this
one. At the same time, you can also see that we have not explicitly
mentioned any specific standard specs except the standard "groups" like ebXML
and Web Services. However, I believe that BCM will find its place in ebSOA TC
specs.
Goran
----- Original Message -----
From:
David RR Webber
(XML)
To:
Cc: ;
Sent: Tuesday, March 28, 2006 1:22
PM
Subject: RE: [ebsoa] Groups -
DiscussionDraft-VisionStatement (VisionStatement.ebSOA_DiscussionDraft.doc)
uploaded
Folks,
Attached edited version - I did more changes et al -
plus re-organization.
Eventually I believe we need three documents - this one seems to be
merging all three into one! ; -)
The good news is - what I see is very good - I'd venture to say the best
we have ever had.
Sometimes though we veer off into telling people motherhood and apple pie
stuff - so I've deleted what I saw as falling into that category. Less
is more always!!
The three eventual products that I see we need are:
1) Revised Charter - short succinct - two pager.
2) Executive Summary / Outreach / Press Release type material
explaining applicablity of Charter to the real world
3) Approach and
Roadmap to guide our own internal work products
I think we can easily derive these from the document - and I've attempted
to re-organize it a bit to make this a bit clearer.
Talk with everyone at 3pm (caveat - I'll be driving around school parking
lots collecting children)
Thanks, DW
--------
Original Message --------
Subject: Re: [ebsoa] Groups -
DiscussionDraft-VisionStatement
(VisionStatement.ebSOA_DiscussionDraft.doc)
uploaded
From:
Date: Tue, March 28, 2006
11:07 am
To: ,
Sally,
I have few comments that are included in the attached file.
Regards,
Goran
>-----Original Message-----
>From:
[mailto:]
>Sent: Friday,
March 17, 2006 06:21 PM
>To:
>Subject: [ebsoa] Groups -
DiscussionDraft-VisionStatement (VisionStatement.ebSOA_DiscussionDraft.doc)
uploaded
>
>Draft that outlines goals of defining a complete SOA
solution by providing
>an integrated framework and providing guidance
for how to achieve the
>solution. Circulate comments on the list.
Intent is to prepare a final
>statement and to use discussion to
advance work on specification and best
>practices
documents.
>
> -- Sally St. Amand*
>
>The document
named
DiscussionDraft-VisionStatement
>(VisionStatement.ebSOA_DiscussionDraft.doc)
has been submitted by Sally St.
>Amand* to the OASIS Electronic
Business Service Oriented Architecture
>(ebSOA) TC document
repository.
>
>Document Description:
>
>
>View
Document
Details:
>http://www.oasis-open.org/apps/org/workgroup/ebsoa/document.php?document_id=17279
>
>Download
Document:
>http://www.oasis-open.org/apps/org/workgroup/ebsoa/download.php/17279/VisionStatement.ebSOA_DiscussionDraft.doc
>
>
>PLEASE
NOTE: If the above links do not work for you, your email
application
>may be breaking the link into two pieces. You may be able
to copy and paste
>the entire link address into the address field of
your web browser.
>
>-OASIS Open
Administration
>
