Skip to content

Clearly state scope of ecocore on README #135

@cmungall

Description

@cmungall

I think there is a clear need for something like ecocore. We need terms to be able to describe various organismal characteristics/traits that pertain to how organisms interact with larger communities. I think it would be good to be clearer about scope in the documentation (README and on http://obofoundry.org/ontology/ecocore). This is really challenging as the boundaries between PATO, RO, PCO, ENVO, GO, NBO, Micro, OMP etc are a bit fuzzy here as is evidenced by #131

For some context, see this document on challenges in modularity in OBO, particularly wrt ENVO

Some areas where I think the README can be improved:

Through ECOCORE, we look forward to creating a semantic rallying point for the ecological community, a need expressed repeatedly over the past few years at workshops focused on ecological, environmental, and population-based semantics.

What is a semantic rallying point?

Can we provide a link to the workshops?

We're working closely with the Environment Ontology (ENVO), Population and Community Ontology (PCO), the Ontology of Biological Attributes (OBA), and the Neuro Behavior Ontology (NBO) to build a robust and interoperating resource.

IMO adjectives like robust are superfluous.

I think what would be ideal here would be a table listing how ecocore relates to each of these resources. This might also be visualized with a diagram

Naturally, the ontology is importing existing semantics where relevant, and has begun to channel requests for improvement to the hosting ontologies to promote collaboration.

I think you mean importing terms, not importing semantics? #134.

The text "has begun" is >3 years old, so maybe this can be updated now?

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