xml_jats_resolver 0.0.1

data/lib/dtd/jats/0.4/dtd/rng/JATS-chars0.ent.rng

@@ -0,0 +1,498 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- ============================================================= -->
+<!-- MODULE:    Custom Special Characters Module -->
+<!-- VERSION:   NISO 0.4 -->
+<!-- DATE:      January 2011 -->
+<!---->
+<!-- ============================================================= -->
+<!-- ============================================================= -->
+<!-- PUBLIC DOCUMENT TYPE DEFINITION -->
+<!-- TYPICAL INVOCATION -->
+<!--
+  "-//NLM//DTD JATS (Z39.96) Archiving and Interchange DTD Suite Custom Special Characters Module v0.4 20110131//EN"
+       Delivered as file "JATS-chars0.ent"
+-->
+<!-- ============================================================= -->
+<!-- ============================================================= -->
+<!-- SYSTEM:     Archiving and Interchange DTD Suite -->
+<!---->
+<!-- PURPOSE:    XML special character entities -->
+<!---->
+<!-- CONTAINS:   1) Definitions of DTD-specific and custom -->
+<!-- special characters (as general entities -->
+<!-- defined as hexadecimal or decimal character -->
+<!-- entities - Unicode numbers) -->
+<!---->
+<!-- REQUESTS FOR DTD CHANGES: -->
+<!-- Send email to: pmc@ncbi.nlm.nih.gov -->
+<!---->
+<!-- CREATED FOR: -->
+<!-- Digital archives and publishers who wish to -->
+<!-- create a custom XML DTD for original markup of -->
+<!-- journal literature, books, and related material, -->
+<!-- or for archiving and transferring such material -->
+<!-- between archives. -->
+<!---->
+<!-- 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 Archiving and -->
+<!-- Interchange 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 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 NISO Z39.96 Journal Article Tag -->
+<!-- Suite." -->
+<!---->
+<!-- ORIGINAL CREATION DATE: -->
+<!-- December 2002 -->
+<!---->
+<!-- CREATED BY: Jeff Beck       (NCBI) -->
+<!-- Deborah Lapeyre (Mulberry Technologies, Inc.) -->
+<!-- Bruce Rosenblum (Inera Inc.) -->
+<!-- B. Tommie Usdin (Mulberry Technologies, Inc.) -->
+<!---->
+<!-- NLM thanks the Harvard University Libraries, both -->
+<!-- for proposing that a draft archiving NLM DTD for -->
+<!-- life sciences journals be extended to accommodate -->
+<!-- journals in all disciplines and for sponsoring -->
+<!-- Bruce Rosenblum's collaboration with other DTD -->
+<!-- authors in completing NLM Version 1.0. The -->
+<!-- Andrew W. Mellon Foundation provided support for -->
+<!-- these important contributions. -->
+<!---->
+<!-- Suggestions for refinements and enhancements to -->
+<!-- the DTD suite should be sent in email to: -->
+<!-- jats@ncbi.nlm.nih.gov -->
+<!---->
+<!-- ============================================================= -->
+<!-- ============================================================= -->
+<!-- DTD VERSION/CHANGE HISTORY -->
+<!-- ============================================================= -->
+<!--
+  
+  Version  Reason/Occasion                   (who) vx.x (yyyy-mm-dd)
+  
+       =============================================================
+       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, NLM "Version 3.1 Draft" has 
+       been changed to NISO "Version 0.4". No model, attribute, or
+       parameter entity changes were made as part of this renaming.
+  
+       Details on NISO Tial Use Draft Version 0.4 are available at
+             http://jats.nlm.nih.gov/JATS-0.4.
+  
+    6. Updated the public identifier to "v0.4 20110131//EN", 
+       modified the formal public identifier to include "JATS (Z39.96)",
+       and the filename as delivered to include "JATS" and the
+       new version number "0".
+  
+       =============================================================
+       Version 3.1                       (DAL/BTU) v3.1 (2010-04-30)
+  
+       Version 3.1 is fully compatible with Version 3.0.
+  
+       Details on version 3.1 are available at
+             http://jats.nlm.nih.gov/3.1.
+  
+    5. @SPECIFIC-USE and @XML:LANG - Added the @specific-use and
+       @xml:lang to the following elements:
+         - private-char through private-char-atts (@specific-use)
+  
+    4. PES FOR CONTENT MODELS - Added parameter entity redefinitions
+       for the model of the <private-char> element.
+  
+    3. PES FOR ATTLISTS - Added parameter entity redefinitions for the
+       attribute lists of the following elements: (no attributes or
+       values were changed)
+         - glyph-ref         glyph-ref-atts
+         - glyph-data        glyph-data-atts
+         - private-char      private-char-atts
+  
+    2. Updated public identifier to "v3.1 20100830//EN"
+  
+       =============================================================
+       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://jats.nlm.nih.gov/3.0.
+  
+    1. Updated public identifier to "v3.0 20080202//EN"
+-->
+<!-- ============================================================= -->
+<!-- DESIGN COMMENT -->
+<!-- ============================================================= -->
+<!--
+  This DTD Suite has been designed with Unicode
+  as the basic representation of all special
+  characters. The use of combining characters
+  is supported and encouraged as is the use
+  of entities defined by the STIX project
+  (http://www.ams.org/STIX/). Unicode values
+  in planes other than Plane 0 may be freely
+  used.
+  
+  Use of private publisher entities and Unicode
+  Private Use Area is discouraged, but supported
+  with the <private-char> element, for which a
+  corresponding bitmap must be submitted.
+  
+  In cases where an entity name has been generally
+  accepted with a corresponding Unicode number
+  and the entity has not been added to
+  the ISO standard entity sets, a named entity
+  may be defined below (e.g. &euro;).
+  
+  Because of the potential for conflicts in
+  assignments by different publishers,
+  the Archival and Interchange DTD Suite does
+  not support assignment of values in the
+  Unicode Private Use Area.
+  Publishers who have defined characters in the
+  Private Use Area must remap those characters
+  to existing Unicode values (using combining
+  characters for special accented characters
+  where appropriate), or must submit bitmaps of
+  those characters using one of the two methods
+  supported under the <private-char> element.
+  
+  Those custom publisher entities for which
+  corresponding Unicode values have not been
+  determined must be tagged with the
+  <private-char> element. Publishers must submit
+  bitmaps of those characters using one of the
+  two methods supported in the <private-char>
+  element.
+-->
+<!-- ============================================================= -->
+<!--
+  COMMONLY ACCEPTED ENTITIES FOR UNICODE
+  GLYPHS
+-->
+<!-- ============================================================= -->
+<!--
+  For each of the following entities a name
+  and a Unicode numerical character reference
+  is given. Where a unique Unicode character
+  could be determined, that character was used.
+  For some of the symbols combining characters
+  have been used. Do not use this space to
+  redefine characters already found in standard
+  ISO entity sets. Do not use this space to
+  define any character that cannot be
+  represented with Unicode.
+-->
+<!-- LATIN SMALL LETTER G WITH CARON -->
+<!-- LATIN CAPITAL LETTER H WITH MACRON -->
+<!-- EURO CURRENCY -->
+<!-- FRANC CURRENCY -->
+<!-- ============================================================= -->
+<!-- ATTRIBUTE LISTS FOR PRIVATE CHARACTERS -->
+<!-- ============================================================= -->
+<!-- GLYPH DATA ATTRIBUTES -->
+<!--
+  Attribute list for the <glyph-data>
+  element
+-->
+<grammar xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" xmlns="http://relaxng.org/ns/structure/1.0" datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">
+  <define name="glyph-data-atts">
+    <optional>
+      <attribute name="id">
+        <data type="ID"/>
+      </attribute>
+    </optional>
+    <optional>
+      <attribute name="fontchar"/>
+    </optional>
+    <optional>
+      <attribute name="fontname"/>
+    </optional>
+    <optional>
+      <attribute name="format">
+        <data type="NMTOKEN"/>
+      </attribute>
+    </optional>
+    <optional>
+      <attribute name="resolution"/>
+    </optional>
+    <optional>
+      <attribute name="xml:space" a:defaultValue="preserve">
+        <value>preserve</value>
+      </attribute>
+    </optional>
+    <optional>
+      <attribute name="x-size"/>
+    </optional>
+    <optional>
+      <attribute name="y-size"/>
+    </optional>
+  </define>
+  <!-- GLYPH REFERENCE ATTRIBUTES -->
+  <!--
+    Attribute list for the <glyph-ref>
+    element
+  -->
+  <define name="glyph-ref-atts">
+    <optional>
+      <attribute name="glyph-data">
+        <data type="IDREF"/>
+      </attribute>
+    </optional>
+  </define>
+  <!--
+    PRIVATE USE AREA AND CUSTOM CHARACTERS
+    ATTRIBUTES
+  -->
+  <!--
+    Attribute list for the <private-char>
+    element
+  -->
+  <define name="private-char-atts">
+    <optional>
+      <attribute name="description"/>
+    </optional>
+    <optional>
+      <attribute name="name"/>
+    </optional>
+    <optional>
+      <attribute name="specific-use"/>
+    </optional>
+  </define>
+  <!-- ============================================================= -->
+  <!-- PRIVATE USE AREA AND CUSTOM CHARACTERS -->
+  <!-- ============================================================= -->
+  <!--
+    Special characters defined by publishers as
+    custom entities or in the Unicode Private Use
+    Area may not be deposited as is. If they
+    cannot be remapped to existing Unicode values,
+    they must be submitted as a bitmap using
+    the <private-char> element. The most
+    repository-friendly technique is <glyph-data>
+    although individual bitmap files may be
+    submitted with inline-graphic.
+    
+    We would like to thank Beacon Publishing and
+    the APS (American Physical Society) for
+    providing us with this technique.
+  -->
+  <!-- PRIVATE CHARACTER MODEL -->
+  <!--
+    The content model for the <private-char>
+    element
+  -->
+  <define name="private-char-model">
+    <choice>
+      <choice>
+        <ref name="glyph-data"/>
+        <ref name="glyph-ref"/>
+      </choice>
+      <zeroOrMore>
+        <ref name="inline-graphic"/>
+      </zeroOrMore>
+    </choice>
+  </define>
+  <!-- PRIVATE CHARACTER (CUSTOM OR UNICODE) -->
+  <!--
+    A custom character entity defined by a
+    publisher or a custom character from the
+    Unicode private-use area for which a bitmap
+    is submitted for the glyph.
+    
+    Since there are no completely standard/public
+    agreements on how such characters are to be
+    named and displayed, this technique is to be
+    used instead of a custom general entity
+    reference, to provide complete information
+    on the intended character.
+    A document should contain a <private-char>
+    element at each location where a private
+    character is used within the document. The
+    corresponding image for the glyph may be
+    given in the <glyph-data> element or as an
+    external bitmap file referenced by an
+    <inline-graphic> element.
+    
+    Implementation Note: <inline-graphic> should
+    only be used outside <private-char> when the
+    graphic is something other than a special
+    character.
+    Details at:
+    http://jats.nlm.nih.gov/archiving/tag-library/0.4/index.html?elem=private-char
+    http://jats.nlm.nih.gov/publishing/tag-library/0.4/index.html?elem=private-char
+    http://jats.nlm.nih.gov/articleauthoring/tag-library/0.4/index.html?elem=private-char
+    http://jats.nlm.nih.gov/book/tag-library/3.1/index.html?elem=private-char
+  -->
+  <define name="private-char">
+    <element name="private-char">
+      <ref name="private-char-attlist"/>
+      <ref name="private-char-model"/>
+    </element>
+  </define>
+  <!--
+    description
+               A human-readable description of the
+               character, for example, "Arrow, normal
+               weight, single line, two-headed, Northwest
+               to Southeast".
+    name       Unique name for the character in all
+               uppercase ASCII, similar to names found
+               in Unicode standard (e.g., "NORTHWEST
+               SOUTHEAST ARROW"
+  -->
+  <define name="private-char-attlist" combine="interleave">
+    <ref name="private-char-atts"/>
+  </define>
+  <!-- GLYPH DATA FOR A PRIVATE CHARACTER -->
+  <!--
+    This element is used when there is known to
+    be no font available to render the private
+    character. The <glyph-data> element can be
+    used to provide information on the actual
+    glyph that is associated with the private-use
+    character. The element includes an inline
+    bitmap of the glyph encoded in plain
+    PBM (Plain Bit Map) format so that it is
+    human-readable.
+    
+    For example:
+    <private-char name="NORTHWEST SOUTHEAST ARROW"
+    description="Arrow, normal weight, single
+    line, two-headed, Northwest to Southeast">
+    <glyph-data format="PBM" resolution="300"
+    x-size="34" y-size="34">
+    0000000000000000000000000000000000
+    0111111111111100000000000000000000
+    0111111111111100000000000000000000
+    0111110000000000000000000000000000
+    0111110000000000000000000000000000
+    0111111000000000000000000000000000
+    0110111100000000000000000000000000
+    0110011110000000000000000000000000
+    0110001111000000000000000000000000
+    0110000111100000000000000000000000
+    0110000011110000000000000000000000
+    0110000001111000000000000000000000
+    0110000000111100000000000000000000
+    0110000000011110000000000000000000
+    0110000000001111000000000000000000
+    0110000000000111100000000000000000
+    0110000000000011110000000000000000
+    0000000000000001111000000000000000
+    0000000000000000111100000000000110
+    0000000000000000011110000000000110
+    0000000000000000001111000000000110
+    0000000000000000000111100000000110
+    0000000000000000000011110000000110
+    0000000000000000000001111000000110
+    0000000000000000000000111100000110
+    0000000000000000000000011110000110
+    0000000000000000000000001111000110
+    0000000000000000000000000111100110
+    0000000000000000000000000011110110
+    0000000000000000000000000001111110
+    0000000000000000000000000001111110
+    0000000000000000011111111111111110
+    0000000000000000011111111111111110
+    0000000000000000000000000000000000
+    </glyph-data></private-char>
+    Details at:
+    http://jats.nlm.nih.gov/archiving/tag-library/0.4/index.html?elem=glyph-data
+    http://jats.nlm.nih.gov/publishing/tag-library/0.4/index.html?elem=glyph-data
+    http://jats.nlm.nih.gov/articleauthoring/tag-library/0.4/index.html?elem=glyph-data
+    http://jats.nlm.nih.gov/book/tag-library/3.1/index.html?elem=glyph-data
+  -->
+  <define name="glyph-data">
+    <element name="glyph-data">
+      <ref name="glyph-data-attlist"/>
+      <text/>
+    </element>
+  </define>
+  <!--
+    id         Identifier so that the full glyph data need
+               not be repeated every time the character is
+               used. The <glyph-ref> element can be used
+               to point to this ID, to reuse a character
+               in subsequent text.
+    fontchar   The offset of the character into a glyph
+               table, such as a Unicode character.
+    fontname   The name of the character
+    format     Names the image format of the bitmap. Should
+               be "PBM" if the plain bitmap is included
+               inline.
+    resolution Resolution of the bitmap in dots per inch,
+               expressed as a decimal integer (e.g. 72, 300)
+    xml:space  Preserve whitespace within this element.
+    x-size     Number of pixels per row in the bit-mapped
+               glyph
+    y-size     Number of rows of the bit-mapped glyph
+  -->
+  <define name="glyph-data-attlist" combine="interleave">
+    <ref name="glyph-data-atts"/>
+  </define>
+  <!-- GLYPH REFERENCE FOR A PRIVATE CHARACTER -->
+  <!--
+    Once a private character has been declared
+    using a <glyph-data> element, the character
+    can be reused by using this element to
+    point to the full <glyph-data> element.
+    The pointing uses the ID/IDREF mechanism,
+    using the "glyph-data" attribute of this
+    element to point to the "id" attribute of
+    another <glyph-data> element.
+    Details at:
+    http://jats.nlm.nih.gov/archiving/tag-library/0.4/index.html?elem=glyph-ref
+    http://jats.nlm.nih.gov/publishing/tag-library/0.4/index.html?elem=glyph-ref
+    http://jats.nlm.nih.gov/articleauthoring/tag-library/0.4/index.html?elem=glyph-ref
+    http://jats.nlm.nih.gov/book/tag-library/3.1/index.html?elem=glyph-ref
+  -->
+  <define name="glyph-ref">
+    <element name="glyph-ref">
+      <ref name="glyph-ref-attlist"/>
+      <empty/>
+    </element>
+  </define>
+  <!--
+    glyph-data An IDREF-type attribute that points to the
+    "id" attribute of a <glyph-data> character.
+    The idea is to use the full glyph data once,
+    then point to an existing character instead
+    of repeating the entire glyph data again.
+  -->
+  <define name="glyph-ref-attlist" combine="interleave">
+    <ref name="glyph-ref-atts"/>
+  </define>
+</grammar>
+<!-- ================== End Custom XML Special Characters ======== -->