does not fit to taxonomy     
Comment submitted by daumkep about 2 years ago on osseous in RadLex
Hi all, to my view, "osseus" does not really fit as a child of "disc composition" as it can appear in many other contexts. A good terminology practice would be to name the preferred terms in a unique way, e.g. "osseus disc composition" and put the term "osseous" on a place such as Qualifier "value->Appearance->osseous". What do you think? All the best Philipp
 
Responses    hide all | show all
 
Agree by beverlycollins about 2 years ago
Thanks, Philipp, we agree that the terms in this category more correctly belong in the "composition" class. We will move them there and move the class "disc composition" to Obsolete Radlex terms, since this term does not seem necessary. Beverly

Add Note

Comment Propose New Term Propose Relationship Change Propose Property Value Change

Comment

* required
Subject *

Body *

Preferred name *

Synonyms (comma-separated list)

Definition *

Parent (start typing to autocomplete) *

Contact information (publically visible)

New Term

* required
Reason for change *

New relationship target (start typing to autocomplete) *

Old relationship target (start typing to autocomplete)

New relationship type *

Contact information (publically visible)

New Relationship / Change Hierarchy

* required
Reason for change *

New property value *

Property id *

Old property value

Contact information (publically visible)

Change Property Value

* required
Reason for change *

Please login to submit notes with your user (to submit anonymously, fill in the CAPTCHA)

Add Note

Comment Propose New Term Propose Relationship Change Propose Property Value Change

Comment

* required
Subject *

Body *

Preferred name *

Synonyms (comma-separated list)

Definition *

Parent (start typing to autocomplete) *

Contact information (publically visible)

New Term

* required
Reason for change *

New relationship target (start typing to autocomplete) *

Old relationship target (start typing to autocomplete)

New relationship type *

Contact information (publically visible)

New Relationship / Change Hierarchy

* required
Reason for change *

New property value *

Property id *

Old property value

Contact information (publically visible)

Change Property Value

* required
Reason for change *

Please login to submit notes with your user (to submit anonymously, fill in the CAPTCHA)