Data Portal @ linkeddatafragments.org

Matches in ScholarlyData for { ?s ?p ?o. }

• paper-24 type InProceedings.
• paper-24 label "Reasoning in RDFS is Inherently Serial, at least in the worst case".
• paper-24 sameAs paper-24.
• paper-24 abstract "Although it appears that reasoning in RDFS is embarrassingly parallel, this is not the case. Because all vocabulary is treated the same way in RDF, it is possible to extend the RDFS ontology vocabulary. The ability permits the creation of useful constructs that are not amenable to parallelism, and that in the end require serial processing.".
• paper-24 hasAuthorList authorList.
• paper-24 isPartOf poster-demo-proceedings.
• paper-24 title "Reasoning in RDFS is Inherently Serial, at least in the worst case".
• authorList type List.
• authorList hasFirstItem item-1.
• authorList hasItem item-1.
• authorList hasLastItem item-1.
• item-1 type ListItem.
• item-1 hasContent peter-patel-schneider.
• paper-25 type InProceedings.
• paper-25 label "RIO: Minimizing User Interaction in Ontology Debugging".
• paper-25 sameAs paper-25.
• paper-25 abstract "Interactive ontology debugging incorporates a user who answers queries about entailments of their intended ontology. In order to minimize the amount of user interaction in a debugging session, a user must choose an appropriate query selection strategy. However, the choice of an unsuitable strategy may result in tremendous overhead in terms of time and cost. We present a learning method for query selection which unites the advantages of existing approaches while overcoming their flaws. Our tests show the utility of our approach when applied to a large set of real-world ontologies, its scalability and adequate reaction time allowing for continuous interactivity.".
• paper-25 hasAuthorList authorList.
• paper-25 isPartOf poster-demo-proceedings.
• paper-25 title "RIO: Minimizing User Interaction in Ontology Debugging".
• 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 patrick-rodler.
• item-1 next item-2.
• item-2 type ListItem.
• item-2 hasContent kostyantyn-shchekotykhin.
• item-2 next item-3.
• item-2 previous item-1.
• item-3 type ListItem.
• item-3 hasContent philipp-fleiss.
• item-3 next item-4.
• item-3 previous item-2.
• item-4 type ListItem.
• item-4 hasContent gerhard-friedrich.
• item-4 previous item-3.
• paper-26 type InProceedings.
• paper-26 label "Semantic Vernacular System: an Observation-based, Community-powered, and Semantics-enabled Naming System for Organisms".
• paper-26 sameAs paper-26.
• paper-26 abstract "The Semantic Vernacular System is a novel naming system for creating named, machine-interpretable descriptions for groups of organisms. Unlike the traditional scientific naming system, which is based on evolutionary relationships, it emphasizes the observable features of organisms. By independently naming the descriptions composed of sets of observational features, as well as maintaining connections to scientific names, it preserves the observational data used to identify organisms. The system is designed to support a peer-review mechanism for creating new names, and uses a controlled vocabulary encoded in the Web Ontology Language to represent the observational features. A prototype of the system is currently under development in collaboration with the Mushroom Observer website. It allows users to propose new names and descriptions, provide feedback on those proposals, and ultimately have them formally approved. This effort aims at offering the mycology community a knowledge base of fungal observational features and a tool for identifying fungal observations.".
• paper-26 hasAuthorList authorList.
• paper-26 isPartOf poster-demo-proceedings.
• paper-26 title "Semantic Vernacular System: an Observation-based, Community-powered, and Semantics-enabled Naming System for Organisms".
• 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 han-wang.
• item-1 next item-2.
• item-2 type ListItem.
• item-2 hasContent nathan-wilson.
• item-2 next item-3.
• item-2 previous item-1.
• item-3 type ListItem.
• item-3 hasContent kathryn-dunn.
• item-3 next item-4.
• item-3 previous item-2.
• item-4 type ListItem.
• item-4 hasContent deborah-l-mcguinness.
• item-4 previous item-3.
• paper-27 type InProceedings.
• paper-27 label "Simplifying MIREOT; a MIREOT Protege Plugin".
• paper-27 sameAs paper-27.
• paper-27 abstract "The Web Ontology Language (OWL) is a commonly used standard for creating ontology artifacts. However, its capabilities for reusing existing OWL artifacts in the creation of new artifacts is limited to the import of whole ontologies, even when only a small handful of classes, object properties, and so on (which we refer to generically as OWL components) are relevant. This situation can result in extremely large and unwieldy, or even broken, ontologies. To address this problem while still promoting ontology reuse, the OBI Consortium has elucidated the Minimum Information to Reference an External Ontology Term (MIREOT). We provide a suite of plugins to the Protege editor that greatly simplifies the use of MIREOT principles during ontology creation and editing.".
• paper-27 hasAuthorList authorList.
• paper-27 isPartOf poster-demo-proceedings.
• paper-27 title "Simplifying MIREOT; a MIREOT Protege Plugin".
• authorList type List.
• authorList hasFirstItem item-1.
• authorList hasItem item-1.
• authorList hasItem item-10.
• authorList hasItem item-2.
• authorList hasItem item-3.
• authorList hasItem item-4.
• authorList hasItem item-5.
• authorList hasItem item-6.
• authorList hasItem item-7.
• authorList hasItem item-8.
• authorList hasItem item-9.
• authorList hasLastItem item-9.
• item-1 type ListItem.
• item-1 hasContent josh-hanna.
• item-1 next item-10.
• item-10 type ListItem.
• item-10 hasContent william-hogan.
• item-10 next item-2.
• item-10 previous item-1.
• item-2 type ListItem.
• item-2 hasContent chen-cheng.
• item-2 next item-3.
• item-2 previous item-10.

• first
• previous
• next