obophenotype / obophenotype/uberon
standardize on creation date property
Open
Nobody has claimed this yet.
- Dominant language
- Emacs Lisp
- Stars
- 163
- Forks
- 43
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 5
Description
These sneaked in:
property_value: http://purl.org/dc/elements/1.1/date 2020-09-08T15:05:03Z xsd:dateTime
this is not in the allowed list of properties so this is blocking release
- fix these to be creation_date OE style for now
- document the standard way of doing this and setting up Protege for uberon @nicolevasilevsky - align this with GO, Mondo, etc
- getting the allowed property checks into travis. Preferably not the existing perl. We need shex for OBO any ideas @balhoff @matentzn
We should do the same for creator... and do this more generally for other ontologies
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the unchecked Travis allowed-property validation item, the existing Perl checks, and the documented Protege setup for creation_date and creator. Confirm the agreed OBO standard with the related ontology practices mentioned in the issue. Done means the property standard is documented and validation covers the relevant ontologies without relying on the existing Perl check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- ci-cd, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100