Skip to content

Parent Term Revision Suggestion #244

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

Open
ben-norton opened this issue Apr 16, 2025 · 1 comment
Open

Parent Term Revision Suggestion #244

ben-norton opened this issue Apr 16, 2025 · 1 comment
Assignees
Labels
class:TaxonConcept Organized in the TaxonConcept class

Comments

@ben-norton
Copy link
Member

Term: parent
Class: TaxonConcept
Submitted By: Ben Norton [email protected]

General Recommendations

  1. Although the context is clear, the term parent may be too broad. Adding a qualifier to both terms to indicate that the value should be a concept within a taxonomic hierarchy such as parentConcept
  2. Currently, the definition for parent is 'The direct parent in a classification'.
    The term shouldn't be used in the definition whenever possible (although this can be quite hard at times, I had to define color recently).
    Does this include the subsidiary ranks, such as superfamily or suborder? I recommend rewriting the definition to eliminate the use of parent and clarify the key/subsidiary rank question.
    An alternate definition similar to 'The taxon concept belonging to the rank that is the direct ancestor of the current concept in a taxonomic hierarchy".
  3. Statements should not be repeated in the notes and usage fields.
  4. Suggested addition to the usage notes: "In a taxonomic classification hierarchy, each concept may only have one and only one parent except for the root node. Therefore, a taxon concept should only have one parent value. The parent rank may be a key or subsidiary rank."
@ben-norton ben-norton added the class:TaxonConcept Organized in the TaxonConcept class label Apr 16, 2025
@nielsklazenga
Copy link
Member

nielsklazenga commented Apr 16, 2025

Thanks @ben-norton,

  1. I prefer just 'parent' and 'child'. I think they are unambiguous, as it is obvious that parents and children have to be of the same class. Also, the 'parent' property might be on the Taxon Concept, which is ontologically correct, but it might be practical to use it on the Taxon Name as well (not sure that is an argument). Other people might think differently though, so let's discuss further and we'll do a poll in the end.
  2. Agreed, will do. Not sure how to do it yet, maybe 'immediate higher taxon concept in a hierarchical classification'. This should be further discussed once it is done, as while I agree that self-referencing definitions should be avoided, the terms 'parent' and 'child' are very well understood, so avoiding them might make the definition less clear. I think that the question of the principal vs secondary ranks should not be in the definition, as the rank of the parent (or child) does not come into it and even hierarchical classifications do not have to be ranked (but we can add a note to that extent).
  3. Agreed, will check this out.
  4. Nice, thanks, I will add that.

@nielsklazenga nielsklazenga self-assigned this Apr 16, 2025
nielsklazenga added a commit that referenced this issue Apr 17, 2025
- change definition and comments for `parent` in accordance with #244.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
class:TaxonConcept Organized in the TaxonConcept class
Projects
None yet
Development

No branches or pull requests

2 participants