5JSC/Editor/RDA/Section 1/Chapter 2
March 7, 2008
To:
From:
Subject:
Joint Steering Committee for Development of RDA
Tom Delsey, RDA Editor
Draft of RDA – Section 1 – Chapter 2
Related documents:
5JSC/Editor/RDA/Part A/Chapter 2/Rev
5JSC/M/198-203
Chapter 2 January 2008 wiki
Chapter 4-5 February 2008 wiki
Review of examples in Part A, chapters 1-2, 4-5
5JSC/Editor/Editor’s Guide
Attached is a draft of Section 1, chapter 2, incorporating the following changes to the September
2007 Editor’s draft (5JSC/Editor/RDA/Part A/Chapter 2/Rev):
1.
changes agreed at the October 2007 JSC meeting (see 5JSC/M/198-203)
2.
changes noted as agreed in the Chapter 2 January 2008 wiki
3.
changes noted as agreed in the Chapter 4-5 February 2008 wiki
4.
additions, deletions, and changes to examples as listed in appendix 1 of the Review of examples in Part A, chapters 1-2, 4-5
Additional editorial changes have been made to improve consistency in capitalization, punctuation, sentence structure, phrasing, and word usage, in accordance with the draft Editor’s
Guide.
All changes from the September 2008 draft (other than typographical corrections and numbering changes) are highlighted in yellow.
The following issues remain to be addressed:
Abbreviations
The following are still listed under the general guidelines on transcription at 1.7.7.1 as transcribed elements in which abbreviations are to be used as instructed in appendix B:
Edition statement
Designation of edition
Parallel designation of edition
Designation of a named revision of an edition
Parallel designation of a named revision of an edition
Production statement
Place of production
1

5JSC/Editor/RDA/Section 1/Chapter 2
Parallel place of production
Producer’s name
Parallel producer’s name
Publication statement
Place of publication
Parallel place of publication
Publisher’s name
Parallel publisher’s name
Distribution statement
Place of distribution
Parallel place of distribution
Distributor’s name
Parallel distributor’s name
Once JSC has made final decisions on the use of abbreviations, all examples illustrating the elements listed will have to be reviewed and revised as necessary to reflect those decisions.
Instructions that refer to appendix B (2.14.0.4.2) or refer to abbreviations without specific reference to appendix B (2.5.1.3.2, 2.14.1.1.2, 2.14.1.3.1, 2.14.2.1.2, 2.14.2.3.1), and those that list abbreviations as recorded terms (2.11.8.3.2) will also have to be reviewed and revised as necessary.
Use of square brackets
The instruction at 2.2.3.4 specifies that the fact that information in transcribed elements has been taken from a source outside the resource itself should be indicated “either by means of an annotation or by some other means (e.g., through coding or the use of square brackets).” The wording of that instruction was affirmed at the October 2007 JSC meeting (see 5JSC/M/206.1).
However, there are numerous instructions throughout chapter 2 that specify the use of square brackets when an entire element or sub-element is being supplied from a source outside the resource itself (see 2.3.5.5.1, 2.3.5.6.1, 2.6.1.3.3-2.6.1.3.5, 2.6.2.3.4-2.6.2.3.6, 2.6.3.3.2-2.6.3.3.4,
2.6.4.3.2-2.6.4.3.4, 2.7.1.6.1-2.7.1.6.2, 2.7.3.7.1, 2.7.5.4.3, 2.7.5.6.1-2.7.5.6.2, 2.7.5.7.5,
2.8.1.6.1-2.8.1.6.2, 2.8.3.7.2, 2.8.5.4.3, 2.8.5.6.2-2.8.5.6.4, 2.9.1.6.1-2.9.1.6.2, 2.9.3.7.1, 2.9.5.4.3, and 2.9.5.6.1-2.9.5.6.2).
It was also noted at the October 2007 meeting that it had been agreed there would be no interpolations in transcribed elements (see M/205.7.1). However, there are still a number of instructions in chapter 2 that do specify adding or correcting data within a transcribed element
(see 2.4.0.5.2, 2.4.0.7.1, 2.5.1.3.2, 2.6.2.3.3, 2.7.3.4.2, 2.7.5.4.2, 2.8.3.4.2, 2.8.5.4.2, 2.8.5.7.5,
2.9.3.4.2, and 2.9.5.4.2). In all those cases, the instructions specify enclosing the supplied or corrected data in square brackets.
Hyphens versus dashes
JSC needs to address inconsistencies in the use of the term “hyphen” and “dash” in the instructions in chapter 2 (see line 432 in the chapter 2 January 2008 wiki).
The term “hyphen” is used in the instructions at 2.7.5.5.1-2.7.5.5.3, 2.8.5.5.1-2.8.5.5.3, 2.9.5.5.1-
2.9.5.5.3, and 2.11.8.8a.1. The term “dash” is used in the instruction at 2.14.0.5.3. In all cases, the punctuation specified in the instruction is being used either to indicate an open-ended range of
2

5JSC/Editor/RDA/Section 1/Chapter 2 numbers or dates, or a closed range of consecutive numbers or dates. Specifying a different mark of punctuation in the instruction at 2.14.0.5.3 is, in that respect, anomalous.
The Chicago Manual of Style specifies the use of a dash (i.e., an en dash) when giving an openended range of numbers or dates, or a closed range of consecutive numbers or dates. The use of a hyphen is reserved for compound words or to separate segments of a number such as a telephone number or ISBN.
It should also be noted that there is no perceptible difference between the character displayed when inputting a hyphen using a standard keyboard and the character displayed when using the
Insert function on an MS Word toolbar and selecting an en dash from the special characters menu.
2.3.3 Alternative title
The issue of linking words in alternative titles remains to be addressed (see 5JSC/M/200.1).
2.3.5.3 Recording other title information
The exception for serials and integrating resources at 2.3.5.3.2 specifies that other title information is to be recorded only if it is considered important for identification or access. Is that exception really necessary for an element that is designated as optional? Would it not be more appropriate to delete the exception and leave it to policy manuals to specify when not to record other title information?
2.3.7.3 Recording variant titles
The instruction at 2.3.7.3.2 specifies indicating the source of the variant title. Technically speaking, such data would fall outside the scope of the variant title element per se, and should probably be treated as data about data (i.e., either as an annotation on the source of the title or through coding). If JSC agrees, the scope of the instructions under 2.18.1.3 would need to be extended to cover annotations on the source of a variant title.
2.3.8.3 Recording earlier variant titles
2.3.9.3 Recording earlier variant titles
The instruction at 2.3.8.3.3 and 2.3.9.3.3 specify indicating the numbering or publication dates to which the change in title applies, etc. Technically speaking, such data would fall outside the scope of the earlier and later variant title elements per se, and should probably be treated as data about data (i.e., either as an annotation on title variations or through coding). If JSC agrees, the instructions and examples at 2.3.8.3.3 and 2.3.9.3.3 should be revised and transferred to 2.18.1.4.
The examples under 2.3.8.4-2.3.8.9 and 2.3.9.4-2.3.9.9 would also need to be revised.
2.5.0.2 Sources of information [edition statement]
ALA is to provide a proposal for discussion at the April 2008 JSC meeting re additional guidance on edition statements appearing on multiple sources within a resource (see line 269 in the chapter
2 January 2008 wiki).
2.5.1.1 Scope [designation of edition]
The scope note on designation of edition at 2.5.1.1.3 has been revised, as agreed at the October
2007 JSC meeting, to omit references to “version” as a term designating edition. However, there
3

5JSC/Editor/RDA/Section 1/Chapter 2 are still examples using “version” under 2.5.0.4.1, 2.5.1.3.1, 2.5.1.3.2, 2.5.5.3.1, and 2.5.7.3.1.
Should those examples be deleted?
The term “version” remains in the scope note at 2.5.0.1.4, where it applies only to resources in an unpublished form. Is that use of the term “version” acceptable?
2.7.0.1 Scope [production statement]
Further discussion is needed on the rewording of the scope statement at 2.7.0.1.2 and related changes at 2.7.0.4.1 suggested by ACOC (see line 336 in the chapter 2 January 2008 wiki).
2.7.0.4 Recording production statements
2.8.0.4 Recording publication statements
2.9.0.4 Recording distribution statements
The optional omissions added at 2.7.0.4.5, 2.8.0.4.5, and 2.9.0.4.5 have been worded as agreed at the October 2007 JSC meeting (see 5JSC/M/198.16.1). JSC needs to confirm that marks of omission are to be used to indicate omissions from the hierarchy.
2.7.0.5 Recording changes in production statements
2.8.0.5 Recording changes in publication statements
2.9.0.5 Recording changes in distribution statements
The instructions under 2.7.0.5, 2.8.0.5, and 2.9.0.5 have been left substantially unchanged, pending clarification of decisions taken at the October 2007 JSC meeting (see 5JSC/M/198.31.1 and 198.32.2).
In discussing the instructions on recording changes in production statements, publication, statements, and distribution statements, JSC decided “to record another statement when there are changes over time, with the option to provide an annotation” (see 5JSC/M/198.32.2). JSC needs to confirm that the intent of that decision was to record a second or subsequent occurrence of the production statement, publication statement, or distribution statement as a whole, not just the particular sub-element (place of production, producer's name, etc.) that had changed.
Clarification is also needed on the instructions that should be given with respect to the recording date of production, date of publication, and date of distribution in each occurrence of a production statement, publication statement, or distribution statement when there is a change in one subelement requiring the recording of a second or subsequent statement. Should the date in the earlier statement be “closed” to indicate that the statement applies only to issues or parts issued up to a certain date? Presumably the date in the second or subsequent statement would indicate the date at which the change occurred.
The decision to transfer the instructions currently under 2.7.0.5, 2.8.0.5, and 2.9.0.5 to the sections on the individual sub-elements (see 5JSC/M/198.31.1) also needs to reconsidered in light of the decision noted above that was made later in the discussions. If a second or subsequent occurrence of the production statement, publication statement, or distribution statement as a whole is to be recorded, then the instructions on when and how that is to be done need to remain with the basic instructions on recording the statement. Cross-references can be added under the instructions for the sub-elements within the statement linking back to the instructions under
2.7.0.5, 2.8.0.5, and 2.9.0.5.
4

5JSC/Editor/RDA/Section 1/Chapter 2
Keeping the instructions on recording changes in production statements, publication statements, and distribution statements where they are currently (i.e., with the basic instructions on recording the element as a whole) would also be consistent with the placement of the corresponding instructions on recording changes in edition statements and series statements, elements which also contain sub-elements. The only instances in which instructions on recording changes are not included with the basic instructions at the element level are those where there are element subtypes (as distinct from sub-elements) for which there are different criteria for determining how changes are to be recorded.
2.7.5.3 Recording date of production
2.8.5.3 Recording date of publication
2.9.5.3 Recording date of distribution
Further discussion is needed re instructions on recording multiple dates for the same function (see line 358 in the chapter 2 January 2008 wiki).
2.7.5.6 Date of production not identified in the resource
2.8.5.6 Date of publication not identified in the resource
2.9.5.6 Date of distribution not identified in the resource
The instructions under 2.7.5.6, 2.8.5.6, and 2.9.5.6 have been restructured, replacing the comments on examples with explicit instructions on the form in which supplied dates are to be recorded in specific cases, as suggested by the CCC rep. JSC needs to assess whether those instructions adequately cover the variety of supplied dates that might be given (i.e., year, decade, century); whether the conventions for differentiating between a single date, a range of date, and a terminal date are clear and consistent; and whether the conventions for indicating uncertainty are appropriate. The instructions also need to be reviewed in the context of the broader issues relating to the use of square brackets noted above.
Note also that the example under probable range of decades has been revised to be consistent with the instruction as written. Is the wording of the instruction appropriate?
2.14.0.4 Recording resource identifiers
The instruction at 2.14.0.4.2 specifies using abbreviations as instructed in appendix B. That instruction will have to be reviewed once JSC has made decisions on appendix B.
2.18.6.3 Details relating to publication statement
Further discussion is needed on whether the instruction at 2.18.6.3.1 is adequate to cover situations where two bodies are named by functions are not explicit (see line 311 in the chapter 2
January 2008 wiki).
5