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

Usage/Remarks

This element is intended to record the formatting differentiations made by a standards organization (even when the intent for such a distinction is unclear or not semantic).

Best Practice

For standards organizations who want to keep a number of named styles consistent throughout the document (for use by CSS or HTML, for example), the particular stylistic distinction can be named using the @style attribute.
Related Elements
Named/Styled Content Best Practice: The <styled-content> element may, in some instances, produce the same look on print or display as some <named-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, this 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" or in italics.
Specific Use: 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.
Attributes

Base Attributes

Models and Context
May be contained in
Description
Any combination of:
Content Model
<!ELEMENT  styled-content
                        (#PCDATA %styled-content-elements;)*         >
Expanded Content Model

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

Tagged Samples
To give formatting information
...
<front>
 ...
 <sec sec-type="foreword">
  <title>Foreword</title>
  <p><styled-content style="text-align: center; padding-left: 6em; 
   padding-right:6em"><italic>(This foreword is not part of the proposed 
   standard NISO Z39.96-201x, JATS: Journal Article Tag Suite. It is 
   included for information only.)</italic></styled-content></p>
  ...
 </sec>
</front>
...
To name colors
...
<list-item>
 <p><strike><styled-content style="color" style-type="red">IEEE 
  Std 802.1ad&#x2122; 2005, IEEE Standard for Local and Metropolitan 
  lAi:rea Networks: Tirtual Bridged Local Area Networks Amendment 4: 
  Provider Bridges.</styled-content></strike></p>
</list-item>
<list-item>
 <p><underline><styled-content style="color" style-type="blue">IEEE 
  Std 802.1AE&#x2122;, IEEE Standard for Local and Metropolitan Area 
  Networks: Media Access Control (MAC) Security.</styled-content></underline></p>
</list-item>
...