On a quick read, this looks like it covers all the bases except for the forthcoming certification statements. I have one small suggestion included inline below.
On Jul 26, 2006, at 3:57 PM, Duane Nickull wrote:
TC:
Please read the following and help out where applicable in order that we are
prepared by August 15th, 2006.
Under the policy and procedures section, the TC chair (moi) must send the
following items to OASIS by the 15th of any month. Some of these require
your input:
****************Draft submission for OASIS********************************
By way of a special majority vote held between [insert dates here], we are
hereby making a formal submission to advance the OASIS SOA RM TC's Reference
Model for SOA to an OASIS standard status. Here is our submission package:
1.Links to the approved Committee Specification in the TC's document
repository, and any appropriate supplemental documentation for the
specification, both of which must be written using the OASIS templates. The
specification may not have been changed between its approval as a Committee
Specification and its submission to OASIS for consideration as an OASIS
Standard, except for the changes on the title page and running footer noting
the approval status and date.
TC Chair: The link is
m-cs.pdf
There are no supplemental or other normative documents for inclusion in the
submission. The title, status and date have been changed.
2. The editable version of all files that are part of the Committee
Specification;
TC Chair: The editable versions of the document are:
MS Word:
m-cs.doc
HTML:
m-cs.zip
3. Certification by the TC that all schema and XML instances included
in the specification, whether by inclusion or reference, including fragments
of such, are well formed, and that all expressions are valid;
TC Chair: Given the abstract nature of the Reference Model, this is not
applicable. We have no schemas within our specifications.
4. A clear English-language summary of the specification;
TC Chair: (proposed) This Reference Model for Service Oriented Architecture
is an abstract model for understanding significant entities and
relationships between them within a service-oriented environment, and for
the development of consistent standards or specifications supporting that
environment. It is based on unifying concepts of SOA and may be used by
architects developing specific service oriented architectures or in training
and explaining SOA.
Due to its' abstract nature, this reference model is not directly tied to
any standards, technologies or other concrete implementation details. It
provides a common semantics that can be used unambiguously across and
between different implementations.
While service-orientation may be a popular concept found in a broad variety
of applications, this reference model focuses on the field of software
architecture. The concepts and relationships described may apply to other
"service" environments; however, this specification makes no attempt to
completely account for use outside of the software domain.
5. A statement regarding the relationship of this specification to
similar work of other OASIS TCs or other standards developing organizations;
TC Chair: (Proposed) This work is abstract in nature and
the vocabulary and relationships defined are
meant to be used as
a template by those who architect SOA. Accordingly, it would be relevant to
most SOA activities including the Web Service technology family, any XML
based language that may be used within an SOA, W3C specifications for Web
Services including WSDL and WS-Policy work and other software architecture
practices and standards. It will likely be of interest to ISO, IEEE, IETF,
W3C, UN/CEFACT, AIAG, AIA, the Ontolog Forum, Open Group and many other
standards organizations.
6. Certification by at least three OASIS member organizations that
they are successfully using the specification;
TC Chair: TBD - we require this. To certify such, please send an email to
the general SOA RM list stating the name of your organization, that you are
using the Reference Model as a guide for architecture with success and your
name and company name. This is for OASIS Member Organizations only and we
require at least 3.
7. The beginning and ending dates of the public review(s), a pointer
to the announcement of the public review(s), and a pointer to an account of
each of the comments/issues raised during the public review period(s), along
with its resolution;
TC Chair: There were two Full Public Reviews that happened.
The first public review towards becoming a Committee Specification occurred
between 13 February 2006, and ends 14 April 2006. The accouncement may be
found here:
The second public review towards becoming a Committee Specification occurred
5 June 2006 to 20 June 2006. The announcement may be found here:
The full transcripts of all comments and dispositions are may be linked to
from this page:
Under the "issues" folder. They are expressed in Microsoft Excel
Spreadsheet format along with a resolution for each and every comment
submitted. To our knowledge, there are no outstanding disagreements with
the resolutions for any comment.
8. An account of and results of the voting to approve the
specification as a Committee Specification, including the date of the ballot
and a pointer to the ballot;
TC Chair: The ballot for approval as a Committee Specification opened July
12, 2006 and closed July 19, 2006. The ballot results were 100% in favor
and the ballot details are archived here:
9.An account of or pointer to votes and comments received in any
earlier attempts to standardize substantially the same specification,
together with the originating TC's response to each comment;
TC Chair: This is the first time the RM for SOA has been forwarded as a
candidate for OASIS Standard, hence there are no pointers available.
10. A pointer to the publicly visible comments archive for the
originating TC;
TC Chair:
The publicly visible comments archive is available at:
11.A pointer to any minority reports submitted by one or more Members
who did not vote in favor of approving the Committee Specification, which
report may include statements regarding why the member voted against the
specification or that the member believes that Substantive Changes were made
which have not gone through public review; or certification by the Chair
that no minority reports exist.
TC Chair: I hereby certify that no minority reports exist.