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:

"Riley, Charles" <[log in to unmask]>

Reply-To:

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

Date:

Wed, 9 Nov 2011 20:39:00 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (43 lines)

Hi Ivan,

Welcome! Character encoding and SKOS mappings might be a good place to start.

Bibliographic data is largely built on the MARC-8 character set, in essence a subset of UTF-8; thus a loss of data for the preponderance of materials in non-Latin scripts has already occurred by the time data becomes bibliographic. Similarly, ISO 639-2B is more or less a subset of the languages represented in ISO 639-3: languages of literary warrant having passed a threshold of being used in fifty or more texts. MARC language codes in many cases still carry an outdated colonial legacy: uv for Burkina Faso (the former Upper Volta), rh for Zimbabwe (Rhodesia), dm for Benin (Dahomey).

What are some of the ways you might envision allowing our data to mesh better with that which exists in the rest of the world?

Charles Riley

-----Original Message-----
From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of Ivan Herman
Sent: Wednesday, November 09, 2011 12:31 PM
To: [log in to unmask]
Subject: [BIBFRAME] Introduction (@W3C)

As a new member of this mailing list, allow me to introduce myself and the institution I represent.

I am what we call in our jargon the Semantic Web Activity Lead at the W3C. What this means in practice is that I initiate and coordinate most (if not all) Semantic Web related groups at the W3C and I am also responsible for the outreach activities around the Semantic Web.

I was very excited to see the initiative of the US Library of Congress[1]. From my point of view, this initiative will be an important contribution to the vision of the Semantic Web or, to use another term, a Web of Data on which library data at large would at last take its well deserved place.

I will not repeat that arguments on the benefits for the Library Community of using Linked Library Data. This has been documented in a report of a W3C Incubator Group[2]; they have made a much better job that I would ever do. However, I can express why I believe such a synergy would also be beneficial for the Semantic Web community. Indeed, the Semantic Web envisions a Web of Data, i.e., a place where different types of data can be integrated, used by applications or by end users, regardless of the origin and the exact location of that data. The Web has given us this for documents; it is time to have the same for data in general. However, it is inconceivable to envisage this without the huge amount of data, repositories, catalogues, accumulated knowledge, etc, that is available in libraries around the globe. Furthermore, and that may be less obvious to the library community, the unique experience that this community has in cataloguing, archiving, and managing resources can bring a hugely important extra experience and knowledge to the Semantic Web community, research and development alike.

I am not a librarian. This means that there are many technical and social issues discussed on this list that I cannot really contribute to. 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. I would also be happy to take the problems raised by this group and feed them back to the relevant Working Groups that are currently active at the W3C (see, for example, [3] for some of those). I.e., I hope I can be of help.

Of course, there may specific technical issues and solutions coming up in future that might require further standardization in future; W3C may have a role to play then and I will be happy to discuss this if and when the time comes.

Sincerely

Ivan Herman


[1] http://www.loc.gov/marc/transition/news/framework-103111.html
[2]