This study examines Dublin Core (DC) metadata semantics drawn from the perspectives and experiences of cataloguing and metadata professionals. The study ascertains the extent of difficulty in applying the DC metadata elements encountered by these professionals and examines factors engendering such difficulties during the metadata application process. Comments drawn from the survey participants (n = 141) show that conceptual ambiguities (41%) and semantic overlaps (45%) of the surveyed DC metadata elements are the most frequently cited factors causing difficulty and confusion, in turn leading to variant interpretations of DC metadata elements. This has the potential to bring forth inconsistent and inaccurate applications and implementation of the DC standard across institutions which can directly affect semantic interoperability across digital repositories. The high degree of difficulty (55.3%) engendered by the Relation field indicates that further examination of this element is needed.
Knowledge Organization Systems/ Services, http://nkos.slis. kent.edu/) and digital library communities on scenarios for KOS-based interactive services such as attempting to match user vocabulary with controlled terms, browsing or selecting a concept or set of concepts according to KOS relationships. The API could be used in combination with different kinds of search systems. When considering large-scale, augmented KOS, or ontologies, then general semantic query languages, such as SPARQL (Simple Protocol and RDF Query Language), may be appropriate for applications requiring logicbased reasoning. For more general search-based applications, the SKOS API could be used in combination with query APIs, such as SRW/U (Search/Retrieve via URL/Web Service), Google or Verity. However, we would argue there is also a need for a specialized KOS query API to take full advantage of applications with KOS-indexed metadata.
RecornendationsWith regard to evolution of the API, we recommend that such protocols return relationship information with all calls.Those calls that return a list of concepts related by a specified relationship, such as broader, should return a structured list, identifying the level of expansion from the initial concept, rather than an undifferentiated list (as at present). A single call should be available for the display of a concept and its directly related concepts.
ConcluionsAs initial exploration of programmatic access to KOS with the SKOS API, we developed a pilot PC-based (.NET) Web service client demonstrator application. This was tested on a remote server, which used a different technology platform. Supported by concept caching, it generally achieved a fast enough response for reasonable interaction and suggests that the SKOS API can support client applications of this type. However further refinement of the API is required.Given foreseeable bandwidth limitations, KOS-specific protocols continue to be needed for efficient services. Future API designs should support the further integration of KOS into rich but responsive mapping and query terminology services.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.