OASIS Business-Centric Methodology (BCM) TC

Join TC     TC Page     Send a comment to this TC

Defining methods to acquire interoperable e-business information systems within communities of interest

Carl Mattocks, carlmattocks@gmail.com, Chair
Hans Aanesen, hans@eprforum.no, Secretary

Table of Contents


The BCM team is pleased to announce that the OASIS BCM V1.0 specifications are now recently approved as an OASIS standard specification according to the OASIS approved process.


The purpose of the OASIS Business-Centric Methodology (BCM) TC is to develop a specification which will provide business managers with a set of clearly defined methods with which to acquire agile and interoperable e-business information systems within communities of interests.

There is a quick overview and introductory brochure on BCM.
A powerpoint presentation (used at the OASIS symposium at New Orleans) explains the role of BCM when using XML for a Reliable Infrastructure.
A supporting powerpoint presented at the WWW Semantic Grid Workshop defines the role of BCM when developing e-business Grid / P2P capabilities.

For more information, see the TC Charter and FAQ


Technical Work Produced by the Committee

OASIS/Business Centric Methodology Specification V1.0

Appendix A and B on patterns and linking and switching support

Wiki for OASIS BCM TC member collaboration

Mailing Lists and Comments

bcm: the list used by TC members to conduct Committee work. TC membership required to post. TC members are automatically subscribed; the public may view archives.

bcm-comment: a public mail list for providing input to the OASIS bcm Technical Committee members. Send a comment or view archives.

Additional Information

Click here for an Introductory brochure on BCM.

Click here for a brochure introducing the EPR and erpXML work
Additional resources on EPR from the EPRforum website.

Additional whitepapers, wallchart posters and presentation materials maybe found at the BCM resource site.

Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.