Difference between revisions of "Library Ontology Concepts"

From Code4Lib
Jump to: navigation, search
(first concepts)
 
Line 22: Line 22:
 
@prefix mods: <http://www.loc.gov/mods/v3> . # experimental - MODS is not RDF but parts of it can be used
 
@prefix mods: <http://www.loc.gov/mods/v3> . # experimental - MODS is not RDF but parts of it can be used
 
</pre>
 
</pre>
 +
 +
In addition <tt>mfc:</tt> refers to the [http://www.loc.gov/marc/community/eccihome.html MARC 21 Format for Community Information] which is not an ontology at all - but at least you can point to some existing MARC fields. For instance <tt>mfc:270$k</tt> is the telephone number (which can better be expressed as <tt>vcard:tel</tt> in RDF). In the same way <tt>zeta:</tt> refers to the ZETA cataloging format in PICA+ which is used by the German Sigelverzeichnis (see [http://www.zeitschriftendatenbank.de/erschliessung/arbeitsunterlagen/zeta.html#c10787 their rules]). For instance the telephone number is <tt>zeta:035B$a</tt>.
  
 
== Classes ==
 
== Classes ==
Line 47: Line 49:
 
</pre>
 
</pre>
  
== Services ==
+
== Addresses ==
 +
The Library Ontology does not define address classes and properties because there already is vCard.
 +
 
 +
== Library Services ==
 
See DAIA (no final RDF yet, but [http://www.gbv.de/wikis/cls/DAIA_Format/RDF some notes])
 
See DAIA (no final RDF yet, but [http://www.gbv.de/wikis/cls/DAIA_Format/RDF some notes])
  
Line 60: Line 65:
 
     rdfs:subClassOf dct:identifier .
 
     rdfs:subClassOf dct:identifier .
 
</pre>
 
</pre>
 +
 +
=== Relationships between Libraries and their collections ===
 +
 +
* owns ?
 +
* holds ?
 +
* provides ?
 +
 +
=== Relationships between Libraries ===
 +
Libraries can be and have subordinate entities which do not need to be libraries. Libraries can split and join. Libraries can be friends ;-)
 +
 +
* dct:hasPart/dct:isPartOf
 +
* foaf:knows
 +
* branch? subunit? partner?

Revision as of 22:00, 8 December 2009

This page collects some concepts (classes and properties) of the Library Ontology. To refer to other ontolgies the following namespace prefixes are defined (all in Turtle syntax):

# RDF basics
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix ns: <http://www.w3.org/2003/06/sw-vocab-status/ns#> .

# Other Ontologies
@prefix dct:  <http://purl.org/dc/terms/> .
@prefix dc:   <http://purl.org/dc/elements/1.1/> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix event: <http://purl.org/NET/c4dm/event.owl#> .
@prefix skos: <http://www.w3.org/2008/05/skos#> .
@prefix bibo: <http://purl.org/ontology/bibo/> .
@prefix geo: <http://www.w3.org/2003/01/geo/wgs84_pos#> .
@prefix frbr: <http://purl.org/vocab/frbr/core#> .
@prefix vcard: <http://www.w3.org/2006/vcard/ns#> .
@prefix address: <http://schemas.talis.com/2005/address/schema#> .
@prefix mods: <http://www.loc.gov/mods/v3> . # experimental - MODS is not RDF but parts of it can be used

In addition mfc: refers to the MARC 21 Format for Community Information which is not an ontology at all - but at least you can point to some existing MARC fields. For instance mfc:270$k is the telephone number (which can better be expressed as vcard:tel in RDF). In the same way zeta: refers to the ZETA cataloging format in PICA+ which is used by the German Sigelverzeichnis (see their rules). For instance the telephone number is zeta:035B$a.

Classes

Library

A library can be a collection, an organization, or a place.

:Library rdf:type owl:Class ;
    rdfs:subClassOf [ 
        rdf:type owl:Class ;
        owl:unionOf ( bibo:Collection foaf:Organization geo:SpatialThing )
    ] .

:LibraryBuilding rdf:type owl:Class ;
    rdfs:subClassOf :Library , geo:SpatialThing  ;
    owl:intersectionOf ( :Library , geo:SpatialThing ) .

:LibraryOrganization rdf:type owl:Class ;
    rdfs:subClassOf :Library , foaf:Organization ;
    owl:intersectionOf ( :Library , foaf:Organization ) .

:LibraryCollection rdf:type owl:Class ;
    rdfs:subClassOf :Library , bibo:Collection .
    owl:intersectionOf ( :Library , bibo:Collection ) .

Addresses

The Library Ontology does not define address classes and properties because there already is vCard.

Library Services

See DAIA (no final RDF yet, but some notes)

Other concepts

holding, store, stack, loan...

Properties

Identifiers

:isil rdf:type owl:DatatypeProperty ;
    rdfs:subClassOf dct:identifier .

Relationships between Libraries and their collections

  • owns ?
  • holds ?
  • provides ?

Relationships between Libraries

Libraries can be and have subordinate entities which do not need to be libraries. Libraries can split and join. Libraries can be friends ;-)

  • dct:hasPart/dct:isPartOf
  • foaf:knows
  • branch? subunit? partner?