Search (49 results, page 1 of 3)

0.069985814 = product of:
  0.13997163 = sum of:
    0.036211025 = weight(_text_:data in 57) [ClassicSimilarity], result of:
      0.036211025 = score(doc=57,freq=2.0), product of:
        0.14807065 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046827413 = queryNorm
        0.24455236 = fieldWeight in 57, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.0546875 = fieldNorm(doc=57)
    0.1037606 = sum of:
      0.05934933 = weight(_text_:processing in 57) [ClassicSimilarity], result of:
        0.05934933 = score(doc=57,freq=2.0), product of:
          0.18956426 = queryWeight, product of:
            4.048147 = idf(docFreq=2097, maxDocs=44218)
            0.046827413 = queryNorm
          0.3130829 = fieldWeight in 57, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            4.048147 = idf(docFreq=2097, maxDocs=44218)
            0.0546875 = fieldNorm(doc=57)
      0.044411276 = weight(_text_:22 in 57) [ClassicSimilarity], result of:
        0.044411276 = score(doc=57,freq=2.0), product of:
          0.16398162 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.046827413 = queryNorm
          0.2708308 = fieldWeight in 57, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0546875 = fieldNorm(doc=57)
  0.5 = coord(2/4)

Abstract

Conceptual Knowledge Markup Language (CKML), an application of XML, is a new standard being promoted for the specification of online conceptual knowledge (Kent and Shrivastava, 1998). CKML follows the philosophy of Conceptual Knowledge Processing (Wille, 1982), a principled approach to knowledge representation and data analysis, which advocates the development of methodologies and techniques to support people in their rational thinking, judgement and actions. CKML was developed and is being used in the WAVE networked information discovery and retrieval system (Kent and Neuss, 1994) as a standard for the specification of conceptual knowledge

Date

30.12.2001 16:22:41

0.06274002 = product of:
  0.12548004 = sum of:
    0.09580538 = weight(_text_:data in 48) [ClassicSimilarity], result of:
      0.09580538 = score(doc=48,freq=14.0), product of:
        0.14807065 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046827413 = queryNorm
        0.64702475 = fieldWeight in 48, product of:
          3.7416575 = tf(freq=14.0), with freq of:
            14.0 = termFreq=14.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.0546875 = fieldNorm(doc=48)
    0.029674664 = product of:
      0.05934933 = sum of:
        0.05934933 = weight(_text_:processing in 48) [ClassicSimilarity], result of:
          0.05934933 = score(doc=48,freq=2.0), product of:
            0.18956426 = queryWeight, product of:
              4.048147 = idf(docFreq=2097, maxDocs=44218)
              0.046827413 = queryNorm
            0.3130829 = fieldWeight in 48, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.048147 = idf(docFreq=2097, maxDocs=44218)
              0.0546875 = fieldNorm(doc=48)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

Current hypertext systems have been widely and effectively used on relatively small data volumes. Explores the potential of database technology for aiding the implementation of hypertext systems holding very large amounts of complex data. Databases meet many requirements of the hypermedium: persistent data management, large volumes, data modelling, multi-level architecture with abstractions and views, metadata integrated with operational data, short-term transaction processing and high-level end-user languages for searching and updating data. Describes a system implementing the storage, retrieval and recall of trails through hypertext comprising textual complex objects (to illustrate the potential for the use of data bases). Discusses weaknesses in current database systems for handling the complex modelling required

0.038636878 = product of:
  0.077273756 = sum of:
    0.04138403 = weight(_text_:data in 2408) [ClassicSimilarity], result of:
      0.04138403 = score(doc=2408,freq=2.0), product of:
        0.14807065 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046827413 = queryNorm
        0.2794884 = fieldWeight in 2408, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.0625 = fieldNorm(doc=2408)
    0.03588973 = product of:
      0.07177946 = sum of:
        0.07177946 = weight(_text_:22 in 2408) [ClassicSimilarity], result of:
          0.07177946 = score(doc=2408,freq=4.0), product of:
            0.16398162 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046827413 = queryNorm
            0.4377287 = fieldWeight in 2408, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=2408)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

This paper discuesses the goals and outcome of the OCLC/NCSA Metadata Workshop held March 1-3, 1995 in Dublin Ohio. The resulting proposed "Dublin Core" Metadata Elements Set is described briefly. An attempt is made to map the Dublin Core data elements to USMARC; problems and outstanding questions are noted.

Date

13. 1.2007 18:31:22

Source

Cataloging and classification quarterly. 22(1996) nos.3/4, S.43-58

0.029208332 = product of:
  0.058416665 = sum of:
    0.036211025 = weight(_text_:data in 6128) [ClassicSimilarity], result of:
      0.036211025 = score(doc=6128,freq=2.0), product of:
        0.14807065 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046827413 = queryNorm
        0.24455236 = fieldWeight in 6128, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.0546875 = fieldNorm(doc=6128)
    0.022205638 = product of:
      0.044411276 = sum of:
        0.044411276 = weight(_text_:22 in 6128) [ClassicSimilarity], result of:
          0.044411276 = score(doc=6128,freq=2.0), product of:
            0.16398162 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046827413 = queryNorm
            0.2708308 = fieldWeight in 6128, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0546875 = fieldNorm(doc=6128)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

Discusses the goals and outcome of the OCLC/NCSA Metadata Workshop, held in Dublin, Ohio, 1-3 Mar 95, which resulted in the proposed 'Dublin Core' Metadata Elements. Describes an attempt to map the Dublin Core data elements to the USMARC format (with particular reference to USMARC field 856 for electronic locations), noting problems and outstanding questions. The USMARC format elements considered include: subject, title, author, other-agent, publisher, publication date, identifier, object-type, form, relation, language, source, coverage, and other issues

Series

Cataloging and classification quarterly; vol.22, nos.3/4

0.02594015 = product of:
  0.1037606 = sum of:
    0.1037606 = sum of:
      0.05934933 = weight(_text_:processing in 3597) [ClassicSimilarity], result of:
        0.05934933 = score(doc=3597,freq=2.0), product of:
          0.18956426 = queryWeight, product of:
            4.048147 = idf(docFreq=2097, maxDocs=44218)
            0.046827413 = queryNorm
          0.3130829 = fieldWeight in 3597, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            4.048147 = idf(docFreq=2097, maxDocs=44218)
            0.0546875 = fieldNorm(doc=3597)
      0.044411276 = weight(_text_:22 in 3597) [ClassicSimilarity], result of:
        0.044411276 = score(doc=3597,freq=2.0), product of:
          0.16398162 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.046827413 = queryNorm
          0.2708308 = fieldWeight in 3597, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0546875 = fieldNorm(doc=3597)
  0.25 = coord(1/4)

Abstract

To improve searching, filtering and processing of information on the Web, a common effort is made in the direction of metadata, defined as machine understandable information about Web resources or other things. In particular, the eXtensible Markup Language (XML) aims at providing a common syntax to emerging metadata formats. Proposes the Structured Graph Format (SGF) an XML compliant markup language based on structured graphs, for capturing Web sites' structure. Presents SGMapper, a client-site tool, which aims to facilitate navigation in large Web sites by generating highly interactive site maps using SGF metadata

Date

1. 8.1996 22:08:06

0.020742472 = product of:
  0.08296989 = sum of:
    0.08296989 = weight(_text_:data in 1264) [ClassicSimilarity], result of:
      0.08296989 = score(doc=1264,freq=42.0), product of:
        0.14807065 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046827413 = queryNorm
        0.56033987 = fieldWeight in 1264, product of:
          6.4807405 = tf(freq=42.0), with freq of:
            42.0 = termFreq=42.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.02734375 = fieldNorm(doc=1264)
  0.25 = coord(1/4)

Abstract

Defining metadata as "data about data" provokes more questions than it answers. What are the forms of the data and metadata? Can we be more specific about the manner in which the metadata is "about" the data? Are data and metadata distinguished only in the context of their relationship? Is the nature of the relationship between the datasets declarative or procedural? Can the metadata itself be described by other data? Over the past several years, we have been engaged in a number of efforts examining the role, format, composition, and architecture of metadata for networked resources. During this time, we have noticed the tendency to be led astray by comfortable, but somewhat inappropriate, models in the non-digital information environment. Rather than pursuing familiar models, there is the need for a new model that fully exploits the unique combination of computation and connectivity that characterizes the digital library. In this paper, we describe an extension of the Warwick Framework that we call Distributed Active Relationships (DARs). DARs provide a powerful model for representing data and metadata in digital library objects. They explicitly express the relationships between networked resources, and even allow those relationships to be dynamically downloadable and executable. The DAR model is based on the following principles, which our examination of the "data about data" definition has led us to regard as axiomatic: * There is no essential distinction between data and metadata. We can only make such a distinction in terms of a particular "about" relationship. As a result, what is metadata in the context of one "about" relationship may be data in another. * There is no single "about" relationship. There are many different and important relationships between data resources. * Resources can be related without regard for their location. The connectivity in networked information architectures makes it possible to have data in one repository describe data in another repository. * The computational power of the networked information environment makes it possible to consider active or dynamic relationships between data sets. This adds considerable power to the "data about data" definition. First, data about another data set may not physically exist, but may be automatically derived. Second, the "about" relationship may be an executable object -- in a sense interpretable metadata. As will be shown, this provides useful mechanisms for handling complex metadata problems such as rights management of digital objects. The remainder of this paper describes the development and consequences of the DAR model. Section 2 reviews the Warwick Framework, which is the basis for the model described in this paper. Section 3 examines the concept of the Warwick Framework Catalog, which provides a mechanism for expressing the relationships between the packages in a Warwick Framework container. With that background established, section 4 generalizes the Warwick Framework by removing the restriction that it only contains "metadata". This allows us to consider digital library objects that are aggregations of (possibly distributed) data sets, with the relationships between the data sets expressed using a Warwick Framework Catalog. Section 5 further extends the model by describing Distributed Active Relationships (DARs). DARs are the explicit relationships that have the potential to be executable, as alluded to earlier. Finally, section 6 describes two possible implementations of these concepts.

0.020692015 = product of:
  0.08276806 = sum of:
    0.08276806 = weight(_text_:data in 46) [ClassicSimilarity], result of:
      0.08276806 = score(doc=46,freq=8.0), product of:
        0.14807065 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046827413 = queryNorm
        0.5589768 = fieldWeight in 46, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.0625 = fieldNorm(doc=46)
  0.25 = coord(1/4)

Abstract

The term 'metadata' is becoming commonly used to refer to a variety of types of data which describe other data. A familiar example is bibliographic data, which describes a book or a serial article. Suggests that a routine definiton might be: 'metadata is data which describes attributes of a resource'. Gives some examples before looking at the Dublic Core, a simple response to the challenge of describing a wide range of network resources

0.020692015 = product of:
  0.08276806 = sum of:
    0.08276806 = weight(_text_:data in 107) [ClassicSimilarity], result of:
      0.08276806 = score(doc=107,freq=8.0), product of:
        0.14807065 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046827413 = queryNorm
        0.5589768 = fieldWeight in 107, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.0625 = fieldNorm(doc=107)
  0.25 = coord(1/4)

Abstract

The term 'metadata' is becoming commonly used to refer to a variety of types of data which describe other data. A familiar example is bibliographic data, which describes a book or a serial article. Suggests that a rountine definition might be: 'Metadata is data which describes attributes of a resource'. Provides examples to expand on this before looking at the Dublin Core, a simple set of elements for describing a wide range of network resources

0.020692015 = product of:
  0.08276806 = sum of:
    0.08276806 = weight(_text_:data in 3893) [ClassicSimilarity], result of:
      0.08276806 = score(doc=3893,freq=2.0), product of:
        0.14807065 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046827413 = queryNorm
        0.5589768 = fieldWeight in 3893, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.125 = fieldNorm(doc=3893)
  0.25 = coord(1/4)

0.01828933 = product of:
  0.07315732 = sum of:
    0.07315732 = weight(_text_:data in 2363) [ClassicSimilarity], result of:
      0.07315732 = score(doc=2363,freq=4.0), product of:
        0.14807065 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046827413 = queryNorm
        0.49407038 = fieldWeight in 2363, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.078125 = fieldNorm(doc=2363)
  0.25 = coord(1/4)

Abstract

Reports on a research study, conducted at the Department of Information and Library Studies, Loughborough University, to investigate the potential of metadata for universal data management and explore the attitudes of UK information professionals to these issues

0.017919812 = product of:
  0.07167925 = sum of:
    0.07167925 = weight(_text_:data in 1425) [ClassicSimilarity], result of:
      0.07167925 = score(doc=1425,freq=6.0), product of:
        0.14807065 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046827413 = queryNorm
        0.48408815 = fieldWeight in 1425, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.0625 = fieldNorm(doc=1425)
  0.25 = coord(1/4)

Abstract

The recent increase in electronic publishing has led many in the library community to consider altering standards for bibliographic data to promote greater compatibility between digital works and their bibliographic representation. SGML has been prominently mentioned as a mechanism for encoding bibliographic data. Examines the problems and potential of applying SGML to to USMARC record standard, with a particular emphasis on issues of field order and repeatability, character set encoding, and obsolete fields

0.017919812 = product of:
  0.07167925 = sum of:
    0.07167925 = weight(_text_:data in 2210) [ClassicSimilarity], result of:
      0.07167925 = score(doc=2210,freq=6.0), product of:
        0.14807065 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046827413 = queryNorm
        0.48408815 = fieldWeight in 2210, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.0625 = fieldNorm(doc=2210)
  0.25 = coord(1/4)

Abstract

Metadata, or 'data about data', have been created and used for centuries in the print environment, though the term has its origins in the world of electronic information management. Presents the close relationship between traditional library cataloguing and the documentation of electronic data files (known as 'metadata'), showing that cataloguing is changing under the influence of information technology, but also that metadata provision is essentially an extension of traditional cataloguing processes

0.015679834 = product of:
  0.06271934 = sum of:
    0.06271934 = weight(_text_:data in 6267) [ClassicSimilarity], result of:
      0.06271934 = score(doc=6267,freq=6.0), product of:
        0.14807065 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046827413 = queryNorm
        0.42357713 = fieldWeight in 6267, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.0546875 = fieldNorm(doc=6267)
  0.25 = coord(1/4)

Abstract

The main objective of the proposed high-level 'Visual Repository Definition Language' is to anbale advanced Web presentation of large amounts of exisitng heterogeneous information. Statements of the language serve to describe the desired structure of information repositories, which are composed of metadata entities encapsulating the original data. Such approach helps to to avoid the usual relocation and restructuring of data that occurs when providing Web access to it. The language has been designed to be useful even for inexperienced programmers. Its applicability is demonstrated by a real example, creating a repository of judicial opinions from publicly available raw data

0.014631464 = product of:
  0.058525857 = sum of:
    0.058525857 = weight(_text_:data in 7684) [ClassicSimilarity], result of:
      0.058525857 = score(doc=7684,freq=4.0), product of:
        0.14807065 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046827413 = queryNorm
        0.3952563 = fieldWeight in 7684, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.0625 = fieldNorm(doc=7684)
  0.25 = coord(1/4)

Abstract

Describes the evolving ways of making documents and document like objects bibliographically accessible by the library cataloguing community and reports initiatives. Includes: definition of a basic set of data elements known as the Dublin Core; examination of library cataloguing objectives and record structures; proposals for persistent addresses for resources; and support for the idea of data registry to facilitate interoperability among metadata schemes

0.01345865 = product of:
  0.0538346 = sum of:
    0.0538346 = product of:
      0.1076692 = sum of:
        0.1076692 = weight(_text_:22 in 5743) [ClassicSimilarity], result of:
          0.1076692 = score(doc=5743,freq=4.0), product of:
            0.16398162 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046827413 = queryNorm
            0.6565931 = fieldWeight in 5743, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=5743)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Date

30. 3.2002 19:45:22

Source

Revista Española de Documentaçion Cientifica. 22(1999) no.2, S.198-219

0.013439858 = product of:
  0.053759433 = sum of:
    0.053759433 = weight(_text_:data in 2222) [ClassicSimilarity], result of:
      0.053759433 = score(doc=2222,freq=6.0), product of:
        0.14807065 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046827413 = queryNorm
        0.3630661 = fieldWeight in 2222, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046875 = fieldNorm(doc=2222)
  0.25 = coord(1/4)

Abstract

Describes the structure of metadata formats with particular reference to the taxonomy of data formats set out by the BIBLINK report of the UK Office for Library and Information Networking and based on their underlying complexity. Referes to 3 main types of metadata: Dublin Core; MARC and Federal Geographic Data Committee (FGDC). Provides practical examples of the actual codings used, illustrated with reference to the Dublin Core, Marc and FGDC elements in selected Web sites. Ends with a glossary and a list of Web sites containing background information on metadata, such as the IAMSLIC metadata homepage

Source

Data or information: the fading boundaries. Proceedings of the 23rd Annual Conference of the International Association of Aquatic and Marine Science Libraries and Information Centers (IAMSLIC), Charleston, South Carolina, 5-9 Oct. 1997. Ed.: J.W. Markham et al

0.01293251 = product of:
  0.05173004 = sum of:
    0.05173004 = weight(_text_:data in 4052) [ClassicSimilarity], result of:
      0.05173004 = score(doc=4052,freq=2.0), product of:
        0.14807065 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046827413 = queryNorm
        0.34936053 = fieldWeight in 4052, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.078125 = fieldNorm(doc=4052)
  0.25 = coord(1/4)

Abstract

This special issue of JASIS addresses different applications of metadata standards in geospatial collections, education, historical costume collection, data management, and information retrieval, end explores the future thinking of metadata standards for digital libraries

0.012802532 = product of:
  0.051210128 = sum of:
    0.051210128 = weight(_text_:data in 1055) [ClassicSimilarity], result of:
      0.051210128 = score(doc=1055,freq=4.0), product of:
        0.14807065 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046827413 = queryNorm
        0.34584928 = fieldWeight in 1055, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1055)
  0.25 = coord(1/4)

Abstract

Metadata systems are concerned with the management of data which describes other data (datasets, catalogues, or actual database management systems) and are presently the subject of intensive research. Metadata systems can be used to store richly detailed forms of information, perform seamless wide ranging searches of information distributed across networks, and to integrate information stored in disparate repositories. Describes a model design and methods of implementation derived from the experience of the Leicester University Metadata Project. The approach utilizes the incorporation of semantic metadata in addition to resource metadata, resulting in a generally more powerful system than existing global directory services. Feature of the class of design is flexibility or implementation, with the ability to provide a coherent metadata system functioning above heterogeneous autonomous distributed databases

0.012802532 = product of:
  0.051210128 = sum of:
    0.051210128 = weight(_text_:data in 5333) [ClassicSimilarity], result of:
      0.051210128 = score(doc=5333,freq=4.0), product of:
        0.14807065 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046827413 = queryNorm
        0.34584928 = fieldWeight in 5333, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5333)
  0.25 = coord(1/4)

Abstract

With the transition from cartographic materials to spatial information the nature and amount of access data for the library field is changing. Besides bibliographic data there exists now a range of metadata, each kind for specific purposes within specific user fields. To define their relation to each other they have been put into a diagram. Through the Resource Description Framework these should all be available through a common interface for Internet-searching. To prevent confusion spatial metadata is defined. Spatial metadata introduces new elements to descriptions with new application possibilities.

0.012802532 = product of:
  0.051210128 = sum of:
    0.051210128 = weight(_text_:data in 5334) [ClassicSimilarity], result of:
      0.051210128 = score(doc=5334,freq=4.0), product of:
        0.14807065 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046827413 = queryNorm
        0.34584928 = fieldWeight in 5334, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5334)
  0.25 = coord(1/4)

Abstract

Consistency and interoperability are objectives when creating standards for spatial metadata. Besides FGDC-metadata standards some other international standards are in use or will be in use soon. The use of these standards forms the basis for geospatial data infrastructures (GDI) and clearinghouses. Though most GDIs and clearinghouses are in the planning stage, the contours of regional and a global geospatial data infrastructure (GGDI) are slowly emerging. Maps should be part of the interfaces, which provide access to the GDIs and clearinghouses.