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

💡 Vocabulary Structure Proposal #33

Closed
markdoerr opened this issue Dec 13, 2023 · 3 comments
Closed

💡 Vocabulary Structure Proposal #33

markdoerr opened this issue Dec 13, 2023 · 3 comments
Labels
discussion This needs more discussion

Comments

@markdoerr
Copy link

Description

For the overall structure of the repository I would suggest the following:
General approach: from generic / common terms to specific (collecting most generic terms in a kind of "top-level vocabulary") - each term should be defined, if possible, only once, and as broad as possible:

  1. general chemistry / physics ( molecules, reactions, physical measurements, light, absorbance, ...)
  2. catalysis (terms that are in common to all areas of catalysis (catalyst, .... )
  3. one vocabulary for each catalytic field: heterogen. cat., homogen., biocatalysis, photocatalysis, electrocatalysis
  4. process and process modelling vocabulary (reactors, heat-exchange, material exchange, ...)

(I will create the corresponding sections in the config file)

@dalito
Copy link
Member

dalito commented Dec 13, 2023

We should discuss with @nmoust . - I proposed to him some guidelines how to model (in private). For example we should use broader/narrower for is_a relation put not for part_of. part_of is collection territory.

@dalito
Copy link
Member

dalito commented Feb 13, 2024

@markdoerr - #48 is the result of what @nmoust and I had worked on internally. We propose few top level concepts and give some reasons for the proposed structure.

@dalito dalito added the discussion This needs more discussion label Feb 13, 2024
@dalito
Copy link
Member

dalito commented Oct 8, 2024

Closing this in favor of #48. If required we can create specific new issues later (after finishing #48).

@dalito dalito closed this as completed Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion This needs more discussion
Projects
None yet
Development

No branches or pull requests

2 participants