What You'll Want to Know!
ISO 26162-1:2019 Management of terminology resources — Terminology databases — Part 1: Design and Part 2: Software
Technical Committee: ISO/TC 37/SC 3 Management of terminology resources
“Part 1 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. Part 2 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 these documents are software engineers/developers as well as terminologists, technical communicators, translators, interpreters, language planners, and subject field experts.”
ISO/IEC TS 11179-30:2019 Information technology — Metadata registries (MDR) — Part 30: Basic attributes of metadata
Technical Committee: ISO/IEC JTC 1/SC 32 Data management and interchange
“This document specifies basic attributes which are required to describe data elements and associated metadata, and which might be used in situations where a complete ISO/IEC 11179-3 metadata registry is not appropriate (e.g. in the specification of other International Standards).”
ISO/TS 9241-126:2019 Ergonomics of human-system interaction — Part 126: Guidance on the presentation of auditory information
Technical Committee: ISO/TC 159/SC 4 Ergonomics of human-system interaction
“This document provides guidance for the auditory presentation of information controlled by software, irrespective of the device. It includes specific properties such as the syntactic or semantic aspects of information, e.g. coding techniques, and gives provisions for the organization of information taking account of human perception and memory capabilities. This document does not address the hardware issues of the transmission and the production of auditory information. This document can be utilized throughout the design process (e.g. as specification and guidance for designers during design or as a basis for heuristic evaluation). Its provisions for the presentation of information depend on the auditory design approach, the task, the user, the environment and the single or multiple technologies that can be used for presenting the information. Consequently, this document cannot be applied without knowledge of the context of use.”
Adobe, The New York Times Company and Twitter Announce Content Authenticity Initiative to Develop Industry Standard for Content Attribution
Adobe announced the Content Authenticity Initiative, along with The New York Times Company and Twitter, aimed at developing an industry standard for digital content attribution. The ability to provide proper content attribution for creators and publishers is critical to ensure trust and transparency online. Adobe, The New York Times Company and Twitter believe that creating a long-term solution is a shared responsibility among creators, technology, and media companies, and that joining forces will accelerate progress. Adobe is developing an opt-in system that will allow creators and publishers to securely attach attribution data to content they choose to share. The framework is designed to let authors verify their content so that they receive proper attribution and provide consumers with an attribution trail to give them greater confidence about the authenticity of the content they’re consuming. Adobe, The New York Times Company and Twitter plan to kick off the initiative at a summit along with a larger group of technology and media companies in the coming months. Companies interested in participating in the Content Authenticity Initiative can learn more at hhttps://theblog.adobe.com/content-authenticity-initiative/ or contact contentauthenticity@adobe.com.
(W3C) First Public Working Draft: Use Cases and Requirements for Decentralized Identifiers
“The Decentralized Identifier Working Group has published a First Public Working Draft of Use Cases and Requirements for Decentralized Identifiers. This document sets out use cases and requirements for a new type of identifier that has 4 essential characteristics:
- decentralized: there should be no central issuing agency;
- persistent: the identifier should be inherently persistent, not requiring the continued operation of an underling organization;
- cryptographically verifiable: it should be possible to prove control of the identifier cryptographically;
- resolvable: it should be possible to discover metadata about the identifier.
Although existing identifiers may display some of these characteristics, none currently displays all four.”
