Requirements Coverage
5 Requirements Coverage
In this section we will re-‐visit the requirements listed in Section 2. The table below summarises all the requirements that concerns the RDF formalisms and ontologies. Following, we discuss how these requirements were addressed in this deliverable.
Table 4 – Requirements concerning the RDF formalisms and Ontologies
ID Description
Type
Priority
The GAMBAS framework should be able to support Operational GE_001
1 -‐ High different devices.
requirements
The GAMBAS framework simplifies the development of The purpose of the GE_008
1 -‐ High services that acquire data from different devices.
product
The GAMBAS framework enables the development of The purpose of the GE_009
1 -‐ High composed services.
product
The application services are able to aggregate and Relevant facts and GE_015
1 -‐ High share crowd levels from busses.
assumptions
The GAMBAS
GE_016 environmental quality data for a geolocated point in The scope of the work 1 -‐ High the city.
The application services are able to aggregate and Relevant facts and GE_019
1 -‐ High share environmental information.
assumptions
The data representation must provide a unified view of Functional and data DQ_001
1 -‐ High the data among connected devices and services.
requirements
The data representation and query language should be Functional and data DQ_005
2 -‐ Medium generic.
requirements
The data representation must support spatial data in Functional and data DQ_006
1 -‐ High different formats.
requirements
The data representation should provide a data model Functional and data DQ_011
1 -‐ High for the information relevant to the use cases.
requirements
Functional and data DQ_012 The data representation should be extensible.
2 -‐ Medium
requirements
The data representation and query processing Functional and data DQ_014
1 -‐ High framework should be interoperable.
requirements
The data representation should provide support for Functional and data DQ_016
1 -‐ High context generalizations.
requirements
The data representation should be based on Linked Functional and data DQ_018
1 -‐ High Data principles.
requirements
• GE_001, GE_008, GE_009: The RDF formalisms and ontologies provide a unified data representation and query language, regardless of the device. Allowing data from heterogeneous
sources to be easily integrated.
• GE_015, GE_16, GE_019: Environmental information (i.e. noise level, pollen count, CO2 levels, etc), as well as crowd level information are represented in the ontology and therefore can be queried and further processed.
• DQ_001, DQ_005: The ontology provides the vocabulary for a unified representation of the data in the GAMBAS framework. Both RDF and SPARQL – the data format and query language used – are generic and widely used. The CQELS language for stream processing is very close to SPARQL which favours adoption by SPARQL users. Moreover, RDF can be easily serialised to other data formats.
• DQ_006: The Place class allows different representations of spatial data. • DQ_011, DQ_012: The GAMBAS ontology provides a model to describe the data from the
GAMBAS use cases. Its modular, which makes it easy to extend. At any time, new classes and properties can be added, with minimum effort. This has already been done in this new version of the deliverable. The ontology can be further extended, if needed.
• DQ_014: By using the RDF and SPARLQ/CQELS standards, we have guaranteed that the data model and query language are interoperable. This can be seen in the query examples presented in this deliverable.
• DQ_016: One of the properties of ontologies is to allow context generalisations. As example, two new sub classes of Activity were added in this version of the deliverable. In addition, other means of transport can be added to the Transport Mode class. Queries can be performed at any level on this class hierarchy. That means that, for example, one can query for any activity a user has perform, regardless of its type.
• DQ_18: The RDF and SPARQL/CQELS standards both follow the Linked Data principles. In
addition, each instance of a class will have a URI as unique identifier that is dereferenceable.