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

probleme pour detecter Hierarchical Redundancy #14

Open
croussey opened this issue May 13, 2024 · 1 comment
Open

probleme pour detecter Hierarchical Redundancy #14

croussey opened this issue May 13, 2024 · 1 comment

Comments

@croussey
Copy link

Bonjour
dans mon fichier rdf plusieurs concept schemes sont declarés ainsi il est possible d'avoir aussi les liens broadMatch narrowMatch.
des redundances hierarchiques entre concept appartenant à des concepts schemes differents sont detectés.
sauf que la redundance hierarchique ne s'applique que sur les concepts d'un meme concept scheme, d'apres la doc
https://github.com/cmader/qSKOS/wiki/Quality-Issues#hierarchical-redundancy

voir le gitlab institutionnel https://gitlab.irstea.fr/copain/phenologicalstages
dans le repertoire grapevine
le fichier grapevine_scales_latest.rdf
le fichier owl est visible aussi sur agroportal https://agroportal.lirmm.fr/ontologies/PPD-GV

@tfrancart
Copy link
Collaborator

image

e.g. [ https://opendata.inrae.fr/ppd-res/grapevine#bbch_grapevine_secondaryStage_BBCH67 - https://opendata.inrae.fr/ppd-res/grapevine#bbch_grapevine_principalStage_BBCH6 ]

We have this in the file

<https://opendata.inrae.fr/ppd-res/grapevine#bbch_grapevine_secondaryStage_BBCH67> skos:broader <https://opendata.inrae.fr/ppd-res/grapevine#bbch_grapevine_principalStage_BBCH6> .
<https://opendata.inrae.fr/ppd-res/grapevine#bbch_grapevine_secondaryStage_BBCH67> skos:broadMatch <https://opendata.inrae.fr/ppd-res/grapevine#ifv_epicure_grapevine_secondaryStage_24> .
<https://opendata.inrae.fr/ppd-res/grapevine#ifv_epicure_grapevine_secondaryStage_24> skos:broadMatch <https://opendata.inrae.fr/ppd-res/grapevine#bbch_grapevine_principalStage_BBCH6> .

<https://opendata.inrae.fr/ppd-res/grapevine#bbch_grapevine_secondaryStage_BBCH67> skos:inScheme <https://opendata.inrae.fr/ppd-res/grapevine#bbch_individualScale_grapevine> .
<https://opendata.inrae.fr/ppd-res/grapevine#bbch_grapevine_secondaryStage_BBCH6> skos:inScheme <https://opendata.inrae.fr/ppd-res/grapevine#bbch_individualScale_grapevine> .
<https://opendata.inrae.fr/ppd-res/grapevine#ifv_epicure_grapevine_secondaryStage_24> skos:inScheme <https://opendata.inrae.fr/ppd-res/grapevine#ifv_epicure_scale_grapevine>

and indeed https://opendata.inrae.fr/ppd-res/grapevine#ifv_epicure_grapevine_secondaryStage_24 does not belong to the same scheme.

I think the practice is usually not to have multiple schemes in one files, hence the qSkos hierarchy builder does not check whether the concepts in the hierarchy actually belong to different schemes or not. This is on qSkos side, I can't do anything here.

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

No branches or pull requests

2 participants