In compiling the comments on the Glossary, I made decisions based on the following considerations:
The JSC made a decision that the names of all elements, element sub-types, and sub-elements, as well as the values of at least some of the embedded vocabularies, should be included in the Glossary, even if the definition is obvious. I am including a general comment on the unfortunate affect this has on the usability of the Glossary. However, I have not included any of the specific suggestions to delete terms.
Remember that RDA is being designed as an online product. In that environment, you don't need explicit references from variant terms, so long as the term is included in the definition of the preferred term.
The definition cannot be generalized beyond what is in the instructions. For example, while it is true that geographic coordinates may be included in authority records for place names, that element is not included in Chapter 16; the JSC made a conscious decision not to include them at this time, as they are not (yet?) included in the FRBR/FRAD models.
RDA needs to support all of the implementation scenarios; therefore, it is not appropriate to make reference to authority records, as they are only applicable in scenario #2.
In general, I have been reluctant to recommend the addition of terms that are not used in the instructions. The major exception is "Continuing Resources" which I will attempt one more time to convince the JSC is a useful concept to use -- at least in the Glossary.
The JSC made a decision that the names of all elements, element sub-types, and sub-elements, as well as the values of at least some of the embedded vocabularies, should be included in the Glossary, even if the definition is obvious. I am including a general comment on the unfortunate affect this has on the usability of the Glossary. However, I have not included any of the specific suggestions to delete terms.
Remember that RDA is being designed as an online product. In that environment, you don't need explicit references from variant terms, so long as the term is included in the definition of the preferred term.
The definition cannot be generalized beyond what is in the instructions. For example, while it is true that geographic coordinates may be included in authority records for place names, that element is not included in Chapter 16; the JSC made a conscious decision not to include them at this time, as they are not (yet?) included in the FRBR/FRAD models.
RDA needs to support all of the implementation scenarios; therefore, it is not appropriate to make reference to authority records, as they are only applicable in scenario #2.
In general, I have been reluctant to recommend the addition of terms that are not used in the instructions. The major exception is "Continuing Resources" which I will attempt one more time to convince the JSC is a useful concept to use -- at least in the Glossary.
John
Leave a comment