Semantic Description of CommunicationInformation UrbanDataset from SCP Ontology 2.0

This document provides human-friendly documentation for CommunicationInformation UrbanDataset having semantic definition in the SCP Ontology 2.0, part of the "Smart City Platform Specifications (SCPS) - Semantic Level" developed as part of the Electricity System Research Project.

File creation date

2025-01-31 04:59

SCPS URL

https://smartcityplatform.enea.it/#/it/index.html

Introduction

This document provides the human-friendly representation of the semantic definition of one or more SCPS ontology´s UrbanDatasets.

Each UrbanDataset is described through a table composed of three main sections:

UrbanDataset Identification: defines the purpose of the UrbanDataset and the parameters (identifier, name and URI) uniquely identifing it in the SCPS scope. It states the information that populates the "Specification" section of UrbanDataset messages.
UrbanDataset Contextualization: defines the context properties (ContextProperty) associated with the UrbanDataset; for each one it specifies name, meaning (description), data type and set of values (code list) to which it is constrained, if any. The UrbanDataset context properties have not units of measurement and are all mandatory unless otherwise indicated in the description. Furthermore, this section provides any indications on the use of context properties within the specific UrbanDataset. It states the properties that populate the "Context" section of UrbanDataset messages.
UrbanDataset Properties: states the properties (UrbanDatasetProperty) uniquely defining the UrbanDataset in the SCPS ontology; for each one it specifies name, meaning (description), if it is required, data type, set of values (code list) to which it is constrained, if any, and the admitted units of measurement. The properties properties marked with an asterisk require to indicate, at instance level, the adopted calculation method (for example, total or average value over the measurement period). It states the properties that populate each row of the "Values" section of UrbanDataset messages.

The normative references concerning the syntactic and semantic compliance of UrbanDatasets with the SCPS are:

depending on the adopted syntax, the schema scps-urbandataset-schema-2.0:
- JSON Schema
- XML Schema
the UrbanDataset semantic definition that can be acquired or through the OWL ontology, or through the UDWebLibrary, or through this documentation.

Furthermore, in the resources section available in the tab of each UrbanDataset in the UDWebLibrary, it is possible to download the message templates in JSON and XML syntax, compliant with the specifications. A template is an example of an UrbanDataset instance having all the properties (mandatory and optional) that make it (for any properties with alternative units of measurement and/or calculation method, the default values are used).

SECTION I: UrbanDataset

CommunicationInformation-2.0

UrbanDataset Identification
Scope	Describes the set of parameters necessary to enable direct communication between two vertical solutions without using the SCP as an intermediary
Category / Subcategory	/ UrbanDataset
Identifier	CommunicationInformation-2.0
Name	Communication Information
URI	https://smartcityplatform.enea.it/specification/semantic/2.0/ontology/scps-ontology-2.0.owl#CommunicationInformation
UrbanDataset Contextualization
	Description	Format/Code list
coordinates	Geographical reference	Aggregated property
subProperty: format	Wgs84 format in which the coordinates are expressed (optional attribute)	string FormatCode.gc
subProperty: height	Altitude (optional property)	double
subProperty: latitude	Latitude	double
subProperty: longitude	Longitude	double
language	The language in which the text fields of the instance are expressed	string LanguageCode.gc
timestamp	Timestamp	dateTime
timezone	The time zone to be applied to each timestamp in the instance; it is expressed as an offset, i.e. as + or - the number of hours and minutes respect to UTC time: +/-hh:mm (ISO 8601)	string TimezoneCode.gc
UrbanDataset Properties * properties marked with an asterisk require to indicate, at instance level, the adopted calculation method (e.g. "average", "total", "instantaneous",...)
Name	Description	Mandatory	Format/Code list	Unit of Measure
CommunicationPattern	Communication pattern (possible values: "Push", "Request Response", "Publish Subscribe")	yes	enumeration
DataDescription	Textual description of the sent data	yes	string
DataFormat	An URL identifying the Schema (XML or JSON) used to exchange data	yes	string
VerticalSolutionName	The name of the vertical solution	yes	string
WSEndpoint	URL of the Web Service endpoint that needs to be accessed	yes	string

SECTION II: Code lists

FormatCode.gc

Short name	FormatCode
Version	2.0
URI	https://smartcityplatform.enea.it/specification/semantic/2.0/gc/FormatCode.gc
Agency	ENEA
Code	Value
WGS84-DMS	WGS84 - Degree, Minutes, Seconds format
WGS84-DD	WGS84 - Decimal Degrees format

LanguageCode.gc

Short name	LanguageCode
Version	2.0
URI	https://smartcityplatform.enea.it/specification/semantic/2.0/gc/LanguageCode.gc
Agency	ENEA
Code	Value
IT	Italian
EN	English

TimezoneCode.gc

Short name	TimezoneCode
Version	2.0
URI	https://smartcityplatform.enea.it/specification/semantic/2.0/gc/TimezoneCode.gc
Agency	ENEA
Code	Value
UTC-12	−12:00
UTC-11	−11:00
UTC-10	−10:00
UTC-9:30	−09:30
UTC-9	−09:00
UTC-8	−08:00
UTC-7	−07:00
UTC-6	−06:00
UTC-5	−05:00
UTC-4	−04:00
UTC-3:30	−03:30
UTC-3	−03:00
UTC-2	−02:00
UTC-1	−01:00
UTC	+00:00
UTC+1	+01:00
UTC+2	+02:00
UTC+3	+03:00
UTC+3:30	+03:30
UTC+4	+04:00
UTC+4:30	+04:30
UTC+5	+05:00
UTC+5:30	+05:30
UTC+5:45	+05:45
UTC+6	+06:00
UTC+6:30	+06:30
UTC+7	+07:00
UTC+8	+08:00
UTC+8:30	+08:30
UTC+8:45	+08:45
UTC+9	+09:00
UTC+9:30	+09:30
UTC+10	+10:00
UTC+10:30	+10:30
UTC+11	+11:00
UTC+12	+12:00
UTC+12:45	+12:45
UTC+13	+13:00
UTC+14	+14:00

Semantic Description of CommunicationInformation UrbanDataset from SCP Ontology 2.0

Table of content

Introduction

SECTION I: UrbanDataset

SECTION II: Code lists

Introduction

1. How to read this document

2. Artifacts to create an UrbanDataset message

SECTION I: UrbanDataset

CommunicationInformation-2.0

SECTION II: Code lists

FormatCode.gc

LanguageCode.gc

TimezoneCode.gc