Path: blob/main/tests/docs/jats/xsd/JATS-Authoring-1-2-MathML2-DTD/JATS-articleauthcustom-models1.ent
3593 views
<!-- ============================================================= --> <!-- MODULE: Article Authoring DTD Over-ride Content and --> <!-- Attribute 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 Content and Attribute Module v1.2 20190208//EN" Delivered as file "JATS-articleauthcustom-models1.ent" --> <!-- ============================================================= --> <!-- ============================================================= --> <!-- SYSTEM: Article Authoring DTD of the JATS DTD Suite --> <!-- --> <!-- PURPOSE: To declare the Parameter Entities (PEs) used to --> <!-- over-ride the content models, parts of content --> <!-- models, or attribute lists of the JATS DTD Suite --> <!-- --> <!-- Or-groups within models should use mixes or --> <!-- classes rather than name elements directly. --> <!-- --> <!-- Note: Since PEs must be declared before they --> <!-- are used, this module must be called before the --> <!-- content modules that declare elements. --> <!-- --> <!-- 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). 50. 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). 49. 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. 48. PERSON GROUP TYPES - Replaced the CDATA value for @person-group-type with list of values, parameter entity %person-group-types;, reversing the decision of Version 1.2d1. 47. FOOTNOTES - Made @fn-type from CDATA into a restricted list, reversing the decision of version 1.2d1. - Added back the %fn-types; PE, which is used for values of @fn-type - Added new value "coi-statement", which is best practice replacing value "conflict", which was left on the list. 46. NON-MONETARY SUPPORT - Inside <article-meta> added new <support-group> to hold both funding and non-monetary support descriptions. <support-group> is both a peer to <funding-group> (backward compatibility) and contains <funding-group>. 45. ARRAY - Element added for use in embedded index terms ONLY. Model reduced to the same as that of Blue; therefore, override for array-model added here. 44. 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. 43. 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. 42. SOURCE - Deleted the override for source elements, since Blue, Pumpkin, and the default all have the same model. 41. PERSON GROUP TYPES - Replaced the %person-group-types; parameter entity (allauthors | assignee | author | compiler | curator | director | editor | guest-editor | illustrator | inventor | research-assistant | translator | transed) with CDATA to allow all types. 40. SOURCE/CHAPTER TITLE/PART TITLE - Added the following elements to <source>, <chapter-title>, and <part-title> to more closely mirror the model of <article-title>: - abbrev.class (abbrev) - inline-display.class alternatives | inline-graphic | private-char - inline-math.class chem-struct | inline-formula - math.class mml:math - phrase-content.class named-content | styled-content 39. ARTICLE META MODEL - Added new optional element <article-version> inside <article-meta> to hold one version number for the article. 38. PERSON-GROUP - Made @person-group-type values into a parameter entity and added values "illustrator" and "research-assistant". - Removed string-name.class PE from PE person-group-elements because <string-name> was added to name.class, which person-group-elements already used. 37. FOOTNOTES - Made @fn-type into a CDATA from a restricted list. Deleted %fn-types; PE, which used to be used. 36. 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. 35. 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. 34. JATS became version "1.1d3" and "v1.1 20150301//EN" ============================================================= 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. 33. COLLAB ATTRIBUTES - Redefined to get rid of @symbol 32. UNUSED PARAMETER ENTITIES DELETED - aff-model - fig-group-model 31. VERSION ELEMENTS EDITION The new element <version> uses the PE %-just-rendition, but Authoring has set that PE to null, so the <version> element added <sup> and <sub> to be like the content of <edition>. 30. VALUE LIST FOR PERSON-GROUP-TYPE Added "curator" to the list of person-group role values. 29. NAME OF JATS COMMON ATTRIBUTES Common attlists renamed with "jats-" at the front. 28. TITLE FOR LIST ITEMS Added an optional <title> to the beginning of each <list-item>. 27. EDITION ELEMENTS - Added <sub> and <sup> to the model of edition. These were needed now that the "Edition" element has been renamed and repurposed as "Edition Statement". 26. STATEMENT - Added new statement.class inside the model for <statement>, so that statements can be recursive. 25. JATS became version "1.1d2" and "v1.1d2 20140930//EN" 24. REFERENCE TYPES - Added "collab" 23. CONFERENCE LOCATION ELEMENTS and PUBLISHER-LOC ELEMENTS - Added 3 new OPTIONAL elements: <city>, <state>, and <postal-code> 22. ADDRESS MODEL - Added 3 new OPTIONAL elements: <city>, <state>, and <postal-code> ============================================================= NISO JATS Version 1.1d1 (DAL/BTU) v1.1 (2013-11-15) ANSI/NISO Z39.96-2012 (pre-release for V1.0 BITS; Version 1.1d1) NISO JATS Standing Committee met and answered the requests and suggestions from the NISO request forms. Details concerning ANSI/NISO Z39.96-2012 JATS-based DTDs, XSDs, RNGs and supporting documentation are available at http://jats.nlm.nih.gov/1.0/ 21. GLOBAL ATTRIBUTES - Added the new parameter entity "%jats-common-atts; to every element in this module. This PE adds (for now) the @id attribute and the @xml:base attribute to every element, whether metadata or narrative. Since the @id in this parameter entity is optional, a second parameter entity jats-common-atts-id-required was also added. The two are kept in sync with the jats-base-atts parameter entity. 20. ON-BEHALF-OF NEW CONTENT Added <xref>, <fn>, and <target> (the simple links) to <on-behalf-of>. 19. NEW TOGGLE ATTRIBUTE @toggle added to the attributes for <underline> through %underline-atts;. 18. NEW ELEMENT <era> Added to the model of <date>, optional following year. 17. XML Base Added the attribute @xml:base to the Global (common) attributes used on all elements. 16. INSTITUTION WRAP ADDED Added the elements <institution-wrap> to the following elements through the institution-wrap.class: - <address> - <conf-sponsor> - <funding-source> - <publisher-name> - <std-organization> 15. ABSTRACTS AND KEYWORDS The 2 new classes described in #14 were used to add <abstract> and <keyword> to many elements in the Archiving and Publishing models. Since these were NOT to be added to Authoring, some elements that did not need to be redefined before, now need to be redefined. No content model changes were made by these redefinitions. - disp-formula-group - statement 14. ABSTRACTS AND KEYWORDS Changed "abstract*" to "(%abstract.class;)*" and "kwd-group*" to "(%kwd-group.class;)*" since those classes now exist. Elements should have a limited number of ways to be invoked. - article-meta (through %article-meta-model;) ============================================================= NISO JATS Version 1.0 (DAL/BTU) v1.0 (2012-xx-xx) ANSI/NISO Z39.96-2012 (Version 1.0) Details concerning ANSI/NISO Z39.96-2012 JATS-based DTDs, XSDs, RNGs and supporting documentation are available at http://jats.nlm.nih.gov/1.0/ 13. RELATED OBJECT - Added <related-object> everywhere <related-article> was used, including inside <article-meta> using article-meta-model. 12. CONTRIBUTOR MODEL - Added "contrib-id.class" to the beginning at the <contrib> model, to hold identifiers for people, such as publishers-specific IDs, ORCIDs, and JST and NII identifiers. 11. STANDARDS ORGANIZATION - Added std-organization-elements to reduce what was allowed in the names of standards bodies. 10. PARAGRAPH PARAMETER ENTITY SYNTAX CHANGE (no models changed) Fixed content models that were stated as "p*", "p+", and "sec*" to use the %just-para.class; and %sec.class; classes. Element models that were changed include: - abstract - ack - app-group - disp-quote-model - glossary - ref-list 9. Updated the public identifier to "v1.0 20120330//EN", modified the formal public identifier to include "JATS (Z39.96)", and the filename as delivered to include "JATS" and the new version number "1". ============================================================= 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. 8. Updated the DTD-version attribute to "0.4" 7. 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. 6. KEYWORD GROUP - Made <kwd-group> repeatable inside <article-meta> by modifying %article-meta-model; 5. MEDIA - In 3.0 <graphic> and <media> used the same model, defined by %graphic-model;. In 0.4, %media-model; was added to separate the redefinition possibilities. Since Authoring had redefined %graphic-model;, the same redefinition was necessary for <media> through %media-model;. 4. INITIALS - Removed the attribute over-ride for <surname> and <given-names> to allow the use of @initials. 3. PERSON-GROUP - Became a mixed-content model, so the parameter entity %person-group-model: was changed to %person-group-elements;, which will be mixed with #PCDATA as defined in references.ent. The PE person-group-model has been retained in references.ent for compatibility, but has been set to the mixed model using person-group-elements. 2. @SPECIFIC-USE and @XML:LANG - Added the @specific-use to the following over-rides: - fn through fn-atts (@specific-use only; @xml:lang already) - inline-graphic-atts through inline-graphic-atts (both) - list through list-atts (@xml:lang only; @specific-use already) - person-group through person-group-atts (both - underline through underline-atts (both) ============================================================= 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/ --> <!-- ============================================================= --> <!-- ATTRIBUTE VALUE LISTS --> <!-- ============================================================= --> <!-- FOOTNOTE TYPE VALUES --> <!-- Used to mark the semantics of the footnote, what information does this footnote convey. --> <!ENTITY % fn-types "abbr | coi-statement | com | con | conflict | corresp | current-aff | deceased | edited-by | equal | financial-disclosure | on-leave | participating-researchers | presented-at | presented-by | present-address | previously-at | study-group-members | supplementary-material | supported-by | other" > <!-- PERSON GROUP TYPE VALUES --> <!-- Used to name the type of contributors, such as "editor". --> <!ENTITY % person-group-types "allauthors | assignee | author | compiler | curator | director | editor | guest-editor | illustrator | inventor | research-assistant | translator | transed" > <!-- ============================================================= --> <!-- INLINE MIXES TO OVER-RIDE CONTENT MODELS --> <!-- (ELEMENTS TO BE ADDED TO #PCDATA IN MODELS)--> <!-- ============================================================= --> <!-- ADDRESS LINE ELEMENTS --> <!-- Elements for use in the <addr-line> element--> <!ENTITY % addr-line-elements "%rendition-plus; | %address-line.class;" > <!-- AFFILIATION ELEMENTS --> <!-- Elements for use in the <aff> element Removed <label> --> <!ENTITY % aff-elements "| %address.class; | %address-link.class; | %break.class; | %emphasis.class; | %simple-link.class; | %subsup.class;" > <!-- ARRAY CONTENT MODEL --> <!-- The element used to contain material in rows and columns that is just a block insert into the text flow, not numbered or called a table, and not titled or captioned --> <!ENTITY % array-model "((%access.class; | %address-link.class;)*, ( (%just-base-display.class;)* | %tbody.class; ), (%display-back-matter.class;)* )" > <!-- AWARD-ID ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of the <award-id> --> <!ENTITY % award-id-elements "" > <!-- CHEMICAL STRUCTURE ELEMENTS --> <!-- Those elements that may mix with the data characters inside a Chemical Structure <chem-struct> --> <!ENTITY % chem-struct-elements "| %access.class; | %address-link.class; | %break.class; | %emphasis.class; | %id.class; | %list.class; | %simple-display.class; | %simple-link.class; | %subsup.class; " > <!-- CITATION ELEMENTS --> <!-- Content for both types of citation. These elements may be mixed with #PCDATA in the <mixed-citation> element (in which all punctuation and spacing are left intact), and they also constitute the choices that can be used to form the all-element-content of the <element-citation> element (in which punctuation and spacing are removed). Design Note: All inline mixes begin with an OR bar. --> <!ENTITY % citation-elements "%emphasis.class; | %inline-display.class; | %inline-math.class; | %phrase.class; | %references.class; | %subsup.class;" > <!-- COLLABORATIVE (GROUP) AUTHOR ELEMENTS --> <!-- Elements for use in the <collab> element Design Note: All inline mixes begin with an OR bar, but since %rendition-plus; is an inline mix, the OR bar is already there. --> <!ENTITY % collab-elements "%rendition-plus; | %address.class; | %contrib-info.class;" > <!-- COMMENT ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of the Comment in a Citation <comment> element. Design Note: All inline mixes begin with an OR bar, but since %simple-phrase; is an inline mix, the OR bar is already there. --> <!ENTITY % comment-elements "| %address-link.class; | %article-link.class; | %emphasis.class; | %inline-display.class; | %inline-math.class; | %phrase.class; | %subsup.class;" > <!-- CONFERENCE ACRONYM ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of the conference acronym. Design Note: All inline mixes begin with an OR bar, but since %simple-text; is an online mix, the OR bar is already there. --> <!ENTITY % conf-acronym-elements "" > <!-- CONFERENCE LOCATION ELEMENTS --> <!-- Elements for use in the <conf-loc> element Removed %simple-text; --> <!ENTITY % conf-loc-elements "| %address.class;" > <!-- CONFERENCE NAME ELEMENTS --> <!-- Elements for use in the <conf-name> element. Removed %simple-text; --> <!ENTITY % conf-name-elements "" > <!-- CONFERENCE NUMBER ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of the conference number. Design Note: All inline mixes begin with an OR bar, but since %simple-text; is an inline mix, the OR bar is already there. --> <!ENTITY % conf-num-elements "" > <!-- CONFERENCE SPONSOR ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of the conference sponsor. --> <!ENTITY % conf-sponsor-elements "| %institution-wrap.class;" > <!-- CORRESPONDENCE INFORMATION ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of the correspondence information. --> <!ENTITY % corresp-elements "| %address.class; | %address-link.class; | %emphasis.class; | %subsup.class;" > <!-- DEGREE(S) ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of <degrees> --> <!ENTITY % degrees-elements "" > <!-- FORMULA, DISPLAY ELEMENTS --> <!-- Elements for use mixed with #PCDATA within the <disp-formula> element --> <!ENTITY % disp-formula-elements "| %access.class; | %address-link.class; | %break.class; | %emphasis.class; | %display-back-matter.class; | %inline-display.class; | %inline-math.class; | %label.class; | %math.class; | %simple-display.class; | %subsup.class;" > <!-- EDITION ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of <edition> --> <!ENTITY % edition-elements "| %subsup.class;" > <!-- FAX NUMBER ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of a <fax> --> <!ENTITY % fax-elements "" > <!-- FUNDING-SOURCE ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of the <funding-source> --> <!ENTITY % funding-source-elements "| %institution-wrap.class;" > <!-- GIVEN (FIRST) NAMES ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of a <given-names> --> <!ENTITY % given-names-elements "" > <!-- INSTITUTION NAME ELEMENTS --> <!-- Elements for use in the <institution> element --> <!ENTITY % institution-elements "| %subsup.class;" > <!-- ISSUE TITLE ELEMENTS --> <!-- Elements for use with data characters inside the model for the <issue> element --> <!ENTITY % issue-elements "" > <!-- KEYWORD CONTENT ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of a keyword <kwd>. --> <!ENTITY % kwd-elements "| %emphasis.class; | %phrase.class; | %subsup.class;" > <!-- LABEL ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of the <label> element --> <!ENTITY % label-elements "" > <!-- PATENT NUMBER ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of <patent> --> <!ENTITY % patent-elements "" > <!-- PERSON GROUP MODEL --> <!-- Content model for the <person-group> element --> <!ENTITY % person-group-elements "| %name.class; | %person-group-info.class;" > <!-- PHONE NUMBER ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of a <phone number> --> <!ENTITY % phone-elements "" > <!-- PREFIX ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of a <prefix> --> <!ENTITY % prefix-elements "" > <!-- PREFORMATTED TEXT ELEMENTS --> <!-- Elements that may be used, along with data characters, inside the content model for the <preformat> element, in which whitespace, such as tabs, line feeds, and spaces will be preserved --> <!ENTITY % preformat-elements "| %access.class; | %address-link.class; | %display-back-matter.class; | %emphasis.class; | %phrase.class; | %subsup.class;" > <!-- PRODUCT ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of the <product> element --> <!ENTITY % product-elements "| %article-link.class; | %emphasis.class; | %inline-display.class; | %inline-math.class; | %phrase.class; | %price.class; | %references.class; | %simple-link.class; | %subsup.class;" > <!-- PUBLISHER'S LOCATION ELEMENTS --> <!-- Elements for use in the Publisher Location <publisher-loc> element --> <!ENTITY % publisher-loc-elements "| %address.class;" > <!-- PUBLISHER'S NAME ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of a <publisher-name> --> <!ENTITY % publisher-name-elements "| %institution-wrap.class;" > <!-- ROLE ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of a <role> Design Note: All inline mixes begin with an OR bar; since %rendition-plus; is an inline mix, the OR bar is already there. --> <!ENTITY % role-elements "" > <!-- SUFFIX ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of a <suffix> --> <!ENTITY % suffix-elements "" > <!-- STANDARDS ORGANIZATION ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of <std-organization>. Removed emphasis.class. --> <!ENTITY % std-organization-elements "| %institution-wrap.class; | %subsup.class;"> <!-- SURNAME ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of a <surname> --> <!ENTITY % surname-elements "" > <!-- DEFINITION LIST: TERM ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of a <term>. Design Note: All inline mixes begin with an OR bar, but since %simple-phrase; is an inline mix, the OR bar is already there. --> <!ENTITY % term-elements "| %address-link.class; | %article-link.class; | %emphasis.class; | %inline-display.class; | %inline-math.class; | %phrase.class; | %simple-link.class; | %subsup.class;" > <!-- URI ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of a <uri> --> <!ENTITY % uri-elements "" > <!-- VERSION ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of <version> --> <!ENTITY % version-elements "| %subsup.class;" > <!-- VOLUME NUMBER ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of a <volume> --> <!ENTITY % volume-elements "" > <!-- ============================================================= --> <!-- OVER-RIDES USED IN SHARED CONTENT MODELS --> <!-- ============================================================= --> <!-- DISPLAY ELEMENT BACK MATTER SEQUENCE --> <!-- Miscellaneous stuff at the end of a display element such as a figure or a boxed text element such as a sidebar --> <!ENTITY % display-back-matter "attrib?, permissions?" > <!-- ============================================================= --> <!-- OVER-RIDES OF SHARED CONTENT MODELS (FULL) --> <!-- ============================================================= --> <!-- CONTENT MODEL FOR A STRUCTURAL SECTION --> <!-- The model for a section that requires that a section title be present, used for elements such as Section and Appendix. --> <!ENTITY % sec-model "(title, (%para-level;)*, (%sec-level;)* )" > <!-- CONTENT MODEL FOR AN UNTITLED SECTION --> <!-- The model for a section-like structure that may or may not have an initial title --> <!ENTITY % sec-opt-title-model "(title?, (%para-level;)*, (%sec-level;)* )" > <!-- ============================================================= --> <!-- OVER-RIDES OF CONTENT MODELS (FULL MODELS) --> <!-- ============================================================= --> <!-- ABSTRACT MODEL --> <!-- Abstracts may contain one or more paragraphs (as a typical abstract does) or titled sections, as is done in many physics articles. --> <!ENTITY % abstract-model "(title?, (%just-para.class;)*, %sec.class;*)" > <!-- ACKNOWLEDGMENTS MODEL --> <!-- Content model for the <ack> element Deleted optional sections and closing reference list --> <!ENTITY % ack-model "(title?, (%just-para.class;)*)" > <!-- ANONYMOUS MODEL --> <!-- Content model for the element <anonymous>. When present, it is used to generate the text "anonymous" or "anon.", etc. --> <!ENTITY % anonymous-model "EMPTY" > <!-- ADDRESS MODEL --> <!-- Content model for the <address> element --> <!ENTITY % address-model "((%institution-wrap.class;)*, addr-line*, city?, state?, postal-code?, country, phone*, fax*, email*, ext-link*, uri*)" > <!-- APPENDIX GROUP MODEL --> <!-- Content model for the <app-group> element --> <!ENTITY % app-group-model "(title?, (%just-para.class;)*, (%app.class;)* )" > <!-- ARTICLE METADATA MODEL --> <!-- Full content model for the metadata that is specific to the article. --> <!ENTITY % article-meta-model "(article-version?, title-group, contrib-group, (product | supplementary-material)*, permissions?, self-uri*, (%related-article.class;)*, (%abstract.class;)+, (%kwd-group.class;)*, funding-group*, support-group*, conference*)" > <!-- BOXED TEXT MODEL --> <!-- Complete content model for the boxed text element which is used for sidebars, marginalia, and other text that is outside the narrative flow. --> <!ENTITY % boxed-text-model "((%id.class;)*, caption?, (%para-level;)*, (%sec-level;)*, %display-back-matter; )" > <!-- CHEMICAL STRUCTURE WRAPPER MODEL --> <!-- Content model for the Chemical Structure Wrapper <chem-struct-wrap> element --> <!ENTITY % chem-struct-wrap-model "((%id.class;)*, (%caption.class;)?, (%access.class;)*, (%inside-chem-struct-wrap.class;)+, %display-back-matter;)" > <!-- CONFERENCE MODEL --> <!-- The element components that describe of a conference --> <!ENTITY % conference-model "(conf-date, (conf-name | conf-acronym )+, conf-num?, conf-loc?, conf-sponsor*, conf-theme?)" > <!-- CONTRIBUTOR MODEL --> <!-- Content model for the <contrib> element --> <!ENTITY % contrib-model "((%contrib-id.class;)*, (%name.class;)*, (%degree.class;)*, role*, on-behalf-of?, (%aff-alternatives.class;)*, address*, email*, ext-link*, uri*, bio?, author-comment?)" > <!-- CONTRIBUTOR GROUP MODEL --> <!-- Content model for the <contrib-group> element --> <!ENTITY % contrib-group-model "(%contrib.class;+)" > <!-- DATE ELEMENTS MODEL --> <!-- The content models for elements that describe dates, such as Publication Date <pub-date> and History Dates <date>. The <string-date> element holds dates for which months and years are not given, for example "first quarter", "spring", etc. --> <!ENTITY % date-model "(((day?, month?) | season)?, year, era?)" > <!-- DEFINITION LIST MODEL --> <!-- Content model for the <def-list> element --> <!ENTITY % def-list-model "(title?, term-head?, def-head?, (%def-item.class;)+)" > <!-- DEFINITION LIST: DEFINITION ITEM ELEMENTS --> <!-- The elements that can be included inside the content model of a <def-item> --> <!ENTITY % def-item-model "(term, def*)" > <!-- FORMULA, DISPLAY GROUP MODEL --> <!-- Content model for an <disp-formula-group> --> <!ENTITY % disp-formula-group-model "(label?, (%caption.class;)?, (%access.class; | %address-link.class;)*, (%block-math.class;)* )" > <!-- QUOTE, DISPLAYED MODEL --> <!-- Content model for the Display Quote element--> <!ENTITY % disp-quote-model "(title?, (%just-para.class;)+, %display-back-matter; )" > <!-- FIGURE-LIKE CONTENT MODEL --> <!-- Content model for the Figure element and any similarly structured elements --> <!ENTITY % fig-model "((%id.class;)*, (%caption.class;)?, (%access.class;)*, (%block-math.class; | %chem-struct-wrap.class; | %intable-para.class; | %just-table.class; | %just-para.class; | %list.class; | %simple-display.class;)*, %display-back-matter; )" > <!-- FOOTNOTE GROUP MODEL --> <!-- Content model for the <fn-group> element --> <!ENTITY % fn-group-model "(title?, (%fn-link.class;)+ )" > <!-- FOOTNOTE MODEL --> <!-- Content model for Footnote <fn> --> <!ENTITY % fn-model "((%just-para.class;)+ )" > <!-- GLOSSARY MODEL --> <!-- Content model for the <glossary> element --> <!ENTITY % glossary-model "(title?, (%just-para.class;)*, def-list*, glossary* )" > <!-- GRAPHIC MODEL --> <!-- Content model for the <graphic> element --> <!ENTITY % graphic-model "((%id.class;)?, (%access.class;)*, (%display-back-matter;)*) " > <!-- KEYWORD GROUP MODEL --> <!-- Content model for a <kwd-group> element --> <!ENTITY % kwd-group-model "(title?, (%kwd.class;)+ )" > <!-- LIST ITEM ELEMENTS --> <!-- The elements that can be included inside the content model of a <list-item> --> <!ENTITY % list-item-model "(label?, title?, (%just-para.class; | %list.class;)+ )" > <!-- LIST MODEL --> <!-- Content model for the <list> element --> <!ENTITY % list-model "(title?, (%list-item.class;)+)" > <!-- MEDIA MODEL --> <!-- Content model for the <media> element --> <!ENTITY % media-model "((%id.class;)?, (%access.class;)*, (%display-back-matter;)*) " > <!-- ON BEHALF OF CONTENT ELEMENTS --> <!-- The elements that can be included along with data characters inside the content model of <on-behalf-of> Design Note: -%rendition-plus; begins with an OR bar, so this inline mix beguines with an OR bar. --> <!ENTITY % on-behalf-of-elements "%rendition-plus; | %institution-wrap.class; | %simple-link.class;" > <!-- REFERENCE LIST MODEL --> <!-- Content model for the <ref-list> element --> <!ENTITY % ref-list-model "(title?, (%just-para.class;)*, ref+)" > <!-- REFERENCE ITEM MODEL Model for the <ref> element --> <!ENTITY % ref-model "(%citation.class;)+" > <!-- STATEMENT, FORMAL MODEL --> <!-- Content model for the <statement> element --> <!ENTITY % statement-model "(label?, title?, (%just-para.class; | %statement.class;)+, (%display-back-matter.class;)*)" > <!-- SUPPLEMENTARY MATERIAL MODEL --> <!-- Content model for the <supplementary-material> element --> <!ENTITY % supplementary-material-model "((%id.class;)*, (%caption.class;)?, (%access.class; | %address-link.class;)*, (%just-para.class;)*, %display-back-matter; )" > <!-- TABLE WRAPPER CONTENT MODEL --> <!-- Content model for the container element that surrounds the standard table models for row and columns. --> <!ENTITY % table-wrap-model "((%id.class;)*, (%caption.class;)?, (%access.class;)*, (%inside-table-wrap;)*, %table-foot.class;?, %display-back-matter; )" > <!-- TITLE GROUP MODEL --> <!-- Content model for the <title-group> element--> <!ENTITY % title-group-model "(article-title, subtitle?)" > <!-- TRANSLATED ABSTRACT MODEL --> <!-- Content model for an <trans-abstract> element. --> <!ENTITY % trans-abstract-model "(title?, (%just-para.class;)*, %sec.class;*)" > <!-- VERSE GROUP MODEL --> <!-- Content model for the <verse-group> element--> <!ENTITY % verse-group-model "(title?, subtitle?, verse-line+, %display-back-matter; ) " > <!-- ============================================================= --> <!-- OVER-RIDES OF ATTRIBUTE VALUES --> <!-- ============================================================= --> <!-- LIST PREFIX TYPES --> <!-- Used to request a specific style of prefix characters for the items in lists and de-lists. Ordered is number or letters, bulleted is bullets or other non-ordered character, simple has no prefix at all. --> <!ENTITY % list-types "bullet | order | simple" > <!-- ============================================================= --> <!-- DUPLICATE ATTRIBUTE DECLARATIONS --> <!-- (These are unchanged from the base Suite, --> <!-- but are used in attribute over-rides below)--> <!-- ============================================================= --> <!-- COMMON ATTRIBUTES --> <!-- These lists of attributes will be added to nearly every element, in both the document metadata and the document body, of the entire Tag Set: - including table elements for both the XHTML-inspired and OASIS-inspired table model elements - excluding only <mml:math> and <xi:include> (whose namespaces JATS does not control). Great care should be taken to use these attributes judiciously, not as a shortcut to thinking through where an attribute should be used. Potential use cases include adding @xml:lang or some RDFa attribute to every elements. --> <!-- BASE ATTRIBUTES --> <!-- Holds all the common attributes except @id. Used to keep the two common attribute lists in sync. To add a global attribute, modify this list. --> <!ENTITY % jats-base-atts "xml:base CDATA #IMPLIED" > <!-- COMMON ATTRIBUTES --> <!-- Holds all the common attributes, as defined in the base attribute parameter entity, plus an optional @id. --> <!ENTITY % jats-common-atts "id ID #IMPLIED %jats-base-atts;" > <!-- COMMON ATTRIBUTES --> <!-- Holds all the common attributes, as defined in the base attribute parameter entity, plus a required @id. --> <!ENTITY % jats-common-atts-id-required "id ID #REQUIRED %jats-base-atts;" > <!-- XLINK LINK ATTRIBUTES --> <!-- Attributes for any element that must be a link --> <!ENTITY % link-atts "xmlns:xlink CDATA #IMPLIED xlink:type (simple) #IMPLIED xlink:href CDATA #REQUIRED xlink:role CDATA #IMPLIED xlink:title CDATA #IMPLIED xlink:show (embed | new | none | other | replace) #IMPLIED xlink:actuate (none | onLoad | onRequest | other) #IMPLIED" > <!-- MIGHT LINK XLINK ATTRIBUTES --> <!-- Attributes for any element that may be a link but need not be one --> <!ENTITY % might-link-atts "xmlns:xlink CDATA #IMPLIED xlink:type (simple) #IMPLIED xlink:href CDATA #IMPLIED xlink:role CDATA #IMPLIED xlink:title CDATA #IMPLIED xlink:show (embed | new | none | other | replace) #IMPLIED xlink:actuate (none | onLoad | onRequest | other) #IMPLIED" > <!-- ============================================================= --> <!-- OVER-RIDES OF ATTRIBUTE LISTS --> <!-- ============================================================= --> <!-- COLLABORATION ATTRIBUTES --> <!-- Attributes for <collab> --> <!ENTITY % collab-atts "%jats-common-atts; collab-type CDATA #IMPLIED specific-use CDATA #IMPLIED xml:lang NMTOKEN #IMPLIED %might-link-atts;" > <!-- FOOTNOTE ATTRIBUTES --> <!-- Attribute list for Footnote element --> <!ENTITY % fn-atts "%jats-common-atts; fn-type (%fn-types;) #IMPLIED specific-use CDATA #IMPLIED xml:lang NMTOKEN #IMPLIED" > <!-- INLINE GRAPHIC ATTRIBUTES --> <!-- Attributes for Inline Graphic <inline-graphic> --> <!ENTITY % inline-graphic-atts "%jats-common-atts; baseline-shift CDATA #IMPLIED mimetype CDATA #FIXED 'image' mime-subtype (cgm | gif | jpeg | png | tiff) #IMPLIED specific-use CDATA #IMPLIED xml:lang NMTOKEN #IMPLIED %link-atts;" > <!-- DEFAULT LIST CLASS ATTRIBUTES --> <!-- Default attribute lists to be used for most of the types of lists. Used for the <list> element and <def-list> element. --> <!ENTITY % list-atts "%jats-common-atts; continued-from IDREF #IMPLIED list-type (%list-types;) #IMPLIED prefix-word CDATA #IMPLIED list-content CDATA #IMPLIED specific-use CDATA #IMPLIED xml:lang NMTOKEN #IMPLIED" > <!-- PERSON GROUP ATTRIBUTES --> <!-- Attributes for the <person-group> element --> <!ENTITY % person-group-atts "%jats-common-atts; person-group-type (%person-group-types;) #IMPLIED specific-use CDATA #IMPLIED xml:lang NMTOKEN #IMPLIED" > <!-- SECTION ATTRIBUTES --> <!-- Attributes for the <sec> element --> <!ENTITY % sec-atts "%jats-common-atts; sec-type CDATA #IMPLIED specific-use CDATA #IMPLIED xml:lang NMTOKEN #IMPLIED" > <!-- UNDERLINE ATTRIBUTES --> <!-- Attributes for the <underline> element --> <!ENTITY % underline-atts "%jats-common-atts; toggle (yes | no) #IMPLIED specific-use CDATA #IMPLIED" > <!-- ================== End Authoring Over-ride Content/ATTLIST == -->