Search (676 results, page 1 of 34)

  • × type_ss:"el"
  1. Decimal Classification Editorial Policy Committee (2002) 0.14
    0.14195535 = product of:
      0.2839107 = sum of:
        0.2839107 = product of:
          0.42586604 = sum of:
            0.3714005 = weight(_text_:abridged in 236) [ClassicSimilarity], result of:
              0.3714005 = score(doc=236,freq=6.0), product of:
                0.4697581 = queryWeight, product of:
                  8.2629 = idf(docFreq=30, maxDocs=44218)
                  0.056851476 = queryNorm
                0.79062074 = fieldWeight in 236, product of:
                  2.4494898 = tf(freq=6.0), with freq of:
                    6.0 = termFreq=6.0
                  8.2629 = idf(docFreq=30, maxDocs=44218)
                  0.0390625 = fieldNorm(doc=236)
            0.054465536 = weight(_text_:22 in 236) [ClassicSimilarity], result of:
              0.054465536 = score(doc=236,freq=4.0), product of:
                0.19908418 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.056851476 = queryNorm
                0.27358043 = fieldWeight in 236, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.0390625 = fieldNorm(doc=236)
          0.6666667 = coord(2/3)
      0.5 = coord(1/2)
    
    Abstract
    The Decimal Classification Editorial Policy Committee (EPC) held its Meeting 117 at the Library Dec. 3-5, 2001, with chair Andrea Stamm (Northwestern University) presiding. Through its actions at this meeting, significant progress was made toward publication of DDC unabridged Edition 22 in mid-2003 and Abridged Edition 14 in early 2004. For Edition 22, the committee approved the revisions to two major segments of the classification: Table 2 through 55 Iran (the first half of the geographic area table) and 900 History and geography. EPC approved updates to several parts of the classification it had already considered: 004-006 Data processing, Computer science; 340 Law; 370 Education; 510 Mathematics; 610 Medicine; Table 3 issues concerning treatment of scientific and technical themes, with folklore, arts, and printing ramifications at 398.2 - 398.3, 704.94, and 758; Table 5 and Table 6 Ethnic Groups and Languages (portions concerning American native peoples and languages); and tourism issues at 647.9 and 790. Reports on the results of testing the approved 200 Religion and 305-306 Social groups schedules were received, as was a progress report on revision work for the manual being done by Ross Trotter (British Library, retired). Revisions for Abridged Edition 14 that received committee approval included 010 Bibliography; 070 Journalism; 150 Psychology; 370 Education; 380 Commerce, communications, and transportation; 621 Applied physics; 624 Civil engineering; and 629.8 Automatic control engineering. At the meeting the committee received print versions of _DC&_ numbers 4 and 5. Primarily for the use of Dewey translators, these cumulations list changes, substantive and cosmetic, to DDC Edition 21 and Abridged Edition 13 for the period October 1999 - December 2001. EPC will hold its Meeting 118 at the Library May 15-17, 2002.
  2. Shala, E.: ¬Die Autonomie des Menschen und der Maschine : gegenwärtige Definitionen von Autonomie zwischen philosophischem Hintergrund und technologischer Umsetzbarkeit (2014) 0.08
    0.083254635 = sum of:
      0.07524602 = product of:
        0.22573805 = sum of:
          0.22573805 = weight(_text_:3a in 4388) [ClassicSimilarity], result of:
            0.22573805 = score(doc=4388,freq=2.0), product of:
              0.48198745 = queryWeight, product of:
                8.478011 = idf(docFreq=24, maxDocs=44218)
                0.056851476 = queryNorm
              0.46834838 = fieldWeight in 4388, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                8.478011 = idf(docFreq=24, maxDocs=44218)
                0.0390625 = fieldNorm(doc=4388)
        0.33333334 = coord(1/3)
      0.00800861 = product of:
        0.02402583 = sum of:
          0.02402583 = weight(_text_:12 in 4388) [ClassicSimilarity], result of:
            0.02402583 = score(doc=4388,freq=2.0), product of:
              0.15724345 = queryWeight, product of:
                2.765864 = idf(docFreq=7562, maxDocs=44218)
                0.056851476 = queryNorm
              0.15279384 = fieldWeight in 4388, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                2.765864 = idf(docFreq=7562, maxDocs=44218)
                0.0390625 = fieldNorm(doc=4388)
        0.33333334 = coord(1/3)
    
    Date
    7. 8.2018 12:05:42
    Footnote
    Vgl. unter: https://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&cad=rja&uact=8&ved=2ahUKEwizweHljdbcAhVS16QKHXcFD9QQFjABegQICRAB&url=https%3A%2F%2Fwww.researchgate.net%2Fpublication%2F271200105_Die_Autonomie_des_Menschen_und_der_Maschine_-_gegenwartige_Definitionen_von_Autonomie_zwischen_philosophischem_Hintergrund_und_technologischer_Umsetzbarkeit_Redigierte_Version_der_Magisterarbeit_Karls&usg=AOvVaw06orrdJmFF2xbCCp_hL26q.
  3. Panzer, M.: Designing identifiers for the DDC (2007) 0.08
    0.07787296 = product of:
      0.15574592 = sum of:
        0.15574592 = product of:
          0.23361887 = sum of:
            0.18194832 = weight(_text_:abridged in 1752) [ClassicSimilarity], result of:
              0.18194832 = score(doc=1752,freq=4.0), product of:
                0.4697581 = queryWeight, product of:
                  8.2629 = idf(docFreq=30, maxDocs=44218)
                  0.056851476 = queryNorm
                0.38732344 = fieldWeight in 1752, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  8.2629 = idf(docFreq=30, maxDocs=44218)
                  0.0234375 = fieldNorm(doc=1752)
            0.051670548 = weight(_text_:22 in 1752) [ClassicSimilarity], result of:
              0.051670548 = score(doc=1752,freq=10.0), product of:
                0.19908418 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.056851476 = queryNorm
                0.2595412 = fieldWeight in 1752, product of:
                  3.1622777 = tf(freq=10.0), with freq of:
                    10.0 = termFreq=10.0
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.0234375 = fieldNorm(doc=1752)
          0.6666667 = coord(2/3)
      0.5 = coord(1/2)
    
    Content
    "Although the Dewey Decimal Classification is currently available on the web to subscribers as WebDewey and Abridged WebDewey in the OCLC Connexion service and in an XML version to licensees, OCLC does not provide any "web services" based on the DDC. By web services, we mean presentation of the DDC to other machines (not humans) for uses such as searching, browsing, classifying, mapping, harvesting, and alerting. In order to build web-accessible services based on the DDC, several elements have to be considered. One of these elements is the design of an appropriate Uniform Resource Identifier (URI) structure for Dewey. The design goals of mapping the entity model of the DDC into an identifier space can be summarized as follows: * Common locator for Dewey concepts and associated resources for use in web services and web applications * Use-case-driven, but not directly related to and outlasting a specific use case (persistency) * Retraceable path to a concept rather than an abstract identification, reusing a means of identification that is already present in the DDC and available in existing metadata. We have been working closely with our colleagues in the OCLC Office of Research (especially Andy Houghton as well as Eric Childress, Diane Vizine-Goetz, and Stu Weibel) on a preliminary identifier syntax. The basic identifier format we are currently exploring is: http://dewey.info/{aspect}/{object}/{locale}/{type}/{version}/{resource} where * {aspect} is the aspect associated with an {object}-the current value set of aspect contains "concept", "scheme", and "index"; additional ones are under exploration * {object} is a type of {aspect} * {locale} identifies a Dewey translation * {type} identifies a Dewey edition type and contains, at a minimum, the values "edn" for the full edition or "abr" for the abridged edition * {version} identifies a Dewey edition version * {resource} identifies a resource associated with an {object} in the context of {locale}, {type}, and {version}
    Some examples of identifiers for concepts follow: <http://dewey.info/concept/338.4/en/edn/22/> This identifier is used to retrieve or identify the 338.4 concept in the English-language version of Edition 22. <http://dewey.info/concept/338.4/de/edn/22/> This identifier is used to retrieve or identify the 338.4 concept in the German-language version of Edition 22. <http://dewey.info/concept/333.7-333.9/> This identifier is used to retrieve or identify the 333.7-333.9 concept across all editions and language versions. <http://dewey.info/concept/333.7-333.9/about.skos> This identifier is used to retrieve a SKOS representation of the 333.7-333.9 concept (using the "resource" element). There are several open issues at this preliminary stage of development: Use cases: URIs need to represent the range of statements or questions that could be submitted to a Dewey web service. Therefore, it seems that some general questions have to be answered first: What information does an agent have when coming to a Dewey web service? What kind of questions will such an agent ask? Placement of the {locale} component: It is still an open question if the {locale} component should be placed after the {version} component instead (<http://dewey.info/concept/338.4/edn/22/en>) to emphasize that the most important instantiation of a Dewey class is its edition, not its language version. From a services point of view, however, it could make more sense to keep the current arrangement, because users are more likely to come to the service with a present understanding of the language version they are seeking without knowing the specifics of a certain edition in which they are trying to find topics. Identification of other Dewey entities: The goal is to create a locator that does not answer all, but a lot of questions that could be asked about the DDC. Which entities are missing but should be surfaced for services or user agents? How will those services or agents interact with them? Should some entities be rendered in a different way as presented? For example, (how) should the DDC Summaries be retrievable? Would it be necessary to make the DDC Manual accessible through this identifier structure?"
  4. Kleineberg, M.: Context analysis and context indexing : formal pragmatics in knowledge organization (2014) 0.08
    0.07524602 = product of:
      0.15049204 = sum of:
        0.15049204 = product of:
          0.4514761 = sum of:
            0.4514761 = weight(_text_:3a in 1826) [ClassicSimilarity], result of:
              0.4514761 = score(doc=1826,freq=2.0), product of:
                0.48198745 = queryWeight, product of:
                  8.478011 = idf(docFreq=24, maxDocs=44218)
                  0.056851476 = queryNorm
                0.93669677 = fieldWeight in 1826, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  8.478011 = idf(docFreq=24, maxDocs=44218)
                  0.078125 = fieldNorm(doc=1826)
          0.33333334 = coord(1/3)
      0.5 = coord(1/2)
    
    Source
    http://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=5&ved=0CDQQFjAE&url=http%3A%2F%2Fdigbib.ubka.uni-karlsruhe.de%2Fvolltexte%2Fdocuments%2F3131107&ei=HzFWVYvGMsiNsgGTyoFI&usg=AFQjCNE2FHUeR9oQTQlNC4TPedv4Mo3DaQ&sig2=Rlzpr7a3BLZZkqZCXXN_IA&bvm=bv.93564037,d.bGg&cad=rja
  5. Faceted classification of information (o.J.) 0.08
    0.07516572 = sum of:
      0.059148498 = product of:
        0.17744549 = sum of:
          0.17744549 = weight(_text_:objects in 2653) [ClassicSimilarity], result of:
            0.17744549 = score(doc=2653,freq=2.0), product of:
              0.30216965 = queryWeight, product of:
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.056851476 = queryNorm
              0.58723795 = fieldWeight in 2653, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.078125 = fieldNorm(doc=2653)
        0.33333334 = coord(1/3)
      0.01601722 = product of:
        0.04805166 = sum of:
          0.04805166 = weight(_text_:12 in 2653) [ClassicSimilarity], result of:
            0.04805166 = score(doc=2653,freq=2.0), product of:
              0.15724345 = queryWeight, product of:
                2.765864 = idf(docFreq=7562, maxDocs=44218)
                0.056851476 = queryNorm
              0.30558768 = fieldWeight in 2653, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                2.765864 = idf(docFreq=7562, maxDocs=44218)
                0.078125 = fieldNorm(doc=2653)
        0.33333334 = coord(1/3)
    
    Abstract
    An explanation of faceted classification meant for people working in knowledge management. An example given for a high-technology company has the fundamental categories Products, Applications, Organizations, People, Domain objects ("technologies applied in the marketplace in which the organization participates"), Events (i.e. time), and Publications.
    Date
    30. 7.2004 13:12:38
  6. Understanding metadata (2004) 0.07
    0.06785904 = sum of:
      0.047318798 = product of:
        0.14195639 = sum of:
          0.14195639 = weight(_text_:objects in 2686) [ClassicSimilarity], result of:
            0.14195639 = score(doc=2686,freq=2.0), product of:
              0.30216965 = queryWeight, product of:
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.056851476 = queryNorm
              0.46979034 = fieldWeight in 2686, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.0625 = fieldNorm(doc=2686)
        0.33333334 = coord(1/3)
      0.020540241 = product of:
        0.06162072 = sum of:
          0.06162072 = weight(_text_:22 in 2686) [ClassicSimilarity], result of:
            0.06162072 = score(doc=2686,freq=2.0), product of:
              0.19908418 = queryWeight, product of:
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.056851476 = queryNorm
              0.30952093 = fieldWeight in 2686, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.0625 = fieldNorm(doc=2686)
        0.33333334 = coord(1/3)
    
    Abstract
    Metadata (structured information about an object or collection of objects) is increasingly important to libraries, archives, and museums. And although librarians are familiar with a number of issues that apply to creating and using metadata (e.g., authority control, controlled vocabularies, etc.), the world of metadata is nonetheless different than library cataloging, with its own set of challenges. Therefore, whether you are new to these concepts or quite experienced with classic cataloging, this short (20 pages) introductory paper on metadata can be helpful
    Date
    10. 9.2004 10:22:40
  7. British Library / FAST/Dewey Review Group: Consultation on subject indexing and classification standards applied by the British Library (2015) 0.06
    0.06064944 = product of:
      0.12129888 = sum of:
        0.12129888 = product of:
          0.36389664 = sum of:
            0.36389664 = weight(_text_:abridged in 2810) [ClassicSimilarity], result of:
              0.36389664 = score(doc=2810,freq=4.0), product of:
                0.4697581 = queryWeight, product of:
                  8.2629 = idf(docFreq=30, maxDocs=44218)
                  0.056851476 = queryNorm
                0.7746469 = fieldWeight in 2810, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  8.2629 = idf(docFreq=30, maxDocs=44218)
                  0.046875 = fieldNorm(doc=2810)
          0.33333334 = coord(1/3)
      0.5 = coord(1/2)
    
    Content
    The Library is consulting with stakeholders concerning the potential impact of these proposals. No firm decisions have yet been taken regarding either of these standards. FAST 1. The British Library proposes to adopt FAST selectively to extend the scope of subject indexing of current and legacy content. 2. The British Library proposes to implement FAST as a replacement for LCSH in all current cataloguing, subject to mitigation of the risks identified above, in particular the question of sustainability. DDC 3. The British Library proposes to implement Abridged DDC selectively to extend the scope of subject indexing of current and legacy content.
    Source
    http://www.bl.uk/bibliographic/pdfs/british-library-consultation-fast-abridged-dewey.pdf
  8. Popper, K.R.: Three worlds : the Tanner lecture on human values. Deliverd at the University of Michigan, April 7, 1978 (1978) 0.06
    0.060196813 = product of:
      0.12039363 = sum of:
        0.12039363 = product of:
          0.36118087 = sum of:
            0.36118087 = weight(_text_:3a in 230) [ClassicSimilarity], result of:
              0.36118087 = score(doc=230,freq=2.0), product of:
                0.48198745 = queryWeight, product of:
                  8.478011 = idf(docFreq=24, maxDocs=44218)
                  0.056851476 = queryNorm
                0.7493574 = fieldWeight in 230, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  8.478011 = idf(docFreq=24, maxDocs=44218)
                  0.0625 = fieldNorm(doc=230)
          0.33333334 = coord(1/3)
      0.5 = coord(1/2)
    
    Source
    https%3A%2F%2Ftannerlectures.utah.edu%2F_documents%2Fa-to-z%2Fp%2Fpopper80.pdf&usg=AOvVaw3f4QRTEH-OEBmoYr2J_c7H
  9. Dhillon, P.; Singh, M.: ¬An extended ontology model for trust evaluation using advanced hybrid ontology (2023) 0.06
    0.059799496 = sum of:
      0.050189164 = product of:
        0.15056749 = sum of:
          0.15056749 = weight(_text_:objects in 981) [ClassicSimilarity], result of:
            0.15056749 = score(doc=981,freq=4.0), product of:
              0.30216965 = queryWeight, product of:
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.056851476 = queryNorm
              0.49828792 = fieldWeight in 981, product of:
                2.0 = tf(freq=4.0), with freq of:
                  4.0 = termFreq=4.0
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.046875 = fieldNorm(doc=981)
        0.33333334 = coord(1/3)
      0.009610333 = product of:
        0.028830996 = sum of:
          0.028830996 = weight(_text_:12 in 981) [ClassicSimilarity], result of:
            0.028830996 = score(doc=981,freq=2.0), product of:
              0.15724345 = queryWeight, product of:
                2.765864 = idf(docFreq=7562, maxDocs=44218)
                0.056851476 = queryNorm
              0.1833526 = fieldWeight in 981, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                2.765864 = idf(docFreq=7562, maxDocs=44218)
                0.046875 = fieldNorm(doc=981)
        0.33333334 = coord(1/3)
    
    Abstract
    In the blooming area of Internet technology, the concept of Internet-of-Things (IoT) holds a distinct position that interconnects a large number of smart objects. In the context of social IoT (SIoT), the argument of trust and reliability is evaluated in the presented work. The proposed framework is divided into two blocks, namely Verification Block (VB) and Evaluation Block (EB). VB defines various ontology-based relationships computed for the objects that reflect the security and trustworthiness of an accessed service. While, EB is used for the feedback analysis and proves to be a valuable step that computes and governs the success rate of the service. Support vector machine (SVM) is applied to categorise the trust-based evaluation. The security aspect of the proposed approach is comparatively evaluated for DDoS and malware attacks in terms of success rate, trustworthiness and execution time. The proposed secure ontology-based framework provides better performance compared with existing architectures.
    Date
    6. 6.2023 12:25:46
  10. Priss, U.: Faceted knowledge representation (1999) 0.06
    0.059376657 = sum of:
      0.041403946 = product of:
        0.12421183 = sum of:
          0.12421183 = weight(_text_:objects in 2654) [ClassicSimilarity], result of:
            0.12421183 = score(doc=2654,freq=2.0), product of:
              0.30216965 = queryWeight, product of:
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.056851476 = queryNorm
              0.41106653 = fieldWeight in 2654, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.0546875 = fieldNorm(doc=2654)
        0.33333334 = coord(1/3)
      0.017972711 = product of:
        0.05391813 = sum of:
          0.05391813 = weight(_text_:22 in 2654) [ClassicSimilarity], result of:
            0.05391813 = score(doc=2654,freq=2.0), product of:
              0.19908418 = queryWeight, product of:
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.056851476 = queryNorm
              0.2708308 = fieldWeight in 2654, 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=2654)
        0.33333334 = coord(1/3)
    
    Abstract
    Faceted Knowledge Representation provides a formalism for implementing knowledge systems. The basic notions of faceted knowledge representation are "unit", "relation", "facet" and "interpretation". Units are atomic elements and can be abstract elements or refer to external objects in an application. Relations are sequences or matrices of 0 and 1's (binary matrices). Facets are relational structures that combine units and relations. Each facet represents an aspect or viewpoint of a knowledge system. Interpretations are mappings that can be used to translate between different representations. This paper introduces the basic notions of faceted knowledge representation. The formalism is applied here to an abstract modeling of a faceted thesaurus as used in information retrieval.
    Date
    22. 1.2016 17:30:31
  11. Wallis, R.; Isaac, A.; Charles, V.; Manguinhas, H.: Recommendations for the application of Schema.org to aggregated cultural heritage metadata to increase relevance and visibility to search engines : the case of Europeana (2017) 0.06
    0.059232708 = sum of:
      0.051224098 = product of:
        0.1536723 = sum of:
          0.1536723 = weight(_text_:objects in 3372) [ClassicSimilarity], result of:
            0.1536723 = score(doc=3372,freq=6.0), product of:
              0.30216965 = queryWeight, product of:
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.056851476 = queryNorm
              0.508563 = fieldWeight in 3372, product of:
                2.4494898 = tf(freq=6.0), with freq of:
                  6.0 = termFreq=6.0
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.0390625 = fieldNorm(doc=3372)
        0.33333334 = coord(1/3)
      0.00800861 = product of:
        0.02402583 = sum of:
          0.02402583 = weight(_text_:12 in 3372) [ClassicSimilarity], result of:
            0.02402583 = score(doc=3372,freq=2.0), product of:
              0.15724345 = queryWeight, product of:
                2.765864 = idf(docFreq=7562, maxDocs=44218)
                0.056851476 = queryNorm
              0.15279384 = fieldWeight in 3372, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                2.765864 = idf(docFreq=7562, maxDocs=44218)
                0.0390625 = fieldNorm(doc=3372)
        0.33333334 = coord(1/3)
    
    Abstract
    Europeana provides access to more than 54 million cultural heritage objects through its portal Europeana Collections. It is crucial for Europeana to be recognized by search engines as a trusted authoritative repository of cultural heritage objects. Indeed, even though its portal is the main entry point, most Europeana users come to it via search engines. Europeana Collections is fuelled by metadata describing cultural objects, represented in the Europeana Data Model (EDM). This paper presents the research and consequent recommendations for publishing Europeana metadata using the Schema.org vocabulary and best practices. Schema.org html embedded metadata to be consumed by search engines to power rich services (such as Google Knowledge Graph). Schema.org is an open and widely adopted initiative (used by over 12 million domains) backed by Google, Bing, Yahoo!, and Yandex, for sharing metadata across the web It underpins the emergence of new web techniques, such as so called Semantic SEO. Our research addressed the representation of the embedded metadata as part of the Europeana HTML pages and sitemaps so that the re-use of this data can be optimized. The practical objective of our work is to produce a Schema.org representation of Europeana resources described in EDM, being the richest as possible and tailored to Europeana's realities and user needs as well the search engines and their users.
  12. Godby, C.J.; Young, J.A.; Childress, E.: ¬A repository of metadata crosswalks (2004) 0.05
    0.052616 = sum of:
      0.041403946 = product of:
        0.12421183 = sum of:
          0.12421183 = weight(_text_:objects in 1155) [ClassicSimilarity], result of:
            0.12421183 = score(doc=1155,freq=2.0), product of:
              0.30216965 = queryWeight, product of:
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.056851476 = queryNorm
              0.41106653 = fieldWeight in 1155, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.0546875 = fieldNorm(doc=1155)
        0.33333334 = coord(1/3)
      0.011212054 = product of:
        0.03363616 = sum of:
          0.03363616 = weight(_text_:12 in 1155) [ClassicSimilarity], result of:
            0.03363616 = score(doc=1155,freq=2.0), product of:
              0.15724345 = queryWeight, product of:
                2.765864 = idf(docFreq=7562, maxDocs=44218)
                0.056851476 = queryNorm
              0.21391137 = fieldWeight in 1155, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                2.765864 = idf(docFreq=7562, maxDocs=44218)
                0.0546875 = fieldNorm(doc=1155)
        0.33333334 = coord(1/3)
    
    Abstract
    This paper proposes a model for metadata crosswalks that associates three pieces of information: the crosswalk, the source metadata standard, and the target metadata standard, each of which may have a machine-readable encoding and human-readable description. The crosswalks are encoded as METS records that are made available to a repository for processing by search engines, OAI harvesters, and custom-designed Web services. The METS object brings together all of the information required to access and interpret crosswalks and represents a significant improvement over previously available formats. But it raises questions about how best to describe these complex objects and exposes gaps that must eventually be filled in by the digital library community.
    Source
    D-Lib magazine. 10(2004) no.12, x S
  13. Van der Veer Martens, B.: Do citation systems represent theories of truth? (2001) 0.05
    0.05232758 = product of:
      0.10465516 = sum of:
        0.10465516 = product of:
          0.15698273 = sum of:
            0.04805166 = weight(_text_:12 in 3925) [ClassicSimilarity], result of:
              0.04805166 = score(doc=3925,freq=2.0), product of:
                0.15724345 = queryWeight, product of:
                  2.765864 = idf(docFreq=7562, maxDocs=44218)
                  0.056851476 = queryNorm
                0.30558768 = fieldWeight in 3925, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  2.765864 = idf(docFreq=7562, maxDocs=44218)
                  0.078125 = fieldNorm(doc=3925)
            0.10893107 = weight(_text_:22 in 3925) [ClassicSimilarity], result of:
              0.10893107 = score(doc=3925,freq=4.0), product of:
                0.19908418 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.056851476 = queryNorm
                0.54716086 = fieldWeight in 3925, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.078125 = fieldNorm(doc=3925)
          0.6666667 = coord(2/3)
      0.5 = coord(1/2)
    
    Date
    16. 8.2002 12:31:47
    22. 7.2006 15:22:28
  14. Mitchell, J.S.: DDC 22 : an introduction (2003) 0.05
    0.051400255 = product of:
      0.10280051 = sum of:
        0.10280051 = product of:
          0.15420076 = sum of:
            0.03363616 = weight(_text_:12 in 1936) [ClassicSimilarity], result of:
              0.03363616 = score(doc=1936,freq=2.0), product of:
                0.15724345 = queryWeight, product of:
                  2.765864 = idf(docFreq=7562, maxDocs=44218)
                  0.056851476 = queryNorm
                0.21391137 = fieldWeight in 1936, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  2.765864 = idf(docFreq=7562, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=1936)
            0.12056461 = weight(_text_:22 in 1936) [ClassicSimilarity], result of:
              0.12056461 = score(doc=1936,freq=10.0), product of:
                0.19908418 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.056851476 = queryNorm
                0.6055961 = fieldWeight in 1936, product of:
                  3.1622777 = tf(freq=10.0), with freq of:
                    10.0 = termFreq=10.0
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=1936)
          0.6666667 = coord(2/3)
      0.5 = coord(1/2)
    
    Abstract
    Dewey Decimal Classification and Relative Index, Edition 22 (DDC 22) will be issued simultaneously in print and web versions in July 2003. The new edition is the first full print update to the Dewey Decimal Classification system in seven years-it includes several significant updates and many new numbers and topics. DDC 22 also features some fundamental structural changes that have been introduced with the goals of promoting classifier efficiency and improving the DDC for use in a variety of applications in the web environment. Most importantly, the content of the new edition has been shaped by the needs and recommendations of Dewey users around the world. The worldwide user community has an important role in shaping the future of the DDC.
    Date
    26.12.2011 12:47:25
    Object
    DDC-22
  15. Bourdon, F.: Funktionale Anforderungen an bibliographische Datensätze und ein internationales Nummernsystem für Normdaten : wie weit kann Normierung durch Technik unterstützt werden? (2001) 0.05
    0.05003102 = product of:
      0.10006204 = sum of:
        0.10006204 = product of:
          0.15009306 = sum of:
            0.05766199 = weight(_text_:12 in 6888) [ClassicSimilarity], result of:
              0.05766199 = score(doc=6888,freq=2.0), product of:
                0.15724345 = queryWeight, product of:
                  2.765864 = idf(docFreq=7562, maxDocs=44218)
                  0.056851476 = queryNorm
                0.3667052 = fieldWeight in 6888, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  2.765864 = idf(docFreq=7562, maxDocs=44218)
                  0.09375 = fieldNorm(doc=6888)
            0.092431076 = weight(_text_:22 in 6888) [ClassicSimilarity], result of:
              0.092431076 = score(doc=6888,freq=2.0), product of:
                0.19908418 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.056851476 = queryNorm
                0.46428138 = fieldWeight in 6888, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.09375 = fieldNorm(doc=6888)
          0.6666667 = coord(2/3)
      0.5 = coord(1/2)
    
    Date
    26.12.2011 12:30:22
  16. Qin, J.; Paling, S.: Converting a controlled vocabulary into an ontology : the case of GEM (2001) 0.05
    0.05003102 = product of:
      0.10006204 = sum of:
        0.10006204 = product of:
          0.15009306 = sum of:
            0.05766199 = weight(_text_:12 in 3895) [ClassicSimilarity], result of:
              0.05766199 = score(doc=3895,freq=2.0), product of:
                0.15724345 = queryWeight, product of:
                  2.765864 = idf(docFreq=7562, maxDocs=44218)
                  0.056851476 = queryNorm
                0.3667052 = fieldWeight in 3895, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  2.765864 = idf(docFreq=7562, maxDocs=44218)
                  0.09375 = fieldNorm(doc=3895)
            0.092431076 = weight(_text_:22 in 3895) [ClassicSimilarity], result of:
              0.092431076 = score(doc=3895,freq=2.0), product of:
                0.19908418 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.056851476 = queryNorm
                0.46428138 = fieldWeight in 3895, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.09375 = fieldNorm(doc=3895)
          0.6666667 = coord(2/3)
      0.5 = coord(1/2)
    
    Date
    16. 8.2002 12:31:47
    24. 8.2005 19:20:22
  17. Jaeger, L.: Wissenschaftler versus Wissenschaft (2020) 0.05
    0.05003102 = product of:
      0.10006204 = sum of:
        0.10006204 = product of:
          0.15009306 = sum of:
            0.05766199 = weight(_text_:12 in 4156) [ClassicSimilarity], result of:
              0.05766199 = score(doc=4156,freq=2.0), product of:
                0.15724345 = queryWeight, product of:
                  2.765864 = idf(docFreq=7562, maxDocs=44218)
                  0.056851476 = queryNorm
                0.3667052 = fieldWeight in 4156, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  2.765864 = idf(docFreq=7562, maxDocs=44218)
                  0.09375 = fieldNorm(doc=4156)
            0.092431076 = weight(_text_:22 in 4156) [ClassicSimilarity], result of:
              0.092431076 = score(doc=4156,freq=2.0), product of:
                0.19908418 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.056851476 = queryNorm
                0.46428138 = fieldWeight in 4156, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.09375 = fieldNorm(doc=4156)
          0.6666667 = coord(2/3)
      0.5 = coord(1/2)
    
    Date
    21. 1.2018 19:12:56
    2. 3.2020 14:08:22
  18. Daniel Jr., R.; Lagoze, C.: Extending the Warwick framework : from metadata containers to active digital objects (1997) 0.05
    0.04700997 = sum of:
      0.041403946 = product of:
        0.12421183 = sum of:
          0.12421183 = weight(_text_:objects in 1264) [ClassicSimilarity], result of:
            0.12421183 = score(doc=1264,freq=8.0), product of:
              0.30216965 = queryWeight, product of:
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.056851476 = queryNorm
              0.41106653 = fieldWeight in 1264, product of:
                2.828427 = tf(freq=8.0), with freq of:
                  8.0 = termFreq=8.0
                5.315071 = idf(docFreq=590, maxDocs=44218)
                0.02734375 = fieldNorm(doc=1264)
        0.33333334 = coord(1/3)
      0.005606027 = product of:
        0.01681808 = sum of:
          0.01681808 = weight(_text_:12 in 1264) [ClassicSimilarity], result of:
            0.01681808 = score(doc=1264,freq=2.0), product of:
              0.15724345 = queryWeight, product of:
                2.765864 = idf(docFreq=7562, maxDocs=44218)
                0.056851476 = queryNorm
              0.106955685 = fieldWeight in 1264, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                2.765864 = idf(docFreq=7562, maxDocs=44218)
                0.02734375 = fieldNorm(doc=1264)
        0.33333334 = coord(1/3)
    
    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.
    Date
    26.12.2011 13:54:12
  19. Guidi, F.; Sacerdoti Coen, C.: ¬A survey on retrieval of mathematical knowledge (2015) 0.04
    0.04169252 = product of:
      0.08338504 = sum of:
        0.08338504 = product of:
          0.12507756 = sum of:
            0.04805166 = weight(_text_:12 in 5865) [ClassicSimilarity], result of:
              0.04805166 = score(doc=5865,freq=2.0), product of:
                0.15724345 = queryWeight, product of:
                  2.765864 = idf(docFreq=7562, maxDocs=44218)
                  0.056851476 = queryNorm
                0.30558768 = fieldWeight in 5865, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  2.765864 = idf(docFreq=7562, maxDocs=44218)
                  0.078125 = fieldNorm(doc=5865)
            0.0770259 = weight(_text_:22 in 5865) [ClassicSimilarity], result of:
              0.0770259 = score(doc=5865,freq=2.0), product of:
                0.19908418 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.056851476 = queryNorm
                0.38690117 = fieldWeight in 5865, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.078125 = fieldNorm(doc=5865)
          0.6666667 = coord(2/3)
      0.5 = coord(1/2)
    
    Date
    22. 2.2017 12:51:57
  20. Drewer, P.; Massion, F; Pulitano, D: Was haben Wissensmodellierung, Wissensstrukturierung, künstliche Intelligenz und Terminologie miteinander zu tun? (2017) 0.04
    0.04169252 = product of:
      0.08338504 = sum of:
        0.08338504 = product of:
          0.12507756 = sum of:
            0.04805166 = weight(_text_:12 in 5576) [ClassicSimilarity], result of:
              0.04805166 = score(doc=5576,freq=2.0), product of:
                0.15724345 = queryWeight, product of:
                  2.765864 = idf(docFreq=7562, maxDocs=44218)
                  0.056851476 = queryNorm
                0.30558768 = fieldWeight in 5576, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  2.765864 = idf(docFreq=7562, maxDocs=44218)
                  0.078125 = fieldNorm(doc=5576)
            0.0770259 = weight(_text_:22 in 5576) [ClassicSimilarity], result of:
              0.0770259 = score(doc=5576,freq=2.0), product of:
                0.19908418 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.056851476 = queryNorm
                0.38690117 = fieldWeight in 5576, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.078125 = fieldNorm(doc=5576)
          0.6666667 = coord(2/3)
      0.5 = coord(1/2)
    
    Date
    13.12.2017 14:17:22
    23.12.2022 12:07:17

Years

Languages

  • e 368
  • d 288
  • m 4
  • a 3
  • el 2
  • f 1
  • i 1
  • nl 1
  • More… Less…

Types

  • a 323
  • i 27
  • m 13
  • r 12
  • n 11
  • s 9
  • x 7
  • b 4
  • p 3
  • More… Less…

Themes