Named Special (Subject) Content

Word or phrase whose content/subject matter has distinct semantics or content-related significance.


In print or display, such semantic content is likely to be treated differently, for example, given a stand-out typographic style such as italics or background shading.


alt Alternative Text
content-type Type of Content
id Identifier
specific-use Specific Use
xlink:actuate Actuating the Link
xlink:href Href (Linking Mechanism)
xlink:role Role of the Link
xlink:show Showing the Link
xlink:title Title of the Link
xlink:type Type of Link
xmlns:xlink XLink Namespace Declaration
xml:lang Language

Related Elements

The related <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, 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".

Best Practice: Similarly, if a word is in italics because it is a foreign phrase, one very typical way to tag it would be as:

...remarkable for his <named-content 
xml:lang="fr">joie de vivre</named-content>
and lively expression.

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  named-content
                        (#PCDATA %named-content-elements;)*          >

Expanded Content Model

(#PCDATA | email | ext-link | uri | inline-supplementary-material | related-article | related-object | hr | bold | italic | monospace | overline | overline-start | overline-end | roman | sans-serif | sc | strike | underline | underline-start | underline-end | 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 | 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)*


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>, <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>, <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>, <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>, <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>... Here is the classification system for a common
vegetable, corn:
<named-content content-type="kingdom">Plantae
<named-content content-type="phylum">Anthophyta
<named-content content-type="class">Monocotyledonae
<named-content content-type="order">Commelinales
<named-content content-type="family">Poaceae
<named-content content-type="genus"><italic>Zea</italic>
<named-content content-type="species"><italic>Z.


Example 2

<contrib contrib-type="author" id="a4762">
<aff rid="a4762">
<institution>The Ohio State University</institution>
<addr-line>Columbus, Ohio</addr-line>
<institution>The Ohio State University,
<named-content content-type="department">Department
of Family Medicine</named-content></institution>
<addr-line>2231 N. High St.</addr-line>
<named-content content-type="state">OH</named-content>
<named-content content-type="postcode">43201</named-content>
<country country="US">United States</country>


Example 3

<p>... To given an idea how one might
construct a series of RDF-triples concerning information on
Wikipedia&reg; about &ldquo;March Madness&rdquo;, consider the

<named-content content-type="RDF subject">&lt;http://en.wikipedia.org/wiki/March_madness&gt;
<named-content content-type="RDF predicate">&lt;http://purl.org/dc/elements/1.1/publisher&gt;
<named-content content-type="RDF object">"Wikipedia"</named-content>

<named-content content-type="RDF subject">&lt;http://en.wikipedia.org/wiki/March_madness&gt;
<named-content content-type="RDF predicate">&lt;http://purl.org/dc/elements/1.1/title&gt;
<named-content content-type="RDF object">"NCAA Men's Division I Basketball Championship"</named-content>

<named-content content-type="RDF subject">&lt;http://en.wikipedia.org/wiki/March_madness&gt;
<named-content content-type="RDF predicate">&lt;http://purl.org/dc/elements/1.1/subject&gt;
<named-content content-type="RDF object">"single elimination tournament"</named-content>



Example 4

<p>Profiling of 
<named-content content-type="genus-species">Escherichia 
coli</named-content> chromosome (PEC) described in the
Database version 2.27. Last update 17 September 
2003. Available at <ext-link ext-link-type="uri" 
via the Internet Accessed: 5 November 2003</p>