Home.md

 # Welcome to our Wiki
 You have questions about how emg.owl is developed, what the community process behind the development is or how you can adopt terminology from the artefact for your own use or align your metadata with this artefact? Here we are trying to give you the answer!
 
+# Contact 
+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](emglossary.helmholtz-metadaten.de).
 
@@ -18,11 +21,31 @@ OWL is designed to represent rich and complex knowledge about things, groups of
 
 ---
 # How to adopt
-The EM-Glossary provides stable domain-level semantics for adoption into or alignment of application level semantics and other academic use. We envision different levels of adoption. 
-## textual & oral use
-In order to facilitate re-use , we created the front end for easier browsing - put link
+The EM-Glossary provides stable domain-level semantics for adoption in different forms of application level metadata and semantic artefacts. Also definitions from the EM-Glossary may be used in academic work, e.g. when composing scientific texts of papers. 
+Here we provide some suggestions and guidance on how use and technical adoption may look like to harmonise re-use.
+
+## Use in academic writing
+In order to facilitate exploration and use of information in the EM-Glossary for the use in academic writing we provide the [EM-Glossary Web Explorer](emglossary.helmholtz-metadataten.de). This provides a term-level landing page in which minimally the term label, definition and contributors are shown. Further we also supply a citation suggestion at the bottom of the term-page. This can be conveniently copied to clipboard with the copy-button. 
+
+In the future we are planning to provide bib-tex formatted data of the citation suggestion. 
+
+## Technical adoption in application level metadata & semantics
+
+Irrespective your how you want to technically align metadata and semantics with EM-Glossary terminology, we look forward for you contact us about your plans. We are happy to discuss your planned way of alignment, compare to other adoption cases and would be happy to highlight you on our [webpage](emglossary.helmholzt-metadaten.de) as an adopter!
 
-### metadata schemas, records & SKOS vocabularies
+It is clear that different application cases may require closer or less close semantic alignment. Below we provide suggestions on technical implementation in order to harmonise re-use. 
+
+Every term in the EM-Glossary carries an "international resource identifier" (IRI). The IRIs are assigned to classes within emg.owl and are globally unique and fully persistent. The "IRIs assigned to EM-Glossary classes within emg.owl are globally unique and fully persistent to offer term-level dereferenceability of our artefact. IRIs consist of the base URI `purl.helmholtz-metadaten.de/emg/` and a term specific extension in the form of `EMG_XXXXXXXX`. We use numeric term extensions rather than term labels to provide higher stability (e.g. in case term label are altered).
+
+_Referencing classes in emg.owl using the designated class IRI is the minimum requirement for adoption of EM-Glossary terminology_ 
+
+However for adoption of your application- or domain-level metadata and semantics with terminology in the EM-Glossary, we recommend: 
+- align your metadata as close and as in many places as possible with EM-Glossary terminology;
+- use the OWL representation of the EM-Glossary, specifically use IRIs (see below) to reference to classes in emg.owl;
+- cite the EM-Glossary in appropriate places of your output or publication. 
+
+### Metadata schemas
+Application level metadata is often collected and validated with metadata schemas. Different formats may be used for this, such as xml or JSON-Schema. We here highlight the latter as a very commonly used way of defining schemas, but envision similar implementations also in other formats or serialisation. 
 
 ### semantic file formats
 
@@ -31,11 +54,11 @@ In order to facilitate re-use , we created the front end for easier browsing - p
 - import of classes from emg.owl with annotation properties
 - import of classe from emg.owl with partial annotation properties
 - alignment of own class 
-
+- crosswalk with e.g. sssom
+- 
 keep emg IRI
 
 
-However, every case is different and might require stronger or less tight alignment - please feel free to contact us in order to discuss how we could help you with mapping, alignment or harmonisation. 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).
 
 
 How to adapt and use terminology from emg.owl in your application level artefact metadata