The Z39.50 Cross-Domain Attribute Set
Version
1.4
1999/08/04
Scope
The Z39.50 Cross Domain (XD) Attribute Set
allows a client to perform simple non-domain-specific searches of a database.
It is not intended for sophisticated domain-specific searches or for searches
where semantic precision is required. Such searches should use domain-specific
attribute sets. Cross Domain searches are semantically fuzzy.
The XD Attribute Set
Access Point Attribute Type
The values and semantics of the Access Point
attributes are taken from the definitions of the Dublin Core elements, with the
exception of Name which the Z39.50 Implementors Group has chosen to create from
an aggregation of the DC Creator, Editor and Publisher elements.
|
Name |
Value |
Meaning |
|
Title |
1 |
A name given to the resource. |
|
Subject |
2 |
The topic of the content of the resource. |
|
Name |
3 |
A person or organization associated with the resource. |
|
Description |
4 |
An account of the content of the resource. |
|
Date |
5 |
A date associated with the creation or availability of the resource. |
|
Resource Type |
6 |
The nature or genre of the content of the resource. |
|
Format |
7 |
The physical or digital manifestation of the resource |
|
Resource Identifier |
8 |
An unambiguous reference to the resource within a given context. |
|
Source |
9 |
An identifier of a resource from which the present resource, in whole or in part, is derived. |
|
Language |
10 |
A language of the intellectual content of the resource. |
|
Relation |
11 |
An identifier of a related resource. |
|
Coverage |
12 |
The extent or scope of the resource. |
|
Rights Management |
13 |
Information about rights held in and over the resource. |
Semantic Qualifier Attribute Type
No values are defined in this attribute set.
Functional Qualifier Attribute Type
No values are defined in this attribute set.
Language Attribute Type
No values are defined in this attribute set.
They are defined in the Z39.50 Utility attribute set.
Content Authority Attribute Type
No values are defined in this attribute set.
Expansion/Interpretation Attribute
Type
No values are defined in this attribute set.
They are defined in the Z39.50 Utility attribute set.
Normalized Weight Attribute Type
No values are defined in this attribute set.
They are defined in the Z39.50 Utility attribute set.
Hit Count Attribute Type
No values are defined in this attribute set.
They are defined in the Z39.50 Utility attribute set.
Comparison Attribute Type
No values are defined in this attribute set.
They are defined in the Z39.50 Utility attribute set.
Format/Structure Attribute Type
Development of this attribute awaits
developments in the Z39.50 Implementors Group and other communities. A clear
example is the ISO 1066 date format. Beyond that single example, there is
little agreement.
Occurrence Attribute Type
No values are defined in this attribute set.
They are defined in the Z39.50 Utility attribute set.
Indirection Attribute Type
No values are defined in this attribute set.
Some values are defined in the Z39.50 Utility attribute set.
Further Reading
Z39.50 Attribute Architecture -- Version 1.1 explains the attribute architecture underlying the
Cross Domain Attribute Set. It explains how attributes interact including
attributes from other attribute sets.
A document has been produced explaining the
rationale behind the Cross Domain Attribute Set. It can be found at http://www.oclc.org/~levan/docs/crossdomainattributesetcommentary.html.
The Dublin Core Metadata Initiative has definitions of the DC elements as well as other
information.
Appendix 1: XD/tagSet-G
Crosswalk
The following table shows how the Cross
Domain attribute set Access Points relate to the tagSet-G elements available
for metadata retrieval in Z39.50. The purpose is not to declare the two columns
to be semantically identical. The purpose is to show how the semantically
precise elements in the right column would map to the intentionally
semantically fuzzy Access Points in the left column. The elements in the right
column often have an is-a-kind-of relationship with the attributes in the left
column.
|
Access Point |
tagSet-G element(s) |
|
1 Title |
(2,1) title |
|
2 Subject |
(2,21) subject |
|
3 Name |
(2,2)author, (2,7) name, (2,31) publisher, (2,32) contributor |
|
4 Description |
(2,17) description, (2,19) DocumentContent, (2,32) abstract |
|
5 Date |
(2,4) publicationDate, (2,8) dateTime |
|
6 Resource Type |
(2,22) resourceType |
|
7 Format |
(2,27) format |
|
8 Resource Identifier |
(2,5) documentId, (2,28) identifier |
|
9 Source |
(2,33) source |
|
10 Language |
(2,20) language |
|
11 Relation |
(2,30) relation |
|
12 Coverage |
(2,34) coverage |
|
13 Rights Management |
(2,29) rights |
Appendix 2: XD/Bib-1
Crosswalk
The following table shows how the Cross
Domain attribute set Access Points relate to the Bib-1 Use attributes. The
purpose of this appendix is not to declare the two columns to be semantically
identical. The purpose is to show how the semantically precise Use attributes
in the right column would map to the intentionally semantically fuzzy Access
Points in the left column. The attributes in the right column often have an
is-a-kind-of relationship with the attributes in the left column.
|
Access Point |
Bib-1 Use attribute(s) |
|
1 Title |
4 Title, 5 Title series, 6 Title uniform,
33 Title key, 34 Title collective, 35 Title parallel, 36 Title cover, 37
Title added title page, 38 Title caption, 39 Title running, 40 Title spine,
41 Title other variant, 42 Title former, 43 Title abbreviated, 44 Title
expanded 1033 Title-host-item 1036 Author-Title-Subject 1143
Resource-Description 1068 Reference 1069 Referenced-journal 1178
Cross-Reference-Title 1082 Title-translated 1096 Title-later |
|
2 Subject |
21 Subject heading, 22 Subject Rameau, 23
BDI index subject, 24 INSPEC subject, 25 MeSH subject, 26 PA
subject, 27 LC subject heading, 28 RVM subject heading, 29
Local subject index, 45 Subject precis, 46 Subject rswk, 47 Subject
subdivision, 1008 Subject--LC children's, 1009 Subject
name--personal
1112 Controlled-Subject-Index 1113
Subject-Thesaurus 1114 Subject-Terms-Controlled 1115 Controlled-Term
1036 Author-Title-Subject 1071 Section-heading 1072 Subject-GOO 1073 Subject-name-conference 1074
Subject-name-corporate 1075 Subject-name-form 1076
Subject-name-geographical 1077 Subject-name-chronological 1078
Subject-name-title 1079 Subject-name-topical 1080
Subject-uncontrolled 1081 Terminology-chemical 1085
Subject-AGROVOC 1086 Subject-COMPASS 1087 Subject-EPT 1088
Subject-NAL 1089 Classification-BCM 1090 Classification-DB 1206 MusicalTheme |
|
3 Name |
1 Personal name, 2 Corporate name, 3
Conference name, 1002 Name, 1003 Author, 1004 Author-name personal, 1005
Author-name corporate, 1006 Author-name conference, 1018 Publisher, 1020
Editor, 1131 Distributor, 1132 Distributor-Name, 1133
Distributor-Organization, 1036 Author-Title-Subject, 1057
Meeting-organizer, 1068 Reference, 1185 Performer, 1186 Performer-Individual, 1187 Performer-Group |
|
4 Description |
62 Abstract, 63 Note, 1156 Methodology, 1175 Purpose, 1176 Agency-Program |
|
5 Date |
30 Date, 31 Date of publication, 32 Date of
acquisition, 1011 Date/time added to db, 1012 Date/time last
modified, 1054 Date-conference, 1055 Date-record-status, 1184
Record-Review-Date, 1196 Date-Composition, 1197 Date-Recording |
|
6 Resource Type |
1001 Record type, 1034 Content-type |
|
7 Format |
1031 Material-type, 1153 Linkage-type |
|
8 Resource Identifier |
7 ISBN, 8 ISSN, 9 LC card number, 10 BNB
card number, 11 BGF number, 12 Local number, 48 No. nat'l biblio., 49 No.
legal deposit, 50 No. govt. pub., 51 No. music publisher, 52
Number db, 60 CODEN, 1007 Identifier--standard, 1027 Report-number, 1028
Stock-number, 1030 Thematic-number, 1032 Doc-id, 1048
Control-number-GKD, 1049 Control-number-linking, 1050 Control-number-PND, 1051 Control-number-SWD, 1052 Control-number-ZDB, 1059 Number-CAS-registry, 1060 Number-document, 1061 Number-local-accounting, 1062 Number-local-acquisition, 1063 Number-local-call-copy-specific, 1064 Number-of-reference, 1065 Number-norm, 1066 Number-volume, 1180 Cross-Reference-Linkage, 1181 Schedule-Number, 1182 Original-Control-Identifier, 1091 Identifier-ISRC, 1092 Identifier-ISMN, 1093 Identifier-ISRN, 1094 Identifier-DOI, 1154 Linkage, 1200 Number-ISWC, 1201 Number-Matrix, 1202 Number-Plate |
|
9 Source |
1019 Record-source, 1033 Host-item, 1155 Sources-Of-Data |
|
10 Language |
54 Code--language, 1038 Abstract-language, 1095 Code-language-original, 1183 Language-Of-Record |
|
11 Relation |
1179 Cross-Reference-Relationship |
|
12 Coverage |
55 Code--geographic area, 1083 Year-of-beginning, 1084 Year-of-ending, 1116 Spatial-Domain, 1117 Bounding-Coordinates, 1122 Place, 1123 Place-Keyword-Thesaurus, 1124 Place-Keyword, 1125 Time-Period, 1126 Time-Period-Textual, 1127 Time-Period-Structured, 1130 Time-Period, 1149 Available-Time-Period, 1150 Available-Time-Textual, 1151 Available-Time-Structured, 1174 Supplemental-Information |
|
13 Rights Management |
1157 Access-Constraints, 1158 General-Access-Constraints, 1159 Originator-Dissemination-Control, 1160 Security-Classification-Control, 1161 Use-Constraints |
Appendix 3: XD/GILS
Crosswalk
The following table shows how the Cross
Domain Attribute Set Access Points relate to the GILS Use attributes. Since the
GILS Attribute Set inherits the Bib-1 Attribute Set Use attributes, Appendix 2
also applies here. The purpose of this appendix is not to declare the two
columns to be semantically identical. The purpose is to show how the
semantically precise Use attributes in the right column would map to the
intentionally semantically fuzzy Access Points in the left column. The
attributes in the right column often have an is-a-kind-of relationship with the
attributes in the left column.
|
Access Point |
GILS Use attribute(s) |
|
1 Title |
2016 resourceDescription, 2046 crossReferenceTitle |
|
2 Subject |
2002 subjectTermsControlled, 2036 subjectThesaurus, 2057 controlledSubjectIndex, 2058 uncontrolledTerm, 2074 controlledTerm |
|
3 Name |
2000 distributor, 2001 distributorName, 2006 distributorOrganization |
|
4 Description |
2003 purpose, 2034 agencyProgram, 2037 methodology |
|
5 Date |
2051 recordReviewDate |
|
6 Resource Type |
none |
|
7 Format |
2022 linkageType |
|
8 Resource Identifier |
2021 linkage, 2047 crossReferenceLinkage, 2049 originalControlIdentifier, 2056 scheduleNumber |
|
9 Source |
2035 sourcesOfData |
|
10 Language |
2017 languageOfRecord |
|
11 Relation |
2070 crossReferenceRelationship |
|
12 Coverage |
2019 availableTimeStructured, 2020 availableTimeTextual, 2042 placeKeyword, 2043 placeKeywordThesaurus, 2044 timePeriodStructured , 2045 timePeriodTextual, 2050 supplementalInformation, 2059 spatialDomain, 2060 boundingCoordinates, 2061 place, 2062 timePeriod, 2065 availableTimePeriod |
|
13 Rights Management |
2004 generalAccessConstraints, 2005 useConstraints, 2052 OriginatorDisseminationControl, 2053 SecurityClassificationControl 2066 accessConstraints |