Standard

This standard describes specific methodologies to help users certify how they worked to address and eliminate issues of negative bias in the creation of their algorithms, where negative bias infers the usage of overly subjective or uniformed data sets or information known to be inconsistent with legislation concerning certain protected characteristics (such as race, gender, sexuality, etc); or with instances of bias against groups not necessarily protected explicitly by legislation, but otherwise diminishing stakeholder or user well being and for which there are good reasons to be considered inappropriate. Possible elements include (but are not limited to): benchmarking procedures and criteria for the selection of validation data sets for bias quality control; guidelines on establishing and communicating the application boundaries for which the algorithm has been designed and validated to guard against unintended consequences arising from out-of-bound application of algorithms; suggestions for user expectation management to mitigate bias due to incorrect interpretation of systems outputs by users (e.g. correlation vs. causation).

A set of ontologies with different abstraction levels that contain concepts, definitions, axioms, and use cases that assist in the development of ethically driven methodologies for the design of robots and automation systems is established by this standard. It focuses on the robotics and automation domain without considering any particular applications and can be used in multiple ways, for instance, during the development of robotics and automation systems as a guideline or as a reference “taxonomy” to enable clear and precise communication among members from different communities that include robotics and automation, ethics, and correlated areas. Users of this standard need to have a minimal knowledge of formal logics to understand the axiomatization expressed in Common Logic Interchange Format.

ISO/IEC/IEEE 12207:2017 also provides processes that can be employed for defining, controlling, and improving software life cycle processes within an organization or a project.The processes, activities, and tasks of this document can also be applied during the acquisition of a system that contains software, either alone or in conjunction with ISO/IEC/IEEE 15288:2015, Systems and software engineering?System life cycle processes.In the context of this document and ISO/IEC/IEEE 15288, there is a continuum of human-made systems from those that use little or no software to those in which software is the primary interest. It is rare to encounter a complex system without software, and all software systems require physical system components (hardware) to operate, either as part of the software system-of-interest or as an enabling system or infrastructure. Thus, the choice of whether to apply this document for the software life cycle processes, or ISO/IEC/IEEE 15288:2015, Systems and software engineering?System life cycle processes, depends on the system-of-interest. Processes in both documents have the same process purpose and process outcomes, but differ in activities and tasks to perform software engineering or systems engineering, respectively.

This document specifies the syntax and semantics of description schemes to represent data exchanged by media things (e.g., media sensors, media actuators, media analysers, media storages). Moreover, it specifies the APIs to exchange these data between media things. This document does not specify how sensing and analysing is carried out but defines the interfaces between the media things.

This standard provides stakeholders with certifiable and responsible child and student data governance methodologies.

This recommended practice provides recommendations for next steps in the application of IEEE Std 7010, applied to meeting Environmental Social Governance (ESG) and Social Development Goal (SDG) initiatives and targets. It provides action steps and map elements to review and address when applying IEEE Std 7010. This recommended practice serves to enhance the quality of the published standard by validating the design outcomes with expanded use. It provides recommendations for multiple users to align processes, collect data, develop policies and practices and measure activities against the impact on corporate goals and resulting stakeholders. This recommended practice does not set metrics for measurement and/or reporting, but rather identifies well recognized indicators to consider in assessment and measurement of progress.

This recommended practice produces best practices for meeting the requirements of IEEE P7004: Standard for Child and Student Data Governance, when designing, provisioning, configuring, operating, and maintaining an online virtual classroom experience for synchronous online learning, education, and training. The recommended practice includes language that can be referenced in requests for proposals (RFPs) for online (also known as virtual) classroom solutions, the operational runbook(s) for such solutions, and the assessment and certification guideline(s) for compliance process of such solutions.

This document presents considerations for using VR content in the learning, education and training (LET) domain for reducing reality and virtual reality crossover confusion among users and assisting users to effectively use these emerging technologies. This document addresses VR content that uses a head-mounted display (HMD) in the LET domain. It does not address VR content using immersive technology and does not address augmented reality, mixed or merged reality content.

ISO 29481-2:2012 specifies a methodology and format for describing coordination between actors in a building construction project during all life cycle stages. It therefore specifies: a methodology that describes an interaction framework, an appropriate way to map responsibilities and interactions that provides a process context for information flow; a format in which the interaction framework should be specified. ISO 29481-2:2012 is intended to facilitate interoperability between software applications used in the construction process, to promote digital collaboration between actors in the building construction process, and to provide a basis for accurate, reliable, repeatable, and high-quality information exchange.

ISO 16760:2014 specifies requirements for an RGB workflow for graphic arts printing based on the use of reflection prints (RGB Reference Prints) as the evaluation vehicle for coloured images. It provides guidelines on the creation of print-targeted RGB images (RGB Reference Images) and simulation prints. This International Standard requires the identification of a pair of ICC profiles for each image: an image profile and a profile describing the reference printing system. These profiles provide individual colour transformations for gamut mapping and colour separation. This International Standard does not provide any guidance as to how these gamut mapping or colour separation transforms can be specified.

ISO 16757-2:2016 describes the modelling of building services product geometry. The description is optimized for the interchange of product catalogue data and includes(a) shapes for representing the product itself,(b) symbolic shapes for the visualization of the product's function in schematic diagrams,(c) spaces for functional requirements,(d) surfaces for visualization, and(e) ports to represent connectivity between different objects.The shape and space geometry is expressed as Constructive Solid Geometry (CSG) based on geometric primitives concatenated to boundary representations by Boolean operations. ISO 16757-2:2016 uses the applicable primitives from ISO 10303‑42 and from ISO 16739 and adds primitives which are required for the special geometry of building services products. For symbolic shapes, line elements are also used. ISO 16757-2:2016 neither describes the inner structure and internal functionality of the product nor the manufacturing information because this is typically not published within a product catalogue. Building services products can have millions of variant dimensions. To avoid the exchange of millions of geometries, a parametric model is introduced which allows the derivation of variant-specific geometries from the generic model. This is necessary to reduce the data to be exchanged in a catalogue to a manageable size. The parametric model will result in smaller data files, which can be easier transmitted during data exchanges. The geometry model used does not contain any drawing information such as views, line styles or hatching.

This document describes the COLLADA schema. COLLADA is a Collaborative Design Activity that defines an XML-based schema to enable 3D authoring applications to freely exchange digital assets without loss of information, enabling multiple software packages to be combined into extremely powerful tool chains. The purpose of this document is to provide a specification for the COLLADA schema in sufficient detail to enable software developers to create tools to process COLLADA resources. In particular, it is relevant to those who import to or export from digital content creation (DCC) applications, 3D interactive applications and tool chains, prototyping tools, real-time visualization applications such as those used in the video game and movie industries, and CAD tools. This document covers the initial design and specifications of the COLLADA schema, as well as a minimal set of requirements for COLLADA exporters. This document covers the following information:(a) initial design and specifications of the COLLADA schema;(b) requirements of COLLADA tools and a minimal set of requirements for COLLADA exporters;(c) detailed explanations for COLLADA programming;(d) core elements that describe geometry, animation, skinning, assets, and scenes;(e) physics model, visual effects (FX), boundary representation (B-rep) of animation, kinematics.The document does not specify the implementation of, or definition of a run-time architecture for viewing or processing of COLLADA data.