-
Notifications
You must be signed in to change notification settings - Fork 24
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
Comments
maybe we can structure it even further like e.g. [Term] [Term] [Term] [Term] [Term] [Term] [Term] [Term] [Term] [Term] |
Some points:
Don't think you could call that a cross-linker in the sense of XL:00002 Also
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
and flag Terms with an has relationship. Lastly
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.
|
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 |
|
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 |
okay, fine. This means all the XL example files will need to be changed. |
yes, the restructuring of xlmod.obo is finished |
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?
The text was updated successfully, but these errors were encountered: