<named-content>

Named Special (Subject) Content

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

Remarks

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.
Attribute Best Practice: If the content of the <named-content> element is a term from a taxonomy, ontology, term-list, vocabulary, industry glossary, or other known source, then the vocabulary attributes should be used to record that source. This source can be a formal ontology or an informal field of study. Four attributes are used in this Tag Set to identify terms from such a controlled or an uncontrolled vocabulary:
vocab
Name of the controlled or uncontrolled vocabulary, taxonomy, ontology, index, database, or similar that is the source of the term. For example, for a subject term, a value might be the IPC Codes (“ipc”) or MESH headings (“mesh”). For an uncontrolled term, the value might be an area of study such as “medical-devices” or merely the word “uncontrolled”.
vocab-identifier
Unique identifier of the vocabulary, such as (but not limited to) a URI or DOI. For example, for Dublin Core (DCC), the identifier may be “http://dublincore.org/documents/2012/06/14/dces/”.
vocab-term
The content of the element is the display version of the vocabulary or taxonomic term. The @vocab-term attribute holds the canonical version of the same term, as it appears in the vocabulary. For example, if the attribute value is “digitized-vor”, the element might contain the display text “Digitized Version of Record”.
vocab-term-identifier
Unique identifier of the term within a specific vocabulary, such as (but not limited to) an item number, a URI, DOI, etc.

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 
content-type="foreign-phrase"
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.

Attributes

alt Alternative Text
content-type Type of Content
id Document Internal Identifier
rid Reference to an Identifier
specific-use Specific Use
vocab Vocabulary/Taxonomy Name
vocab-identifier Vocabulary/Taxonomy Identifier
vocab-term Vocabulary/Taxonomy Term
vocab-term-identifier Vocabulary/Taxonomy Term Identifier
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
xml:base Base
xml:lang Language
xmlns:xlink XLink Namespace Declaration

Content Model

<!ELEMENT  named-content
                        (#PCDATA %named-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 | preformat | supplementary-material | table-wrap | table-wrap-group | disp-formula | disp-formula-group | bold | fixed-case | italic | monospace | overline | roman | sans-serif | sc | strike | underline | ruby | 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 | xref | sub | sup | disp-quote | speech | statement | verse-group)*

Description

Any combination of:

This element may be contained in:

<addr-line>, <alt-title>, <article-title>, <attrib>, <award-id>, <bold>, <chapter-title>, <chem-struct>, <code>, <collab>, <comment>, <compound-kwd-part>, <compound-subject-part>, <conf-theme>, <copyright-statement>, <corresp>, <data-title>, <def-head>, <disp-formula>, <element-citation>, <ext-link>, <fixed-case>, <funding-source>, <funding-statement>, <gov>, <inline-formula>, <inline-media>, <inline-supplementary-material>, <italic>, <kwd>, <license-p>, <meta-value>, <mixed-citation>, <monospace>, <named-content>, <on-behalf-of>, <overline>, <p>, <part-title>, <preformat>, <product>, <related-article>, <related-object>, <role>, <roman>, <sans-serif>, <sc>, <see>, <see-also>, <series>, <series-text>, <series-title>, <sig>, <sig-block>, <source>, <std>, <strike>, <styled-content>, <sub>, <subject>, <subtitle>, <sup>, <supplement>, <support-source>, <target>, <td>, <term>, <term-head>, <textual-form>, <th>, <title>, <trans-source>, <trans-subtitle>, <trans-title>, <underline>, <verse-line>, <xref>

Example 1

Making a simple biological nomenclature distinction:
...
<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 xlink:href="http://shigen.lab.nig.ac.jp/ecoli/pec" 
ext-link-type="uri">http://shigen.lab.nig.ac.jp/ecoli/pec</ext-link>
via the Internet Accessed: 5 November 2003</p>
...

Example 2

Used to hold RDF triples:
...
<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
following:

<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>
</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>
</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>
</named-content>
</named-content>

...
</p>
...

Example 3

Making complicated biological nomenclature distinctions:
...
<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.
mays</italic></named-content>
</named-content>
</named-content>
</named-content>
</named-content>
</named-content>
</named-content>
</p>
...

Example 4

Preserving a publisher’s semantics for processing:
...
<abstract>
<p><named-content content-type="sem:AIPTh1.2" rid="kwd1.6">Dielectric</named-content> 
particles flowing through a microfluidic channel over a set of coplanar ...</p>
</abstract>
...
... 
<body>
<p content-type="lead-paragraph">In the field of 
<named-content content-type="sem:AIPTh1.2" rid="kwd1.10">complex 
systems</named-content> study, new measurement and computational 
resources have lead to increased interest ...</p>
...
</body>
...

Journal Publishing Tag Library NISO JATS Version 1.2 (ANSI/NISO Z39.96-2019)

Version of May 2019

Back to Top