Conference paper Open Access

VoCol: An Agile Methodology and Environment for Collaborative Vocabulary Development

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


MARC21 XML Export

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nam##2200000uu#4500</leader>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u">https://creativecommons.org/licenses/by/4.0/</subfield>
    <subfield code="a">Creative Commons Attribution 4.0</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2015-02-11</subfield>
  </datafield>
  <controlfield tag="005">20160912075149.0</controlfield>
  <controlfield tag="001">15023</controlfield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">openaire</subfield>
    <subfield code="o">oai:zenodo.org:15023</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">&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;</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">University of Bonn</subfield>
    <subfield code="a">Halilaj, Lavdim</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">University of Bonn</subfield>
    <subfield code="a">Lange, Christoph</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">University of Bonn</subfield>
    <subfield code="a">Auer, Sören</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">940842</subfield>
    <subfield code="z">md5:ad892cefb46f0fa1db5567da211bb7a4</subfield>
    <subfield code="u">https://zenodo.org/record/15023/files/vocol.pdf</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">conferencepaper</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">University of Bonn</subfield>
    <subfield code="a">Petersen, Niklas</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">collaborative vocabulary development</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.15023</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">VoCol: An Agile Methodology and Environment for Collaborative Vocabulary Development</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
</record>

Share

Cite as