Conference paper Open Access

VoCol: An Agile Methodology and Environment for Collaborative Vocabulary Development

Petersen, Niklas; Halilaj, Lavdim; Lange, Christoph; Auer, Sören

DataCite XML Export

<?xml version='1.0' encoding='utf-8'?>
<resource xmlns:xsi="" xmlns="" xsi:schemaLocation="">
  <identifier identifierType="DOI">10.5281/zenodo.15023</identifier>
      <creatorName>Petersen, Niklas</creatorName>
      <affiliation>University of Bonn</affiliation>
      <creatorName>Halilaj, Lavdim</creatorName>
      <affiliation>University of Bonn</affiliation>
      <creatorName>Lange, Christoph</creatorName>
      <affiliation>University of Bonn</affiliation>
      <creatorName>Auer, Sören</creatorName>
      <affiliation>University of Bonn</affiliation>
    <title>Vocol: An Agile Methodology And Environment For Collaborative Vocabulary Development</title>
    <subject>collaborative vocabulary development</subject>
    <date dateType="Issued">2015-02-11</date>
  <resourceType resourceTypeGeneral="Text">Conference paper</resourceType>
    <rights rightsURI="info:eu-repo/semantics/openAccess">Open Access</rights>
    <description descriptionType="Abstract">&lt;p&gt;Vocabularies typically reflect a consensus among experts in a&lt;br /&gt;
certain application domain. They are thus implemented in collaboration&lt;br /&gt;
of domain experts and knowledge engineers. Particularly the presence of&lt;br /&gt;
domain experts with little technical background requires a low-threshold&lt;br /&gt;
vocabulary engineering methodology. This methodology should be im-&lt;br /&gt;
plementable without dependencies on complex software components, it&lt;br /&gt;
should provide collaborators with comprehensible feedback on syntax&lt;br /&gt;
and semantics errors in a tight loop, and it should give access to a human-&lt;br /&gt;
readable presentation of the vocabulary. Inspired by agile software and&lt;br /&gt;
content development methodologies, we define the VoCol methodology&lt;br /&gt;
to address these requirements. We implemented a prototype based on a&lt;br /&gt;
loose coupling of validation and documentation generation components&lt;br /&gt;
on top of a standard Git repository. All of these components, even the&lt;br /&gt;
repository engine, can be exchanged with little effort. By evaluating the&lt;br /&gt;
usefulness of error feedback of different tools in the realistic setting of an&lt;br /&gt;
emerging mobility vocabulary we prove, however, that our choice of the&lt;br /&gt;
crucial validation component is workable.&lt;/p&gt;</description>


Cite as