-
Panzer, M.: Dewey: how to make it work for you (2013)
0.07
0.07427103 = product of:
0.12378505 = sum of:
0.044850416 = weight(_text_:index in 5797) [ClassicSimilarity], result of:
0.044850416 = score(doc=5797,freq=2.0), product of:
0.18579477 = queryWeight, product of:
4.369764 = idf(docFreq=1520, maxDocs=44218)
0.04251826 = queryNorm
0.24139762 = fieldWeight in 5797, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
4.369764 = idf(docFreq=1520, maxDocs=44218)
0.0390625 = fieldNorm(doc=5797)
0.04035608 = weight(_text_:system in 5797) [ClassicSimilarity], result of:
0.04035608 = score(doc=5797,freq=6.0), product of:
0.13391352 = queryWeight, product of:
3.1495528 = idf(docFreq=5152, maxDocs=44218)
0.04251826 = queryNorm
0.30135927 = fieldWeight in 5797, product of:
2.4494898 = tf(freq=6.0), with freq of:
6.0 = termFreq=6.0
3.1495528 = idf(docFreq=5152, maxDocs=44218)
0.0390625 = fieldNorm(doc=5797)
0.038578555 = product of:
0.057867832 = sum of:
0.029064644 = weight(_text_:29 in 5797) [ClassicSimilarity], result of:
0.029064644 = score(doc=5797,freq=2.0), product of:
0.14956595 = queryWeight, product of:
3.5176873 = idf(docFreq=3565, maxDocs=44218)
0.04251826 = queryNorm
0.19432661 = fieldWeight in 5797, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5176873 = idf(docFreq=3565, maxDocs=44218)
0.0390625 = fieldNorm(doc=5797)
0.028803186 = weight(_text_:22 in 5797) [ClassicSimilarity], result of:
0.028803186 = score(doc=5797,freq=2.0), product of:
0.1488917 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.04251826 = queryNorm
0.19345059 = fieldWeight in 5797, 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=5797)
0.6666667 = coord(2/3)
0.6 = coord(3/5)
- Abstract
- The article discusses various aspects of the Dewey Decimal Classification (DDC) system of classifying library books in 2013. Background is presented on some librarians' desire to stop using DDC and adopt a genre-based system of classification. It says librarians can use the DDC to deal with problems and issues related to library book classification. It highlights the benefits of using captions and relative index terms and semantic relationships in DDC.
- Content
- "As knowledge brokers, we are living in interesting times for libraries and librarians. We wonder sometimes if our traditional tools like the Dewey Decimal Classification (DDC) system can cope with the onslaught of information. The categories provided don't always seem adequate for the knowledge-discovery habits of today's patrons. They have grown accustomed to new ways for their information needs to be met, from the fire-and-forget style of a hard-to-control classic Google search to the pervasive, always-on style of Google Now, anticipating users' information needs without their having even asked a verbal question. Contrariwise, I believe that we, as librarians, could be making better use of our tools. Many (like the DDC) are a reflection of the same social and epistemological forces that brought about modernity at the turn of the last century. We as librarians are in the unique position of providing services that are as ground-breaking as these tools. As we see the need to provide unique and cutting-edge knowledge discovery to our users, I argue in this article that the DDC can play a key role in fulfilling this purpose."
- Source
- Knowledge quest. 42(2013) no.2, S.22-29
-
Panzer, M.: Designing identifiers for the DDC (2007)
0.05
0.0531045 = product of:
0.088507496 = sum of:
0.024209036 = weight(_text_:context in 1752) [ClassicSimilarity], result of:
0.024209036 = score(doc=1752,freq=2.0), product of:
0.17622331 = queryWeight, product of:
4.14465 = idf(docFreq=1904, maxDocs=44218)
0.04251826 = queryNorm
0.13737704 = fieldWeight in 1752, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
4.14465 = idf(docFreq=1904, maxDocs=44218)
0.0234375 = fieldNorm(doc=1752)
0.02691025 = weight(_text_:index in 1752) [ClassicSimilarity], result of:
0.02691025 = score(doc=1752,freq=2.0), product of:
0.18579477 = queryWeight, product of:
4.369764 = idf(docFreq=1520, maxDocs=44218)
0.04251826 = queryNorm
0.14483857 = fieldWeight in 1752, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
4.369764 = idf(docFreq=1520, maxDocs=44218)
0.0234375 = fieldNorm(doc=1752)
0.037388213 = product of:
0.056082316 = sum of:
0.017438786 = weight(_text_:29 in 1752) [ClassicSimilarity], result of:
0.017438786 = score(doc=1752,freq=2.0), product of:
0.14956595 = queryWeight, product of:
3.5176873 = idf(docFreq=3565, maxDocs=44218)
0.04251826 = queryNorm
0.11659596 = fieldWeight in 1752, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5176873 = idf(docFreq=3565, maxDocs=44218)
0.0234375 = fieldNorm(doc=1752)
0.03864353 = weight(_text_:22 in 1752) [ClassicSimilarity], result of:
0.03864353 = score(doc=1752,freq=10.0), product of:
0.1488917 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.04251826 = 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.6 = coord(3/5)
- 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?"
- Date
- 21. 3.2008 19:29:28
-
Green, R.; Panzer, M.: ¬The ontological character of classes in the Dewey Decimal Classification
0.04
0.04356857 = product of:
0.10892142 = sum of:
0.06279058 = weight(_text_:index in 3530) [ClassicSimilarity], result of:
0.06279058 = score(doc=3530,freq=2.0), product of:
0.18579477 = queryWeight, product of:
4.369764 = idf(docFreq=1520, maxDocs=44218)
0.04251826 = queryNorm
0.33795667 = fieldWeight in 3530, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
4.369764 = idf(docFreq=1520, maxDocs=44218)
0.0546875 = fieldNorm(doc=3530)
0.04613084 = weight(_text_:system in 3530) [ClassicSimilarity], result of:
0.04613084 = score(doc=3530,freq=4.0), product of:
0.13391352 = queryWeight, product of:
3.1495528 = idf(docFreq=5152, maxDocs=44218)
0.04251826 = queryNorm
0.34448233 = fieldWeight in 3530, product of:
2.0 = tf(freq=4.0), with freq of:
4.0 = termFreq=4.0
3.1495528 = idf(docFreq=5152, maxDocs=44218)
0.0546875 = fieldNorm(doc=3530)
0.4 = coord(2/5)
- Abstract
- Classes in the Dewey Decimal Classification (DDC) system function as neighborhoods around focal topics in captions and notes. Topical neighborhoods are generated through specialization and instantiation, complex topic synthesis, index terms and mapped headings, hierarchical force, rules for choosing between numbers, development of the DDC over time, and use of the system in classifying resources. Implications of representation using a formal knowledge representation language are explored.
-
Panzer, M.: Cool URIs for the DDC : towards Web-scale accessibility of a large classification system (2008)
0.02
0.02105642 = product of:
0.05264105 = sum of:
0.03727935 = weight(_text_:system in 2629) [ClassicSimilarity], result of:
0.03727935 = score(doc=2629,freq=2.0), product of:
0.13391352 = queryWeight, product of:
3.1495528 = idf(docFreq=5152, maxDocs=44218)
0.04251826 = queryNorm
0.27838376 = fieldWeight in 2629, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.1495528 = idf(docFreq=5152, maxDocs=44218)
0.0625 = fieldNorm(doc=2629)
0.015361699 = product of:
0.046085097 = sum of:
0.046085097 = weight(_text_:22 in 2629) [ClassicSimilarity], result of:
0.046085097 = score(doc=2629,freq=2.0), product of:
0.1488917 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.04251826 = queryNorm
0.30952093 = fieldWeight in 2629, 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=2629)
0.33333334 = coord(1/3)
0.4 = coord(2/5)
- Source
- Metadata for semantic and social applications : proceedings of the International Conference on Dublin Core and Metadata Applications, Berlin, 22 - 26 September 2008, DC 2008: Berlin, Germany / ed. by Jane Greenberg and Wolfgang Klas
-
Green, R.; Panzer, M.: Relations in the notational hierarchy of the Dewey Decimal Classification (2011)
0.02
0.017055526 = product of:
0.042638816 = sum of:
0.032950602 = weight(_text_:system in 4823) [ClassicSimilarity], result of:
0.032950602 = score(doc=4823,freq=4.0), product of:
0.13391352 = queryWeight, product of:
3.1495528 = idf(docFreq=5152, maxDocs=44218)
0.04251826 = queryNorm
0.24605882 = fieldWeight in 4823, product of:
2.0 = tf(freq=4.0), with freq of:
4.0 = termFreq=4.0
3.1495528 = idf(docFreq=5152, maxDocs=44218)
0.0390625 = fieldNorm(doc=4823)
0.009688215 = product of:
0.029064644 = sum of:
0.029064644 = weight(_text_:29 in 4823) [ClassicSimilarity], result of:
0.029064644 = score(doc=4823,freq=2.0), product of:
0.14956595 = queryWeight, product of:
3.5176873 = idf(docFreq=3565, maxDocs=44218)
0.04251826 = queryNorm
0.19432661 = fieldWeight in 4823, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5176873 = idf(docFreq=3565, maxDocs=44218)
0.0390625 = fieldNorm(doc=4823)
0.33333334 = coord(1/3)
0.4 = coord(2/5)
- Abstract
- As part of a larger assessment of relationships in the Dewey Decimal Classification (DDC) system, this study investigates the semantic nature of relationships in the DDC notational hierarchy. The semantic relationship between each of a set of randomly selected classes and its parent class in the notational hierarchy is examined against a set of relationship types (specialization, class-instance, several flavours of whole-part).The analysis addresses the prevalence of specific relationship types, their lexical expression, difficulties encountered in assigning relationship types, compatibility of relationships found in the DDC with those found in other knowledge organization systems (KOS), and compatibility of relationships found in the DDC with those in a shared formalism like the Web Ontology Language (OWL). Since notational hierarchy is an organizational mechanism shared across most classification schemes and is often considered to provide an easy solution for ontological transformation of a classification system, the findings of the study are likely to generalize across classification schemes with respect to difficulties that might be encountered in such a transformation process.
- Date
- 21.11.2011 12:29:56
-
Panzer, M.: Two tales of a concept : aligning FRSAD with SKOS (2011)
0.01
0.009683615 = product of:
0.04841807 = sum of:
0.04841807 = weight(_text_:context in 4789) [ClassicSimilarity], result of:
0.04841807 = score(doc=4789,freq=2.0), product of:
0.17622331 = queryWeight, product of:
4.14465 = idf(docFreq=1904, maxDocs=44218)
0.04251826 = queryNorm
0.27475408 = fieldWeight in 4789, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
4.14465 = idf(docFreq=1904, maxDocs=44218)
0.046875 = fieldNorm(doc=4789)
0.2 = coord(1/5)
- Source
- Concepts in context: Proceedings of the Cologne Conference on Interoperability and Semantics in Knowledge Organization July 19th - 20th, 2010. Eds.: F. Boteram, W. Gödert u. J. Hubrich
-
Mitchell, J.S.; Panzer, M.: Dewey linked data : Making connections with old friends and new acquaintances (2012)
0.01
0.0065901205 = product of:
0.032950602 = sum of:
0.032950602 = weight(_text_:system in 305) [ClassicSimilarity], result of:
0.032950602 = score(doc=305,freq=4.0), product of:
0.13391352 = queryWeight, product of:
3.1495528 = idf(docFreq=5152, maxDocs=44218)
0.04251826 = queryNorm
0.24605882 = fieldWeight in 305, product of:
2.0 = tf(freq=4.0), with freq of:
4.0 = termFreq=4.0
3.1495528 = idf(docFreq=5152, maxDocs=44218)
0.0390625 = fieldNorm(doc=305)
0.2 = coord(1/5)
- Abstract
- This paper explores the history, uses cases, and future plans associated with availability of the Dewey Decimal Classification (DDC) system as linked data. Parts of the Dewey Decimal Classification (DDC) system have been available as linked data since 2009. Initial efforts included the DDC Summaries (the top three levels of the DDC) in eleven languages exposed as linked data in dewey.info. In 2010, the content of dewey.info was further extended by the addition of assignable numbers and captions from the Abridged Edition 14 data files in English, Italian, and Vietnamese. During 2012, we will add assignable numbers and captions from the latest full edition database, DDC 23. In addition to the "old friends" of different Dewey language versions, institutions such as the British Library and Deutsche Nationalbibliothek have made use of Dewey linked data in bibliographic records and authority files, and AGROVOC has linked to our data at a general level. We expect to extend our linked data network shortly to "new acquaintances" such as GeoNames, ISO 639-3 language codes, and Mathematics Subject Classification. In particular, we will examine the linking process to GeoNames as an example of cross-domain vocabulary alignment. In addition to linking plans, we report on use cases that facilitate machine-assisted categorization and support discovery in the Semantic Web environment.
-
Panzer, M.: Taxonomies as resources identification, location and access of a »Webified« Dewey (2008)
0.01
0.006523886 = product of:
0.03261943 = sum of:
0.03261943 = weight(_text_:system in 5471) [ClassicSimilarity], result of:
0.03261943 = score(doc=5471,freq=2.0), product of:
0.13391352 = queryWeight, product of:
3.1495528 = idf(docFreq=5152, maxDocs=44218)
0.04251826 = queryNorm
0.2435858 = fieldWeight in 5471, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.1495528 = idf(docFreq=5152, maxDocs=44218)
0.0546875 = fieldNorm(doc=5471)
0.2 = coord(1/5)
- Abstract
- The paper outlines the first steps in an initiative to weave the Dewey Decimal Classification (DDC) as a resource into the fabric of the Web. In order for DDC web services to not only being »on« the Web, but rather a part of it, Dewey has to be available under the same rules as other information resources. The process of URI design for identified resources is described and a draft URI template is presented. In addition, basic semantic principles of RESTful web service architecture are discussed, and their appropriateness for making a large-scale knowledge organization system (KOS) like the DDC more congenial for Semantic Web applications is evaluated.
-
Panzer, M.; Zeng, M.L.: Modeling classification systems in SKOS : Some challenges and best-practice (2009)
0.01
0.006523886 = product of:
0.03261943 = sum of:
0.03261943 = weight(_text_:system in 3717) [ClassicSimilarity], result of:
0.03261943 = score(doc=3717,freq=2.0), product of:
0.13391352 = queryWeight, product of:
3.1495528 = idf(docFreq=5152, maxDocs=44218)
0.04251826 = queryNorm
0.2435858 = fieldWeight in 3717, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.1495528 = idf(docFreq=5152, maxDocs=44218)
0.0546875 = fieldNorm(doc=3717)
0.2 = coord(1/5)
- Abstract
- Representing classification systems on the web for publication and exchange continues to be a challenge within the SKOS framework. This paper focuses on the differences between classification schemes and other families of KOS (knowledge organization systems) that make it difficult to express classifications without sacrificing a large amount of their semantic richness. Issues resulting from the specific set of relationships between classes and topics that defines the basic nature of any classification system are discussed. Where possible, different solutions within the frameworks of SKOS and OWL are proposed and examined.
-
Baker, T.; Bermès, E.; Coyle, K.; Dunsire, G.; Isaac, A.; Murray, P.; Panzer, M.; Schneider, J.; Singer, R.; Summers, E.; Waites, W.; Young, J.; Zeng, M.: Library Linked Data Incubator Group Final Report (2011)
0.01
0.0064557428 = product of:
0.032278713 = sum of:
0.032278713 = weight(_text_:context in 4796) [ClassicSimilarity], result of:
0.032278713 = score(doc=4796,freq=2.0), product of:
0.17622331 = queryWeight, product of:
4.14465 = idf(docFreq=1904, maxDocs=44218)
0.04251826 = queryNorm
0.18316938 = fieldWeight in 4796, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
4.14465 = idf(docFreq=1904, maxDocs=44218)
0.03125 = fieldNorm(doc=4796)
0.2 = coord(1/5)
- Abstract
- The mission of the W3C Library Linked Data Incubator Group, chartered from May 2010 through August 2011, has been "to help increase global interoperability of library data on the Web, by bringing together people involved in Semantic Web activities - focusing on Linked Data - in the library community and beyond, building on existing initiatives, and identifying collaboration tracks for the future." In Linked Data [LINKEDDATA], data is expressed using standards such as Resource Description Framework (RDF) [RDF], which specifies relationships between things, and Uniform Resource Identifiers (URIs, or "Web addresses") [URI]. This final report of the Incubator Group examines how Semantic Web standards and Linked Data principles can be used to make the valuable information assets that library create and curate - resources such as bibliographic data, authorities, and concept schemes - more visible and re-usable outside of their original library context on the wider Web. The Incubator Group began by eliciting reports on relevant activities from parties ranging from small, independent projects to national library initiatives (see the separate report, Library Linked Data Incubator Group: Use Cases) [USECASE]. These use cases provided the starting point for the work summarized in the report: an analysis of the benefits of library Linked Data, a discussion of current issues with regard to traditional library data, existing library Linked Data initiatives, and legal rights over library data; and recommendations for next steps. The report also summarizes the results of a survey of current Linked Data technologies and an inventory of library Linked Data resources available today (see also the more detailed report, Library Linked Data Incubator Group: Datasets, Value Vocabularies, and Metadata Element Sets) [VOCABDATASET].
-
Panzer, M.: Relationships, spaces, and the two faces of Dewey (2008)
0.00
0.003954072 = product of:
0.01977036 = sum of:
0.01977036 = weight(_text_:system in 2127) [ClassicSimilarity], result of:
0.01977036 = score(doc=2127,freq=4.0), product of:
0.13391352 = queryWeight, product of:
3.1495528 = idf(docFreq=5152, maxDocs=44218)
0.04251826 = queryNorm
0.14763528 = fieldWeight in 2127, product of:
2.0 = tf(freq=4.0), with freq of:
4.0 = termFreq=4.0
3.1495528 = idf(docFreq=5152, maxDocs=44218)
0.0234375 = fieldNorm(doc=2127)
0.2 = coord(1/5)
- Content
- "When dealing with a large-scale and widely-used knowledge organization system like the Dewey Decimal Classification, we often tend to focus solely on the organization aspect, which is closely intertwined with editorial work. This is perfectly understandable, since developing and updating the DDC, keeping up with current scientific developments, spotting new trends in both scholarly communication and popular publishing, and figuring out how to fit those patterns into the structure of the scheme are as intriguing as they are challenging. From the organization perspective, the intended user of the scheme is mainly the classifier. Dewey acts very much as a number-building engine, providing richly documented concepts to help with classification decisions. Since the Middle Ages, quasi-religious battles have been fought over the "valid" arrangement of places according to specific views of the world, as parodied by Jorge Luis Borges and others. Organizing knowledge has always been primarily an ontological activity; it is about putting the world into the classification. However, there is another side to this coin--the discovery side. While the hierarchical organization of the DDC establishes a default set of places and neighborhoods that is also visible in the physical manifestation of library shelves, this is just one set of relationships in the DDC. A KOS (Knowledge Organization System) becomes powerful by expressing those other relationships in a manner that not only collocates items in a physical place but in a knowledge space, and exposes those other relationships in ways beneficial and congenial to the unique perspective of an information seeker.
