Search
×
FR

Placeholder headline

This is just a placeholder headline

API Technical Report TDB-6 Chapter 6 – Density

$

204

BUY NOW

Placeholder headline

This is just a placeholder headline

API STD 560: Fired Heaters for General Refinery Services

$

721

BUY NOW

Placeholder headline

This is just a placeholder headline

API STD 64: Diverter Equipment Systems

$

324

BUY NOW

Placeholder headline

This is just a placeholder headline

API MPMS CH 17.10.1: Refrigerated Light Hydrocarbon Fluids – Measurement of Cargoes on Board LNG Carries

$

417

BUY NOW

Placeholder headline

This is just a placeholder headline

API RP 13B-1: Testing Water-based Drilling Fluids

$

418

BUY NOW

Placeholder headline

This is just a placeholder headline

API Technical Report TDB-12 Chapter 12 – Thermal Conductivity

$

214

BUY NOW

Placeholder headline

This is just a placeholder headline

API 16FI Frac Iron Guidelines and Requirements

$

129

BUY NOW

ISO 30182:2017

ISO 30182:2017 Smart city concept model – Guidance for establishing a model for data interoperability

CDN $0.00

Description

ISO/IEC 30182:2017 describes, and gives guidance on, a smart city concept model (SCCM) that can provide the basis of interoperability between component systems of a smart city, by aligning the ontologies in use across different sectors. It includes:

– concepts (e.g. ORGANIZATION, PLACE, COMMUNITY, ITEM, METRIC, SERVICE, RESOURCE); and

– relationships between concepts (e.g. ORGANIZATION has RESOURCEs, EVENT at a PLACE).

The SCCM does not replace existing models where they exist, but, by mapping from a local model to a parent model, questions can be asked about data in a new and joined-up way.

ISO/IEC 30182:2017 is aimed at organizations that provide services to communities in cities, and manage the resulting data, as well as decision-makers and policy developers in cities.1)

The SCCM is relevant wherever many organizations provide services to many communities within a place.

It does not cover the data standards that are relevant to each concept in the SCCM and does not attempt to list or recommend the sources of identifiers and categorizations that cities map to the SCCM.

The SCCM has been devised to communicate the meaning of data. It does not attempt to provide concepts to describe the metadata of a dataset, for example, validity and provenance of data.

It covers semantic interoperability, that is, defining the meaning of data, particularly from many sources. It does not cover other barriers to interoperability, some of which are described at 3.2.

Edition

1

Published Date

2017-05-23

Status

PUBLISHED

Pages

55

Language Detail Icon

English

Format Secure Icon

Secure PDF

Abstract

ISO/IEC 30182:2017 describes, and gives guidance on, a smart city concept model (SCCM) that can provide the basis of interoperability between component systems of a smart city, by aligning the ontologies in use across different sectors. It includes:

- concepts (e.g. ORGANIZATION, PLACE, COMMUNITY, ITEM, METRIC, SERVICE, RESOURCE); and

- relationships between concepts (e.g. ORGANIZATION has RESOURCEs, EVENT at a PLACE).

The SCCM does not replace existing models where they exist, but, by mapping from a local model to a parent model, questions can be asked about data in a new and joined-up way.

ISO/IEC 30182:2017 is aimed at organizations that provide services to communities in cities, and manage the resulting data, as well as decision-makers and policy developers in cities.1)

The SCCM is relevant wherever many organizations provide services to many communities within a place.

It does not cover the data standards that are relevant to each concept in the SCCM and does not attempt to list or recommend the sources of identifiers and categorizations that cities map to the SCCM.

The SCCM has been devised to communicate the meaning of data. It does not attempt to provide concepts to describe the metadata of a dataset, for example, validity and provenance of data.

It covers semantic interoperability, that is, defining the meaning of data, particularly from many sources. It does not cover other barriers to interoperability, some of which are described at 3.2.

Previous Editions

Can’t find what you are looking for?

Please contact us at: