ISO/IEC

This document specifies the conformance and reference software implementing ISO/IEC 23093-3. The information provided is applicable for determining the reference software modules available for ISO/IEC 23093-3, understanding the functionality of the available reference software modules, and utilizing the available reference software modules. Furthermore, this document provides means for conformance testing, i.e. bitstreams - XML descriptions that conform or do not conform to ISO/IEC 23093-3.

ISO/IEC 18023-1:2005 addresses the concepts, syntax and semantics for the representation and interchange of environmental data. It specifies: - a data representation model for expressing environmental data; - specifications of the data types and classes that together constitute the data representation model; and- an application program interface that supports the storage and retrieval of environmental data using the data representation model.ISO/IEC 18023-1:2005 also specifies topological, rule-based, and other constraints that ensure appropriate data can be available for applications that rely on automatically generated behaviours when interacting with environmental data.

This document describes best practices for use case projects in terms of characterization, template, plan and maintenance. It is intended to developers of use case projects, including in the context of standardisation. The document can be used to complement existing methodology standards such as IEC 62559 or IEC Guide 125.

This document specifies an Internet of Things (IoT) reference architecture (IoT RA). The IoT RA is a generalization of existing practice including the distinguishing characteristics of IoT systems and other 195 fundamental characteristics exhibited by IoT systems. The IoT RA addresses stakeholder concerns related to 196 the business value of IoT systems. The IoT RA also addresses the interactions between the IoT system, the 197 users, and the physical environment. Implementation of IoT systems is also addressed in this IoT RA. Among 198 the characteristics specified in the IoT RA are abstract functions within IoT systems and a variety of structures 199 that are used to construct IoT systems.

ISO/IEC 14772-1, the Virtual Reality Modeling Language (VRML), defines a file format that integrates 3D graphics and multimedia. Conceptually, each VRML file is a 3D time-based space that contains graphic and aural objects that can be dynamically modified through a variety of mechanisms. This part of ISO/IEC 14772 defines the interface that applications external to the VRML browser may use to access and manipulate the objects defined in ISO/IEC 14772-1. The interface described here is designed to allow an external environment to access nodes in a VRML scene using the existing VRML event model. In this model, an eventOut of a given node can be routed to an eventIn of another node. When the eventOut generates an event, the eventIn is notified and its node processes that event. Additionally, if a script in a Script node has a reference to a given node it can send events directly to any eventIn of that node and it can read the last value sent from any of its eventOuts. The scope of this standard is to cover all forms of access to a VRML browser from external applications. It is equally valid for a database with a object interface to access a standalone browser in a presentation slide as it is for a Java applet operating within a web browser and the available services do not vary. This standard does not provide a byte level protocol description as there can be many valid ways of expressing an interaction with a browser. Instead, it represents the interface in terms of the services provided and the parameters that are passed to access these services. Individual language and protocol bindings to these services are available as annexes to this part of ISO/IEC 14772.

ISO/IEC 18023-2:2006 specifies the abstract syntax of a SEDRIS transmittal. Actual encodings (e.g. binary encoding) are specified in other parts of ISO/IEC 18023.

ISO/IEC 18023-3:2006 defines a binary encoding for DRM objects specified in ISO/IEC 18023-1 according to the abstract syntax specified in ISO/IEC 18023-2.

ISO/IEC 18024-4:2006 specifies a language-dependent layer for the C programming language. ISO/IEC 18023-1 specifies a language-independent application program interface (API) for SEDRIS. For integration into a programming language, the SEDRIS API is embedded in a language-dependent layer obeying the particular conventions of that language.

ISO/IEC 19775-2:2015 specifies a standard set of services that are made available by a browser so that an author can access the scene graph while it is running. Such access is designed to support inspection and modification of the scene graph.

ISO/IEC 19775-1:2015, Extensible 3D (X3D), defines a system that integrates 3D graphics and multimedia. Conceptually, each X3D file is a 3D time-based space that contains graphic and aural objects that can be dynamically modified through a variety of mechanisms. This part of ISO/IEC 19776 defines a mapping of the abstract objects in X3D to a specific X3D encoding using the Extensible Markup Language. Each XML-encoded X3D file:a. supports all of the purposes of X3D files defined in the X3D abstract specification ISO/IEC 19775; andb. encodes X3D constructs in an XML format.An XML-encoded X3D file may be referenced from files using other X3D encodings and may itself reference other X3D files encoded using other X3D encodings. Such files can only be processed by browsers that conform to all of the utilized X3D encodings.

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.

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.