Standard

The present document provides an overview and an introduction to the interface specification for the reference points "AR 16 - World Anchors" and "AR 17 - Reference Objects" of the AR framework architecture, ETSI GS ARF 003 (V1.1.1): Augmented Reality Framework (ARF) AR framework architecture, developed by the ETSI Industry Specification Group (ISG) for an Augmented Reality Framework (ARF). The actual interface specification is provided as OpenAPI™ specification, ARF005 - World Storage API, revision 1.0.0, and forms the baseline for the present document.

This document defines the scope and key concepts of mixed and augmented reality, the relevant terms and their definitions and a generalized system architecture that together serve as a reference model for mixed and augmented reality (MAR) applications, components, systems, services and specifications. This architectural reference model establishes the set of required sub-modules and their minimum functions, the associated information content and the information models to be provided and/or supported by a compliant MAR system. The reference model is intended for use by current and future developers of MAR applications, components, systems, services or specifications to describe, compare, contrast and communicate their architectural design and implementation. The MAR reference model is designed to apply to MAR systems independent of specific algorithms, implementation methods, computational platforms, display systems and sensors or devices used. This document does not specify how a particular MAR application, component, system, service or specification is designed, developed or implemented. It does not specify the bindings of those designs and concepts to programming languages or the encoding of MAR information through any coding technique or interchange format. This document contains a list of representative system classes and use cases with respect to the reference model.

For integration into a programming language, the X3D abstract interfaces are embedded in a language-dependent layer obeying the particular conventions of that language. ISO/IEC 19777-1:2006 specifies such a language dependent layer for the ECMAScript language. ISO/IEC 19775-2 specifies a language-independent application programmer interface (API) to a set of services and functions.

The Extensible 3D (X3D) specification, ISO/IEC 19775, specifies a language-independent application programmer interface (API) to a set of services and functions. For integration into a programming language, the X3D abstract interfaces are embedded in a language dependent layer obeying the particular conventions of that language. ISO/IEC 19777-2:2006 specifies such a language-dependent layer for the Java programming language.

This document describes the glTF file format. glTF is an API-neutral runtime asset delivery format. glTF bridges the gap between 3D content creation tools and modern graphics applications by providing an efficient, extensible, interoperable format for the transmission and loading of 3D content.

This document defines the framework and information reference model for representing sensor-based 3D mixed-reality worlds. It defines concepts, an information model, architecture, system functions, and how to integrate 3D virtual worlds and physical sensors in order to provide mixed-reality applications with physical sensor interfaces. It defines an exchange format necessary for transferring and storing data between physical sensor-based mixed-reality applications. This document specifies the following functionalities:a) representation of physical sensors in a 3D scene;b) definition of physical sensors in a 3D scene;c) representation of functionalities of each physical sensor in a 3D scene;d) representation of physical properties of each physical sensor in a 3D scene;e) management of physical sensors in a 3D scene; andf) interface with physical sensor information in a 3D scene.This document defines a reference model for physical sensor-based mixed-reality applications to represent and to exchange functions of physical sensors in 3D scenes. It does not define specific physical interfaces necessary for manipulating physical devices, but rather defines common functional interfaces that can be used interchangeably between applications. This document does not define how specific applications are implemented with specific physical sensor devices. It does not include computer generated sensor information using computer input/output devices such as a mouse or a keyboard. The sensors in this document represent physical sensor devices in the real world.

ISO/IEC 23000-13:2017 specifies the following:- scene description elements for representing AR content; and- mechanisms to connect to local and remote sensors and actuators; mechanisms to integrated compressed media (image, audio, video, graphics); mechanisms to connect to remote resources such as maps and compressed media.

This document is the first of a family of standards. ISO/IEC 12087 is concerned with the manipulation, processing, and interchange of all types of digital images. The main purpose of this part is to define a generic, unifying imaging architecture to which other parts of ISO/IEC 12087 conform. This part of ISO/IEC 12087 also defines those specializations or delineations of the generic imaging architecture that are required to support IPI-PIKS and IPI-IIF.

This document analyses visualization elements that are key components of the interface between the physical asset and the avatar (digital replica of the physical asset).

ISO 14306:2017 defines the syntax and semantics of a file format for the 3D visualization and interrogation of lightweight geometry and product manufacturing information derived from CAD systems, using visualization software tools that do not need the full capability of a CAD system. ISO 14306:2017 has been adopted as a 3D visualization capability in addition to the ISO 10303 series. The file format supports the following information:(1) facet information (triangles), stored with geometry compression techniques(2) visual attributes such as lights, textures and materials(3) product manufacturing information, such as dimensions, tolerances and other attributes(4) boundary representation (b-rep) solid model shape representations. Several alternatives are available, including a representation based on the geometry standard defined in ISO 10303(5) configuration representations(6) delivery methods such as asynchronous streaming of content ISO 14306:2017 does not specify the implementation of, or definition of a run-time architecture for viewing or processing of the file format.

This document is the first of a family of standards. ISO 12637-1:2006 defines a set of fundamental terms that can be used in the drafting of other International Standards for graphic technology. In order to facilitate their translation into other languages, the definitions are worded so as to avoid, where possible, any peculiarity attached to one language. The entries in ISO 12637-1:2006 are arranged alphabetically.

ISO/IEC 19775, X3D, defines a software system that integrates network-enabled 3D graphics and multimedia. Conceptually, each X3D application is a 3D time-based space that contains graphic and aural objects that can be dynamically modified through a variety of mechanisms. ISO/IEC 19775-1:2013 defines the architecture and base components of X3D. The semantics of X3D describe an abstract functional behaviour of time-based, interactive 3D, multimedia information. ISO/IEC 19775-1:2013 does not define physical devices or any other implementation-dependent concepts (e.g. screen resolution and input devices). It is intended for a wide variety of devices and applications, and provides wide latitude in interpretation and implementation of the functionality. For example, it does not assume the existence of a mouse or 2D display device. Each X3D application:(1) implicitly establishes a world coordinate space for all objects defined, as well as all objects included by the application;(2) explicitly defines and composes a set of 3D and multimedia objects;(3) can specify hyperlinks to other files and applications;(4) can define programmatic or data-driven object behaviours;(5) can connect to external modules or applications via programming and scripting languages;(6) explicitly declares its functional requirements by specifying a profile; and(7) can declare additional functional requirements by specifying components.