...
| Développer |
|---|
| title | Voir le rapport qSkos |
|---|
|
| Html-bobswift |
|---|
<pre><font color="#12488B"><b>~/qSKOS/target</b></font>$ java -jar qSKOS-cmd.jar analyze -dc mil,bl ../jel_2024.rdf -o report.txt
Initializing evaluation repository for jel_2024.rdf...
trying to create report file report.txt
file.exists()=false
file.canRead()=false
file.canWrite()=false
file.canExecute()=false
Processing issue 1 of 27 (Empty Labels)
Processing issue 2 of 27 (Omitted or Invalid Language Tags)
Processing issue 3 of 27 (Incomplete Language Coverage)
Processing issue 4 of 27 (Undocumented Concepts)
guessing publishing host
Guessed authoritative resource identifier: 'zbw.eu'
Processing issue 5 of 27 (No Common Languages)
Processing issue 6 of 27 (Missing Labels)
Processing issue 7 of 27 (Overlapping Labels)
Collecting resource labels
Processing issue 8 of 27 (Orphan Concepts)
Processing issue 9 of 27 (Disconnected Concept Clusters)
Processing issue 10 of 27 (Cyclic Hierarchical Relations)
Creating hierarchy graph
Processing issue 11 of 27 (Valueless Associative Relations)
Processing issue 12 of 27 (Solely Transitively Related Concepts)
Processing issue 13 of 27 (Omitted Top Concepts)
Processing issue 14 of 27 (Top Concepts Having Broader Concepts)
Processing issue 15 of 27 (Hierarchical Redundancy)
Processing issue 16 of 27 (Mapping Relations Misuse)
Processing issue 17 of 27 (Reflexively Related Concepts)
Processing issue 18 of 27 (Ambiguous Notation References)
Processing issue 19 of 27 (Unprintable Characters in Labels)
Processing issue 20 of 27 (Missing Out-Links)
finding resources
Processing issue 21 of 27 (Undefined SKOS Resources)
Processing issue 22 of 27 (Unidirectionally Related Concepts)
Processing issue 23 of 27 (HTTP IRI Scheme Violation)
Processing issue 24 of 27 (Relation Clashes)
Processing issue 25 of 27 (Mapping Clashes)
Processing issue 26 of 27 (Inconsistent Preferred Labels)
Processing issue 27 of 27 (Disjoint Labels Violation)
Report complete!
* Summary of Quality Issue Occurrences:
Empty Labels: OK (no potential problems found)
Omitted or Invalid Language Tags: OK (no potential problems found)
Incomplete Language Coverage: OK (no potential problems found)
Undocumented Concepts: FAIL (997)
No Common Languages: OK (no potential problems found)
Missing Labels: OK (no potential problems found)
Overlapping Labels: FAIL (365)
Orphan Concepts: OK (no potential problems found)
Disconnected Concept Clusters: FAIL (20)
Cyclic Hierarchical Relations: OK (no potential problems found)
Valueless Associative Relations: OK (no potential problems found)
Solely Transitively Related Concepts: OK (no potential problems found)
Omitted Top Concepts: FAIL (1)
Top Concepts Having Broader Concepts: OK (no potential problems found)
Hierarchical Redundancy: OK (no potential problems found)
Mapping Relations Misuse: OK (no potential problems found)
Reflexively Related Concepts: OK (no potential problems found)
Ambiguous Notation References: OK (no potential problems found)
Unprintable Characters in Labels: OK (no potential problems found)
Missing Out-Links: FAIL (997)
Undefined SKOS Resources: OK (no potential problems found)
Unidirectionally Related Concepts: FAIL (977)
HTTP IRI Scheme Violation: FAIL (1)
Relation Clashes: OK (no potential problems found)
Mapping Clashes: OK (no potential problems found)
Inconsistent Preferred Labels: OK (no potential problems found)
Disjoint Labels Violation: OK (no potential problems found)
</pre> |
|
Zéro erreur 
sur erreur sur les critères de qualité essentiels ! Une performance quperformance qu'on se doit de saluer.
Pour nous, voilà qui offrait une vraie issue : une fois le vocabulaire récupéré, il suffisait de le charger dans un serveur adapté aux données sémantiques (Apache Jena Fuseki) et d'empaqueter le tout dans un container Docker !
...
- le Leibniz-Informationszentrum Wirtschaft corrige 🔧 les problèmes de son serveur
- ... ou publie une nouvelle version du vocabulaire JEL...
- ... ou que HAL ou une autre institution publie le vocabulaire dans son propre domaine...
- ... ou que HAL remplace les codes par des URI dans les données...
Notre solution n'apparaîtra plus que comme un bricolage provisoire qui aura vocation à être modifié ou remplacé !Le cas des économistes étant traité, c'est le tour des médecins : dans un prochain billet, nous essaierons d'exploiter la classification Mesh au sein des données HAL.
...
Notes
...