REQIF11 — XHTML integration does not work as expected

A key feature of the Requirements Interchange Format is the ability to exchange formatted content (e.g. bulleted lists, text with fonts applied etc.) between requirements authoring tools.
Transporting formatted content is implemented in ReqIF by the use of W3C’s XHMTL, and the XHTML integration does not work as proposed in the beta2 version of ReqIF, rendering the format almost useless for non-trivial exchanges.

Background:
In earlier, “non-OMG” versions of the Requirements Interchange Format, XHTML had already been incorporated, but using a proprietary, customized XHTML schema.
For better compliance with international standards, XHTML has been incorporated using a XML schema driver for the beta2 OMG version.

As only a subset of XHTML should be included, the project group needed to incorporate so-called XHTML XML schema “modules”, which proved to be a complex task.
Not until the implementation of a ReqIF based transformation tool, it turned out that some XHTML element definitions were not pulled in from the W3C modules, but only their XML schema types.

This currently makes it impossible to use these XHTML elements in XML documents conforming to the ReqIF XML schema.

Resolution:
Rewrite the XHTML schema driver (which incorporates XHTML in ReqIF), in a way that all needed XHTML elements can be used in ReqIF XML documents.
In other words: replace the file driver.xsd with a new version that works as expected and adapt chapter 11.4 of the specification, which shows the content of driver.xsd, accordingly.
This new version has already been created and tested by ProSTEP.

Replace the ReqIF 1.0 driver.xsd file (dtc/10-12-15) by the revised version
dtc/11-02-12, and adapt chapter 11.4 of the specification dtc/10-12-11,
which shows the content of driver.xsd, accordingly.