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:

Proportional Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  November 2011

BIBFRAME November 2011

Subject:

Re: Introduction (@W3C)

From:

"John, Phil (CSS)" <[log in to unmask]>

Reply-To:

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

Date:

Thu, 10 Nov 2011 10:03:39 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (123 lines)

Worth pointing out that Lexvo was used by the BL in their recent RDF modelling exercise: http://www.bl.uk/bibliographic/datafree.html

Phil John
Technical Lead, Capita Software Services
Knights Court, Solihull Parkway
Birmingham Business Park B37 7YB

Office: 0870 400 5000
Fax: 0870 400 5001
email: [log in to unmask]
  
Part of The Capita Group plc www.capita.co.uk 

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

Charles,

On Nov 9, 2011, at 21:39 , Riley, Charles wrote:

> Hi Ivan,
> 
> Welcome!  

Thank you.


> 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?
> 

With my Semantic Web/RDF hat on: RDF has made the choice of (1) use Unicode ("The lexical space of a datatype is a set of Unicode [UNICODE] strings."[1]) and, if needed, the language tag (the 2004 version of RDF referred to rfc 3066, the new one in preparation relies on bcp47[2]). I would think that the combination of these two should provide a standard for interchanging data; even if a particular language or script is not present in the current standards, these are evolving, so by sufficient peer pressure (and the library community has the possibility to provide such a pressure) any missing entry could be added, eventually.

I can imagine that, in some cases, you would need a richer description of the language involved, eg, for a human reader. This could be incorporated into an RDF based vocabulary using existing ontologies and URI references. The one I know just a bit is lexvo:

http://www.lexvo.org/

that provides URI-s for languages, as well as some description that can be linked to. For example, if I take Hungarian, it provides a URI for the language:

http://lexvo.org/id/term/hun/

there is an RDF representation for this URI which links further to a more detailed information (through the http://lexvo.org/ontology#language property) to:

http://www.lexvo.org/page/iso639-3/hun

which then includes further information about Hungarian (essentially the various labels of the language in different languages).

The beauty of the Linked Data is that, from the library community point of view, there is no need to repeat this information; you should just link to it and let other people feel the pain of keeping that data up to date...

I hope this answers your question!

Cheers

Ivan

P.S. I am not an internationalization expert, but I have a colleague at W3C (Richard Ishida) who is really really knowledgeable in this. Some of the services he provides on his web page may be helpful here (see [3] or [4] for language tag and unicode lookup), and his page on the W3C on the language tag may also be interesting...




[1] http://www.w3.org/TR/rdf-concepts/#section-Datatypes
[2] http://tools.ietf.org/html/bcp47
[3] http://rishida.net/utils/subtags/
[4] http://rishida.net/scripts/uniview/
[4] http://www.w3.org/International/articles/language-tags/Overview.en.php

> 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] http://www.w3.org/blog/SW/2011/10/27/w3c-library-linked-data-xg-final-report-published/
> [3] http://www.w3.org/2001/sw/
> 
> ----
> 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


----
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


This email and any attachment to it are confidential.  Unless you are the intended recipient, you may not use, copy or disclose either the message or any information contained in the message. If you are not the intended recipient, you should delete this email and notify the sender immediately.

Any views or opinions expressed in this email are those of the sender only, unless otherwise stated.  All copyright in any Capita material in this email is reserved.

All emails, incoming and outgoing, may be recorded by Capita and monitored for legitimate business purposes. 

Capita exclude all liability for any loss or damage arising or resulting from the receipt, use or transmission of this email to the fullest extent permitted by law.

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

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