- Issue created by @fishfree
- 🇩🇪Germany Knurg
You can't! They are populated from your ontology when loading the ontology. :)
Cheers
- Status changed to Closed: works as designed
9 months ago 8:53am 29 February 2024 - 🇨🇳China fishfree
@Knurg Why the namespaces defined in this ontology (and the related doc) don't show up?
- Status changed to Active
9 months ago 9:53pm 7 March 2024 - 🇩🇪Germany Knurg
You go to Configuration -> WissKI Ontology and load this ontology by providing the URL. According to the Ontology the URL should be the base namespace (https://renie26.github.io/homepage.github.io/resource/ont/MAoCorpus/MAon... has http://EncodingActs.github.io/annotated/MAon# as base namespace). However http://EncodingActs.github.io/annotated/MAon# gives me a 404 neither the base namespace nor the file on github do fulfill the requirements from the "Best Practice Recipes for Publishing RDF Vocabularies" (https://www.w3.org/TR/swbp-vocab-pub/). So in fact this ontology is a worst praxis example for a not-really-linked-open-data (without wanting to offend anybody - they probably do their best!).
So this probably can't be loaded from WissKI properly and there is only a workaround possible which is directly loading the ontology to the triplestore into a named graph "http://EncodingActs.github.io/annotated/MAon#". However this does not give you any namespaces - that simply does not work with work-arounded ontologies.... We do not really intend to support worst-practices :/ But you should not have any drawbacks from that other than a not-so-beautiful pathbuilder...
Sorry!
- 🇨🇳China fishfree
@Knurg Thank you for your important tip! Would you please share me a published properly working WissKI compatible ontology file or link?
- 🇩🇪Germany Knurg
Dear all,
no, especially that is NOT one of the compatible links. http://erlangen-crm.org/231027/ is - it is set to download the ontology if you access the link directly and it works as intended :)
Cheers!
- Status changed to Closed: works as designed
8 months ago 5:32am 12 March 2024