This recommended practice specifies how the elements and attributes defined in the Atom Syndication Format (Atom) relate to the components of the conceptual model for resource aggregation defined in IEEE Std 1484.13.1(tm)-2012.
Specified in this recommended practice are how the elements and attributes defined in the Open Archives Initiative Object Reuse and Exchange (OAI-ORE) Abstract Model and expressed in the OAI-ORE Resource Map Implementation in RDF/XML relate to the components of the conceptual model for resource aggregation defined in IEEE Std 1484.13.1(TM)-2012.
Augmented Reality (AR) promises to provide significant boosts in operational efficiency by making information available to employees needing task support in context in real time. To support according implementations of AR training systems,this document proposes an overarching integrated conceptual model that describes interactions between the physical world, the user, and digital information, the context for AR-assisted learning and other parameters of the environment. It defines two data models and their binding to XML and JSON for representing learning activities (also known as employee tasks and procedures) and the learning environment in which these tasks are performed (also known as the workplace). The interoperability specification and standard is presented in support of an open market where interchangeable component products provide alternatives to monolithic Augmented Reality-assisted learning systems. Moreover, it facilitates the creation of experience repositories and online marketplaces for Augmented Reality-enabled learning content. Specific attention was given to reuse and repurposing of existing learning content and catering to ‘mixed' experiences combining real world learner guidance with the consumption (or production) of traditional contents such as instructional video material or learning apps and widgets.
This Standard describes a data model to support the interchange of agreed upon data elements and their values between a learning-related content object and a runtime service (RTS) used to support learning management. This Standard does not specify the means of communication between a content object and an RTS nor how any component of a learning environment shall behave in response to receiving data in the form specified. This Standard is based on a related data model defined in the "Computer Managed Instruction (CMI) Guidelines For Interoperability," version 3.4, defined by the Aviation Industry CBT Committee (AICC). To balance the need to support existing implementations with the need to make technical corrections and support emerging practice, this Standard selectively includes those data elements from the CMI specification that are commonly implemented; renames some data elements taken from the CMI specification to clarify their intended meaning; modifies the data types of data elements taken from the CMI specification to reflect ISO standard data types and internationalization requirements; removes some organizational structures used in the CMI specification to group data elements that are specific to the AICC community of practice and not generally applicable; and introduces some data elements not present in the CMI specification to correct known technical defects in data elements taken from that specification.
This guide will provide a framework that outlines technologies and the processes for planning the evolution of a smart city. Smart Cities and related solutions require technology standards and a cohesive process planning framework for the use of the internet of things to ensure interoperable, agile, and scalable solutions that are able to be implemented and maintained in a sustainable manner. This framework provides a methodology for municipalities and technology integrators to use as a tool to plan for innovative and technology solutions for smart cities.
Specific configuration requirements within the relevant Internet Engineering Task Force (IETF) Request for Comments (RFC) for implementation of the Internet Protocol Security (IPsec) protocol suite within a utility control system are identified in this standard. It is not intended to be a comprehensive guide to implementing IPsec. Promoting interoperability between products developed by different vendors is the primary goal in developing this standard. Configuration parameters needed to support the establishment and sustained operation of an IPsec Virtual Private Network (VPN) tunnel between two devices which have implemented IPsec conforming to this standard are the focus of this standard. Minimizing configuration errors involving IPsec implementations within utility control systems is a secondary goal of this standard. Product agnosticism and applicability to any device (e.g., router, substation gateway, intelligent electronic device, etc.) is the intent of this standard, within the utility control system as the end user deems necessary for their unique system architecture.
The performance and functional capability requirements for DER connected with the Area Electric Power Systems (Area EPS) are defined in IEEE Std 1547(TM). This amendment revises the ranges of allowable trip clearing time settings in Table 13 for DERs in abnormal operating performance category III to allow wider ranges that can broaden and simplify the adoption of the standard. In addition, the related informative Figure H.9 is revised accordingly.
This standard defines a suite of cryptographic protocols supporting the protection of Electric Power System communications links. It does not address specific applications or hardware implementations, and is independent of the underlying communications protocol.
This standard defines a cryptographic protocol to provide integrity, and optional confidentiality, for cybersecurity of Electrical Power System (EPS) serial links. It does not address specific applications or hardware implementations, and is independent of the underlying communications protocol.
This standard defines a privacy scale that shall be applied to data that is defined as personal identifiable information that is being collected, retained, processed or shared by or among applications implemented on networked edge, fog, or cloud computing devices. This privacy scale data provides input to assessment tools that developers or users of these applications use to develop, discover, recognize, or implement appropriate privacy settings for types or levels of personal data resident on these devices.
The enhanced security management function for the protocol defined in IEEE 1888(TM), “Ubiquitous Green Community Control Network Protocol,” is described in this standard. Security requirements, system security architecture definitions, and a standardized description of authentication and authorization, along with security procedures and protocols, are specified. This standard can help avoid unintended data disclosure to the public and unauthorized access to resources, while providing enhanced integrity and confidentiality of transmitted data in the ubiquitous green community control network.
This standard defines secure message formats and processing for use by Wireless Access in Vehicular Environments (WAVE) devices, including methods to secure WAVE management messages and methods to secure application messages. It also describes administrative functions necessary to support the core security functions.