Z39.50 Profile for Access to Digital Collections
From Library of Congress Subject Headings
Z39.50 Profile for Access to Digital Collections
URI(s)
- http://id.loc.gov/authorities/subjects/sh2004001163
- info:lc/authorities/sh2004001163
- http://id.loc.gov/authorities/sh2004001163#concept
Instance Of
Scheme Membership(s)
Collection Membership(s)
Variants
ANSI Z39.50 Profile for Access to Digital Collections
Z39.50 Profile for the Digital Library Application
Broader Terms
Sources
- found: Work cat.: Collection level description, c1999: p. 23 (Z39.50 Profile for Access to Digital Collections; to support libraries and other institutions who are creating a growing number of collections of numerous diverse objects, both digital and physical that are often organised hierarchically and may be physically distributed across servers; the profile specifies a conforming subset of Z39.50-1995 to address this area) pp. 49-51 (ANSI Z39.50 Profile for Access to Digital Collections; early in its development was renamed from Z39.50 Profile for the Digital Library Application to Z39.50 Profile for Access to Digital Collections; to provide a mechanism for access to digital collections organised via descriptive information, i.e., metadata. In order to achieve this purpose, the profile provides semantics for navigating digital collections, and to locate and retrieve objects of interest.)
- found: Information retrieval (Z39.50) : application service definition and protocol specification, c2003, via NISO home page, Apr. 12, 2004: PDF p. 199 (Z39.50 Profile for Access to Digital Collections. Provides access to digital collections organized via descriptive information and semantics for navigating digital collections to locate and retrieve objects of interest.)
Change Notes
- 2004-05-05: new
- 2004-05-05: revised
Alternate Formats
Suggest terminology
The LC Linked Data Service welcomes any suggestions you might have about terminology used for a given heading or concept.
Would you like to suggest a change to this heading?
Please provide your name, email, and your suggestion so that we can begin assessing any terminology changes.
Fields denoted with an asterisk (*) are required.
