PublishingLanguage
RIXML 2.5 Element
A specific language in which an organization publishes research with some frequency and fluency.
Specification Guide
Overview
PublishingLanguage declares an individual language in which a research-publishing organization regularly produces content with demonstrated fluency and frequency. It is a leaf element whose meaning is carried entirely by its mandatory publishingLanguage attribute, which uses an ISO 639 language code. Each instance represents one distinct language capability of the publisher, and multiple instances together describe the full set of languages the organization actively supports (sources: data-dictionary-2.4 p.30, release-notes-2.4 p.18, data-dictionary-v3-draft p.80).
Usage
PublishingLanguage appears as a required child of the PublishingLanguages container (renamed PublishingLanguageList in the v3 draft), with cardinality 1..n so that multilingual organizations can list every language they publish in (sources: release-notes-2.4 p.18, data-dictionary-v3-draft p.80).
The publishingLanguage attribute is mandatory on every instance and must be populated with an ISO 639-2/T three-letter language code in 2.x (the v3 draft generalises this to the ISO639LanguageType). Typical placement is within an organization's expertise/profile section, where consumers use it to filter and route research by linguistic audience (sources: data-dictionary-2.4 p.30, example-company-advanced-2.4, example-rosterupdates-2.4).
Rules
- MUSTPublishingLanguage MUST carry the publishingLanguage attribute populated with a valid ISO 639 language code (ISO 639-2/T in RIXML 2.x; ISO 639 more generally in the v3 draft).[RIXML Research Data Dictionary v2.4 p.30] [RIXML Release Notes v2.4 p.18] [RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.80]↗
- MUSTWhen PublishingLanguages (or
PublishingLanguageListin v3) is present, it MUST contain at least one PublishingLanguage child; multiple instances MAY be used to declare additional languages.[RIXML Release Notes v2.4 p.18] [RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.80]↗ - SHOULDEach PublishingLanguage SHOULD represent a language in which the organization publishes with demonstrated frequency and professional fluency, rather than an occasional or ad hoc translation.[RIXML Research Data Dictionary v2.4 p.30] [RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.80]↗
Relationships
- child-ofPublishingLanguages — PublishingLanguage is a required child of the PublishingLanguages container, which aggregates one or more language capabilities for an organization.
- requiresPublishingLanguage.publishingLanguage — PublishingLanguage requires the publishingLanguage attribute to identify the language using a standardized ISO 639 code.
- qualifiesExpertise — Used as part of an organization's expertise profile to describe linguistic publishing capability alongside other Expertise dimensions.
Where It Fits
Canonical Path
Definition
| Type | |
| Namespace | http://www.rixml.org/2017/9/RIXML |
| Min Occurs | 1 |
| Max Occurs | 1 |
Attributes
Restricted by ISO 639-2/T standard. requiredSince 2.4 |
Children
No child elements defined
Example
<PublishingLanguage publishingLanguage="eng" />Version History
Unchanged since introduction in RIXML 2.4
Present in RIXML 2.4 as a required child of PublishingLanguages with the mandatory publishingLanguage attribute typed as ISO639-2LanguageType (three-letter codes from ISO 639-2/T) (sources: data-dictionary-2.4 p.30, release-notes-2.4 p.18).
In the v3 draft the parent container is renamed from PublishingLanguages to PublishingLanguageList and the language attribute is generalised to ISO639LanguageType, broadening the accepted ISO 639 variants while retaining the same semantic role [data-dictionary-v3-draft p.80].