Extending the Simple Knowledge Organization System for Concept Management in Vocabulary Development Applications

In this article, we describe the development of an exten- sion to the Simple Knowledge Organization System (SKOS) to accommodate the needs of vocabulary devel- opment applications (VDA) managing metadata schemes and requiring close tracking of change to both those schemes and their member concepts. We take a neo- pragmatic epistemic stance in asserting the need for an entity in SKOS modeling to mediate between the abstract concept and the concrete scheme. While the SKOS model sufficiently describes entities for modeling the current state of a scheme in support of indexing and search on the Semantic Web, it lacks the expressive power to serve the needs of VDA needing to maintain scheme historical continuity. We demonstrate prelimi- narily that conceptualizations drawn from empirical work in modeling entities in the bibliographic universe, such as works, texts, and exemplars, can provide the basis for SKOS extension in ways that support more rig- orous demands of capturing concept evolution in VDA.

URIs and Intertextuality: Incumbent Philosophical Commitments in the Development of the Semantic Web

Examines two commitments inherent in Resource Description Framework (RDF): intertextuality and rationalism. After introducing how rationalism has been studied in knowledge organization, this paper then introduces the concept of bracketed-rationalism. This paper closes with a discussion of ramifications of intertextuality and bracketed rationalism on evaluation of RDF.

Versioning Concept Schemes for Persistent Retrieval

Things change. Words change, meaning changes and use changes both words and meaning. In information access systems this means concept schemes such as thesauri or clas- sification schemes change. They always have. Concept schemes that have survived have evolved over time, moving from one version, often called an edition, to the next. If we want to manage how words and meanings - and as a conse- quence use - change in an effective manner, and if we want to be able to search across versions of concept schemes, we have to track these changes. This paper explores how we might expand SKOS, a World Wide Web Consortium (W3C) draft recommendation in order to do that kind of tracking.The Simple Knowledge Organization System (SKOS) Core Guide is sponsored by the Semantic Web Best Practices and Deployment Working Group. The second draft, edited by Alistair Miles and Dan Brickley, was issued in November 2005. SKOS is a “model for expressing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, folksonomies, other types of controlled vocabulary and also concept schemes embedded in glossaries and terminologies” in RDF. How SKOS handles version in concept schemes is an open issue. The current draft guide suggests using OWL and DCTERMS as mechanisms for concept scheme revision.As it stands an editor of a concept scheme can make notes or declare in OWL that more than one version exists. This paper adds to the SKOS Core by introducing a tracking sys- tem for changes in concept schemes. We call this tracking system vocabulary ontogeny. Ontogeny is a biological term for the development of an organism during its lifetime. Here we use the ontogeny metaphor to describe how vocabularies change over their lifetime. Our purpose here is to create a conceptual mechanism that will track these changes and in so doing enhance information retrieval and prevent document loss through versioning, thereby enabling persistent retrieval.

The Notion of the “Concept Instance”: Problems in Modeling Concept Change in SKOS

The U.S. National Science Foundation metadata registry under development for the National Science Digital Library (NSDL) is a repertory intended to manage both metadata schemes and schemas. The focus of this draft discussion paper is on the scheme side of the development work. In particular, the concern of the discussion paper is with issues around the creation of historical snapshots of concept changes and their encoding in SKOS. Through framing the problem as we see it, we hope to find an optimal solution to our need for a SKOS encoding of these snapshots. Since what we are seeking to model is concept change, it is necessary at the outset to make it clear that we are not talking about changes to a concept of such a nature that would require the declaration a new concept with its own URI.In the project, we avoid the use of the terms “version” and “versioning” with regard to changes in concepts and reserve their use to the significant changes of schemes as a whole. Significant changes triggering a new scheme version might include changes in scheme documentation that express a significant shift in the purpose, use or architecture of the scheme. We use the term “snapshot” to denote the state of a scheme at identifiable points in time. Thus, snapshots are identifiable views of a scheme that record the incremental changes that have occurred to concepts, relationships among concepts, and scheme documentation since the last snapshot. Aspects of concept change occur that we need to capture and make available both through the registry and through potentially in transmission of a scheme to other registries. We call these capturings “concept instances.”