MetaData-discussions.md

@@ -27,11 +27,21 @@ Issues:
 
 - Astronomy Thesaurus (proposal from Mark)
 
-
 - What is the goal here? Use case?
 
 - We need to differentiate between what is requested (because it’s used by a service) and suggestion for good practice
 
+[DISCUSSION]: Discussed during FG2 call on 18-02-2022: https://indico.in2p3.fr/event/26263/
+- Be careful to not avoid overlap with existing vocabulary if we use a  keyword for OSSR classification
+- However, the recommended keywords should stay generic enough to still have meaning in xx years
+- the keyword `jupyter-notebook` for example does not mean that it is runnable by a specific service (that would  require specifying versions and environments) but simply that it contains a jupyter notebook
+- no specific keyword is required - they are overall recommended
+- Issue #68 got closed
+- Issue #75: we will include the Astronomy Thesaurus in the recommendation for keywords
+- We stay open to suggestions for other widely used  thesaurus for other communities  (particle physics in particular)
+
+
+
 ## 2. Software / Analysis environment building
 
 - Goal: being able to install the  environment for the provided software or analysis
@@ -47,6 +57,12 @@ Issues:
 
  - My opinion: we should come up with a way to **require** these
 
+[DISCUSSION]: Discussed during FG2 call on 18-02-2022: https://indico.in2p3.fr/event/26263/
+- We want to mention clearly that an environment must be provided in the policy
+-  the build instruction should link to an internal document in codemeta (good practice)
+- the documentation URL is required but we can't require the human-readable documentation itself to be included in the record (this documentation is often automatically built)
+
+
 ## 3. Software / Analysis running environment
 
 - Goal: being able to run the analysis in an existing environment (= docker container)