Search (6 results, page 1 of 1)

0.049510285 = product of:
  0.09902057 = sum of:
    0.09902057 = sum of:
      0.07156913 = weight(_text_:class in 1236) [ClassicSimilarity], result of:
        0.07156913 = score(doc=1236,freq=2.0), product of:
          0.28640816 = queryWeight, product of:
            5.6542544 = idf(docFreq=420, maxDocs=44218)
            0.05065357 = queryNorm
          0.2498851 = fieldWeight in 1236, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            5.6542544 = idf(docFreq=420, maxDocs=44218)
            0.03125 = fieldNorm(doc=1236)
      0.027451439 = weight(_text_:22 in 1236) [ClassicSimilarity], result of:
        0.027451439 = score(doc=1236,freq=2.0), product of:
          0.17738017 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.05065357 = queryNorm
          0.15476047 = fieldWeight in 1236, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.03125 = fieldNorm(doc=1236)
  0.5 = coord(1/2)

Abstract

Dublin Core is often presented as a modern form of catalog card -- a set of elements (and now qualifiers) that describe resources in a complete package. Sometimes it is proposed as an exchange format for sharing records among multiple collections. The founding principle that "every element is optional and repeatable" reinforces the notion that a Dublin Core description is to be taken as a whole. This paper, in contrast, is based on a much different premise: Dublin Core is a language. More precisely, it is a small language for making a particular class of statements about resources. Like natural languages, it has a vocabulary of word-like terms, the two classes of which -- elements and qualifiers -- function within statements like nouns and adjectives; and it has a syntax for arranging elements and qualifiers into statements according to a simple pattern. Whenever tourists order a meal or ask directions in an unfamiliar language, considerate native speakers will spontaneously limit themselves to basic words and simple sentence patterns along the lines of "I am so-and-so" or "This is such-and-such". Linguists call this pidginization. In such situations, a small phrase book or translated menu can be most helpful. By analogy, today's Web has been called an Internet Commons where users and information providers from a wide range of scientific, commercial, and social domains present their information in a variety of incompatible data models and description languages. In this context, Dublin Core presents itself as a metadata pidgin for digital tourists who must find their way in this linguistically diverse landscape. Its vocabulary is small enough to learn quickly, and its basic pattern is easily grasped. It is well-suited to serve as an auxiliary language for digital libraries. This grammar starts by defining terms. It then follows a 200-year-old tradition of English grammar teaching by focusing on the structure of single statements. It concludes by looking at the growing dictionary of Dublin Core vocabulary terms -- its registry, and at how statements can be used to build the metadata equivalent of paragraphs and compositions -- the application profile.

Date

26.12.2011 14:01:22

0.031311493 = product of:
  0.06262299 = sum of:
    0.06262299 = product of:
      0.12524597 = sum of:
        0.12524597 = weight(_text_:class in 5896) [ClassicSimilarity], result of:
          0.12524597 = score(doc=5896,freq=2.0), product of:
            0.28640816 = queryWeight, product of:
              5.6542544 = idf(docFreq=420, maxDocs=44218)
              0.05065357 = queryNorm
            0.43729892 = fieldWeight in 5896, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.6542544 = idf(docFreq=420, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5896)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

This paper proposes the use of the Unified Modeling Language (UML) as a language for modelling ontologies for Web resources and the knowledge contained within them. To provide a mechanism for serialising and processing object diagrams representing knowledge, a pair of XSI-T stylesheets have been developed to map from XML Metadata Interchange (XMI) encodings of class diagrams to corresponding RDF schemas and to Java classes representing the concepts in the ontologies. The Java code includes methods for marshalling and unmarshalling object-oriented information between in-memory data structures and RDF serialisations of that information. This provides a convenient mechanism for Java applications to share knowledge on the Web

0.020588579 = product of:
  0.041177157 = sum of:
    0.041177157 = product of:
      0.082354315 = sum of:
        0.082354315 = weight(_text_:22 in 6048) [ClassicSimilarity], result of:
          0.082354315 = score(doc=6048,freq=2.0), product of:
            0.17738017 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05065357 = queryNorm
            0.46428138 = fieldWeight in 6048, 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=6048)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 9.2007 15:41:14

0.013725719 = product of:
  0.027451439 = sum of:
    0.027451439 = product of:
      0.054902878 = sum of:
        0.054902878 = weight(_text_:22 in 2686) [ClassicSimilarity], result of:
          0.054902878 = score(doc=2686,freq=2.0), product of:
            0.17738017 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05065357 = 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.5 = coord(1/2)
  0.5 = coord(1/2)

Date

10. 9.2004 10:22:40

0.010294289 = product of:
  0.020588579 = sum of:
    0.020588579 = product of:
      0.041177157 = sum of:
        0.041177157 = weight(_text_:22 in 266) [ClassicSimilarity], result of:
          0.041177157 = score(doc=266,freq=2.0), product of:
            0.17738017 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05065357 = queryNorm
            0.23214069 = fieldWeight in 266, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046875 = fieldNorm(doc=266)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 5.2021 12:43:05

0.008578574 = product of:
  0.017157149 = sum of:
    0.017157149 = product of:
      0.034314297 = sum of:
        0.034314297 = weight(_text_:22 in 4550) [ClassicSimilarity], result of:
          0.034314297 = score(doc=4550,freq=2.0), product of:
            0.17738017 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05065357 = queryNorm
            0.19345059 = fieldWeight in 4550, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0390625 = fieldNorm(doc=4550)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

10.11.2018 16:27:22