xml_jats_resolver 0.0.1

data/lib/dtd/archiving_dtd/1.1/dtd/para.ent

@@ -0,0 +1,368 @@
+<!-- ============================================================= -->
+<!--  MODULE:    Paragraph-Like Elements                           -->
+<!--  VERSION:   1.1                                               -->
+<!--  DATE:      November 1, 2003                                  -->
+<!--                                                               -->
+<!-- ============================================================= -->
+
+<!-- ============================================================= -->
+<!--                    PUBLIC DOCUMENT TYPE DEFINITION            -->
+<!--                        TYPICAL INVOCATION                     -->
+<!--
+"-//NLM//DTD Archiving and Interchange DTD Suite Paragraph-Like Elements v1.1 20031101//EN"
+     Delivered as file "para.ent"                                  -->
+<!-- ============================================================= -->
+
+<!-- ============================================================= -->
+<!-- SYSTEM:     Archiving and Interchange DTD Suite               -->
+<!--                                                               -->
+<!-- PURPOSE:    Names structural elements that will appear in     -->
+<!--             the same places as a paragraph                    -->
+<!--                                                               -->
+<!-- CONTAINS:   1) Default definition of the paragraph class      -->
+<!--             2) Paragraph <p>                                  -->
+<!--             3) Displayed Quote <disp-quote>                   -->
+<!--                                                               -->
+<!-- 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 Archiving and Interchange DTD Suite."  -->
+<!--                                                               -->
+<!--             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 Archiving and Interchange DTD    --> 
+<!--                    Suite."                                    -->
+<!--                                                               -->
+<!--             Suggestions for refinements and enhancements to   -->
+<!--             the DTD suite should be sent in email to:         -->
+<!--                 archive-dtd@ncbi.nlm.nih.gov                  -->
+<!--                                                               -->
+<!-- ORIGINAL CREATION DATE:                                       -->
+<!--             December 2002                                     -->
+<!--                                                               -->
+<!-- CREATED BY: Jeff Beck       (NCBI)                            -->
+<!--             Deborah Lapeyre (Mulberry Technologies, Inc.)     -->
+<!--             Bruce Rosenblum (Inera 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 Version 1.0. The Andrew W.  --> 
+<!--             Mellon Foundation provided support for these      --> 
+<!--             important contributions.                          -->
+<!--                                                               -->
+<!-- ============================================================= -->
+
+
+<!-- ============================================================= -->
+<!--                    DTD VERSION\CHANGE HISTORY                 -->
+<!-- ============================================================= -->
+<!--
+     =============================================================
+
+Version  Reason/Occasion                   (who) vx.x (yyyy-mm-dd)
+
+     =============================================================
+     Version 1.1                           (TRG) v1.1 (2003-11-01)
+      
+  3. Added attribute "content-type" to elements <p>, <speech> and 
+     <statement>.  
+     Rationale: To identify and preserve the semantic intent of 
+     semantically rich source documents.
+     
+  2. Added ID attribute to elements <p>, <speech>, <disp-quote>,
+     and <verse-group>. 
+     Rationale: Provide unique identifier so these elements can be 
+     linked to. 
+                                                                   
+     =============================================================
+     Version 1.0 Changes Before Public Release
+                                       (Lapeyre) V1.0 (2002-12-25)
+
+  1. DIALOG/SPEECH - Element <dialog> renamed <speech>  
+                                                                   -->
+
+
+<!-- ============================================================= -->
+<!--                    PARAMETER ENTITY DEPENDENCIES             
+                        Requires the following parameter entities
+                        be defined before calling this module, 
+                        usually accomplished in the Customization
+                        Module for the specific DTD:
+                          %emphasized.text;
+                          %inside-para;
+                          %para-level;
+                          %person-name.class;
+                          %simple-link.class;
+                          %simple-text;                              
+                                                                   -->
+<!-- ============================================================= -->
+
+
+<!-- ============================================================= -->
+<!--                    DEFAULT DEFINITION OF PARAGRAPH CLASSES    -->
+<!-- ============================================================= -->
+
+
+<!--                    REST OF PARAGRAPH CLASS (MINUS PARAGRAPH)  -->
+<!--                    Full paragraph class, minus the paragraph
+                        element itself, so this PE can be used inside
+                        the content model of a paragraph           -->
+<!ENTITY % rest-of-para.class   
+                        "ack | speech | disp-quote | statement | 
+                         verse-group"                                >
+
+
+<!--                    PARAGRAPH CLASS                            -->
+<!--                    Information for the reader that is at the
+                        same structural level as a Paragraph
+                        Note: While most DTDs limit <ack> to inside
+                        Back Matter, the Wiley journal article DTD 
+                        allows <ack> at either a paragraph or a 
+                        section level, so it was added here.       -->
+<!ENTITY % para.class   "p | %rest-of-para.class;"                   >
+
+
+<!--                    IN TABLE PARAGRAPH CLASS                   -->
+<!--                    The simpler of the paragraph-level elements
+                        that might be found inside a table cell    -->
+<!ENTITY % intable-para.class                                   
+                        "speech | disp-quote | statement | 
+                         verse-group"                                >
+
+
+<!-- ============================================================= -->
+<!--                    PARAGRAPH-LEVEL ELEMENTS                   -->
+<!-- ============================================================= -->
+
+
+<!--                    PARAGRAPH                                  -->
+<!ELEMENT  p            (#PCDATA | %inside-para;)*                   >
+<!--         id         Unique identifier so the element may be
+                        referenced                                 
+             content-type   
+                        Identification of the subject, type of
+                        content, or reason that this word or phrase
+                        is considered semantically special, as a 
+                        means of preserving the semantic intent of 
+                        the original tagging.                      
+             xml:lang   The language in which the value of the
+                        element is expressed.  Recommended best 
+                        practice is to use values as defined in
+                        RFC 1766, typically 2-letter language
+                        codes such as "FR" (French), "EN" (English),
+                        and "DE" (German). These values are NOT
+                        case sensitive, so "EN" = "en". The values
+                        may include hyphenated differentiators such 
+                        as "EN-AU" (Australian English) and "EN-US"
+                        (United States English).                   -->
+<!ATTLIST  p
+             id         ID                                 #IMPLIED  
+             content-type
+                        CDATA                              #IMPLIED  
+             xml:lang   NMTOKEN                            #IMPLIED  >
+                        
+
+<!--                    SPEECH                                     -->
+<!--                    One exchange in a real or imaginary 
+                        conversation between two or more entities, 
+                        for example, between a an interviewer and the 
+                        person being interviewed, between a nurse or 
+                        doctor and a patient, between a person and a 
+                        computer, etc.
+                        Authoring and Conversion Note: Speechs are
+                        modeled as a full paragraph, even if what is
+                        spoken is only a few words.                
+                        Design Note: Speeches are not gathered into
+                        a larger structure, because there is no
+                        consistency in how this is done in existing
+                        journal DTDs, nor any real need for a
+                        full wrapper.                              -->
+<!ELEMENT  speech       (speaker, p+)                                >
+<!--         id         Unique identifier so the element may be
+                        referenced                                 
+             content-type   
+                        Identification of the subject, type of
+                        content, or reason that this word or phrase
+                        is considered semantically special, as a 
+                        means of preserving the semantic intent of 
+                        the original tagging.                      
+             xml:lang   The language in which the value of the
+                        element is expressed.  Recommended best 
+                        practice is to use values as defined in
+                        RFC 1766, typically 2-letter language
+                        codes such as "FR" (French), "EN" (English),
+                        and "DE" (German). These values are NOT
+                        case sensitive, so "EN" = "en". The values
+                        may include hyphenated differentiators such 
+                        as "EN-AU" (Australian English) and "EN-US"
+                        (United States English).                   -->
+<!ATTLIST  speech
+             id         ID                                 #IMPLIED  
+             content-type
+                        CDATA                              #IMPLIED
+             xml:lang   NMTOKEN                            #IMPLIED  >
+
+
+<!--                    SPEAKER ELEMENTS                           -->
+<!--                    The elements that can be included along with
+                        data characters inside the content model of
+                        a speaker.                                 -->
+<!ENTITY % speaker-elements
+                        "| %person-name.class; | %simple-link.class;">
+                        
+
+<!--                    SPEAKER                                    -->
+<!--                    One who utters a speech as part of a 
+                        speech, for example the computer "HAL" in
+                        the exchange 'Hal: "Hi Dave"'.             -->
+<!ELEMENT  speaker      (#PCDATA %speaker-elements;)*                >
+
+
+<!--                    QUOTE, DISPLAYED MODEL                     -->
+<!--                    Content model for the Display Quote element-->
+<!ENTITY % disp-quote-model     
+                        "title?, (%para-level;)*, attrib?"           > 
+            
+
+<!--                    QUOTE, DISPLAYED                           -->
+<!--                    Extract or extended quoted passage from 
+                        another work, usually made typographically 
+                        distinct from the surrounding text.
+                        Authoring and Conversion Note: Use this 
+                        element for epigraphs as well as block
+                        quotes and extracts within the text.       --> 
+<!ELEMENT  disp-quote   (%disp-quote-model;)                         >
+<!--         id         Unique identifier so the element may be
+                        referenced                                
+             xml:lang   The language in which the value of the
+                        element is expressed.  Recommended best 
+                        practice is to use values as defined in
+                        RFC 1766, typically 2-letter language
+                        codes such as "FR" (French), "EN" (English),
+                        and "DE" (German). These values are NOT
+                        case sensitive, so "EN" = "en". The values
+                        may include hyphenated differentiators such 
+                        as "EN-AU" (Australian English) and "EN-US"
+                        (United States English).                   -->
+<!ATTLIST  disp-quote
+             id         ID                                 #IMPLIED  
+             xml:lang   NMTOKEN                            #IMPLIED  >
+ 
+
+<!--                    ATTRIBUTION ELEMENTS                       -->
+<!--                    The elements that can be included along with
+                        data characters inside the content model of
+                        an attribution                             -->
+<!ENTITY % attrib-elements
+                        "| %emphasized-text;"                        >
+            
+
+<!--                    ATTRIBUTION                                -->
+<!--                    Source, author, formal thanks, copyright
+                        material, or other information concerning 
+                        the origins of an extract, a poem 
+                        <verse-group> or similar element.
+                        Formatting Note: Typically displayed on 
+                        a separate line (or lines, following the 
+                        material it concerns, inheriting that
+                        material's margins.                        --> 
+<!ELEMENT  attrib       (#PCDATA %attrib-elements;)*                 >
+
+
+<!--                    STATEMENT, FORMAL MODEL                    -->
+<!--                    Content model for the <statement> element  -->
+<!ENTITY % statement-model   
+                        "label?, title?, p+"                         > 
+            
+
+<!--                    STATEMENT, FORMAL                          -->
+<!--                    A Theorem, Lemma, Proof, Postulate,
+                        Hypothesis, Proposition, Corollary, or
+                        other formal statement, identified as such
+                        with a label, usually made typographically 
+                        distinct from the surrounding text         --> 
+<!ELEMENT  statement    (%statement-model;)                          >
+<!--         id         Unique identifier so that the statement can 
+                        be referenced by a <xref> element          
+             content-type   
+                        Identification of the subject, type of
+                        content, or reason that this word or phrase
+                        is considered semantically special, as a 
+                        means of preserving the semantic intent of 
+                        the original tagging.                      -->
+<!ATTLIST  statement
+             id         ID                                 #IMPLIED 
+             content-type
+                        CDATA                              #IMPLIED  >
+                        
+
+<!--                    VERSE FORM FOR POETRY                      -->
+<!--                    A song, poem, or verse.
+                        Implementer's Note: No attempt has been made
+                        to retain the look or visual form of the
+                        original.
+                        Remarks: Many physics journals include both
+                        initial epigraphs to articles and short
+                        articles that contain nothing but a topical,
+                        humorous, or elegiac poem.
+                        Related Elements: Poetry may also be tagged 
+                        with the <preformat> if spacing is critical, 
+                        but usually poetry should be tagged with the
+                        <verse-group> element, which may not preserve
+                        the exact indentation but is likely to be
+                        displayed in a proportional font.          -->
+<!ELEMENT  verse-group  ((verse-line | verse-group)+, attrib?)       > 
+<!--          id         Unique identifier so the element may be
+                        referenced
+             xml:lang   The language in which the value of the
+                        element is expressed.  Recommended best 
+                        practice is to use values as defined in
+                        RFC 1766, typically 2-letter language
+                        codes such as "FR" (French), "EN" (English),
+                        and "DE" (German). These values are NOT
+                        case sensitive, so "EN" = "en". The values
+                        may include hyphenated differentiators such 
+                        as "EN-AU" (Australian English) and "EN-US"
+                        (United States English).                   -->                
+<!ATTLIST  verse-group
+             id         ID                                 #IMPLIED  
+             xml:lang   NMTOKEN                            #IMPLIED  >
+
+
+<!--                    LINE OF A VERSE                            -->
+<!--                    One line of a poem or verse                --> 
+<!ELEMENT  verse-line   (#PCDATA | %simple-text;)*                   >
+
+
+<!-- ================== End Paragraph Class Module =============== -->

data/lib/dtd/archiving_dtd/1.1/dtd/phrase.ent

@@ -0,0 +1,244 @@
+<!-- ============================================================= -->
+<!--  MODULE:    Subject Phrase Class Elements                     -->
+<!--  VERSION:   1.1                                               -->
+<!--  DATE:      November 1, 2003                                  -->
+<!--                                                               -->
+<!-- ============================================================= -->
+
+<!-- ============================================================= -->
+<!--                    PUBLIC DOCUMENT TYPE DEFINITION            -->
+<!--                        TYPICAL INVOCATION                     -->
+<!--
+"-//NLM//DTD Archiving and Interchange DTD Suite Subject Phrase Class Elements v1.1 20031101//EN"
+     Delivered as file "phrase.ent"                                -->
+<!-- ============================================================= -->
+
+<!-- ============================================================= -->
+<!-- SYSTEM:     Archiving and Interchange DTD Suite               -->
+<!--                                                               -->
+<!-- PURPOSE:    Defines the phrase.class, that is, names the      -->
+<!--             inline, subject-specific elements                 -->
+<!--                                                               -->
+<!--             If more specific subject words (such as "gene")   -->
+<!--             are added to later version of this DTD, they      -->
+<!--             should be added to the %phrase.class; entity and  -->
+<!--             defined in this module or in %common.ent;         -->
+<!--                                                               -->
+<!-- CONTAINS:   1) Definition of the phrase class                 -->
+<!--             2) Subject Emphasis                               -->
+<!--                                                               -->
+<!-- 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 Archiving and Interchange DTD Suite."  -->
+<!--                                                               -->
+<!--             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 Archiving and Interchange DTD    --> 
+<!--                    Suite."                                    -->
+<!--                                                               -->
+<!--             Suggestions for refinements and enhancements to   -->
+<!--             the DTD suite should be sent in email to:         -->
+<!--                 archive-dtd@ncbi.nlm.nih.gov                  -->
+<!--                                                               -->
+<!-- ORIGINAL CREATION DATE:                                       -->
+<!--             December 2002                                     -->
+<!--                                                               -->
+<!-- CREATED BY: Jeff Beck       (NCBI)                            -->
+<!--             Deborah Lapeyre (Mulberry Technologies, Inc.)     -->
+<!--             Bruce Rosenblum (Inera 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 Version 1.0. The Andrew W.  --> 
+<!--             Mellon Foundation provided support for these      --> 
+<!--             important contributions.                          -->
+<!--                                                               -->
+<!-- ============================================================= -->
+
+
+<!-- ============================================================= -->
+<!--                    DTD VERSION\CHANGE HISTORY                 -->
+<!-- ============================================================= -->
+<!--
+     =============================================================
+
+Version  Reason/Occasion                   (who) vx.x (yyyy-mm-dd)
+
+     =============================================================
+     Version 1.1                           (TRG) v1.1 (2003-11-01)
+  
+  3. Added following parameter entities to the content model for
+     <named-content>:
+        %block.display.class;
+        %block.math;
+        %emphasized-text;
+        %inline-display.class;
+        %list.class;
+        %rest-of-para.class;
+     Rationale: To expand content model of <named-content> to 
+     encompass most of the other phrase-level structures, which
+     will allow preservation ofphrase-level semantic information
+     in content converted to this format.
+     
+  2. Added ID attribute to parameter entity %named-content-atts;  
+     Rationale: Provide unique identifier so <named-content>
+     element can be linked to. 
+         
+  1. Added ID attribute to element <abbrev>. 
+     Rationale: Provide unique identifier so <abbrev> element 
+     can be linked to. 
+                                                                   -->
+
+
+<!-- ============================================================= -->
+<!--                    PARAMETER ENTITY DEPENDENCIES             
+                        Requires that the following parameter 
+                        entities be defined before calling this
+                        module, usually accomplished in the 
+                        Customization Module for the specific DTD:
+                          %emphasized-text;   
+                          %might-link-atts;  
+                                                                   -->
+<!-- ============================================================= -->
+
+
+<!-- ============================================================= -->
+<!--                    DEFAULT DEFINITION OF THE PHRASE CLASS     -->
+<!-- ============================================================= -->
+
+
+<!--                    PHRASE CLASS ELEMENTS                      -->
+<!--                    Small inline elements, that surround a word
+                        or phrase in the text because the subject
+                        (content) should be identified as something
+                        special or different                       -->
+<!ENTITY % phrase.class "abbrev | named-content"                     >
+
+
+<!-- ============================================================= -->
+<!--                    PARAMETER ENTITIES FOR ATTRIBUTE LISTS     -->
+<!-- ============================================================= -->
+                                                                
+                                                                 
+<!--                    NAMED CONTENT ATTRIBUTES                   -->
+<!--                    Attributes for the <named-content> element -->
+<!ENTITY % named-content-atts
+            "content-type   
+                        CDATA                            #REQUIRED 
+             id         ID                                #IMPLIED
+             %might-link-atts;"                                      >
+
+
+<!-- ============================================================= -->
+<!--                    PHRASE-LEVEL ELEMENTS                      -->
+<!-- ============================================================= -->
+
+
+<!--                    ABBREVIATION ELEMENTS                      -->
+<!--                    Elements for use in the <abbrev> element   -->
+<!ENTITY % abbrev-elements
+                        "| def"                                      >
+
+
+<!--                    ABBREVIATION OR ACRONYM                    -->
+<!--                    Used to identify an abbreviation or acronym
+                        DTD Design Note: We have not seen this much 
+                        in the world of STM journal publishing.
+                        This element was added explicitly to
+                        meet "Checkpoint 4.3[3.5] Annotate complex, 
+                        abbreviated, or unfamiliar information with 
+                        summaries and definitions" from the W3C Web
+                        Content Accessibility Guidelines 2.0.
+                        Remarks: The linking attributes can be used
+                        to provide a live link to an expansion,
+                        definition, or additional explanation.     -->
+<!ELEMENT  abbrev       (#PCDATA %abbrev-elements;)*                 >
+<!--         id         Unique identifier so the element may be
+                        referenced                                 
+             xlink:href Provides an address or identifier of the
+                        object to which the link points, for
+                        example a URI or a filename                -->            
+<!ATTLIST  abbrev
+             id         ID                                 #IMPLIED  
+             %might-link-atts;                                       >
+
+
+<!--                    NAMED CONTENT ELEMENTS                     -->
+<!--                    Elements for use in the <named-content> 
+                        content model                              -->
+<!ENTITY % named-content-elements
+                        "| %block-display.class; | %block-math; |
+                         %emphasized-text; | %inline-display.class; |
+                         %list.class; | %rest-of-para.class;"        >
+<!--!ENTITY % named-content-elements
+                        "| %emphasized-text; "                     -->
+
+<!--                    NAMED SPECIAL (SUBJECT) CONTENT            -->
+<!--                    A word or phrase within the text that should
+                        be treated differently, often given a
+                        special typographic style or look, because
+                        the content/subject matter is distinct. For
+                        example, the word is a drug name or a 
+                        gene or the phrase identifies an organism 
+                        genus/species.                             -->
+<!ELEMENT  named-content
+                        (#PCDATA %named-content-elements;)*          >
+<!--         content-type   
+                        Identification of the subject or type of
+                        content that makes this word or phrase
+                        semantically special, usually to be treated 
+                        differently, for example, given a different 
+                        look in print or display.
+                           As an example, this attribute could be 
+                        used to identify a drug name, company name, 
+                        or product name.  It could be used to define 
+                        systematics terms such as genus, family, 
+                        order,  or suborder. It could be used to 
+                        identify biological components such as 
+                        gene, protein, or peptide. Therefore 
+                        values may include information classes, 
+                        semantic categories, or types of nouns, 
+                        such as "generic-drug-name", "genus-species",
+                        "gene", "peptide", "product", etc.  
+             id         Unique identifier so the element may be
+                        referenced                                 
+             xlink:href Provides an address or identifier of the
+                        object to which the link points, for
+                        example a URI or a filename                --> 
+ <!ATTLIST  named-content
+             %named-content-atts;                                    >
+
+
+<!-- ================== End Phrase Class Module ================== -->