IT in general

This standard defines an architectural framework, protocols and Application Programming Interfaces (APIs) for providing Real-time Onsite Operations Facilitation (ROOF). ROOF computing and networking for the data and the devices include next-hop connectivity for the devices, real-time context building and decision triggers, efficient backhaul connectivity to the cloud, and security & privacy. This standard covers interoperability, collaboration and autonomous operation of an Internet of Things (IoT) system with computing required for context building, security, access control, data storage, data aggregation and ability to choose different cloud and application service providers. Furthermore, this standard defines how an end user is able to securely provision, commission and decommission the devices. This standard leverages existing applicable standards and is complimentary to architectural frameworks defined in broader IoT environments.

This document provides an overview of the High Level Architecture (HLA), defines a family of related HLA documents, and defines the principles of HLA in terms of responsibilities that federates (simulations, supporting utilities, or interfaces to live systems) and federations (sets of federates working together) must uphold.

Specify an initial extension to SAREF to include the semantic model for Smart Cities
. This initial extension will be based on a limited set of use cases and available existing data model identified in the corresponding requirement TR.
This work is expected to be developed in close collaboration with AIOTI, the H2020 Large Scale Pilots and with ETSI activities in the Smart Cities, primarily ISG CIM. Use cases and related semantic model are expected to be aligned with corresponding work in CIM.
Further extensions are envisaged in future to cover entirely the Smart Cities domain.

Defining indicators (KPIs) for Smart Cities expressing city level in terms of People, Planet, Prosperity and Governance.,

The purpose of this Group Report is to explain with examples the usage of NGSI-LD information model and API, as defined in GS-004 prelimAPI, and considering also some use cases from GR-002 for ICT professionals. Worked examples are provided, with code fragments made available in a public repository. No changes in the GS-004 prelimAPI specification can be introduced or proposed in this document.

The purpose of this Group Specification is the (preliminary) definition of a standard API for Context Information Management (CIM-API) enabling close to real-time access to information coming from many different sources (not only IoT). The document shall define how such an API enables applications to perform updates on context, register context providers which can be queried to get updates on context, query information on current and historic context information and subscribe for receiving notifications on context changes. The criteria for choice of the API characteristics shall be based on results in WI UC and WI GAP.
This Group Specification is labelled "preliminary" because it should be published widely in order to elicit comment and critique from the user communities and their comments will be used to modify and improve the later final API specification. Accordingly a feedback process shall be described in this document.
This Group Specification shall be compatible with an example data model published at the same time (see Work Item MOD0), so that implementers of appropriate software can efficiently test and compare results and interoperability.

This Group Specification provides additions and corrections to the GS-009 NGSI-LD API specification, based on feedback received from developers in the linked-data, internet-of-things, mobile-apps and smart-applications communities, as well as from end users and stakeholders.

The purpose of this Group Specification is to define or identify a cross-domain data model compatible with the CIM API defined in WI API0, for use in testing that preliminary API specification. The preliminary cross-cutting data model shall be applied using two or more of the use case domains in WI UC. It is not essential that the data model be in any sense comprehensive, but it should allow testing of all functions of CIM API0.

It is expected that recent work within ETSI SmartM2M and within oneM2M will strongly influence this preliminary specification.

This document defines a comprehensive set of evaluation indicators specially related to information and communication technologies (ICT) adoption and usage in smart cities. Firstly, it establishes an overall framework for all the indicators. Then, it specifies the name, description, classification and measurement method for each indicator.

ISO 12006-3:2007 specifies a language-independent information model which can be used for the development of dictionaries used to store or provide information about construction works. It enables classification systems, information models, object models and process models to be referenced from within a common framework.

The definitions in this edition of ISO 6107 are based on available standards and aim to harmonise the understanding of terms used within ISO TC147 Water quality to facilitate clear understanding and application of the water quality standards and to reduce variation of interpretation as far as possible. Source information is provided where available. This standard aims to improve and feed the terminology database for ISO TC147 and to serve as a reference document for all water quality characterisation committees and users. Terms and the interpretation thereof may differ in various fields i.e.: chemistry microbiology and ecotoxicology. This is indicated in brackets, if applicable, after the term being defined. ISO 6107 is restricted to definitions for terms which appear in standards of ISO/TC 147, Water quality.

The deliverable will define indicators (KPI) for Smart Cities expressing city level in terms of People, Planet, Prosperity, Governance and Propagation