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

Jump to bottom

allow property_value tags in ontology headers #71

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

allow property_value tags in ontology headers #71

GoogleCodeExporter opened this issue Mar 12, 2015 · 4 comments
Labels
auto-migrated Priority-Medium Type-Specification

Comments

@GoogleCodeExporter
Copy link 

currently these are allowed in all stanza types but not headers

property_value tags in headers would be mapped to ontology annotations. obof 
could then support an open-ended list of ontology metadata - dc:creator, IAO, 
etc.

Impact on current tools expected to be minimal. OE will roundtrip these without 
necessarily understanding them.

Original issue reported on code.google.com by cmung...@gmail.com on 17 Jul 2012 at 12:28
@GoogleCodeExporter
Copy link
Author 

Parsing and writing obo is simple. How do we translate them to owl 
(specification?) and safely back to obo?

Original comment by HDie...@lbl.gov on 31 Jul 2012 at 10:30

@GoogleCodeExporter
Copy link
Author 

implement in r558

Original comment by HDie...@lbl.gov on 17 Sep 2012 at 11:15

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author 

do you have an example of "property_value" appearing in the header?

Original comment by erick.an...@gmail.com on 25 Feb 2013 at 9:37

@GoogleCodeExporter
Copy link
Author 

http://purl.obolibrary.org/obo/uberon.obo

Original comment by cmung...@gmail.com on 25 Feb 2013 at 11:25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Specification
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter