Joint Steering Committee for Development of RDA. Gordon Dunsire, Chair, JSC Technical Working Group

Similar documents
Joint Steering Committee for Development of RDA. This paper discusses the data about data or meta- metadata elements (meta- elements) in RDA.

Introduction and background

Abstract. Background. 6JSC/ALA/Discussion/5 31 July 2015 page 1 of 205

Update on 3R Project (RDA Toolkit Restructure and Redesign Project)

RDA work plan: current and future activities

To: Joint Steering Committee for Development of RDA. Subject: RDF representation of RDA relationship designators: a follow- up discussion paper

Joint Steering Committee for Development of RDA. Mapping ISBD and RDA element sets; briefing/ discussion paper

RDF representation of RDA relationship designators. Appendix 5: Issues relating to minor changes in the RDA Toolkit

3R Project. RDA Toolkit Restructure and Redesign Project. James Hennelly, Managing Editor of RDA Toolkit Judy Kuhagen, 3R Project Consultant

Latest news! IFLA LRM s impact on cataloguing

6JSC/Chair/8 25 July 2013 Page 1 of 34. From: Barbara Tillett, JSC Chair To: JSC Subject: Proposals for Subject Relationships

RDA and Linked Data. by Gordon Dunsire National Seminar, National Library of Finland, Helsinki, Finland, 25 March 2014

Interoperability and Semantics in RDF representations of FRBR, FRAD and FRSAD

IFLA Library Reference Model. WHAT AND WHY? Chris Oliver University of Ottawa Library

RDA Steering Committee and RSC Working Group Chairs

[Draft] RDA Resource Description and Access

6JSC/ALA/Discussion/4 [Transcription issues associated with the Production Statement (RDA 2.7]

Alexander Haffner. RDA and the Semantic Web

National Library 2

Linked data for manuscripts in the Semantic Web

NAVIGATING THE RDA TOOLKIT

RDA Update: The 3R Project. Kate James Cataloging Policy Specialist, Library of Congress LC Representative to NARDAC RDA Examples Editor

RDA Resource Description and Access

The metadata content standard: RDA

Background. Recommendations. SAC13-ANN/11/Rev. SAC/RDA Subcommittee/2013/1 March 8, 2013; rev. July 11, 2013 page 1 of 7

Summary and Recommendations

Looking to the Future

FRBRoo, the IFLA Library Reference Model, and now LRMoo: a circle of development

Joint Steering Committee for Development of RDA. Related document: 5JSC/RDA/Scope/Rev/4

Building RDA using the FRBR Library Reference Model

RDA? GAME ON!! A B C L A / B C C A T S P R E C O N F E R E N C E A P R I L 2 2, : : 0 0 P M

Application profiles and cataloging a manifestation

Joint Steering Committee for Development of RDA

RDA 3R Project: Status Report. Kate James RDA Examples Editor

5JSC/ACOC/1/Rev 7 August Joint Steering Committee for the Revision of AACR

Resource Description and Access Setting a new standard. Deirdre Kiorgaard

RDA Steering Committee Kathy Glennan, ALA Representative Discussion paper: RDA and WGA treatment of aggregates

RDA: a new cataloging standard for a digital future

Contribution of OCLC, LC and IFLA

Reconsidering DCRM in the light of RDA: A Discussion Paper

Using the RDA Toolkit

Metadata. Week 4 LBSC 671 Creating Information Infrastructures

This RSC document is a minor revision of its counterpart JSC document (6JSC/Policy/6); only minimal updating of names has occurred.

Activities Report, September 2015-August 2016 (Draft)

Alignment of the ISBD: International Standard Bibliographic Description element set with RDA: Resource Description & Access element set

Table of contents for The organization of information / Arlene G. Taylor and Daniel N. Joudrey.

AACR3: Resource Description and Access

Appellations, Authorities, and Access Plus. Gordon Dunsire Presented to CC:DA, Chicago, USA, 24 June 2017

UPDATE ON THE RDA 3R PROJECT

datos.bne.es: a Library Linked Data Dataset

SUBJECT: Revision to RDA (Number, date, location, of a conference, etc.)

Recording Methods, Transcription, and Manifestation Statements

data elements (Delsey, 2003) and by providing empirical data on the actual use of the elements in the entire OCLC WorldCat database.

Using the RDA Toolkit

Statement of International Cataloguing Principles (ICP)

Cataloguing is riding the waves of change Renate Beilharz Teacher Library and Information Studies Box Hill Institute

School of Library & Information Science, Kent State University. NOR-ASIST, April 4, 2011

Joined up data and dissolving catalogues

From: Renate Behrens, European Regional Representative. Subject: Proposal on Sources of Information (RDA 2.2.2)

ResolutionDefinition - PILIN Team Wiki - Trac. Resolve. Retrieve. Reveal Association. Facets. Indirection. Association data. Retrieval Key.

Association for Library Collections and Technical Services (A Division of the American Library Association) Cataloging and Classification Section

SEVEN WHAT IS MODELED IN FRBR?

Joint Steering Committee for Development of RDA

INTRODUCTION. RDA provides a set of guidelines and instructions on recording data to support resource discovery.

Recommendations. A. Containers in RDA and JSC/ALA/21 August 8, 2012 page 1 of 9

THE MODELING OF SERIALS IN IFLA LRM AND RDA

Assessing Metadata Utilization: An Analysis of MARC Content Designation Use

BIBFRAME Update Why, What, When. Sally McCallum Library of Congress NCTPG 10 February 2015

Joint Steering Committee for Development of RDA. Related document: 5JSC/RDA/Scope/Rev

The Semantic Web and expert metadata: pull apart then bring together. Gordon Dunsire

The cataloging world marches towards the next in a continuing procession of evolving bibliographic standards RDA: Resource Description and Access.

Features & Functionality

Draft for discussion, by Karen Coyle, Diane Hillmann, Jonathan Rochkind, Paul Weiss

CATALOGUING SECTION ISBD Review Group

RDA Toolkit Redesign Update and Preview ALA Midwinter Conference Denver, Colorado February 9, 2018

Joint Steering Committee for Development of RDA Dave Reser, LC Representative

Oshiba Tadahiko National Diet Library Tokyo, Japan

BIBLIOGRAPHIC REFERENCE DATA STANDARD

NISO STS (Standards Tag Suite) Differences Between ISO STS 1.1 and NISO STS 1.0. Version 1 October 2017

RECORD SYNTAXES FOR DESCRIPTIVE DATA

The Dublin Core Metadata Element Set

I want to start by reporting some of the most recent revisions to RDA, made by the JSC

IFLA Cataloguing Section s ISBD Review Group

Metadata for Digital Collections: A How-to-Do-It Manual. Introduction to Resource Description and Dublin Core

Enrichment, Reconciliation and Publication of Linked Data with the BIBFRAME model. Tiziana Possemato Casalini Libri

Retrospective Implementation of Faceted Vocabularies for Music

Vocabulary-Driven Enterprise Architecture Development Guidelines for DoDAF AV-2: Design and Development of the Integrated Dictionary

Looking to the Future: Information Systems and Metadata

Marcia Lei Zeng Kent State University Kent, Ohio, USA

RDA: Where We Are and

SAS Clinical Data Integration Server 2.1

Enhancing information services using machine to machine terminology services

PRESENTATION OUTLINE RESEARCH AND DEVELOPMENT OF FRBR-BASED SYSTEMS TO SUPPORT USER INFORMATION SEEKING 11/9/2010. Dr. Yin Zhang Dr.

For each use case, the business need, usage scenario and derived requirements are stated. 1.1 USE CASE 1: EXPLORE AND SEARCH FOR SEMANTIC ASSESTS

EDQ Product Data Extensions Essentials

RDA DEVELOPMENTS OF NOTE P RESENTED TO CC:DA B Y KATHY GLENNAN, ALA REPRESENTATIVE TO THE RSC J ANUARY 21, 2017

RDA ESSENTIALS. t h o m a s b r e n n d o r f e r. Chicago 2016

ISO/IEC Information technology Software asset management. Part 2: Software identification tag

This document is a preview generated by EVS

Background and Implementation Issues

Transcription:

Page 1 of 15 To: From: Subject: Joint Steering Committee for Development of RDA Gordon Dunsire, Chair, JSC Technical Working Group High-level subject in RDA Abstract The paper discusses the high-level accommodation in RDA for the FRSAD subject, and makes recommendations for improving the consistency and coherency of RDA elements and designators associated with concept of subject. Introduction The JSC Technical Working Group has developed these recommendations to provide a coherent and comprehensive framework for the future development of the treatment of the Subject concept in RDA. FRSAD model The Functional Requirements for Subject Authority Data (FRSAD) model has a namespace published in the Open Metadata Registry. 1 The primary between a FRBR Work and a Thema is represented as a reciprocal pair of properties (in terse triple language, ttl): frsad:p2001 rdfs:label "has as subject" ; skos:definition "Relates a work to a thema." ; owl:inverseof frsad:p2002. frsad:p2002 rdfs:label "is subject of" ; skos:definition " Relates a thema to a work." ; owl:inverseof frsad:p2001. The "has as subject" is the high-level that should be added to the RDA elements to maintain semantic consistency with designators that refine a high-level subject. The is also consistent with the FRAD model, so it is unlikely to change significantly as a result of consolidation of the FR models. Thema is defined as "Any entity used as a subject of a work". There is no current or anticipated requirement for the FRSAD entity Thema to be added to RDA because it is only required for clarity within the FRSAD model and between FRSAD, FRBR, and FRAD. 2 1 http://metadataregistry.org/schemaprop/list/sort/label/type/asc/schema_id/26.html

Page 2 of 15 Recommendation 1: Add a primary element to the RDA element set with the label "Subject", definition "The subject of a work", and domain Work. The corresponding Registry property will have rdfs:label "has subject", skos:definition "Relates a work to the subject of a work", rdfs:domain rdac:c10001, and no range. RDA designators Descriptive s for WEMI entities are given in RDA Appendix J. The descriptive designators appear to cover all of the kinds of subject between the RDA WEMI entities. The semantics of descriptive s are part of the semantics of subject s. That is, the generic s at RDA J.1.3, J.2.3, J.3.3, and J.4.3 are element sub-types or subproperties of the Subject element, effectively adding each of the WEMI entities as a range to refine the high-level element. However, RDA assigns descriptive s to Expressions as well as Works. This allows an Expression of a Work to describe: Another Work; for example "Dunsire, Gordon. Description of Hamlet. French" describes "Shakespeare, William. Hamlet". An Expression of another Work; for example "Dunsire, Gordon. Description of the French translation of Hamlet. French" describes "Shakespeare, William. Hamlet. French". A Manifestation or Item. There are 2 levels of hierarchy of designators for descriptive s for each WEMI entity. The top level designators, together with the super-properties for the generic s at RDA J.1.3, J.2.3, J.3.3, and J.4.3 are given in Table 1 in the Appendix, with their Registry semantics. 3 The Toolkit semantics were revised in the April 2014 update to remove the anomaly of Item-Item and Manifestation-Manifestation descriptive s when such s apply in the primary direction from Works and their Expressions only. Further similar revisions to the Toolkit semantics are required for the 2 nd level designators for analysis, commentary, critique, evaluation, and review s. Table 1 reveals some missing designators: 1. Definition: "A work that describes an expression."; Domain: Expression; Range: Work 2. Definition: "An expression described by a describing work."; Domain: Work; Range: Expression 3. Definition: "An expression of a work that describes a work."; Domain: Work; Range: Expression. 2 Dunsire, Gordon. Representing the FR Family in the Semantic Web, http://www.gordondunsire.com/pubs/docs/representing_the_fr_family_in_the_semantic_webpre.pdf 3 The Registry has pending updates to conform to this table.

Page 3 of 15 4. Definition: "A work described by an expression of a describing work."; Domain: Expression; Range: Work. 5. Definition: "An expression of a work that describes a manifestation."; Domain: Manifestation; Range: Expression. 6. Definition: "An expression of a work that describes an item."; Domain: Item; Range: Expression. 7. Definition: "A manifestation described by an expression of a describing work."; Domain: Expression ; Range: Manifestation. 8. Definition: "An item described by an expression of a describing work."; Domain: Expression ; Range: Item. 1 and 2, 3 and 4, 5 and 7, and 6 and 8 are reciprocal pairs. 3, 5, and 6 complete the "Expression of a Work describing " s. These are all examples of cross-entity designators; that is, designators covering s between different WEMI entities. The matrix established by the existing designators and completed with the new designators is given in Table 2 in the Appendix. The five second-level designators (analysis, commentary, critique, evaluation, and review) will have similar matrices, and will require similar additional designators. Discussion The current RDA semantics of descriptive designators is not compatible with the FRSAD model. To make RDA compatible with FRSAD, the "Expression of a Work describing " designators must be removed, so that only Work is the domain of the descriptive designators in the primary direction from Work. This will also considerably simplify RDA and reduce the need to add as many new designators as indicated. The resulting entity matrix is shown in Table 3 in the Appendix, with transformations of existing designators to accommodate the new cross-entity additions. The resulting marked-up list of designators and Registry elements is shown in Table 4 in the Appendix, with a clean version in Table 5 in the Appendix. The changes to the published elements do not require new replacement elements; the semantics are bent, but not broken, by the changes. Table 4 indicates, however, that corresponding changes to the RDA Registry element URIs to maintain consistency will require the deprecation of some elements with re-registration under a different URI, and redirection from deprecated to active URIs. This approach removes the generic same-entity s at RDA J.2.3, J.3.3, and J.4.3, leaving only the J.1.3 "descriptive work " to be a sub-property of the proposed primary subject element. A generic covers designators and their reciprocals; the reciprocal swaps the domain and range, so a generic property must have the same domain and

Page 4 of 15 range, that is be a same-entity. Generic cross-entity s must therefore be unconstrained. The changes shown in Table 4 remove the cross-entity designators from the sub-property chain leading to the proposed primary subject element. They remain in the sub-property chain leading to a published unconstrained designator. The descriptive designators " " in the primary direction (from Work) become sub-properties of the proposed subject element. Recommendation 2: Bring the RDA descriptive s designators into line with FRSAD by allowing only Work to be the domain of primary descriptive designators for WEMI entities (and the range of their reciprocal designators) as indicated in Table 4, and by adding subproperty s to the new subject element. The Working Group recognizes that Recommendation 2 removes accommodation for one of the use cases that the "" was intended to support. The "" is the reciprocal of the " ". The use case is illustrated by the descriptive practice that was specified in AACR2 1.7B15, References to Published Descriptions, using the MARC field 510. Such references to published descriptions or citations are very frequently included in records for rare materials; there is even a published list of Standard Citation Forms for Rare Book Cataloging, the third edition of which is being prepared for publication. These references provide detailed information that supports the identification of the particular resource (WEMI) being described. While many of the bibliographies and catalogues that are referenced exist in only one expression (and therefore the "" with range Work is adequate), many exist in multiple expressions and the reference must often be to a specified Expression of the Work. However, the semantics of the term "" are significantly different in this case. Recommendation 2 ensures the term means the reciprocal of "". The term "described by" can have the same meaning; this is another example of the problems of relying on labels. The nuances between "in" and "by" are those of extent: "in" indicating "part" and "by" indicating "coextensive". Also, the term "description" can refer to unstructured or structured data about a thing. Recommendation 2 is consistent with unstructured data (a Work) which is co-extensive with its Thema, that is, WEMI. The use case is consistent with a structured or unstructured description which is part of a specific Expression of a Work which is not intended to be about the particular subject of the description (the specified WEMI). Less ambiguous terms for a structured description are "metadata", "bibliographic record", "bibliographic reference", "citation", etc. The RDA element Preferred Citation is a Manifestation attribute, and therefore has a literal containing the text of the citation as its range. RDA refers confusingly to such a citation as an unstructured description. The definitions of the designators appendix and appendix to contain the phrase "list of references". These have overlapping semantics.

Page 5 of 15 The need to maintain RDA support for the "citation" use case and the overlap in semantics with at least one RDA element and several designators suggests the development of a set of designators that relate WEMI to the Work or Expression containing the citation, such as "cited in" and "cites" for the reciprocal. These will be cross-entity designators with the issues discussed above. However, this does not preclude the addition of an attribute element for each of WEMI that accommodates the text of the citation to the Work or Expression, in a similar way to Preferred Citation. The generic label of the element might be Reference to Published Citation (or Reference to Published Description if "citation" is too narrow). A proposed definition is "A citation for a published a ". Recommendation 3: Add to RDA the elements: Reference to Published Citation (Work), Definition: "A citation for a published a work.", domain: Work; Reference to Published Citation (Expression), Definition: "A citation for a published an expression.", domain: Expression; Reference to Published Citation (Manifestation), Definition: "A citation for a published a manifestation.", domain: Manifestation; Reference to Published Citation (Item), Definition: "A citation for a published a item.", domain: Item. Recommendation 4: Develop a set of designators that relate WEMI to the Work or Expression containing the citation. Relationship hierarchy The hierarchy of current RDA designators under the proposed high-level element is shown in Table 6. Triple Domain URI Range GWTWAnalysis has subject GWTW W P1???? -GWTWAnalysis has descriptive work with GWTW W P10230 W --GWTWAnalysis is GWTW W P10100 W ---GWTWAnalysis is analysis of GWTW W P10140 W Table 6: Hierarchy of RDA subject and designators. Table 6 uses the example of the work "Gone with the wind" (GWTW) and a work that is an analysis of the work "Gone with the wind (GWTWAnalysis). The refinement level of the hierarchy is indicated by the number of hyphens (-) indenting the sample data triple using the. The order of the hierarchy is determined by the human-readable semantics in definitions and scope notes, and the machine-readable semantics in domains and ranges. In particular, the rule for domains and ranges is: A specified domain/range class is finer than a super-class of the specified domain/range class is finer than no specified domain/range class.

Page 6 of 15 There is no requirement to deprecate existing range statements for coherency or consistency, as shown in Table 6. Following Recommendation 1, new designators should not specify a range class. The domain class should be the RDA Work entity. Recommendation 5: New subject designators should not specify a range, unless this is required for a specified purpose such as consistency with legacy s. New designators following Recommendation 5 will have no specified range, and will therefore fit into the hierarchy at the first level of refinement of the subject element. A new designator cannot fit into the current hierarchy shown in Table 6 at a finer level than the descriptive work because it has a specified range of Work. Any new subject designators at a finer level of granularity will require a separate hierarchy in RDA. Labels If Recommendation 2 is not accepted, the matrix in Table 2 shows that the labels with the pattern "descriptive entity " are not consistently matched to the hierarchy. The current pattern of qualifying similar designators by their domain cannot be applied to the new designators, because the domains are the same, but the ranges are different. An extension of the current pattern would result in double qualifiers; for example: New 1 Label: " (expression) " This is not user-friendly, and is ambiguous; is there a difference with " (expression)"? Recommendation 6: If Recommendation 2 is not accepted, refer the labelling of the designators in Table 1 to the discussion on element labels designated as task 3 for 2014 for the JSC Technical Working Group. Recommendations Recommendation 1: Add a primary element to the RDA element set with the label "Subject", definition "The subject of a work", and domain Work. The corresponding Registry property will have rdfs:label "has subject", skos:definition "Relates a work to the subject of a work", rdfs:domain rdac:c10001, and no range. Recommendation 2: Bring the RDA descriptive s designators into line with FRSAD by allowing only Work to be the domain of primary descriptive designators for WEMI entities (and the range of their reciprocal designators) as indicated in Table 4, and by adding subproperty s to the new subject element.

Page 7 of 15 Recommendation 3: Add to RDA the elements: Reference to Published Citation (Work), Definition: "A citation for a published a work.", domain: Work; Reference to Published Citation (Expression), Definition: "A citation for a published an expression.", domain: Expression; Reference to Published Citation (Manifestation), Definition: "A citation for a published a manifestation.", domain: Manifestation; Reference to Published Citation (Item), Definition: "A citation for a published an item.", domain: Item. Recommendation 4: Develop a set of designators that relate WEMI to the Work or Expression containing the citation. Recommendation 5: New subject designators should not specify a range, unless this is required for a specified purpose such as consistency with legacy s. Recommendation 6: If Recommendation 2 is not accepted, refer the labelling of the designators in Table 1 to the discussion on element labels designated as task 3 for 2014 for the JSC Technical Working Group. Justification The recommended amendments and additions to RDA elements and designators provide a consistent and coherent framework for assessing future proposals for treating aspects of the subject in RDA. Impact The recommendations result in changes to the semantics and definitions of some designators, but do not require changes to the instructions beyond the editorial policy of duplicating Glossary definitions in the text. The addition of a primary element requires supporting text, etc. in the RDA instructions. It will have a significant impact on the utility of RDA. Summary of changes Add a primary element and four attribute elements to the RDA element set. Amend s designators to allow only Work to be the domain of primary descriptive designators for WEMI entities Marked up copy Marked up changes are given in Table 4. Additions are specified in the recommendations. Marked up copy of RDA is not provided. Appendix

Page 8 of 15

Page 9 of 15 Table 1: RDA designators for descriptive s in WEMI entities Label Definition Scope note Domain Range URI subpropof inverseof An expression described by an Expression Expression rdae:p20072 rdae:p20234 rdae:p20202 (expression) expression of a describing work. An expression of a work that Expression Expression rdae:p20202 rdae:p20234 rdae:p20072 (expression) descriptive expression describes an expression. An expression of a work that is or is a the expression. Expression Expression rdae:p20234 rdae:p20205 rdae:p20234 New 7 A manifestation described by Expression Manifestation n/a New 6 an expression of a describing work. New 8 An item described by an Expression Item n/a New 5 expression of a describing work. New 1 A work that describes an Expression Work n/a New 2 expression. New 2 An expression described by a Work Expression n/a New 1 describing work. New 3 An expression of a work that Work Expression n/a New 4 describes a work. New 4 A work described by an Expression Work n/a New 3 expression of a describing work. A work described by a Work Work rdaw:p10100 rdaw:p10230 rdaw:p10118

Page 10 of 15 descriptive work (manifestation) New 5 descriptive manifestation New 6 descriptive item describing work. A work that describes a described work. A work that is or is a the work. An item described by a describing work. A manifestation described by a describing work. An expression of a work that describes a manifestation. A work that is a the manifestation. An expression of a work that describes an item. A work that is a the item. Descriptive works include descriptions, critiques, evaluations, reviews, commentaries, etc. Work Work rdaw:p10118 rdaw:p10230 rdaw:p10100 Work Work rdaw:p10230 rdaw:p10198 rdaw:p10230 Work Item rdai:p40030 rdai:p40052 n/a Work Manifestation rdam:p30023 rdam:p30211 n/a Manifestation Expression n/a New 8 Manifestation Work rdam:p30211 rdam:p30048 n/a Item Expression n/a New 7 Item Work rdai:p40052 rdai:p40046 n/a

Page 11 of 15

Page 12 of 15 Table 2: Cross-entity matrix for RDA descriptive designators Domain\Range Work Expression Manifestation Item Work / [descriptive work ] New 2/New3 (manifestation) Expression New 1/New4 (expression)/ (expression) [descriptive expression ] Manifestation Item descriptive manifestation descriptive item New 7 New 8 New 5 n/a n/a New 6 n/a n/a Table 3: Cross-entity matrix for RDA/FRSAD descriptive designators Domain\Range Work Expression Manifestation Item Work / [descriptive work ] New 2 => ( (expression)) (manifestation) Expression New 1 => (expression) Manifestation Item descriptive manifestation => (manifestation) descriptive item => n/a n/a n/a n/a n/a n/a n/a n/a n/a

{dd August 2014} Page 13 of 15 Table 4: Amendments to RDA for FRSAD compatible designators for descriptive s in WEMI entities. Label Definition Scope note Domain Range URI subpropof inverseof descriptive A work that is or Descriptive Work Work rdaw:p10230 rdaw:p10198 rdaw:p10230 work is a the work. works include descriptions, critiques, evaluations, reviews, commentaries, etc. A work described by a Work Work rdaw:p10100 rdaw:p10230 rdaw:p10118 describing work. A work that describes a Work Work rdaw:p10118 rdaw:p10230 rdaw:p10100 (expression) (expression) descriptive expression (manifestation) descriptive manifestation described work. An expression described by an expression of a describing work. An expression of a work that describes an expression. An expression of a work that is or is a the expression. A manifestation described by a describing work. A work that is a the describes a manifestation. Expression Work Expression rdae:p20072 rdaw:p1???? rdae:p20234 rdae:p20202 Expression Expression rdae:p20202 rdae:p20234 rdae:p20072 Work rdaw:p1???? Expression Expression rdae:p20234 rdae:p20205 rdae:p20234 Work Manifestation rdam:p30023 rdaw:p1???? rdam:p30211 rdam:p30211 Manifestation Work rdam:p30211 rdam:p30048 rdam:p30023 rdaw:p1????

{dd August 2014} Page 14 of 15 (manifestation) descriptive item An item described by a describing work. A work that is a the describes an item. Work Item rdai:p40030 rdaw:p1???? rdai:p40052 rdai:p40052 Item Work rdai:p40052 rdai:p40046 rdai:p40030 rdaw:p1????

{dd August 2014} Page 15 of 15 Table 5: RDA/FRSAD designators for descriptive s in WEMI entities. Label Definition Scope note Domain Range URI subpropof inverseof descriptive A work that is or Descriptive Work Work rdaw:p10230 rdaw:p10198 rdaw:p10230 work is a the work. works include descriptions, critiques, evaluations, reviews, commentaries, etc. A work described by a Work Work rdaw:p10100 rdaw:p10230 rdaw:p10118 describing work. A work that describes a Work Work rdaw:p10118 rdaw:p10230 rdaw:p10100 described work. An expression described by a Work Expression rdaw:p1???? rdae:p20202 (expression) work. A work that describes an Expression Work rdae:p20202 rdaw:p1???? (expression) expression. A manifestation described by Work Manifestation rdaw:p1???? rdam:p30211 (manifestation) a describing work. A work that describes a Manifestation Work rdam:p30211 rdaw:p1???? (manifestation) manifestation. An item described by a Work Item rdaw:p1???? rdai:p40052 describing work. A work that describes an item. Item Work rdai:p40052 rdaw:p1????