LISTSERV mailing list manager LISTSERV 16.0

Help for BIBFRAME Archives


BIBFRAME Archives

BIBFRAME Archives


BIBFRAME@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  November 2011

BIBFRAME November 2011

Subject:

Re: Introduction (@W3C)

From:

Ivan Herman <[log in to unmask]>

Reply-To:

Bibliographic Framework Transition Initiative Forum <[log in to unmask]>

Date:

Thu, 10 Nov 2011 11:06:41 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (65 lines)

On Nov 10, 2011, at 10:33 , Bernhard Eversberg wrote:

> Am 10.11.2011 09:41, schrieb Ivan Herman:
>>>>
>>>> ... However, I would be very pleased to provide
>>>> feedback, whenever that is necessary, on specific, Semantic Web
>>>> related technical questions concerning the intricacies of RDF,
>>>> OWL, SKOS, or SPARQL.
>
> Are these the tools or cornerstones of the Semantic Web, and nothing
> else besides?

Cornerstones: yes. Nothing else: no. This is an evolving area, and I expect new technologies and approaches to appear that a larger 'Web of Data' should work with in some way or other...


> There are some projects that have published library data
> in RDF; do you know of promising applications based on these?
>

For me, the boundaries are blurred, I must admit. To take one example, the URI-s provided by the LC for their authorities provide a fixed and stable reference for a number of subjects that people use to annotate, say, their bibliographic entries but also other online documents. Entry points like these to the cataloguing world would become an essential element for a number of applications. Projects on cultural heritage, to take another area, that has become really important in the past few years (eg, the Europeana project) would/should/could also rely on such references.

Tom Baker or Dan Brickley (cc-d) are more familiar with these areas, they may have more specific examples.

> The goal of this Transition Initiative is, first and foremost, to
> find a successor to the now 40 years old MARC bibliographic record
> format. This format or its future successor is, however, nothing that
> would have to be openly exposed on the web or used for communication
> with end-users. Appropriate web services should be able to deliver
> data in whatever form web applications may need it. Much in the way
> of this might be done right now, if only the database engines were
> open enough to allow for easy contruction of services; mostly, they
> are proprietary commercial software packages.
>
> Could you name a few functions for library data on the web which you
> would give a high priority? A lot of functionality is conceivable, so
> we could use ideas about priorities.

Wow. I cannot necessarily describe that in terms of explicit functions. But... I would like to have an easy way to access library catalogues all over the world, to find the most up-to-date information on, say, Bach's Hohe Messe (to take a non-book example). Using Linked Data, I should be able, actually, to _integrate_ that various data on that work that is around the globe, including the list of recordings, maybe the reviews, etc. Much of this type of data is in libraries already but, today, the only source people have is to go to, say, Wikipedia (or its RDF dump, DBPedia) and similar sites. Lots of information are missing out today.

Of course, if the digital data is also available, then a reference to that is also of a great value (although I am aware that this is bound to access control issue).

Mind you: this is my personal opinion. Others in the community may have other priorities...


>
> You are aware that we have millions of legacy data with all sorts
> of limitations, and no way to get rid of these...
>

Of course. I would expect some sort of a translation service, so to say. You may know that there is a work going on mapping RDB-s to RDF; essentially, providing some sort of an on-the-fly translation, at least in some cases, to SQL data but seen through an RDF goggle. Maybe something similar is conceivable for that legacy data, but I may be optimistic...

Cheers

Ivan


> B.Eversberg


----
Ivan Herman, W3C Semantic Web Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
FOAF: http://www.ivan-herman.net/foaf.rdf

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
July 2011
June 2011

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager