Skip to Content

Bibliographic Ontology Specification

Specification Document - 4 November 2009

Last update:
2009/11/04
Revision:
Revision: 1.3
Editor:
Frédérick Giasson - Structured Dynamics
Authors:
Bruce D'Arcus
Frédérick Giasson - Structured Dynamics
 

Copyright © 2008-2013 by Structured Dynamics LLC.

 

“I got my sources, now I need someone to write an essay for me!” Our pro writers can help with any assignment and class if that sounds familiar.

This work is licensed under a Creative Commons Licens. This copyright applies to the Bibliographic Ontology Specification and accompanying documentation and does not apply to Bibliographic Ontology data formats, ontology terms, or technology. Regarding underlying technology, Bibliographic Ontology relies heavily on W3C's RDF technology, an open Web standard that can be freely used by anyone.


Abstract

The Bibliographic Ontology Specification provides main concepts and properties for describing citations and bibliographic references (i.e. quotes, books, articles, etc) on the Semantic Web.


Status of This Document

NOTE: This section describes the status of this document at the time of its publication. Other documents may supersede this document.

This specification is an evolving document. This document is generated by a machine-readable Bibliographic Ontology expressed in RDF/XML with a specification template.

Authors welcome suggestions on the Bibliographic Ontology and this document. This document may be updated or added to based on implementation experience, but no commitment is made by the authors regarding future updates.

 

Table of Contents

  • Introduction
    • Terminology and Notation
  • Backgroun
  • The Bibliographic Ontology Description
    • Evolution and Extension of Bibliographic Ontology
    • Bibliographic Ontology and Standards
    • Bibliographic Ontology and RDF
  • The Bibliographic Ontology Documentation

 

Introduction

The Bibliographic Ontology describe bibliographic things on the semantic Web in RDF. This ontology can be used as a citation ontology, as a document classification ontology, or simply as a way to describe any kind of document in RDF. It has been inspired by many existing document description metadata formats, and can be used as a common ground for converting other bibliographic data sources.

 

Terminology and Notation

 

Namespace URIs of the general form "http://www.example.com/." represents some application-dependent or context-dependent URI as defined in RFC 2396.

The XML Namespace URI that MUST be used by implementations of this specification is:

  • http://purl.org/ontology/bibo/

Background

The Bibliographic Ontology is an effort of and Bruce D'Arcus to express citations and bibliographic relations using RDF and to query that same information using the SPARQL query language for RDF.

The specific contents of the Bibliographic Ontology are detailed in the Bibliographic Ontology namespace document.

 

The Bibliographic Ontology Description

This specification serves as the Bibliographic Ontology "namespace document". As such it describes the Bibliographic Ontology and the terms (classes and properties) that constitute it, so that Semantic Web applications can use those terms in a variety of RDF-compatible document formats and applications.

This document presents the Bibliographic Ontology as a vocabulary or Ontology. The Bibliographic Ontology is straightforward, pragmatic and designed to allow simultaneous deployment and extension, and is therefore intended for widescale use.

 

Evolution and Extension of the Bibliographic Ontology

The Bibliographic Ontology is identified by the namespace URI 'http://purl.org/ontology/bibo/'.

Revisions and extensions of Bibliographic Ontology are conducted through edits to the namespace document, which by convention is published in the Web at the namespace URI.

The properties and types defined here provide some basic concepts for use in Bibliographic Ontology descriptions. Other vocabularies (e.g. the Dublin Core metadata elements for simple bibliographic description, FOAF, etc.) can also be mixed in with the Bibliographic Ontology terms, as can local extensions. The Bibliographic Ontology is designed to be extended, and modules may be added at a later date.

 

Bibliographic Ontology Modules

Bibliographic Ontology modules may be used to extend the ontology and avoid making the base ontology too complex.

 

The Bibliographic Ontology and Standards

It is important to understand that the Bibliographic Ontology as specified in this document is not a standard in the sense of ISO Standardisation, or that associated with.

The Bibliographic Ontology depends heavily on W3C's standards work, specifically on XML, XML Namespaces, RDF, and OWL. All the Bibliographic Ontology documents must be well-formed RDF/XML documents.

This specification contributes an ontology, the "Bibliographic Ontology ", to the Semantic Web, specifying it using W3C's Resource Description Framework (RDF). As such, the Bibliographic Ontology adopts by reference both a syntax (using XML), a data model (RDF graphs) and a mathematically grounded definition for the rules that underpin the RDF design.

 

The Bibliographic Ontology and RDF

Why does the Bibliographic Ontology use ?

The Bibliographic Ontology is an application of the Resource Description Framework (RDF) because the subject area we're describing – citations and bibliographic references-- has so many competing requirements that a standalone format would not capture them or would lead to trying to describe these requirements in a number of incompatible formats. By using RDF, the Bibliographic Ontology gains a powerful extensibility mechanism, allowing Bibliographic-Ontology-based descriptions to be mixed with claims made in any other RDF vocabulary.

The Bibliographic Ontology as an ontology cannot incorporate everything we might want to talk about that is related to citations and bibliographic references. Instead of covering all topics within the Bibliographic Ongoloty itself, we describe the basic topics and build into a larger framework - RDF - that allows us to take advantage of work elsewhere on more specific description vocabularies.

RDF provides the Bibliographic Ontology with a way to mix together different descriptive vocabularies in a consistent way. Vocabularies can be created by different communities and groups as appropriate and mixed together as required, without needing any centralized agreement on how terms from different vocabularies can be written down in XML or N3.

Check the Ontology namespaces referenced section to find some ontologies that ca be use in conjonction with the Bibliographic Ontology.

There are mechanisms for saying which RDF properties are connected to which classes, and how different classes are related to each other, using RDF Syntax and OWL. These can be quite general (all RDF properties by default come from an rdf:Resource for example) or very specific and precise (for example by using OWL constructs). This is another form of self-documentation, which allows you to connect different vocabularies together as you please.

In summary then, RDF is self-documenting in ways which enable the creation and combination of vocabularies in a devolved manner. This is particularly important for an ontology which describes communities, since online communities connect to many other domains of interest, which it would be impossible (as well as suboptimal) for a single group to describe adequately in non-geological time.

RDF is usually written using the XML or syntaxes. If you want to process the data, you will need to use one of the many RDF toolkits available, such as Jena (Java) or Redland (C).

More information about RDF can be found in the.

The Bibliographic Ontology Documentation

To best way to read the specification is by loading the ontology into Protégé
  1. Download Protégé
  2. Open Protégé
  3. Click Menu: "File -> Open From URL...
  4. Use that URL: 

Navigation

  • Recent posts
Copyright © 2008-2012. The Bibliographic Ontology. All content available via Creative Commons Attribution-Share Alike 3.0  Site hosted by Structured Dynamics LLC.