Archiving Changes in Classes

The following changes were made to the base classes defined in archivecustom-classes3.ent:

• Alternatives Clashes — There is sometimes a need to allow alternatives, but since DTDs cannot handle interleaving, there is also a grammar requirement to name only one <alternatives> element even when groups of display objects are combined. So, in default-classes3.ent, created the following element classes for use in combinations; they hold the contents of the like-named parameter entity, minus only the <alternatives> element:
  • %block-display-noalt.class; (used in archivecustom-models3.ent)
  • %simple-display-noalt.class; (used in archivecustom-models3.ent)
• Citations — Created a new type of citation <element-citation> and added it to %citation.class;.
• References Class — The Archiving Tag Set no longer overrides %references.class;, which is used in the models of <mixed-citation>, <element-citation>, <product>, <related-article>, and <related-object>.
• In archivecustom-classes3.ent, removed %references.class; as duplicative of the Suite default.
  In default-classes3.ent, in %references.class;, added the elements:
  • <chapter-title>,
  • <part-title>,
  • <date-in-citation>,
  • <size>,
  • <string-name>, and
  • <volume-series>.
  
  Also deleted the following elements from %references.class;:
  • <access-date> (replaced by <date-in-citation>),
  • <page-count> (replaced by <size>), and
  • <time-stamp> (replaced by <date-in-citation>).
  
  The current default references class (used by all Tag Sets) is now:

   annotation | article-title | chapter-title |
  collab | comment | conf-date | conf-loc | 
  conf-name | conf-sponsor | date |
  date-in-citation | day | edition | email | 
  elocation-id | etal | ext-link | fpage | 
  gov | institution | isbn | issn | 
  issue | issue-id | issue-part | issue-title | 
  lpage | month | name | object-id | 
  page-range | part-title | 
  patent | person-group | pub-id | 
  publisher-loc | publisher-name | role |
  season | series | size | source | std | 
  string-name | supplement | 
  trans-source | trans-title | uri | 
  volume | volume-id | volume-series | year

• Rest of Paragraph Class — Removed <x> from this class as <x>has now been added to both %all-phrase; and %para-level;.

Archiving Expand use of <x>

For Archiving, it seemed appropriate to “put <x> almost everywhere”, that is, allow <x> everywhere text can be used as well as inside any OR groups where it makes sense.

In All Phrase — First <x> was added to text everywhere by adding <x> to the content of %all-phrase; (using %x.class;) in the module archivecustom-mixes3.ent.

• The addition of <x> to %all-phrase; added <x> to the following elements:
  • <abbrev> (using %abbrev-elements;)
  • <aff> (using %aff-elements;)
  • <alt-title> (using %title-elements;)
  • <anonymous> (using %anonymous-elements;)
  • <article-title> (using %article-title-elements;)
  • <chapter-title> (using %chapter-title-elements;, which uses %source-elements;)
  • <chem-struct> (using %chem-struct-elements;)
  • <compound-kwd-part> (using %compound-kwd-part-elements;)
  • <corresp> (using %corresp-elements;)
  • <copyright-statement> (using %copyright-statement-elements;)
  • <disp-formula> (using %disp-formula-elements;)
  • <email> (using %email-elements;)
  • <etal> (using %etal-elements;)
  • <ext-link> (using %ext-link-elements;)
  • <history> (using %history-elements;)
  • <inline-formula> (using %inline-formula-elements;)
  • <inline-supplementary-material> (using %inline-supplementary-material-elements;)
  • <institution> (using %institution-elements;)
  • <issue-title> (using %issue-title-elements;)
  • <kwd> (using %kwd-elements;)
  • <label> (using %label-elements;)
  • <license> (using %license-model;)
  • <meta-name> (using %meta-name-elements;)
  • <meta-value> (using %meta-value-elements;)
  • <named-content> (using %named-content-elements;)
  • <p> (using %p-elements;)
  • <part-title> (using %part-title-elements;), which uses (using %source-elements;)
  • <preformat> (using %preformat-elements;)
  • <publisher-loc> (using %publisher-loc-elements;)
  • <role> (using %role-elements;)
  • <self-uri> (using %self-uri-elements;)
  • <sig-block> (using %sig-block-elements;)
  • <sig> (using %sig-elements;)
  • <source> (using %source-elements;)
  • <speaker> (using %speaker-elements;)
  • <string-date> (using %string-date-elements;)
  • <string-name> (using %string-name-elements;)
  • <styled-content> (using %styled-content-elements;)
  • <subject> (using %subject-elements;)
  • <subtitle> (using %title-elements;)
  • <target> (using %target-elements;)
  • <term> (using %term-elements;)
  • <title> (using %struct-title-elements;)
  • <trans-source> (using %source-elements;)
  • <trans-subtitle> (using %title-elements;)
  • <trans-title> (using %title-elements;)
  • <xref> (using %xref-elements;)
• In Emphasized Text — The parameter entity %all-phrase; is also used in the definition of %emphasized-text;, which added <x> to the following elements:
  • <attrib> (using %attrib-elements;)
  • <bold>
  • <italic>
  • <monospace>
  • <roman>
  • <sans-serif>
  • <sc>
  • <overline>
  • <strike>
  • <sub>
  • <sup>
  • <underline>
• In Tables — The parameter entity %all-phrase; is also used in the definition of %inside-cell;, which added <x> to the following elements:
  • <td> (XHTML Table Data via %Flow.mix;)
  • <th> (XHTML Table Head via the parameter entity %Flow.mix;)
  • entry (Oasis Table Entry via the parameter entity paracon)
• In Simple Text Elements — The parameter entity %all-phrase; is also used in the definition of %just-rendition;, which added <x> to the following elements:
  • <abbrev-journal-title>
  • <degrees>
  • <edition>
  • <fax>
  • <given-names>
  • <issue-part>
  • <issue-sponsor>
  • <issue>
  • <journal-subtitle>
  • <journal-title>
  • <patent>
  • <phone>
  • <prefix>
  • <publisher-name>
  • <suffix>
  • <surname>
  • <unstructured-kwd-group>
  • <uri>
  • <volume-id>
  • <volume-series>
  • <volume>
• In Ordinary Text Elements — The parameter entity %all-phrase; is also used in the definition of %rendition-plus;, which added <x> to the following elements:
  • <gov>
  • <on-behalf-of>
  • <series-text>
  • <series-title>
  • <series>
  • <std>
• In Text Elements — The parameter entity %all-phrase; is also used in the definition of %simple-phrase;, which added <x> to the following elements:
  • <term-head> (using %def-list-head-elements;)
  • <def-head> (using %def-list-head-elements;)
  • <comment> (using %comment-elements;)
• In Complex Text Elements — The parameter entity %all-phrase; is also used in the definition of %simple-text;, which added <x> to the following elements:
  • <addr-line>
  • <award-id>
  • <conf-acronym>
  • <conf-loc>
  • <conf-name>
  • <conf-num>
  • <conf-sponsor>
  • <conf-theme>
  • <funding-source>
  • <string-conf>
  • <supplement>
  • <verse-line>
• Duplication — Adding <x> to %all-phrase; also caused a few element duplications in models where <x> had previously been included explicitly. Therefore, removed <x> from %rest-of-para.class; (using %x.class;).
  Removal of <x> from %rest-of-para.class; meant that, to retain <x> at the Paragraph level, %x.class; had to be added back to the mix %para-level; in the module archivecustom-mixes3. All other content models which used %rest-of-para.class; had already been redefined by Archiving and so already included <x>.

Trivial Addition to OR Groups — The element <x>was added to the following element content elements (using %x.class;) as a trivial change to an internal OR group:

• <author-notes> (as an alternative to <corresp> or <fn> inside %author-notes-model;)
• <fn-group> (as an alternative to <fn> inside %fn-group-model;)
• <list> (as an alternative to <list-item> inside %list-model;)

Trivial Addition to Mixed Content — The element <x> was added as a trivial change to the following mixed-content elements (using %x.class;) :

• <copyright-holder> (using %copyright-holder-elements;)
• <country> (using %country-elements;)
• <isbn> (using %isbn-elements;)
• <issn> (using %issn-elements;)
• <long-desc> (using %long-desc-elements;)
• <related-object> (using %related-object-elements;)
• <size> (using %size-elements;)
• <time-stamp> (using %time-stamp-elements;)
• <x> (using %x-elements;)

Major Model Change — The element <x> was added to the following elements (using %x.class;) , resulting in major model changes:

• Contributor — In archivecustom-models3.ent, changed <contrib> (using %contrib-model;) from a semi-sequential model that required the name elements to be first:

  ( (%name.class;)*, 
  (%degree.class; | %contrib-info.class; | 
  %x.class;)* )

  
  to a large OR group which includes <x> and all the contributor information class elements as well as all of the name class elements in any order as required, which should give archives maximum freedom:

  ( (%name.class; | %degree.class; | 
  %contrib-info.class; | %x.class;)* )

• Publication Date — In archivecustom-models3.ent, changed <pub-date> from a sequential model:

  (season?, (day?, month?)?, year?, string-date?)

  
  to a large OR group which includes <x> as well as all the potential dates:

  (day | month | year | season | string-date | x)*

• Reference List — In archivecustom-models3.ent, changed a <ref-list> sequence of paragraph-level objects followed by all the references <ref>:

  (title?, (%para-level;)*, ref*, (%ref-list.class;)* )

  
  to a large OR group, with <x> coming in through para-level and all paragraph objects being allowed to be interspersed with references (<ref>):

  (label*, title?, (%para-level; | ref)*, 
  (%ref-list.class;)* )

  
  Best practice would not tag interspersed paragraphs in a reference list, since these almost always indicate the presence of subsidiary (untitled) reference lists. In an authoring or publishing tag set, such lists would be identified explicitly. But archiving tag sets do not always have the luxury of reading and understanding the content being converted, and all that can be determined without human intelligence is that paragraphs are interspersed with references <ref> inside the reference list.

Where <x> is Not — By design, <x> was therefore not added to elements that were viewed as critical #PCDATA-only metadata such as identifiers, page numbers, and date components. The <x> was also not added to the few restricted, single-function elements in the Tag Sets (such as <glyph-data>). Therefore, the element <x> was explicitly not added to the following #PCDATA-only elements:

• <alt-text>
• <article-id>
• <copyright-year>
• <day>
• <elocation-id>
• <fpage>
• <glyph-data>
• <issue-id>
• <journal-id>
• <lpage>
• <month>
• <object-id>
• <page-range>
• <pub-id>
• <season>
• <tex-math>
• <year>

Archiving Article Metadata Element

In the module archivecustom-models3.ent, the new <article-meta> element, after all changes, is defined as:

(article-id*, article-categories?, 
title-group?, 
(contrib-group | aff | %x.class;)*, 
author-notes?, pub-date*,
volume?, volume-id*, volume-series?, 
issue?, issue-id*, issue-title*,
issue-sponsor*, issue-part?, isbn*, 
supplement?, 
( ( (fpage, lpage?)?, page-range?) | 
elocation-id )?, 
(%address-link.class; | product | 
supplementary-material)*, 
history?, permissions?, self-uri*, 
related-article*, abstract*, 
trans-abstract*, kwd-group*, funding-group*, 
conference*, counts?, custom-meta-group?)

The changes to make this new model (using %article-meta-model;) are:

• Funding Information — Replaced the following element grouping with “funding-group*”:

  contract-num*, contract-sponsor*, grant-num*, grant-sponsor*,

• Loose Copyright — Inside %article-meta-model;, moved <copyright-statement>, <copyright-year>, and <license> to inside <permissions> instead of being both inside and outside it. The modeling:

  history?, copyright-statement?, 
  copyright-year?, license?, permissions?, self-uri*, 

  
  was changed to:

  history?, permissions?, self-uri*, 

• Issue Part — Added <issue-part> and <issue-sponsor> to <article-meta> following the other issue information:

  issue?, issue-id*, issue-title*,
  issue-sponsor*, issue-part?, isbn*, 

• ISBN — Added an optional, repeatable <isbn> as part of the potential issue information inside <article-meta>.
• String Conference — Added new element <string-conf>, which uses (%string-conf-elements;) for use inside <conference> using %conference.class;. This element provides a way to record textual statements of all the conference information in one place. For best practice (when possible), this single statement should be in addition to, not as a replacement for, the regular conference metadata.
• Volume Series — Added <volume-series> to <article-meta> to hold the series number, in those odd cases where, for example, a Journal has started reissuing with number one and has added a series number to the volume numbers:

   volume?, volume-id*, volume-series?, 
  

Archiving Other Article Metadata

Some elements within the article metadata also changed models:

• Article Title — In archivecustom-models3.ent, added an override for the new parameter entity %article-title-elements; to be used inside <article-title> instead of %title-elements;, because the content of all structural titles was expanded, but the content for <article-title> should not do so. The <article-title> element now includes:

  %all-phrase; | %break.class;

• Author Notes — In archivecustom-models3.ent, expanded the model for <author-notes>, by adding the following elements to the OR group inside <author-notes> (using %author-notes-model;):
  • <p> (using %just-para.class;) (which can contain both text and, for example, <named-content>)
  • <x> (using %x.class;)
• Collab — In archivecustom-models3.ent, enhanced the model of <collab> (using %collab-elements;) to allow additional elements inside a <collab>, to make it more like a contributor. The original model for <collab> included the following elements:

  %all-phrase; | %break.class; | %x.class;

  • Added the elements of the %contrib-info.class; to this OR mix. That adds the following elements to <collab>:

    address | aff | author-comment | bio | 
    email | etal | ext-link | on-behalf-of |
    role | uri | xref
    

  • Also added <contrib-group> to <collab>
  • Also added %address.class;, which added the elements:

    addr-line | country | fax | institution | phone

  
  (Implementor’s Note: When %contrib-info.class; was added to <collab>, that caused some duplication errors. Changed the content of %collab-elements; from including %all-phrase; to including most of the pieces of %all-phrase;. Added %contrib-info.class; to the mix, which necessitated removing %address-link.class;, %simple-link.class;, and %fn-link.class; to get rid of duplications.)
• Contributor Model — In archivecustom-models3.ent, modified the model of <contrib> ( using %contrib-model;) from an ordered model where the name elements must precede all other elements, to a optional repeatable OR group that includes <x>.

  (%name.class; | %degree.class; | %contrib-info.class; | %x.class;)*

• Contrib Group — The new %contrib-group.class; adds <contrib-group> to <collab> (using the override %collab-elements;).
• Keyword Group — In archivecustom-models3.ent, modified the model of <kwd-group> ( using %kwd-group-model;):
  • Added an optional <label> before the <title>,
  • Allowed <x> as an alternative to <kwd>, and
  • Added <unstructured-kwd-group> as an alternative to a bunch of keywords.
  The resulting model is as follows:

  (label*, title?,
  ( (%kwd.class; | %x.class;)+ | unstructured-kwd-group ) )
  

• Publication Date — In archivecustom-models3.ent, modified the model of <pub-date> ( using %pub-date-model;) from an ordered model where season must precede day and month and both must precede year, to a optional repeatable OR group that includes <x> along with all the date elements, because complete freedom in dates is more in the spirit of Archiving:

  (day | month | year | season | string-date | x)*

• Related Object — In archivecustom-models3.ent, modified <related-object> by allowing the following elements to be mixed with text (overriding %related-object-elements;) . (Note: This includes the content named by %all-phrase;, which was not used explicitly because of duplication clashes with %references.class;):

  | %article-link.class; | 
  %appearance.class; | %break.class; |
  %emphasis.class; |
  %inline-display.class; | 
  %inline-math.class; | %label.class; |
  %math.class; | %phrase.class; | 
  %references.class; |
  %simple-link.class; |
  %subsup.class; | %x.class;

Archiving Funding Information

• Funding Statement —<funding-statement>. This is a mixed-content model patterned after the <copyright-statement>. In the Suite default, which all Tag Sets except Archiving use, the content includes the text, potentially mixed with emphasis elements, subscript and superscript, the phrase-level elements such as <named-content>, and a few links. In Archiving, the content includes the parameter entity %all-phrase;, which allows the new elements <award-id>, <funding-source>, and <open-access> to be mixed into the text, since they may not be identified separately.
• Inside Article Metadata — In the module archivecustom-models3.ent, replaced the following element grouping by “funding-group*”:

  contract-num*, contract-sponsor*, grant-num*, grant-sponsor*,

• Inside a Paragraph — In archivecustom-models3.ent, modified Paragraph (<p> using %p-elements;) by replacing contract-grant.class (which named the old grant and contract elements) with %funding.class; (which names the new funding and award elements).
• Award-ID Attributes — In the module archivecustom-models3.ent), the attributes for <award-id> are expanded to be the same optional attributes available for <award-group>, since <award-id>s are more likely to be loose in text in Archiving than in the other Tag Sets.
  • @id (an ID-type attribute, so the award can be referenced)
  • @rid (an IDREFS-type attribute)
  • @award-type (a textual description or categorization of the award)
  • and the usual linking attributes for optional linking

Archiving Front Stub Metadata

In archivearticle3.dtd, enhanced the <front-stub> model to include all elements in <article-meta>. Thus, in Archiving, the potential metadata elements are same for both <front-stub> and <article-meta>, to accommodate whatever subset a publisher might think appropriate for a <front-stub>, while retaining the convenience of not being required to repeat the infrastructure of a full <front> for a <sub-article> .

Archiving Reference Lists

The Archiving Tag Set no longer has an override for the %references.class;. This Tag Set uses the default references elements, adding special Archive-only elements such as <x> to the individual models of the citation elements (<element-citation> and <mixed-citation>) using the parameter entity %citation-elements; .

• New Elements in Citations — In default-classes3.ent, added the following new elements to %references.class;:
  • <chapter-title>,
  • <date-in-citation> (replaces <time-stamp> and <access-date>),
  • <issue-part>,
  • <part-title>,
  • <series> (a requested addition; was already present in the class),
  • <size> (replaces <page-count>), and
  • <volume-series>.
  
  This lead to duplication, so in archivecustom-models3.ent, removed <size> (using size.class) from <product> through %product-elements;.
• Date Elements Deleted from Citations — In default-classes3.ent, deleted the following elements from %references.class;: [Backward incompatible]
  • <access-date> (replaced by <date-in-citation>)
  • <time-stamp> (replaced by <date-in-citation>)
  • <page-count> (replaced by <size>)
• Comment — Added an override for %comment-elements; to expand the elements available in the mixed content by changing %simple-phrase; to %all-phrase;.
• Size Versus Page Count — Now that the <size> element exists within <product>, <mixed-citation>, <element-citation>, <related-article>, and <related-object> (using %references.class;), there is no need to carry the EMPTY <page-count> element as well; so <page-count> can be reserved for metadata uses. Therefore, in archivecustom-classes3.ent, removed <page-count> from the parameter entity %references.class;.
• Parameter Entity Modification — Implementor’s Note: In previous Tag Set versions, the parameter entity %citation-elements; was only used to create mixed-content, so by convention it started with an “|” bar. Now it may be used mixed with #PCDATA or used as an entire element-only model, so the initial “|” bar has been removed in the base Suite. For Archiving, also removed from the “|” from the beginning of %citation-elements; in archivecustom-models3.ent.

Archiving New Labels

Added an optional <label> to just before <title> in all the following elements:

• <app-group> (in backmatter3.ent)
• <author-notes> (in archivecustom-models3.ent)
• <back> (in archivearticle3.dtd)
• <disp-quote> (in para3.ent)
• <fn-group> (in archivecustom-models3.ent)
• <fn-group> (in backmatter3.ent)
• <kwd-group> (in archivecustom-models3.ent)
• <kwd-group> (in articlemeta3.ent)
• <ref-list> (in archivecustom-models3.ent)
• <ref-list> (in references3.ent)
• <table-wrap-foot> (in archivecustom-models3.ent)
• <textual-form> (in archivecustom-models3.ent)
• <verse-group> (in para3.ent)

Archiving Element Overrides

In archivecustom-models3.ent:

• Anonymous — Changed the parameter entity but not the content of <anonymous> (using %anonymous-elements;) to use %all-phrase;.
• Citations Inside Titles
  • Structural Titles — In archivecustom-models3.ent, added the citation elements to <title> (using %struct-title-elements;, which now contains the %citation.class;, which names <mixed-citation>, <element-citation>, and <nlm-citation>).
  • Lesser Titles — In archivecustom-models3.ent, added the citation elements to the following elements (using %title-elements;, which now contains %citation.class;, which names <mixed-citation>, <element-citation>, and <nlm-citation>). This allows citations to appear inside the following elements:
    • <alt-title>
    • <subtitle>
    • <trans-title>
    • <trans-subtitle>
• Compound Keyword — Changed the mixed content of <compound-kwd-part> (using %compound-kwd-part-elements; ) to use %all-phrase; and line break (using %break.class;).
• Et Al. — Changed the parameter entity but not the content of <etal> (using %etal-elements; ) to use %all-phrase;.
• Role — Changed the parameter entity but not the content of <role> (using %role-elements; ) to use %all-phrase;.
• Signature Block — In archivecustom-models3.ent, changed the model of <sig-block> (using the override for %sig-block-elements;) by adding the following elements to the large OR group that is the <sig-block> model:
  • <aff> and <etal> (using %person-group-info.class;), and
  • <contrib> (using %contrib.class;)
  After these changes, <sig-block> may contain:

  %all-phrase; | %break.class; | %contrib.class; | 
  %just-base-display.class; | %person-group-info.class; | 
  %phrase-content.class; | %sig.class;
  
  

• Styled-Content Override — Changed the content of <styled-content> (using %styled-content-elements;) to include %all-phrase;. Also replaced %block-display.class; with %block-display-noalt.class; to prevent duplicate <alternatives> elements.
• Table Wrap Foot — In archivecustom-models3.ent, added to the model of <table-wrap-foot> (using %table-wrap-foot-model;) by:
  • Adding an optional repeatable <label> to the start of the element
  • Adding <fn-group> (using the new class %fn-group.class;)
  • Adding <x> (using %x.class;)
• X Elements — In archivecustom-models3.ent, added <named-content> and <styled-content> to <x> (using %phrase-content.class; inside %x-elements;).

Archiving Chemical Structures Changes

Although it was not the intent when the Tag Sets were written, most Tag Set users have been treating <chem-struct> as an inline and <chem-struct-wrap> as a block structure. This greatly simplifies all processing with the two and seems quite flexible, so steps were taken to regularize this usage:

• As an inline object, <chem-struct> should be able to be used anywhere that <inline-formula> is used, therefore <chem-struct> has been added to %inline-math.class; (in default-classes3.ent.
• As an inline object, <chem-struct> should not be used as a block-level object, so it was removed from %block-display.class; (in default-classes3.ent).
• As an inline object, <chem-struct> must be inside <chem-struct-wrap> (using %chem-struct-wrap-model;) (in display3.ent).
• As a block object, <chem-struct-wrap> needs to be everywhere block display objects are used, so it needs to be part of the %block-display.class; and %floats-display.class;, which it already was in the default (default-classes3.ent).
• As a block object, <chem-struct-wrap> should be inside figures (using %fig-model;), which it already was in the default (display3.ent).
• Changed the OR group allowed inside <table-wrap> (using %inside-table-wrap;) to allow <chem-struct-wrap> instead of <chem-struct>.

The element <chem-struct> has been removed from within the following elements, where it has been allowed in previous versions, allowing only the block <chem-struct-wrap> to be used: [Backward incompatible]

• <table-wrap> (using %inside-table-wrap;)

Following these changes, <chem-struct> is now allowed within the following elements:

• <abbrev>
• <abbrev-journal-title>
• <addr-line>
• <aff>
• <alt-title>
• <alternatives>
• <anonymous>
• <article-title>
• <attrib>
• <award-id>
• <bold>
• <chapter-title>
• <chem-struct>
• <chem-struct-wrap>
• <mixed-citation>
• <collab>
• <comment>
• <compound-kwd-part>
• <conf-acronym>
• <conf-loc>
• <conf-name>
• <conf-num>
• <conf-sponsor>
• <conf-theme>
• <copyright-statement>
• <corresp>
• <def-head>
• <degrees>
• <disp-formula>
• <edition>
• <email>
• <etal>
• <ext-link>
• <fax>
• <element-citation>
• <funding-source>
• <given-names>
• <gov>
• <history>
• <inline-formula>
• <inline-supplementary-material>
• <institution>
• <issue>
• <issue-part>
• <issue-sponsor>
• <issue-title>
• <italic>
• <journal-subtitle>
• <journal-title>
• <kwd>
• <label>
• <license-p>
• <meta-name>
• <meta-value>
• <monospace>
• <named-content>
• <on-behalf-of>
• <overline>
• <p>
• <part-title>
• <patent>
• <phone>
• <prefix>
• <preformat>
• <product>
• <publisher-loc>
• <publisher-name>
• <related-article>
• <related-object>
• <role>
• <roman>
• <sans-serif>
• <sc>
• <self-uri>
• <series>
• <series-text>
• <series-title>
• <sig>
• <sig-block>
• <source>
• <speaker>
• <std>
• <strike>
• <string-conf>
• <string-date>
• <string-name>
• <styled-content>
• <sub>
• <subject>
• <subtitle>
• <suffix>
• <sup>
• <supplement>
• <surname>
• <target>
• <td>
• <term>
• <term-head>
• <th>
• <title>
• <trans-source>
• <trans-subtitle>
• <trans-title>
• <underline>
• <unstructured-kwd-group>
• <uri>
• <verse-line>
• <volume>
• <volume-id>
• <volume-series>
• <xref>

Following these changes, <chem-struct-wrap> is now allowed within the following elements:

• <abstract>
• <ack>
• <app>
• <app-group>
• <bio>
• <body>
• <boxed-text>
• <disp-quote>
• <fig>
• <floats-group>
• <glossary>
• <license-p>
• <named-content>
• <notes>
• <p>
• <ref-list>
• <sec>
• <styled-content>
• <supplementary-material>
• <table-wrap>
• <td>
• <term>
• <th>
• <trans-abstract>

Archiving Attribute Changes

• Trans Title Group — In archivecustom-models3.ent, used an override to make the @xml:lang attribute optional on <trans-title-group> (via %trans-title-group-atts; ). The Suite default has a required @xml:lang attribute on the <trans-title-group> element (which holds the translated title in the metadata) but not on the <trans-title> element (which is used in citations).