Exactly. I agree with Bill. One thing that came up during the call is that in our definition of infection acquisition is to which extend the fact that the textual definition talks about reproduction is creating ambiguity with respect to the infection per se."The biological process of pathogen organism(s) entering (the body of) a host organism from a contagious host or a contaminated thing and reproducing using host resources"I think this could be easily fixed.Best,MathiasOn Sun, Oct 26, 2014 at 1:05 PM, Bill Hogan <hog...@gmail.com> wrote:The reason we called the process 'infection acquisition' in Apollo was to highlight the fact that the infectious host does not undergo any change, only the susceptible one that acquires an infection.So in Apollo for sure, we decided that transmission occurs only when it results in an infection.What is the plan for capturing the discussion to date? IDO itself, or also its documentation?
BillOn Sun, Oct 26, 2014 at 10:48 AM, Mathias Brochhausen <mbroch...@gmail.com> wrote:Hi,so following Alan's suggestion I'll make the start in continuing the discussion via e-mail.I have to go back to something we already discussed during the call and I am fully aware that this is an issue that needs to be discussed with the Transmission Ontology:During the phone call it was suggested to propose to Lynn to change the definition of transmission process to something along the line of:"A pathogen transmission process in which a pathogen is transmitted from one host to another."re-using formulation for the definition of 'horizontal pathogen transmission process".I'd hold that the definition could be optimized. The definition doesn't actually say what a transmission is (what necessary parts it has, etc.), but it uses the verb transmitted to define the transmission process, which seems a little bit circular to me.Question that might help writing the definition are:Is transmission only about re-location of pathogens?Do we only talk about a transmission when it results in an infection?Maybe I am overlooking something…Best,MathiasOn Thu, Oct 23, 2014 at 10:19 AM, Lindsay Cowell <Lindsay...@utsouthwestern.edu> wrote:Thank you Alan for the thoughtful response. I agree with all of Alan’s comments.
Lindsay
From: Alan Ruttenberg <alanrut...@gmail.com>
Date: Thursday, October 23, 2014 at 10:04 AM
To: Mathias Brochhausen <mbroch...@gmail.com>
Cc: Dept of Clinical Sciences <lindsay...@utsouthwestern.edu>, Asiyah Yu Lin <lini...@gmail.com>, Alexander Diehl <add...@buffalo.edu>, Bill Hogan <hog...@gmail.com>, Barry Smith <phis...@buffalo.edu>, Albert Goldfain <albertg...@gmail.com>
Subject: Re: IDO issues (from the perspective of the Apollo project)
On Wed, Oct 22, 2014 at 7:05 PM, Mathias Brochhausen <mbroch...@gmail.com> wrote:
I think the meeting went fairly well.
One or two questions/comments:
What is the final vision? Once we eliminated the discord between IDO and Apollo-SV, will IDO also look to re-use Apollo-SV terms that are domain relevant, but not present now?
I will offer only my vision.
- Once IDO changes are made, If there are terms in Apollo-SV that are duplicative of terms in IDO (i.e. equivalent, but previously not understood to be) then such Apollo-SV terms should be obsoleted and the IDO terms used.
- if there are terms in Apollo-SV that we agree properly belong in the domain of IDO, we should discuss moving them to IDO, retaining, however, the Apollo-SV identifier, possibly clarified definition, and provenance (term editor, etc). IDO would be, in such agreed-upon-cases, the manager of the term and Apollo-SV would MIREOT it back in. We have discussed, in the technical committee, a mechanism for distinguishing the current managing ontology for a term from the original ontology it was defined in.
- If there are terms that are in Apollo-SV which are closer to being application specific then I would leave them in Apollo-SV
- The revised Apollo-SV would formally become an IDO extension and developers engage constructively to participate (and define) the process of coordination among members of the IDO Consortium. Selected developers might join the IDO effort, if interest was in the broader scope ontology.The elephant in the room is that many definitions (both textual definitions and axioms) revolve around the term IDO:infection once we get the main issues resolved, I need to check whether we can maintain terms for Apollo-SV that are less centered around that term and more centered on the process (which is by and large the approach Apollo-SV took).
I don't think this is a problem, in principle. Once axioms are added that link one to the other then we should be able to have queries that query across both.
I do think that it would be helpful to have some collaborative discussions with the Apollo-SV team to share experience and discuss whether, in the the light of that experience, it might be more beneficial for Apollo-SV to pay more attention to the OGMS-based formulation. There is a lot of thought that went into OGMS and IDO, and it may be that the Apollo-SV team will discover things they haven't thought of in such a discussion.
YVMV (your vision may vary ;-) (I would be very interested in hearing alternative visions)
Alan
UT Southwestern Medical Center
The future of medicine, today.
--
--
Google Groups "infectious-disease-ontology" group.
http://groups.google.com/group/ido-discuss
---
You received this message because you are subscribed to the Google Groups "infectious-disease-ontology" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ido-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi, Mathias,
As for the second question, my opinion is that transmission is not only process that leads to an infection, which is captured by 'infection acquisition' in Apollo.
I am not sure about the first question.
Best,
Asiyah