content-type
Type of Content
Subject or type of content that makes this element semantically distinct.
Remarks
The values for this attribute may include information classes, semantic categories, or functions for grouping elements. This attribute could identify: the name of a drug, company, or product; systematics terms such as genus, species, or family; or biological systems components, such as gene, protein, or peptide. The attribute could also be used to record that the content of a table cell is a total or subtotal amount, that a sidebar (<boxed-text>) contains a case study, or that a <statement> is a theorem or a proof.
Conversion Note: This attribute can be used to preserve semantic tagging that can’t be captured directly with an element in this Tag Set.
Display/Formatting Note: The presence of a @content-type attribute may be used to treat its element in a
distinct way, for example, giving the word, phrase, or structure a different look in print or on display. This type of formatting may be guided by the value of the attribute, for example, making all circulatory system words (identified by a <named-content> element) red or putting a background image behind case studies.
Historical Note:In the redesign of this Tag Set that led to
NISO JATS, a @content-type attribute was added to more
than 60 elements because “type” attributes are viewed as a useful tool
for preserving Publisher semantics without extending the Tag Set. The attribute was added according
to the following rationale:
- Unless there was a conflicting rule, a @content-type attribute was added.
- Elements that cannot repeat (such as <body> and <title-group>) were not given a @content-type attribute. This includes all the “-meta” elements and most top-level structural elements (such as <front> and <back>).
- Elements that can appear more than once by virtue of being part of a #PCDATA OR-group were given a @content-type attribute.
- Elements that already had a “type” or “style” attribute were not given a second such attribute.
- Elements concerning glyph characters were not given a @content-type attribute.
- EMPTY elements (such as all the counts) were not given a @content-type attribute.
Used on Element: <contrib-group>
| Value | Meaning |
|---|---|
| Text, numbers, or special characters | Names the shared role for the contributors within the <contrib-group> element. |
| Restriction | @content-type is an optional attribute; there is no default. |
Suggested usage
CRediT Best Practice: The @content-type attribute on <contrib-group> was designed to name the role of the contributors in the group and was also designed to accept any text as its value. However, if the @content-type value is to be taken from a controlled vocabulary, such as CRediT, Best Practice is not to name the role using @content-type. Best Practice (when possible) is to tag the CRediT taxonomy of contributor roles by using the <role> element inside the <contrib-group> or inside individual contributors (<contrib>). The major advantages of using the <role> element are the ability to tie the content of the role to the formal vocabulary using the four JATS vocabulary attributes and the ability for a contributor or group to play more than one role in the creation of an article.
Use of the CRediT taxonomy of contributor roles (http://dictionary.casrai.org/Contributor_Roles) with @content-type is encouraged when such use is possible. Additional non-CRediT values such as
“deep sea diver” may also be used. As of this Tag Library Publication, the CRediT roles were:
Conceptualization | Ideas; formulation or evolution of overarching research goals and aims. |
|---|
Used on Element: <role>
| Value | Meaning |
|---|---|
| Text, numbers, or special characters | Names/describes a distinct semantic role of the contributor (person or collaboration) in the research behind the article or the article itself. If the contributor played more than one role in the creation of an article, the <role> element should be repeated with a different value for this attribute. |
| Restriction | @content-type is an optional attribute; there is no default. |
Suggested usage
Best Practice for <role>: Although designed to accept any text as its value, use of the CRediT taxonomy of contributor roles (http://dictionary.casrai.org/Contributor_Roles) with @content-type is encouraged when such use is possible. Additional non-CRediT values such as
“deep sea diver” may also be used. As of this Tag Library Publication, the CRediT roles were:
Conceptualization | Ideas; formulation or evolution of overarching research goals and aims. |
|---|---|
Data curation | Management activities to annotate (produce metadata), scrub data and maintain research data (including software code, where it is necessary for interpreting the data itself) for initial use and later reuse. |
Formal analysis | Application of statistical, mathematical, computational, or other formal techniques to analyze or synthesize study data. |
Funding acquisition | Acquisition of the financial support for the project leading to this publication. |
Investigation | Conducting a research and investigation process, specifically performing the experiments, or data/evidence collection. |
Methodology | Development or design of methodology or protocols; creation of models |
Project administration | Management and coordination responsibility for the research activity planning and execution.
Resources |
Software | Programming, software development; designing computer programs; implementation of the computer code and supporting algorithms; testing of existing code components. |
Supervision | Oversight and leadership responsibility for the research activity planning and execution, including mentorship external to the core team. |
Validation | Verification, whether as a part of the activity or separate, of the overall replication/reproducibility of results/experiments and other research outputs. |
Visualization | Preparation, creation and/or presentation of the published work, specifically visualization/data presentation. |
Writing – original draft | Creation and/or presentation of the published work, specifically writing the initial draft (including substantive translation). |
Writing – review & editing | Preparation, creation and/or presentation of the published work by those from the original research group, specifically critical review, commentary or revision – including pre- or post-publication stages. |
Used on Element: <related-object>
| Value | Meaning |
|---|---|
| Text, numbers, or special characters | May be used to name stages in the lifecycle of a related object such as a book, with values such as “preprint” and “version-of-record”. |
| Restriction | @content-type is an optional attribute; there is no default. |
Used on Element: <named-content>
| Value | Meaning |
|---|---|
| Text, numbers, or special characters | Names/describes the distinct function for the <named-content> that cannot otherwise be described by the elements in this Tag Set. For example, a medical article might use the value “body-system” or “gene” while a management article might use the value “product-name” or “stock-code”. |
| Restriction | @content-type is required; it must be provided if the element is used. |
Used on these Elements:
<abbrev>, <access-date>, <ack>, <addr-line>, <address>, <aff>, <ali:free_to_read>, <ali:license_ref>, <alt-text>, <annotation>, <app>, <app-group>, <article-version>, <author-comment>, <bio>, <boxed-text>, <caption>, <chem-struct>, <chem-struct-wrap>, <city>, <col>, <colgroup>, <comment>, <compound-kwd>, <compound-kwd-part>, <conf-acronym>, <conf-date>, <conf-loc>, <conf-name>, <conf-num>, <conf-sponsor>, <conf-theme>, <conference>, <contrib-id>, <copyright-holder>, <copyright-statement>, <copyright-year>, <country>, <data-title>, <date-in-citation>, <day>, <degrees>, <disp-formula>, <disp-formula-group>, <disp-quote>, <edition>, <elocation-id>, <email>, <era>, <fax>, <fixed-case>, <fn-group>, <fpage>, <glossary>, <gov>, <graphic>, <inline-formula>, <inline-supplementary-material>, <institution>, <institution-id>, <isbn>, <issn>, <issue>, <issue-id>, <issue-part>, <issue-title>, <kwd>, <license-p>, <long-desc>, <lpage>, <media>, <month>, <name>, <nested-kwd>, <object-id>, <p>, <page-range>, <patent>, <phone>, <postal-code>, <prefix>, <price>, <rb>, <ref>, <ref-list>, <rt>, <ruby>, <season>, <self-uri>, <series>, <source>, <speaker>, <speech>, <state>, <statement>, <std>, <std-organization>, <string-name>, <subtitle>, <suffix>, <supplementary-material>, <table>, <table-wrap>, <tbody>, <td>, <tfoot>, <th>, <thead>, <time-stamp>, <title>, <tr>, <trans-source>, <trans-title>, <uri>, <verse-group>, <verse-line>, <version>, <volume>, <volume-id>, <volume-series>, <year>
| Value | Meaning |
|---|---|
| Text, numbers, or special characters | Names/describes any distinct semantics of the associated element. This may be used to preserve the semantic intent of prior tagging, for example, to record that a table cell was a total or subtotal amount. This may also be used to attach information classes to an element for retrieval purposes. |
| Restriction | @content-type is an optional attribute; there is no default. |
Example 1
Used to make a semantic distinction that JATS does not make:
...
<p>Profiling of
<named-content content-type="genus-species">Escherichia
coli</named-content> chromosome (PEC) described in the
Database ...</p>
...
Example 2
Describes the role of each compound keyword part in the compound keyword as a whole:
... <kwd-group kwd-group-type="Inspec-class"> <compound-kwd> <compound-kwd-part content-type="code">B0260</compound-kwd-part> <compound-kwd-part content-type="text">Optimisation techniques</compound-kwd-part> </compound-kwd> ... </kwd-group> ...