[RDA-L] DCMI RDA Workshop at DC-2010

[gor...@gordondunsire.com]

Apologies for cross-posting. Sent on behalf of the DCMI RDA Task Group.

The DCMI RDA Task Group is hosting a workshop at the forthcoming DC-2010
conference in Pittsburgh (20-22 October 2010). The workshop will take place on
Friday 22 October 2010, 2.00-3.30 pm.

The agenda for the meeting is available at
http://dublincore.org/dcmirdataskgroup/DC_2d2010_20Meeting

The workshop will be presented with the latest information about the
representation of the RDA element set and vocabularies in RDF, and news of
related initiatives such as the representation of the Functional Requirements
family of models (Bibliographic Records, Authority Data, and Subject Authority
Data), RDA/ONIX Framework for Resource Categorization, and International
Standard Bibliographic Description - all in RDF. A report from the W3C's Library
Linked Data Incubator Group will also be included.

The workshop will be of interest to librarians and developers involved with the
Semantic Web, linked-data, and the future of libraries.

All full and day delegates to DC-2010 are welcome.

We look forward to seeing you at the workshop.
 
Cheers
 
Gordon
 
Gordon Dunsire (Co-chair, DCMI RDA Task Group)

[RDA-L] Call for Use Cases: Library Linked Data

[gor...@gordondunsire.com]

[apologies for cross-posting]

W3C Library Linked Data Incubator Group - http://www.w3.org/2005/Incubator/lld/

Call for Use Cases: Library Linked Data

Are you currently using linked data technology [1] for library-related data, or
considering doing it in the near future? If so, please tell us more by filling
in the questionnaire below and sending it back to us or to public-...@w3.org,
preferably before October 15th, 2010.

The information you provide will be influential in guiding the activities the
Library Linked Data Incubator Group will undertake to help increase global
interoperability of library data on the Web. The information you provide will
be curated and published on the group wikispace at [3].

We understand that your time is precious, so please don't feel you have to
answer every question. Some sections of the templates are clearly marked as
optional. However, the more information you can provide, the easier it will be
for the Incubator Group to understand your case. And, of course, please do not
hesitate to contact us if you have any trouble answering our questions.
Editorial guidance on specific points is provided at [2], and examples are
available at [3].

We are particularly interested in use cases describing the use of library
linked data for end-user oriented applications. However, we're not ruling
anything out at this stage, and the Incubator Group will carefully consider
all submissions we receive.

On behalf of the Incubator Group, thanks in advance for your time,

Emmanuelle Bermes (Emmanuelle.Bermes_bnf.fr), Alexander Haffner
(A.Haffner_d-nb.de),
Antoine Isaac (aisaac_few.vu.nl) and Jodi Schneider (jodi.schneider_deri.org)

[1] http://www.w3.org/DesignIssues/LinkedData.html
[2] http://www.w3.org/2005/Incubator/lld/wiki/UCCuration
[3] http://www.w3.org/2005/Incubator/lld/wiki/UseCases




=== Name ===

A short name by which we can refer to the use case in discussions.

=== Owner ===

The contact person for this use case.

=== Background and Current Practice ===

Where this use case takes place in a specific domain, and so requires some prior
information to understand, this section is used to describe that domain. As far
as possible, please put explanation of the domain in here, to keep the scenario
as short as possible. If this scenario is best illustrated by showing how
applying
technology could replace current existing practice, then this section can be
used
to describe the current practice. Often, the key to why a use case is important
also lies in what problem would occur if it was not achieved, or what problem
means it is hard to achieve.

=== Goal ===

Two short statements stating (1) what is achieved in the scenario without
reference to linked data, and (2) how we use linked data technology to achieve
this goal.

=== Target Audience ===

The main audience of your case. For example scholars, the general public,
service
providers, archivists, computer programs...

=== Use Case Scenario ===

The use case scenario itself, described as a story in which actors interact with
systems. This section should focus on the user needs in this scenario. Do not
mention technical aspects and/or the use of linked data.

=== Application of linked data for the given use case ===

This section describes how linked data technology could be used to support the
use case above. Try to focus on linked data on an abstract level, without
mentioning concrete applications and/or vocabularies. Hint: Nothing library
domain specific.

=== Existing Work (optional) ===

This section is used to refer to existing technologies or approaches which
achieve
the use case (Hint: Specific approaches in the library domain). It may
especially
refer to running prototypes or applications.

=== Related Vocabularies (optional) ===

Here you can list and clarify the use of vocabularies (element sets and value
vocabularies) which can be helpful and applied within this context.

=== Problems and Limitations (optional) ===

This section lists reasons why this scenario is or may be difficult to achieve,
including pre-requisites which may not be met, technological obstacles etc.
Please
explicitly list here the technical challenges made apparent by this use case.
This
will aid in creating a roadmap to overcome those challenges.

=== Related Use Cases and Unanticipated Uses (optional) ===

The scenario above describes a particular case of using linked data. However, by
allowing this scenario to take place, the likely solution allows for other use
cases. This section captures unanticipated uses of the same system apparent in
the
use case scenario.

=== References (optional) ===

This section is used to refer to cited literature and quoted websites.

[RDA-L] Five years on: major conference on libraries and the Semantic Web, 27 April 2012 - Final announcement

[gor...@gordondunsire.com]

 There are still places available for the Seminar “Five years on”, marking
the five years of progress in library linked data since the “London
Meeting” of 2007. The Seminar takes place on Friday 27 April 2012, 09.00/30
to 17.00. The venue for the Seminar is the British Library, St. Pancras,
London.

The final list of speakers for the Seminar includes:



* Mikael Nilsson, Google
* Edmund Chamberlain, Cambridge University Library
* Alan Danskin, British Library
* Barbara Tillett, Joint Steering Committee for the Development of RDA
(JSC)
* Robina Claphan, Europeana
* Mirna Willer, IFLA ISBD Review Group
* Pat Riva, IFLA FRBR Review Group
* Thomas Baker, DCMI
* Gordon Dunsire, IFLA Namespaces Technical Group and DCMI
* Diane Hillmann, DCMI and Metadata Management Associates
* Owen Stephens, JISC

The London Meeting of 31 April/1 May 2007 stimulated significant
development of Semantic Web representations of the major international
bibliographic metadata models, including IFLA’s Functional Requirements
family and the International Standard Bibliographic Description (ISBD), and
MARC as well as RDA itself. Attention is now beginning to focus on the
management and sustainability of this activity, and the development of
high-level semantic and data structures to support library applications.

Registration for the Seminar has been set at USD 190 (including VAT), which
includes lunch and refreshments for two breaks. Further information and
online registration is available at:

http://dcevents.dublincore.org/index.php/BibData/fyo

Please note that registration for the DCMI meetings on Thursday 26 April
has now closed, as all places have been taken.

Cheers, and apologies for cross-posting.

Diane Hillmann (Moderator, DCMI Vocabulary Management Community; Co-Chair,
DCMI Bibliographic Metadata Task Group)
Gordon Dunsire (Co-Chair, DCMI Bibliographic Metadata Task Group)

Re: [RDA-L] Order of 040 subfields

[gor...@gordondunsire.com]

It also matters when it comes to semantic analysis of the MARC21 schema for
linked data and Semantic Web applications. See the last paragraph of my blog
post:

http://managemetadata.com/blog/2012/06/07/by-passing-taggregations/

It matters even more when the provenance of the billions of data triples derived
from existing MARC21 records is needed to distinguish them from metadata
generated by end-users and machines, which will be orders of magnitude higher in
number.

Cheers

Gordon


On 20 August 2012 at 14:26 Mike Tribby  wrote:

> "I have been following this thread about the 040. Does it really matter what
> order the subfields are placed in in  the 040 in an online environment?"
>
> It matters greatly (at least theoretically) to those who enjoy assigning blame
> to specific cataloging agencies for what they perceive to be bad cataloging.
> It's a bad tool for doing that, but righteous sentiment about avenging
> cataloging "errors" seems to overwhelm that.
>
>
>
> Mike Tribby
> Senior Cataloger
> Quality Books Inc.
> The Best of America's Independent Presses
>
> mailto:mike.tri...@quality-books.com

Re: [RDA-L] JSC, ISBD, and ISSN: harmonization discussions

[gor...@gordondunsire.com]

To clarify how far down the road ISBD and RDA are in RDF representations: The
ISBD element set and value vocabularies in English and Spanish have been in
"published" status in the Open Metadata Registry since March 2012. Croatian and
Italian translations of the value vocabularies are in development. A draft ISBD
Application Profile has been developed. The RDA element set in the same registry
is in "new-proposed" status. Some of the RDA value vocabularies are in
"published" status, with German translations in development.

For ISBD elements and vocabularies, and their status, see:

http://iflastandards.info/ns/isbd/

For RDA elements and vocabularies, and their status, see:

http://rdvocab.info/

Cheers

Gordon


On 16 August 2012 at 07:25 John Hostage  wrote:


> I think most people would agree that AACR2 was based on the ISBD.  The
> essential characteristics were the 8 areas of description, a prescribed order
> of elements, and prescribed punctuation.  Although some claim that ISBD is one
> of the foundations of RDA, I see RDA as a fairly clean break with that
> tradition.  Punctuation and order of elements are relegated to an appendix.
> 
>  There is now a study group working on an RDF representation of the ISBD as
> well as mappings with RDA, but since RDA is so much further along on this
> road, one has to wonder if the effort is worthwhile.
> 
>  The UNIMARC format
> (http://www.ifla.org/en/publications/unimarc-formats-and-related-documentation
> 
> ) attempts to keep in alignment with the ISBD.  The concise format is
> available for free download of the PDF file, but the full format is only
> available for sale. This is now a burning issue within IFLA for this and other
> standards.  From the concise format you can see that it's similar to MARC 21
> in its use of fields, subfields, and indicators, but the fields represent
> different things.
> 
>  Germany is planning to switch to RDA (a translation is in progress), but up
> to now they have used RAK
> (http://de.wikipedia.org/wiki/Regeln_f%C3%BCr_die_alphabetische_Katalogisierung
> 
> ) (sorry, no English page) for description and access points.  The descriptive
> part was also based on ISBD.
> 
>  Subject headings are a specialized area because they are so language
> dependent.  The Bibliotheque nationale de France has developed RAMEAU
> (http://www.bnf.fr/en/professionals/anx_cataloging_indexing/a.subject_reference_systems.html
> 
> ), which I think was based on LCSH.  The Deutsche Nationalbibliothek has the
> Schlagwortnormdatei
> (http://en.wikipedia.org/wiki/Subject_Headings_Authority_File
>  ), which is a
> very different system of descriptors.  I think Italy has its own subject
> heading list.
> 
>  I'm not familiar with what other countries use.
> 
>  --
>  John Hostage
>  Authorities and Database Integrity Librarian
>  Langdell Hall
>  Harvard Law School Library
>  Cambridge, MA 02138
>  host...@law.harvard.edu 
>  +(1)(617) 495-3974 (voice)
>  +(1)(617) 496-4409 (fax)
>  http://www.law.harvard.edu/library/ 
> 
> 
> 
>