SIOC Post profile for "AI3:::Adaptive Information"
type: Document
description: A SIOC profile describes the structure and contents of a weblog in a machine readable form. For more information please refer to http://sioc-project.org/.
primary topic: CWPK #49: Mapping External Sources
generator agent: http://rdfs.org/sioc/wp-sioc.php

CWPK #49: Mapping External Sources
type: Post
has container: weblog
has creator: Mike Bergman
maker: Mike Bergman
created: 2020-10-07T15:02:05Z
content: Sometimes KR is Kind of Tricky I think I pretty much lied to you about 'roundtripping' and the importance of the last major section that we just completed in this Cooking with Python and KBpedia series. We had indeed accomplished the extraction-and-build cycle for classes, properties, and their annotations. These are the same roundtrip objectives we had been pursuing and doing with our Clojure procedures for years. But we were incomplete. There is another purpose to KBpedia as a 'scaffolding' to external sources that is not captured in this initial 'roundtripping' sense. If you download KBpedia, right now as version 2.50, and load it up into an editor like Protégé, you will see the KBpedia structure and its properties and annotations, but you will not see the links to the external resources that KBpedia integrates. These mappings (correspondences) are provided in separate mapping files, and have been since KBpedia was first released. This has struck me for some time as an unneeded indirection. I think the better approach is to embed these links directly into KBpedia (or whatever your master knowledge graph may be). OK, so if we do that, does that not become part of the baseline that needs to be roundtripped? And, if to be used, what is the best practice for representing these external relationships? Like much that has an open world approach, these kinds of questions and open-ended project requirements can stretch into the unachievable future. I don't want to keep moving the goalposts. But I do think the role of top-level knowledge graphs is integration and coverage. The addition of key mappings to our basic expectation for our central knowledge graph seems appropriate and reasonable. Thus, for a 'truer' conceptualization of 'roundtripping', I now include mappings with our basic remit. This correction (which, of course, is an addition), and some other utilities and tools explorations, are the focus of this next major Part V in our CWPK series. Think of this next majo…
encoded: Sometimes KR is Kind of Tricky I think I pretty much lied to you about ‘roundtripping‘ and the importance of the last major section that we just completed in this Cooking with Python and KBpedia series. We had indeed accomplished the extraction-and-build cycle for classes, properties, and their annotations. These are the same roundtrip objectives we had been pursuing and doing with our Clojure procedures for years. But we were incomplete. There is another purpose to KBpedia as a ‘scaffolding’ to external sources that is not captured in this initial ’roundtripping’ sense. If you download KBpedia, right now as version 2.50, and load it up into an editor like Protégé, you will see the KBpedia structure and its properties and annotations, but you will not see the links to the external resources that KBpedia integrates. These mappings (correspondences) are provided in separate mapping files, and have been since KBpedia was first released. This has struck me for some time as an unneeded indirection. I think the better approach is to embed these links directly into KBpedia (or whatever your master knowledge graph may be). OK, so if we do that, does that not become part of the baseline that needs to be roundtripped? And, if to be used, what is the best practice for representing these external relationships? Like much that has an open world approach, these kinds of questions and open-ended project requirements can stretch into the unachievable future. I don’t want to keep moving the goalposts. But I do think the role of top-level knowledge graphs is integration and coverage. The addition of key mappings to our basic expectation for our central knowledge graph seems appropriate and reasonable. Thus, for a ‘truer’ conceptualization of ’roundtripping’, I now include mappings with our basic remit. This correction (which, of course, is an addition), and some other utilities and tools explorations, are the focus of this next major Part V in our CWPK series. Think of this next majo…
topic: CWPK
topic: KBpedia
topic: Semantic Web Tools
links to: roundtripping
links to: Cooking with Python and KBpedia
links to: Clojure
links to: Protégé
links to: knowledge graph
links to: open world approach
links to: cb1-1
links to: cb1-2
links to: cb1-3
links to: cb2-1
links to: cb2-2
links to: cb2-3
links to: cb2-4
links to: cb2-5
links to: cb2-6
links to: cb2-7
links to: cb2-8
links to: cb2-9
links to: cb2-10
links to: cb2-11
links to: cb2-12
links to: cb2-13
links to: cb2-14
links to: cb2-15
links to: cb2-16
links to: cb2-17
links to: cb2-18
links to: cb2-19
links to: cb2-20
links to: cb2-21
links to: cb2-22
links to: cb2-23
links to: cb2-24
links to: cb2-25
links to: cb2-26
links to: cb2-27
links to: cb2-28
links to: cb2-29
links to: cb2-30
links to: cb2-31
links to: cb2-32
links to: cb2-33
links to: cb2-34
links to: cb2-35
links to: cb2-36
links to: cb2-37
links to: cb2-38
links to: cb2-39
links to: cb2-40
links to: cb2-41
links to: cb2-42
links to: cb2-43
links to: cb2-44
links to: cb2-45
links to: cb2-46
links to: cb2-47
links to: cb2-48
links to: cb2-49
links to: cb2-50
links to: cb2-51
links to: cb2-52
links to: cb2-53
links to: cb2-54
links to: cb2-55
links to: cb2-56
links to: cb2-57
links to: cb2-58
links to: cb2-59
links to: cb2-60

Mike Bergman
type: User

Mike Bergman
type: Person

Cooking with Python and KBpedia
label: CWPK listing

triples

owlready2

KBpedia

code listing covering the series

direct download

notify me