The range of inSubset should be an IRI, not a literal #1527
Assignees
Comments
|
As of also
|
SELECT ?o (COUNT(?s) AS ?s_count)
(IF(isIRI(?o), "IRI", "Literal") AS ?type)
WHERE {
?s <http://www.geneontology.org/formats/oboInOwl#inSubset> ?o .
}
GROUP BY ?o |
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
SELECT ?s (GROUP_CONCAT(?c;
SEPARATOR=" | ") AS ?comments)
WHERE {
?s rdfs:subPropertyOf+ <http://www.geneontology.org/formats/oboInOwl#SubsetProperty> .
OPTIONAL {
?s rdfs:comment ?c
}
}
GROUP BY ?s
order by ?s |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The range of inSubset should be an IRI, not a string literal. We have a mix at the moment
valid:
not valid:
These are the counts of invalids
environmental_hazards|90
envoAstro|72
envoAtmo|111
envoCesab|5
envoCloudAtlas|10
envoCmecs|36
envoCryo|40
envoEOVs|9
envoEmpo|37
envoMarine|62
envoMeo|27
envoNceas|22
envoOmics|35
envoPlastics|69
envoPolar|442
nlcd2011|22
subset_siren|37
wwfBiome|41
We already have IRIs defined for the subsets - nothing links to them so far
Note: this issue should not be used for discussing whether we use inSubset or a different AP. We have a different mega-ticket for this: #1202. Fixing the current ranges does not preclude using a different AP in the future, and would be a good incremental step towards this goal.
The text was updated successfully, but these errors were encountered: