ISO/TR 21636-2:2023 Language coding — A framework for language varieties — Part 2: Description of the framework
Technical Committee: ISO/TC 37/SC 2 Terminology workflow and language coding
“This document, and the ISO 21636 series in general, provides the general principles for the identification and description of varieties of individual human languages. It, therefore, does not apply to: artificial means of communication with or between machines such as programming languages; those means of human communication which are not fully or largely equivalent to human language such as individual symbols or gestures that carry isolated meanings but cannot be freely combined into complex expressions. This document together with the other parts of the ISO 21636 series establishes the dimensions of linguistic variation as well as core values necessary to identify individual varieties in these dimensions or sub-dimensions. This document forms the basis for the other parts by outlining the general framework for language varieties.”
ISO 233-3:2023 Information and documentation — Transliteration of Arabic characters into Latin characters — Part 3: Persian language — Transliteration
Technical Committee: ISO/TC 46 Information and documentation
“This document establishes a system for the transliteration of the Arabic characters (often called Perso-Arabic script) used to write in the Persian language into Latin characters. This modification of the stringent rules established by ISO 233:1984 is specifically intended to facilitate the processing of bibliographic information (e.g. catalogues, indices, citations, etc.).”
ISO 8000-51:2023 Data quality — Part 51: Data governance: Exchange of data policy statements
Technical Committee: ISO/IEC JTC 1/SC 38 Cloud computing and distributed platforms
“This document specifies requirements that support the exchange of data governance policy statements and automated conformance testing of data sets to the data specifications referenced by policy statements. The following are within the scope of this document:
requirements for the syntax and semantics of identifiers for organizations issuing data governance policy statements; requirements for the syntax and semantics of identifiers for data governance policy statements; data specifications referenced by data governance policy statements, where those specifications are computer processable. The following are outside the scope of this document: general processes, roles and responsibilities for performing data governance; requirements for the syntax and semantics of data specifications referenced by a data governance policy statement; requirements for the syntax and semantics of data governance policy statements; methods used for the creation of data governance policy statements; methods used for measuring conformance with the requirements referenced by data governance policy statements; methods used for monitoring conformance with the requirements referenced by data governance policy statements.”
Working Group Note: EPUB Type to ARIA Role Authoring Guide 1.1 [W3C]
“The EPUB 3 Working Group has just published the Working Group Note of EPUB Type to ARIA Role Authoring Guide 1.1. This document provides guidance for publishers looking to move from the use of the EPUB 3 epub:type attribute to ARIA roles for accessibility. The epub:type attribute has evolved to aid publisher workflows. It has limited use enabling reading system behaviors outside of some core functionality of EPUB (identifying navigation elements and enhancing media overlay documents). Although it was hoped the attribute would also expose information to assistive technologies, in practice it does not. The primary purpose of the ARIA role attribute, on the other hand, is to expose information to assistive technologies. It is not to facilitate user agent behaviors. This guide addresses key authoring differences to be aware of when migrating to ARIA roles from the epub:type attribute, or when using both attributes together. The goal is to help publishers avoid the pitfalls of applying ARIA roles like they would epub:type semantics and breaking the reading experience for users of assistive technologies.”