Home
An automated asynchronous Linked Data quality evaluation framework. __Because [5 stars](http://www.w3.org/DesignIssues/LinkedData.html) aren't enough.__
To realize its value, Linked Data must be used. But how good is any part of the linked data cloud? Does it suit best practices? Is it complete for a given application? Is it accurate, connected -- consistent? The DataFAQs linked data evaluation framework is being designed to provide automated, asynchronous feedback to Publishers, Curators, and Consumers about relevant portions of the cloud. Let's accelerate the health of Linked Data.
- Integration tools
- LOD Cloud on CKAN
- Validation tools
- SADI Semantic Web Services framework
- FAqT Service and vocabulary
- Sample FAqT deployment
- FAqT Brick of accumulated results
Why we're doing this:
About FAqT evaluation services:
- SADI Semantic Web Services framework - an existing web services framework (that finally got it right!).
- FAqT Service - SADI service that evaluates datasets.
- FAqT Vocabulary - that FAqTs can/should use to be helpful in a DataFAQs environment.
- Sample FAqT deployment - they sit on the web and wait for datasets to evaluate.
- FAqT Brick - accumulation of FAqT evaluations of datasets over time.
- DataFAQs Core Services - SADI services that provide configurations for a FAqT Brick.
About datasets:
- CKAN - An existing dataset cataloging architecture.
- CKAN lodcloud RDF vocabulary - an RDFS encoding of the implicit relations encoded by the lodcloud group.
- Missing CKAN API Key - is needed to make changes to CKAN via their API.
- DCAT Data Catalog Vocabulary - another convention from which one can find out about datasets.
- LOD Cloud - the subset of Linked Data that is in the lodcloud CKAN group.
Analyzing what we have:
- LODSPeaKr - Linked Data publishing kit that we're using to analyze the FAqT Brick.
- Evaluating evaluators
Some implementation details:
Related work:
- Pedantic Web Group
- Integration tools
- Validation tools
- Testing apparatuses
- frbr:lebo2012datafaqs