<!– ============================================================= –> <!– MODULE: Journal Publishing DTD Customize Content and –> <!– Attributes Module –> <!– VERSION: 2.0 –> <!– DATE: September 2004 –> <!– –> <!– ============================================================= –>

<!– ============================================================= –> <!– PUBLIC DOCUMENT TYPE DEFINITION –> <!– TYPICAL INVOCATION –> <!– “-//NLM//DTD Journal Publishing DTD Customize Content and Attributes Module v2.0 20040830//EN” Delivered as file “journalpubcustom-models.ent” –> <!– ============================================================= –>

<!– ============================================================= –> <!– SYSTEM: Journal Publishing DTD of the –> <!– Archiving and Interchange DTD Suite –> <!– –> <!– PURPOSE: To declare the Parameter Entities (PEs) used to –> <!– over-ride content models or parts of content –> <!– models when making a new DTD from the modules of –> <!– the Archiving and Interchange 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. –> <!– –> <!– CONTAINS: 1) PEs that define OR lists of elements to be –> <!– mixed with #PCDATA in element content models –> <!– (all PEs are named “yyy-elements”, where “yyy” –> <!– is the name of the primary element whose –> <!– content model will use the declared PE.) –> <!– 2) PEs that define complete content models. –> <!– (names ending in the suffix “-model”) –> <!– 3) PEs that define attribute list or attribute –> <!– value over-rides –> <!– –> <!– CREATED FOR: –> <!– Digital Archive of Journal Articles –> <!– National Center for Biotechnology Information –> <!– (NCBI) –> <!– National Library of Medicine (NLM) –> <!– –> <!– ORIGINAL CREATION DATE: –> <!– September 2004 –> <!– –> <!– CREATED BY: Deborah Lapeyre (Mulberry Technologies, Inc.) –> <!– B. Tommie Usdin (Mulberry Technologies, Inc.) –> <!– –> <!– Suggestions for refinements and enhancements to –> <!– this DTD should be sent in email to: –> <!– archive-dtd@ncbi.nlm.nih.gov –> <!– ============================================================= –>

<!– ============================================================= –> <!– DTD VERSION/CHANGE HISTORY –> <!– ============================================================= –> <!–

Version Reason/Occasion (who) vx.x (yyyy-mm-dd)

    =============================================================
    Version 2.0                  (Beck/DAL/BTU) v2.0 (2004-08-30)

    Minor tweaks before public release. Decision was made not to
    change release number

16. JOURNAL METADATA MODEL - Made publisher optional

15. FOOTNOTE ATTRIBUTES - Added the "symbol" attribute back to
    Footnote attributes

14. DISP-FORMULA - Added -%label.class; therefore removed it 
    from this module, as it was then the same as in the
    baseic Suite math.ent

13. AFF-ELEMENTS - Added -%label.class;; therefore removed it 
    from this module, as it was then the same as in the
    baseic Suite math.ent

12. ARTICLE METADATA MODEL -
    a. COUNTS - Added to article metadata model
    b. ARTICLE-ID - Made optional and repeatable (was required
       and repeatable)
    c. COPYRIGHT-YEAR - Made optional

11. FOOTNOTE - Delete over-ride of content model. This has the
    effect of making the Publishing DTD the same as base, 
    adding an optional <label> at the front of footnote.

    =============================================================
    Version 2.0                       (DAL/BTU) v2.0 (2004-08-30)

    Major requirement changes led to the new release, producing
    DTD version "2.0":
      a) The splitting of the Archival and Interchange Tag Set 
         DTDs into three DTDs from two: an authoring DTD, an
         archive regularization and interchange DTD (the
         current Blue Publishing DTD), and a preservationist 
         archive DTD (the current Green Archiving and Interchange 
         DTD).
      b) AIT Working Group suggestions from the June 04 meeting 
         and June/July 2004 followup discussions
      c) Suite remodularization to meet new (and newly articulated)
         modularization requirements
      d) New or renamed classes and mixes to make modifications
         easier and more consistent

10. OVER-RIDE OF ARTICLE-META-MODEL - Added new elements
    a. <custom-meta-wrap> containing <custom-meta>
    b. <email>
    c. <issue-id>
    d. <issue-title> (for special title or theme)
    e. <page-range>
    f. <volume-id>
    g. <license> (for now, just a bucket into which to
       dump license-related material until the AIT Workgroup
       does more analysis)

 9. MOVE AND REMOVE PARAMETER ENTITY DECLARATIONS
    - Deleted duplicate %might-link-atts; (There were two!)
    - Collected ATTLIST over-rides into one place.
    - Deleted all the Parameter Entities which were
      duplicated in this module ONLY because they were
      needed to parse subsequent entities.

 8. ADDRESS-ELEMENTS - added <email> and <uri> to everywhere 
    <ext-link> was allowed, by renaming %ext-link.class; to
    %address-link.class; and using it:
       <email> and <uri> should be added to 
        - %article-meta-model;
        - %aff-elements;
        - %p-elements;

 7.  FOOT NOTE ATTRIBUTES
      - added "symbol"

 6.  Replaced element names in OR groups with the appropriate
     classes. Not a model change, just entity usage:
      - %array-model;
      - %fig-group-model;
      - %list-item-model;

 5. ACCESS CLASS
       ### Customization Alert ###
    a. Took <ext-link> out of -%access.class;. It did not belong.
       It belongs in -%address-link.class;
    b. Added -%address-link.class; to anywhere regular
       %access.class; was used.

 4. OVER-RIDE OF ARTICLE-META-MODEL - Added new elements
    a. <custom-meta-wrap> containing <custom-meta>
    b. <email>
    c. <issue-id>
    d. <issue-title> (for special title or theme)
    e. <page-range>
    f. <volume-id>

 3. COMPLETE MODELS WHEN OVER-RIDING A MODEL 
    (for all Parameter Entities suffixed "-model")
    ### Customization Alert ###
    a. Made all the model over-rides consistent. Some included
       the outer parentheses, some did not. They all do now,
       as this is the most flexible system, allowing for
       #PCDATA, mixed, or element content. (This is in direct
       contrast to the "-element" suffixed models, which are
       designed to prohibit element content and permit only
       #PCDATA or mixed content.)
    -  %article-meta-model; (added parentheses to Parameter
       Entity and removed them from Element Declaration)
    - %abstract-model;
    - %ack-model;
    - %array-model;
    - %author-notes-model;
    - %def-item-model;
    - %fig-group-model;
    - %gloss-group-model;
    - %journal-meta-model;
    - %list-model;
    - %ref-model;
    - %sec-model;
    - %sec-opt-title-model;
    - %trans-abstract-model;

 2. PARAMETER ENTITIES FOR CLASSES/MIXES/ATT LISTS

    a. NEW PARAMETER ENTITIES - To correct potential classing 
       problems,  new Parameter Entities were created. The following
       PEs and models were changed to use these new PEs:
            New Content model PEs:
       - %just-para.class;  used in 
            - %list-item-model; 
       - In <author-notes> "(corresp | fn)+" was replaced
           with the %fn-link.class; and the new class
           -%corresp.class; and )

    b. RENAMED CLASSES
       ### Customization Alert ###
       Not all classes ended in the ".class" suffix. Changed the 
       following to add the class suffix:
       - %address-elements; (also renamed this one -%address.class;!)
         used in:
            - %aff-elements; 
            - %corresp-elements; 
       - %block-math.class; and -%inline-math.class; used in 
            - %p-elements;
       - %display-back-matter.class; used in 
            - %array-model;
       - %rest-of-para.class;
         Inside the content model for Paragraph <p>, was renamed 
         -%p-elements;. The content model for Named Content 
         and %p-elements; still use %rest-of-para.class;.

    c. LINK CLASSES
       ### Customization Alert ###
       - Deleted 
           - %link.class;, 
           - %inpara-address; 
           - %ext-links.class;
       - Replaced above with four link classes: 
         (some unchanged from before)
           - %address-link.class;   (the links used in addresses)
           - %fn-link.class.class;  (just fn)
           - %simple-link.class;    (the internal links, same)
           - %article-link.class;   (links for journal article)
       - All occurrences of %link.class replaced with
           - %address-link.class; and 
           - %simple-link.class;, and 
           - %article-link.class;  links
       - Replaced all occurrences of %ext-links.class; with
         the new %address-links.class;
       - This changed the following Parameter Entities (no DTD 
         model change):
           - %disp-formula-elements;
           - %emphasized.text; 
           - %simple-phrase; 

    d. PARA CLASS
       ### Customization Alert ###
       - Deleted %para.class; 
       - Its place in the definition of the Paragraph <p> element 
         will be taken by the -%p-elements; entity.
       - Its place in other mixes will be taken by the combination
         of %just-para.class; and %rest-of-para.class;

 1. Created this module from material previously in the single
    journal publishing customization module (journalpubcustomize.ent)
    Created at version "v2.0 20040830"                            -->

<!– ============================================================= –> <!– INLINE MIXES TO OVER-RIDE CONTENT MODELS –> <!– (ELEMENTS TO BE ADDED TO #PCDATA IN MODELS)–> <!– ============================================================= –>

<!– ABBREVIATED JOURNAL TITLE ELEMENTS –> <!– The elements that can be included along with

data characters inside the content model of
a <abbrev-journal-title> 
Removed the face markup, %just-rendition;  -->

<!ENTITY % abbrev-journal-title-elements

""                                           >

<!– CONFERENCE ACRONYM ELEMENTS –> <!– The elements that can be included along with

data characters inside the content model of
the conference acronym.    
Removed %simple-text;                      -->

<!ENTITY % conf-acronym-elements

""                                           >

<!– CONFERENCE LOCATION ELEMENTS –> <!– Elements for use in the <conf-loc> element

Removed %simple-text;                      -->

<!ENTITY % conf-loc-elements

" "                                          >

<!– 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.     
Removed %simple-text;                      -->

<!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. 
Removed %simple-text;                      -->

<!ENTITY % conf-sponsor-elements

""                                           >

<!– CONTRACT/GRANT NUMBER ELEMENTS –> <!– The elements that can be included along with

data characters inside the content model of
the contract number.  
Removed %simple-text;                      -->

<!ENTITY % contract-elements

""                                           >

<!– 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>                             
Removed %just-rendition;                   -->

<!ENTITY % degrees-elements

" "                                          >

<!– EDITION ELEMENTS –> <!– The elements that can be included along with

data characters inside the content model of
Removed %just-rendition;                   -->

<!ENTITY % edition-elements

" "                                          >

<!– FAX NUMBER ELEMENTS –> <!– The elements that can be included along with

data characters inside the content model of
a <fax>    
Removed %just-rendition;                   -->

<!ENTITY % fax-elements

" "                                          >

<!– GIVEN (FIRST) NAMES ELEMENTS –> <!– The elements that can be included along with

data characters inside the content model of
a <given-names>                   
Removed %just-rendition;                   -->

<!ENTITY % given-names-elements

" "                                          >

<!– INSTITUTION NAME ELEMENTS –> <!– Elements for use in the <institution>

element                                    
Removed %break.class; and %emphasis.class; -->

<!ENTITY % institution-elements

"| %subsup.class;"                           >

<!– ISSUE TITLE ELEMENTS –> <!– Elements for use with data characters inside

the model for the <issue> element     
Removed %just-rendition;                   -->

<!ENTITY % issue-elements

" "                                          >

<!– JOURNAL TITLE ELEMENTS –> <!– The elements that can be included along with

data characters inside the content model of
a <journal-title>
Removed %just-rendition;                   -->

<!ENTITY % journal-title-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; | %subsup.class;"        >

<!– PATENT NUMBER ELEMENTS –> <!– The elements that can be included along with

data characters inside the content model of
<patent>                             
Removed %just-rendition;                   -->

<!ENTITY % patent-elements

" "                                          >

<!– PHONE NUMBER ELEMENTS –> <!– The elements that can be included along with

data characters inside the content model of
a <phone number>             
Removed %just-rendition;                   -->

<!ENTITY % phone-elements

" "                                          >

<!– PREFORMATTED TEXT ELEMENTS –> <!– Elements that may be used, along with data

characters, inside the content model for the
<preformat> element, in which white space,
such as tabs, line feeds, and spaces will
be preserved                               -->

<!ENTITY % preformat-elements

"| %address-link.class; | %emphasis.class; |
 %subsup.class;"                             >

<!– PREFIX ELEMENTS –> <!– The elements that can be included along with

data characters inside the content model of
a <prefix>  
Removed %just-rendition;                   -->

<!ENTITY % prefix-elements

" "                                          >

<!– PUBLISHER'S LOCATION ELEMENTS –> <!– Elements for use in the Publisher Location

<publisher-loc> element
Removed %address.class;, %address-link.class;, |
%emphasis.class;, and %subsup.class;       -->

<!ENTITY % publisher-loc-elements

" "                                          >

<!– PUBLISHER'S NAME ELEMENTS –> <!– The elements that can be included along with

data characters inside the content model of
a <publisher-name>   
Removed %just-rendition;                   -->

<!ENTITY % publisher-name-elements

" "                                          >

<!– SUFFIX ELEMENTS –> <!– The elements that can be included along with

data characters inside the content model of
a <suffix>
Removed %just-rendition;                   -->

<!ENTITY % suffix-elements

" "                                          >

<!– SURNAME ELEMENTS –> <!– The elements that can be included along with

data characters inside the content model of
a <surname>                                
Removed %just-rendition;                   -->

<!ENTITY % surname-elements

" "                                          >

<!– URI ELEMENTS –> <!– The elements that can be included along with

data characters inside the content model of
a <uri> 
Removed %just-rendition;                   -->

<!ENTITY % uri-elements

" "                                          >

<!– VOLUME NUMBER ELEMENTS –> <!– The elements that can be included along with

data characters inside the content model of
a <volume> 
Removed %just-rendition;                   -->

<!ENTITY % volume-elements

" "                                          >

<!– ============================================================= –> <!– 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.
Unlike the default model in the base DTD
Suite, this <abstract> requires that all
sections in the abstract start with titles.-->

<!ENTITY % abstract-model

"(title?, p*, sec*)"                         >

<!– ACKNOWLEDGMENTS MODEL –> <!– Content model for the <ack> element –> <!ENTITY % ack-model “(title?, p*, sec*, ref-list*)” >

<!– 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;)* )"          >

<!– ARTICLE METADATA MODEL –> <!– Full content model for the metadata that is

specific to the article.                  
Unlike in Archive DTD, some of the metadata  
is required here.                          -->

<!ENTITY % article-meta-model

"(article-id*, article-categories?, 
 title-group, (contrib-group | aff)*, 
 author-notes?, pub-date+, 
 volume?, volume-id*, 
 issue?, issue-id*, issue-title*,  
 supplement?, 
 ((fpage, lpage?, page-range?) | 
   elocation-id)?, 
 (%address-link.class; | product | 
 supplementary-material)*, history?, 
 copyright-statement?, copyright-year?,
 license?,  
 self-uri*, related-article*, abstract*, 
 trans-abstract*, kwd-group*, contract-num*, 
 contract-sponsor*, conference*, counts?,
 custom-meta-wrap*)"                         >

<!– AUTHOR NOTE MODEL –> <!– The content model of a <author-notes>. –> <!ENTITY % author-notes-model

"(title?, 
  (%corresp.class; | %fn-link.class;)+ )"    >

<!– CONFERENCE MODEL –> <!– The content model of the <conference>

element                                    -->

<!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

"((%name.class;)*, (%degree.class;)*,  
  (%contrib-info.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.   
Unlike the base DTD Suite, this <date> 
requires a <year> and may not take a string
date as an alternative.                    -->

<!ENTITY % date-model “(((day?, month?) | season)?, year)” >

<!– DEFINITION LIST: DEFINITION ITEM ELEMENTS –> <!– The content model of a <def-item>. –> <!ENTITY % def-item-model

"(term, def*)"                               >

<!– ET AL –> <!– Unlike in NLMART, <etal> is empty. When

present, it is used to generate the text
"et al."                                   -->

<!ENTITY % etal-model “EMPTY” >

<!– FIGURE-LIKE CONTENT MODEL –> <!– Content model for the Figure element and any

similarly structured elements              
Made <label> and <caption> non-repeatable. -->

<!ENTITY % fig-model “((%id.class;)*, (%label.class;)?,

(%caption.class;)?, 
(%access.class; | %address-link.class;)*,  
(%block-math.class; | %intable-para.class; |
 %just-table.class; | %just-para.class; |
 %list.class; | %simple-display.class;)*,
(%display-back-matter.class;)* )"          >

<!– FIGURE GROUP MODEL –> <!– Content model for a <fig-group> –> <!ENTITY % fig-group-model

"(caption?, 
  (%access.class; | %address-link.class;)*,  
  (%fig-display.class; | 
   %just-base-display.class;)* )"            >

<!– JOURNAL METADATA MODEL –> <!– Content model for the journal metadata

element <journal-meta>                     -->

<!ENTITY % journal-meta-model

"(journal-id+, journal-title*, 
  abbrev-journal-title*, issn+, 
  publisher?, notes?)"                       >

<!– LIST ITEM ELEMENTS –> <!– The content model of a <list-item>. –> <!ENTITY % list-item-model

"(%just-para.class; | %list.class;)+"        >

<!– LIST MODEL –> <!– Content model for the <list> element –> <!ENTITY % list-model “(title?, list-item+)” >

<!– REFERENCE ITEM MODEL –> <!ENTITY % ref-model “(label?,

(citation | nlm-citation | note)+ )"        >

<!– 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. 
Unlike the base DTD Suite, this <section>
may not contain the <label> element.       -->

<!ENTITY % sec-model “(title, (%para-level;)*,

(%sec-level;)*, 
(%sec-back-matter-mix;)* )"                >

<!– CONTENT MODEL FOR AN UNTITLED SECTION –> <!– The model for a section-like structure that

copyright-statement may or may not have 
an initial title                           -->

<!ENTITY % sec-opt-title-model

"(title?, (%para-level;)*,  
  (%sec-level;)*, 
  (%sec-back-matter-mix;)* )"                >

<!– TRANSLATED ABSTRACT MODEL –> <!– Content model for an <trans-abstract>

element                                    -->

<!ENTITY % trans-abstract-model

"(title?, p*, sec*)"                         >

<!– ============================================================= –> <!– DUPLICATE LINKING ATTRIBUTES –> <!– (For use in the attribute over-rides below)–> <!– ============================================================= –>

<!– DISPLAY ATTRIBUTES OPTIONAL ID –> <!– position Must this display object (figure, boxed text,

etc.) be anchored in its exact location
within the text or may it float, for example
to the top of the next page, next column, or
within a separate window?  Values are:
  anchor      Object must remain in place
  float       Object is not anchored and
              may be moved to a new column,
              a new window, etc.
  margin      In print, item should be placed
              in the margin or gutter. 
              Online the item should 
              remain closely associated 
              with the text.               -->

<!ENTITY % display-atts

"position  (anchor | float | margin)        'float'"    >

<!– XLINK LINK ATTRIBUTES –> <!– Attributes for any element that must be a

link                                       -->

<!ENTITY % link-atts

"xmlns:xlink CDATA                            #FIXED
                         'http://www.w3.org/1999/xlink'
 xlink:type  (simple)                   #FIXED 'simple'
 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                            #FIXED
                         'http://www.w3.org/1999/xlink'
 xlink:type  (simple)                   #FIXED 'simple'
 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 –> <!– ============================================================= –>

<!– CITATION ATTRIBUTES –> <!– Attributes for <citation> –> <!ENTITY % citation-atts

"citation-type   
           (book | commun | confproc | discussion |
            gov | journal | list | patent | thesis  |
            web  | other )                    #IMPLIED  
 id         ID                                #IMPLIED
 %might-link-atts;"                                     >

<!– FOOTNOTE ATTRIBUTES –> <!– Attribute list for Footnote element

Unlike base, "fn-type" values have been made 
explicit and removed the symbol attribute  -->

<!ENTITY % fn-atts

"id        ID                                 #IMPLIED  
 fn-type   (abbr | 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)             #IMPLIED  
 symbol     CDATA                             #IMPLIED 
 xml:lang  NMTOKEN                            #IMPLIED" >

<!– GIVEN NAMES ATTRIBUTES –> <!– Removed the “initial” attribute for the given

name, that held initials for those cases in 
which they could not be algorithmically 
determined.                                -->

<!ENTITY % given-names-atts

""                                                      >

<!– GRAPHIC ATTRIBUTES –> <!– Attributes for Graphic <graphic> –> <!ENTITY % graphic-atts

"alternate-form-of
           IDREF                            #IMPLIED
 alt-version
           (yes|no)                             'no'
 id        ID                               #IMPLIED
 mime-subtype  
           (cgm | gif | jpeg | png | tiff)  #IMPLIED 
 mimetype  CDATA                      #FIXED 'image'
 %display-atts;                                       
 %link-atts;"                                           >

<!– SURNAME ATTRIBUTES –> <!– Removed the initial(s) for the surname of

the person. Particularly useful in those 
cases that cannot be algorithmically 
determined.                                -->

<!ENTITY % surname-atts

""                                                      >

<!– INLINE GRAPHIC ATTRIBUTES –> <!– Attributes for Inline Graphic

<inline-graphic>                           -->

<!ENTITY % inline-graphic-atts

"alternate-form-of
           IDREF                              #IMPLIED
 id        ID                                 #IMPLIED
 mimetype  CDATA                        #FIXED 'image'
 mime-subtype  
           (cgm | gif | jpeg | png | tiff)    #IMPLIED 
 %link-atts;"                                           >

<!– PERSON GROUP ATTRIBUTES –> <!– Attributes for the <person-group> element

Valid Types include:
  author - Content creators
  editor - Content editors
  guest-editor
         - a content editor that has been invited 
           to edit all or part of a work.
  inventor
         - Idea, software, or machine creator
  assignee
         - the person to whom a patent is awarded
  translator
         - Translated the cited work from
           one language into another
  transed
         - Editor of a translated version of
           a work
  allauthors
         - used to identify a complete list 
           of authors when a subset of the 
           author group has been used 
           elsewhere in the citation. See 
           "Standard reference to a chapter 
           in a book" (II.C.1) in the 
           tagging examples.
  compiler 
         - Put together a composite work
           from multiple sources           -->

<!ENTITY % person-group-atts

"person-group-type 
           (allauthors | assignee | author | compiler |
            editor | guest-editor | inventor | 
            translator | transed)             #IMPLIED" >

<!– SECTION ATTRIBUTES –> <!– Attribute list for Section element –> <!ENTITY % sec-atts

"id         ID                                 #IMPLIED
 xml:lang   NMTOKEN                            #IMPLIED
 sec-type   CDATA                              #IMPLIED" >

<!– ================== End Publishing Content/ATT Override ====== –>