Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validation of services based on ontology #67

Closed
akuckartz opened this issue Jul 28, 2014 · 4 comments
Closed

Validation of services based on ontology #67

akuckartz opened this issue Jul 28, 2014 · 4 comments

Comments

@akuckartz
Copy link

Validation of services can be done by using formal ontologies. No specific syntactic validation is necessary because this can be done implicitely by using JSON-LD libraries.

Collaboration with the Hydra W3C CG and the new validation WG of the W3C will be helpful.

@akuckartz
Copy link
Author

A lot of interesting material was produced for and by this workshop:

RDF Validation Workshop
Practical Assurances for Quality RDF Data
10-11 September 2013, Cambridge, MA, USA
http://www.w3.org/2012/12/rdf-val/

This workshop also is the basis on which the W3C is discussing a charter for a WG.

Examples of RDF Validation
http://www.w3.org/2012/12/rdf-val/SOTA

Parts of a test-suite created for JSON-LD are reusable:
https://github.com/json-ld/json-ld.org/tree/master/test-suite

@akuckartz
Copy link
Author

Hydra is experimenting with RDFUnit (https://github.com/AKSW/RDFUnit) for validation purposes. Seems to be usable.

Quick guide:

Example:

@akuckartz
Copy link
Author

The mission of the RDF Data Shapes Working Group is to produce a language for defining structural constraints on RDF graphs. In the same way that SPARQL made it possible to query RDF data, the product of the RDF Data Shapes WG will enable the definition of graph topologies for interface specification, code development, and data verification.

RDF Data Shapes Working Group Charter
http://www.w3.org/2014/data-shapes/charter

@akuckartz
Copy link
Author

akuckartz commented Jun 12, 2015

Work will proceed in #137 - therefore closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant