Skip to content
Snippets Groups Projects
Commit 68229bc3 authored by Abril Azocar Guzman's avatar Abril Azocar Guzman
Browse files

fix typos

parent c1a30e74
No related branches found
No related tags found
1 merge request!5Content for repo readme wiki
Pipeline #365988 passed
......@@ -4,32 +4,32 @@
# Welcome to the EM-Glossary
We work towards harmonized metadata in electron microscopy!
Visit our our [webpage](emglossary.helmholtz-metadaten.de) and start developing with us in our develop with us in our [communty repository](https://codebase.helmholtz.cloud/em_glossary/em_glossary)!
Visit our [webpage](emglossary.helmholtz-metadaten.de) and start developing with us in our [community 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. With this we offer electron microscopy terminology that was harmonized through a community process in a machine exploitable way. It is intended for integration and adaption into application level semantics and metadata to build bridges between applicaiton cases.
### In this repository:
This is where the EM_Glossary OWL artefact is built, documented, released and maintained. We offer electron microscopy terminology that was harmonized through a community process in a machine-exploitable way. It is intended for integration and adaption into application level semantics and metadata to build bridges between application cases.
In this repository you will find:
| :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 and some of its inputs |
| :file_folder: documentation | documentation build and deployment inputs for [WIDOCU](https://github.com/dgarijo/Widoco) |
| :file_folder: old versions | old versions of emg.owl |
| :file_folder: documentation | documentation build and deployment inputs for [WIDOCO](https://github.com/dgarijo/Widoco) |
| :file_folder: previous versions | previous versions of emg.owl |
| :page_facing_up: [CITATION.cff](https://codebase.helmholtz.cloud/em_glossary/em_glossary_owl/CITATION.cff) | information on how to cite this repository |
| :page_facing_up: [codemeta.json](https://codebase.helmholtz.cloud/em_glossary/em_glossary_owl/codemeta.json) | complementary metadata for here deposited files |
| :page_facing_up: [License](https://codebase.helmholtz.cloud/em_glossary/em_glossary_owl/LICENSE) | copyright and licensing files |
### 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 aggregated 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).
### Further information in our wiki:
You have questions - 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 aggregated in our [community 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
### 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
### Acknowledgements
This work was supported by the [Helmholtz Metadata Collaboration (HMC)](www.helmholtz-metadaten.de) and the [NFDI-MatWerk](https://nfdi-matwerk.de/) consortium 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.
<p align="center">
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment