John, The JSC has done a wonderful job of making many documents re. RDA available, e.g., Working Documents: http://www.rda-jsc.org/working1.html
And Historic Documents: http://www.rda-jsc.org/docs.html Including the "Issues Deferred until after the First Release" referred to by Barbara Tillett: http://www.rda-jsc.org/docs/5sec6rev.pdf Your own excellent document re. the ALA decisions re. the "Issues Deferred until after the First Release" is available here: http://www.libraries.psu.edu/tas/jca/ccda/docs/jsc1004.pdf Many other documents referring to RDA issues are available at the CC:DA site: http://www.libraries.psu.edu/tas/jca/ccda/ The CILIP-BL Committee on RDA also puts many documents on it's website: http://www.slainte.org.uk/AACR/BLDocs.htm http://www.slainte.org.uk/AACR/CILIPDocs.htm LC has begun posting policy decision files on RDA: http://www.loc.gov/catdir/cpso/RDAtest/rdatest.html I could not find documentation from the other official RDA representative bodies at their sites: Canadian Committee on Cataloguing: http://www.collectionscanada.gc.ca/cataloguing-standards/040006-3000-e.html Australian Committee on Cataloguing: http://www.nla.gov.au/lis/stndrds/grps/acoc/index.html There are so many documents that we should be consulting when we have a question about a particular RDA instruction, or missing AACR concept, or where's the rule for this MARC field, or where's the MARC field for this rule. I know that much will be revealed when we finally get our hands on the RDA Toolkit with all the pieces in place. But Q&A and revision requests will continue to come along and it would be great to be able to easily find out whether a concern has already been decided (positive *or negative*) or is still in the works. It does seem that the RDA Toolkit would be an ideal place to access some sort of project tracking/bug tracking/version tracking tool, such as: Trac (http://trac.edgewall.org/); Subversion (http://subversion.apache.org/); Bugzilla (http://www.bugzilla.org/), etc. But I guess the bigger question might be, who would be responsible for maintaining such a thing?? CC:DA? ALCTS? LC? one of the other NatLibs or their committees? JSC itself? The cataloging community as a whole, if we someone could jump start it? Deborah ------ Deborah Fritz MARC Database Consultant The MARC of Quality www.marcofquality.com Voice/Fax: (321) 676-1904 > -----Original Message----- > From: Resource Description and Access / Resource Description > and Access [mailto:[email protected]] On Behalf Of > John Attig > Sent: Tuesday, May 04, 2010 8:07 AM > To: [email protected] > Subject: Re: [RDA-L] RDA websites > > At 05:07 PM 5/3/2010, Deborah Fritz wrote: > >I asked one of the ALA Publishing reps, at one of the RDA > meetings at > >ALA Midwinter, about tracking official changes to RDA, and was told > >that this was on the list of enhancements, and would be > addressed once > >the initial product was released. > > > >Of equal concern to me is somehow keeping track of and making public > >all the change *requests* before they are officially decided and > >released. It seems like it would be very useful for us to > know whether > >someone has already asked about something that we think > needs changing, > >and whether it is either in the works, or decided for or > against (with > >reasons why in either case) > > Proposals to change the content of RDA will continue to be > considered and decided upon by the Joint Steering Committee > (or some such body). For the past several years, the JSC has > been posting all proposals, responses, and decisions on its > website at www.rda-jsc.org > -- and will continue to do so as it begins to consider > proposals to revise RDA. > > >There must be some kind of software out there that would help in > >tracking these open issues, but I guess the harder question > is who would do this? > > At this time, it is unclear whether the RDA Toolkit itself > will be able to offer a means of tracking change requests and > proposals. That was certainly the intention of the Committee > of Principals and the Co-Publishers; once the RDA Toolkit has > been released, we expect that this will again become a > development issue. > > On the other hand, as noted above, the JSC will continue to > post proposals, whether this is done on the JSC website or as > part of the RDA Toolkit itself. We are committed to making > the maintenance of RDA a public process. > > John Attig > ALA Rep to the JSC > > > __________ Information from ESET NOD32 Antivirus, version of > virus signature database 5083 (20100503) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > __________ Information from ESET NOD32 Antivirus, version of virus signature database 5083 (20100503) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
