diff --git a/documentation/abstract.md b/documentation/abstract.md index b44e47e5197edd2cc6bf939a2210f9e64033d49d..b4b4c36bfcc56339599bc97c6af0b17552287227 100644 --- a/documentation/abstract.md +++ b/documentation/abstract.md @@ -1,4 +1,8 @@ -The present document is a technical specification of SAREF4CITY, an extension of SAREF [[1]](#[1]) for the Smart Cities domain. This extension has been created by investigating resources from potential stakeholders of the ontology, such as standardization bodies (e.g. Open Geospatial Consortium), associations (e.g. Spanish Federation of Municipalities and Provinces), IoT platforms (e.g. FIWARE) and European projects and initiatives (e.g. ISA2 programme) as reported in ETSI TR 103 506 [[i.1]](#[i.1]). In addition, the use cases defined in [[i.1]](#[i.1]) were also taken into account, namely: +The present document is a technical specification of SAREF4CITY, an extension of SAREF [[1]](#[1]) for the Smart Cities domain. + +SAREF4CITY V2.1.1 is a major revision of SAREF4CITY, using updated reference ontology patterns specified in ETSI TS 103 548 [2] to solve the harmonization needs identified in ETSI TR 103 781 [i.2], with updated development framework and tools defined in ETSI TS 103 673 [3]. + +This extension has been created by investigating resources from potential stakeholders of the ontology, such as standardization bodies (e.g. Open Geospatial Consortium), associations (e.g. Spanish Federation of Municipalities and Provinces), IoT platforms (e.g. FIWARE) and European projects and initiatives (e.g. ISA2 programme) as reported in ETSI TR 103 506 [[i.1]](#[i.1]). In addition, the use cases defined in [[i.1]](#[i.1]) were also taken into account, namely: - Use case 1: eHealth and Smart Parking. - Use case 2: Air Quality Monitoring and Mobility. @@ -8,7 +12,10 @@ Taking into account ontologies, data models, standards and datasets provided by After the first complete implementation of the ontology, a second validation workshop, the "Towards interoperability and harmonization of Smart City models with SAREF4CITY" one, took place on the 22nd of November 2018 at the European Commission premises in Brussels. During the workshop the ontology was presented to a variety of stakeholders from industry to academia and public administration. Apart from observations and comments on the reuse and alignment with other ontologies, the discussion addressed more general questions like how to promote the adoption of SAREF or which is the technological and methodological support needed to create a SAREF ecosystem of collaborative ontologies. -SAREF4CITY is an OWL-DL ontology that extends SAREF and reuses six other ontologies. SAREF4CITY includes 31 classes (13 defined in SAREF4CITY and 18 reused from the SAREF, time, geosp, geo, foaf, dcterms, org, cpsv, and time ontologies), 36 object properties (20 defined in SAREF4CITY and 16 reused from the SAREF, geosp, geo, and cpsv ontologies) and 7 data type properties (3 defined in SAREF4CITY and 4 reused from the SAREF ontology). +The current version of the ontology, V2.1.1, represents the adaptation of the previous SAREF4CITY conceptualization according to the new SAREF core and the homogenization process across extensions. + +SAREF4CITY is an OWL-DL ontology that extends SAREF and reuses seven other ontologies. SAREF4CITY includes 124 classes (13 defined in SAREF4CITY and 111 reused from the SAREF, time, sf, geo, foaf, dc, org, cpsv, skos and time ontologies), 103 object properties (18 defined in SAREF4CITY and 85 reused from the SAREF, geo, skos and cpsv ontologies) and 13 data type properties (6 defined in SAREF4CITY and 4 reused from the SAREF ontology). + SAREF4CITY focuses on extending SAREF in order to create a common core of general concepts for smart city data oriented to the IoT field. The main idea is to identify the core components, as mentioned, that could be extended for particular smart city subdomains, for example, for public transport. diff --git a/documentation/description.html b/documentation/description.html index 699e3586eba33bc6b5bccd0b3f850251e7e4b81a..fa9b754b1c0bf1704626d77e80074b549a9de5fa 100644 --- a/documentation/description.html +++ b/documentation/description.html @@ -22,7 +22,7 @@

Topology

-

In the SAREF4CITY ontology existing models have been reused when needed in order to increase interoperability and reduce effort in modelling general domains. As an example, for modelling the requirements related to the topology domain, standard ontologies already developed have been reused and connected to the SARE4CITY elements. As shown in Figure 2, for representing spatial objects the geosp:SpatialObject class from GeoSPARQL has been reused along with its subclasses geosp:Feature, geosp:Geometry and the properties geosp:sfContains, geosp:sfWithin and geosp:hasGeometry. In addition, the class geo:Point and the property geo:location have been reused from the W3C de-facto standard for geographical information "WGS84 Geo Positioning vocabulary" in order to be able to indicate that something is located at certain coordinates.

+

In the SAREF4CITY ontology existing models have been reused when needed in order to increase interoperability and reduce effort in modelling general domains. As an example, for modelling the requirements related to the topology domain, standard ontologies already developed have been reused and connected to the SARE4CITY elements. As shown in Figure 2, for representing spatial objects the geo:SpatialObject class from GeoSPARQL has been reused along with its subclasses geo:Feature, geo:Geometry and the classes from the simple features ontology sf:Geometry and sf:Point and the properties geo:sfContains, geo:sfWithin and geo:hasGeometry.

@@ -33,7 +33,7 @@

Administrative Area

-

The model defined to describe administrative areas is depicted in Figure 3. As it can be observed, this model heavily relies on the topology pattern described in clause 4.2.2. In this sense, the ability to connect administrative areas (e.g. a city) with their inner areas, (e.g. its neighbourhoods) is given by inheritance of the geosp:SpatialObject class and through the geosp:Feature class. That is, as s4city:AdministrativeArea is subclass of geosp:SpatialObject, the geosp:sfContains and geosp:sfWithin properties could also be applied to all the administrative areas defined, namely s4city:City, s4city:Country, s4city:District and s4city:Neighbourhood.

+

The model defined to describe administrative areas is depicted in Figure 3. As it can be observed, this model heavily relies on the topology pattern described in clause 4.2.2. In this sense, the ability to connect administrative areas (e.g. a city) with their inner areas, (e.g. its neighbourhoods) is given by inheritance of the geo:SpatialObject class and through the geo:Feature class. That is, as s4city:AdministrativeArea is subclass of geo:SpatialObject, the geo:sfContains and geo:sfWithin properties could also be applied to all the administrative areas defined, namely s4city:City, s4city:Country, s4city:District and s4city:Neighbourhood.

Administrative Area model @@ -42,7 +42,7 @@

City Object

-

The model developed to represent city objects is shown in Figure 4. This model also relies on the topology pattern described in clause 4.2.2, as for the administrative area case. The ability to connect city objects with the city or with the parts in which they are located is enabled by means of the properties geosp:sfContains and geosp:sfWithin inherited from the geosp:SpatialObject class.

+

The model developed to represent city objects is shown in Figure 4. This model also relies on the topology pattern described in clause 4.2.2, as for the administrative area case. The ability to connect city objects with the city or with the parts in which they are located is enabled by means of the properties geo:sfContains and geo:sfWithin inherited from the geo:SpatialObject class.

City Object model @@ -59,49 +59,47 @@
-

Measurement

- -

As it can be observed in Figure 6, the modelling of measurements in the SAREF4CITY ontology totally relies on the measurement model proposed in SAREF. This modelling includes the saref:FeatureOfInterest class that provides the means to refer to the real world phenomena that is being observed in the given measurement. In order to reduce duplication with SAREF documentation, the reader is referred to the SAREF specification for details about SAREF modelling including here details only for the new concepts.

- -
- Measurement model -
Figure 6: Measurement model
-
+

Observation

+

The modelling of observation in the SAREF4CITY ontology totally relies on the observation model proposed in SAREF. This modelling includes the saref:FeatureOfInterest class that provides the means to refer to the real world phenomena that is being observed in the given measurement. In order to reduce duplication with SAREF documentation, the reader is referred to the SAREF specification for details about SAREF modelling including here details only for the new concepts.

Key Performance Indicator

-Figure 7 provides an overview of the modelling of Key Performance Indicators (KPI). The KPI modelling involves two main concepts, namely s4city:KeyPerformanceIndicator and s4city:KeyPerformanceIndicatorAssessment. This distinction is needed to decouple the definition of a KPI in general terms, for example the mean air pollution per week, and a particular value of such KPI, for example the mean value of air pollution last week in Madrid. +Figure 6 provides an overview of the modelling of Key Performance Indicators (KPI). The KPI modelling involves two main concepts, namely s4city:KeyPerformanceIndicator and s4city:KeyPerformanceIndicatorAssessment. This distinction is needed to decouple the definition of a KPI in general terms, for example the mean air pollution per week, and a particular value of such KPI, for example the mean value of air pollution last week in Madrid.

A s4city:KeyPerformanceIndicator is related to a saref:FeatureOfInterest by means of the property s4city:isKPIOf. It should be noted that the inverse relation of s4city:isKPIOf is also defined, more precisely, the relation s4city:hasKPI links a given saref:FeatureOfInterest to its KPIs represented as instances of s4city:KeyPerformanceIndicator. The calculation period of a s4city:KeyPerformanceIndicator is indicated by the property s4city:hasCalculationPeriod. The name and a natural language description of the s4city:KeyPerformanceIndicator are indicated by the attributes s4city:hasName and s4city:hasDescription, respectively.

-

The relation between a specific assessment of a KPI (s4city:KeyPerformanceIndicatorAssessment) and the general KPI definition (s4city:KeyPerformanceIndicator) can be established by means of the property s4city:quantifiesKPI. A s4city:KeyPerformanceIndicatorAssessment is related to the saref:FeatureOfInterest by means of the property s4city:assesses. The temporal entity to which the assessment of the KPI refers to is represented by the property s4city:refersToTime. The agent assessing the KPI is linked by means of the property s4city:isAssessedBy. In order to express the administrative area or geographical location assessed by the KPI, the property s4city:refersToSpace is included in the model. In case the KPI represents a value extracted from an aggregation of measurements, the property s4city:isDerivedFrom can be used to link to such measurements (saref:Measurement). The unit of measure in which a KPI value is expressed is indicated by means of the reused property saref:isMeasuredIn while the value itself is indicated by the attribute saref:hasValue. The name and a natural language description of the s4city:KeyPerformanceIndicatorAssessment are indicated by the attributes s4city:hasName and s4city:hasDescription, respectively. The creation, expiration and last update dates of the value are represented by the attributes s4city:hasCreationDate, s4city:hasExpirationDate and s4city:hasLastUpdateDate, respectively.

+

The relation between a specific assessment of a KPI (s4city:KeyPerformanceIndicatorAssessment) and the general KPI definition (s4city:KeyPerformanceIndicator) can be established by means of the property s4city:quantifiesKPI. A s4city:KeyPerformanceIndicatorAssessment is related to the saref:FeatureOfInterest by means of the property s4city:assesses. The temporal entity to which the assessment of the KPI refers to is represented by the property s4city:refersToTime. The agent assessing the KPI is linked by means of the property s4city:isAssessedBy. In order to express the administrative area or geographical location assessed by the KPI, the property s4city:refersToFeature is included in the model. In case the KPI represents a value extracted from an aggregation of observations, the property s4city:isDerivedFrom can be used to link to such observations (saref:Observation). The unit of measure in which a KPI value is expressed is indicated by means of the reused property saref:isMeasuredIn while the value itself is indicated by the attribute saref:hasValue. The name and a natural language description of the s4city:KeyPerformanceIndicatorAssessment are indicated by the attributes s4city:hasName and s4city:hasDescription, respectively. The creation, expiration and last update dates of the value are represented by the attributes s4city:hasCreationDate, s4city:hasExpirationDate and s4city:hasLastUpdateDate, respectively.

Key Performance Indicator model -
Figure 7: Key Performance Indicator model
+
Figure 6: Key Performance Indicator model

Public Service

-

The model developed to describe public services within the SAREF4CITY ontology is depicted in Figure 8. The main entity included is the s4city:PublicService class which is a specialization of the reused concept cpsv:PublicService class defined in the Public Service vocabulary provided by the ISA vocabularies European initiative. The facility in which the service is provided is indicated by the s4city:involvesFacility property. It can be also possible to indicate in which administrative area it is provided, for example a neighbourhood, by means of the property cpsv:physicallyAvailableAt. The public services that an agent (s4city:Agent) provides or uses are indicated by means of the properties cpsv:provides and cpsv:uses, respectively. The languages in which a service is provided are indicated by the property s4city:isAvailableInLanguage. The name and a natural language description of the s4city:PublicService are indicated by the attributes s4city:hasName and s4city:hasDescription, respectively.

+

The model developed to describe public services within the SAREF4CITY ontology is depicted in Figure 7. The main entity included is the s4city:PublicService class which is a specialization of the reused concept cpsv:PublicService class defined in the Public Service vocabulary provided by the ISA vocabularies European initiative. The facility in which the service is provided is indicated by the s4city:involvesFacility property. It can be also possible to indicate in which administrative area it is provided, for example a neighbourhood, by means of the property cpsv:physicallyAvailableAt. The public services that an agent (s4city:Agent) provides or uses are indicated by means of the properties cpsv:provides and cpsv:uses, respectively. The languages in which a service is provided are indicated by the property s4city:isAvailableInLanguage. The name and a natural language description of the s4city:PublicService are indicated by the attributes s4city:hasName and s4city:hasDescription, respectively.

Public Service model -
Figure 8: Public Service model
+
Figure 7: Public Service model
+ diff --git a/documentation/examples.html b/documentation/examples.html new file mode 100644 index 0000000000000000000000000000000000000000..be3608d7adf032503b52a442b469fbba9fc9f19a --- /dev/null +++ b/documentation/examples.html @@ -0,0 +1,13 @@ +

Figure 8 shows an example of how to instantiate the SAREF4CITY extension of SAREF. This example shows the use of different patterns included in the SAREF4CITY ontology. First of all, a camera (ex:Camera1) measures the speed of a car (ex:Car35) in the information attached to the individual ex:Camera1Measurement200, which provides a value of 35 Km/hour. The position of the car at that moment is captured by the instance ex:CarLocation2018-11-20T13-30-00 with points to the geographical coordinates in which the car is located and also to the road segment in which it is included. It can be observed that such road segment might contain (see property geo:sf:Contains) other city objects such as a lamppost or a building.

+ +

The KPI pattern is also instantiated in the example. The instance ex:RoadSegment50Congestion2018-11-20T13-30-00 refer to the value (70 %) of the road congestion on the 2018-11-20 at 13:20. Such value is assessed by the public administration ex:City4. In the calculation of such value the speed of the cars (ex:CarsSpeed2018-11-20), the pollution (ex:Polution2018-11-20) and the GMaps API (ex:GMapsAPI2018-11-20) values have been taken into account as it can be observed from the s4city:isDerivedFrom property between the KPI value and the different saref:Observation instances.

+ +

In the example the event ex:BasketMatch23, as sub event of the ex:BasketWeek2018, is described. It can be seen that the match is accessible by metro, is organized by ex:City4 and takes place at the facility ex:BasketArena7. +Finally, some examples of public services are shown. One service example is the ex:HealthService123 that involves the facility ex:BasketArena7 and is available in Spanish. Such service is available in area ex:Neighbourhood34 that is contained in ex:City4, which is the service provider organization. In addition, another service, ex:BusService33, is provided by another organization, in this case ex:TransportCo.

+ + +
+ Road Congestion exampleexample +
Figure 8: Road Congestion example
+
+ diff --git a/documentation/references.html b/documentation/references.html index 23828e3aec8fe30a606bf7cd44fc37c1a620bfb3..39d620e9b957e394508a6ee463dd3a04cf4331f2 100644 --- a/documentation/references.html +++ b/documentation/references.html @@ -2,10 +2,13 @@

Informative references