Combined presentation by Diane Hillmann and Gordon Dunsire at the DCMI/RDA Task Group meeting at DC-2010, Friday, October 22, 2010, Pittsburgh, PA.

1. History, Rationale, and Remaining Work The RDA Vocabularies

2. A brief history A structural tour, including: Rationale and decision making Use of domains and ranges Potential for extension Moving towards completion What we’ve learned Setting the Stage 10/22/10 2 DC-2010

3. A Brief History It all started in London, the last day of April 2007 10/22/10 3 DC-2010

4. The participants agreed that DCMI and the Joint Steering Committee for the Development of RDA should work together to: Develop an RDA Element Vocabulary Expose RDA Value Vocabularies Develop an RDA Application Profile, based on FRBR and FRAD The first two are largely complete; the third is started 4 What Was Accomplished 10/22/10 DC-2010

5. Property and value vocabularies registered on the Open Metadata Registry (formerly the NSDL Registry): http://metadataregistry.org/rdabrowse.htm Used RDF Schema (RDFS), Simple Knowledge Organisation System (SKOS) and Web Ontology Language (OWL) Registry provides human and machine usable interfaces All vocabularies have change history and versioning capabilities Structure: Rationale & Decisions 10/22/10 5 DC-2010

7. Wanted to create a “bridge” between XML and RDF to support innovation in the library community as a whole, not just those at the cutting edge or the trailing edge

8. We registered the FRBR entities as classes in a ‘FRBR in RDA’ vocabulary, to enable specific relationships between RDA properties and FRBR

9. IFLA has followed suit using the Open Metadata Registry to add the ‘official’ FRBR entities, FRAD, and ISBD (more from Gordon about that)

10. This provides exciting opportunities to relate all the vocabularies together10/22/10 6 DC-2010 The General Strategy

11. Started with the Entity Relationship Diagrams produced by ALA Publishing The latest iterations are available on the RDA Toolkit Site (http://www.rdatoolkit.org/background) ERDs are organized in three groups: core, enhanced, special These were developed and iterated with no change management strategy, so each new iteration had to be checked carefully to spot changes ERDs built with a very XML view of the world Our Methodology 10/22/10 7 DC-2010

12. We think of the ‘generalized’ RDA properties as the real RDA vocabulary The ‘bounded’ properties should be seen as the first pass at an Application Profile Extensions can be built more usefully from the generalized properties Mapping will be cleaner using the generalized properties (since most properties mapped to or mapped from will not be based on FRBR) Generalized properties much more acceptable to non-library implementers (not often using FRBR) The Basic ‘WHY’? 10/22/10 8 DC-2010

13. FRBR in RDA Vocabulary declared as classes RDA Properties declared as a ‘generalized’ vocabulary, with no explicit relationship to FRBR entities Subproperties for the generalized elements may be explicitly related to FRBR entities (using ‘domain’) Label/Name includes (Work) or other class to provide unique name (unless the entity name already appears in the name of the property) The Structure, Simplified 10/22/10 9 DC-2010

14. Property (Generalized, no FRBR relationship) Semantic Web Subproperty (with relationship to one FRBR entity) FRBR Entity The Simple Case: One Property-- One FRBR Entity Library Applications 10/22/10 10 DC-2010

15. Book format Semantic Web Book format (Manifestation) Manifestation The Simple Case: One Property-- One FRBR Entity Library Applications 10/22/10 11 DC-2010

16. 10/22/10 DC-2010 12 http://RDVocab.info/Elements/bookFormatManifestation

18. Some properties related to more than one FRBR entity

19. Relationships in Appendix J actually include the name of the FRBR entity in the name and have separate definitions (we re-used this strategy for the FRBR-bounded properties)

20. Other properties and sub-properties appear multiple times in the text and ERDs, with the same definitions and no indication that they might be repeated elsewhere (we consolidated these)10/22/10 13 DC-2010 More Complex Relationships

21. Property (Generalized, no FRBR relationship) Semantic Web Subproperty (with relationship to one FRBR entity) FRBR Entity Subproperty (with relationship to one FRBR entity) FRBR Entity The Not-So-Simple Case: One Property—more than One FRBR Entity Library Applications 10/22/10 14 DC-2010

22. Extent Semantic Web Extent (Manifestation) FRBR Manifestation Extent (Item) FRBR Item The Not-So-Simple Case: One Property—more than One FRBR Entity Library Applications 10/22/10 15 DC-2010

23. 10/22/10 DC-2010 16

25. This work provided a template for the registration of the role terms in RDA (in Appendix I) and, by extension, the other RDA relationships

26. Role and relationship properties are registered at the same level as elements, rather than as attributes (as MARC does with relators, and RDA does in its XML)10/22/10 17 DC-2010 Roles: Attributes or Properties?

27. Mapping, Etc. “Super” Property Semantic Web Subproperty (Generalized, no FRBR relationship) Subproperty (with relationship to one FRBR entity) FRBR Entity The Roles Case: Properties, Subproperties and FRBR Entities Library Applications 10/22/10 18 DC-2010

28. Mapping, Etc. RDA:Creator Semantic Web RDArole:Composer RDArole:Composer (Work) Work The Roles Case: Properties, Subproperties and FRBR Entities Library Applications 10/22/10 19 DC-2010

30. Assumed aggregation of Place, Name and Date are obvious leftovers from catalog cards, and are not necessary to enable indexing or display of those elements together if libraries want to do that

31. We viewed those aggregations as ‘Syntax Encoding Schemes’ and built in ways to accommodate them within the bounded properties

32. Those using the generalized properties (outside libraries, usually) need not be constrained by these traditional aggregations of properties10/22/10 20 DC-2010 Aggregated Statements

33. Pre-coordinated Statements: Structure Aggregated Statement (no domain or range) Aggregated Statement Subproperty Domain: FRBR Entity Range: RDA Syntax Encoding Scheme (Subclass of RDF Datatype) Range: [Specific] Encoding Scheme (Subclass) General Property (no domain or range) Subproperty Option 1 10/22/10 21 DC-2010

34. Pre-coordinated Statements: Example Publication Statement (no domain or range) Publication Statement (Manifestation) Domain: Manifestation Range: RDA Syntax Encoding Scheme (Subclass of RDF Datatype) Range: Publication Statement Encoding Scheme (Subclass) Place of publication (no domain or range) Place of publication (Manifestation) Option 1 10/22/10 22 DC-2010

35. Release from the tyranny of records Potential for use with a variety of encodings Opportunity to re-think how we build and share data Potential for sharing data beyond the library silo A challenge to our old notions of what library data can do and should be doing What Does This Structure Buy Us? 10/22/10 23 DC-2010

36. 10/22/10 DC-2010 24 Statements on the Floor? ID=23456 hasStatementOfEdition “1st trade edition” ID=23456 hasPublicationDate “1987” ID=23456 hasPublisher “Delacorte Press” ID=23456 hasOriginalLanguage “English” ID=23456 hasLanguageOfExpression “English” ID=23456 hasAuthor “Kurt Vonnegut” ID=23456 isFormOfWork “Novel” ID=23456 hasPlaceOfPublication “New York” ID=23456 hasPreferredTitle “Bluebeard, a novel”

37. 10/22/10 DC-2010 25 Is This Really Chaos? ID=23456 hasStatementOfEdition “1st trade edition” ID=23456 hasAuthor “Kurt Vonnegut” ID=23456 hasPublicationDate “1987” ID=23456 isFormOfWork “Novel” ID=23456 hasPublisher “Delacorte Press” ID=23456 hasPlaceOfPublication “New York” ID=23456 hasLanguageOfExpression “English” ID=23456 hasOriginalLanguage “English” ID=23456 hasPreferredTitle “Bluebeard, a novel”

38. 10/22/10 DC-2010 26 ID=23456 hasAuthor “Kurt Vonnegut” Or Just an Aggregation In the Making? ID=23456 hasStatementOfEdition “1st trade edition” ID=23456 hasPublicationDate “1987” ID=23456 isFormOfWork “Novel” ID=23456 hasPublisher “Delacorte Press” ID=23456 hasPlaceOfPublication “New York” ID=23456 hasLanguageOfExpression “English” ID=23456 hasOriginalLanguage “English” ID=23456 hasPreferredTitle “Bluebeard, a novel”

39. 10/22/10 DC-2010 27 ID=23456 hasAuthor “Kurt Vonnegut” ID=23456 hasPreferredTitle “Bluebeard, a novel” ID=23456 hasStatementOfEdition “1st trade edition” ID=23456 hasPublicationDate “1987” ID=23456 isFormOfWork “Novel” ID=23456 hasPublisher “Delacorte Press” ID=23456 hasPlaceOfPublication “New York” ID=23456 hasLanguageOfExpression “English” ID=23456 hasOriginalLanguage “English”

40. 10/22/10 DC-2010 28 ID=23456 hasAuthor “Kurt Vonnegut” ID=23456 hasPreferredTitle “Bluebeard, a novel” ID=23456 hasOriginalLanguage “English” ID=23456 hasStatementOfEdition “1st trade edition” ID=23456 hasPublicationDate “1987” ID=23456 isFormOfWork “Novel” ID=23456 hasPublisher “Delacorte Press” ID=23456 hasPlaceOfPublication “New York” ID=23456 hasLanguageOfExpression “English”

41. 10/22/10 DC-2010 29 ID=23456 hasAuthor “Kurt Vonnegut” ID=23456 hasPreferredTitle “Bluebeard, a novel” ID=23456 hasOriginalLanguage “English” ID=23456 isFormOfWork “Novel” ID=23456 hasPublicationDate “1987” ID=23456 hasPublisher “Delacorte Press” ID=23456 hasStatementOfEdition “1st trade edition” ID=23456 hasPlaceOfPublication “New York” ID=23456 hasLanguageOfExpression “English”

42. 10/22/10 DC-2010 30 ID=23456 hasAuthor “Kurt Vonnegut” ID=23456 hasPreferredTitle “Bluebeard, a novel” Work ID=23456 hasOriginalLanguage “English” ID=23456 isFormOfWork “Novel” ID=23456 hasPublicationDate “1987” ID=23456 hasPublisher “Delacorte Press” ID=23456 hasStatementOfEdition “1st trade edition” ID=23456 hasPlaceOfPublication “New York” ID=23456 hasLanguageOfExpression “English”

43. 10/22/10 DC-2010 31 ID=23456 hasLanguageOfExpression “English” ID=23456 hasPublicationDate “1987” ID=23456 hasPublisher “Delacorte Press” ID=23456 hasStatementOfEdition “1st trade edition” ID=23456 hasPlaceOfPublication “New York”

44. 10/22/10 DC-2010 32 ID=23456 hasLanguageOfExpression “English” ID=23456 hasStatementOfEdition “1st trade edition” ID=23456 hasPublicationDate “1987” ID=23456 hasPublisher “Delacorte Press” ID=23456 hasPlaceOfPublication “New York”

45. 10/22/10 DC-2010 33 ID=23456 hasLanguageOfExpression “English” Expression ID=23456 hasStatementOfEdition “1st trade edition” ID=23456 hasPublicationDate “1987” ID=23456 hasPublisher “Delacorte Press” ID=23456 hasPlaceOfPublication “New York”

46. 10/22/10 DC-2010 34 ID=23456 hasPlaceOfPublication “New York” ID=23456 hasPublicationDate “1987” ID=23456 hasPublisher “Delacorte Press”

47. 10/22/10 DC-2010 35 ID=23456 hasPlaceOfPublication “New York” ID=23456 hasPublisher “Delacorte Press” ID=23456 hasPublicationDate “1987”

48. 10/22/10 DC-2010 36 ID=23456 hasPlaceOfPublication “New York” ID=23456 hasPublisher “Delacorte Press” ID=23456 hasPublicationDate “1987”

49. 10/22/10 DC-2010 37 ID=23456 hasPlaceOfPublication “New York” Manifestation ID=23456 hasPublisher “Delacorte Press” ID=23456 hasPublicationDate “1987”

50. The inclusion of generalized properties provides a path for extension of RDA into specialized library communities and non-library communities They may have a different notion of how FRBR ‘aggregates’, for example, a colorized version of a film may be viewed as a separate work They may not wish to use FRBR at all They may have additional properties to include, that have a relationship to the RDA properties Extension 10/22/10 38 DC-2010

51. RDA:adaptedAs hasSubproperty RDA:adaptedAsARadioScript 10/22/10 39 DC-2010

52. RDA:adaptedAs hasSubproperty RDA:adaptedAsARadioScript hasSubproperty KidLit:adaptedAsAPictureBook 10/22/10 40 DC-2010

53. RDA:adaptedAs hasSubproperty RDA:adaptedAsARadioScript hasSubproperty hasSubproperty KidLit:adaptedAsAPictureBook KidLit:adaptedAsAChapterBook 10/22/10 41 DC-2010

54. Completing the hierarchies, both generalized and FRBR-bounded Elements and Relationships need to have bounded hierarchies built (generalized hierarchies complete) Roles need generalized properties created JSC review incomplete, for both properties and vocabularies Status designations need to be updated from ‘New—proposed’ to ‘Published’ Completing the Vocabularies 10/22/10 42 DC-2010

55. Extent Subproperty Subproperty Extent (I) Extent (M) Subproperty Subproperty Extent of Text Extent of Still Image Subproperty Extent of Still Image (M) Extent of Text (M) Extent of Still Image (I) Extent of Text (I) Current Registered Relationships 10/26/10 43 ASIS&T-2010

56. Extent Subproperty Subproperty Extent (I) Extent (M) Subproperty Subproperty Extent of Text Extent of Still Image Subproperty Subproperty Extent of Text (M) Extent of Still Image (M) Subproperty Extent of Text (I) Extent of Still Image (I) Added Registered Relationships 10/26/10 44 ASIS&T-2010

57. How do these relate to the RDA guidance text? Who will maintain these? How will they be kept in sync with the text? Will the governance model for these be the same as the text? Who decides? How can we use these vocabularies effectively? What else do we need to identify? How should we continue this work? Remaining Issues 10/22/10 45 DC-2010

58. We wrote about the decisions we made for RDA in DLib: http://dlib.org/dlib/january10/hillmann/01hillmann.html Need to continue to disclose what we’ve learned and work on building best practices documentation in this environment What We’ve Learned 10/22/10 46 DC-2010

59. Important related work Gordon Dunsire

60. Summary FR family (FRBR, FRAD, and FRSAD) RDF/XML representation of the consolidated edition of ISBD. General issues arising feedback into standards development labels, definitions and scope notes constrained and unconstrained representations use of opaque URIs IFLA Namespaces Technical Group. Relating FR, ISBD and RDA, SKOS, FOAF, etc.

61. FR family “Functional Requirements” family or “FRBR family of models”: FRBR, 1998: Bibliographic Records [data] FRAD, 2009: Authority Data FRSAD, [2010]: Subject Authority Data Preliminary work: theFRBR Namespace Project used the testing area of the National Science Digital Library Metadata Registry (NSDL) Now the Open Metadata Registry WLIC 2010, Gothenburg: Sun 15 August 2010

62. FR namespaces FRBR Review Group decided to declare separate namespaces for FR components Length of time since FRBR publication Dependence of FRAD on FRBR, and FRSAD on FRAD Might lead to change of earlier semantics Prevent delay in RDF representation while ... Consolidated model in development Not until after IFLA 2011 (Puerto Rico)

63. FR in RDF Representation of FRBRer model element set is mainly complete Classes and properties have “approved” status FRAD and FRSAD close behind Representation in Resource Description Framework (RDF) is informing work on combining and consolidating the model family Also supplies “learning curve” for Semantic Web environment OWL representation of FRBRer completed To be published real soon now WLIC 2010, Gothenburg: Sun 15 August 2010

64. International Standard Bibliographic Description FRBR is a conceptual model built on the E-R methodology which is intrinsically applicable to representation in RDF, while ISBD is a data standard Design of the RDF representation of ISBD involves: the treatment of aggregated statements in a defined number of elements within the areas; the treatment of mandatory and optional elements and areas; the order of areas and elements within an area; the repeatability of areas and elements; the treatment of punctuation and its double function. WLIC 2010, Gothenburg: Sun 15 August 2010

65. ISBD Basic element set developed (near-final) Analysis fed back into development of final consolidated edition, due IFLA 2011 Represented in Open Metadata Registry Aggregated statements identified Treated in the same way as for RDA DC Application Profile started Describes ISBD record structure (sequence, mandatory status, repeatability of elements) Completion due Spring 2011

66. Stats * 24 ISBD classes are Syntax Encoding Schemes

67. General issues arising (1) Labels, definitions and scope notes Text follows ur-documents as closely as possible Adjustments for consistency “has”+attribute name / “is” + attribute name + “of” property pairs (inverses) No inverse properties in ISBD! Scope note contains examples, “includes ...” Constrained properties FRBR is investigating Domain/Range-free equivalents Less of an issue with ISBD

68. General issues arising (2) Use of opaque URIs http://iflastandards.info/ns/isbd/elements/P1004 “has title proper” Does not favour a particular language in a multi-lingual environment Translations of labels, etc. – same URI Forces de-referencing by the non-expert E.g. Multiple “has title ...” properties

69. IFLA Namespaces Task Group reported to Professional Committee in May 2010 Recommendations and options for namespace infrastructure Accepted August 2010 (IFLA WLIC) Technical Group to be set up Will report to new IFLA Bibliographic Standards Program (Core Activity) Universal bibliographic control for 21st century FRBR and ISBD Review Groups agree to work more closely with JSC, and liaise with Semantic Web communities (Aug 2010)

70. RDA properties Extent Extent of text Extent of still image Extent (M/) Extent (I/) Extent of text (I/) Extent of still image (I/) Extent of text (M/) Extent of still image (M/) Subproperty Label (Domain/Range)

71. RDA/IFLA properties (minimal linkage) Extent has extent has extent (R/) has extent of the carrier Extent of text Extent (M/) has extent of the carrier (M/) Note: Manifestation sub-class-of Resource Extent of text (M/) SameAs RDA FRBR ISBD Subproperty Label (Domain/Range) FRBR lite ISBD lite

72. RDA/IFLA properties (maximum linkage) Extent has extent has extent (R/) has extent of the carrier Extent of text Extent (M/) has extent of the carrier (M/) Extent of text (M/) SameAs RDA FRBR ISBD Subproperty Label (Domain/Range) FRBR lite ISBD lite

73. RDA/IFLA/other properties (minimal linkage) format Extent (/S) Extent has extent has extent of the carrier has extent (R/) Extent of text Extent (M/) has extent of the carrier (M/) numPages (D/l) numVolumes (C/l) Extent of text (M/) Note: Document sub-class-of Resource SameAs Label (Domain/Range) RDA FRBR ISBD DCT BIBO Subproperty FRBR lite ISBD lite DC Classes: Manifestation, Resource, Collection, Document, SizeOrDuration, literal

74. DCMI/RDA Task Group Wiki: http://dublincore.org/dcmirdataskgroup/ RDA Vocabularies: http://metadataregistry.org/rdabrowse.htm Diane: metadata.maven@gmail.com Gordon: gordon@gordondunsire.com Please join us and participate! Links and Contact Info 10/22/10 62 DC-2010