BITS 2.0 and JATS 1.1 Changes

Based on user experience using the Question and Answers model in BITS Version 1.0, the Question and Answer model has been significantly modified. Among the changes:

• The usage of the element <answer> has been limited to contain only correct answers to questions; it should not be used for the possible answers to multiple-choice style questions.
• The element <option> has been created for the options provided for multiple-choice style questions.
• The <explanation> element is now allowed to appear separately from either questions or answers, since many users fill entire sections with <explanation>s.
• The usage of the pointing attributes (of type ID and IDREF) in associating questions, answers, and explanations has been redesigned. The @rid on <question> has been removed. The @rid on <answer> has been replaced with @pointer-to-question. The @rid on <explanation> has been replaced with @pointer-to-explained. It is intended that each <answer> will point to its question(s). Each <explanation> will point to the object(s) it is explaining. Therefore best practice will be to provide an @id attribute on questions, answers, and question-wraps. Other cross-references associated with a question, answer, or explanation should be part of the text and referenced with an <xref> or <ext-link> element.
• Question Preamble (<question-preamble>) has been created to hold material that is referenced by two or more questions. This is often used when a reading, figure, or map is displayed once and several questions refer to this shared material.
• Question Wrapper Group (<question-wrap-group>) has been provided to contain material that is germain to several questions (tagged as <question-preamble>) as well as the questions with which that material is associated (which will be tagged as <question-wrap> elements).

Two new elements (<index-title-group> and <toc-title-group>) were created to contain the various title-related structures (label, titles, subtitles, etc.) inside the Index and Table of Contents.

In the previous BITS version, models for the structural index (<index>, <index-div>, and <index-group>) contained the element <title-group> as a direct child. Since the element <title-group> is also used inside book-part metadata and collection metadata, this tied the models for Index to book parts and collections in a way that would not allow these structures to evolve independently. The new <index-title-group> element will preform the same function thaT <title-group> performed, but will also allow a clean separation between Indexes and other parts of books.

Similarly, in the previous BITS version, models for the structural Table of Contents (<toc>, <toc-div>, and <toc-group>) contained the element <title-group> as a direct child. Since the element <title-group> is also used inside book-part metadata and collection metadata, this tied the models for TAble of Contents to book parts and collections in a way that would not allow these structures to evolve independently. The new <toc-title-group> element will preform the same function thaT <title-group> performed, but will also allow a clean separation between Indexes and other parts of books.

The model for the Ruby element (<ruby>) changed between versions 1.1d1 and 1.1d3 of JATS. The intent of the JATS Standing Committee was to follow the lead of the W3C HTML5 specification in how to model Ruby. HTML5 changed between the two drafts of JATS, and the JATS Standing Committee chose to follow the new HTML5 model, even though it was not the same and not backwards compatible with JATS Version 1.1d1. Thus in JATS 1.1,the Ruby model <ruby>, may contain only a single Ruby textual annotation (<rt>) on a given Ruby base (<rb>). The previous model allowed multiple annotations to cover a single Ruby base.

In this Tag Set, ruby parenthesis (<rp>) can be used to separate the Ruby base from the textual annotation.