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

Proposed NBO - ABO merges #30

Open
3 tasks
dosumis opened this issue Oct 25, 2015 · 4 comments
Open
3 tasks

Proposed NBO - ABO merges #30

dosumis opened this issue Oct 25, 2015 · 4 comments
Assignees

Comments

@dosumis
Copy link
Collaborator

dosumis commented Oct 25, 2015

A list of propose NBO-ABO merges.

  • For each case,
    • NBO parentage should be considered, NBO flattened where needed
    • ABO subClasses should have names changed to be less ambigous when considered in isolation
    • Old names need to be retained as synonyms with some dedicated type
    • All ABO terms moved across for merge must have NBO IDs in a dedicated ID range

flee SubClassOf anti-predation

flee > flee predator

@DitchingIt
Copy link
Collaborator

Is this issue closed?

@matentzn
Copy link
Collaborator

NBO does not really get much systematic development in the last 3 years or so... None of these issues are closed!

@pmidford
Copy link
Collaborator

Keep it open for now, I'll review in the next few days.

@pmidford
Copy link
Collaborator

As far as I can tell, most of these haven't been addressed. The text definition of flee certainly sounds like antipredator behavior, so maybe it should be moved, but then what about fleeing physical threats such as fire or flooding? If we move flee, we should a term for moving from other, non-predator, threats.

I support adding maintenance behavior from ABO; I've never been happy with the motivation behavior synonymy.

Also agree with nest building, as having a second parent under refuge creation.

So, unless there are objections, lets just do these and then we can close this.

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

5 participants