You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some of these issues are due to the limitations of hosting on Github. For example, we can't host a URL that can resolve into an HTML document based on an HTTP request.
Many issues have to do with metadata that could be easy to add.
For some reason, the validator is not picking up the fact we are generating SKOS documentation for all of our declared classes and properties, which would raise our reusability.
Some things we can do to improve the score are:
register ontology uris with w3id, purl, DOI or W3C
make ontology uris the same as their github raw content url
although this is technically a minor pitfall in OOPS, this is likely impossible to avoid when using Github
we could try storing our ontology files without a file type?
properly add version uris
add triple metadata! at minimum:
title
description
license (make sure the license declaration actually resolves for bonus points)
version iri
creator
author *
creationDate *
namespace URI
declare a prefix in each ontology
register metadata with LOV:
ontology prefix
ontology URL/URI
minimum metadata (same as above)
add other metadata such as:
doi
previous version *
contributor *
publisher *
logo
backwards compatibility
status
modified
source
issued date *
* provenance metadata: this is worth bonus point in FAIR assessments
Looks like we're failing miserably at FAIRness standards (at least outside of interoperability)
The proposed CityGML 3.0 core ontology scored 23% on the FOOPS validator. Below is a breakdown of the results:
Some of these issues are due to the limitations of hosting on Github. For example, we can't host a URL that can resolve into an HTML document based on an HTTP request.
Many issues have to do with metadata that could be easy to add.
For some reason, the validator is not picking up the fact we are generating SKOS documentation for all of our declared classes and properties, which would raise our reusability.
Some things we can do to improve the score are:
* provenance metadata: this is worth bonus point in FAIR assessments
Originally posted by @DiegoVinasco in #19 (comment)
The text was updated successfully, but these errors were encountered: