BCM Submitted for OASIS Standard

["Mary McRae" <mary.mcrae@oasis-open.org>]

OASIS Members:

The OASIS Business-Centric Methodology (BCM) Technical Committee has submitted the following specification, which is an approved
Committee Specification, to be considered as an OASIS Standard:

Business Centric Methodology v1.0

The TC's submission is attached below.

In accordance with the OASIS Technical Committee Process, the specification has already gone through a 30 day public review period:

http://lists.oasis-open.org/archives/tc-announce/200403/msg00015.html

OASIS members now have until the 15th of March to familiarize themselves with the submission below. OASIS members should give their
input on this question to the voting representative of their organization.

By the 16th of the month we will send out a Call For Vote to the voting representatives of the OASIS member organizations, who will
have until the end of the month to cast their ballots on whether this Committee Specification should be approved as an OASIS
Standard.

The normative TC Process for approval of Committee Specifications as OASIS Standards is found at
http://www.oasis-open.org/committees/process.php#3.4

Any statements related to the IPR of this specification are posted at:
http://www.oasis-open.org/committees/bcm/ipr.php

Mary

Mary P McRae
Manager of TC Administration, OASIS
email: mary.mcrae@oasis-open.org
phone: 603.232.9090

-----------------------

The OASIS Business Centric Methodology Technical Committee is pleased to provide the following documentation with its submission of
the Committee Specification of the Business Centric Methodology, Version 1.0 Specification for Member Approval as an OASIS Standard.

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.

      The specifications and Schemas are publicly available from:
HTML:
http://www.oasis-open.org/committees/download.php/16081/bcm-v1_0-spec-pr-r03.zip
PDF:
http://www.oasis-open.org/committees/download.php/16078/bcm-v1_0-spec-pr-r03.pdf
http://www.oasis-open.org/committees/download.php/16080/bcmappendixC-v1_0-spec-pr-r03.pdf

2.   The editable version of all files that are part of the Committee Specification;
http://www.oasis-open.org/committees/download.php/5906/BCM.OASIS.SpecificationDraft.2004-03-12.doc
http://www.oasis-open.org/committees/5905/BCM.AppendixB.LinkingSwitching.2003-08-07.doc

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;

    I can certify that the schema and XML instances included in the specification are well formed and all expressions are valid.

4.  A clear English-language summary of the specification:

    The Business Centric Methodology (BCM) specification is a complementary approach to current architectures and methods for
constructing a customer-provider, net-centric infrastructure that transforms the heterogeneous interoperability problem into agility
opportunities by bridging differences between vocabularies, applications, partnerships and technologies.  The specification
addresses strategic and tactical interoperability through:

*       Unconstrained conceptual alignment
*       Authorative source mediation
*       Layering of business semantic and syntactical constraints and constructs.
*       Rational capture through templates.
*       Universal Identifiers (UIDs) of assets.

5.  A statement regarding the relationship of this specification to similar work of other OASIS TCs or other standards developing
organizations:

     The BCM work has been instructed in part by earlier work particularly the UN/CEFACT work on UMM and BPM, the ebXML work on
partner collaboration agreements, the ebXML registry work, the ebXML core components work, the ebXML architecture work, the OASIS
Content Assembly Mechanism (CAM) work and work by external authorities such as Zachman and the Zachman framework and Daniel S.
Appleton, Principles of Business Engineering.  Other current related work within OASIS includes ebBP, ebSOA, and ebRM.

6.  Certification by at least three OASIS member organizations that they are successfully using the specification consistently with
the OASIS IPR Policy:

1.  DOD Endorsement: 
http://www.oasis-open.org/apps/org/workgroup/bcm/email/archives/200602/msg00004.html
Date 07 February 2006

2.   Met Life Endorsement: 
http://www.oasis-open.org/apps/org/workgroup/bcm/email/archives/200601/msg00006.html
Date 26 January 2006

3.  Semantion
http://www.oasis-open.org/apps/org/workgroup/bcm/email/archives/200509/msg00001.html
Date 20 September 2005

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;

No comments/issues were raised during the public review and liaison and review by associated OASIS TC groups that ended in December,
2004.

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;

     The specification was unanimously approved by BCM TC members.

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;

     This specification has not previously been submitted to OASIS for standardization.

10.  A pointer to the publicly visible comments archive for the originating TC;

     - http://lists.oasis-open.org/archives/bcm-comment/

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.

    No such reports exist as the specification was unanimously approved.

Regards,
Mike Lubash
Co-Chair BCM TC