New OASIS Discussion List for Bridge API

OASIS members have requested that we open a new discussion list to explore interest in starting an OASIS Bridge API TC (details below). The proposal conforms to

OASIS rules and is presented below.

Standards are always improved by broad participation. OASIS encourages open discussions about possible new TCs by offering a dedicated e-mail list for 90 days upon member request. The address of this discussion list is:

Anyone may subscribe to this list in order to discuss the merits and details of the proposed project. The list is now open, and can be joined by sending a message to:

The discussion list is governed by Section 2.1 of the OASIS TC Process and will remain open until 17 November 2011. Typically, participants in the list will determine

whether there is sufficient interest to form an OASIS TC, and then collaborate on a draft TC charter for submission.

Only subscribers to the list will have the ability to post to it. If you do not wish to subscribe but would like to monitor the discussion, archives of the list will be visible at http://lists.oasis-open.org/archives/.

Please feel free to forward this announcement to other appropriate lists. OASIS is an open standards organization, and welcomes your feedback. We look forward to assisting parties interested in joining the community of implementers, technologists, academics and end-users contributing to open standardization for e-business and information exchange.

---------- Discussion List Proposal ----------

(1) Name of discussion list:

Bridge API

(2) Preliminary statement of scope:

We are considering the creation of an OASIS Bridge API TC with a charter focused on producing guidelines for facilitating and encouraging the further development of a Bridge API which is a standard web service based exchange protocol for exchanging data between content authoring environments and the Common Source Database (CSDB) Management Systems that manage and control the data sets.

The API already exists and is almost ready for its initial release. The intention is to move the continued development of the Bridge API into an OASIS TC.

The benefits of a Bridge API are:

• Ability of Learning Content developers to seamlessly reuse technical data modules

• Ability of any Content Authoring Tool to exchange data with any technical publication database environment

Implementations of the draft Bridge API are currently being implemented for verification purposes by several vendors.

The Bridge API specification was primarily developed for SCORM and S1000D, but has a larger potential. The scope of the specification and the TC Charter needs to be further discussed.

(3) The names, electronic mail addresses, and membership affiliations of the three or more Eligible Persons:

Svante Ericsson, svante.ericsson@corena.com, Corena Sverige AB

Mats Bertilsson, mats.bertilsson@corena.com, Corena Sverige AB

Anna Ohrnell, anna.ohrnell@fmv.se, FMV

Mats Nilsson, mats.nilsson@fmv.se, FMV

Wayne Gafford, wayne.gafford@adlnet.gov, Advanced Distributed Learning

Leif Gyllstrom, leif.gyllstrom@saabgroup.com, Saab Support and Services

(4) The name of the discussion list leader:

Mats Bertilsson, mats.bertilsson@corena.com, Corena Sverige AB

Messages By Date: members message