37
edits
Changes
no edit summary
@prefix mods: <http://www.loc.gov/mods/v3> . # experimental - MODS is not RDF but parts of it can be used
</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 ==
</pre>
== 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])
rdfs:subClassOf dct:identifier .
</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?