Re: [CODE4LIB] First draft of patron account API
Hi,
[CODE4LIB] Classification of loan types
Hi, is there an established classification of loan types, preferable as Ontology with URIs for each type? I am not sure about the English terminology with terms such as loan, hold and recall. In particular I am looking for a simple (!) list of types for current relationships between a patron and
[CODE4LIB] Mapping vocabularies (was: LCSH and Linked Data)
- The Kingdom of Great Britain (1707 to 1801) - The United Kingdom of Great Britain and Ireland (1801 to 1922) - etc. I gave a talk about the fruitless attempt to put reality in terms of Semantic Web at Wikimania 2007 (stating with slide 12):
[CODE4LIB] XML Schema vs Library APIs (OAI-PMH/SRU/unAPI)
Hi, We are developing a general API management tool to provide different APIs (unAPI, SRU, OAI-PMH...) with different record formats (MARC, MODS, DC...) to our databases. We now stumbled upon some confusion regarding XML formats. The basic question is what is a format and how do you refer to
[CODE4LIB] Bibliography of Code4Lib journal
Hi,
Re: [CODE4LIB] Twitter annotations and library software
On 07.06.2010 16:15, Jay Luker wrote: Hi all, I found this thread rather interesting and figured I'd try and revive the convo since apparently some things have been happening in the twitter annotation space in the past month. I just read on techcrunch that testing of the annotation features] Handling non-Unicode characters (was: Unicode persistence)
Hi Stuart, These have been included because they are in widespread use in a current written culture. The problems I personally have are down to characters used by a single publisher in a handful of books more than a hundred years ago. Such characters are explicitly excluded from Unicode. In
[CODE4LIB] Unicode persistence (was: it's cool to hate on OpenURL)
Eric Hellman wrote: May I just add here that of all the things we've talked about in these threads, perhaps the only thing that will still be in use a hundred years from now will be Unicode. إن شاء الله Stuart Yeates wrote: Sadly, yes, I agree with you on this. Do you have any idea how
Re: [CODE4LIB] it's cool to hate on OpenURL
Stuart Yeates wrote: A great deal of heat has been vented in this thread, and at least a little light. I'd like to invite everyone to contribute to the wikipedia page at in the hopes that it evolves into a better overview of the protocol, the ecosystem
Re: [CODE4LIB] Twitter annotations and library software
Jonathan Rochkind wrote: Call me pedantic but if you do not have an identifier than there is no hope to identity the publication by means of metadata. You only *describe* it with metadata and use additional heuristics (mostly search engines) to hopefully identify the publication based on the
Re: [CODE4LIB] Twitter annotations and library software
Dear Tim, you wrote: So this is my recommended framework for proceeding. Tim, I'm afraid you'll actually have to do the hard work yourself. No, I don't. Because the work isn't fundamentally that hard. A complex standard might be, but I never for a moment considered anything like that. We have
Re: [CODE4LIB] it's cool to hate on OpenURL (was: Twitter annotations...)
Eric Hellman wrote: What I hope for is that OpenURL 1.0 eventually takes a place alongside SGML as a too-complex standard that directly paves the way for a universally adopted foundational technology like XML. What I fear is that it takes a place alongside MARC as an anachronistic standard that
Re: [CODE4LIB] Twitter annotations and library software
Hi it's funny how quickly you vote against BibTeX, but at least it is a format that is frequently used in the wild to create citations. If you call BibTeX undocumented and garbage then how do you call MARC which is far more difficult to make use of? My assumption was that there is a
Re: [CODE4LIB] Twitter annotations and library software
Ed Summers wrote: II. Description: To nicely show which publication someone refers to. I think this is right. I wonder, would you consider a potential use case for Description to also provide machine readable data for a resource when a standard identifier is not known? There are lookup
Re: [CODE4LIB] Twitter annotations and library software
Jonathan Rochkind wrote: Jakob Voss wrote: I. Identifiy publication = this can *only* be done seriously with identifiers like ISBN, DOI, OCLCNum, LCCN etc. Ah, but for better or for worse, that's not the world we live in. We have LOTS of publications that either lack such identifiers
Re: [CODE4LIB] Twitter annotations and library software
Hi Tim, you wrote: Unless someone can come up with a perfect pre-cooked format—one that not only covers what we need but is also super easy and space-efficient (we have only 1/2k to use!)—Why don't we just decide on: 'simplebib' : { } and start filling in fields. I don't think it makes
[CODE4LIB] DAIA project hosted at SourceForge
Hi, I'd just like to announce that we moved our DAIA related resources [1] to SourceForge: DAIA is a data model to express information about the availability of documents and
[CODE4LIB] Availability Information API
Hi, I just wanted to announce that I finished a reference implementation of the Document Availability Information API (DAIA) as CPAN module at. More information about DAIA can be found in the specification at and at
Re: [CODE4LIB] One Data Format Identifier (and Registry) to Rule Them All
Ross Singer wrote: ?xml version=1.0 encoding=UTF-8? formats xmlns=; format name=foaf uri= /formats I generally agree with this, but what about formats that aren't XML or RDF based? How do I also say that you can grab my text/x-vcard? Or my
Re: [CODE4LIB] One Data Format Identifier (and Registry) to Rule Them All
Hi, I summarized my thoughts about identifiers for data formats in a blog posting: In short it’s not a technology issue but a commitment issue and the problem of identifying the right identifiers for data formats can be reduced
[CODE4LIB] Formats and its identifiers
Hi Rob, You wrote: A format should be described with a schema (XML Schema, OWL etc.) or at least a standard. Mostly this schema already has a namespace or similar identifier that can be used for the whole format. This is unfortunately not the case. It is mostly the case - but people like] RDA - a standard that nobody will notice?
:// It would be a pitty if RDA is an irrelevant anachronism from the beginning just because it is not published the way standards need to be published on the Web. Greetings Jakob Voss [1]
Re: [CODE4LIB] RFC 5005 ATOM extension and OAI
Hi Clay,.
Re: [CODE4LIB] RFC 5005 ATOM extension and OAI
Peter wrote: Also, re: blog mirroring, I highly recommend the current discussions floating aroung the blogosphere regarding distributed source control (Git, Mercurial, etc.). It's a fundamental paradigm shift from centralized control to distributed control that points the way toward the future
Re: [CODE4LIB] RFC 5005 ATOM extension and OAI
Hi Ed, You wrote: I completely agree. When developing software it's really important to focus on the cleanest/clearest solution, rather than getting bogged down in edge cases and the comments from nay sayers. I hope that my response didn't come across that way. :-) A couple follow on
Re: [CODE4LIB] RFC 5005 ATOM extension and OAI
Ed Summers wrote: Thanks for posting this Jakob. I was just reading RFC 5005 on the train yesterday (literally) and the parallels between it and OAI-PMH struck me as well. It's not quite clear to me how deleted records would be handled with an atom archive feed. But I guess one could assume if