Path: blob/main/tests/docs/jats/xsd/JATS-Authoring-1-2-MathML3-DTD/JATS-articleauthcustom-mixes1.ent
3593 views
<!-- ============================================================= --> <!-- MODULE: Article Authoring DTD Over-ride Mixes Module --> <!-- VERSION: ANSI/NISO JATS Version 1.2 (Z39.96-2019) --> <!-- DATE: February 2019 --> <!-- --> <!-- ============================================================= --> <!-- ============================================================= --> <!-- PUBLIC DOCUMENT TYPE DEFINITION --> <!-- TYPICAL INVOCATION --> <!-- "-//NLM//DTD JATS (Z39.96) Article Authoring DTD Over-ride Mixes Module v1.2 20190208//EN" Delivered as file "JATS-articleauthcustom-mixes1.ent" --> <!-- ============================================================= --> <!-- ============================================================= --> <!-- SYSTEM: Article Authoring DTD of the JATS DTD Suite --> <!-- --> <!-- PURPOSE: To declare the Parameter Entities (PEs) used to --> <!-- over-ride the JATS DTD Suite default named, --> <!-- general purpose mixes. (Mixes for particular --> <!-- elements are declared in the Article Authoring --> <!-- DTD Models module.) --> <!-- --> <!-- Note: Since PEs must be declared before they --> <!-- are used, this module must be called before the --> <!-- default mixes modules (%default-mixes;) --> <!-- --> <!-- TAG SET SPONSOR --> <!-- National Center for Biotechnology --> <!-- Information (NCBI) --> <!-- National Library of Medicine (NLM) --> <!-- --> <!-- CREATED FOR: --> <!-- This DTD was created from the JATS DTD Suite. --> <!-- Authors, digital archives, and publishers may --> <!-- use the DTD as is for markup of journal --> <!-- literature or related material for archiving --> <!-- and transferring such material between archives --> <!-- or create a custom XML DTD from the Suite for --> <!-- these purposes. --> <!-- --> <!-- This DTD is in the public domain. An organization --> <!-- that wishes to create its own DTD from the suite --> <!-- may do so without permission from NLM. --> <!-- --> <!-- The suite has been set up to be extended using a --> <!-- new DTD file and a new DTD-specific customization --> <!-- module to redefine the many Parameter Entities. --> <!-- Do not modify the suite directly or redistribute --> <!-- modified versions of the suite. --> <!-- --> <!-- In the interest of maintaining consistency and --> <!-- clarity for potential users, NLM requests: --> <!-- --> <!-- 1. If you create a DTD from the JATS DTD Suite --> <!-- and intend to stay compatible with the suite, --> <!-- then please include the following statement --> <!-- as a comment in all of your DTD modules: --> <!-- "Created from, and fully compatible with, --> <!-- the ANSI/NISO Z39.96 Journal Article Tag --> <!-- Suite (JATS)." --> <!-- --> <!-- 2. If you alter one or more modules of the suite, --> <!-- then please rename your version and all its --> <!-- modules to avoid any confusion with the --> <!-- original suite. Also, please include the --> <!-- following statement as a comment in all your --> <!-- DTD modules: --> <!-- "Based in part on, but not fully compatible --> <!-- with, the ANSI/NISO Z39.96 Journal Article --> <!-- Tag Suite (JATS)." --> <!-- --> <!-- ORIGINAL CREATION DATE: --> <!-- June 2005 --> <!-- --> <!-- CREATED BY: Mulberry Technologies, Inc. for the NISO Z39.96 --> <!-- Working Group. Mulberry Technologies was --> <!-- supported by National Center for Biotechnology --> <!-- Information (NCBI), a center of the US National --> <!-- Library of Medicine (NLM). --> <!-- --> <!-- The Article Authoring DTD is built from the --> <!-- Archiving and Interchange DTD Suite. --> <!-- --> <!-- Suggestions for refinements and enhancements to --> <!-- this DTD should be sent in email to: --> <!-- [email protected] --> <!-- ============================================================= --> <!-- ============================================================= --> <!-- DTD VERSION/CHANGE HISTORY --> <!-- ============================================================= --> <!-- Version Reason/Occasion (who) vx.x (yyyy-mm-dd) ============================================================== JATS Version 1.2 (ANSI/NISO Z39.96-2019) (DAL/BTU) v1.2 (2019-02-08) NISO JATS is a continuing maintenance NISO Standard, which requires voting by the both the NISO and ANSI membership to be changed. This version of the NISO JATS was approved by ANSI vote on Feb 08, 2019, so it supersedes all Committee Drafts as well as the draft version JATS 1.2 2018 (the version submitted for vote), becoming NISO JATS v1.2 20190208 (ANSI/NISO Z39.96-2019). 13. JATS "1.2" becomes "v1.2 20190208" (final ANSI vote date) "ANSI/NISO Z39.96-2015" becomes "ANSI/NISO Z39.96-2019" ============================================================== JATS Version 1.2 (ANSI/NISO Z39.96-2018) and BITS 2.1 (v2.0 20180401) (DAL/BTU) v1.2 (2018-11-30) NISO JATS is a continuing maintenance NISO Standard, which requires voting by the both the NISO and ANSI membership to be changed. This version of the NISO JATS was approved by ANSI and NISO vote, so it supersedes all Committee Drafts and becoming NISO JATS 1.2 (ANSI/NISO Z39.96-2018). 12. BITS "2.1" and "v2.0 20180401" remains unchanged. JATS "1.2d2" and "v1.2d2 20180401" became JATS "1.2" and "v1.2 20181130" ============================================================= BITS Version 2.1 (DAL/BTU) v2.1 (2018-04-01) JATS Version 1.2d2 (DAL/BTU) v1.2d2 (2018-04-01) JATS is a continuing maintenance NISO Standard, which requires voting by the ANSI and NISO memberships to be changed. BITS is under continuous maintenance, and is modified at the discretion of the working group. This draft DTD represents an interim version of the non-normative JATS DTD Suite, as an indication to JATS users the decisions that have been made by the JATS Standing Committee. This draft has not yet been given public review or voting. The formal public identifiers were changed in the modules and the catalogs. 11. BITS "2.0" and "v2.0 20151225" became BITS "2.1" and "v2.1 20180401". JATS "1.2d1" and "v1.2d1 20171231" became JATS "1.2d2" and "v1.2d2 20180401". No module names were changed. ============================================================= JATS Version 1.2d1 (ANSI/NISO Z39.96-2015) (DAL/BTU) v1.2d1 (2017-12-31) NISO JATS is a continuing maintenance NISO Standard, which requires voting by the ANSI and NISO memberships to be changed. This draft DTD represents an interim version of the non-normative JATS DTD Suite, as an indication to JATS users the decisions that have been made by the JATS Standing Committee. This draft has not yet been given public review or voting. The formal public identifiers were changed in the modules and the catalogs. 10. JATS "1.2d1" and "v1.2d1 20170631" became JATS "1.2d1" and "v1.2d1 20171231". ============================================================= JATS Version 1.2d1 (DAL/BTU) v1.2d1 (2017-06-31) NISO JATS is a continuing maintenance NISO Standard, which requires voting by the ANSI and NISO memberships to be changed. This draft DTD represents an interim version of the non-normative JATS DTD Suite, as an indication to JATS users the decisions that have been made by the JATS Standing Committee. This draft has not yet been given public review or voting. The formal public identifiers were changed in the modules and the catalogs. 9. SIMPLE PHRASE - Added math class (which in Pumpkin is just <mml:math>) to simple phrase, adding it to many places, including <article-title> 8. JATS became version "1.2d1" and "v1.2d1 20170631" ============================================================= JATS Version 1.1 (DAL/BTU) v1.1 (2015-12-15) JATS is a continuing maintenance NISO Standard, which requires voting by the ANSI and NISO memberships to be changed. JATS 1.1 was approved in late 2015, so the formal public identifiers were changed in the modules and the catalogs. No model or attribute changes were made at this time. 7. JATS became version "1.1" and "v1.1 20151215" ============================================================= JATS Version 1.1d3 (DAL/BTU) v1.1d3 (2015-03-01) The changes in this release are in response to NISO License and Indicators Recommended Practice. NISO JATS is a continuing maintenance NISO Standard, which requires voting by the NISO membership to be changed. This Committee Draft 1.1d3 will be sent to the NISO voting membership, to become (if approved) NISO JATS 1.1. This draft DTD represents an interim version of the non-normative JATS DTD Suite, as an indication to JATS users the decisions that have been made by the JATS Standing Committee. 6. JATS became version "1.1d3" and "v1.1d3 20150301" ============================================================= JATS Version 1.1d2 (DAL/BTU) v1.1d2 (2014-09-30) NISO JATS is a continuing maintenance NISO Standard, which requires voting by the NISO membership to be changed. This Committee Draft 1.1d2 will be sent to the NISO voting membership, to become (if approved) NISO JATS 1.1. This catalog represents an interim version of the non-normative JATS DTD Suite, as an indication to JATS users the decisions that have been made by the JATS Standing Committee. 5. JATS became version "1.1d2" and "v1.1d2 20140930//EN" ============================================================= NISO JATS Version 1.0 (DAL/BTU) v1.0 (2012-xx-xx) 4. PARA-LEVEL PARAMETER ENTITY CONFLICT - Changed the parameter entity %para-level; to use the PE %nothing-but-para.class;, removing the similar PE "just-para.class;". It is possible to add element(s) to %just-para.class;, so that the added element(s) may be used everywhere <p> is used. Such elements would also be named in %block-display.class;. This would lead to a conflict in %para-level; if both %just-para.class; and %block-display.class; named <p>. So %just-para.class; is replaced here in %para-level;. This is backward compatible for all XML documents. If a JATS customization has modified %just-para.class; they may need to change their customization to accommodate. ============================================================= Version 0.4 (DAL/BTU) v0.4 (2011-01-31) This Tag Set is in the process of becoming a NISO standard. The version numbers are starting over from 0.4", as a Trial Use Draft, to be made into "Version 1.0" when the Tag Suite becomes a NISO standard. Thus, the version number that would have been "NLM Version 3.1 Draft" has become NISO JATS "Version 0.4". Details on NISO Trial Use Draft Version 0.4 are available at http://jats.nlm.nih.gov/JATS-0.4. 3. Updated the DTD-version attribute to "0.4" 2. Updated the public identifier to "v0.4 20110131", modified the formal public identifier to include "JATS (Z39.96)", and the filename as delivered to include "JATS" and the new version number "0". http://jats.nlm.nih.gov/0.4. ============================================================= Version 3.0 (DAL/BTU) v3.0 (2007-10-31) Version 3.0 is the first non-backward-compatible release. In addition to the usual incremental changes, some elements and attributes have been renamed and/or remodeled to better meet user needs and to increase tag set consistency. All module change histories are available through the Tag Suite web site at http://dtd.nlm.nih.gov. Details on version 3.0 are available at http://dtd.nlm.nih.gov/3.0. 1. Updated public identifier to "v3.0 20071031//EN" --> <!-- ============================================================= --> <!-- Details concerning ANSI/NISO Z39.96-2015 JATS-based DTDs, XSDs, RNGs and supporting documentation are available at http://jats.nlm.nih.gov/1.1/ --> <!-- ============================================================= --> <!-- BLOCK MIXES FOR USE IN CONTENT MODELS --> <!-- (MIXES ARE COMPOSED USING CLASSES) --> <!-- ============================================================= --> <!-- PARAGRAPH-LEVEL ELEMENTS --> <!-- Elements that may be used at the same structural level as a paragraph, for example inside a Section Note: There a major overlap between this parameter entity and that for the elements that are at the same level as a paragraph. Inline elements appear only inside a paragraph, but block elements such as quotes and lists may appear either within a paragraph or at the same level as a paragraph. This serves a requirement in a repository DTD, since some incoming material will have restricted such elements to only inside a paragraph, some incoming material will have restricted them to only outside a paragraph and some may allow them in both places. Thus the DTD must allow for them to be in either or both. --> <!ENTITY % para-level "%block-display.class; | %block-math.class; | %list.class; | %nothing-but-para.class; | %rest-of-para.class;" > <!-- ============================================================= --> <!-- INLINE MIXES FOR USE IN CONTENT MODELS --> <!-- (MIXES ARE COMPOSED USING CLASSES) --> <!-- ============================================================= --> <!-- EMPHASIS MIX ELEMENTS --> <!-- Elements that may be used inside most of the emphasis class elements --> <!ENTITY % emphasized-text "| %address-link.class; | %article-link.class; | %emphasis.class; | %inline-display.class; | %inline-math.class; | %phrase.class; | %simple-link.class; | %subsup.class;" > <!-- JUST RENDITION --> <!-- Only the simplest of the typographic emphasis elements, as well as subscript and superscript. Usually used in a model that allows #PCDATA and this restricted mixture. This mix may be stripped down to only subscript and superscript by some, more restrictive DTDs. MAINTENANCE NOTE: This Parameter Entity and the related PE "rendition-plus" have been put in place to restrict the amount of variability that a person modifying the DTD through PE redefinition can achieve. Some elements have been set #PCDATA plus one PE and some have been set to #PCDATA plus the other in an effort to allow designers to modify entire groups of elements, but not to change similar models individually . --> <!ENTITY % just-rendition "" > <!-- RENDITION MARKUP PLUS --> <!-- Only the simplest of the typographic emphasis elements, as well as subscript and superscript. Usually used in a model that allows #PCDATA and this restricted mixture. This mix may be enhanced slightly in some more permissive DTDs, and should always contain at least typographic emphasis, subscript, and superscript. MAINTENANCE NOTE: This Parameter Entity and the related PE "just-rendition" have been put in place to restrict the amount of variability that a person modifying the DTD through PE redefinition can achieve. Some elements have been set #PCDATA plus one PE and some have been set to #PCDATA plus the other in an effort to allow designers to modify entire groups of elements, but not to individually change similar models. modify entire groups of elements, but not to change similar models individually . --> <!ENTITY % rendition-plus "| %emphasis.class; | %subsup.class;" > <!-- SIMPLE PHRASE-LEVEL TEXTUAL ELEMENTS --> <!-- Elements that may be used almost anywhere text is used, for example, inside a title. Simple text plus inline display and math elements. --> <!ENTITY % simple-phrase "| %address-link.class; | %emphasis.class; | %inline-display.class; | %inline-math.class; | %math.class; | %phrase.class; | %simple-link.class; | %subsup.class;" > <!-- SIMPLE TEXTUAL CONTENT --> <!-- Elements that may be used inside elements that are really expected to be #PCDATA and not to contain any of these things. Note that there is no math and no links. Simpler even than %simple-phrase; Design Note: Inline mixes begin with an OR bar --> <!ENTITY % simple-text "| %emphasis.class; | %inline-display.class; | %inline-math.class; | %phrase.class; | %subsup.class; " > <!-- ================== End Authoring DTD Mixes Customization ==== -->