References on the web
by ostephens
- 1,300 views
Accessibility
Categories
Upload Details
Uploaded via SlideShare as Apple Keynote
Usage Rights
© All Rights Reserved
Statistics
- Likes
- 0
- Downloads
- 12
- Comments
- 0
- Embed Views
- Views on SlideShare
- 1,300
- Total Views
- 1,300
Pros
No special skills for authors
Clarity
Full descriptions can be held in appropriate systems
No messy stuff in the HTML
Cons
Some Identifiers are not perfect
Not all items have identifiers (although this can be
Not all identifiers ‘resolvable’
Error prone
However, only real use is for (mainly) bibliographic material – books, chapters, articles
Was originally introduced because of ‘appropriate copy’ problem
OpenURLs made up of ‘resolver address’ and context object. Works well in dynamic page with user context (e.g. bib database) but not so well on open web
Hence COinS – Context Object in Span
Pros:
Well established in libraries, already used by Zotero and others to extract metadata
Metadata in the page – stands alone
Links into resolvers
Doesn’t require identifier, but can exploit them if they are available
Backwards compatible – wide range of browsers
Cons:
Someone has to create the COinS
Lack of takeup outside library sector
OpenURL is long and ugly standard – tends to be disliked by implementers!
Microformats – build on existing standards to enable you to embed ‘semantics’ into XHTML
Specifically hCard and hCalendar have proved popular
Example http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/sessions/kelly/
Pros
Combine human readable and computer readable versions of data – no duplication
Metadata in the page – stands alone
Doesn’t require identifier
Backwards compatible to any XHTML
Cons:
Mixes human readable and computer readable versions of data – leads to confusion, and more complex data structures
Lack of take-up of microformats excepting hCard and hCalendar
Possible accessibility issues (re BBC decision to drop hCalendar)
No ‘use case’ (unlike COinS)
As far as I know not consumed by existing tools (e.g. Zotero)
Combine human readable and computer readable versions of data – no duplication
Metadata in the page – stands alone
Doesn’t require identifier
Backwards compatible to any XHTML
Cons:
Mixes human readable and computer readable versions of data – leads to confusion, and more complex data structures
Lack of take-up of microformats excepting hCard and hCalendar - is hCitation going anywhere?
Possible accessibility issues (re BBC decision to drop hCalendar)
No ‘use case’ (unlike COinS)
As far as I know not consumed by existing tools (e.g. Zotero)
JSON (Javascript Notation)
MARC-JSON
BibJSON http://www.bibkn.org/bibjson/index.html
CSL example http://serials.infomotions.com/code4lib/archive/2010/201004/1203.html
CSL
Citeproc-js
(seen as) simple
in-line styling
Separates display elements from data
CSL
Cons:
Essentially a variation on use of identifier
No well-established schema
Not a single type of data
Enables you to embed RDF statements into web pages
Pros
Combine human readable and computer readable versions of data – no duplication
Metadata in the page – stands alone
Doesn’t require identifier
Growing number of tools that can extract RDFa – Zotero working on it?
Part of growing ‘linked data’ movement
Cons:
Mixes human readable and computer readable versions of data – leads to confusion, and more complex data structures
No widespread takeup yet – although some significant uses (e.g. O’Reilly)
Requires new doc type = XHTML+RDFa
Enables you to embed RDF statements into web pages
Describes the way in which it is being used