Skip to content
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

more structure in XLMOD.obo #60

Closed
edeutsch opened this issue Jun 23, 2016 · 8 comments
Closed

more structure in XLMOD.obo #60

edeutsch opened this issue Jun 23, 2016 · 8 comments

Comments

@edeutsch
Copy link
Contributor

I think it would be very valuable to add some hierarchical structure to XLMOD.obo. right now there are no parents. I propose that we have a top-level term, perhaps similar to the PSI-MS top term:

[Term]
id: XL:00000
name: Proteomics Standards Initiative cross-linking controlled vocabulary
def: "Proteomics Standards Initiative cross-linking controlled vocabulary." [PSI:XL]

and then a child something like:

[Term]
id: XL:00012
name: cross-linking entity
def: "Entity relevant to the domain of cross-linking in proteomics." [PSI:XL]
is_a: XL:00000 ! Proteomics Standards Initiative cross-linking attribute
relationship: part_of XL:00000 Proteomics Standards Initiative cross-linking controlled vocabulary

[Term]
id: XL:00013
name: cross-linker
def: "Compound that can link one polymer chain to another." [PSI:XL]
is_a: XL:00012 ! cross-linking entity

This would allow us to grow the CV in a more tidy fashion, plus would allow the mapping file to stipulate that location X is the right place to put a child of XL:00013. I don't think this is possible in the current layout.

What do you think?

@germa
Copy link
Collaborator

germa commented Jun 29, 2016

maybe we can structure it even further like e.g.

[Term]
id: XL:00000
name: Proteomics Standards Initiative cross-linking controlled vocabulary
def: "Proteomics Standards Initiative cross-linking controlled vocabulary." [PSI:XL]

[Term]
id: XL:00001
name: cross-linking entity
def: "Entity relevant to the domain of cross-linking in proteomics." [PSI:XL]
relationship: part_of XL:00000 Proteomics Standards Initiative cross-linking controlled vocabulary

[Term]
id: XL:00002
name: cross-linker
def: "Compound that can link one polymer chain to another." [PSI:XL]
is_a: XL:00001 ! cross-linking entity

[Term]
id: XL:00003
name: monofunctional cross-linker
def: "A cross-linker reagent with one reactive group." [PSI:XL]
is_a: XL:00002 ! cross-linker

[Term]
id: XL:00004
name: bifunctional cross-linker
def: "A cross-linker reagent with two reactive groups." [PSI:XL]
is_a: XL:00002 ! cross-linker

[Term]
id: XL:00005
name: homobifunctional cross-linker
def: "A cross-linker reagent with identical reactive groups at either end of the spacer arm." [PSI:XL]
is_a: XL:00004 ! bifunctional cross-linker

[Term]
id: XL:00006
name: heterobifunctional cross-linker
def: "A cross-linker reagent with different reactive groups at either end of the spacer arm." [PSI:XL]
is_a: XL:00004 ! bifunctional cross-linker

[Term]
id: XL:00007
name: photoreactive cross-linker
def: "A cross-linker reagent that becomes reactive when exposed to ultraviolet or visible light." [PSI:XL]
synonym: "non-selective cross-linker" EXACT [PSI:XL]
is_a: XL:00002 ! cross-linker

[Term]
id: XL:00008
name: trifunctional cross-linker
def: "A cross-linker reagent acting as label (e.g. biotin) transfer reagent." [PSI:XL]
is_a: XL:00002 ! cross-linker

[Term]
id: XL:00009
name: zero-length cross-linker
def: "A cross-linker reagent causing direct conjugation of carboxylates (-COOH) to primary amines (-NH2) without becoming part of the final crosslink (amide bond) between the target molecules." [PSI:XL]
is_a: XL:00002 ! cross-linker

@lutzfischer
Copy link
Contributor

Some points:

[Term]
id: XL:00003
name: monofunctional cross-linker
def: "A cross-linker reagent with one reactive group." [PSI:XL]
is_a: XL:00002 ! cross-linker

Don't think you could call that a cross-linker in the sense of XL:00002
Can we call it something along the lines of "cross-linker related PTM" or "cross-linker derived PTM"

Also

[Term]
id: XL:00008
name: trifunctional cross-linker
def: "A cross-linker reagent acting as label (e.g. biotin) transfer reagent." [PSI:XL]
is_a: XL:00002 ! cross-linker

trifunctional is ambiguous - you can have three groups on a cross-linker - but for some cross-linker that is used purification (e.g. biotin) on others that is just another group that is supposed to react with amino-acids (e.g. three nhs-ester groups.)

So maybe could name this to

[Term]
id: XL:00008
name: label transfer reagent
def: "label (e.g. biotin) transfer reagent." [PSI:XL]

and flag Terms with an has relationship.

Lastly

[Term]
id: XL:00005
name: homobifunctional cross-linker
def: "A cross-linker reagent with identical reactive groups at either end of the spacer arm." [PSI:XL]
is_a: XL:00004 ! bifunctional cross-linker

[Term]
id: XL:00006
name: heterobifunctional cross-linker
def: "A cross-linker reagent with different reactive groups at either end of the spacer arm." [PSI:XL]
is_a: XL:00004 ! bifunctional cross-linker

Can we rename these to homofunctional and heterofunctional? And not flag them as bifunctional?

Do we need to have separate categories for bifunctional? We have the number of reatcive sites as part of the cross-linker definition.

[Term]
id: XL:00000
name: Proteomics Standards Initiative cross-linking controlled vocabulary
def: "Proteomics Standards Initiative cross-linking controlled vocabulary." [PSI:XL]


[Term]
id: XL:00001
name: cross-linking entity
def: "Entity relevant to the domain of cross-linking in proteomics." [PSI:XL]
relationship: part_of XL:00000 Proteomics Standards Initiative cross-linking controlled vocabulary

[Term]
id: XL:00002
name: cross-linker
def: "Compound that can link two or more polymer chain." [PSI:XL]
is_a: XL:00001 ! cross-linking entity

[Term]
id: XL:00003
name: cross-linker related PTM
def: "A cross-linker reagent with one reactive group." [PSI:XL]
relationship: part_of XL:00000 Proteomics Standards Initiative cross-linking controlled vocabulary

[Term]
id: XL:00004
name: homo-functional cross-linker
def: "A cross-linker reagent with identical reactive groups at each end of the spacer arm." [PSI:XL]
is_a: XL:00002 ! cross-linker

[Term]
id: XL:00005
name: hetero-functional cross-linker
def: "A cross-linker reagent with at least two different reactive groups." [PSI:XL]
is_a: XL:00002 ! cross-linker

[Term]
id: XL:00006
name: photoreactive cross-linker
def: "A cross-linker reagent that becomes reactive when exposed to ultraviolet or visible light." [PSI:XL]
synonym: "non-selective cross-linker" EXACT [PSI:XL]
is_a: XL:00002 ! cross-linker

[Term]
id: XL:00007
name: label transfer reagent
def: "NOT SURE WHAT TO WRITE HERE" [PSI:XL]
relationship: part_of XL:00000 Proteomics Standards Initiative cross-linking controlled vocabulary

[Term]
id: XL:00008
name: zero-length cross-linker
def: "A cross-linker reagent causing direct conjugation without becoming part of the final crosslink  between the target molecules." [PSI:XL]
is_a: XL:00002 ! cross-linker

@andrewrobertjones
Copy link
Contributor

Proposal seems reasonable, @germa and @lutzfischer - please continue to work on this

Need to add lines to mapping file for linking to Unimod for regular mods and to XLMOD for these, so need appropriate branch node to link to. thanks Andy

@germa
Copy link
Collaborator

germa commented Jul 12, 2016

@germa
Copy link
Collaborator

germa commented Jul 13, 2016

Had to change the identifiers from XL:nnnnn to XLMOD:nnnnn in order to avaoid name clashes, as reported by Chris Mungall, see OBOFoundry/OBOFoundry.github.io#284

@edeutsch
Copy link
Contributor Author

okay, fine. This means all the XL example files will need to be changed.

@andrewrobertjones
Copy link
Contributor

@germa @edeutsch Can we now close this thread? The new OBO looks sensible to me

@germa
Copy link
Collaborator

germa commented Jul 18, 2016

yes, the restructuring of xlmod.obo is finished

@germa germa closed this as completed Jul 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants