<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Reihaneh Amini</style></author><author><style face="normal" font="default" size="100%">Michelle Cheatham</style></author><author><style face="normal" font="default" size="100%">Pawel Grzebala</style></author><author><style face="normal" font="default" size="100%">Helena B. McCurdy</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Towards Best Practices for Crowdsourcing Ontology Alignment Benchmarks</style></title><secondary-title><style face="normal" font="default" size="100%">15th International Semantic Web Conference (ISWC) 2016</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2016</style></year></dates><pub-location><style face="normal" font="default" size="100%">Kobe, Japan</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">&lt;p&gt;Ontology alignment systems establish the links between ontologies that enable knowledge from various sources and domains to be used by applications in many different ways. Unfortunately, these systems are not perfect. Currently, the results of even the best-performing alignment systems need to be manually verified in order to be fully trusted. Ontology alignment researchers have turned to crowdsourcing platforms such as Amazon's Mechanical Turk to accomplish this. However, there has been little systematic analysis of the accuracy of crowdsourcing for alignment verification and the establishment of best practices. In this work, we analyze the impact of the presentation of the context of potential matches and the way in which the question is presented to workers on the accuracy of crowdsourcing for alignment verification.&lt;/p&gt;
</style></abstract></record></records></xml>