<subj-group> Subject Group
Container element for the subject matter descriptors (<subject>) that name the classifications, categories, topics, or themes of the standards document, for example: IPC Codes, UNSPSC Codes, or UNS Codes.
Types of Subjects
This Tag Set contains several differently-structured types of subjects:
- <subject> Used with simple subjects: words or phrases.
- <compound-subject> Used with multi-part subjects, such as a subjects that contains both a code and its expansion/description/name/title.
- <ics> and <ics-wrap> Used to hold ICS codes. The ICS elements were originally part of ISO STS, which did not use other subject groups, so the element <ics> and <ics-wrap> are not inside <subj-group>, but are at the same level as these groupings.
Language in Subjects
A standard may take multiple sets of subject codes, with the @subj-group-type, @specific-use, or @xml:lang attributes used to discriminate between them. The <subject> element does not take the @xml:lang attribute; that is reserved for the <subj-group>. This means that subjects must be sorted by language and entered in language groups.
For controlled vocabularies, two attributes can be used to link a subject group to its source:
- @vocab — This attribute holds the name of a controlled or generic vocabulary, taxonomy, ontology, database, thesaurus, etc. that is the source of the subject terms in the group, for example, “ipc”, “unspsc”, or “uns”. In cases where there is no named vocabulary, the @vocab attribute should be set to “uncontrolled”.
- @vocab-identifier — This attribute holds a unique identifier and possibly a pointer to the named vocabulary, typically a URI or DOI reference.
Vocabulary Attributes Best Practice
If the subject terms in <subj-group> come from a controlled vocabulary, taxonomy, ontology, database, term list, or similar formally defined term source, the @vocab attribute (and if possible, the @vocab-identifier attribute) should be used on the <subj-group> element to name the source. If there is a subject-term-specific identifier in this source of terms, then also use the @vocab-term and @vocab-term-identifier on the subject term (<subject>), if possible.
If the subject terms come from, or are specific to, a field of study that can be named (particularly where different fields might define the same term differently), name the field of study in the @subj-group-type attribute (“structural engineering”, “mechanical engineering”, “bird watching”). Such terms are typically, but not always, informally defined.
Although subject terms may be from an uncontrolled vocabulary, this is less likely than for terms such as keywords, since subject codes such as IPC, UNSPSC, UNS, etc. are controlled by defined vocabularies. If the subject terms are uncontrolled, either omit the @vocab attribute on <subj-group> or use the value “uncontrolled”.
Subject Group Type Attribute
The @subj-group-type attribute most commonly names an uncontrolled vocabulary source of the subject terms, such as “chemical engineering”, “author-generated”, or “working-group-generated”. But @subj-group-type has also been used to record the type of subject terms, for example, “hierarchical” for subjects that are grouped into a hierarchy, “abbreviations” for subjects that contain an abbreviation and its expansion, or “code” for subjects that contain a code and its text but where the source of the codes is unknown.
Older documents, coded before NISO STS added the vocabulary attributes, may have used @subj-group-type to name the vocabulary source. Going forward, this is information to be recorded in the vocabulary attributes.
Models and Context
<!ELEMENT subj-group %subj-group-model; >
Expanded Content Model
((subject | compound-subject)+, subj-group*)
UNSPSC codes with their descriptions given using <compound-subject>
... <subj-group vocab="UNSPSC"> <compound-subject> <compound-subject-part content-type="code">30102204</compound-subject-part> <compound-subject-part content-type="value">Steel Plate</compound-subject-part> </compound-subject> </subj-group> ...
... <subj-group vocab="ipc"> <compound-subject> <compound-subject-part content-type="code">B82B1/00</compound-subject-part> <compound-subject-part content-type="value">Nano structures</compound-subject-part> </compound-subject> <compound-subject> <compound-subject-part content-type="code">H01L21/02</compound-subject-part> <compound-subject-part content-type="value">Manufacture or treatment of semiconductor devices or of parts thereof</compound-subject-part> </compound-subject> </subj-group> ...
Subjects showing named vocabulary that has sub-vocabularies which are also fields of study, so both @vocab and @subj-group-type attributes are used
... <subj-group id="SG1.1" originator="ASME" vocab="ASME-Taxonomy" xml:lang="en" subj-group-type="Industries" vocab-identifier="http:/www.asme.org/ASME-Taxonomy/Industries/"> <subject id="SG1.1-1" vocab-term-identifier="http:/www.asme.org/ASME-Taxonomy/Industries/fossil-power" >Fossil Power</subject> <subject id="SG1.1-2" vocab-term-identifier="http:/www.asme.org/ASME-Taxonomy/Industries/power-plants" >Power Plants</subject> </subj-group> <subj-group id="SG1.2" originator="ASME" vocab="ASME-Taxonomy" xml:lang="en" subj-group-type="Materials-Product-Form" vocab-identifier="http:/www.asme.org/ASME-Taxonomy/Materials-Product-Form/"> <subject id="SG1.2-1" vocab-term-identifier="http:/www.asme.org/ASME-Taxonomy/Materials-Product-Form/piping" >Piping</subject> <subject id="SG1.2-2" vocab-term-identifier="http:/www.asme.org/ASME-Taxonomy/Materials-Product-Form/pressure-vessels" >Pressure Vessels</subject> </subj-group> ...
Subject from Dewey Decimal showing canonical term in @vocab-term attribute and its translation in subject content (Note “Engineering of railroads, roads” is DDC term, not free text.)
... <subj-group id="DDC-ex1" vocab="DDC" vocab-identifier="DDC23" xml:lang="en"> <subject id="DCC-625" vocab-term="Engineering of railroads, roads" vocab-term-identifier="http://www.oclc.org/en/dewey/features/summaries.html#thou"> Ingénierie des chemins de fer, routes</subject> </subj-group> ...