Search
116 results for “janmartinkeil”
-
A great tool for improving ontology quality and best practices — thanks for sharing this at #HMCConference2026.
Definitely worth exploring!
-
@janmartinkeil It was more a high level overview of this field, this event is to network with other fields to exchange knowledge and ideas.
Regarding your points (my view):
Ontologies are more like the description of how the data is modeled. For example, the ontology #FOAF says `foaf:Person` is a Person. While the #KnowledgeGraph (KG) will have `<Dylan> rdf:type foaf:Person` to say that I'm a person modeled according to the FOAF ontology. The data in the KG is modeled after the ontology.
-
Atanas Kiryakov, President of Graphwise, in his keynote at ESWC points out a merging advantage of (re-)using public ontologies: LLMs already know these ontologies, which increases the interoperability of the data by making use of knowledge graphs as context easier and cheaper.
-
Atanas Kiryakov, President of Graphwise, in his keynote at ESWC points out a merging advantage of (re-)using public ontologies: LLMs already know these ontologies, which increases the interoperability of the data by making use of knowledge graphs as context easier and cheaper.
-
Atanas Kiryakov, President of Graphwise, in his keynote at ESWC points out a merging advantage of (re-)using public ontologies: LLMs already know these ontologies, which increases the interoperability of the data by making use of knowledge graphs as context easier and cheaper.
-
Atanas Kiryakov, President of Graphwise, in his keynote at ESWC points out a merging advantage of (re-)using public ontologies: LLMs already know these ontologies, which increases the interoperability of the data by making use of knowledge graphs as context easier and cheaper.
-
Atanas Kiryakov, President of Graphwise, in his keynote at ESWC points out a merging advantage of (re-)using public ontologies: LLMs already know these ontologies, which increases the interoperability of the data by making use of knowledge graphs as context easier and cheaper.
-
@w3c
The RDF version of SKOS [1] does not contain a licensing information, other than e.g. SSN [2] or DCAT3 [3]. Is it permitted to distribute (parts of) it and under which conditions? Does the W3C Software license [4] or the W3C Document license [5] apply to it, and if yes, which version? Could a licensing statement be added?1. https://www.w3.org/2009/08/skos-reference/skos.rdf
2. https://www.w3.org/ns/ssn/ssn.rdf
3. https://www.w3.org/ns/dcat3.ttl
4. https://www.w3.org/copyright/software-license-2023/
5. https://www.w3.org/copyright/document-license-2023/ -
@w3c
The RDF version of SKOS [1] does not contain a licensing information, other than e.g. SSN [2] or DCAT3 [3]. Is it permitted to distribute (parts of) it and under which conditions? Does the W3C Software license [4] or the W3C Document license [5] apply to it, and if yes, which version? Could a licensing statement be added?1. https://www.w3.org/2009/08/skos-reference/skos.rdf
2. https://www.w3.org/ns/ssn/ssn.rdf
3. https://www.w3.org/ns/dcat3.ttl
4. https://www.w3.org/copyright/software-license-2023/
5. https://www.w3.org/copyright/document-license-2023/ -
@w3c
The RDF version of SKOS [1] does not contain a licensing information, other than e.g. SSN [2] or DCAT3 [3]. Is it permitted to distribute (parts of) it and under which conditions? Does the W3C Software license [4] or the W3C Document license [5] apply to it, and if yes, which version? Could a licensing statement be added?1. https://www.w3.org/2009/08/skos-reference/skos.rdf
2. https://www.w3.org/ns/ssn/ssn.rdf
3. https://www.w3.org/ns/dcat3.ttl
4. https://www.w3.org/copyright/software-license-2023/
5. https://www.w3.org/copyright/document-license-2023/ -
@w3c
The RDF version of SKOS [1] does not contain a licensing information, other than e.g. SSN [2] or DCAT3 [3]. Is it permitted to distribute (parts of) it and under which conditions? Does the W3C Software license [4] or the W3C Document license [5] apply to it, and if yes, which version? Could a licensing statement be added?1. https://www.w3.org/2009/08/skos-reference/skos.rdf
2. https://www.w3.org/ns/ssn/ssn.rdf
3. https://www.w3.org/ns/dcat3.ttl
4. https://www.w3.org/copyright/software-license-2023/
5. https://www.w3.org/copyright/document-license-2023/ -
@w3c
The RDF version of SKOS [1] does not contain a licensing information, other than e.g. SSN [2] or DCAT3 [3]. Is it permitted to distribute (parts of) it and under which conditions? Does the W3C Software license [4] or the W3C Document license [5] apply to it, and if yes, which version? Could a licensing statement be added?1. https://www.w3.org/2009/08/skos-reference/skos.rdf
2. https://www.w3.org/ns/ssn/ssn.rdf
3. https://www.w3.org/ns/dcat3.ttl
4. https://www.w3.org/copyright/software-license-2023/
5. https://www.w3.org/copyright/document-license-2023/ -
LintedData is a linter for RDF and Ontologies for easy use in CI pipelines, we recently released. It checks for common violations of best practices in ontology engineering.
GitLab: https://gitlab.com/dlr-dw/linteddata/
Docker: https://hub.docker.com/r/dlrdw/linteddata/Today I present LintedData at the Helmholtz Metadata Conference 2026 demo session.
Abstract & Poster: https://doi.org/10.5281/zenodo.20024644 or https://elib.dlr.de/223803/#RDF #Ontologies #KnowledgeGraphs #DataQuality #OntologyQuality #OntologyEngineering #HMC2026 @helmholtz_hmc
-
LintedData is a linter for RDF and Ontologies for easy use in CI pipelines, we recently released. It checks for common violations of best practices in ontology engineering.
GitLab: https://gitlab.com/dlr-dw/linteddata/
Docker: https://hub.docker.com/r/dlrdw/linteddata/Today I present LintedData at the Helmholtz Metadata Conference 2026 demo session.
Abstract & Poster: https://doi.org/10.5281/zenodo.20024644 or https://elib.dlr.de/223803/#RDF #Ontologies #KnowledgeGraphs #DataQuality #OntologyQuality #OntologyEngineering #HMC2026 @helmholtz_hmc
-
LintedData is a linter for RDF and Ontologies for easy use in CI pipelines, we recently released. It checks for common violations of best practices in ontology engineering.
GitLab: https://gitlab.com/dlr-dw/linteddata/
Docker: https://hub.docker.com/r/dlrdw/linteddata/Today I present LintedData at the Helmholtz Metadata Conference 2026 demo session.
Abstract & Poster: https://elib.dlr.de/223803/#RDF #Ontologies #KnowledgeGraphs #DataQuality #OntologyQuality #OntologyEngineering #HMC2026 @helmholtz_hmc
-
LintedData is a linter for RDF and Ontologies for easy use in CI pipelines, we recently released. It checks for common violations of best practices in ontology engineering.
GitLab: https://gitlab.com/dlr-dw/linteddata/
Docker: https://hub.docker.com/r/dlrdw/linteddata/Today I present LintedData at the Helmholtz Metadata Conference 2026 demo session.
Abstract & Poster: https://elib.dlr.de/223803/#RDF #Ontologies #KnowledgeGraphs #DataQuality #OntologyQuality #OntologyEngineering #HMC2026 @helmholtz_hmc
-
LintedData is a linter for RDF and Ontologies for easy use in CI pipelines, we recently released. It checks for common violations of best practices in ontology engineering.
GitLab: https://gitlab.com/dlr-dw/linteddata/
Docker: https://hub.docker.com/r/dlrdw/linteddata/Today I present LintedData at the Helmholtz Metadata Conference 2026 demo session.
Abstract & Poster: https://elib.dlr.de/223803/#RDF #Ontologies #KnowledgeGraphs #DataQuality #OntologyQuality #OntologyEngineering #HMC2026 @helmholtz_hmc
-
Already yesterday, I presented at the ESWC 2026 Pre-Conference in the Knowledge Graphs for Sustainability Workshop (KG4S) the Design-for-Circularity Ontology (D4CO). Related artifacts are available online.
🔗 Ontology: https://w3id.org/d4co
🧑💻 Repository: https://gitlab.com/dlr-dw/d4co
📄 Paper Pre-Print: https://elib.dlr.de/224130/ -
Recently, I was discussing about the pros and cons of different unit ontologies. However, I was not able to really express, why I am in favor of an ontology, which not only provides the direct conversion factors between units for direct application, but also provides the explanation for these values. In her keynote, Maria-Esther Vidal provided an explanation for my intuition (free after Aristotle): "We think we know a thing only when we know its cause." #eswc2026 #UnitsOfMeasurement #Ontologies
-
Maybe late to the party, but this days I learned that #Wikidata query service (#WDQS) now technically enforces descriptive user-agents as mandated by the Wikimedia User-Agent Policy: https://foundation.wikimedia.org/wiki/Policy:Wikimedia_Foundation_User-Agent_Policy
At different places I read that including an e-mail address in the user-agent is required by the Wikimedia User-Agent Policy. But up to the policy a project URL or similar would also be fine, right?
-
📢 #ABECTO version 3.1.5 has been released:
🔗 https://github.com/fusion-jena/abecto/releases/tag/v3.1.5ABECTO is an #OpenSource #CLI tool that compares #RDF graphs to spot errors 🪲 and assess completeness 📊 intended for use in #CICD pipelines.
Versions 3.1.3, 3.1.4, & 3.1.5 add rudimentary HTTP rate limit handling, some bug fixes, and (most important) a descriptive HTTP user-agent to cope with the #Wikidata query service (#WDQS) user-agent policy 🛂.
-
Tiny mistake, huge effect:
Due to a single wrong statement "day subclass of counting unit" (http://www.wikidata.org/entity/statement/Q573-b8a19c53-425d-0009-2c55-decdfeb3ff19), #Wikidata / @wikidata classifies every resource representing a calendar date, like "November 12, 1655" https://www.wikidata.org/entity/Q69107205, as unit. As a result, a query for all #UnitsOfMeasurement returns > 210.000 instead of < 7000 resources. -
Today and tomorrow, I demonstrate the Continuous Knowledge Graph Quality Assessment through Comparison using ABECTO at #SEMANTiCS2024 / #semanticsconf. I am looking forward to discuss with you about #CICD and #DataQuality in #Ontologies and #KnowledgeGraphs, as well as about my tool #ABECTO. All related resources are public available:
📄 https://ceur-ws.org/Vol-3759/paper5.pdf (paper)
⚙️ https://github.com/fusion-jena/abecto (software)
🧑💻 https://github.com/fusion-jena/abecto-ci-demo/ (demo scripts) -
The current activities on the #DBpedia issue board (https://github.com/dbpedia/extraction-framework/issues) are curious: While there is no reaction by the maintainers on (mine and other) issues, there are a lot responses by enthusiastic users volunteering to work on the issues. Even if each of these comments looks valid on its own, the accumulation and similarity of them makes me doubt these users are all actual humans.
-
Added a hotfix to the #ABECTO space data comparison project: https://github.com/fusion-jena/abecto-space-travel-comparison/commit/4ec43c8e317e5f0535e82d85e217795894ed7751
Ironically, the hotfix is to use #Wikidata classes to locally query the fetched #DBpedia data. At the next regular refresh, on 2026-01-10, mismatches based on properly aligned data will be available in https://mismatch-finder.toolforge.org/. Unfortunately, I can not invalidate the current mismatches before.
@nightrose @wikidata -
Surprisingly, I could not find an Issue about this #DBpedia problem. Now there is one: https://github.com/dbpedia/extraction-framework/issues/820
Contrary to my initial guess of an extractor bug, further investigations made an SPARQL endpoint (#openlinksw #virtuoso) bug seem more likely.
-
Remarkably:
➡️ Despite the lack of #DBpedia types, equivalent #Wikidata types are present in DBpedia.
➡️ Not all resources are affected: e.g. https://dbpedia.org/page/John_Young_(astronaut) is typed as http://dbpedia.org/ontology/Astronaut.
➡️ Right and wrong typed astronauts have the astronaut infobox (which is properly mapped https://mappings.dbpedia.org/index.php/Mapping_en:Infobox_astronaut) on #Wikipedia.I guess an extractor bug 🪲.
Side effect: Many astronauts are displayed as "animals". Although on might consider this as ontologically correct, it is quiet odd.
-
With ABECTO 3.1.5, I restored regular pushes of space travel data deviations between #Wikidata and #DBpedia to https://mismatch-finder.toolforge.org @nightrose. But it provides (at first glance) strange results (🔗 https://mismatch-finder.toolforge.org/results?ids=Q107667|Q115651852), like:
➡️ John Young member of the crew of Apollo 16 mismatches http://dbpedia.org/resource/Apollo_16
➡️ SpaceX Crew-10 crew member Anne McClain mismatches http://dbpedia.org/resource/Anne_McClainReason: Missing http://dbpedia.org/ontology/SpaceMission, http://dbpedia.org/ontology/Astronaut, … type statements in @dbpedia.
-
An unconventional approach to avoid providing an email address in the User-Agent was chosen in #DBpedia by reusing the user agent of #curl: https://github.com/dbpedia/extraction-framework/commit/de3ca70694f347db84a2daeb88d8218506075f81
I proposed an alternative: https://github.com/dbpedia/extraction-framework/issues/819