Code4Lib - User contributions [en]

CSE Reference Style

2014-07-10T06:53:21Z

JakobVoss: Link to CSL style

''A [http://citationstyles.org/ CSL file] to automatically create CSE reference style [https://github.com/citation-style-language/styles/raw/master/council-of-science-editors-author-date.csl can be found here]''

__TOC__

==Book==

Bibliography:
McCormac JS, Kennedy G. 2004. Birds of Ohio. Auburn (WA): Lone Pine. p. 77-78.

In-Text:
(McCormac and Kennedy 2004)

==Book Chapter==

Bibliography:
McDaniel TK, Valdivia RH. 2005. New tools for virulence gene discovery. In: Cossart P, Boquet P, Normark S, Rappuoli R, editors. Cellular microbiology. 2nd ed. Washington (DC): ASM Press. p. 473-488.

In-Text:
(McDaniel and Valdivia 2005)

==Electronic Book==

Bibliography:
Rollin, BE. The unheeded cry: animal consciousness, animal pain, and science [Internet]. Ames (IA): The Iowa State University Press; 1998 [cited 2007 August 27]. Available from: http://www.netlibrary.com

In-Text:
(Rollin 1998)

==Journal Article (Print)==

Bibliography:
Meise CJ, Johnson DL, Stehlik LL, Manderson J, Shaheen P. 2003. Growth rates of juvenile Winter Flounder under varying environmental conditions. Trans Am Fish Soc 132(2):225-345.

In-Text:
(Meise et al. 2003)

==Electronic Article (From OpenURL link)==

Bibliography:
Parmentier H, Golding S, Ashworth M, Rowlands G. 2004. Community pharmacy treatment of minor ailments in refugees. Journal of Clinical Pharmacy and Therapeutics [Internet]. [cited 2007 Jul 24]; 29(5):465-469. Available from: http://journals.ohiolink.edu/ejc/pdf.cgi/Parmentier_H.pdf?issn=02694727&issue=v29i0005&article=465_cptomair

In-Text:
(Parmentier et al. 2004)

==Electronic Article (From Publisher's Website)==

Bibliography:
Leng F, Amado L, McMacken R. 2004. Coupling DNA supercoiling to transcription in defined protein systems. Journal of Biological Chemistry [Internet]. [cited 2007 Jul 24];279(46):47564-47571. Available from: http://www.jbc.org/cgi/reprint/279/46/47564

In-Text:
(Leng et al. 2004)

==Electronic Article (From Online-Only Journal)==

Bibliography:
Hong P, Wong W. 2005. GeneNotes: a novel information management software for biologists. BMC Bioinformatics [Internet]. [cited 2007 July 24]; 6:20. Available from: http://www.biomedcentral.com/1471-2105/6/20

In-Text:
(Hong and Wong 2005)

==Electronic Encyclopedia Article (From Database)==

Bibliography:
Wang C. c2007. Stem Cells. In: AccessScience@McGraw-Hill. [Internet][Hightstown (NJ)]: McGraw-Hill Education; [cited 2007 Sept 10]. Available from: http://www.accessscience.com/content.aspx?id=800100

In-Text:
(Wang c2007)

==Dissertation/Thesis==

Bibliography:
Dettmers JM. 1995. Assessing the trophic cascade in reservoirs: the role of an introduced predator [dissertation]. [Columbus (OH)]: Ohio State University. p. 7-14.

In-Text:
(Dettmers 1995)

==Conference Paper==

Bibliography:
Clarke A, Crame JA. 2003. Importance of historical processes in global patterns of diversity. In: Blackburn TM, Gaston KJ, editors. Macroecology: concepts and consequences. Proceedings of the 43rd annual symposium of the British Ecological Society; 2002 Apr 17-19; Birmingham. Malden (MA): Blackwell. p. 130-152.

In-Text:
(Clarke and Crame 2003)

==Conference Abstract==

Bibliography:
Swanson TA, Blair P, Madigan L. 2004. Reduction in medication errors through redesign of the medication use system [abstract]. In: American Society of Health-system Pharmacists 39th midyear meeting; 2004 Dec 5-9; Orlando. Bethesda (MD): American Society of Health-System Pharmacists. MCS-28.

In-Text:
(Swanson et al. 2004)

==Technical Report==

Bibliography:
Ford PL, Fagerlund RA, Duszynski DW, Polechla PJ. 2004. Fleas and lice of mammals in New Mexico. Fort Collins (CO): USDA Forest Service Rocky Mountain Research Station. General Technical Report No. RMRS-GTR-123.

In-Text:
(Ford et al. 2004)

==Web Page (With No Author Listed)==

Bibliography:
Emerald Ash Borer (EAB) [Internet]. [updated 2007 Feb 27]. Columbus (OH): Ohio Department of Natural Resources, Division of Forestry; [cited 2007 Jul 24]. Available from: http://www.dnr.state.oh.us/forestry/health/eab.htm

In-Text:
(Emerald Ash Borer ... [updated 2007])

==Notes==
(Page adapted from The Ohio State University Libraries guide on reference styles http://library.osu.edu/help/research-strategies/)

User:JakobVoss

2013-04-03T12:28:01Z

JakobVoss:

* [[DAIA extensions]]: moved to https://github.com/gbv/dso
* [[Library Ontology]]: moved to https://gist.github.com/nichtich/5300505
* [[Citation Style Language]] (CSL)
----
* =[http://www.gbv.de/wikis/cls/Benutzer:Voss Voss@GBV-Verbundwiki]

DAIA extensions

2013-04-03T12:26:54Z

JakobVoss:

This page collected some proposed '''service types''' and other suggestions as extension to the [http://purl.org/NET/DAIA Document Availability Information API]. See [https://github.com/gbv/dso Document Service Ontology (DSO)] for a more up-to-date approach.

== Additional Service types ==

=== Excerpt ===
http://purl.org/NET/daia-ext/excerpt

Request library staff to make a photocopy or scan of a part (chapter or article) of a physical item, which will them be emailed or delivered to the user.
:Copying/Scaning as service makes sense. Is the act of copying the relevant service or the fact that you get only a part of the item as copy? -- [[User:JakobVoss|JakobVoss]] 02:12, 29 September 2009 (PDT)
::In my library, the nature of the service is that you only get part of the item AND you get choose what part. The act of copying isn't the relevant service, although I'm not sure how a library would provide a user-choice part of the item without copying, but if there's a way, that's fine! [[User:jrochkind]]
:::An item may have the ''fragment'' attribute but that would mean the library does only have a specific excerpt. So Excert looks like a reasonable service type. -- [[User:JakobVoss|JakobVoss]] 01:39, 23 October 2009 (PDT)

'''Please refer to https://github.com/gbv/dso/issues/1 for further discussion'''

=== Deliver ===
http://purl.org/NET/daia-ext/deliver

Request delivery of a physical item, to a circulation desk, an office, or even a home, depending on what the library provides.

:Does deliver imply loan? I think a broad "deliver" does not help, but more specific services like "home-deliver", "office-deliver" etc. as subtypes of "loan". Delivering to a circulation desk is not a specific service in my opinion. -- [[User:JakobVoss|JakobVoss]] 02:12, 29 September 2009 (PDT)

::Why is delivering to a circulation desk not a specific service? I guess I'm trying to figure out how to represent the services that my library actually does offer. Now, I kind of see your vision of services, and I WISH my library offered the kind of services you're thinking of, and in such a way that my software could actually predict them... but it kind of doesn't. And I'm not in charge.

:::There is a difference between deliver to a circulation desk for use in the rooms of the library (presentation) and for loaning. Deliver to an office or at home is a different kind of service that implies loan. To distinguish deliver to circulation desk and self-pick up with open-access shelving we may need another method. -- [[User:JakobVoss|JakobVoss]] 01:39, 23 October 2009 (PDT)

:::: Hmm. I hear you. But we have some items for some patrons that can be checked out, but you've got to go get them from the stacks yourself. There are other items for certain patrons that can be checked out, and you can click a button and have them waiting at the circ desk. There are other items that can be checked out, and you can have them delivered to your office. The end result of all of these things could be considered a 'loan' -- but it matters to the user which of these things are available, the difference in convenience may effect their decision of whether to access the item at this time or not. How should this be encoded in DAIA so it can be presented to the user? I'm trying to take a stab at it, I hear your critique, but I'm still not sure the better way to do it. I see how to create new services simply by creating new URI's for them in DAIA -- you mention 'sub-service', but how can I extend DAIA with a 'sub-service', what does this look like?

* Similarly: It matters to the user whether they can do 'presentation' by simply going to the stacks and picking it up themselves, and reading it in the library location of their choice, or whether they can only access 'presentation' by filing a request, waiting a certain amount of time, and then viewing the material during certain business hours of a special reading room in that special reading room. (Another actual situation in my actual library). How should this be represented in a DAIA response, so it can be communicated to the user? I am not sure. Any ideas? [[User:Jrochkind|Jrochkind]] 19:33, 27 October 2009 (PDT)
: Except again, it makes me think of the 'obstacle' field. Maybe an 'obstacle' field is the elegant answer to many of my use cases. Is there a way for me to legally add an 'obstacle' extension to my DAIA response such that it will still validate against the DAIA schema? Not sure if 'obstacle' should be a URI, or a human displayable message -- probably both. [[User:Jrochkind|Jrochkind]] 19:48, 27 October 2009 (PDT)

'''Please refer to https://github.com/gbv/dso/issues/2 for further discussion'''

=== Request ===
http://purl.org/NET/daia-ext/request

ILS 'request' function. Sadly, the typical ILS 'request' function can be used for a variety of actual services, including:
* recall a checked out item
* place a 'hold' on an item
* request an item for delivery to a particular location (circ desk or other)

Where possible, you should not use the 'request' service, but should instead use a service expressing a more specific action availability. However, actually existing ILS's can make it very hard to figure out what more specific actions are available, and it may still be useful to advertise the ILS 'request' function, this service represents that.

:Looks like a super-class of all service types with meaning "unknown". In this case we may better '''make the service field optional''' so if you can specify an unknown service. -- [[User:JakobVoss|JakobVoss]] 02:12, 29 September 2009 (PDT)

::That might work, as long as it's possible to specify a user-displayable label for the service. Won't be able to be understood/acted upon by software, but the user can still be told this is, say, a generic 'Request'.

=== Recall ===
http://purl.org/NET/daia-ext/recall

Recall a checked out item, which will typically then be placed on hold for you.

:Placed for you for what purpose? -- [[User:JakobVoss|JakobVoss]] 02:12, 29 September 2009 (PDT)
::So are you suggesting this shouldn't be a service of it's own, but instead should just be indicated in the 'delay' and user-displayable comments on the actual end-purpose service, that a 'recall' is possible? One thing is that in my library I am told that the user wants to know if they will be recalling the item from someone else or not before making the request.
:::This should better be encoded in the 'delay' and 'queue' attributes. If I understand you right, you want to encode whether an item is hold by someone else or is not available for some other reason. If we start encoding this, we can build an ontology of reasons why I cannot get a book (someone else holds it, it's a the bookbinder, the cat of the librarian is sitton on it...) which is not purpose of core DAIA. Maybe you could add a custom 'reason' field to unavailable or an 'obstacle' field to available/unavailable. -- [[User:JakobVoss|JakobVoss]] 01:39, 23 October 2009 (PDT)
:::: Yes, I think I can buy this, seems workable, thanks for explaining. Although I'd clarify I don't want to say why an item _isn't_ available. I in fact want to say that an item IS available, after a specified delay, but you can't just take it off the stacks, the only way you can get it is by pressing a button. This is in general something I'm not sure how to do in DAIA, a thread throughout these new services. It's not always enough to say that 'loan' is available, sometimes I need to make sure a user knows they can't just pull it off the stacks themselves, the ONLY way to access 'loan' is to access this link here. I'm not sure how to do that in DAIA, so the system can make sure to let the user know this? Or maybe it's just indicated by 'loan' being available but NOT 'presentation'. My end system consuming DAIA knows that if 'loan' is avaialable but not 'presentation', it should warn the user "don't go try to pull this off the stacks yourself, follow this link instead." Or maybe I DO need an 'obstacle' field, I kind of like that. But I don't think the current DAIA schema gives me any way to add such an 'obstacle' field while still having XML that validates against the DAIA schema? [[User:Jrochkind|Jrochkind]] 19:41, 27 October 2009 (PDT)
:::: Additionally, I've been told that in my library users want to know if by accessing 'loan' they are going to be triggering an early return from someone who has it out now. Some users will decide they don't want the book that bad (especially cause the person who they got it from can then trigger an early return for THEM, the chances of them being able to keep it long are not that great. Not sure what to do with this either. Except it again makes me think of an 'obstacle' field maybe. [[User:Jrochkind|Jrochkind]] 19:27, 27 October 2009 (PDT)

User:JakobVoss

2013-04-03T11:56:21Z

JakobVoss:

* [[DAIA extensions]]
* [[Library Ontology]]: moved to https://gist.github.com/nichtich/5300505
* [[Citation Style Language]] (CSL)
----
* =[http://www.gbv.de/wikis/cls/Benutzer:Voss Voss@GBV-Verbundwiki]

Library Ontology Concepts

2013-04-03T11:55:43Z

JakobVoss: Moved to GitHub

This page has been moved to https://gist.github.com/nichtich/5300505#library-concepts-md together with the page [[Library Ontology]] which has been moved to https://gist.github.com/nichtich/5300505#file-library-ontology-md.

Library Ontology

2013-04-03T11:54:47Z

JakobVoss: Moved to GitHub

This page has been moved to to https://gist.github.com/nichtich/5300505#file-library-ontology-md together with the page [[Library Ontology Concepts]] which has been moved to https://gist.github.com/nichtich/5300505#library-concepts-md.

Citation Style Language

2010-04-28T15:00:29Z

JakobVoss: /* Bibliographic record format */ excerpt from the spec

The '''Citation Style Language''' (CSL) is an XML-Based stylesheet language for formatting of citations and bibliographies. It is used in reference management software such as [[Zotero]], [[Mendeley]], [[CiteProc]] and [[Pandoc]]. CSL was initiated by Bruce D’Arcus in the XBib project. The CSL 1.0 specification was published in March 2010.

== The idea behind CSL ==

If you know [[BibTeX]] you can compare CSL with the BibTeX style file language BAFLL (BibTeX Anonymous Forth-Like). If you know XSL than you can compare it with XSLT. The basic idea is to seperate bibliographic data and a citation styles that can be used to create nicely formatted citations.

CSL-Style
|
v
Bibliographic record -> CSL-Processor -> Citation

CLS-Processors are available in different programming languages. The most elaborated CSL-Processor is citeproc-js.

== Getting started ==

If you use a reference management software such as Zotero you already use CLS under the hood. If you want to dig your hands into code, have a look at citeproc-js:

hg clone http://bitbucket.org/fbennett/citeproc-js

Documentation is located in the manual directory or online at http://gsl-nagoya-u.net/http/pub/citeproc-doc.html and a demo that runs in a Browser is available at http://gsl-nagoya-u.net/http/pub/citeproc-demo/demo.html

== Bibliographic record format ==

Of course you cannot throw any bibliographic record format into a CSL-Processor but you must use the [http://citationstyles.org/downloads/specification.html#appendices field names defined in the CSL 1.0 specification]. Some of the fields are repeatable and have an interal structure [http://gsl-nagoya-u.net/http/pub/citeproc-doc.html#data-input as described here].

=== CSL record format ===

Derived from the CSL 1.0 specification and the citeproc-js documentation a CSL record can be defined as a follows in incomplete Backus-Naur-Form and additional description:

A record is a JSON object with unique keys of three kinds (VAR, NAME, DATE, and TYPE):

'''(1)''' <tt>RECORD := '{' { STD ':' STD_VAL | NAME ':' NAME_VAL | DATE ':' DATE_VAL | TYPE }* '}'</tt> (plus comma as seperator)

A <tt>STD</tt> is a standard variable name as listed at http://citationstyles.org/downloads/specification.html#standard-variables.

'''(2)''' <tt>STD := '"abstract"' | '"annote"' | '"archive"' | ... </tt>

A <tt>NAME</tt> is a name variable name as listed at http://citationstyles.org/downloads/specification.html#name-variables.

'''(3)''' <tt>NAME := '"author"' | '"editor"' | ... </tt>

A <tt>DATE</tt> is a date variable name as listed at http://citationstyles.org/downloads/specification.html#date-variables.

'''(4)''' <tt>NAME := '"accessed"' | '"container"' | ... </tt>

A <tt>STD_VAL</tt> is simple JSON string

'''(5)''' <tt>STD_VAL := JSON_STRING</tt> (see JSON standard)

A <tt>TYPE</tt> contains a value from the types listed at http://citationstyles.org/downloads/specification.html#appendix-ii-types

'''(6)''' <tt>TYPE := '"type"' ':' ( '"article"' | '"book"' | ... )</tt>

A <tt>NAME_VAL</tt> is non-empty JSON array of JSON objects with <tt>NAME_PART</tt> keys and simple JSON string values:

'''(7)''' <tt>NAME_VAL := '[' ( '{' NAME_PART ':' JSON_STRING | STATIC_ORDERING '}' )+ ']'</tt> (plus comma as seperator)

A <tt>NAME_PART</tt> is variable name is one of

'''(8)''' <tt>NAME_PART := '"family"' | '"given"' | '"suffix"' | '"non-dropping-particle"' | '"dropping-particle"'</tt>

In addition you can add <tt>STATIC_ORDERING</tt> as part of the <tt>NAME_VAL</tt> to flag that a name is always displayed with the family name first ("non-Byzantine" names):

'''(9)''' <tt>STATIC_ORDERING := '"static-ordering"' ':' ANY_TRUE_JSON_VALUE</tt> (TODO: what is ANY_TRUE_JSON_VALUE?)

A <tt>DATE_VAL</tt> is a JSON object which contains at least a <tt>DATE_PARTS</tt> element and optionally a <tt>SEASON_VAL</tt> element:

'''(10)''' <tt>NAME_VAL := '{' '"date-parts"' ':' DATE_PARTS ( ',' '"season"' ':' SEASON_VAL )? '}'</tt>

A <tt>DATE_PARTS</tt> is is a nested JSON array containing a start date and optional end date, each of which consists of a year, an optional month and an optional day, in that order if present.

'''(11a)''' <tt>DATE_PARTS := '[' DATE ( ',' DATE )? ']'</tt> 
'''(11b)''' <tt>DATE := '[' YEAR ( ',' MONTH ( ',' DAY )? )? ']'</tt> 
'''(11c)''' <tt>YEAR := JSON_STRING | JSON_INTEGER</tt> (string must contain an interger. Number must not be zero) 
'''(11d)''' <tt>MONTH := JSON_STRING | JSON_INTEGER</tt> (1 to 12) 
'''(11e)''' <tt>DAY := JSON_STRING | JSON_INTEGER</tt> (1 to 31) 

A <tt>SEASON_VAL</tt> should be one of 1 to 4 or a fixed JSON string:

'''(12)''' <tt>SEASON_VAL := '"1"' | '"2"' | '"3"' | '"4"' | JSON_STRING</tt>

The [http://gsl-nagoya-u.net/http/pub/citeproc-doc.html#dirty-tricks dirty-tricks fields of citeproc-js] are ''not valid'' CSL. Please clean your input data before feeding it to a CSL processor if you want to get sane citations.

=== Other record formats ===

If you want to use some other format (BibTeX, RIS, MARC, MODS, Bibliographic Ontology etc.) you go this way:

Record in your format -> some miracle occurs -> record in CSL format -> CSL-Processor -> Citation

Please replace "some miracle occurs" with the conversion service of your choice, for instance Zotero or some library software hacks that libraries tend to use. There is nothing wrong with specific bibliographic formats but its not their purpose to create citations (counterexamples: BibTeX and RIS).

== Embedding CSL records in twitter annotations ==

On the Code4lib mailing list it has been discussed to embed bibliographic data in twitter annotations. If this annotations contain CSL records then you could display a bibliographic reference in the citation style of your choice.

A twitter annotation is a JSON object with up to 512 bytes (later more):

* http://www.readwriteweb.com/archives/what_twitter_annotations_mean.php
* http://groups.google.com/group/twitter-meta

The CSL input format is also JSON but you need to specify a root element and how to deal with multiple references. This is how an annotation could look like:

<pre>
{ "cslrecords" : {
"ITEM-2" : {
"author": [ {
"family": "Bennett",
"given": "Frank G.",
"suffix": "Jr.",
"static-ordering": false
} ],
"title":"Getting Property Right: \"Informal\" Mortgages in the Japanese Courts",
"container-title":"Pacific Rim Law & Policy Journal",
"volume": "18",
"page": "463-509",
"issued": { "date-parts": [ [2009, 8] ] },
"type": "article-journal"
}
}
</pre>

But you could also wrap the single records in a way to easily add more non-CSL data to it:

<pre>
{ "bibrecords":
"ITEM-2" : {
"csl" : {
"author": [ {
"family": "Bennett",
"given": "Frank G.",
"suffix": "Jr.",
"static-ordering": false
} ],
"title":"Getting Property Right: \"Informal\" Mortgages in the Japanese Courts",
"container-title":"Pacific Rim Law & Policy Journal",
"volume": "18",
"page": "463-509",
"issued": { "date-parts": [ [2009, 8] ] },
"type": "article-journal"
},
"identifier" [
"urn:issn:1066-8632",
"http://ssrn.com/abstract=1541102",
"bibkey:18561d99b88967f176f0e4ab63d230c0e"
]
}
}
</pre>

== References ==
* http://CitationStyles.org - the home of the Citation Style Language (CSL)
* http://citationstyles.org/downloads/specification.html - CSL 1.0 specification
* http://citationstyles.org/styles/ - the Zotero style repository contains hundreds of citation styles (maily in CSL 0.8)
* http://bitbucket.org/fbennett/citeproc-js - citeproc-js
* http://xbiblio.sourceforge.net/ - XBib project (no longer maintained)

== Alternatives ==
* http://www.refbase.net/ is open source and contains import filters and citation styles to create citations from bibliographic data

----
''This page is licensed under CC-BA-SA and thus can be used on other pages such as Wikipedia as you like''

Citation Style Language

2010-04-28T12:43:18Z

JakobVoss: /* Embedding CSL records in twitter annotations */

Citation Style Language

2010-04-28T12:25:52Z

JakobVoss: /* References */

Citation Style Language

2010-04-28T12:18:54Z

JakobVoss: + alternatives

Citation Style Language

2010-04-28T12:01:49Z

JakobVoss:

Citation Style Language

2010-04-28T11:45:21Z

JakobVoss: New page: The '''Citation Style Language''' (CSL) is an XML-Based stylesheet language for formatting of citations and bibliographies. It is used in reference management software such as Zotero, ...

User:JakobVoss

2010-04-28T11:19:10Z

JakobVoss:

* [[DAIA extensions]]
* [[Library Ontology]]
* [[Citation Style Language]] (CSL)
----
* =[http://www.gbv.de/wikis/cls/Benutzer:Voss Voss@GBV-Verbundwiki]

Library Ontology Concepts

2010-04-11T19:56:07Z

JakobVoss: /* Properties */ libo:exemplar

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 [http://en.wikipedia.org/wiki/Turtle_(syntax) Turtle syntax]):

<pre>
# 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 daia: <http://purl.org/ontology/daia/> .
@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
</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 ==
=== Library ===
A library can be a collection, an organization, or a place.

<pre>
: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 ) .
</pre>

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

=== Library Services ===
See DAIA (see http://purl.org/ontology/daia/ and [http://www.gbv.de/wikis/cls/DAIA_Format/RDF some notes])

=== Other concepts ===
holding, store, stack, loan...

== Properties ==

=== FRBR simplified ===

* libo:exemplar can link a work, expression or manifestation to an item
* libo:exemplarOf implies beeing a frbr:item but nothing less

=== Identifiers ===
<pre>
:isil rdf:type owl:DatatypeProperty ;
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?

Library Ontology

2010-04-07T17:14:39Z

JakobVoss: /* Relevant formats and models */ +institutional identifier schema

= Library Ontology Draft =
Editor: ''Jakob Voß'' (but everybody feel free to modify this page, it's a wiki!)

The '''Library Ontology''' is a proposed RDFS/OWL ontology to describe information about libraries in RDF. Up to now it is drafted in an open planning phase. There are many [[#Relevant_formats_and_models|formats and some ontologies]] for bibliographic data, addresses, and places which could be reused (instead of reinventing the wheel). Information about libraries is collected in several [[#Existing_library_registries|library registries]] which could be mapped to the Library Ontology.

''No background needed but fluent in RDF/Turtle syntax? Then goto [[Library Ontology Concepts]]!''

__TOC__
== Purpose ==
The purpose of the Library Ontology can best be described by examples and use cases. For example how do you state and express (in RDF) ...

* that something is a library?
* that some library building belongs to a given library institution?
* opening times in RDF?
* the URL of the OPAC of a library?
* which fees are bound to the use of the library (library card, reminder charges etc.)?
* that a given collection is held by one library?
* that a given collection is owned by someone?
* the type of a library (if "type" is a usefull concept at all)?
* ...

''please add more use-cases when you stumble upon!''

Some information can be expressed by existing Ontologies like vCard, but surely there are concepts and relationships which only make sense in context of libraries. The Library Ontology should define this RDFS/OWL classes and properties and collect existing classes and properties to be used for the description of libraries.

== Concepts ==
The basic concepts of the Library Ontology are collected at the page '''[[Library Ontology Concepts]]'''.

== Existing library registries ==
The [http://biblstandard.dk/isil/ International ISIL Agency] maintains a registry of library registries which act as local ISIL authorities.

* English speaking countries or international
** [http://www.librarytechnology.org/libwebcats/ lib-web-cats]: maintained by Marshall Breeding
** [http://www.worldcat.org/registry/Institutions/ WorldCat Registry]: by OCLC
** [http://lists.webjunction.org/libweb/ LibWeb]: only name, place, and URL
** [http://directory.talis.com/ui/ Talis Directory]
** [http://www.librarything.com/local LibraryThing Local]
** [http://irspy.indexdata.com/ IRSpy]: Indexdata Z39.50 Target Directory
** [http://www.ockham.org/registry.php OCKHAM Digital Library Services Registry]
** [http://archives.eprints.org Registry of Open Access Repositories (ROAR)]
* Germany
** [http://dispatch.opac.d-nb.de/DB=1.2/ ISIL- und Sigelverzeichnis]: German ISIL registry
** [http://www.hebis.de/de/1ueber_uns/projekte/bibdir.php BibDir]: proposed German project
** [http://www.hbz-nrw.de/produkte_dienstl/germlst/index.html Deutsche Bibliotheken Online]: will be replaced by BibDir
** [http://www.vdb-online.info/jahrbuch.html VdB Jahrbuch]: German printed registry
** [http://www.bock-net.de/joeb/ Jahrbuch der Öffentlichen Bibliotheken]: Another German printed registry
** [http://webis.sub.uni-hamburg.de/ WEBIS]: special collections of the distributed German National Library

Other related projects:
* [http://www.gils.net/ Global Information Locator Service (GILS)]

== Other linked data sources with library information ==
* libris.kb.se
* dbpedia
* ...

== Relevant formats and models ==
* RDFS/OWL Ontologies
** [http://dublincore.org/documents/dcmi-terms/ Dublin Core Metadata Terms]
** [http://xmlns.com/foaf/spec/ FOAF]
** [http://motools.sf.net/event/event.html Event Ontology]
** [http://www.w3.org/2008/05/skos SKOS]
** [http://www.w3.org/2006/vcard vCard]
** [http://www.w3.org/2003/01/geo/ Basic Geo (WGS84 lat/long) Vocabulary]
** [http://purl.org/vocab/frbr/core FRBR]
** [http://schemas.talis.com/2005/library/schema Talis Library Schema]
** [http://www.talis.com/tdn/platform/reference/schemas/address Talis Address Schema]
** [http://schemas.talis.com/2005/dir/schema Talis Directory Schema]
** [http://bibliontology.com/ Bibliographic Ontology (Bibo)]: OWL Ontology
** [http://www.cidoc-crm.org/ CIDOC-CRM]: Data Model with OWL representation
** [http://purl.org/goodrelations/ GoodRelations]: includes for instance OpeningHoursSpecification and [http://developer.yahoo.com/searchmonkey/smguide/gr.html recognizable to Yahoo!'s SearchMonkey]
** [http://vocab.org/aiiso/schema Academic Institution Internal Structure Ontology (AIISO)]: Includes foaf:Organization subclasses
** [http://purl.org/NET/book/vocab RDF Book Vocabulary]
** [http://purl.org/net/cito/ CiTO, The Citation Typing Ontology]: OWL Ontology
** [http://www.mesur.org/MESUR.html MESUR] (semantic model of the scholarly communication process)
** [http://marcont.org/ontology/index.html#term_documentation/marcont.html MarcOnt Ontology Specification] (for the sake of completeness)
** [http://gist.github.com/358857 Institutional identifier schema]
** ...
* Other formats
** [http://www.loc.gov/marc/community/eccihome.html MARC Communities format]
** [http://www.zeitschriftendatenbank.de/erschliessung/arbeitsunterlagen/zeta.html#c10787 ZETA format] (used in Sigelverzeichnis)
** WorldCat Registry XML Schemas
*** http://worldcat.org/registry/xsd/collections/Institutions/institution.xsd
*** http://worldcat.org/registry/xsd/collections/Institutions/identifiers.xsd
*** http://worldcat.org/registry/xsd/collections/Institutions/nameLocation.xsd
*** http://worldcat.org/registry/xsd/collections/Institutions/branches.xsd
*** http://worldcat.org/registry/xsd/collections/Institutions/opac.xsd
*** http://worldcat.org/registry/xsd/collections/Institutions/virtualReference.xsd
*** http://worldcat.org/registry/xsd/collections/Institutions/administrative.xsd
*** http://worldcat.org/registry/xsd/collections/Institutions/people.xsd
*** http://worldcat.org/registry/xsd/collections/Institutions/openURL.xsd
** [http://wiki.openstreetmap.org/wiki/Tag:amenity=library OpenStreemap library tags]
** [http://en.wikipedia.org/wiki/Template:Infobox_Library Wikipedia library template]: Base of DBPedia, different in each language edition
** [http://www.niso.org/workrooms/i2 I2 (Institutional Identifiers)]: NISO working group
** [http://www.nla.gov.au/wgroups/ISO2146/ ISO 2146] A framework for registry services in the form of an object-oriented data model.
** Gonçalves, Fox, and Watson: ''[http://www.dcs.vein.hu/CIR/cikkek/MFIR_DLOntology4.pdf Towards a digital library theory: a formal digital library ontology].'' In: International Journal on Digital Libraries archive. Volume 8, Issue 2 (April 2008), pp 91-114 (includes a data model of digital libraries)
** [http://www.delos.info/index.php?option=com_content&task=view&id=345 DELOS Reference Model for Digital Library Management Systems]
** [http://esw.w3.org/OpeningHoursUseCase Opening Hours Use Case on the ESW Wiki]
** Kruk, Sebastian Ryszard, and Bill McDaniel. [http://dx.doi.org/10.1007/978-3-540-85434-0 Semantic Digital Libraries]. Berlin: Springer, 2009.

Library Ontology Concepts

2010-04-07T17:07:50Z

JakobVoss: +DAIA

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 [http://en.wikipedia.org/wiki/Turtle_(syntax) Turtle syntax]):

<pre>
# 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 daia: <http://purl.org/ontology/daia/> .
@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
</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 ==
=== Library ===
A library can be a collection, an organization, or a place.

<pre>
: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 ) .
</pre>

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

=== Library Services ===
See DAIA (see http://purl.org/ontology/daia/ and [http://www.gbv.de/wikis/cls/DAIA_Format/RDF some notes])

=== Other concepts ===
holding, store, stack, loan...

=== Properties ===

=== Identifiers ===
<pre>
:isil rdf:type owl:DatatypeProperty ;
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?

User:JakobVoss

2009-12-18T11:15:23Z

JakobVoss:

* [[DAIA extensions]]
* [[Library Ontology]]
----
* =[http://www.gbv.de/wikis/cls/Benutzer:Voss Voss@GBV-Verbundwiki]

User:JakobVoss

2009-12-18T11:10:11Z

JakobVoss:

* [[DAIA extensions]]
* [[Library Ontology]]

{{User:JakobVoss/LISWikis}}

Library Ontology

2009-12-15T20:40:32Z

JakobVoss: /* Relevant formats and models */ +WorldCat Registry XML Schemas

= Library Ontology Draft =
Editor: ''Jakob Voß'' (but everybody feel free to modify this page, it's a wiki!)

The '''Library Ontology''' is a proposed RDFS/OWL ontology to describe information about libraries in RDF. Up to now it is drafted in an open planning phase. There are many [[#Relevant_formats_and_models|formats and some ontologies]] for bibliographic data, addresses, and places which could be reused (instead of reinventing the wheel). Information about libraries is collected in several [[#Existing_library_registries|library registries]] which could be mapped to the Library Ontology.

''No background needed but fluent in RDF/Turtle syntax? Then goto [[Library Ontology Concepts]]!''

__TOC__
== Purpose ==
The purpose of the Library Ontology can best be described by examples and use cases. For example how do you state and express (in RDF) ...

* that something is a library?
* that some library building belongs to a given library institution?
* opening times in RDF?
* the URL of the OPAC of a library?
* that a given collection is held by one library?
* that a given collection is owned by someone?
* the type of a library (if "type" is a usefull concept at all)?
* ...

''please add more use-cases when you stumble upon!''

Some information can be expressed by existing Ontologies like vCard, but surely there are concepts and relationships which only make sense in context of libraries. The Library Ontology should define this RDFS/OWL classes and properties and collect existing classes and properties to be used for the description of libraries.

== Concepts ==
The basic concepts of the Library Ontology are collected at the page '''[[Library Ontology Concepts]]'''.

== Existing library registries ==
The [http://biblstandard.dk/isil/ International ISIL Agency] maintains a registry of library registries which act as local ISIL authorities.

* English speaking countries or international
** [http://www.librarytechnology.org/libwebcats/ lib-web-cats]: maintained by Marshall Breeding
** [http://www.worldcat.org/registry/Institutions/ WorldCat Registry]: by OCLC
** [http://lists.webjunction.org/libweb/ LibWeb]: only name, place, and URL
** [http://directory.talis.com/ui/ Talis Directory]
** [http://www.librarything.com/local LibraryThing Local]
** [http://irspy.indexdata.com/ IRSpy]: Indexdata Z39.50 Target Directory
** [http://www.ockham.org/registry.php OCKHAM Digital Library Services Registry]
** [http://archives.eprints.org Registry of Open Access Repositories (ROAR)]
* Germany
** [http://dispatch.opac.d-nb.de/DB=1.2/ ISIL- und Sigelverzeichnis]: German ISIL registry
** [http://www.hebis.de/de/1ueber_uns/projekte/bibdir.php BibDir]: proposed German project
** [http://www.hbz-nrw.de/produkte_dienstl/germlst/index.html Deutsche Bibliotheken Online]: will be replaced by BibDir
** [http://www.vdb-online.info/jahrbuch.html VdB Jahrbuch]: German printed registry
** [http://www.bock-net.de/joeb/ Jahrbuch der Öffentlichen Bibliotheken]: Another German printed registry
** [http://webis.sub.uni-hamburg.de/ WEBIS]: special collections of the distributed German National Library

Other related projects:
* [http://www.gils.net/ Global Information Locator Service (GILS)]

== Other linked data sources with library information ==
* libris.kb.se
* dbpedia
* ...

== Relevant formats and models ==
* RDFS/OWL Ontologies
** [http://dublincore.org/documents/dcmi-terms/ Dublin Core Metadata Terms]
** [http://xmlns.com/foaf/spec/ FOAF]
** [http://motools.sf.net/event/event.html Event Ontology]
** [http://www.w3.org/2008/05/skos SKOS]
** [http://www.w3.org/2006/vcard vCard]
** [http://www.w3.org/2003/01/geo/ Basic Geo (WGS84 lat/long) Vocabulary]
** [http://purl.org/vocab/frbr/core FRBR]
** [http://schemas.talis.com/2005/library/schema Talis Library Schema]
** [http://www.talis.com/tdn/platform/reference/schemas/address Talis Address Schema]
** [http://schemas.talis.com/2005/dir/schema Talis Directory Schema]
** [http://bibliontology.com/ Bibliographic Ontology (Bibo)]: OWL Ontology
** [http://www.cidoc-crm.org/ CIDOC-CRM]: Data Model with OWL representation
** [http://purl.org/goodrelations/ GoodRelations]: includes for instance OpeningHoursSpecification and [http://developer.yahoo.com/searchmonkey/smguide/gr.html recognizable to Yahoo!'s SearchMonkey]
** [http://vocab.org/aiiso/schema Academic Institution Internal Structure Ontology (AIISO)]: Includes foaf:Organization subclasses
** [http://purl.org/NET/book/vocab RDF Book Vocabulary]
** [http://purl.org/net/cito/ CiTO, The Citation Typing Ontology]: OWL Ontology
** [http://www.mesur.org/MESUR.html MESUR] (semantic model of the scholarly communication process)
** ...
* Other formats
** [http://www.loc.gov/marc/community/eccihome.html MARC Communities format]
** [http://www.zeitschriftendatenbank.de/erschliessung/arbeitsunterlagen/zeta.html#c10787 ZETA format] (used in Sigelverzeichnis)
** WorldCat Registry XML Schemas
*** http://worldcat.org/registry/xsd/collections/Institutions/institution.xsd
*** http://worldcat.org/registry/xsd/collections/Institutions/identifiers.xsd
*** http://worldcat.org/registry/xsd/collections/Institutions/nameLocation.xsd
*** http://worldcat.org/registry/xsd/collections/Institutions/branches.xsd
*** http://worldcat.org/registry/xsd/collections/Institutions/opac.xsd
*** http://worldcat.org/registry/xsd/collections/Institutions/virtualReference.xsd
*** http://worldcat.org/registry/xsd/collections/Institutions/administrative.xsd
*** http://worldcat.org/registry/xsd/collections/Institutions/people.xsd
*** http://worldcat.org/registry/xsd/collections/Institutions/openURL.xsd
** [http://wiki.openstreetmap.org/wiki/Tag:amenity=library OpenStreemap library tags]
** [http://en.wikipedia.org/wiki/Template:Infobox_Library Wikipedia library template]: Base of DBPedia, different in each language edition
** [http://www.niso.org/workrooms/i2 I2 (Institutional Identifiers)]: NISO working group
** [http://www.nla.gov.au/wgroups/ISO2146/ ISO 2146] A framework for registry services in the form of an object-oriented data model.
** Gonçalves, Fox, and Watson: ''[http://www.dcs.vein.hu/CIR/cikkek/MFIR_DLOntology4.pdf Towards a digital library theory: a formal digital library ontology].'' In: International Journal on Digital Libraries archive. Volume 8, Issue 2 (April 2008), pp 91-114 (includes a data model of digital libraries)
** [http://www.delos.info/index.php?option=com_content&task=view&id=345 DELOS Reference Model for Digital Library Management Systems]

Library Ontology

2009-12-15T08:44:30Z

JakobVoss: /* Relevant formats and models */ +DELOS and Gonçalves

= Library Ontology Draft =
Editor: ''Jakob Voß'' (but everybody feel free to modify this page, it's a wiki!)

The '''Library Ontology''' is a proposed RDFS/OWL ontology to describe information about libraries in RDF. Up to now it is drafted in an open planning phase. There are many [[#Relevant_formats_and_models|formats and some ontologies]] for bibliographic data, addresses, and places which could be reused (instead of reinventing the wheel). Information about libraries is collected in several [[#Existing_library_registries|library registries]] which could be mapped to the Library Ontology.

''No background needed but fluent in RDF/Turtle syntax? Then goto [[Library Ontology Concepts]]!''

__TOC__
== Purpose ==
The purpose of the Library Ontology can best be described by examples and use cases. For example how do you state and express (in RDF) ...

* that something is a library?
* that some library building belongs to a given library institution?
* opening times in RDF?
* the URL of the OPAC of a library?
* that a given collection is held by one library?
* that a given collection is owned by someone?
* the type of a library (if "type" is a usefull concept at all)?
* ...

''please add more use-cases when you stumble upon!''

Some information can be expressed by existing Ontologies like vCard, but surely there are concepts and relationships which only make sense in context of libraries. The Library Ontology should define this RDFS/OWL classes and properties and collect existing classes and properties to be used for the description of libraries.

== Concepts ==
The basic concepts of the Library Ontology are collected at the page '''[[Library Ontology Concepts]]'''.

== Existing library registries ==
The [http://biblstandard.dk/isil/ International ISIL Agency] maintains a registry of library registries which act as local ISIL authorities.

* English speaking countries or international
** [http://www.librarytechnology.org/libwebcats/ lib-web-cats]: maintained by Marshall Breeding
** [http://www.worldcat.org/registry/Institutions/ WorldCat Registry]: by OCLC
** [http://lists.webjunction.org/libweb/ LibWeb]: only name, place, and URL
** [http://directory.talis.com/ui/ Talis Directory]
** [http://www.librarything.com/local LibraryThing Local]
** [http://irspy.indexdata.com/ IRSpy]: Indexdata Z39.50 Target Directory
** [http://www.ockham.org/registry.php OCKHAM Digital Library Services Registry]
** [http://archives.eprints.org Registry of Open Access Repositories (ROAR)]
* Germany
** [http://dispatch.opac.d-nb.de/DB=1.2/ ISIL- und Sigelverzeichnis]: German ISIL registry
** [http://www.hebis.de/de/1ueber_uns/projekte/bibdir.php BibDir]: proposed German project
** [http://www.hbz-nrw.de/produkte_dienstl/germlst/index.html Deutsche Bibliotheken Online]: will be replaced by BibDir
** [http://www.vdb-online.info/jahrbuch.html VdB Jahrbuch]: German printed registry
** [http://www.bock-net.de/joeb/ Jahrbuch der Öffentlichen Bibliotheken]: Another German printed registry
** [http://webis.sub.uni-hamburg.de/ WEBIS]: special collections of the distributed German National Library

Other related projects:
* [http://www.gils.net/ Global Information Locator Service (GILS)]

== Other linked data sources with library information ==
* libris.kb.se
* dbpedia
* ...

== Relevant formats and models ==
* RDFS/OWL Ontologies
** [http://dublincore.org/documents/dcmi-terms/ Dublin Core Metadata Terms]
** [http://xmlns.com/foaf/spec/ FOAF]
** [http://motools.sf.net/event/event.html Event Ontology]
** [http://www.w3.org/2008/05/skos SKOS]
** [http://www.w3.org/2006/vcard vCard]
** [http://www.w3.org/2003/01/geo/ Basic Geo (WGS84 lat/long) Vocabulary]
** [http://purl.org/vocab/frbr/core FRBR]
** [http://schemas.talis.com/2005/library/schema Talis Library Schema]
** [http://www.talis.com/tdn/platform/reference/schemas/address Talis Address Schema]
** [http://schemas.talis.com/2005/dir/schema Talis Directory Schema]
** [http://bibliontology.com/ Bibliographic Ontology (Bibo)]: OWL Ontology
** [http://www.cidoc-crm.org/ CIDOC-CRM]: Data Model with OWL representation
** [http://purl.org/goodrelations/ GoodRelations]: includes for instance OpeningHoursSpecification and [http://developer.yahoo.com/searchmonkey/smguide/gr.html recognizable to Yahoo!'s SearchMonkey]
** [http://vocab.org/aiiso/schema Academic Institution Internal Structure Ontology (AIISO)]: Includes foaf:Organization subclasses
** [http://purl.org/NET/book/vocab RDF Book Vocabulary]
** [http://purl.org/net/cito/ CiTO, The Citation Typing Ontology]: OWL Ontology
** [http://www.mesur.org/MESUR.html MESUR] (semantic model of the scholarly communication process)
** ...
* Other formats
** [http://www.loc.gov/marc/community/eccihome.html MARC Communities format]
** [http://www.zeitschriftendatenbank.de/erschliessung/arbeitsunterlagen/zeta.html#c10787 ZETA format] (used in Sigelverzeichnis)
** [http://wiki.openstreetmap.org/wiki/Tag:amenity=library OpenStreemap library tags]
** [http://en.wikipedia.org/wiki/Template:Infobox_Library Wikipedia library template]: Base of DBPedia, different in each language edition
** [http://www.niso.org/workrooms/i2 I2 (Institutional Identifiers)]: NISO working group
** [http://www.nla.gov.au/wgroups/ISO2146/ ISO 2146] A framework for registry services in the form of an object-oriented data model.
** Gonçalves, Fox, and Watson: ''[http://www.dcs.vein.hu/CIR/cikkek/MFIR_DLOntology4.pdf Towards a digital library theory: a formal digital library ontology].'' In: International Journal on Digital Libraries archive. Volume 8, Issue 2 (April 2008), pp 91-114 (includes a data model of digital libraries)
** [http://www.delos.info/index.php?option=com_content&task=view&id=345 DELOS Reference Model for Digital Library Management Systems]

Library Ontology

2009-12-15T08:35:54Z

JakobVoss: /* Relevant formats and models */ +MESUR

= Library Ontology Draft =
Editor: ''Jakob Voß'' (but everybody feel free to modify this page, it's a wiki!)

The '''Library Ontology''' is a proposed RDFS/OWL ontology to describe information about libraries in RDF. Up to now it is drafted in an open planning phase. There are many [[#Relevant_formats_and_models|formats and some ontologies]] for bibliographic data, addresses, and places which could be reused (instead of reinventing the wheel). Information about libraries is collected in several [[#Existing_library_registries|library registries]] which could be mapped to the Library Ontology.

''No background needed but fluent in RDF/Turtle syntax? Then goto [[Library Ontology Concepts]]!''

__TOC__
== Purpose ==
The purpose of the Library Ontology can best be described by examples and use cases. For example how do you state and express (in RDF) ...

* that something is a library?
* that some library building belongs to a given library institution?
* opening times in RDF?
* the URL of the OPAC of a library?
* that a given collection is held by one library?
* that a given collection is owned by someone?
* the type of a library (if "type" is a usefull concept at all)?
* ...

''please add more use-cases when you stumble upon!''

Some information can be expressed by existing Ontologies like vCard, but surely there are concepts and relationships which only make sense in context of libraries. The Library Ontology should define this RDFS/OWL classes and properties and collect existing classes and properties to be used for the description of libraries.

== Concepts ==
The basic concepts of the Library Ontology are collected at the page '''[[Library Ontology Concepts]]'''.

== Existing library registries ==
The [http://biblstandard.dk/isil/ International ISIL Agency] maintains a registry of library registries which act as local ISIL authorities.

* English speaking countries or international
** [http://www.librarytechnology.org/libwebcats/ lib-web-cats]: maintained by Marshall Breeding
** [http://www.worldcat.org/registry/Institutions/ WorldCat Registry]: by OCLC
** [http://lists.webjunction.org/libweb/ LibWeb]: only name, place, and URL
** [http://directory.talis.com/ui/ Talis Directory]
** [http://www.librarything.com/local LibraryThing Local]
** [http://irspy.indexdata.com/ IRSpy]: Indexdata Z39.50 Target Directory
** [http://www.ockham.org/registry.php OCKHAM Digital Library Services Registry]
** [http://archives.eprints.org Registry of Open Access Repositories (ROAR)]
* Germany
** [http://dispatch.opac.d-nb.de/DB=1.2/ ISIL- und Sigelverzeichnis]: German ISIL registry
** [http://www.hebis.de/de/1ueber_uns/projekte/bibdir.php BibDir]: proposed German project
** [http://www.hbz-nrw.de/produkte_dienstl/germlst/index.html Deutsche Bibliotheken Online]: will be replaced by BibDir
** [http://www.vdb-online.info/jahrbuch.html VdB Jahrbuch]: German printed registry
** [http://www.bock-net.de/joeb/ Jahrbuch der Öffentlichen Bibliotheken]: Another German printed registry
** [http://webis.sub.uni-hamburg.de/ WEBIS]: special collections of the distributed German National Library

Other related projects:
* [http://www.gils.net/ Global Information Locator Service (GILS)]

== Other linked data sources with library information ==
* libris.kb.se
* dbpedia
* ...

== Relevant formats and models ==
* RDFS/OWL Ontologies
** [http://dublincore.org/documents/dcmi-terms/ Dublin Core Metadata Terms]
** [http://xmlns.com/foaf/spec/ FOAF]
** [http://motools.sf.net/event/event.html Event Ontology]
** [http://www.w3.org/2008/05/skos SKOS]
** [http://www.w3.org/2006/vcard vCard]
** [http://www.w3.org/2003/01/geo/ Basic Geo (WGS84 lat/long) Vocabulary]
** [http://purl.org/vocab/frbr/core FRBR]
** [http://schemas.talis.com/2005/library/schema Talis Library Schema]
** [http://www.talis.com/tdn/platform/reference/schemas/address Talis Address Schema]
** [http://schemas.talis.com/2005/dir/schema Talis Directory Schema]
** [http://bibliontology.com/ Bibliographic Ontology (Bibo)]: OWL Ontology
** [http://www.cidoc-crm.org/ CIDOC-CRM]: Data Model with OWL representation
** [http://purl.org/goodrelations/ GoodRelations]: includes for instance OpeningHoursSpecification and [http://developer.yahoo.com/searchmonkey/smguide/gr.html recognizable to Yahoo!'s SearchMonkey]
** [http://vocab.org/aiiso/schema Academic Institution Internal Structure Ontology (AIISO)]: Includes foaf:Organization subclasses
** [http://purl.org/NET/book/vocab RDF Book Vocabulary]
** [http://purl.org/net/cito/ CiTO, The Citation Typing Ontology]: OWL Ontology
** [http://www.mesur.org/MESUR.html MESUR] (semantic model of the scholarly communication process)
** ...
* Other formats
** [http://www.loc.gov/marc/community/eccihome.html MARC Communities format]
** [http://www.zeitschriftendatenbank.de/erschliessung/arbeitsunterlagen/zeta.html#c10787 ZETA format] (used in Sigelverzeichnis)
** [http://wiki.openstreetmap.org/wiki/Tag:amenity=library OpenStreemap library tags]
** [http://en.wikipedia.org/wiki/Template:Infobox_Library Wikipedia library template]: Base of DBPedia, different in each language edition
** [http://www.niso.org/workrooms/i2 I2 (Institutional Identifiers)]: NISO working group
** [http://www.nla.gov.au/wgroups/ISO2146/ ISO 2146] A framework for registry services in the form of an object-oriented data model.

Library Ontology

2009-12-09T12:58:54Z

JakobVoss: more soruces from feedback at NGC4LIB

= Library Ontology Draft =
Editor: ''Jakob Voß'' (but everybody feel free to modify this page, it's a wiki!)

The '''Library Ontology''' is a proposed RDFS/OWL ontology to describe information about libraries in RDF. Up to now it is drafted in an open planning phase. There are many [[#Relevant_formats_and_models|formats and some ontologies]] for bibliographic data, addresses, and places which could be reused (instead of reinventing the wheel). Information about libraries is collected in several [[#Existing_library_registries|library registries]] which could be mapped to the Library Ontology.

''No background needed but fluent in RDF/Turtle syntax? Then goto [[Library Ontology Concepts]]!''

__TOC__
== Purpose ==
The purpose of the Library Ontology can best be described by examples and use cases. For example how do you state and express (in RDF) ...

* that something is a library?
* that some library building belongs to a given library institution?
* opening times in RDF?
* the URL of the OPAC of a library?
* that a given collection is held by one library?
* that a given collection is owned by someone?
* the type of a library (if "type" is a usefull concept at all)?
* ...

''please add more use-cases when you stumble upon!''

Some information can be expressed by existing Ontologies like vCard, but surely there are concepts and relationships which only make sense in context of libraries. The Library Ontology should define this RDFS/OWL classes and properties and collect existing classes and properties to be used for the description of libraries.

== Concepts ==
The basic concepts of the Library Ontology are collected at the page '''[[Library Ontology Concepts]]'''.

== Existing library registries ==
The [http://biblstandard.dk/isil/ International ISIL Agency] maintains a registry of library registries which act as local ISIL authorities.

* English speaking countries or international
** [http://www.librarytechnology.org/libwebcats/ lib-web-cats]: maintained by Marshall Breeding
** [http://www.worldcat.org/registry/Institutions/ WorldCat Registry]: by OCLC
** [http://lists.webjunction.org/libweb/ LibWeb]: only name, place, and URL
** [http://directory.talis.com/ui/ Talis Directory]
** [http://www.librarything.com/local LibraryThing Local]
** [http://irspy.indexdata.com/ IRSpy]: Indexdata Z39.50 Target Directory
** [http://www.ockham.org/registry.php OCKHAM Digital Library Services Registry]
** [http://archives.eprints.org Registry of Open Access Repositories (ROAR)]
* Germany
** [http://dispatch.opac.d-nb.de/DB=1.2/ ISIL- und Sigelverzeichnis]: German ISIL registry
** [http://www.hebis.de/de/1ueber_uns/projekte/bibdir.php BibDir]: proposed German project
** [http://www.hbz-nrw.de/produkte_dienstl/germlst/index.html Deutsche Bibliotheken Online]: will be replaced by BibDir
** [http://www.vdb-online.info/jahrbuch.html VdB Jahrbuch]: German printed registry
** [http://www.bock-net.de/joeb/ Jahrbuch der Öffentlichen Bibliotheken]: Another German printed registry
** [http://webis.sub.uni-hamburg.de/ WEBIS]: special collections of the distributed German National Library

Other related projects:
* [http://www.gils.net/ Global Information Locator Service (GILS)]

== Other linked data sources with library information ==
* libris.kb.se
* dbpedia
* ...

== Relevant formats and models ==
* RDFS/OWL Ontologies
** [http://dublincore.org/documents/dcmi-terms/ Dublin Core Metadata Terms]
** [http://xmlns.com/foaf/spec/ FOAF]
** [http://motools.sf.net/event/event.html Event Ontology]
** [http://www.w3.org/2008/05/skos SKOS]
** [http://www.w3.org/2006/vcard vCard]
** [http://www.w3.org/2003/01/geo/ Basic Geo (WGS84 lat/long) Vocabulary]
** [http://purl.org/vocab/frbr/core FRBR]
** [http://schemas.talis.com/2005/library/schema Talis Library Schema]
** [http://www.talis.com/tdn/platform/reference/schemas/address Talis Address Schema]
** [http://schemas.talis.com/2005/dir/schema Talis Directory Schema]
** [http://bibliontology.com/ Bibliographic Ontology (Bibo)]: OWL Ontology
** [http://www.cidoc-crm.org/ CIDOC-CRM]
** [http://purl.org/goodrelations/ GoodRelations]: includes for instance OpeningHoursSpecification and [http://developer.yahoo.com/searchmonkey/smguide/gr.html recognizable to Yahoo!'s SearchMonkey]
** [http://vocab.org/aiiso/schema Academic Institution Internal Structure Ontology (AIISO)]: Includes foaf:Organization subclasses
** [http://purl.org/NET/book/vocab RDF Book Vocabulary]

** ...
* Other formats
** [http://www.loc.gov/marc/community/eccihome.html MARC Communities format]
** [http://www.zeitschriftendatenbank.de/erschliessung/arbeitsunterlagen/zeta.html#c10787 ZETA format] (used in Sigelverzeichnis)
** [http://wiki.openstreetmap.org/wiki/Tag:amenity=library OpenStreemap library tags]
** [http://en.wikipedia.org/wiki/Template:Infobox_Library Wikipedia library template]: Base of DBPedia, different in each language edition
** [http://www.niso.org/workrooms/i2 I2 (Institutional Identifiers)]: NISO working group
** ...

Library Ontology

2009-12-09T10:24:19Z

JakobVoss: /* Existing library registries */ +LibraryThing Local

Library Ontology Concepts

2009-12-08T22:01:15Z

JakobVoss:

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 [http://en.wikipedia.org/wiki/Turtle_(syntax) Turtle syntax]):

<pre>
# 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
</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 ==
=== Library ===
A library can be a collection, an organization, or a place.

<pre>
: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 ) .
</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])

=== Other concepts ===
holding, store, stack, loan...

=== Properties ===

=== Identifiers ===
<pre>
:isil rdf:type owl:DatatypeProperty ;
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?

Library Ontology Concepts

2009-12-08T22:00:34Z

JakobVoss:

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 [http://en.wikipedia.org/wiki/Turtle_(syntax) Turtle syntax]):

<pre>
# 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
</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 ==
=== Library ===
A library can be a collection, an organization, or a place.

<pre>
: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 ) .
</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])

== Other concepts ==
holding, store, stack, loan...

== Properties ==

=== Identifiers ===
<pre>
:isil rdf:type owl:DatatypeProperty ;
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?

Library Ontology

2009-12-08T21:43:06Z

JakobVoss: /* Relevant formats and models */ +cidoc-crm

Library Ontology

2009-12-08T21:37:15Z

JakobVoss: /* Relevant formats and models */ +ZETA

Library Ontology

2009-12-08T21:05:56Z

JakobVoss: +link

Library Ontology

2009-12-08T21:04:52Z

JakobVoss: /* Concepts */

Library Ontology Concepts

2009-12-08T21:03:46Z

JakobVoss: first concepts

Library Ontology

2009-12-08T20:41:23Z

JakobVoss: first public draft

User:JakobVoss

2009-12-08T20:00:40Z

JakobVoss: links

* [[DAIA extensions]]
* [[Library Ontology]]

Daia ext

2009-10-23T08:41:06Z

JakobVoss: #REDIRECT DAIA extensions

#REDIRECT [[DAIA extensions]]

DAIA

2009-10-23T08:40:56Z

JakobVoss: #REDIRECT DAIA extensions

#REDIRECT [[DAIA extensions]]

DAIA extensions

2009-10-23T08:40:36Z

JakobVoss: DAIA service types moved to DAIA extensions

This page collects some proposed service types and other suggestions as extension to the [http://purl.org/NET/DAIA Document Availability Information API].

== Additional Service types ==

=== Request ===
http://purl.org/NET/daia-ext/request

ILS 'request' function. Sadly, the typical ILS 'request' function can be used for a variety of actual services, including:
* recall a checked out item
* place a 'hold' on an item
* request an item for delivery to a particular location (circ desk or other)

Where possible, you should not use the 'request' service, but should instead use a service expressing a more specific action availability. However, actually existing ILS's can make it very hard to figure out what more specific actions are available, and it may still be useful to advertise the ILS 'request' function, this service represents that.

:Looks like a super-class of all service types with meaning "unknown". In this case we may better make the service field optional so if you can specify an unknown service. -- [[User:JakobVoss|JakobVoss]] 02:12, 29 September 2009 (PDT)
::That might work, as long as it's possible to specify a user-displayable label for the service. Won't be able to be understood/acted upon by software, but the user can still be told this is, say, a generic 'Request'.

=== Recall ===
http://purl.org/NET/daia-ext/recall

Recall a checked out item, which will typically then be placed on hold for you.

:Placed for you for what purpose? -- [[User:JakobVoss|JakobVoss]] 02:12, 29 September 2009 (PDT)
::So are you suggesting this shouldn't be a service of it's own, but instead should just be indicated in the 'delay' and user-displayable comments on the actual end-purpose service, that a 'recall' is possible? One thing is that in my library I am told that the user wants to know if they will be recalling the item from someone else or not before making the request.
:::This should better be encoded in the 'delay' and 'queue' attributes. If I understand you right, you want to encode whether an item is hold by someone else or is not available for some other reason. If we start encoding this, we can build an ontology of reasons why I cannot get a book (someone else holds it, it's a the bookbinder, the cat of the librarian is sitton on it...) which is not purpose of core DAIA. Maybe you could add a custom 'reason' field to unavailable or an 'obstacle' field to available/unavailable. -- [[User:JakobVoss|JakobVoss]] 01:39, 23 October 2009 (PDT)

=== Deliver ===
http://purl.org/NET/daia-ext/deliver

Request delivery of a physical item, to a circulation desk, an office, or even a home, depending on what the library provides.

:Does deliver imply loan? I think a broad "deliver" does not help, but more specific services like "home-deliver", "office-deliver" etc. as subtypes of "loan". Delivering to a circulation desk is not a specific service in my opinion. -- [[User:JakobVoss|JakobVoss]] 02:12, 29 September 2009 (PDT)

::Why is delivering to a circulation desk not a specific service? I guess I'm trying to figure out how to represent the services that my library actually does offer. Now, I kind of see your vision of services, and I WISH my library offered the kind of services you're thinking of, and in such a way that my software could actually predict them... but it kind of doesn't. And I'm not in charge.

:::There is a difference between deliver to a circulation desk for use in the rooms of the library (presentation) and for loaning. Deliver to an office or at home is a different kind of service that implies loan. To distinguish deliver to circulation desk and self-pick up with open-access shelving we may need another method. -- [[User:JakobVoss|JakobVoss]] 01:39, 23 October 2009 (PDT)

=== Excerpt ===
http://purl.org/NET/daia-ext/excerpt

Request library staff to make a photocopy or scan of a part (chapter or article) of a physical item, which will them be emailed or delivered to the user.
:Copying/Scaning as service makes sense. Is the act of copying the relevant service or the fact that you get only a part of the item as copy? -- [[User:JakobVoss|JakobVoss]] 02:12, 29 September 2009 (PDT)
::In my library, the nature of the service is that you only get part of the item AND you get choose what part. The act of copying isn't the relevant service, although I'm not sure how a library would provide a user-choice part of the item without copying, but if there's a way, that's fine! [[User:jrochkind]]
:::An item may have the ''fragment'' attribute but that would mean the library does only have a specific excerpt. So Excert looks like a reasonable service type. -- [[User:JakobVoss|JakobVoss]] 01:39, 23 October 2009 (PDT)

== Reference Client ==
There are many ways to interpret and display a DAIA result (traffic light, icons, detailed description, summary of items etc.). Maybe we can collect some best practise? -- [[User:JakobVoss|JakobVoss]] 01:39, 23 October 2009 (PDT)

DAIA service types

2009-10-23T08:40:36Z

JakobVoss: DAIA service types moved to DAIA extensions

#REDIRECT [[DAIA extensions]]

DAIA extensions

2009-10-23T08:39:57Z

JakobVoss: answers and strukturing

DAIA extensions

2009-09-29T09:12:10Z

JakobVoss: Comments

This page collects some proposed service types as extension to the [http://purl.org/NET/DAIA Document Availability Information API].

== Request ==
http://purl.org/NET/daia-ext/request

ILS 'request' function. Sadly, the typical ILS 'request' function can be used for a variety of actual services, including:
* recall a checked out item
* place a 'hold' on an item
* request an item for delivery to a particular location (circ desk or other)

Where possible, you should not use the 'request' service, but should instead use a service expressing a more specific action availability. However, actually existing ILS's can make it very hard to figure out what more specific actions are available, and it may still be useful to advertise the ILS 'request' function, this service represents that.

:Looks like a super-class of all service types with meaning "unknown". In this case we may better make the service field optional so if you can specify an unknown service. -- [[User:JakobVoss|JakobVoss]] 02:12, 29 September 2009 (PDT)

== Recall ==
http://purl.org/NET/daia-ext/recall

Recall a checked out item, which will typically then be placed on hold for you.

:Placed for you for what purpose? -- [[User:JakobVoss|JakobVoss]] 02:12, 29 September 2009 (PDT)

== Deliver ==
http://purl.org/NET/daia-ext/deliver

Request delivery of a physical item, to a circulation desk, an office, or even a home, depending on what the library provides.

:Does deliver imply loan? I think a broad "deliver" does not help, but more specific services like "home-deliver", "office-deliver" etc. as subtypes of "loan". Delivering to a circulation desk is not a specific service in my opinion. -- [[User:JakobVoss|JakobVoss]] 02:12, 29 September 2009 (PDT)

== Excerpt ==
http://purl.org/NET/daia-ext/excerpt

Request library staff to make a photocopy or scan of a part (chapter or article) of a physical item, which will them be emailed or delivered to the user.
:Copying/Scaning as service makes sense. Is the act of copying the relevant service or the fact that you get only a part of the item as copy? -- [[User:JakobVoss|JakobVoss]] 02:12, 29 September 2009 (PDT)

DAIA extensions

2009-09-29T08:29:30Z

JakobVoss: Daia ext moved to DAIA service types

Extension services for [http://wiki.code4lib.org/index.php/Daia_ext DAIA].

== Request ==
http://purl.org/NET/daia-ext/request

ILS 'request' function. Sadly, the typical ILS 'request' function can be used for a variety of actual services, including:
* recall a checked out item
* place a 'hold' on an item
* request an item for delivery to a particular location (circ desk or other)

Where possible, you should not use the 'request' service, but should instead use a service expressing a more specific action availability. However, actually existing ILS's can make it very hard to figure out what more specific actions are available, and it may still be useful to advertise the ILS 'request' function, this service represents that.

== Recall ==
http://purl.org/NET/daia-ext/recall

Recall a checked out item, which will typically then be placed on hold for you.

== Deliver ==
http://purl.org/NET/daia-ext/deliver

Request delivery of a physical item, to a circulation desk, an office, or even a home, depending on what the library provides.

== Excerpt ==
http://purl.org/NET/daia-ext/excerpt

Request library staff to make a photocopy or scan of a part (chapter or article) of a physical item, which will them be emailed or delivered to the user.

Daia ext

2009-09-29T08:29:30Z

JakobVoss: Daia ext moved to DAIA service types

#REDIRECT [[DAIA service types]]

Umlaut Technical Overview

2008-11-26T09:13:01Z

JakobVoss: link

To give you an overview of the technical architecture of [[Umlaut]], we will go through a typical Resolve request, identifying all the classes involved, and pointing to their api doc if possible.

OpenURLs are sent to the default index action of the [http://umlaut.rubyforge.org/api/files/app/controllers/resolve_controller_rb.html resolve controller].

In the resolve controller, a before filter method called init_processing is run to parse the OpenURL and set up the Umlaut request (or retrieve an existing request).

==Technical Overview Sections==

# [[Request Setup and Environmental Context]]
# [[ServiceResponse data structures and generation]] -- Includes guide to writing your own services.
# [[View architecture and control flow]]
# [[Background services]] -- control and view architectures for background services