<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="https://ontobee.org/ontology/view/SEPIO?iri=http://purl.obolibrary.org/obo/SEPIO_0000173"?>
<rdf:RDF xmlns="http://www.w3.org/2002/07/owl#"
     xml:base="http://www.w3.org/2002/07/owl"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
     xmlns:owl="http://www.w3.org/2002/07/owl#"
     xmlns:oboInOwl="http://www.geneontology.org/formats/oboInOwl#"
     xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
     xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
     xmlns:foaf="http://xmlns.com/foaf/0.1/"
     xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:ns3="http://purl.obolibrary.org/obo/">
    


    <!-- 
    ///////////////////////////////////////////////////////////////////////////////////////
    //
    // Annotation properties
    //
    ///////////////////////////////////////////////////////////////////////////////////////
     -->

    <AnnotationProperty rdf:about="http://purl.obolibrary.org/obo/IAO_0000118"/>
    <AnnotationProperty rdf:about="http://purl.obolibrary.org/obo/IAO_0000116"/>
    <AnnotationProperty rdf:about="http://purl.obolibrary.org/obo/IAO_0000115"/>
    <AnnotationProperty rdf:about="http://purl.obolibrary.org/obo/IAO_0000112"/>
    <AnnotationProperty rdf:about="http://purl.obolibrary.org/obo/SEPIO_0000061"/>
    


    <!-- 
    ///////////////////////////////////////////////////////////////////////////////////////
    //
    // Datatypes
    //
    ///////////////////////////////////////////////////////////////////////////////////////
     -->

    


    <!-- 
    ///////////////////////////////////////////////////////////////////////////////////////
    //
    // Object Properties
    //
    ///////////////////////////////////////////////////////////////////////////////////////
     -->

    


    <!-- http://purl.obolibrary.org/obo/RO_0002353 -->

    <ObjectProperty rdf:about="http://purl.obolibrary.org/obo/RO_0002353">
        <rdfs:label xml:lang="en">output of</rdfs:label>
    </ObjectProperty>
    


    <!-- 
    ///////////////////////////////////////////////////////////////////////////////////////
    //
    // Classes
    //
    ///////////////////////////////////////////////////////////////////////////////////////
     -->

    


    <!-- http://purl.obolibrary.org/obo/SEPIO_0000125 -->

    <Class rdf:about="http://purl.obolibrary.org/obo/SEPIO_0000125">
        <rdfs:label xml:lang="en">research study</rdfs:label>
    </Class>
    


    <!-- http://purl.obolibrary.org/obo/SEPIO_0000173 -->

    <Class rdf:about="http://purl.obolibrary.org/obo/SEPIO_0000173">
        <rdfs:label xml:lang="en">study finding</rdfs:label>
        <rdfs:subClassOf rdf:resource="http://purl.obolibrary.org/obo/SEPIO_0000174"/>
        <rdfs:subClassOf>
            <Restriction>
                <onProperty rdf:resource="http://purl.obolibrary.org/obo/RO_0002353"/>
                <someValuesFrom rdf:resource="http://purl.obolibrary.org/obo/SEPIO_0000125"/>
            </Restriction>
        </rdfs:subClassOf>
        <ns3:SEPIO_0000061>- While the act of generating a finding is simpler, it does involve some cognitive effort that could be guided by some method (i.e., one defining what experimental context should be included in the finding statement, and how this and the observed outcomes are reported). Which means that findings are not the direct output of an assay, which merely generates data. So perhaps in SEPIO we commit to only considering research processes at the level of studies - such that even assays would potentially involve some act of summarizing the results as a finding.

- Note that at present &#39;study data sets&#39; can serve the same &#39;organizational&#39; purpose as &#39;study findings&#39; - we should converge on one recommended way to perform this level of organization of evidence data.</ns3:SEPIO_0000061>
        <ns3:IAO_0000112>Findings statements tend to take the form of &quot;We observed that . . . &quot;, or &quot;Assay X revelaned that . . . &quot;, or &quot;X was determined to be Y in a study of . . . &quot;.  
For example:

&quot;Smith et. al observed that a positive response to imatinib treatment was two-fold higher in a cohort of leukemia patients bearing Bcr-Abl fusions compared to those lacking this driver mutaiton.&quot; 

A statement summarizing the outcome of a sequencing analysis: &quot;DNA sequencing data from patient X revealed an A-&gt;T mutation at position 2143 in gene Y&quot;.

A statement summarizing the outcome of a variant population frequency study: &quot;The frequency of variant X was determined to be 0.00015 in a cohort of non-finnish european subjects described in the ExAC dataset.&quot;</ns3:IAO_0000112>
        <ns3:IAO_0000118>study outcome</ns3:IAO_0000118>
        <ns3:IAO_0000115>A statement describing the immediate results of a research study, describing what was directly observed, measured, or derived through mathematical calculation.</ns3:IAO_0000115>
        <rdfs:comment>SEPIO distinguishes two high-level subtypes of statements:
1. Findings are statements that report the immediate, objective results of an experiment, observation, or study -  without bias or interpretation.  A finding statement results simply from an act of reporting or summarizing these direct observations, calculations, or measurements.
2. Assertions, by contrast, result from acts of interpretation and/or inference, based on information used as evidence. The statement here is a conclusion drawn from critical evaluation of this more foundational information, and its validity depends on the quality of this information and its interpretation as evidence.</rdfs:comment>
        <rdfs:comment>A study finding is a statement that summarizes the immediate results of a particular experiment or study. It describes only what was directly observed, measured, or calculated, and optionally the experimental context of these observations.  It does not describe more general conclusions that may have been inferred from such results. As such, the scope of what a finding describes is limited to the direct participants in the study - i.e. it is about only the instances observed or measured in the study.  It makes no broader inference or conclusion about types or classes to which these instances belong. 

This is not to say that the onserved findings are necessarily accurate or correct - only that they were indeed made in a particular study. For example, the finding that &quot;Sequencing of DNA from patient X revealed an A-&gt;T mutation at position 2143 in gene Y&quot; is a matter of fact - this was the outcome of the assay, even if the finding is an artifact of low sequencing coverage. Metadata about the finding (e.g. sequencing methods/reagents used, coverage or read depth) are recoded so users can judge for themselves whether the objectively reported finding accurtely reflects the biology it describes.</rdfs:comment>
        <ns3:IAO_0000116>In SEPIO, a high-level distinction is made between statements that are &#39;findings&#39; vs &#39;assertions&#39;.  Findings are statements that report/summarize what was directly observed or calculated in a study, and are about only the immediate  participants in the experiment or study. As such, findings involve no interpretation or inference from the data to draw broader conclusions. Assertions, by contrast, are statements that derive from some degree of interpretation or inference based on the evaluation of &#39;evidence&#39;, and often make broader claims about the types or categories to which study participants belong. This distinction is important because the provenance and validity of a &#39;finding&#39; statement does not depend on subjective interpretation of &#39;evidence&#39; in the same way that of an assertion does. This has modeling implications for how findings and assertions are linked to information that supports them.

In practices, instances of &#39;study findings&#39; are used to group one or more data items from a particular research study that are relevant as evidence for an assertion.  The utility of this class is in allowing the shared provenance of these data items to be more efficiently represented - as things like agent, date, and methods can be described once for the data set and inferred to apply to all individual data items that comprise it.</ns3:IAO_0000116>
    </Class>
    


    <!-- http://purl.obolibrary.org/obo/SEPIO_0000174 -->

    <Class rdf:about="http://purl.obolibrary.org/obo/SEPIO_0000174">
        <rdfs:label xml:lang="en">statement</rdfs:label>
    </Class>
</rdf:RDF>



<!-- Generated by the OWL API (version 3.2.4.1806) http://owlapi.sourceforge.net -->



