> FrontPage

The following 496 words could not be found in the dictionary of 550 words (including 550 LocalSpellingWords) and are highlighted below:

01hillmann   5rda   A2   About   about   ac   Access   adding   agendas   agreed   agreements   aimed   ala   all   Allen   allow   an   An   Anaheim   Analyse   Analysis   analysis   and   Announcements   Annual   ap   Application   application   applications   appropriate   approved   April   Architecture   archives   as   Assign   at   attributes   August   authority   available   background   based   be   Become   been   before   Begins   behind   being   between   bibliographic   Bibliographic   bin   bl   blog   Blog   blogspot   Brad   bradleypallen   British   broader   building   by   ca   came   can   Can   candidates   carrier   Cases   cases   Cataloger   catalogingfutures   Charter   choices   chosen   Christine   City   classes   Co   code   Code4   code4lib   Code4lib   code4lib2008   code4rda   collaborative   collectionscanada   com   Comments   comments   Comparison   complete   Completed   components   concept   concern   Conference   Congress   Contact   containing   context   Control   controlled   conversion   Conversion   Core   Cornell   cost   Coyle   Create   create   created   data   Data   dataset   date   dc   dcmirdataskgroup   decided   declared   Define   define   defined   definitions   Del   Deliverables   deliverables   Description   design   Designs   dev   Develop   Developer   developing   development   diane   Diane   discussed   discusses   discussion   dlib   doc   docs   document   documents   domain   done   draft   Dublin   dublincore   Dunsire   each   effort   efforts   element   Element   elementanalysisrev   elements   empty   enable   end   entities   entity   etc   examples   exceptions   exclamation   excluded   expect   explaining   explanation   expressing   Extract   fall   far   for   formal   Forum   forwarded   frad   fradmapping   frbr   frbrmappingrev   from   front   Functional   funding   further   future   Future   garden   gathered   general   General   generalist   Goals   google   Gordon   gov   Group   groups   guide   has   held   here   Hillmann   hillmann   historical   id   identify   Identify   ification   ifla   implemented   implications   in   included   including   ind0802   information   infrastructure   initiative   interactions   interest   internally   interviews   is   Is   issues   it   its   Jan   january10   jiscmail   jonphipps   jsc   June   Karen   kcoyle   labels   lack   large   led   level   Lib   librarian   Libraries   librarieswiki   Library   library   line   link   linked   list   List   listing   Listing   lists   loc   located   location   London   made   Magazine   mail   manage   managed   mapping   Mar   March   may9   meeeting   meeting   Meeting   meetings   Metadata   metadata   metadataregistry   midterm   Milestone   milestone   Milestones   mock   Model   model   modeling   more   namespace   Namespace   namespaces   net   new   New   nodes   not   note   Note   notes   now   ns   October   of   on   one   One   open   or   organization   originally   other   Our   our   out   outcome   Outcome   output   outputs   packet   page   pages   Pages   Participants   particular   pdf   perhaps   plan   Plan   planning   Podcast   policies   policy   possible   post   pr   preliminary   Preliminary   presentation   Process   Produce   producing   Product   profile   Profile   Profiles   project   Project   Proof   properties   property   proposed   pubguide   public   publication   Published   publishing   purposed   Quebec   quick   Quick   rda   rdadc   rdf   re   recommendation   regarding   registered   registration   Registry   registry   relationship   relationships   relevant   remaining   remains   Report   report   reports   representation   representations   represented   requirements   Resource   resources   Resources   Review   review   revised   Revised   Rigorous   rules   s13   sandbox   Scenarios   schema   Schneider   Schwartz   scope   secret   See   see   Seeking   select   Semantic   service   services   set   should   show   single   skos   slide   slideshare   so   some   Some   specification   Specify   standard   still   Strathclyde   swbp   syntaxes   Syracuse   taken   Talis   talis   talk   Talking   Task   task   Task1   tasks   Tasks   techsource   Test   testimony   testing   text   that   the   The   then   thesaurus   these   this   This   those   though   Timetable   to   To   tools   uk   University   Update   updated   ups   use   Use   used   user   User   using   value   vlists   Vocab   Vocabularies   vocabularies   Vocabulary   vocabulary   Volume   w3   was   Washington   We   Web   web   webadmin   webarch   Webcast   webcasts   well   which   whose   Wide   will   with   work   Work   Working   Workplan   World   would   yet  

Clear message

DCMI/RDA Task Group Wiki

This Task Group is for collaborative work to enable broader use of the Resource Description and Access (RDA), building on agreements made at a [WWW]meeting held at the British Library April 30/May 1, 2007. Participants in the meeting came from DCMI and other Semantic Web groups, and the RDA development effort. The Task Group is led by Diane Hillmann (then of Cornell University, now at Syracuse University) and Gordon Dunsire of Strathclyde University.

The planning for the London meeting was originally located on the [WWW]DC-Libraries Wiki Some information gathered for the meeting, including documents, agendas, a meeting packet, and other information of historical interest remains at that location.

Announcements

Mar. 2011 midterm report

DC-2010 Meeting

[WWW]Work Begins

Wiki Pages

Charter and Work Plan

Charter: To define components of the draft standard "RDA - Resource Description and Access" as an RDF vocabulary for use in developing a Dublin Core application profile.

Workplan for RDA Vocabularies Project

1. Define RDA modeling entities as an RDF vocabulary (properties and classes).

Tasks

Task 1.1 Analyse the RDA data model entities to identify those elements that will be included in the declared “RDA Element Vocabulary”. analysisTask1

Task 1.2 Produce a report explaining the choices made and listing open issues regarding those excluded (modeling issues, cost etc.) [an preliminary discussion document is being discussed internally]

Task 1.3 Specify each element in the vocabulary using the agreed attributes (see [WWW]here for a possible set (to be updated with more DCAM-appropriate labels))

Task 1.4 Create an RDA namespace (a recommendation has been forwarded to JSC/CoP for this)

Task 1.5 Assign URIs to each element [The NSDL Registry tools created and manage these using an RDA domain]

Task 1.6 Create web pages containing the element specification [The NSDL Registry tools can create and manage these as well]

Task 1.7 Create an RDF schema representation of the vocabulary [The NSDL Registry tools can create this output; review of the output has been discussed]

Deliverables

Del 1.1 Listing of elements to be declared as the RDA element vocabulary

Del 1.2 Report explaining the choices made in producing the list and open issues

Del 1.3 An RDA namespace

Del 1.4 A set of web pages containing the specification of the RDA Element Vocabulary

Del 1.5 An RDF schema of the RDA Element Vocabulary

2. Identify in-line value vocabularies as candidates for publication in [WWW]RDFS or [WWW]SKOS.

Tasks

Task 2.1 Analyse the RDA Element Vocabulary to identify those elements whose value would be taken from a controlled vocabulary in the library domain.

Task 2.2 Extract the controlled vocabularies from RDA for SKOS-ification

Task 2.3 Produce a report explaining the choices made and listing open issues.

Task 2.4 Produce RDF representations of the chosen vocabularies using SKOS

Deliverables

Del 2.1 A set of controlled vocabularies represented in RDF/SKOS

Del 2.2 Report explaining the choices made and listing open issues

Timetable/Milestones for Goals 1 & 2

March 31, 2008:

[This date was chosen to allow this set of deliverables to be available for discussion at the JSC meeting in April]

TM 1.1 Preliminary set of elements available as "proposed" in the NSDL Registry (with RDA Namespace, definitions and URIs), with registry outputs in RDF (vocabulary and single element level) and XML schema.

TM 1.2 Wiki available behind the proposed elements in the Registry, available for managed public discussion

TM 1.3 Report explaining the choices made so far and an explanation of open issues

June 15, 2008

This milestone should allow revised work to be available for discussion at ALA Annual (Anaheim) at the end of June and IFLA (Quebec City) in August.

TM 2.1 Revised set of elements available as "proposed" in the NSDL Registry (with RDA Namespace, definitions and URIs), with registry outputs in RDF (vocabulary and single element level) and XML schema.

TM 2.2 Revised report explaining the choices made and implemented so far, with still open issues defined

TM 2.3 Preliminary set of value vocabularies available as proposed in the NSDL Registry (with RDA Namespace, definitions and URIs), with registry outputs in RDF (vocabulary and single element level) and XML schema. [We expect these to lack definitions and scope notes, with some exceptions]

TM 2.4 Test plan for service interactions between the Registry and the RDA Web Product for registered element and value vocabularies

TBD, fall

TM 3.1 "Published" (though perhaps not yet complete) set of elements approved for use in the NSDL Registry and for applications using the Registry services.

TM 3.2 Revised report of open issues still to be decided before RDA formal "publication"

TM 3.3 Revised set of of value vocabularies, with plan for adding remaining definitions and scope notes

TM 3.4 Completed testing of service interactions between the Registry and the RDA Web Product for registered element and value vocabularies

Some Resources

3. Develop a DC Application Profile for RDA based on FRBR and FRAD.

Tasks

Task 3.1 Analyse the RDA Element Vocabulary and identify those elements to be used in the application profile.

Task 3.2 Identify the RDA rules relevant to the elements in this context and select those appropriate for this application profile.

Task 3.3 Produce a report explaining the choices made and listing open issues.

Task 3.4 Produce the RDA DC Application Profile

Deliverables

Del 3.1 RDA DC Application Profile

Del 3.2 Report explaining the choices made and listing open issues

Use Cases

Workplan for Namespace for FRBR entities/elements in RDF project

Define appropriate namespaces for FRBR (entity-relationship) in RDF and other appropriate syntaxes.

This project reports to the FRBR Review Group. See Namespace for FRBR entities/elements in RDF for background information, resources, etc. Contact Gordon Dunsire for further information.

Tasks

Task 1 Analyse the FRBR model entities and relationships to identify those elements to be included in one or more namespaces.

Task 2 Extract the controlled vocabularies from FRBR for SKOS-ification.

Task 3 Produce a report explaining the choices made and listing open issues.

Task 4 Produce RDF representations of the chosen vocabularies using SKOS.

Deliverables

Del 1 A set of controlled vocabularies represented in RDF/SKOS.

Del 2 Report explaining the choices made and listing open issues.

General infrastructure

-- http://www.jiscmail.ac.uk/lists/dc-rda.html (a re-purposed mail list)

-- http://dublincore.org/dcmirdataskgroup/

-- Seeking funding for our tasks

Resources and Comments About Our Work

-- Karen Coyle's talk at Code4lib 2008 on the RDA Vocabularies Project: [WWW]RDA in RDF, Can Resource Description Become Rigorous Data?

-- [WWW]Webcast of Diane Hillmann's testimony to the Library of Congress Working Group on the Future of Bibliographic Control

-- [WWW]Podcast with Diane Hillmann done for "Talking with Talis" which discusses the London meeeting and it's implications.

-- Some exclamation from the FRBR Blog: [WWW]RDA + DC + FRBR + FRAD + RDF = OMG!!!

-- Karen Coyle's [WWW]blog report of the RDA Update Forum at ALA Annual in Washington DC.

-- Karen Schneider's [WWW]explanation of our efforts aimed at the generalist librarian--based on interviews with Diane and Karen Coyle.

-- Christine Schwartz's [WWW]blog comments about our efforts.

-- Brad Allen's [WWW]blog post expressing concern about our use of empty nodes.