Presentation on theme: "Presented to the ALCTS FRBR Interest Group, ALA Annual, 24 June 2011"— Presentation transcript:
1Presented to the ALCTS FRBR Interest Group, ALA Annual, 24 June 2011 Functional requirements for bibliographic linked data: the FR family and the Semantic WebGordon DunsirePresented to the ALCTS FRBR Interest Group, ALA Annual, 24 June 2011
2Overview Background Resource Description Framework Representing Functional Requirements for the Semantic WebSome issuesLegacy catalogue records
3FRADDoes not coversubjectsFRBRDoes not cover“authorities”FRConsolidatedmodelFRSADSemantic Web versions recapitulate this sequence:* Earlier models in use before later models published* Later models re-use elements from earlier models* Reflects semantic development over time* Provides learning curve for FRBR Review Group1998200920102012?
4BackgroundRDA: resource description and access is based on FRBR and FRADBibliographic metadata content guidelinesDCMI RDA Task Group asked to develop an RDF representation of RDAFollowing the “London” meeting in April 2007Stimulated creation of “FRBR namespaces project”To develop RDF representation of FRBR
5RDF Resource Description Framework Basis of the Semantic WebMetadata expressed as “atomic” statementsA simple, single, irreducible statementThe creator of this work is R. ShankarConstructed in 3 parts“Triple”
6RDF triples The creator of this work is R. Shankar Subject of the statement = Subject: This workNature of the statement = Predicate: has creatorValue of the statement = Object: R. ShankarThis work – has creator – R. Shankarsubject – predicate – objectRDF requires the subject and predicate of a triple to have machine-readable identifiersUniform Resource Identifier (URI)Object of triple can be a URI, or a literal string like a title
7RDF properties and classes A predicate is called a propertyProperties link two thingsA specific work with a specific creatorThis work <-> R. ShankarA generic type of thing is called a classWorks, Persons, Places, etc.Properties can specify which class the subject and object of a triple should belong toSubject “domain”; object “range”
8Methodology (1)Open Metadata Registry used for basic representation in RDFSame approach as RDAProvides URI assignment; labels, definition, scope note, property range and domainFR family are entity-relationship modelsEntity => RDF ClassE.g. FRBR WorkEntity attribute => RDF propertyE.g. FRBR has-intended-audienceEntity-entity relationship => RDF propertyE.g. FRBR is-realized-through (Work-Expression)
9ClassesPropertiesFRBR Groups are not (super-)classes [FRBR Review Group]Group 1 entities are not classes [some ontologists]
10Attribute => Property 3.2.5 PersonThe fifth entity defined in the model is person: an individual.The entity defined as person encompasses individuals that are deceased as well as those that are living.Entity => ClassLabelDefinitionScope noteCapture modeCapture mode is the means used to record notation, sound, or images in the production of a manifestation (e.g., analogue, acoustic, electric, digital, optical etc.).Attribute => PropertyLabelDefinitionScope note
12Spanish translation of label - URI remains the same
13Methodology (2)Terminology of labels, definitions and scope notes based as closely as possible on source documentationE.g. Property label = “has” + attribute nameClasses and properties declared for prior model(s) re-used in current modelE.g. FRAD re-uses URIs from FRBR namespaceE.g. FRBR Expression; FRBR has-keyNo re-use of RDF resources from external community namespaces such as Dublin Core TermsEquivalences likely to be established later
14Methodology (3) FR attribute properties have domain but no range Required by the model for extensibilityE.g. FRBR has-key (domain = Work)Relationship properties have domain and rangeE.g. FRBR is-realized-through (domain = Work; range = Expression)
15General, non-technical issues Consistency within documentationWritten for human consumption; evidence of variable phrasing to make it more readableE.g. “prior”, “preceding”, “first”Consistency of labels of RDF resourcesE.g. “has a reproduction” (regular) vs “has reproduction” (irregular)Documentation refers to sub-types of entityE.g. “musical work”, “serial”First pass: sub-type => sub-classBut wrong due to semantic overlap
16Opaque URIs http://iflastandards.info/ns/fr/frbr/frbrer/P1001 frbrer:P1001NotIFLA operates in a multilingual environmentAnglophone bias avoidedLabels, etc. in English but no problem in accommodating translationsAllows subsequent changes to alternative and preferred labels without causing confusionURI must not change!
17Linking the FR modelsRelationships between separate FR model classes and properties are declared with RDF equivalence and hierarchical propertiesE.g. owl:sameAs, rdfs:subClassOfE.g. FRAD class Corporate Body seems to be a sub-class of FRBR Corporate BodyWill inform the consolidated modelWhich may also require additional classes and properties
18RDA issuesDCMI RDA Task Group has declared parallel FRBR classes within RDA namespaceCould not wait for FRBR RDF resources to be approvedJSC to decide whether to substitute FRBR namespace resources, or declare equivalenceConflict with FRBR in RDA implementation scenarios?RDA Manifestation “embodies” Work and Expression; FRBR allows only Expression
19Legacy catalogue records Domain and range of FR (and RDA) properties inhibit use for creating triples from non-FRBRized catalogue recordsNeed separate URIs for each specific Work, Expression, Manifestation, and ItemSolution: equivalent properties with no domain or rangeNeed just a URI for the specific resource describedRDA has such unbounded properties
20Thank you firstname.lastname@example.org Sponsors FRBR Review GroupOpen Metadata RegistryLibrary Linked Data Incubator GroupSponsorsALACataloging & Classification QuarterlyMARCIVE, Inc.