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 #42: Other Structural Considerations
generator agent: http://rdfs.org/sioc/wp-sioc.php

CWPK #42: Other Structural Considerations
type: Post
has container: weblog
has creator: Mike Bergman
maker: Mike Bergman
created: 2020-09-24T15:12:59Z
content: Segregating the Structure and Looking for Orphans We have progressed through these build portions of the Cooking with Python and KBpedia series to capture the bulk of the structure in KBpedia by defining its classes, properties, and the hierarchical relationships among them. We have, so to speak, tossed all of the components into the bin, and have mostly defined our knowledge structure's scaffolding. But we still lack some structural definitions and analysis prior to beginning the testing for whether this structure is coherent or not. Today's installment directly addresses these gaps. You will note we still, as yet, have not done anything to annotate our concepts or predicates. That is OK, and we will hold off for a bit further, because annotations are all trappings useful for humans and language to interact with the knowledge graph. It is the structural aspects alone that set the logical framework of the knowledge graph. We will settle questions about this prior to adding labels, definitions, and alternative terms to KBpedia. Say Goodbye to the Start-up This is the last installment that we will begin with our standard start-up routine. As needed, our installments will from here on begin with standard Python module import statements. We will be moving our start-up routine into cowpoke.__main__ import and removing that comment below. We also have added the 'extract' switch, as we first described a couple of installments back: Which environment? The specific load routine you should choose below depends on whether you are using the online MyBinder service or local files. The example below is based on using local files, which given the complexity of the routines that are emerging, is probably your better choice. Make sure to modify the URIs for your local directories. Getting ready for cowpoke: As I mentioned a few installments back, all of this code we are assembling will be released under the cowpoke package come installment CWPK #46, which is due to be posted in one …
encoded: Segregating the Structure and Looking for Orphans We have progressed through these build portions of the Cooking with Python and KBpedia series to capture the bulk of the structure in KBpedia by defining its classes, properties, and the hierarchical relationships among them. We have, so to speak, tossed all of the components into the bin, and have mostly defined our knowledge structure’s scaffolding. But we still lack some structural definitions and analysis prior to beginning the testing for whether this structure is coherent or not. Today’s installment directly addresses these gaps. You will note we still, as yet, have not done anything to annotate our concepts or predicates. That is OK, and we will hold off for a bit further, because annotations are all trappings useful for humans and language to interact with the knowledge graph. It is the structural aspects alone that set the logical framework of the knowledge graph. We will settle questions about this prior to adding labels, definitions, and alternative terms to KBpedia. Say Goodbye to the Start-up This is the last installment that we will begin with our standard start-up routine. As needed, our installments will from here on begin with standard Python module import statements. We will be moving our start-up routine into cowpoke.__main__ import and removing that comment below. We also have added the ‘extract’ switch, as we first described a couple of installments back: Which environment? The specific load routine you should choose below depends on whether you are using the online MyBinder service or local files. The example below is based on using local files, which given the complexity of the routines that are emerging, is probably your better choice. Make sure to modify the URIs for your local directories. Getting ready for cowpoke: As I mentioned a few installments back, all of this code we are assembling will be released under the cowpoke package come installment CWPK #46, which is due to be posted in one …
topic: CWPK
topic: KBpedia
topic: Semantic Web Tools
links to: Cooking with Python and KBpedia
links to: KBpedia
links to: cb1-1
links to: cb1-2
links to: cb1-3
links to: cb1-4
links to: cb1-5
links to: cb1-6
links to: cb1-7
links to: cb1-8
links to: cb1-9
links to: cb1-10
links to: cb1-11
links to: cb1-12
links to: cb1-13
links to: cb1-14
links to: cb1-15
links to: cb1-16
links to: cb1-17
links to: cb1-18
links to: cb1-19
links to: cb1-20
links to: cb1-21
links to: cb1-22
links to: cb1-23
links to: cb1-24
links to: cb1-25
links to: cb1-26
links to: cb1-27
links to: cb1-28
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: KKO
links to: CWPK #38
links to: CWPK #40
links to: CWPK #17
links to: cb3-1
links to: cb3-2
links to: cb3-3
links to: cb3-4
links to: cb3-5
links to: cb3-6
links to: cb3-7
links to: cb3-8
links to: cb3-9
links to: cb3-10
links to: cb3-11
links to: cb3-12
links to: cb3-13
links to: cb3-14
links to: cb3-15
links to: cb3-16
links to: roundtripping
links to: cb4-1
links to: cb4-2
links to: cb4-3
links to: cb4-4
links to: cb4-5
links to: cb4-6
links to: cb4-7
links to: cb4-8

Mike Bergman
type: User

Mike Bergman
type: Person

Cooking with Python and KBpedia
label: CWPK listing

KBpedia

direct download

notify me