IDT - Information, documentation, language and terminology

This document specifies the structure of an ontology for a fine-grained description of the expressive power of corpus query languages (CQLs) in terms of search needs. The ontology consists of three interrelated taxonomies of concepts: the CQLF metamodel (a formalization of ISOÂ 24623-1); the expressive power taxonomy, which describes different facets of the expressive power of CQLs; and a taxonomy of CQLs.
This document specifies:
a) the taxonomy of the CQLF metamodel;
b) the topmost layer of the expressive power taxonomy (whose concepts are called “functionalities”);
c) the structure of the layers of the expressive power taxonomy and the relationships between them, in the form of subsumption assertions;
d) the formalization of the linkage between the CQL taxonomy and the expressive power taxonomy, in the form of positive and negative conformance statements.
This document does not define the entire contents of the ontology (see Clause 4).

This document provides requirements and recommendations for representing subject fields and concept relations in TBX-compliant terminological document instances. Examples in this document utilize the DCA style of TBX markup.

This document specifies requirements and recommendations related to fundamentals of translation-oriented terminography for producing sound bilingual or multilingual terminology collections. It deals with the main tasks, skills, processes and technologies for translation-oriented terminography practiced by terminology workers who do terminology work in low-complexity settings as part of non-terminological activities. It does not cover terminology management involving sophisticated workflows, a multitude of roles, or advanced terminological skills and competences.

This document establishes a framework for defining metadata elements consistent with the principles and implementation considerations outlined in ISOÂ 23081-1. The purpose of this framework is to:
a) enable standardized description of records and critical contextual entities for records;
b) provide common understanding of fixed points of aggregation to enable interoperability of records and information relevant to records between organizational systems; and
c) enable reuse and standardization of metadata for managing records over time, space and across applications.
It further identifies some of the critical decision points that need to be addressed and documented to enable implementation of metadata for managing records. It aims to:
—   identify the issues that need to be addressed in implementing metadata for managing records;
—   identify and explain the various options for addressing the issues; and
—   identify various paths for making decisions and choosing options in implementing metadata for managing records.

This document covers the measurable or magnitudinal aspect of quantity so that it can focus on the technical or practical use of measurements in IR (information retrieval), QA (question answering), TS (text summarization), and other NLP (natural language processing) applications. It is applicable to the domains of technology that carry more applicational relevance than some theoretical issues found in the ordinary use of language.
NOTEÂ Â Â Â Â Â ISO 24617-12 deals with more general and theoretical issues of quantification and quantitative information.
This document also treats temporal durations that are discussed in ISO 24617-1, and spatial measures such as distances that are treated ISO 24617-7, while making them interoperable with other measure types. It also accommodates the treatment of measures or amounts that are introduced in ISO 24617‑6:2016, 8.3.

This document describes a set of principles, guidelines, and requirements for the preparation of bibliographic references and citations in works that are not themselves primarily bibliographical. It is applicable to bibliographic references and citations for all kinds of information resources, including but not limited to monographs, serials, contributions within monographs and serials, patents, cartographic materials, artworks, performances and diverse electronic resources, such as research datasets, databases, programs and applications, Web archives and social media, music, recorded sound, prints, photographs, graphic and audio-visual materials, archival sources and moving images.
This document provides a system for citing information resources that renders deterministic output, such that a citation generated by this system can be uniquely mapped back to the originally defined set of source elements. This system is intended to be applicable across multiple languages. Citations generated by this system are machine-parseable. The citation system described in this document can be used as a configurable framework for building citation styles.
This document does not specify a data model for machine‑readable citations, although such specification may be provided in a separate document or added to a later edition of ISO 690.
Guidelines for legal citations, such as references to cases, statutes or treatises, are not addressed in this document, since such guidelines are usually country-specific1. Recommendations with regards to what kind of information resources may or may not be cited, or describing the risks involved with, for example, citing social media, are not within the scope of this document2.
  
1 For example, the ALWD Guide to Legal Citation, and Bluebook, are commonly used in the USA depending on jurisdiction acceptance.
2 Academic institutions or scientific publishers may not accept references for some information resources such as Wikipedia articles for research papers and other scientific documents.

This document specifies guidelines for the archives community on the collection and reporting of statistics for the following purposes:
—   strategic planning and internal management of archives;
—   aggregating and comparing operational and performance statistics at regional, national, and international levels;
—   reporting to stakeholders such as funding institutions, politicians, researchers, and the general public;
—   promoting the role and value of archives for advancing learning and research, education and culture, and social and economic life;
—   improving the management of processes, reinforcing transparency and supporting good governance.
This document does not apply to records centres responsible for records that are still in the legal custody of the organization that created or received them, although it is recognized that some archives also have responsibilities for appraising, acquiring, and managing the current records of organizations that can or not be transferred to the archives for permanent retention. When applying this document to archives that also perform records management functions, the archives can exclude statistics that pertain to its records management functions, including measures pertaining to holdings and their usage and preservation, funding and expenditures, space and facilities, staffing and management.

This document describes an extension to ISO 24613-1 and ISO 24613-2 to support the development of detailed descriptions of common etymological phenomena and/or diachronic information with respect to lexical entries in born-digital and/or retro-digitized lexicons. It provides both a meta-model for such an extension as well as the relevant data categories.

This document specifies requirements for typical conference systems, the parts they are composed of, the auxiliary devices necessary for their use (such as microphones, headphones, and sound reinforcement equipment) and the environment in which they are used. These requirements ensure interoperability and optimum performance under conditions of normal operation.
It is applicable to both wired and wireless systems.
The environment and areas where events are held are described in Annex A.
This document facilitates the determination of the quality of conference systems, the comparison of different systems and the assessment of their proper use by listing their characteristics. This document contains the technical backbone of ISO 20108 and ISO 20109.

This document provides a set of empirically and theoretically well-motivated concepts for dialogue annotation, a formal language for expressing dialogue annotations (the Dialogue Act Markup Language, DiAML), and a method for segmenting a dialogue into semantic units. This allows the manual or automatic annotation of dialogue segments with information about the communicative actions which the participants perform by their contributions to the dialogue. The annotation scheme specified in this document supports multidimensional annotation of spoken, written, and multimodal dialogues involving two or more participants. Dialogue units are viewed as having multiple communicative functions in different dimensions. The markup language DiAML has an XML-based representation format and a formal semantics which makes it possible to perform inferences with DiAML representations. This document also specifies data categories for dimensions of dialogue analysis, for communicative functions, for dialogue act qualifiers, and for relations between dialogue acts. Additionally, it provides mechanisms for customizing these sets of concepts, extending them with application-specific or domain-specific concepts and descriptions of semantic content, or selecting relevant coherent subsets of them. These mechanisms make the dialogue act concepts specified in this document useful not only for annotation but also for the recognition and generation of dialogue acts in interactive systems.

This document specifies how to represent (not visualize) documents (instance data, not data schemas) as graphs. It does not specify how to visualize or operate on document data, but it aims at making documents easier for people to compose and comprehend by allowing for various graph-based flexible user interfaces, possibly incorporating document-visualization practices (see Introduction). In this connection, this document does not specify annotations to existing documents either, but rather it specifies a schema of documents with explicit logical structures.

This document provides basic principles and a methodology for establishing a specification for designing and constructing a formally defined, or controlled, system of oral communication that avoids or filters out phonetic interferences and confusions between words of the same language and between languages. The system is both abstracted from, and contextually situated in, the domains of industry, business or other technologies.
This document deals only with oral communication between native speakers, or non-native speakers, or a native speaker and a non‑native speaker, who can be disturbed due to different phenomena, such as phoneme confusion, phonetic interferences and confusions between words (for example: homophony, quasi-homophony or co-articulation) of the same language and/or different languages and the resulting ambiguities due, for example, to multilingual communication or stressful situations. This document deals with speakers and listeners without speech or hearing impediments[16], and does not include sign languages which have a phonological system equivalent to the system of sounds in spoken languages[23].
Foreseen applications are essentially in safety critical applications using human oral communication. This document is also applicable to other domains involving, for example, training and evaluation procedures and robots.

This document specifies requirements and recommendations for healthcare interpreting services in spoken and signed communication. It is applicable to all situations requiring healthcare interpreting, where the parties involved need to communicate using spoken or signed language, to treat a health-related issue. It is intended for interpreting service providers and healthcare interpreters.

This document describes the serialization of the lexical markup framework (LMF) model defined as an XML model compliant with the Text Encoding Initiative (TEI) Guidelines. This serialization covers the classes of ISO 24613-1 (the LMF core model) as well as classes provided by ISO 24613-2 (the machine readable dictionary, MRD, model) and ISO 24613-3 (the etymological extension).

This document describes the machine-readable dictionary (MRD) model, a metamodel for representing data stored in a variety of electronic dictionary subtypes, ranging from direct support for human translators to support for machine processing.

This document provides a framework for encoding a broad range of spatial information and spatiotemporal information relating to motion as expressed in natural language texts. This document includes references to locations, general spatial entities, spatial relations (involving topological, orientational, and metric values), dimensional information, motion events, paths, and event-paths triggered by motions.

This document specifies requirements for the competences and qualifications of legal translators, revisers and reviewers, best translation practices and the translation process directly affecting the quality and delivery of legal translation services. In particular, it specifies the core processes, resources, confidentiality, professional development requirements, training and other aspects of the legal translation service provided by individual translators.
Fulfilment of all the requirements set out in this document enables the individual legal translator to demonstrate conformity of their legal translation services to this document and their capability to maintain a level of quality in legal translation services that will meet the client's and other applicable specifications.
The use of output from machine translation, even with post-editing, is outside the scope of this document. Consulting of a machine translation resource by a legal translator, does not constitute use of raw machine translation plus post-editing.
This document does not apply to interpreting services.

This document provides a comprehensive model for the annotation and representation of referential phenomena in natural language texts and multimodal interactions. Such phenomena can cover simple anaphoric or coreferential mechanisms as well as more complex bridging or multimodal mechanisms. It provides a reference serialisation in XML defined as a customisation of the TEI P5 guidelines. In addition, the document describes the core data categories related to referential entities and link structures, and also needed for the description of annotation schemes and serialisation mechanisms for implementing conformant models as concrete data formats.

This document contains terms and definitions that are relevant to the core concepts of the records management domain. It does not limit the definition of new terms in ISO/TC 46/SC 11 standards.

This document provides policy makers in governments, administration, non-profit and profit organizations with guidelines and a methodology for the development and implementation of a comprehensive policy concerning the planning and management of terminology.
This document defines key concepts and describes scenarios and environments that can require different kinds of terminology policies. It also places terminology policies in the broader context of institutional strategic frameworks.

This document specifies essential features of terminology management systems, regardless of specific software engineering paradigms, user interface and user assistance design principles, and specific data models. These features enable maximum efficiency and quality in terminology work and, thus, support creating, processing, and using high quality terminology. The intended audiences of this document are software engineers/developers as well as terminologists, technical communicators, translators, interpreters, language planners, and subject field experts.
This document describes all features needed for recording, editing, maintaining, exchanging, and presenting terminological data. Term extraction features used to identify new terms are out of the scope of this document.

This document describes a test method for conservation materials which can evaluate their impact on cellulose as the main constituent of paper-based collections caused by emission of their volatile compounds.
NOTE This test can be extended to museum artefacts.
This document is applicable to papers and boards used for conservation and storage of cellulose based items.  
It is not applicable to parchment-based items.
It does not evaluate the effects due to direct contact between the papers and boards used for conservation and the collections.

This document establishes basic terms and definitions for terminology work and terminology science. It does not include terms and definitions that are specific to computer applications in terminology work.

This document specifies general, i.e. implementation- and use-case-independent terminology database design principles to enable maximum efficiency and quality in terminology work. Thus, this document supports creating, processing, and using high quality terminology. The intended audiences of this document are terminologists, translators, interpreters, technical communicators, language planners, subject field experts, and terminology management system developers.
This document describes a maximum approach, i.e. terminology database design for distributed, multilingual terminology management. It can also be used for designing smaller solutions.

The component metadata lifecycle needs a comprehensive infrastructure with systems that cooperate well together. To enable this level of cooperation this document provides in depth descriptions and definitions of what CMDI records, components and their representations in XML look like.
This document describes these XML representations, which enable the flexible construction of interoperable metadata schemas suitable for, but not limited to, describing language resources. The metadata schemas based on these representations can be used to describe resources at different levels of granularity (e.g. descriptions on the collection level or on the level of individual resources).

This document presents a model for cloud records management and outlines the risks and issues that are considered by records managers before adopting cloud services for records management. The model for cloud records management includes a stakeholder model, processes, metadata, architecture, and use cases. Risks and issues are classified into those originating from cloud services internally and those originating from cloud services externally. Internal risks are associated with cloud services, systems and stakeholders. External risks and issues can occur in the social and legal context in which cloud services operate.
The target audience of this document includes:  
— records, information, knowledge, and governance professionals;  
— cloud service architects;  
— archivists using cloud services for managing records;  
— developers of cloud-deployed records management software;  
— ICT staff; and  
— providers of cloud-based records management services.

This document provides an effective presentation of rights information in digital collections to end-users. Digital collection, in this document, is mainly focused on digital collections in libraries, museums, archives or other organizations that offer similar resources to their patrons.
This document deals with the human-readable aspects of the rights presentation. Technical aspects of the storage and management of rights expression information, such as, metadata schemas, interoperability of machine-readable expressions and user interfaces are out of scope of this document.

This document provides the vocabulary for translation, interpreting and related technology standards.

This document specifies the International Standard identifier for libraries and related organizations (ISIL), which comprises a set of standard identifiers used for the unique identification of libraries and related organizations such as museums and archives with a minimum impact on already existing systems.
An ISIL identifies an organization, i.e. a library or a related organization, or one of its subordinate units, which is responsible for an action or service in an informational environment (e.g. creation of machine-readable information). It can be used to identify the originator or holder of a resource (e.g. library material or a collection in an archive). The ISIL is intended for use by libraries and related organizations such as museums and archives and agencies doing business or interacting with these organizations (e.g. suppliers, publishers, and government institutions). An ISIL identifies an organization or one of its subordinate units throughout its life. In some cases, such as when an organization has undergone a significant administrative change (e.g. a merger with another organization), particularly one that results in a name change, a new ISIL can be allocated.
Since this document allows the use of existing codes to be incorporated into the ISIL, it is possible that a given organization can have more than one ISIL. However, it is the intention of this document to minimize the number of codes.
Any library or related organization, administrative unit or subordinate unit, acting autonomously, can be allocated an ISIL.
An ISIL is not intended to be used to classify organizations or their services and holdings.

This document specifies a set of key indicators for assessing the quality of museums:
— for the purpose of strategic planning and internal management of museums;
— for reporting to stakeholders such as funding institutions, policy makers, or the public;
— to promote the museums' role and value for learning and research, education and culture, social and economic life;
— for comparing results over time and between museums.
The aim of this document is to provide a selection of key indicators applicable to a wide range of museums. It is recognized that not all indicators are pertinent for each individual museum category or each individual museum. Limitations on the applicability of individual indicators are listed in the scope clause of the description of each indicator (see Annex A).
This document is not intended to exclude the use of other indicators not specified in it.

This document describes the orthographic system of the Akson-Thai-Noi script using Romanized characters.
This document can be used by anyone who has a clear understanding of the system and is certain that it can be applied without ambiguity. The result obtained will not give a correct pronunciation of the original text in a person's own language, but it will serve as a means of finding automatically the original graphism and thus allow anyone who has a knowledge of the original language to pronounce it correctly.
NOTE Similarly, one can only pronounce correctly a text written in, for example, English or Polish, if one has a knowledge of English or Polish.

This document provides guidance for decision making and processes associated with the selection, design, implementation and maintenance of software for managing records, according to the principles specified in ISO 15489-1.
This document is applicable to any kind of records system supported by software, including paper records managed by software, but is particularly focused on software for managing digital records.
This document provides guidance to records professionals charged with, or supporting the selection, design, implementation and maintenance of systems for managing records using a variety of software. It can also provide assistance to information technology professionals such as solution architects/designers, IT procurement decision makers, business analysts, business owners and software developers and testers seeking to understand records requirements.

This document provides model, high-level functional requirements and associated guidance for software applications that are intended to manage digital records (including digital copies of analogue source records), either as the main purpose of the application or as a part of an application that is primarily intended to enable other business functions and processes.
It does not include:
— functional requirements for applications that manage analogue records;
— generic design requirements such as reporting, application administration and performance;
— requirements for the long-term preservation of digital records in a dedicated preservation environment;
NOTE The model requirements are intended to encourage the deployment of applications that do not hinder long-term preservation of records. As such, some of the requirements support long-term digital preservation outcomes.
— implementation guidance for applications that manages analogue and/or digital records. Such guidance can be found in ISO/TS 16175-2:—[1].
[1] Under development. Stage at the time of publication: ISO/DTS 16175-2:2020.

This document defines and promotes the use of a standard code (ISSN) for the unique identification of serials and other continuing resources.
Each International Standard Serial Number (ISSN) is a unique identifier for a serial or other continuing resource in a defined medium whether print or electronic.
This document also allows for grouping related continuing resources into clusters identified by a separately-prefixed ISSN as defined in this document.
ISSNs are applicable to serials and to other continuing resources, whatever the business model or modes of distribution (e.g. free, open access, on subscription, etc.) and irrespective of whether the serial is currently in publication, has ceased publication, or publication is planned for the foreseeable future. Continuing resources include whatever the medium of production (print or electronic):
— serials, such as newspapers, periodicals, journals, magazines, conference proceedings, monographic series with no predetermined conclusion, annual or other periodic reports, and
— ongoing integrating resources that are updated, such as loose-leaf publications, updating websites, blogs, institutional repositories, directories and databases.
Monographs, sound and video recordings, notated music publications, audiovisual works, textual works and musical works have their own standard identifiers and are not specifically mentioned in this document. Such items can carry an ISSN in addition to their appropriate identifiers when they are part of a continuing resource.
NOTE This document does not contain any operational guidance for its practical implementation.

This document establishes a vocabulary for cross-domain resource description, known as the Dublin Core metadata terms (hereafter DCMI Metadata Terms). It includes all of the properties and classes in the main namespace of DCMI Metadata Terms[1] (hereafter "the /terms/ namespace"), as published in the DCMI Recommendation document "DCMI Metadata Terms" of 2012 (DCMI-TERMS and Annex A). As explained in Annex B, these properties and classes can be identified by URIs for use in linked data.
NOTE The 15 terms of the original Dublin Core Metadata Element Set, as defined in the namespace https://purl.org/dc/elements/1.1/ (hereafter "the /elements/1.1/ namespace"), are also documented in the DCMI Recommendation "DCMI Metadata Terms" and in ISO 15836-1.
This document does not contain the following supporting terms from "DCMI Metadata Terms" specification:
a) terms from the /elements/1.1/ namespace (included in ISO 15836-1);
b) vocabulary encoding schemes;
c) syntax encoding schemes;
d) DCMI Type vocabulary;
e) terms related to the DCMI Abstract Model.
Both ISO 15836-1 and this document include the 15 so-called core terms, but in ISO 15836-1 they are from the /elements/1.1/ namespace, and in this document from the /terms/ namespace. In the latter, the terms have narrower semantics due to formal domain and range specifications.
This document does not limit what might be a resource.
This document does not provide specific implementation guidelines. The properties and classes are typically used in the context of an application profile, which constrains or specifies their use in accordance with local or community-based requirements and policies.
[1] Available at: https://purl.org/dc/terms/.

This document provides guidance on how to carry out appraisal for managing records. It describes some of the products and outcomes that can be delivered using the results of appraisal. As such, this document describes a practical application of the concept of appraisal outlined in ISO 15489-1.
This document:
a) lists some of the main purposes for appraisal;
b) describes the importance of establishing scope for appraisal;
c) explains how to analyse business functions and develop an understanding of their context;
d) explains how to identify records requirements;
e) describes the relationships between records requirements, business functions and work processes;
f) explains how to use risk assessment for making decisions related to records;
g) lists options for documenting the results of appraisal;
h) describes possible uses for the results of appraisal; and
i) explains the importance of monitoring and review of the execution of appraisal decisions.
This document can be used by all organizations regardless of size, nature of their business activities, or the complexity of their functions and structure.

This document provides a context for emergency planning, response and recovery for all types of an archive, library or museum collections in light of other existing plans. It provides responders and other stakeholders with an outline for planning, responding and recovering. This document does not address the causes of a critical event, but the consequences and wider impacts. This document outlines a cycle for developing, exercising and reviewing a plan, and how to present a plan. It aims to encourage responders to develop their capabilities in emergency preparedness and touches on some elements of response and recovery, where relevant, by highlighting indicators of good practice.
It is not intended to be an operations manual as there is no single approach that meets the needs of every site, nor is there one single set of organizational arrangements that is appropriate to each and every type of emergency.

This document specifies basic guidelines for the implementation and maintenance of codes for formerly used names of countries.
This code is intended to represent non-current country names, i.e. the country names deleted from ISO 3166 since its first publication in 1974.

This document specifies basic guidelines for the implementation and maintenance of country subdivision codes.  
This code is intended for use in any application requiring the expression of current country subdivision names in coded form.

This document specifies basic guidelines for the implementation and maintenance of country codes.
This code is intended for use in any application requiring the expression of current country names in
coded form.

This document specifies a data model and encoding rules for the use of radio frequency identification
(RFID) tags for items appropriate for the needs of all types of libraries (including national, academic,
public, corporate, special, and school libraries). The rules for encoding a subset of data elements taken
from the total set of data elements defined in ISO 28560-1 are based on ISO/IEC 15962, which uses an
object identifier structure to identify data elements.
This document defines the technical characteristics required to encode the data elements defined in
ISO 28560-1 in accordance with ISO/IEC 15962. These subsets of data elements can be different on
different items in the same library. The encoding rules also enable the optional data to be organized on
the RFID tag in any sequence. In addition, the encoding rules provide for flexible encoding of variable
length and variable format data.
This document provides essential standards-based information about RFID in libraries. A source of
additional information about implementation issues is provided in Annex A.

This document provides guidelines and requirements governing data category specifications for
language resources. It specifies mechanisms for creating, documenting, harmonizing and maintaining
data category specifications in a data category repository. It also describes the structure and content of
data category specifications. The intended audience of this document is researchers and practitioners
in fields of language resource management who use data categories and data category specifications.

This document establishes the minimum characteristics required for the presentation and identification of periodicals including not only the obvious traditional elements that print periodicals typically display (e.g. title, ISSN, publisher, date), but also the “footprints” of periodicals published on digital dynamic media that enable them to be traced along the path of their history, such as changes of URL and publisher or content provider. Furthermore, this document provides information about persistent identifiers, using ISSN, and citation of periodicals (especially when published online or digitized and when titles have changed). It also makes specific recommendations for presentation and identification aspects of retrospective digitization of periodicals.
This document is applicable to a subcategory of continuing resources identifiable as “periodicals” (see Clause 3).
NOTE 1 For the purposes of this document, newspapers are not considered to be periodicals; therefore, specialized information relevant only to newspapers is not included.
This document does not specifically address or apply to books, including series of books, nor to content that is continuously updated such as loose-leaf services, databases, online reference works, and most websites.
NOTE 2 For information about series titles, see ISO 7275.
This document focuses only on elements of periodicals — printed, born-digital or retrospectively digitized — that relate to the presentation of title and supporting descriptive information, as well as
practices related to title identification and content access over time. Therefore, this document is not
concerned with the overall design of the periodical, except where that design affects the presentation
of the title and has unintended consequences for resource discovery and access to earlier content.
Neither is it concerned with the technical specifications for print, born-digital or digitized periodicals.
The recommendations might not apply in all circumstances, and do not always accommodate certain artistic, technical or advertising considerations.
This document contains recommendations intended to enable editors and publishers of periodicals
to identify and present key information in a form that will help users discover, cite and access their
information over time and through any changes. This benefits all stakeholders of the periodical supply chain: publishers, content providers, authors, librarians, and researchers.
The recommendations address the following:
— display of periodical title(s) and other critical identifying information: issues, numbering systems,
pagination, etc.;
— retention of title and citation information under which articles were originally published;
— display of title histories, i.e. changes in titles over time together with their dates of coverage;
— specification of appropriate metadata for digital periodicals;
NOTE 3 This document concentrates on metadata elements which are applicable at the title-level and does not provide guidelines for complete article-level metadata.
— display of correct ISSN, including different ISSN for each format, language edition, and for
changed titles;
— retention and display of vital publication information across the duration of a periodical, including:
publisher names, numbering and dates, editors, editorial boards, and sponsoring organizations, and frequency of publication;
— graphic design that supports clarity and consistency of information, particularly title information and inclusion of information that allows easy access to all content;
— special considerations for retrospective digitization;
— usage of persistent identifiers for identification of periodical titles and articles;
— long-term preservation of periodical information across time.

This document specifies requirements to be met by a management system for records (MSR) in order
to support an organization in the achievement of its mandate, mission, strategy and goals. It addresses
the development and implementation of a records policy and objectives and gives information on
measuring and monitoring performance.
An MSR can be established by an organization or across organizations that share business activities.
Throughout this document, the term “organization” is not limited to one organization but also includes
other organizational structures.
This document is applicable to any organization that wishes to:
— establish, implement, maintain and improve an MSR to support its business;
— ensure itself of conformity with its stated records policy;
— demonstrate conformity with this document by
a) undertaking a self-assessment and self-declaration, or
b) seeking confirmation of its self-declaration by a party external to the organization, or
c) seeking certification of its MSR by an external party.

This document defines terms for the quality assessment of national libraries and specifies the following
methods for the assessment:
— performance measurement, and
— impact assessment.
The results of both methods are of special interest for comparison over time within the same library.
Comparisons between libraries are possible if differences in the mandate, tasks and constituencies of
the libraries are taken into account.
Not all methods described in this document apply to all national libraries. Limitations of the applicability
of individual methods are specified in the descriptions.
This document is not intended to exclude the use of performance indicators or of methods for impact
assessment not specified in it.
This document does not cover web archiving, but refers to ISO/TR 14873 for statistics and quality
issues for this new task of national libraries.

This document explains fundamental concepts and describes the metamodel, data categories, and
XML styles: DCA (Data Category as Attribute) and DCT (Data Category as Tag). It also specifies the
methodology for defining TBX dialects.
The audience for this document is anyone wishing to create a new dialect compliant with TBX. This
document can also be used to analyze and to understand a terminological data collection or to design a
new terminology database that complies with international standards and best practices. Typical users
are programmers, software developers, terminologists, analysts, and other language professionals.
Intended application areas include translation and authoring.
The TBX-Core dialect is described in detail in this document. All other industry-supported dialects are
out of the scope of this document.
NOTE TBX dialects are defined by industry stakeholders. Any materials needed to implement currently
shared dialects are publicly available as self-contained industry specifications (see for instance the TBX Info
website[15]).

The document creates a common language that embeds records management concerns and
requirements into enterprise architecture with the twin goals of building consensus
— among records managers, enterprise architects and solution architects, and
— across the domains of records management, enterprise architecture and solution architecture.
NOTE This common understanding of Records Management enables Enterprise Architects to understand the
motivations, concerns and goals of Records Managers, recognize them as influential key business stakeholders
during organizational transformation, and use this understanding to influence systems planning and design. As a
result, Records Management becomes an organizational capability at governance, strategic and operational levels.
This document provides a records management viewpoint, with architecture principles and
corresponding architectural views of records. It explains records management for enterprise
architects and other related professionals, so that they can achieve the competency needed to support
collaborative initiatives.
This document provides support to enterprise architects in areas including:
— understanding and identifying records management principles, goals and requirements significant
for the architectural representation,
— facilitating consultations with records managers during the project lifecycle,
— identifying opportunities to reuse existing records management analyses and tools.
This document provides scenarios and models for solution architects and those who have responsibility
for infrastructure overview.
This document also provides a common language to records managers for collaboration with enterprise
architects to position records management requirements in the architecture development process.