home.social

Search

18 results for “janmartinkeil”

  1. @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 says `foaf:Person` is a Person. While the (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.

  2. 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.

    @eswc_conf

  3. 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.

    #ESWC2026 @eswc_conf #KnowledgeGraphs #LLM

  4. 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.

    #ESWC2026 @eswc_conf #KnowledgeGraphs #LLM

  5. 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.

    #ESWC2026 @eswc_conf #KnowledgeGraphs #LLM

  6. 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.

    #ESWC2026 @eswc_conf #KnowledgeGraphs #LLM

  7. 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: w3id.org/d4co
    🧑‍💻 Repository: gitlab.com/dlr-dw/d4co
    📄 Paper Pre-Print: elib.dlr.de/224130/

    #eswc2026 @eswc_conf #KG4S @kg4s #ontologies

  8. 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

  9. 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: gitlab.com/dlr-dw/linteddata/
    Docker: hub.docker.com/r/dlrdw/lintedd

    Today I present LintedData at the Helmholtz Metadata Conference 2026 demo session.
    Abstract & Poster: elib.dlr.de/223803/

    @helmholtz_hmc

  10. 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: gitlab.com/dlr-dw/linteddata/
    Docker: hub.docker.com/r/dlrdw/lintedd

    Today I present LintedData at the Helmholtz Metadata Conference 2026 demo session.
    Abstract & Poster: elib.dlr.de/223803/

    #RDF #Ontologies #KnowledgeGraphs #DataQuality #OntologyQuality #OntologyEngineering #HMC2026 @helmholtz_hmc

  11. 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: gitlab.com/dlr-dw/linteddata/
    Docker: hub.docker.com/r/dlrdw/lintedd

    Today I present LintedData at the Helmholtz Metadata Conference 2026 demo session.
    Abstract & Poster: elib.dlr.de/223803/

    #RDF #Ontologies #KnowledgeGraphs #DataQuality #OntologyQuality #OntologyEngineering #HMC2026 @helmholtz_hmc

  12. 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: gitlab.com/dlr-dw/linteddata/
    Docker: hub.docker.com/r/dlrdw/lintedd

    Today I present LintedData at the Helmholtz Metadata Conference 2026 demo session.
    Abstract & Poster: elib.dlr.de/223803/

    #RDF #Ontologies #KnowledgeGraphs #DataQuality #OntologyQuality #OntologyEngineering #HMC2026 @helmholtz_hmc

  13. 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: gitlab.com/dlr-dw/linteddata/
    Docker: hub.docker.com/r/dlrdw/lintedd

    Today I present LintedData at the Helmholtz Metadata Conference 2026 demo session.
    Abstract & Poster: elib.dlr.de/223803/

    #RDF #Ontologies #KnowledgeGraphs #DataQuality #OntologyQuality #OntologyEngineering #HMC2026 @helmholtz_hmc

  14. @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. w3.org/2009/08/skos-reference/
    2. w3.org/ns/ssn/ssn.rdf
    3. w3.org/ns/dcat3.ttl
    4. w3.org/copyright/software-lice
    5. w3.org/copyright/document-lice

  15. @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. w3.org/2009/08/skos-reference/
    2. w3.org/ns/ssn/ssn.rdf
    3. w3.org/ns/dcat3.ttl
    4. w3.org/copyright/software-lice
    5. w3.org/copyright/document-lice

    #RDF #SKOS #W3C

  16. @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. w3.org/2009/08/skos-reference/
    2. w3.org/ns/ssn/ssn.rdf
    3. w3.org/ns/dcat3.ttl
    4. w3.org/copyright/software-lice
    5. w3.org/copyright/document-lice

    #RDF #SKOS #W3C

  17. @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. w3.org/2009/08/skos-reference/
    2. w3.org/ns/ssn/ssn.rdf
    3. w3.org/ns/dcat3.ttl
    4. w3.org/copyright/software-lice
    5. w3.org/copyright/document-lice

    #RDF #SKOS #W3C

  18. @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. w3.org/2009/08/skos-reference/
    2. w3.org/ns/ssn/ssn.rdf
    3. w3.org/ns/dcat3.ttl
    4. w3.org/copyright/software-lice
    5. w3.org/copyright/document-lice

    #RDF #SKOS #W3C