Skip to content

best practice for shadow classes between disease and disorder in OGMS #175

@cmungall

Description

@cmungall

When I see a lot of OGMS-based ontologies, I see lots of shadow classes created.

For example

  • neurological disease has material basis neurological disorder
  • heart disease has material basis heart disorder

is this considered good practice? what are best practices for naming explicit shadow classes? what is a good exemplar ontology here?

(this shadow class problem persists with other branches, I often see X disease, X diagnosis, X disorder, X process, .... but for the purposes of this issue I am interested in disease and disorder branches)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions