RDA 9.2: Addition of elements for Given name and Surname

Similar documents
Abstract. Justification. Scope. RSC/RelationshipWG/1 8 August 2016 Page 1 of 31. RDA Steering Committee

Subject: Fast Track entries and other revisions included in the October 2016 release of RDA Toolkit

Joint Steering Committee for Development of RDA Judith A. Kuhagen, Secretary, JSC Colour content in RDA

Preparing for the new RDA Toolkit: special topics

Instantiating LRM in RDA K AT H Y G L E N N A N H E A D, O R I G I N A L & S P E C I A L C O L L E C T I O N S C ATA LO G I N G, U N I V E R S I T Y

Joint Steering Committee for Development of RDA Kathy Glennan, ALA Representative 2.7 Production Statement: changing method of recording

1. Additional text and examples in

RDA Steering Committee Update F EB. 10, 2018

The change to the paragraph on appendix B in 0.5 is from 6JSC/CCC/10/Sec final.

6JSC/DNB/Discussion/3 July 31, 2014 page 1 of 5

Abstract. Justification. Scope. RSC/TechnicalWG/1 8 August 2016 Page 1 of 39. RDA Steering Committee

Mapping of ISBD area 0 vocabularies to RDA/ONIX Framework vocabularies

Joint Steering Committee for Development of RDA

Country Associated with the Corporate Body Other Place Associated with the Corporate Body.

FRBR Primary Entities

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

Background. Issues and Recommendations. 6JSC/ALA/26 August 2, 2013 page 1 of 10

NACO-AV Workshop Kansas City, MO October 23, 2014 Presented by Peter H. Lisius, Music and Media Catalog Librarian, Kent State University

This Figure here illustrates the operation for a 2-input OR gate for all four possible input combinations.

Merging Recording Base Material and Base Material for Microfilm Microfiche, Photographic Film, and Motion Picture Film.

Mary McKeown May Institute May 25, 2011

Winterbourne House (Winterbourne, New South Wales) Space Needle (Seattle, Washington) Normanby (Redcar and Cleveland, England)

Definition of Bulk Electric System Phase 2

Joint Steering Committee for Development of RDA Dave Reser, LC Representative Subject: Revision of 9.6

No, the monkey on my back (picture taken in Gibraltar) is not named RDA!

Suggested Statement/Substantiation for The PoE Task Group PIs

To: Joint Steering Committee for Development of RDA From: Dave Reser, LC Representative Subject: Revision of 9.6

Related documents. Justification. Issues. Status. 6JSC/ALA/44/rev/UK rep follow up 31st January 2016 Page 1 of 12. RDA Steering Committee

PRC Generator Relay Loadability. Guidelines and Technical Basis Draft 4: (June 10, 2013) Page 1 of 75

MPJO : FEATURE WRITING GEORGETOWN UNIVERSITY: MPS- JOURNALISM Tuesdays, 6 p.m. to 9:20 p.m. Summer 2014

Standard VAR-002-2b(X) Generator Operation for Maintaining Network Voltage Schedules. 45-day Formal Comment Period with Initial Ballot June July 2014

Alberta Reliability Standard Frequency Response and Frequency Bias Setting BAL-003-AB-1.1

PRC Generator Relay Loadability. Guidelines and Technical Basis Draft 5: (August 2, 2013) Page 1 of 76

Standard VAR-002-2b(X) Generator Operation for Maintaining Network Voltage Schedules

Standard VAR-002-2b(X) Generator Operation for Maintaining Network Voltage Schedules

Joint Steering Committee for Development of RDA Bill Leonard, CCC representative Subject: Revision of RDA (Dimensions of still images)

Fiscal 2007 Environmental Technology Verification Pilot Program Implementation Guidelines

Patents reward inventions (Lundbeck). What is an invention? How are subject matter conceived as inventions?

Operational Intelligence to Deliver Smart Solutions. Copyright 2015 OSIsoft, LLC

Comparison of the definition of innovation in the Oslo Manual and the definition used by the International Organisation for Standardisation (ISO)

Joint ILAC CIPM Communication regarding the. Accreditation of Calibration and Measurement Services. of National Metrology Institutes.

Comments on Summers' Preadvies for the Vereniging voor Wijsbegeerte van het Recht

ADVOCACY WORKING GROUP Work Plan

Identifying Significant Changes in Serials with Title Changes in the Recognition of New Works

Bulk Electric System Definition Reference Document

A DST-SARIMA project to profile publicly-funded technologies and drive them towards commercialisation.

This document is a preview generated by EVS

2

Bulk Electric System Definition Reference Document

VIUS Reports 5.3. Initial Plan for Data Element Definitions

1

General Guidelines on Constructing Access Points to Represent Persons

Applying Text Analytics to the Patent Literature to Gain Competitive Insight

How it works and Stakeholder Benefits

2 Logic Gates THE INVERTER. A logic gate is an electronic circuit which makes logic decisions. It has one output and one or more inputs.

PERSONAS, TAXONOMIES AND ONTOLOGIES MAPPING PEOPLE TO THEIR WORK AND WORK TO THEIR SYSTEMS (DATE)

SPECIAL REGULATIONS FOR THE EVALUATION OF MAXIMAPHILY EXHIBITS AT FIP EXHIBITIONS (SREV)

CIDOC CRM-based modeling of archaeological catalogue data

Working with Woodworking Machinery. Ofqual unit reference number (code) Organisation Reference A/507/2883. Unit Level Level 2. Unit Sub Level GLH 120

IAASB Main Agenda (March, 2015) Auditing Disclosures Issues and Task Force Recommendations

Standard Development Timeline

Technical Requirements for Land Mobile and Fixed Radio Services Operating in the Bands / MHz and / MHz

Digital signal is denoted by discreet signal, which represents digital data.there are three types of line coding schemes available:

April 30, Andreas Bergman Chair International Public Sector Accounting Standards Board 529 Fifth Avenue, 6th Floor New York, NY USA

EL PASO COMMUNITY COLLEGE PROCEDURE

Authorized Access Points in RDA

A.1.2 If a player's opponent is unable to cycle their deck (see E.2.2), that player wins the game.

Operational Intelligence to deliver Smart Solutions

arxiv: v2 [cs.ai] 15 Jul 2016

ENGINEERING COUNCIL OF SOUTH AFRICA. Qualification Standard for Higher Certificate in Engineering: NQF Level 5

CHAPTER 6: Tense in Embedded Clauses of Speech Verbs

Airwave Service Government Security Classifications Guidance

Guide to the Genealogy Search

IMPLEMENTING AGREEMENT NON-NUCLEAR ENERGY SCIENTIFIC AND TECHNOLOGICAL CO-OPERATION

Bulk Electric System Definition Reference Document

June 17, 2013 JPO / U.S. Bar Liaison Council Meeting 2013

ISO Graphical symbols Safety colours and safety signs Part 3: Design principles for graphical symbols for use in safety signs

Arrangements for: National Progression Award in Food Manufacture (SCQF level 6) Group Award Code: GF4N 46. Validation date: July 2012

Standard BAL Frequency Response and Frequency Bias Setting

8th Floor, 125 London Wall, London EC2Y 5AS Tel: +44 (0) Fax: +44 (0)

The Revised EU Block Exemption Regulation for Research and Development Agreements

Software Engineering: A Practitioner s Approach, 7/e. Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman

CSC/MATA67 Tutorial, Week 12

When recording the preferred name of a place, include an initial article if present.

In explanation, the e Modified PAR should not be approved for the following reasons:

HPS Scope & Sequence K-8 Grade Level Essential Skills DRAFT August 2009

IEEE Broadband Wireless Access Working Group <

Title Change Characteristics of Academic and Nonacademic Serials

PRC Generator Relay Loadability. A. Introduction 1. Title: Generator Relay Loadability 2. Number: PRC-025-1

How to use two Standard Sensors to calibrate a single UUT with the Power Sensor Package

Standard Specification for Candle Fire Safety Labeling 1

IS STANDARDIZATION FOR AUTONOMOUS CARS AROUND THE CORNER? By Shervin Pishevar

CHAPTER 8 RESEARCH METHODOLOGY AND DESIGN

Brave New FRBR World

EUROPEAN PATENT OFFICE U.S. PATENT AND TRADEMARK OFFICE CPC NOTICE OF CHANGES 98 DATE: JULY 1, 2015 PROJECT RP0104. Action* Subclass Group(s)

Guide to Connected Earth s Telecommunications Object Thesaurus 1.0

Fact Sheet IP specificities in research for the benefit of SMEs

Conceptual Metaphors for Explaining Search Engines

5.4 Imperfect, Real-Time Decisions

Data required for the assignation of Digital Object Identifiers in the Global Information System - v.1

Transcription:

Page 1 of 10 To: From: Subject: RDA Steering Committee Gordon Dunsire, Chair, RSC Technical Working Group RDA 9.2: Addition of elements for Given name and Surname Abstract This paper proposes the addition of given name and surname as sub-elements of RDA name of the person. Justification A task (#9.3) for the JSC Technical Working Group in 2016 is to consider adding the RDA elements family name and given name as sub-elements of name of the person, recommendation #3a of 6JSC/TechnicalWG/5, noting that recommendation #3b will be carried out by the RDA Development Team, and prepare a proposal paper. The RDA Development Team published Person properties for given name and surname in release v4.5.0 of RDA Vocabularies prior to the August 2016 release of RDA Toolkit. Surname was used instead of family name because it already had an entry in the Toolkit Glossary. The definitions are: given name: A name given to a person at birth or at some later point in addition to, or instead of, a surname. surname: A name used as a family name. Names used as family names by Romans of classical times are excluded. Issues requiring resolution Element hierarchy The current instructions for the name of the person element treat surname and given name as components; see RDA 9.2.2.9, RDA 9.2.2.18-20, and RDA 9.2.2.23. This suggests that the given name and surname elements are sub-elements of the aggregating element name of the person. It is also possible to treat surname and given name as variants of a person s name, used in isolation to label the Person. For example, friends and relations will use a given name as the name of a person, while academic colleagues may use a surname on its own. This suggests that given name and surname might also be element sub-types of name of the person.

Page 2 of 10 There is no restriction in RDF on a property being a sub-property of a super-property and also being specified in a syntax encoding scheme as a component of the super-property. It is not clear what will be the impact of the proposed FRBR-LRM entity Nomen. Given name, surname, and name of the person are refinements of the LRM appellation relationship, so each implies a different type of Nomen. Recommendation 1: The given name and surname elements should be treated in the RDA instructions as sub-elements of name of the person until further review of the impact of the LRM is undertaken. Name of the family There is an overlap in the semantics of surname and name of the family, reflected in the definition of surname and the instructions at RDA 10.2.2.8. The context of use is different, and it is likely that the semantics are not completely equivalent. Recommendation 2: The surname and name of the family elements should be related only by instruction references, and not semantic relationships, until further review of the impact of the LRM is undertaken. Patronymic RDA 9.2.2.19 treats a patronymic as a separate piece of data in a similar way to the current instructions for surname in RDA 9.2.2.9. The examples emphasize the separation of patronymic from given name, and surname from name, respectively. Recommendation 3: Add patronymic as a separate sub-element of name of the person to complement given name and surname. Components of a name of a person If the revisions and Recommendation 3 are accepted, RDA will accommodate data for components of a name of a person in the discrete elements listed in Table 1. Components are treated in RDA as parts of a name and qualifiers of a name, but there is no clear distinction between these functions. Table 1: RDA components of name of the person Element Instruction number surname 9.2.1.5 given name 9.2.1.6 patronymic tba

Page 3 of 10 title of the person 9.4 fuller form of name 9.5 other designation associated with the person 9.6 Instance data that cannot be assigned to any of these sub-elements can be accommodated in the parent element name of the person. If there is a further regular pattern or semantic structure in such data, it may indicate additional components for consideration as subelements. All of these elements are assigned to the Person entity. In the LRM, they would be treated as components of a name and assigned to the Nomen entity. Recommendation 4: Review the RDA accommodation of components of name of the person as distinct sub-elements of LRM Nomen, using IFLA's Names of Persons service as a source of data. Recommendations Recommendation 1: The given name and surname elements should be treated in the RDA instructions as sub-elements of name of the person until further review of the impact of the LRM is undertaken. Recommendation 2: The surname and name of the family elements should be related only by instruction references, and not semantic relationships, until further review of the impact of the LRM is undertaken. Recommendation 3: Add patronymic as a separate sub-element of name of the person to complement given name and surname. Recommendation 4: Review the RDA accommodation of components of name of the person as distinct sub-elements of LRM Nomen, using IFLA's Names of Persons service as a source of data. Impact of the revisions The recommended revisions will serve user needs to identify persons based on the information recorded in these sub-elements. The new sub-elements will support greater flexibility in constructing access points for persons in the future.

Page 4 of 10 Change: Recommended revisions for RDA Marked-up version: 9.2 Name of the Person CORE ELEMENT Preferred name for the person is a core element. Variant names for the person are optional. 9.2.1 Basic Instructions on Recording Names of Persons 9.2.1.1 Scope A name of the person is a word, character, or group of words and/or characters by which a person is known. When identifying persons, there are two categories of names: a) preferred name for the person (see 9.2.2) b) variant name for the person (see 9.2.3). A name of a person may consist of a surname (see 9.2.1.5), a given name (see 9.2.1.6), and other components (see 9.4-9.6). 9.2.1.2 Sources of Information Take the name or names of the person from any source. For additional guidance on sources of information for the preferred name for the person, see 9.2.2.2. 9.2.1.3 General Guidelines on Choosing Names of Persons Choose a preferred name for the person by applying the instructions at 9.2.2.3 and 9.2.2.5 9.2.2.7. If an individual has more than one identity, choose a preferred name for each identity (see 9.2.2.8). Names and forms of the name not chosen as the preferred name may be recorded as variant names (see 9.2.3). 9.2.1.34 General Guidelines on Recording Names of Persons Record the name chosen as the preferred name. Apply the instructions at 9.2.2.4 and 9.2.2.9 9.2.2.26.

Page 5 of 10 9.2.1.5 Surname 9.2.1.5.1 Scope When recording a name of a person, apply the general guidelines on recording names at 8.5. When those guidelines refer to an appendix, apply the additional instructions in that appendix, as applicable. Choose a preferred name for the person by applying the instructions at 9.2.2.3 and 9.2.2.5 9.2.2.7. If an individual has more than one identity, choose a preferred name for each identity (see 9.2.2.8). Record the name chosen as the preferred name. Apply the instructions at 9.2.2.4 and 9.2.2.9 9.2.2.26. Names and forms of the name not chosen as the preferred name may be recorded as variant names (see 9.2.3). A surname is a name used as a family name. Names used as family names by Romans of classical times are excluded. 9.2.1.5.2 Sources of Information Take the surname from any source. 9.2.1.5.3 Recording Surname Record the surname as the first element in the name of a person. Apply the additional instructions at 9.2.2.9, as applicable. 9.2.1.6 Given Name 9.2.1.6.1 Scope A given name is a name given to a person at birth or at some later point in addition to, or instead of, a surname. 9.2.1.6.2 Sources of Information Take the given name from any source. 9.2.1.6.3 Recording Given Name If a name of the person contains both a surname and a given name, apply the instructions at 9.2.2.9, as applicable.

Page 6 of 10 If a name of the person contains a given name but not a surname, apply the instructions at 9.2.2.18 9.2.2.19 and 9.2.2.22 9.2.2.23 as applicable. 9.2.2.9 General Guidelines on Recording Names Containing a Surname The instructions at 9.2.2.9 9.2.2.12 apply to all names containing a surname (or a name that functions as a surname) (see 9.2.1.5). 9.2.2.18 General Guidelines on Recording Names Containing Neither a Surname nor a Title of Nobility [1 st -3 rd paragraphs and their examples unchanged] Treat a roman numeral associated with a given name (see 9.2.1.6) as an integral part of the name (e.g., in the case of some popes, royalty, and ecclesiastics). 9.2.2.19 Names Including a Patronymic Record a name consisting of one or more given names (see 9.2.1.6) and a patronymic by applying the general guidelines at 8.5. 9.2.2.22 General Guidelines on Recording Names Consisting of a Phrase If: a person is commonly identified by: a) a phrase or appellation that does not contain a given name or b) a phrase that consists of a given name (see 9.2.1.6) or names preceded by words other than a term of address or a title of position or office then: consider this phrase or appellation to be the preferred name for the person. Record the phrase or appellation by applying the general guidelines on recording names at 8.5. Record the name in direct order.

Page 7 of 10 9.2.2.23 Phrase Consisting of a Given Name or Given Names Preceded by a Term of Address, Etc. Clean-copy version: If a person is commonly identified by a phrase consisting of a given name (see 9.2.1.6) preceded by a term of address or a title of position or office, consider this phrase to be the preferred name for the person. Record the phrase by applying the general guidelines on recording names at 8.5. 9.2 Name of the Person CORE ELEMENT Preferred name for the person is a core element. Variant names for the person are optional. 9.2.1 Basic Instructions on Recording Names of Persons 9.2.1.1 Scope A name of the person is a word, character, or group of words and/or characters by which a person is known. When identifying persons, there are two categories of names: a) preferred name for the person (see 9.2.2) b) variant name for the person (see 9.2.3). A name of a person may consist of a surname (see 9.2.1.5), a given name (see 9.2.1.6), and other components (see 9.4-9.6). 9.2.1.2 Sources of Information Take the name or names of the person from any source. For additional guidance on sources of information for the preferred name for the person, see 9.2.2.2. 9.2.1.3 General Guidelines on Choosing Names of Persons Choose a preferred name for the person by applying the instructions at 9.2.2.3 and 9.2.2.5 9.2.2.7. If an individual has more than one identity, choose a preferred name for each identity (see 9.2.2.8).

Page 8 of 10 Names and forms of the name not chosen as the preferred name may be recorded as variant names (see 9.2.3). 9.2.1.4 General Guidelines on Recording Names of Persons 9.2.1.5 Surname 9.2.1.5.1 Scope Record the name chosen as the preferred name. Apply the instructions at 9.2.2.4 and 9.2.2.9 9.2.2.26. When recording a name of a person, apply the general guidelines on recording names at 8.5. When those guidelines refer to an appendix, apply the additional instructions in that appendix, as applicable. A surname is a name used as a family name. Names used as family names by Romans of classical times are excluded. 9.2.1.5.2 Sources of Information Take the surname from any source. 9.2.1.5.3 Recording Surname Record the surname as the first element in the name of a person. Apply the additional instructions at 9.2.2.9, as applicable. 9.2.1.6 Given Name 9.2.1.6.1 Scope A given name is a name given to a person at birth or at some later point in addition to, or instead of, a surname. 9.2.1.6.2 Sources of Information Take the given name from any source. 9.2.1.6.3 Recording Given Name If a name of the person contains both a surname and a given name, apply the instructions at 9.2.2.9, as applicable. If a name of the person contains a given name but not a surname, apply the instructions at 9.2.2.18 9.2.2.19 and 9.2.2.22 9.2.2.23 as applicable.

Page 9 of 10 9.2.2.9 General Guidelines on Recording Names Containing a Surname The instructions at 9.2.2.9 9.2.2.12 apply to all names containing a surname (or a name that functions as a surname) (see 9.2.1.5). 9.2.2.18 General Guidelines on Recording Names Containing Neither a Surname nor a Title of Nobility [1 st -3 rd paragraphs and their examples unchanged] Treat a roman numeral associated with a given name (see 9.2.1.6) as an integral part of the name (e.g., in the case of some popes, royalty, and ecclesiastics). 9.2.2.19 Names Including a Patronymic Record a name consisting of one or more given names (see 9.2.1.6) and a patronymic by applying the general guidelines at 8.5. 9.2.2.22 General Guidelines on Recording Names Consisting of a Phrase If: a person is commonly identified by: a) a phrase or appellation that does not contain a given name or b) a phrase that consists of a given name (see 9.2.1.6) or names preceded by words other than a term of address or a title of position or office then: consider this phrase or appellation to be the preferred name for the person. Record the phrase or appellation by applying the general guidelines on recording names at 8.5. Record the name in direct order. 9.2.2.23 Phrase Consisting of a Given Name or Given Names Preceded by a Term of Address, Etc.

Page 10 of 10 If a person is commonly identified by a phrase consisting of a given name (see 9.2.1.6) preceded by a term of address or a title of position or office, consider this phrase to be the preferred name for the person. Record the phrase by applying the general guidelines on recording names at 8.5. Changes to the RDA Element Set This proposal adds these two element sub-types for the element Name of the person: Given name Surname Application profile Element Aggregating or super element Domain Vocabulary encoding scheme RDA instruction number given name name of the person Person n/a 9.2.1.6 surname name of the person Person n/a 9.2.1.5 Compare with: name of the family Family n/a 10.2