[Updated versions of the Tag Suite have been released. Current version information is available here.]
Version 2.2 was released on June 8, 2006. Following is a list of updates.
The files for Version 2.2 are available:
by anonymous FTP: ftp://ftp.ncbi.nih.gov/pub/archive_dtd/publishing/
on the web: journalpublishing.dtd
The Tag Library for version 2.2 is here: http://dtd.nlm.nih.gov/publishing/tag-library/2.2/
Version 2.2 was a minor dot release that added small changes (typically new attribute values) that were requested by NLM and other users based on operational concerns. The three Tag Sets for describing journal articles were all changed; the book, historical book, and book collection Tag Sets were not modified in this release.
Version Number and Date—The version number for all changed Suite modules, the Publishing Tag Set (Blue), the Archiving Tag Set (Green), and the Article Authoring Tag Set (Pumpkin) was set to “v2.2 20060430”. This change was made in the initial comments for a module, in the formal public identifier in the module, in the Suite Module of Modules or the Tag Sets themselves where the modules were called, and in the XML and SOCAT catalogs.
That change was made in the following Suite modules:
Versioning Note: Only modules that have changed are marked as version 2.2. All modules change version numbers at a numbered release, but, for a dot release, a module that has not changed (for example %phrase.ent;) retains its previous version number.
Long Description—Corrected the model for <long-desc> by adding an asterisk to the #PCDATA model.
Preformat Model—Added the Parameter Entity %phrase.class; to the content model for the <preformat> element to allow use of <named-content> inside <preformat>.
Price—Added new element <price> and made a new class for it %price.class; so that it can be added selectively to elements, initially to the <product> element. (Note: The Authoring Tag Set [Pumpkin] has overridden the base modules and so does not see this change.)
Section (Note: The Authoring Tag Set [Pumpkin] has overridden the base modules and so does not see these changes.)
Section Metadata—Added new element <sec-meta> to the start of the content models for section (%sec-model;) and section optional title model (%sec-opt-title-model;). There are sections that are authored independently, even in journal articles, and this allows additional metadata for such sections, allowing contributors to be listed at the section level.
Section Meta Model—Added New Parameter Entity %sec-meta-model; to hold the content of the new element.
Signature Block—Added new element <sig-block>. A <sig-block> may be located at the end of the <body> in journal articles.(Note: The Authoring Tag Set [Pumpkin] has overridden the base modules and so does not see this change.) This element will hold any graphic signatures, text describing the contributors, etc. A <sig-block> contains text plus face markup and the new element <sig>, which holds the information for a single contributor. A new default class %sig.class; was created to hold the Signature <sig>.
Verse Group—Added new optional <title> and <subtitle> elements to the beginning of <verse-group>, through the %verse-group-model; Parameter Entity.
Paragraph Attribute Parameter Entities — Added new Parameter Entities %caption-model; and %inline-graphic-model; to hold the complete content models for their respective elements so that the models can be more easily over-ridden.
Related Article Type—Added a new suggested value “partial-retraction” to the “related-article-type” attribute of <related-article>.
Paragraph Attribute Parameter Entity—Added the new Parameter Entity %p-atts; to hold the attribute list for a Paragraph <p> so that it can be more easily over-ridden.
Person Group Type—Added "director" to list of suggested values for this CDATA attribute.
In addition to the full Suite changes listed in Changes to the Entire Suite, the following changes were made to the Publishing Tag Set and its specific modules. Each changed module had its formal public identifier and comment date changed, which was reflected in the two catalog files and the module calls in the Tag Set. Modules changed include:
Preformat Model—Added %phrase.class; to the model of <preformat>, mirroring what was done in the base Suite, to allow use of <named-content> inside <preformat>.
Publisher Location—Allowed <email>, <uri>, and <ext-link> inside <publisher-loc>; changed through the Parameter Entity %publisher-loc-elements;.
Section—Made all the changes needed to bring Blue along with the Suite and in addition, modified the use of <label>:
Label—Added optional <label> element to the start of the content models for section (%sec-model;) and section optional title model (%sec-opt-title-model;). The change is to accommodate use of the Blue Tag Set for articles that have already been published.
Signature Block—Added <sig-block> to the end of article <body>. Used Parameter Entity over-rides to modify the models of both <sig-block> (using %sig-block-elements;) and <sig> (using %sig-elements;) to include all phrase-level elements in the textual mix.
Sub-article and Response—Added a new element <front-stub> as an alternative to the typical <front> metadata inside a <sub-article>, so that not as much metadata is replicated between the article and sub-article. For example, a <sub-article> that uses a <front-stub> will inherit all of its <journal-meta> from the journal meta of the associated article. Also changed the model for %article-short-model;, which is used only for <response> to also use <front-stub>.
Article Types Values—Added new values to “article-types” (which is used on both the element <article> and the element <sub-article>):
ID Attributes—Added to the elements <sub-article> and <response> through their respective attribute Parameter Entities.
Person Group Type—Added “director” to list of suggested values for this CDATA attribute, mirroring what was done in the base Suite.
Response Type Attribute—Changed the comment on this attribute to reflect actual usage. First, the use of the attribute is no longer discouraged. Second, there are a few suggested values.
A Frequently Asked Questions page is available.
In addition to the DTD format, the Tag Set is also available as a W3C XML schema and as a RELAX NG schema. Both are generated directly from the DTD and neither is intended for maintenance. See the individual schema pages for more information.
Last updated: September 17, 2012