README.md

# EM Glossary - *OWL* 
<img src="https://codebase.helmholtz.cloud/em_glossary/em_glossary/-/raw/main/EMGlossary.png" alt="EM Glossary Group Logo" width="400"/> 

# Welcome to the EM-Glossary
We work towards harmonized metadata in electron microscopy!

Visit our our [webpage](emglossary.helmholtz-metadaten.de) and develop with us in our [communty repository](https://codebase.helmholtz.cloud/em_glossary/em_glossary)!

### in this repository:
This is where the EM_Glossary OWL artefact is build, documented, released and maintained. Via this machine readible artefact we offer electron microscopy terminology that was harmonized through a community process to be integrated and adapted to application level semantics and metadata (see also bellow).

In this repository you will fine:
|--|--|
| :page_facing_up: [**emg.owl**](https://codebase.helmholtz.cloud/em_glossary/em_glossary_owl/emg.owl) | :bangbang: **the current version of the EM_Glossary OWL artefact** :bangbang: |
| :file_folder: development | development files for the OWL artefact such as the automated build pipeline, its requirements |
| :file_folder: documentation | input for the build and deployment of the onotology documentaton with WIDOCU |
| :file_folder: old versions | prior versions of emg.owl |
| some administration... | |
| :page_facing_up: [CITATION.cff](https://codebase.helmholtz.cloud/em_glossary/em_glossary_owl/CITATION.cff) | information regarding how to cite this repository |
| :page_facing_up: [codemeta.json](https://codebase.helmholtz.cloud/em_glossary/em_glossary_owl/codemeta.json) | complementary metadata for files in this respository |
| :page_facing_up: [License](https://codebase.helmholtz.cloud/em_glossary/em_glossary_owl/LICENSE) | :copyright:	file with licensing information regarding files in this repository |


### further information in our WIKI: 
You have quesitons - our WIKI[https://codebase.helmholtz.cloud/em_glossary/em_glossary_owl/-/wikis/home] has the answer: Find out how we build emg.owl from the resources in our [communty repository](https://codebase.helmholtz.cloud/em_glossary/em_glossary) through an automated pipeline, how we handle the release cycle of emg.owl or how you can adopt the EM Glossary into your metadata schema or ontology. For more information regarding the EM Glossary initiative and its scope, please visit our [Webpage](emglossary.helmholtz-metadaten.de).

### please cite this repository as
TBD 


### acknowledgements
This work was supported by the [Helmholtz Metadata Collaboration (HMC)](www.helmholtz-metadaten.de) and the NFDI consortum [MatWerk](https://nfdi-matwerk.de/) in the context of the work of the association German National Research Data Infrastructure (NFDI) e.V.. NFDI is financed by the Federal Republic of Germany and the 16 federal states and funded by the Federal Ministry of Education and Research (BMBF) – funding code M532701 / the Deutsche 
 Forschungsgemeinschaft (DFGs, German Research Foundation) under the National Research Data Infrastructure – NFDI 38/1 – project number 460247524.

<img src="https://github.com/Materials-Data-Science-and-Informatics/Logos/blob/main/HMC/HMC_Logo_M.png?raw=true" alt="HMC" width="300"/> 
<img src="https://nfdi-matwerk.de/fileadmin/_processed_/8/3/csm_Logo_NFDI-MatWerk-1000px__1__d04d7a77da.png" alt="MatWErk" width="100"/> 
<img src="https://github.com/Materials-Data-Science-and-Informatics/Logos/blob/main/FZJ/Logo_FZ_Juelich_412x120_rgb_jpg.jpg?raw=true" alt="FZJ" width="200" />
<img src="https://www.helmholtz-berlin.de/media/design/logo/hzb-logo.svg" width="300" alt="HZB" style="float:left"/>