Re: [CODE4LIB] viaf

The ontology document shouldn't 404s, but either way I'm pretty sure that all the vocabulary terms defined there are obsolete (e.g. viaf:NameAuthorityCluster). The diagram referenced in the 2011-04 Outgoing blog post is still current: http://outgoing.typepad.com/.a/6a00d83459bf2269e20147e410996

Re: [CODE4LIB] OpenURL linking but from the content provider's point of view

misunderstood. I thought David meant resolving > OpenURLs pointed at his content. > > Jason > > Jason Stirnaman > Digital Projects Librarian > A.R. Dykes Library > University of Kansas Medical Center > 913-588-7319 > > > From

Re: [CODE4LIB] OpenURL linking but from the content provider's point of view

If the referent has a DOI, then I would argue that rft_id=http://dx.doi.org/10.1145/2132176.2132212 is all you need. The descriptive information that typically goes in the ContextObject can be obtained (if necessary) by content-negotiating for application/rdf+xml. OTOH, if someone pokes this same U

Re: [CODE4LIB] COinS

Jonathan Rochkind wrote: > What do you mean by "suggest schema.org"? I'm suggesting Schema.org as a cross-domain extensible vocabulary that that can be (but doesn't have to be) embedded in HTML (e.g. via Microdata and/or RDFa

Re: [CODE4LIB] COinS

If the goal is to embed bibliographic metadata in HTML, I would suggest Schema.org instead of COinS. Jeff Jonathan Rochkind wrote: It _IS_ an old unused metadata format that should be replaced by something else (among other reasons because it's actually illegal in HTML5), but I'm not sure th

Re: [CODE4LIB] Worldcat schema.org & search API

Karen, Your output looks like it comes from the old 2007 RDFa 1.0 parser: http://www.w3.org/2007/08/pyRdfa/extract?uri=http%3A%2F%2Fwww.worldcat.org%2Foclc%2F527725&format=pretty-xml&warnings=false&parser=lax&space-preserve=true The new 2012 RDFa 1.1 parser does a better job: http://www.w3.org/

Re: [CODE4LIB] Planned changes to the VIAF RDF

"if", heh. > > Have you guys at VIAF made it clear to LC that you'd consider them > publishing in linked data to be a complement to VIAF, rather than > duplication? I think maybe some people think it'd be duplication, which > I think is not true. > > -Origin

Re: [CODE4LIB] Planned changes to the VIAF RDF

VIAF. The only VIAF contributors we're aware of today that publish their own authority Linked Data are Deutsche Nationalbibliothek, National Library of Sweden, and the National Széchényi Library (Hungary). Jeff From: Young,Jeff (OR) Sent: Tuesday, April 12, 2011 10:21 AM Subject: Plann

[CODE4LIB] Planned changes to the VIAF RDF

Thom Hickey posted a blog entry about our plans to streamline the VIAF RDF. http://outgoing.typepad.com/outgoing/2011/04/changes-to-viafs-rdf.html I can elaborate on the listserv if anyone wants to discuss the changes. Jeff --- Jeffrey A. Young Software Architect OCLC Research, Mai

Re: [CODE4LIB] FW: VIAF linked data and non-Latin searching

[CODE4LIB] FW: VIAF linked data and non-Latin searching > > Nice, Jeff. I really like the simplified VIAF RDF. In particular I > like how you've modeled the deprecation of resources. Are you planning > to use a 301, e.g. http://viaf.org/viaf/77390479/ -> > http://viaf.org/

[CODE4LIB] FW: VIAF linked data and non-Latin searching

To: v...@listserv.log.gov Cc: Young,Jeff (OR) Subject: VIAF linked data and non-Latin searching Non-Latin searching: We believe we have resolved a reoccurring issue with non-Latin searching failing (it had to do with restarting VIAF in different environments). If anyone still has issues with this, pleas

Re: [CODE4LIB] "universal citation index"

that URIs are names. It is impossible to express semantics adequately in a name. That's what HTTP GET and RDF are for. > and (b) how do we actually generate/store/query the > resulting > graph. Use Linked Data. Jeff > > Jodi, is any of this correct? > >

Re: [CODE4LIB] "universal citation index"

thing doesn't already exist. Jeff > -Original Message- > From: Tom Morris [mailto:tfmor...@gmail.com] > Sent: Tuesday, July 20, 2010 5:37 PM > To: Young,Jeff (OR) > Cc: Karen Coyle; Jodi Schneider; public-lld; Code for Libraries; Brian > Mingus > Subject: Re: &qu

Re: [CODE4LIB] "universal citation index"

-Original Message- > From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of > stuart yeates > Sent: Tuesday, July 20, 2010 4:14 PM > To: CODE4LIB@LISTSERV.ND.EDU > Subject: Re: [CODE4LIB] "universal citation index" > > Young,Jeff (OR) wrote: &g

Re: [CODE4LIB] "universal citation index"

eb Document URI: ??? Jeff > -Original Message- > From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of > Lars Aronsson > Sent: Tuesday, July 20, 2010 3:35 PM > To: CODE4LIB@LISTSERV.ND.EDU > Subject: Re: [CODE4LIB] "universal citation index"

Re: [CODE4LIB] "universal citation index"

I tried to keep the examples abstract in my earlier message, but probably to the point of obscurity. If you think these URIs or something like them would help, then convince someone at OCLC to implement them: http://www.worldcat.org/oclc/{oclc#}/citation-apa.txt (text/plain) http://www.worldcat.or

Re: [CODE4LIB] "universal citation index"

In terms of Linked Data, it should make sense to treat citations as text/plain variant representations of a FRBR Manifestation. The linking aspects can be handled in HTML and RDF representations. http://example.org/manifestation/1 (303 redirect to...) http://example.org/manifestation/1/ (Generic r

Re: [CODE4LIB] dc:identifier in Google XML

UOM presumably indicates some sort of identifier from the University of Michigan. UCSC is presumably University of California Santa Cruz. Try going to their library catalogs and see if the numbers that follow line up somehow. If the person who coined these identifiers understood Linked Data, we

Re: [CODE4LIB] Library Class Registration System

Mike, Google Docs might be worth a look. http://docs.google.com/support/bin/static.py?page=guide.cs&guide=20322&t opic=20330 Jeff -Original Message- From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of Bell, Mike (Libraries) Sent: Monday, July 12, 2010 4:17 PM To: COD

Re: [CODE4LIB] audio/video citations in an OpenURL

The sap2-2004 Community Profile (http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadat aPrefix=oai_dc&identifier=info:ofi/pro:sap2-2004) only recognizes oai_dc and MARC21. The mods metadata format was registered to support the rtm-2007 profile (http://alcme.oclc.org/openurl/serv

Re: [CODE4LIB] OpenURL code libraries?

Jonathan, The OpenURL Object Model is still in an alpha state, but we've been using it in some development projects here at OCLC for several months now. This is a different approach than what has been taken by other OpenURL implementation in that all the classes are designed to mirror the OpenURL

Re: [CODE4LIB] next generation opac mailing list

In our effort to redefine the future, it is important that we all challenge our assumptions. We should cherish our heretics, right or wrong. My $.02 is that we don't need yet another system; we need to develop and adopt standards and coerce everyone in sight to play along. Standards enable innovat

Re: [CODE4LIB] Authority records and the OSS ILS

Ed, Could you make a distributed solution work? We have a search service available at http://alcme.oclc.org/eprintsUK/index.html. (Currently, it only includes LC name authorities only.) Perhaps we could add COinS of some sort to allow you to link back into your system. Jeff > On 5/25/06, Edward