<custom-meta-group> Custom Metadata Group
Container element for metadata not otherwise defined in the NISO STS Tag Sets.
Some DTDs and schemas allow for metadata elements above and beyond that which can be specified by this Tag Set. This element can be used as an escape-hatch to record additional metadata that a standards organization wishes to preserve (so that the intellectual work to capture that content will not be lost) even though there is no direct expression for the metadata element in this Tag Set.
The <custom-meta> element allows for an infinite variety of name/value pairs (<meta-name> and <meta-value>), with few constraints on the length or content of the value. This element will probably be used for special cases, product-specific material, or other organization-specific metadata.
The <custom-meta-group> element is repeatable to hold different types of information (production, editorial, conversion, legal, for example), with typing attributes at the group level (@content-type and @specific-use) to distinguish between uses.
When used as part of <processing-meta>, the <custom-meta-group> element is typically, but not exclusively, used for internal processing purposes. Thus this element is more likely than <extended-by>, <restricted-by>, or the <processing-meta> attributes to be used during internal processing and stripped out before interchange.
Such custom metadata might hold information about the XML file (as opposed to the standard encoded by the file) such as:
- Generation or conversion date
- Name of the conversion vendor
- Name of the conversion software and/or its version number
- Initials of the chief proofreader
- Claimed quality level
- An indication that the document had been approved by the legal team
- Created-by (to distinguish among files originating from outsourcing partners, subsidiaries, projects etc. and those originating with the parent organization)
- Released-by (to distinguish between files from the co-authors of a multi-author standard, and keep track of situations where a third party has created an XML version of a standard for their own use, but also given the XML version back to the original SDO to be released by them.)
Models and Context
May be contained in
<!ELEMENT custom-meta-group %custom-meta-group-model; >
Expanded Content Model
Sales numbers and suppliers are not explicit elements in JATS.
... <nat-meta originator="DIN" id="profile.nat"> ... <custom-meta-group> ... <custom-meta> <meta-name>sales.number</meta-name> <meta-value>1454006</meta-value> </custom-meta> <custom-meta> <meta-name>supply</meta-name> <meta-value>Alleinverkauf der Normen durch Beuth Verlag GmbH, 10772 Berlin</meta-value> </custom-meta> ... </custom-meta-group> </nat-meta> ...