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 4
generator agent: http://rdfs.org/sioc/wp-sioc.php

Making Linked Data Reasonable using Description Logics, Part 4
type: Post
has container: weblog
has creator: Mike Bergman
maker: Mike Bergman
created: 2009-02-23T19:14:05Z
content: Concluding with a Simplified Instance Record Vocabulary for Linked Data ABoxes 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. In Part 2, I reinforced that argument from the perspective of the work to be done within a knowledge base. In Part 3 we surveyed some of the key literature, finding justification for the split of the TBox from the ABox and the use of specialty RDFS and OWL dialects for work-oriented reasoning in the context of an integral logics. We now conclude this series and try to bring these threads full circle to address what might be a vocabulary for an ABox instance record design. We'd very much like to thank Dr. Jim Pitman of the Bibliographic Knowledge Network project for having stimulated much of the thinking about the benefits and design of simple, human-authored and -readable instance records. A Re-cap Up until about six to eight months ago Fred Giasson and I were spending much of our thinking and design time on UMBEL, ontologies and what we now more precisely define as the TBox. Our intent all along was to get our process and thinking down pat there, and then turn ourselves to the representation of the actual entity data. We have wanted to keep data records separate from logic and structure all along. Some clients have their own specific data records but may still want to interact with Web stuff or apply similar logic. Moreover, some client data is proprietary, some public. By organizing the data into "named entity dictionaries" we could modularize the architecture to allow swapping in and out of data appropriate to the customer or circumstance at hand. Our initial design of this and what we share publicly has UMBEL and various standard public ontologies (FOAF, DC, SIOC, BIBO, etc) for the TBox, with Wikipedia entities and stuff from the BBC at the entity level (the ABox). However, earlier work with another client showed us that our i…
encoded: Concluding with a Simplified Instance Record Vocabulary for Linked Data ABoxes 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. In Part 2, I reinforced that argument from the perspective of the work to be done within a knowledge base. In Part 3 we surveyed some of the key literature, finding justification for the split of the TBox from the ABox and the use of specialty RDFS and OWL dialects for work-oriented reasoning in the context of an integral logics. We now conclude this series and try to bring these threads full circle to address what might be a vocabulary for an ABox instance record design. We’d very much like to thank Dr. Jim Pitman of the Bibliographic Knowledge Network project for having stimulated much of the thinking about the benefits and design of simple, human-authored and -readable instance records. A Re-cap Up until about six to eight months ago Fred Giasson and I were spending much of our thinking and design time on UMBEL, ontologies and what we now more precisely define as the TBox. Our intent all along was to get our process and thinking down pat there, and then turn ourselves to the representation of the actual entity data. We have wanted to keep data records separate from logic and structure all along. Some clients have their own specific data records but may still want to interact with Web stuff or apply similar logic. Moreover, some client data is proprietary, some public. By organizing the data into “named entity dictionaries” we could modularize the architecture to allow swapping in and out of data appropriate to the customer or circumstance at hand. Our initial design of this and what we share publicly has UMBEL and various standard public ontologies (FOAF, DC, SIOC, BIBO, etc) for the TBox, with Wikipedia entities and stuff from the BBC at the entity level (the ABox). However, earlier work with another client showed us that our i…
topic: Description Logics
topic: Linked Data
topic: Semantic Web
topic: Structured Dynamics
topic: Structured Web
topic: UMBEL
links to: Part 1
links to: linked data
links to: description logics
links to: [1]
links to: separation of concerns
links to: Part 2
links to: Part 3
links to: Dr. Jim Pitman
links to: Bibliographic Knowledge Network
links to: Fred Giasson
links to: UMBEL
links to: FOAF
links to: DC
links to: SIOC
links to: BIBO
links to: earlier posting
links to: microformats
links to: [2]
links to: Structured Dynamics
links to: key-value
links to: [3]
links to: QName
links to: RDF
links to: RDFS
links to: DCterms
links to: XSD
links to: OpenLink's
links to: Virtuoso
links to: Sponger
links to: Notation 3
links to: voiD
links to: lambda calculus
links to: domain-specific language
links to: SWSE
links to: [4]
links to: Talis
links to: JDIL
links to: YAML
links to: simpler approaches
links to: topic maps
links to: [5]
links to: working definition
links to: dissertation camera ready.pdf
links to: owl2-profiles
links to: saor billiontc08.pdf

Mike Bergman
type: User

Mike Bergman
type: Person

earlier posting
label: Naïve Representations and Structs