Group items tagged

Primary Objectives * Build a demo that spans from bench to bedside using RDF and OWL. * Explore the effectiveness of current tools. * Document our finding to help accelerate adoption of the Semantic Web.

# The primary intention of creating aTags is not the categorization of the document, but the representation of the key facts inside the document. Key facts in the biomedical domain might be, for example, "Protein A interacts with protein B" or "Overexpression of protein A in tissue B is the cause of disease C". # An aTag is comprised of a set of associated entities. The size of the set is arbitrary, but will typically lie between 2 and 5 entities. For example, the fact "Protein A binds to protein B" can be represented with an aTag comprising of the three entities "Protein A", "Molecular interaction" and "Protein B". Similarly, the fact "Overexpression of protein A in tissue B is the cause of disease C" can be represented with an aTag comprising of the four entities "Overexpression", "Protein A", "Tissue B" and "Disease C". # Each document or database entry can be described with an arbitrary number of such aTags. Each aTag can be associated with the relevant portions of text or data in a fine granularity. # The entities in an aTag are not simple strings, but resources that are part of ontologies and RDF/OWL-enabled databases. For example, "Protein A" and "Protein B" are resources that are defined in the UniProt database, whereas "Molecular Interaction" is a class in the branch of biological processes of the Gene Ontology. They are identified with their URIs.