Protégé4US: Harvesting Ontology Authoring Data with Protégé

M Vigo, C Jay, R Stevens, H Paulheim (Editor), M Voigt (Editor), A Mitschick (Editor), R Garcia (Editor)

    Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

    137 Downloads (Pure)

    Abstract

    The inherent complexity of ontologies poses a number of cognitive and perceptual challenges for ontology authors. We investigate how users deal with the complexity of the authoring process by analysing how one of the most widespread ontology development tools (i.e. Protégé) is used. To do so, we build Protégé4US (Protégé for User Studies) by extending Protégé in order to generate log files that contain ontology authoring events. These log files not only contain data about the interaction with the environment, but also about OWL entities and axioms. We illustrate the usefulness of Protégé4US with a case study with 15 participants. The data generated from the study allows us to know more about how Protégé is used (e.g. most frequently used tabs), how well users perform (e.g. task completion times) and identify emergent authoring strategies, including moving down the class hierarchy or saving the current workspace before running the reasoner. We argue that Protégé4US is an valuable instrument to identify ontology authoring patterns.
    Original languageEnglish
    Title of host publication2nd Workshop on Human-Semantic Web Interaction Workshop (HSWI14)
    EditorsH Paulheim, M Voigt, A Mitschick, R Garcia
    Publication statusPublished - 2014
    EventWorkshop on Human-Semantic Web Interaction (HSWI’14) - Crete (Greece)
    Duration: 1 Jan 1824 → …

    Conference

    ConferenceWorkshop on Human-Semantic Web Interaction (HSWI’14)
    CityCrete (Greece)
    Period1/01/24 → …

    Keywords

    • ontologies
    • user studies
    • user testing
    • OWL
    • protégé

    Fingerprint

    Dive into the research topics of 'Protégé4US: Harvesting Ontology Authoring Data with Protégé'. Together they form a unique fingerprint.

    Cite this