The intent of the NLM Journal Archiving and Interchange Tag Suite is to provide a common format in which publishers and archives can exchange journal content. The Suite provides a set of XML schema modules that define elements and attributes for describing the textual and graphical content of journal articles as well as some non-article material such as letters, editorials, and book and product reviews.
The Article Authoring Tag Set creates a standardized format for new journal articles that can be used by authors to submit publications to journals and to archives such as PubMed Central. While in theory the document scope is the same as for the Publishing Tag Set, in practice Authoring defines elements and attributes that describe the content of typical research-style journal articles.
This is a Tag Set optimized for authorship of new journal articles, where regularization and control of content is important, and where it is useful rather than harmful to have only one way to tag a structure. Therefore, Authoring is more prescriptive than descriptive and includes many elements whose content must occur in a specified order.
Since an author is assumed to be creating and submitting an article for submission to a journal or journals, no publishing history or journal-specific information has been included in this Authoring Tag Set.
Since no assumptions can be made concerning the processing software or editorial situation that will receive an article authored in this Tag Set, tagging that forces specific formatting has also been avoided. There is no way for an author to number his/her lists explicitly, for example, or to manually number the cited references, since many journals have their own citation policies and publication styles. Numbers for the cited references must be generated by the publisher’s software to match editorial policy and established practice.
By design, this is a model for journal articles, such as the typical research article found in an STM journal, and not a model for complete journals. This Tag Set does not include an overarching model for a collection of articles. In addition, the following journal material is not described by this Tag Set:
The Article Authoring Tag Set defines a document that is a top-level component of a journal such as an article, a book or product review, or a letter to the editor. Each such document is composed of one or more parts; if there is more than one part, they must appear in the following order:
This Tag Set is one of several created from the Suite. Information about these Tag Sets may be found at the following site: http://dtd.nlm.nih.gov.
Because access for a wide range of output devices, as well as for the visually impaired, is becoming more and more important in the STM journal community, the modules in the Archiving and Interchange Suite were designed to follow, as much as possible, the W3C Web Content Accessibility Guidelines 2.0 working draft (22 August 2002), which was the latest accessibility specification available when the Suite was initially constructed. This Specification specifies accessibility guidelines on many levels from design through application. The guidelines which pertain to the modeling of materials were followed to at least Level-2 compliance. For example, a Long Description <long-desc> element was defined as part of many other elements, such as Figure <fig>, so it can be added not only to all figures and other graphical objects, but to any section of the text (for example, to a Boxed Text <boxed-text>) to provide an accessible description of the object. The @xml:lang attribute was added to all section-level elements and many paragraph-level elements to permit explicit indication of the language of the content, as required by these guidelines. The Abbreviation or Acronym <abbrev> element (also to be used for acronyms) was added to meet Checkpoint 4.3.
Because access for a wide range of output devices, as well as for the visually impaired, is becoming more and more important in the STM journal community, the modules in the Archiving and Interchange Suite were designed to follow, as much as possible, the W3C Web Content Accessibility Guidelines 2.0 working draft (22 August 2002), which was the latest accessibility specification available when the Suite was initially constructed. This Specification specifies accessibility guidelines on many levels from design through application. The guidelines which pertain to the modeling of materials were followed to at least Level-2 compliance. For example, a Long Description <long-desc> element was defined as part of many other elements, such as Figure <fig>, so it can be added to all figures and other graphical objects to provide an accessible description of the object. The @xml:lang attribute was added to all section-level elements and many paragraph-level elements to permit explicit indication of the language of the content, as required by these guidelines. The Abbreviation or Acronym <abbrev> element (also to be used for acronyms) was added to meet Checkpoint 4.3.
|
Element |
Elements are nouns, like “speech” and “speaker”, that represent components of journal articles, the articles themselves, and accompanying metadata. |
|
Attribute |
Attributes hold facts about an element, such as which type of list (e.g., numbered, bulleted, or plain) is being requested when using the List <list> tag, or the name of a pointer to an external file that contains an image. Each attribute has both a name (e.g., @list-type) and a value (e.g., “bullet”). |
|
Metadata |
Data about the data, for example, bibliographic information. The distinction is between metadata elements which describe an article (such as author of the article) versus elements which contain the textual and graphical content of the article. |
The Article Authoring Tag Set is available on the NLM Journal Archiving and Interchange Tag Suite Website including: the Tag Set models expressed as DTDs, XSD schemas, and RELAX NG schemas; one or more tagged sample documents; and this Tag Library documentation (a set of linked HTML files). The DTD file delivery includes the Article Authoring DTD; the Tag Set customization files needed for the Article Authoring Tag Set to override the declarations in the modular Suite, any new modules that define Tag-Set-specific elements, and the modules that comprise the full Suite.
How you use the documentation will depend on what you need to learn about the modules and the Tag Set.
If you want to learn about the elements and the attributes in this Tag Set so you can tag documents or learn how the journal article model is constructed, here is a good way to start.
Finally, if you are interested in conversion from a particular source:
This Tag Library contains the following sections:
|
How To Use (Read Me First |
How to make best use of this Tag Library to reference XML tags, become familiar with the Authoring Tag Set as a whole, or see examples of recommended usage. |
|
Introduction |
This introduction to the contents of this Tag Library, to the design philosophy and intended usage of the Archiving and Interchange Suite, and to the Article Authoring Tag Set. |
|
Elements Section |
Descriptions of the elements used in the Article Authoring Tag Set and the parts of the Archiving and Interchange Suite used in this Tag Set. The element descriptions are listed in alphabetical order by tag name. [Note: Each element has two names: a “tag name” (formally called an element-type name) that is used in tagged documents, in the DTDs/schemas, and by XML software; and an “element name” (usually longer) that provides a fuller, more descriptive name for the benefit of human readers. For example, a tag name might be <disp-quote> with the corresponding element name Quote, Displayed, or a tag name might be <verse-group> with the corresponding element name Verse Form for Poetry.] |
|
Attributes Section |
Descriptions of the attributes in the Article Authoring Tag Set. Like elements, attributes also have two names: the shorter machine-readable one and a (usually longer) human-readable one. Attributes are listed in order by the shorter, machine-readable names. For example, the attribute short name @list-type instead of the more informal, easier to read: Type of List. |
|
Parameter Entity Section |
Names (with occasional descriptions) and contents of the parameter entities in the Tag Set modules. |
|
Document Hierarchy Diagrams |
Tree-like graphical representations of the content of many elements. This can be a fast, visual way to determine the structure of an article or of any element within an article. |
|
Full Article Sample |
One full article is provided in both PDF format and in XML according to this Tag Set. This is provided to help users understand the relationship between the article as displayed and the XML version of the article. |
|
Common Tagging Practice |
Tips, tricks, hints, and examples of how (and why) to tag certain structures using this Tag Set. |
|
Implementing This Tag Set |
Implementor’s instructions for using the Tag Set, customizing this Tag Set, or making derivative tag sets based on this one. |
|
Change Report: Version 3.0 |
Detailed information about the changes between version 3.0 and 2.3 for both for the base Suite and the Article Authoring Tag Set. The report has two sections: the first identifies how each element changed between the two versions; the second provides an implementor’s view of the changes in parameter entities, content models, attribute lists and/or values, etc. |
|
DTD, XSD, and RNG |
The Article Authoring Tag Set is available in three forms: an XML Document Type Definition (DTD); a W3C XML Schema (XSD); and a RELAX NG Schema (RNG). Each of these formats is available in two forms: a zipped file containing a downloadable version of the schema (often in multiple files), and a readable/browsable version in which the internal markup has been escaped. |
|
Context Table |
A listing of where each element may be used. All elements in the Tag Set are given in a single alphabetical list. The Context Table is formatted in two columns. The first column (“This Element”) names an element, with the name shown in pointy brackets. In the second column (“May Be Contained In”) for each element is an alphabetical list of all the elements in which the first column element may occur. For example, if the first column contains the element <front> and the second column contains only the <article> element, this means that the <front> element may only be used directly inside an <article>. Most elements may be used inside more than one other element. For example, the element <def> (a definition) may be used inside the <abbrev> and the <def-item> elements. The Context Table contains the same information that is found on each element page under the heading “May Be Contained In”. |
|
Index |
Where to find elements, tags, and terms used in this Tag Library. Includes synonyms (terms not used in this Tag Set) that direct the reader to elements used in this Tag Library, for example, “author” is paired with Contributor <contrib>. |
| <alt-text> | The tag name of an element (written in lower case with the entire name surrounded by “< >”) |
| Alternate Title Text (For a Figure, Etc.) | The element name (long descriptive name of an element) or the descriptive name of an attribute (written in title case, with important words capitalized, and the words separated by spaces) |
| must not | Emphasis to stress a point |
This version of the Tag Suite and the derivative Tag Sets marks a significant departure from all previous versions. Before now, all changes to the Suite had been fully backward compatible. That meant that while the Suite changed and grew, no document tagged according to a particular Tag Set was invalid because of any new or changed models. For the first time, this is not the case. Version 3.0 is non-backward compatible, meaning documents which were valid against any previous version may not be valid against this version. Some users will choose to keep their existing documents as they are, valid according to an older version of the Tag Set and to use the new Tag Set for future documents. Some users will convert their existing documents to the new Tag Set, a conversion that we believe will be mostly automatable in most cases. It is possible that some users will choose to continue to use an older version of the Tag Set.
The rationales behind the changes vary, but all were made with the intent to make it easier to move forward. There has been nearly six years of experience working with this Tag Set on journal articles as varied as medicine, biotechnology, and physics. Many of the changes were of the “if we had known then what we know now” variety. Others were changes that have been obvious improvements for four or five years, but could not be made within the scope of normal maintenance because they would have been non-backward compatible.
Version 3.0 includes the regular scope changes and additions that have been the subject of previous version releases. For example, a new funding model (<funding-group>) has been added to reflect the changing needs of the community. In addition to this kind of change, version 3.0 changes also include:
A report listing all changes is available in the Change Report section.