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: Making Linked Data Reasonable using Description Logics, Part 2
generator agent: http://rdfs.org/sioc/wp-sioc.php

Making Linked Data Reasonable using Description Logics, Part 2
type: Post
has container: weblog
has creator: Mike Bergman
maker: Mike Bergman
created: 2009-02-16T01:10:55Z
content: Good Design is Based on the Work to be Done In Part 1 of this series, I advocated the placement of linked data in an ABox construct from description logics [1] based on a separation of concerns argument. Actually, this broader position arose from close inspection of an earlier table on TBox and ABox purposes and roles that I had assembled from the literature. That table synthesized TBox and ABox purposes and roles from the citations listed in Back to the Future with Description Logics, though was based for the most part on the The Description Logic Handbook [2]. As we continued to look further at the assignments in that table we saw a few issues: First, some of the assignments seemed to be in error (as likely due to my own misunderstandings when making the assignments than anything else) Second, the use of my phrase "purposes and roles" in describing the assignments seemed too mushy: what work actually could occur within a 'box' seemed to be a more precise way of thinking and evaluating the assignments Third, two columns were inadequate: some work requires both the ontology and instances in order to be performed (that is, the work occurs at the conjoined layer of the knowledge base), and Last, some useful or necessary work may not even occur in whole or part within the confines of either the ABox or TBox. Work, of course, is what our computers do for us on the data. Properly identifying and isolating these work tasks is a good starting point for teasing out architectural and schema design. These perspectives allowed Fred Giasson and me to re-evaluate this earlier assignments table (see earlier version), as shown below. Note that some items have been moved to a different column (shown in blue, all of which were formerly in the 'ABox') and some have been added and may be external (shown in green): Work Tasks for an 'Open World' Knowledge Base TBox TBox <--> ABox ABox Definitions of the concepts and properties (relationships) of the controlled vocabulary Declarations o…
encoded: Good Design is Based on the Work to be Done In Part 1 of this series, I advocated the placement of linked data in an ABox construct from description logics [1] based on a separation of concerns argument. Actually, this broader position arose from close inspection of an earlier table on TBox and ABox purposes and roles that I had assembled from the literature. That table synthesized TBox and ABox purposes and roles from the citations listed in Back to the Future with Description Logics, though was based for the most part on the The Description Logic Handbook [2]. As we continued to look further at the assignments in that table we saw a few issues: First, some of the assignments seemed to be in error (as likely due to my own misunderstandings when making the assignments than anything else) Second, the use of my phrase “purposes and roles” in describing the assignments seemed too mushy: what work actually could occur within a ‘box’ seemed to be a more precise way of thinking and evaluating the assignments Third, two columns were inadequate: some work requires both the ontology and instances in order to be performed (that is, the work occurs at the conjoined layer of the knowledge base), and Last, some useful or necessary work may not even occur in whole or part within the confines of either the ABox or TBox. Work, of course, is what our computers do for us on the data. Properly identifying and isolating these work tasks is a good starting point for teasing out architectural and schema design. These perspectives allowed Fred Giasson and me to re-evaluate this earlier assignments table (see earlier version), as shown below. Note that some items have been moved to a different column (shown in blue, all of which were formerly in the ‘ABox’) and some have been added and may be external (shown in green): Work Tasks for an ‘Open World’ Knowledge Base TBox TBox <–> ABox ABox Definitions of the concepts and properties (relationships) of the controlled vocabulary Declarations of…
topic: Description Logics
topic: Linked Data
topic: Ontologies
topic: Semantic Web
topic: Structured Dynamics
topic: Structured Web
topic: UMBEL
has reply: comment-50486
has reply: comment-50493
links to: Part 1
links to: linked data
links to: description logics
links to: [1]
links to: separation of concerns
links to: Back to the Future with Description Logics
links to: [2]
links to: Fred Giasson
links to: LOD cloud
links to: lod-datasets 2008-09-18.html
links to: LODD
links to: [3]
links to: DBpedia
links to: SPARQL
links to: Web of Data
links to: RDF
links to: REST
links to: WOA
links to: Zitgist Data Viewer
links to: 2007 Big 12 Women's Basketball Tournament
links to: [4]
links to: OpenLink Data Explorer
links to: Marbles
links to: DISCO
links to: Tabulator.
links to: sparql demo
links to: query
links to: Bio2RDF
links to: Demo+queries
links to: Falcons
links to: IWS China
links to: Sindice
links to: DERI Ireland
links to: Watson
links to: KMi
links to: Semantic Web Search Engine (SWSE)
links to: Swoogle
links to: Ebiquity Group
links to: Powerset
links to: Hakia
links to: True Knowledge
links to: Cognition
links to: Mike Bergman
links to: semsets
links to: UMBEL
links to: AI
links to: KR
links to: Solr
links to: 5
links to: 6
links to: [7]
links to: [8]
links to: [9]
links to: working definition
links to: course
links to: iswc08 prudhommeaux swhcls 05.ppt
links to: DataSetEvaluation
links to: LinkedDataTutorial
links to: Pat Hayes
links to: Tim Finin
links to: document5.pdf
links to: "OWL 2 Web Ontology Language:Structural Specification and Functional-Style Syntax

Mike Bergman
type: User

Mike Bergman
type: Person

Back to the Future with Description Logics
label: earlier version