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

Provide OBO conform names & IDs #7

Closed
StroemPhi opened this issue Jun 16, 2020 · 2 comments · Fixed by #152
Closed

Provide OBO conform names & IDs #7

StroemPhi opened this issue Jun 16, 2020 · 2 comments · Fixed by #152

Comments

@StroemPhi
Copy link
Contributor

StroemPhi commented Jun 16, 2020

http://www.obofoundry.org/principles/fp-003-uris.html

StroemPhi added a commit that referenced this issue Sep 28, 2020
StroemPhi added a commit that referenced this issue Sep 28, 2020
StroemPhi added a commit that referenced this issue Nov 30, 2020
StroemPhi added a commit that referenced this issue Nov 30, 2020
StroemPhi added a commit that referenced this issue Nov 30, 2020
StroemPhi added a commit that referenced this issue Nov 30, 2020
StroemPhi added a commit that referenced this issue Nov 30, 2020
StroemPhi added a commit that referenced this issue Nov 30, 2020
StroemPhi added a commit that referenced this issue Nov 30, 2020
StroemPhi added a commit that referenced this issue Nov 30, 2020
StroemPhi added a commit that referenced this issue Dec 4, 2020
* refactor event type instances #7
* refactor identifer property IDs #7
* refactor has fee ID #7
* refactor has output #7
* refactor all has contributor properties/subproperties #7
* refactor committee class #7
* refactor "occurent part of" & "has occurent part" subproperties #7
* refactor "occurs in" subproperties #7
* refactor DataProperties #7
* update example instances #7
* fix TTL indentation
@StroemPhi StroemPhi changed the title Provide BFO conform names & IDs Provide OBO conform names & IDs Jun 23, 2021
@StroemPhi
Copy link
Contributor Author

At the moment I still use a mix of numeral and textual IDs. But this will be fixed before v1. The idea is to set better ID ranges depending on the type of class or property (e.g. all material entities share an ID range). I didn't want to mess around with this now, as AEON is stil in development.

@StroemPhi
Copy link
Contributor Author

I hope to have replaced all textual IDs in #152, apart from the ones that have been deprecated. Those will probably be deleted before making a stable release.

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

Successfully merging a pull request may close this issue.

1 participant