Search (15 results, page 1 of 1)

0.03873793 = product of:
  0.07747586 = sum of:
    0.07747586 = product of:
      0.15495172 = sum of:
        0.15495172 = weight(_text_:class in 3370) [ClassicSimilarity], result of:
          0.15495172 = score(doc=3370,freq=24.0), product of:
            0.28640816 = queryWeight, product of:
              5.6542544 = idf(docFreq=420, maxDocs=44218)
              0.05065357 = queryNorm
            0.5410171 = fieldWeight in 3370, product of:
              4.8989797 = tf(freq=24.0), with freq of:
                24.0 = termFreq=24.0
              5.6542544 = idf(docFreq=420, maxDocs=44218)
              0.01953125 = fieldNorm(doc=3370)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Content

"Last week, I received an email from Yulia Skora in Ukraine who is working on the mapping between UDC Summary and BBK (Bibliographic Library Classification) Summary. It reminded me of yet another challenging area of work. When responding to Yulia I realised that the issues with mapping, for instance, UDC Summary to Dewey Summaries [pdf] are often made more difficult because we have to deal with classification summaries in both systems and we cannot use a known exactMatch in many situations. In 2008, following advice received from colleagues in the HILT project, two of our colleagues quickly mapped 1000 classes of Dewey Summaries to UDC Master Reference File as a whole. This appeared to be relatively simple. The mapping in this case is simply an answer to a question "and how would you say e.g. Art metal work in UDC?" But when in 2009 we realised that we were going to release 2000 classes of UDC Summary as linked data, we decided to wait until we had our UDC Summary set defined and completed to be able to publish it mapped to the Dewey Summaries. As we arrived at this stage, little did we realise how much more complex the reversed mapping of UDC Summary to Dewey Summaries would turn out to be. Mapping the Dewey Summaries to UDC highlighted situations in which the logic and structure of two systems do not agree. Especially because Dewey tends to enumerate combinations of subject and attributes that do not always logically belong together. For instance, 850 Literatures of Italian, Sardinian, Dalmatian, Romanian, Rhaeto-Romanic languages Italian literature. This class mixes languages from three different subgroups of Romance languages. Italian and Sardinian belong to Italo Romance sub-family; Romanian and Dalmatian are Balkan Romance languages and Rhaeto Romance is the third subgroup that includes Friulian Ladin and Romanch. As UDC literature is based on a strict classification of language families, Dewey class 850 has to be mapped to 3 narrower UDC classes 821.131 Literature of Italo-Romance Languages , 821.132 Literature of Rhaeto-Romance languages and 821.135 Literature of Balkan-Romance Languages, or to a broader class 821.13 Literature of Romance languages. Hence we have to be sure that we have all these classes listed in the UDC Summary to be able to express UDC-DDC many-to-one, specific-to-broader relationships.
Another challenge appears when, e.g., mapping Dewey class 890 Literatures of other specific languages and language families, which does not make sense in UDC in which all languages and literatures have equal status. Standard UDC schedules do not have a selection of preferred literatures and other literatures. In principle, UDC does not allow classes entitled 'others' which do not have defined semantic content. If entities are subdivided and there is no provision for an item outside the listed subclasses then this item is subsumed to a top class or a broader class where all unspecifiied or general members of that class may be expected. If specification is needed this can be divised by adding an alphabetical extension to the broader class. Here we have to find and list in the UDC Summary all literatures that are 'unpreferred' i.e. lumped in the 890 classes and map them again as many-to-one specific-to-broader match. The example below illustrates another interesting case. Classes Dewey 061 and UDC 06 cover roughy the same semantic field but in the subdivision the Dewey Summaries lists a combination of subject and place and as an enumerative classification, provides ready made numbers for combinations of place that are most common in an average (American?) library. This is a frequent approach in the schemes created with the physical book arrangement, i.e. library schelves, in mind. UDC, designed as an indexing language for information retrieval, keeps subject and place in separate tables and allows for any concept of place such as, e.g. (7) North America to be used in combination with any subject as these may coincide in documents. Thus combinations such as Newspapers in North America, or Organizations in North America would not be offered as ready made combinations. There is no selection of 'preferred' or 'most needed countries' or languages or cultures in the standard UDC edition: <Tabelle>
If we map the Dewey Summaries to UDC in general and do not have to worry about a reverse relationship the situation is very simple as shown above. Mapping of UDC Summary to Dewey Summaries requires more thought. Firstly, UDC class (7) North America (common auxiliary of place) which simply represents the place has to be mapped to all occurences in which this place is 'built in' to the Dewey subjects: 063 Organization of North America 073 Journalism of North America 917 Geography of North America 970 History of North America 277 Christianity in North America 317 General Statistics in North America 557 Earth Sciences of North America The type of mapping from what is a general UDC concept of place (7) North America to a specific subject is clearly a broader-to-narrow match. Mapping of, for instance , UDC class 07 Newspapers. The press (includes journalism) to DDC class of 073 Journalim of North America is again broad-to-narrow match.
Precombined subjects, such as those shown above from Dewey, may be expressed in UDC Summary as examples of combination within various records. To express an exact match UDC class 07 has to contain example of combination 07(7) Journals. The Press - North America. In some cases we have, therefore, added examples to UDC Summary that represent exact match to Dewey Summaries. It is unfortunate that DDC has so many classes on the top level that deal with a selection of countries or languages that are given a preferred status in the scheme, and repeating these preferences in examples of combinations of UDC emulates an unwelcome cultural bias which we have to balance out somehow. This brings us to another challenge.. UDC 913(7) Regional Geography - North America [contains 2 concepts each of which has its URI] is an exact match to Dewey 917 [represented as one concept, 1 URI]. It seems that, because they represent an exact match to Dewey numbers, these UDC examples of combinations may also need a separate URIs so that they can be published as SKOS data. Albeit challenging, mapping proves to be a very useful exercise and I am looking forward to future work here especially in relation to our plans to map UDC Summary to Colon Classification. We are discussing this project with colleagues from DRTC in Bangalore (India)."

0.031311493 = product of:
  0.06262299 = sum of:
    0.06262299 = product of:
      0.12524597 = sum of:
        0.12524597 = weight(_text_:class in 1574) [ClassicSimilarity], result of:
          0.12524597 = score(doc=1574,freq=2.0), product of:
            0.28640816 = queryWeight, product of:
              5.6542544 = idf(docFreq=420, maxDocs=44218)
              0.05065357 = queryNorm
            0.43729892 = fieldWeight in 1574, 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=1574)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

This paper describes an approach to SKOS vocabulary mapping that takes into account the context in which vocabulary terms are used in annotations. The standard vocabulary mapping properties in SKOS only allow for binary mappings between concepts. In the BestMap ontology, annotated resources are the contexts in which annotations coincide and allow for a more fine grained control over when mappings hold. A mapping between two vocabularies is defined as a class that groups descriptions of a resource. We use the OWL 2 features for property chains, disjoint properties, union, intersection and negation together with careful use of equivalence and subsumption to specify these mappings.

0.024020009 = product of:
  0.048040017 = sum of:
    0.048040017 = product of:
      0.096080035 = sum of:
        0.096080035 = weight(_text_:22 in 8365) [ClassicSimilarity], result of:
          0.096080035 = score(doc=8365,freq=2.0), product of:
            0.17738017 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05065357 = queryNorm
            0.5416616 = fieldWeight in 8365, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.109375 = fieldNorm(doc=8365)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 6.2015 16:08:38

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

Content

Vortrag anlässlich des Workshops: "Extending the multilingual capacity of The European Library in the EDL project Stockholm, Swedish National Library, 22-23 November 2007".

0.01897763 = product of:
  0.03795526 = sum of:
    0.03795526 = product of:
      0.07591052 = sum of:
        0.07591052 = weight(_text_:class in 2127) [ClassicSimilarity], result of:
          0.07591052 = score(doc=2127,freq=4.0), product of:
            0.28640816 = queryWeight, product of:
              5.6542544 = idf(docFreq=420, maxDocs=44218)
              0.05065357 = queryNorm
            0.26504317 = fieldWeight in 2127, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              5.6542544 = idf(docFreq=420, maxDocs=44218)
              0.0234375 = fieldNorm(doc=2127)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Content

What are those "other" relationships that Dewey possesses and that seem so important to surface? Firstly, there is the relationship of concepts to resources. Dewey has been used for a long time, and over 200,000 numbers are assigned to information resources each year and added to WorldCat by the Library of Congress and the German National Library alone. Secondly, we have relationships between concepts in the scheme itself. Dewey provides a rich set of non-hierarchical relations, indicating other relevant and related subjects across disciplinary boundaries. Thirdly, perhaps most importantly, there is the relationship between the same concepts across different languages. Dewey has been translated extensively, and current versions are available in French, German, Hebrew, Italian, Spanish, and Vietnamese. Briefer representations of the top-three levels (the DDC Summaries) are available in several languages in the DeweyBrowser. This multilingual nature of the scheme allows searchers to access a broader range of resources or to switch the language of--and thus localize--subject metadata seamlessly. MelvilClass, a Dewey front-end developed by the German National Library for the German translation, could be used as a common interface to the DDC in any language, as it is built upon the standard DDC data format. It is not hard to give an example of the basic terminology of a class pulled together in a multilingual way: <class/794.8> a skos:Concept ; skos:notation "794.8"^^ddc:notation ; skos:prefLabel "Computer games"@en ; skos:prefLabel "Computerspiele"@de ; skos:prefLabel "Jeux sur ordinateur"@fr ; skos:prefLabel "Juegos por computador"@es .

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

Content

Vortrag anlässlich des Workshops: "Extending the multilingual capacity of The European Library in the EDL project Stockholm, Swedish National Library, 22-23 November 2007".

0.014558325 = product of:
  0.02911665 = sum of:
    0.02911665 = product of:
      0.0582333 = sum of:
        0.0582333 = weight(_text_:22 in 1967) [ClassicSimilarity], result of:
          0.0582333 = score(doc=1967,freq=4.0), product of:
            0.17738017 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05065357 = queryNorm
            0.32829654 = fieldWeight in 1967, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046875 = fieldNorm(doc=1967)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

This paper reports on the second part of an initiative of the authors on researching classification systems with the conceptual model defined by the Functional Requirements for Subject Authority Data (FRSAD) final report. In an earlier study, the authors explored whether the FRSAD conceptual model could be extended beyond subject authority data to model classification data. The focus of the current study is to determine if classification data modeled using FRSAD can be used to solve real-world discovery problems in multicultural and multilingual contexts. The paper discusses the relationships between entities (same type or different types) in the context of classification systems that involve multiple translations and /or multicultural implementations. Results of two case studies are presented in detail: (a) two instances of the DDC (DDC 22 in English, and the Swedish-English mixed translation of DDC 22), and (b) Chinese Library Classification. The use cases of conceptual models in practice are also discussed.

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

Date

7.11.2008 10:40:22

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

Date

26.12.2011 13:22:46

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

Date

7.11.2008 10:40:22

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

Date

26.12.2011 13:22:27

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

Date

11. 5.2013 19:22:18

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

Date

22. 1.2011 10:16:32

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

Date

3.12.2016 18:39:22

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

Content

This paper is a pre-print version presented at the ISKO UK 2009 conference, 22-23 June, prior to peer review and editing. For published proceedings see special issue of Aslib Proceedings journal.