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

xref-differentiation #2

Closed
GoogleCodeExporter opened this issue Mar 12, 2015 · 4 comments
Closed

xref-differentiation #2

GoogleCodeExporter opened this issue Mar 12, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

Consider differentiating xrefs. 

Common uses:

- To designate a source of some item (e.g. the source of a definition, of a 
synonym)
- To designate a non-ontology resource about the thing the term denotes

(continue the list)

Original issue reported on code.google.com by alanruttenberg@gmail.com on 3 Nov 2010 at 2:59

@GoogleCodeExporter
Copy link
Author

Another xref case: example of usage

Original comment by alanruttenberg@gmail.com on 3 Nov 2010 at 3:38

@GoogleCodeExporter
Copy link
Author

An xref in a definition should denote the source of the definition - may be a 
person, a meeting, a publication, a class from another ontology.

An xref in a synonym should denote a usage of a label to denote the class, or a 
source of the synonym (these two cases seem indistinguishable from me - e.g. 
the source of a synonym in GO may be a CHEBI class, and this is also an 
instance of usage).

An xref at the level of a Term stanza has no strong semantics. However, 
additional semantics can be provided on a per prefix basis using obof1.4 header 
macros (e.g. treat-xrefs-as-equivalent-to)


Original comment by cmung...@gmail.com on 3 Nov 2010 at 4:51

@GoogleCodeExporter
Copy link
Author

An example of usage is typically use of the term in a paper or other narrative, 
so listing of a synonym in Chebi, or biothesaurus would not count as such. 
Perhaps that doesn't matter. 

treat-xrefs-as-equivalent-Tag semantics not yet in spec. Todo.

Providing this documentation in the spec may solve the problem adequately.

Original comment by alanruttenberg@gmail.com on 3 Nov 2010 at 5:17

@GoogleCodeExporter
Copy link
Author

treat-xrefs-as-equivalent-Tag added to spec.

The translation rules for xrefs should now be complete. Guidelines for usage 
belong elsewhere

Original comment by cmung...@gmail.com on 16 Jun 2011 at 10:29

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant