Search (8 results, page 1 of 1)

  • × author_ss:"Schreiber, G."
  1. Wielinga, B.; Wielemaker, J.; Schreiber, G.; Assem, M. van: Methods for porting resources to the Semantic Web (2004) 0.04
    0.04454048 = product of:
      0.06681072 = sum of:
        0.054823436 = weight(_text_:development in 4640) [ClassicSimilarity], result of:
          0.054823436 = score(doc=4640,freq=4.0), product of:
            0.16011542 = queryWeight, product of:
              3.652261 = idf(docFreq=3116, maxDocs=44218)
              0.04384008 = queryNorm
            0.34239948 = fieldWeight in 4640, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.652261 = idf(docFreq=3116, maxDocs=44218)
              0.046875 = fieldNorm(doc=4640)
        0.011987286 = product of:
          0.035961855 = sum of:
            0.035961855 = weight(_text_:29 in 4640) [ClassicSimilarity], result of:
              0.035961855 = score(doc=4640,freq=2.0), product of:
                0.1542157 = queryWeight, product of:
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.04384008 = queryNorm
                0.23319192 = fieldWeight in 4640, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.046875 = fieldNorm(doc=4640)
          0.33333334 = coord(1/3)
      0.6666667 = coord(2/3)
    
    Abstract
    Ontologies will play a central role in the development of the Semantic Web. It is unrealistic to assume that such ontologies will be developed from scratch. Rather, we assume that existing resources such as thesauri and lexical data bases will be reused in the development of ontologies for the Semantic Web. In this paper we describe a method for converting existing source material to a representation that is compatible with Semantic Web languages such as RDF(S) and OWL. The method is illustrated with three case studies: converting Wordnet, AAT and MeSH to RDF(S) and OWL.
    Date
    29. 7.2011 14:44:56
  2. Assem, M. van; Malaisé, V.; Miles, A.; Schreiber, G.: ¬A method to convert thesauri to SKOS (2006) 0.03
    0.03383554 = product of:
      0.05075331 = sum of:
        0.038766023 = weight(_text_:development in 4642) [ClassicSimilarity], result of:
          0.038766023 = score(doc=4642,freq=2.0), product of:
            0.16011542 = queryWeight, product of:
              3.652261 = idf(docFreq=3116, maxDocs=44218)
              0.04384008 = queryNorm
            0.242113 = fieldWeight in 4642, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.652261 = idf(docFreq=3116, maxDocs=44218)
              0.046875 = fieldNorm(doc=4642)
        0.011987286 = product of:
          0.035961855 = sum of:
            0.035961855 = weight(_text_:29 in 4642) [ClassicSimilarity], result of:
              0.035961855 = score(doc=4642,freq=2.0), product of:
                0.1542157 = queryWeight, product of:
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.04384008 = queryNorm
                0.23319192 = fieldWeight in 4642, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.046875 = fieldNorm(doc=4642)
          0.33333334 = coord(1/3)
      0.6666667 = coord(2/3)
    
    Abstract
    Thesauri can be useful resources for indexing and retrieval on the Semantic Web, but often they are not published in RDF/OWL. To convert thesauri to RDF for use in Semantic Web applications and to ensure the quality and utility of the conversion a structured method is required. Moreover, if different thesauri are to be interoperable without complicated mappings, a standard schema for thesauri is required. This paper presents a method for conversion of thesauri to the SKOS RDF/OWL schema, which is a proposal for such a standard under development by W3Cs Semantic Web Best Practices Working Group. We apply the method to three thesauri: IPSV, GTAA and MeSH. With these case studies we evaluate our method and the applicability of SKOS for representing thesauri.
    Date
    29. 7.2011 14:44:56
  3. Speel, P.-H.; Schreiber, G.; Van Joolingen, W.; Van Heijst, G.; Beijer, G.: Conceptual modeling for knowledge-based systems (2002) 0.02
    0.019262992 = product of:
      0.057788976 = sum of:
        0.057788976 = weight(_text_:development in 4254) [ClassicSimilarity], result of:
          0.057788976 = score(doc=4254,freq=10.0), product of:
            0.16011542 = queryWeight, product of:
              3.652261 = idf(docFreq=3116, maxDocs=44218)
              0.04384008 = queryNorm
            0.36092073 = fieldWeight in 4254, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              3.652261 = idf(docFreq=3116, maxDocs=44218)
              0.03125 = fieldNorm(doc=4254)
      0.33333334 = coord(1/3)
    
    Abstract
    In this article, we presented knowledge-based system (KBS) development as a specific way of software engineering. What makes conceptual modeling for KBSs unique? STRENGTHS Knowledge-based system development is a very complex process. The approach in this article to clearly separate conceptual modeling from software implementation, which makes the process of KBS development feasible and manageable in a business environment. In addition, the knowledge model resulting from conceptual modeling is a deliverable in itself. For example, in knowledge management, knowledge mapping is a popular area in which graphical, high-level, business-focused knowledge models are delivered. Another strength is the ease of maintenance. Separating models and program code makes the process of updating more flexible. Last but not least, methodological approaches to KBS development have been matured, which provide a professional basis. Knowledge engineers start working in a similar way, and as a result exchange of work is possible and project planning is better manageable. WEAKNESSES The separation of conceptual modeling and KBS software implementation will take more time initially. However, reuse of models and code may speed up the separate processes considerably. In addition, the separate phases need different expertise; knowledge engineers with specific analytical skills should be assigned to conceptual modeling, whereas software engineers with specific programming skills should be assigned to software implementation. Finally, the various methodological approaches lack mature support tools. OPPORTUNITIES Reuse of various knowledge models as well as program code may bring several advantages, in improved quality of the KBSs as well as in speed to market. Separate development of conceptual vocabularies (also called dictionaries or ontologies), corporate memories, and generic domain models in an explicit form may form the basis of effective management of business-critical knowledge domains, which leads to sustainable competitive advantage.
  4. Assem, M. van; Menken, M.R.; Schreiber, G.; Wielemaker, J.; Wielinga, B.: ¬A method for converting thesauri to RDF/OWL (2004) 0.00
    0.0046617216 = product of:
      0.013985164 = sum of:
        0.013985164 = product of:
          0.041955493 = sum of:
            0.041955493 = weight(_text_:29 in 4644) [ClassicSimilarity], result of:
              0.041955493 = score(doc=4644,freq=2.0), product of:
                0.1542157 = queryWeight, product of:
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.04384008 = queryNorm
                0.27205724 = fieldWeight in 4644, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=4644)
          0.33333334 = coord(1/3)
      0.33333334 = coord(1/3)
    
    Date
    29. 7.2011 14:44:56
  5. Assem, M. van; Gangemi, A.; Schreiber, G.: Conversion of WordNet to a standard RDF/OWL representation (2006) 0.00
    0.003995762 = product of:
      0.011987286 = sum of:
        0.011987286 = product of:
          0.035961855 = sum of:
            0.035961855 = weight(_text_:29 in 4641) [ClassicSimilarity], result of:
              0.035961855 = score(doc=4641,freq=2.0), product of:
                0.1542157 = queryWeight, product of:
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.04384008 = queryNorm
                0.23319192 = fieldWeight in 4641, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.046875 = fieldNorm(doc=4641)
          0.33333334 = coord(1/3)
      0.33333334 = coord(1/3)
    
    Date
    29. 7.2011 14:44:56
  6. Hollink, L.; Assem, M. van; Wang, S.; Isaac, A.; Schreiber, G.: Two variations on ontology alignment evaluation : methodological issues (2008) 0.00
    0.003995762 = product of:
      0.011987286 = sum of:
        0.011987286 = product of:
          0.035961855 = sum of:
            0.035961855 = weight(_text_:29 in 4645) [ClassicSimilarity], result of:
              0.035961855 = score(doc=4645,freq=2.0), product of:
                0.1542157 = queryWeight, product of:
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.04384008 = queryNorm
                0.23319192 = fieldWeight in 4645, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.046875 = fieldNorm(doc=4645)
          0.33333334 = coord(1/3)
      0.33333334 = coord(1/3)
    
    Date
    29. 7.2011 14:44:56
  7. Schreiber, G.; Amin, A.; Assem, M. van; Boer, V. de; Hardman, L.; Hildebrand, M.; Omelayenko, B.; Ossenbruggen, J. van; Wielemaker, J.; Wielinga, B.; Tordai, A.; Aroyoa, L.: Semantic annotation and search of cultural-heritage collections : the MultimediaN E-Culture demonstrator (2008) 0.00
    0.003995762 = product of:
      0.011987286 = sum of:
        0.011987286 = product of:
          0.035961855 = sum of:
            0.035961855 = weight(_text_:29 in 4646) [ClassicSimilarity], result of:
              0.035961855 = score(doc=4646,freq=2.0), product of:
                0.1542157 = queryWeight, product of:
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.04384008 = queryNorm
                0.23319192 = fieldWeight in 4646, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.046875 = fieldNorm(doc=4646)
          0.33333334 = coord(1/3)
      0.33333334 = coord(1/3)
    
    Date
    29. 7.2011 14:44:56
  8. Schreiber, G.; Amin, A.; Assem, M. van; Boer, V. de; Hardman, L.; Hildebrand, M.; Hollink, L.; Huang, Z.; Kersen, J. van; Niet, M. de; Omelayenko, B.; Ossenbruggen, J. van; Siebes, R.; Taekema, J.; Wielemaker, J.; Wielinga, B.: MultimediaN E-Culture demonstrator (2006) 0.00
    0.003995762 = product of:
      0.011987286 = sum of:
        0.011987286 = product of:
          0.035961855 = sum of:
            0.035961855 = weight(_text_:29 in 4648) [ClassicSimilarity], result of:
              0.035961855 = score(doc=4648,freq=2.0), product of:
                0.1542157 = queryWeight, product of:
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.04384008 = queryNorm
                0.23319192 = fieldWeight in 4648, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.046875 = fieldNorm(doc=4648)
          0.33333334 = coord(1/3)
      0.33333334 = coord(1/3)
    
    Date
    29. 7.2011 14:44:56