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

How to model abstract concepts, like a hypothesis, a synthesis idea, an algorithm in EMMO ? #309

Closed
markdoerr opened this issue Jun 18, 2024 · 2 comments

Comments

@markdoerr
Copy link

Since EMMO is also a top level ontology for many scientific eras,
shouldn't it be able to also describe abstract concepts, like
a hypothesis of an experiment, a chemical synthesis idea, an algorithm for a computer program ?

How would one model such abstract concepts in EMMO ?

@jesper-friis
Copy link
Contributor

EMMO is nomenalistic. So abstract concepts are described by classes.
All individuals must stand for real world entities.

@emanueleghedini
Copy link
Member

Hypothesis, synthesis ideas, algorithms are quite different things and not abstract entities. What goes under the term 'abstract' is really extremely broad and not univocally defined (https://plato.stanford.edu/entries/abstract-objects/)

For example: algorithms are represented using standardised representations. So an algorithm is e.g., a flow chart, a text, that may be the starting point for a derived entity such as the program implementing it. The design of a bridge is a set of documents (drawings, numbers, simulations, schematics) and the real bridge is an entity standing for the blueprint (and viceversa, depending on the perspective). Also an idea is a mental representation.

So no abstract entities here. What you called idea, hypothesis, algorithm, is simply a data entity. On paper, electronic device, neuron, ...

If with abstract you refer to entities outside space and time, then they simply don't exist as physical entities and we don't speak about what we cannot speak of ;-)

If you refer to general ideas of e.g. cat, than we are pure nominalistics: the idea of a cat is simply the set of all entities identified as cats. So classes, for the EMMO, are the entities representing this archetypal ideas and individuals are instances, i.e. that specific cat, and the rdf:type relation is the instantiation.
In other ontologies there is the possibility to declare an instantiation relation between individuals, so that one is of higher order than another. We don't think this is the best approach for an ontology based on scientific evidences.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants