Journal Archiving and Interchange Tag Library NISO JATS Draft Version 1.1d1

<styled-content>

Styled Special (Subject) Content

Stylistically distinct word or phrase within the text that cannot be tagged using any of the other mechanisms for such content. In other words, the content cannot be described with bold, italic, monospace or any of the other emphasis elements, and <named-content> is inappropriate because the semantic reason behind the typographic distinction is unknown or not clear.

Remarks

This element is intended for archives who wish to preserve all of the differentiations made by the original publisher (even when the intent for such a distinction is unclear or not necessarily semantic) as well as for publishers and authors who want to make a stylistic rather than a semantic distinction.

Best Practice: For publishers who want to keep a number of named styles consistent throughout the document, the particular stylistic distinction can be named using the @style attribute.

Historical Note: This element replaces the <font> element that was in previous versions of the Tag Suite.

Attributes

alt Alternative Text
id Document Internal Identifier
specific-use Specific Use
style Style (NISO JATS table model; MathML Tag Set)
style-type Style Type
toggle Toggle Switch
xml:base Base
xml:lang Language

Related Elements

The related <named-content> element may, in some instances, produce the same look on print or display as some <styled-content> elements. Both mark content that has a visual distinction; the difference between the two elements is intent. If it is known that this word is in italics because it is a genus or species name, those semantics should be preserved with a <named-content> element with a @content-type attribute of “genus-species” or equivalent. The <styled-content> element would merely tell you that it was always in green shaded background (style="green-shading").

Being web-only or print-only is not a stylistic matter, but rather a particular use, which should be tagged with the @specific-use attribute on the appropriate element, perhaps even on a <named-content> or <styled-content> element.

Content Model

<!ELEMENT  styled-content
                        (#PCDATA %styled-content-elements;)*         >

Expanded Content Model

(#PCDATA | email | ext-link | uri | inline-supplementary-material | related-article | related-object | hr | bold | fixed-case | italic | monospace | overline | overline-start | overline-end | roman | sans-serif | sc | strike | underline | underline-start | underline-end | ruby | alternatives | inline-graphic | private-char | chem-struct | inline-formula | tex-math | mml:math | abbrev | milestone-end | milestone-start | named-content | styled-content | fn | target | xref | sub | sup | x | address | array | boxed-text | chem-struct-wrap | code | fig | fig-group | graphic | media | preformat | supplementary-material | table-wrap | table-wrap-group | disp-formula | disp-formula-group | def-list | list | ack | disp-quote | speech | statement | verse-group)*

Description

Any combination of:

This element may be contained in:

<abbrev>, <abbrev-journal-title>, <addr-line>, <aff>, <alt-title>, <anonymous>, <article-title>, <attrib>, <award-id>, <bold>, <chapter-title>, <chem-struct>, <code>, <collab>, <comment>, <compound-kwd-part>, <compound-subject-part>, <conf-acronym>, <conf-loc>, <conf-name>, <conf-num>, <conf-sponsor>, <conf-theme>, <copyright-statement>, <corresp>, <def-head>, <degrees>, <disp-formula>, <edition>, <element-citation>, <email>, <etal>, <ext-link>, <fax>, <fixed-case>, <funding-source>, <funding-statement>, <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>, <mixed-citation>, <monospace>, <named-content>, <on-behalf-of>, <overline>, <p>, <part-title>, <patent>, <phone>, <prefix>, <preformat>, <product>, <publisher-loc>, <publisher-name>, <rb>, <related-article>, <related-object>, <role>, <roman>, <sans-serif>, <sc>, <self-uri>, <series>, <series-text>, <series-title>, <sig>, <sig-block>, <source>, <speaker>, <std>, <std-organization>, <strike>, <string-conf>, <string-date>, <string-name>, <styled-content>, <sub>, <subject>, <subtitle>, <suffix>, <sup>, <supplement>, <surname>, <target>, <td>, <term>, <term-head>, <textual-form>, <th>, <title>, <trans-source>, <trans-subtitle>, <trans-title>, <underline>, <unstructured-kwd-group>, <uri>, <verse-line>, <volume>, <volume-id>, <volume-series>, <x>, <xref>

Example 1

...
<p><styled-content specific-use="print" style="drop cap">D</styled-content>etecting
pancreatic cancer in its early stages is complicated by the non-specificity
and variety of its symptoms, many of which may go unnoticed or be seen as
indicia of other diseases or medical conditions.  Symptoms commonly occuring
include upper abdominal pain traversing to the back, weight loss, decreased
appetite, and jaundice ...</p>
...

Example 2

The empty attribute is a signal to screen readers to skip a graphic:

...
<p>While we know from the earlier analysis that these hens
formed a linear hierarchy and the rank of the individuals
within the hierarchy, we do not know any of the behavioural
details by which they formed the hierarchy or came to take
their places within it ...
<styled-content alt="" specific-use="background image">
<graphic xlink:href="images/1800-648-1.jpg"
position="background"/>
</styled-content></p>
...

Module

JATS-phrase1.ent

Journal Archiving and Interchange Tag Library NISO JATS Draft Version 1.1d1

Version of December 2013