11.07.2015 Views

RDA and FRBR - Joint Steering Committee for Development of RDA

RDA and FRBR - Joint Steering Committee for Development of RDA

RDA and FRBR - Joint Steering Committee for Development of RDA

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Slide 33Content vs. display• <strong>RDA</strong> will be a content st<strong>and</strong>ard --not adisplay or encoding st<strong>and</strong>ard• Independent <strong>of</strong> the communication <strong>for</strong>mat(e.g., MARC 21, MODS)• Independent <strong>of</strong> display <strong>for</strong>mat (e.g., OPAClabels, ISBD)• International St<strong>and</strong>ard BibliographicDescription order <strong>of</strong> data elements <strong>and</strong>prescribed punctuation in AACR2 are notpart <strong>of</strong> the <strong>RDA</strong> instructions• ISBD Display in<strong>for</strong>mation in Appendix to <strong>RDA</strong>• <strong>RDA</strong>-created records can be displayed in anISBD display if desired33The JSC decision to make <strong>RDA</strong> a content st<strong>and</strong>ard rather than a display st<strong>and</strong>ard was reallya key to moving <strong>RDA</strong> <strong>for</strong>ward. This allowed us to move beyond the ISBDs – by not requiringISBD punctuation (which is irrelevant to metadata communities, <strong>and</strong> not used in many OPACsanyway).However, we need to ensure that <strong>RDA</strong> records can be displayed in an ISBD display if a librarystill wants to do that – in this way we can honor our agreement to keep <strong>RDA</strong> compatible withthe ISBDs. So we’re trying to build in compatibility yet flexibility at the same time. There willbe an appendix on ISBD display <strong>of</strong> <strong>RDA</strong> records to indicate the order <strong>of</strong> elements <strong>and</strong>punctuation to be used.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!