-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can biological and technical replicates be used for environmental metagenome samples? #1693
Comments
Also if anyone has examples of using these classes in aboxes this would be very useful. Also interested in axioms that help us data model - e.g should one sample be prohibited from having multiple biological replicate roles? |
Thank you Chris, another really good catch! My first gut reaction is to
change mentions of 'subject' or 'participant' to 'material'. It will
require deeper looking into what that could harm, but I think it would make
things more consistent overall.
…On Thu, May 4, 2023 at 1:59 PM Chris Mungall ***@***.***> wrote:
Also if anyone has examples of using these classes in aboxes this would be
very useful. Also interested in axioms that help us data model - e.g should
one sample be prohibited from having multiple biological replicate roles?
—
Reply to this email directly, view it on GitHub
<#1693 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADJX2IWEQSAMWPSXMAUU7TLXEQKCDANCNFSM6AAAAAAXWJNKIU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Bjoern Peters
Professor
La Jolla Institute for Immunology
9420 Athena Circle
La Jolla, CA 92037, USA
Tel: 858/752-6914
Fax: 858/752-6987
http://www.liai.org/pages/faculty-peters
|
Thank you, Chris. We discussed this on the OBI call today (05.08.23). We agree with your feedback about broadening OBI's terms beyond applications for humans/organisms. We are planning to use an OBI meeting in the future to discuss strategy and implementation for a fix of this issue. Can you and/or @turbomam attend a future OBI call about this? See also: #1629 |
The call is at a bad time for me but Mark may be able to make a call and
present on what we are doing in NMDC. There is also the #obi channel on OBO
slack which is good for async discussion but it seems not a lot of people
are there?
…On Mon, May 8, 2023 at 9:34 AM Sebastian Duesing ***@***.***> wrote:
Thank you, Chris. We discussed this on the OBI call today (05.08.23). We
agree with your feedback about broadening OBI's terms beyond applications
for humans/organisms. We are planning to use an OBI meeting in the future
to discuss strategy and implementation for a fix of this issue. Can you
and/or @turbomam <https://github.com/turbomam> attend a future OBI call
about this?
See also: #1629 <#1629>
—
Reply to this email directly, view it on GitHub
<#1693 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAMMOIXYGINLCV7ZSIEONLXFEOB5ANCNFSM6AAAAAAXWJNKIU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I'm in the OBI call right now! |
We're checking "reference subject role" which contains two issues - axiom and label semantics - that would need resolution
A more general issue is whether OBI should shift language around "investigation participant" vs "investigation subject" |
For "reference subject role" I propose a tentative narrow rewrite:
That definition accommodates assays which are generating data about a subject's characteristics - material or organism - or are collecting other kinds of information, like surveys, or animal behaviours, with a choice of subject to consider as a "reference". The reference subject role is likely born by some entity which is representative of some material or population, but is not itself a target of an investigation's assay sampling - unless say the investigation is longitudinal, and the reference subject is sampled over time. Right? |
I support this rewrite, though with a (fairly minor) critique about the "such that the characteristics or related information are used for comparison or reference [...]" part of the definition: as you say, it's the data about the subject's characteristics that is used for comparison. Perhaps we could rephrase that portion to say |
I like it! Right, its a comparison of data about reference/subjects that we're after! |
Thanks for addressing this. I do think that if you eliminate some of the layers or abstraction here it might be faster to fix these issues, and easier for users to find and use the terms they need. I don't understand the use case for some of these abstract higher level groupings, they don't seem to correspond to normal concepts in fields I'm familiar with. The more layers of abstraction, the more mental reasoning that needs to be done to check consistency between levels, and the the more room for subjective interpretations. My advice would be to focus on concrete concepts, using standard definitions, and groupings that scientists are familiar with (e.g "replicate" as a grouping for technical and biological replicates) |
I apologize for missing the call, and also not previously catching some of
the problems in this ticket. There is a lot of stupid history here. Some of
these roles were specifically created to match clinical study designs - and
written only with human subjects in mind as bearers. Others were intended
to be more general, and we never cleaned it up. I support revisiting the
whole 'role' branch - but there is only so much we can bite of.
…On Wed, Nov 8, 2023 at 11:13 AM Chris Mungall ***@***.***> wrote:
Thanks for addressing this. I do think that if you eliminate some of the
layers or abstraction here it might be faster to fix these issues, and
easier for users to find and use the terms they need. I don't understand
the use case for some of these abstract higher level groupings, they don't
seem to correspond to normal concepts in fields I'm familiar with. The more
layers of abstraction, the more mental reasoning that needs to be done to
check consistency between levels, and the the more room for subjective
interpretations.
My advice would be to focus on concrete concepts, using standard
definitions, and groupings that scientists are familiar with (e.g
"replicate" as a grouping for technical and biological replicates)
—
Reply to this email directly, view it on GitHub
<#1693 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADJX2IXORYNNGSS6YTCN23DYDPKWRAVCNFSM6AAAAAAXWJNKIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBSGQ4TOMZRG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Bjoern Peters
Professor
La Jolla Institute for Immunology
9420 Athena Circle
La Jolla, CA 92037, USA
Tel: 858/752-6914
Fax: 858/752-6987
http://www.liai.org/pages/faculty-peters
|
We are looking into using replicate roles for samples derived from environments, e.g. a sample drawn from a lake with the intention of sequencing (or even a non-biological chemical analysis).
Looking at the labels used in the hierarchy it looks like this is wired for humans or at least whole organisms:
Although not explicitly forbidden, the language ("participant", "subject") seems exclusive of environmental samples.
However if we look deeper at example of usage in OBI:0000097, we see that in fact it is intended to be inclusive:
Lake example: a lake could realize this role in an investigation that assays pollution levels in samples of water taken from the lake.
It seems odd to call a lake a "participant", not everyone speaks BFO.
But then the lake example is inconsistent with the definition on the direct parent (OBI:0000220), "a reference subject role which inheres in an organism or entity of organismal origin"
But then again I see SubClassOf axioms on all these classes that is somewhat more inclusive:
This is inclusive enough for my use case (samples taken from lakes) but is still more restrictive than the example given for OBI:0000097 (unless entire lakes can be specimens?)
I propose one of two paths:
As an aside (and feel free to ignore this part of move to a separate issue), I find the level of abstraction in this hierarchy hard to mentally reason over:
Single is-a is an anti-pattern, and in this case I am having some issues thinking of cohort role as a subclass of biological replicate. I guess this is justified given the very broad definition of biological replicate in OBI. But I don't understand the use case for having such broad abstract inclusive concepts. What's the use case for grouping cohorts with replicates of an RNA-Seq sample? Is this a standard way of thinking about this?
I know it's probably annoying to have someone from outside the ontology come along and suggest wholesale rearrangements without knowing the whole history
* OBI:0000249 ! technical replicate role
* OBI:0000198 ! biological replicate role
cc @turbomam
The text was updated successfully, but these errors were encountered: