| ... | ... | @@ -5,7 +5,7 @@ You have questions about how emg.owl is developed, what the community process be |
|
|
|
Write an email to hmc@fz-juelich.de or hmc-matter@helmholtz-berlin.de or talk to us directly on [HMC public mattermost](https://mattermost.hzdr.de/hmc-public).
|
|
|
|
|
|
|
|
# About the EM Glossary
|
|
|
|
The EM_Glossary groups offers terminology that was harmonised through a community process. The full provenance of this process is documented in our [community repository](https://codebase.helmholtz.cloud/em_glossary/em_glossary) - please feel free to contribute to the development there. The full extend of the current artefact can be conveniently explored in our [webpage](https://emglossary.helmholtz-metadaten.de).
|
|
|
|
The EM_Glossary group offers terminology that was harmonised through a community process. The full provenance of this process is documented in our [community repository](https://codebase.helmholtz.cloud/em_glossary/em_glossary). Please feel free to contribute to the development by writing comments and opening issues there. The full extend of the current artefact can be conveniently explored in our [webpage](https://emglossary.helmholtz-metadaten.de).
|
|
|
|
|
|
|
|
The idea behind the EM_Glossary is to offer community accepted, harmonised domain-level semantics for adoption to the application level. Using the EM_Glossary as a domain level bridge we intend to facilitate metadata alignment between different application cases such as metadata schemas that are recorded with different instruments or annotated using different dialects.
|
|
|
|
|
| ... | ... | |
| ... | ... | |
