SOD1 - Evaluating and Publishing Data Concerns for Data-as-a-Service (DaaS)
This page provides some supplement materials for the paper:
Here are two simple examples to demonstrate the relationship
between the DaaS data provider and DaaS service provider in
the development of DaaS:
Here are three examples to demonstrate the evaluation and publishing
of data concerns with the Adult literacy rate percent data set
of the UNDataAPI:
- Without specifying any QoD request, a call of our test service:
http://localhost:8080/concernsmodels/resources/undata/Adult_literacy_rate_percent will return the following result (which is the same data provided by the UNDataAPI).
- By querying only QoD metrics through a call of our test service:
http://localhost:8080/concernsmodels/resources/undata/Adult_literacy_rate_percent?QoD, the QoD metrics are evaluated on the fly and the data consumer will receive the following result. The QoD metrics are described using a custom QoD schema based on the data concern analysis work.
- Through a call of our test service:
http://localhost:8080/concernsmodels/resources/undata/Adult_literacy_rate_percent?QoD=annotation, QoD metrics will be evaluated and annotated with the data as shown in the following result.
The common data concern publishing (DCP) specification is an example of how
to publish data concerns with services, service operations and
data resources. In principle, we allow any data concern model
to be included.
Note that one can use this specification with their own service
registries or Atom feeds. Other approaches could use it together
with WSDL, SAWSDL, hREST, etc.
Contact Hong-Linh
Truong for comments and further information.
