Matches in ScholarlyData for { ?s ?p ?o. }
- authorList type List.
- authorList hasFirstItem item-1.
- authorList hasItem item-1.
- authorList hasItem item-2.
- authorList hasLastItem item-2.
- item-1 type ListItem.
- item-1 hasContent christian-wartena.
- item-1 next item-2.
- item-2 type ListItem.
- item-2 hasContent rogier-brussee.
- item-2 previous item-1.
- 237 creator christophe-gueret.
- 237 creator eyal-oren.
- 237 creator stefan-schlobach.
- 237 type InProceedings.
- 237 label "Anytime Query Answering in RDF through Evolutionary Algorithms".
- 237 sameAs 237.
- 237 abstract "We present a technique for answering queries over RDF data through an evolutionary search algorithm, using fingerprinting and bloomfilters for rapid approximate evaluation of generated solutions. Our evolutionary approach has several advantages compared to traditional database-style query answering. First, the result quality increases monotonically and converges with each evolution, offering ``anytime'' behaviour with arbitrary trade-off between computation time and query results; in addition, the level of approximation can be tuned by varying the size of the bloomfilters. Secondly, through bloomfilter compression we can fit large graphs in main memory, reducing the need for disk I/O during query evaluation. Finally, since the individuals evolve independently, parallel execution is straightforward. We present an initial prototype that evaluates basic SPARQL queries over arbitrary RDF graphs and show initial results over large datasets.".
- 237 hasAuthorList authorList.
- 237 hasTopic Semantic_Web.
- 237 isPartOf proceedings.
- 237 keyword "SPARQL".
- 237 keyword "approximate reasoning".
- 237 keyword "bloom filters".
- 237 keyword "evolutionary algorithms".
- 237 keyword "query answering".
- 237 title "Anytime Query Answering in RDF through Evolutionary Algorithms".
- authorList type List.
- authorList hasFirstItem item-1.
- authorList hasItem item-1.
- authorList hasItem item-2.
- authorList hasItem item-3.
- authorList hasLastItem item-3.
- item-1 type ListItem.
- item-1 hasContent eyal-oren.
- item-1 next item-2.
- item-2 type ListItem.
- item-2 hasContent christophe-gueret.
- item-2 next item-3.
- item-2 previous item-1.
- item-3 type ListItem.
- item-3 hasContent stefan-schlobach.
- item-3 previous item-2.
- 246 creator bijan-parsia.
- 246 creator matthew-horridge.
- 246 creator ulrike-sattler.
- 246 type InProceedings.
- 246 label "Laconic and Precise Justifications in OWL".
- 246 sameAs 246.
- 246 abstract "A justification for an entailment in an OWL ontology is a minimal subset of the ontology that is sufficient for that entailment to hold. Since justifications respect the syntactic form of axioms in an ontology, they are usually neither syntactically nor semantically minimal. This paper presents two new subclasses of justifications - laconic justications and precise justications. Laconic justications only consist of axioms that do not contain any redundant parts. Precise justications can be derived from laconic justications and are characterised by the fact that they consist of flat, small axioms, which facilitate the generation of semantically minimal repairs. Formal denitions for both types of justication are presented. In contrast to previous work in this area, these definitions make it clear as to what exactly parts of axioms are. In order to demonstrate the practicability of computing laconic, and hence precise justications, an algorithm is provided and results from an empirical evaluation carried out on several published ontologies are presented. The evaluation showed that laconic/precise justications can be computed in a reasonable time for entailments in a range of ontologies that vary in size and complexity. It was found that in half of the ontologies sampled there were entailments that had more laconic/precise justications than regular justications. More surprisingly it was observed that for some ontologies there were fewer laconic/precise justications than regular justications.".
- 246 hasAuthorList authorList.
- 246 hasTopic Semantic_Web.
- 246 isPartOf proceedings.
- 246 keyword "Explanation".
- 246 keyword "Laconic justifications".
- 246 keyword "Precise justifications".
- 246 title "Laconic and Precise Justifications in OWL".
- authorList type List.
- authorList hasFirstItem item-1.
- authorList hasItem item-1.
- authorList hasItem item-2.
- authorList hasItem item-3.
- authorList hasLastItem item-3.
- item-1 type ListItem.
- item-1 hasContent matthew-horridge.
- item-1 next item-2.
- item-2 type ListItem.
- item-2 hasContent bijan-parsia.
- item-2 next item-3.
- item-2 previous item-1.
- item-3 type ListItem.
- item-3 hasContent ulrike-sattler.
- item-3 previous item-2.
- 251 creator mark-a-musen.
- 251 creator natalya-noy.
- 251 creator samson-tu.
- 251 creator tania-tudorache.
- 251 type InProceedings.
- 251 label "Supporting Collaborative Ontology Development in Protégé".
- 251 sameAs 251.
- 251 abstract "Ontologies are becoming so large in their coverage that no single person or a small group of people can develop them effectively and ontology development becomes a community-based enterprise. In this paper, we discuss requirements for supporting collaborative ontology development and present Collaborative Protege-—a tool that supports many of these requirements, such as discussions integrated with ontology-editing process, chats, and annotations of changes and ontology components. We have evaluated Collaborative Protege in the context of ontology development in an ongoing large-scale biomedical project that actively uses ontologies: the ATHENA-DSS project at the VA Palo Alto Healthcare System. Users have found the new tool effective as an environment for carrying out discussions and for recording references for the information sources and design rationale.".
- 251 hasAuthorList authorList.
- 251 hasTopic Semantic_Web.
- 251 isPartOf proceedings.
- 251 keyword "Protege".
- 251 keyword "biomedical ontologies".
- 251 keyword "collaborative ontology development".
- 251 title "Supporting Collaborative Ontology Development in Protégé".
- authorList type List.
- authorList hasFirstItem item-1.
- authorList hasItem item-1.
- authorList hasItem item-2.
- authorList hasItem item-3.
- authorList hasItem item-4.
- authorList hasLastItem item-4.
- item-1 type ListItem.
- item-1 hasContent tania-tudorache.
- item-1 next item-2.
- item-2 type ListItem.
- item-2 hasContent natalya-noy.