create a recipe about expressing data use

_config.yml

@@ -1,4 +1,4 @@
-#######################################################################################
+ #######################################################################################
 # Book settings
 title                       :  # The title of the book. Will be placed in the left navbar.
 author                      : The FAIRplus project members  # The author of the book

_toc.yml

@@ -105,6 +105,7 @@
     - file: content/recipes/reusability/ATI_licensing_software
     - file: content/recipes/reusability/ATI_licensing_data
     # - file: content/recipes/reusability/license-selection
+    - file: content/recipes/reusability/expressing-data-use
     - file: content/recipes/reusability/provenance
     - file: content/recipes/reusability/community-standards
 

content/recipes/help/recipe-template.md

@@ -206,6 +206,20 @@ import holoview
 
 ### ... create workflow figures
 
+If you want to include figures, please use the following 
+
+
+
+```{figure} ./my_figure.svg
+---
+width: 700px
+name: the figure title
+alt: something to display if the link to the figure is broken
+---
+the proper caption for the figure.
+```
+
+
 one may use the following **[mermaid](https://mermaid-js.github.io/mermaid/#/)** syntax:
 
 ````{panels} 

content/recipes/reusability/10.1007_978-3-030-31095-0_3.bib

@@ -0,0 +1,19 @@
+@InProceedings{10.1007/978-3-030-31095-0_3,
+author="De Vos, Marina
+and Kirrane, Sabrina
+and Padget, Julian
+and Satoh, Ken",
+editor="Fodor, Paul
+and Montali, Marco
+and Calvanese, Diego
+and Roman, Dumitru",
+title="ODRL Policy Modelling and Compliance Checking",
+booktitle="Rules and Reasoning",
+year="2019",
+publisher="Springer International Publishing",
+address="Cham",
+pages="36--51",
+abstract="This paper addresses the problem of constructing a policy pipeline that enables compliance checking of business processes against regulatory obligations. Towards this end, we propose an Open Digital Rights Language (ODRL) profile that can be used to capture the semantics of both business policies in the form of sets of required permissions and regulatory requirements in the form of deontic concepts, and present their translation into Answer Set Programming (via the Institutional Action Language (InstAL)) for compliance checking purposes. The result of the compliance checking is either a positive compliance result or an explanation pertaining to the aspects of the policy that are causing the non-compliance. The pipeline is illustrated using two (key) fragments of the General Data Protect Regulation, namely Articles 6 (Lawfulness of processing) and Articles 46 (Transfers subject to appropriate safeguards) and industrially-relevant use cases that involve the specification of sets of permissions that are needed to execute business processes. The core contributions of this paper are the ODRL profile, which is capable of modelling regulatory obligations and business policies, the exercise of modelling elements of GDPR in this semantic formalism, and the operationalisation of the model to demonstrate its capability to support personal data processing compliance checking, and a basis for explaining why the request is deemed compliant or not.",
+isbn="978-3-030-31095-0"
+}
+

content/recipes/reusability/data-usage-mermaid.mmd

@@ -0,0 +1,31 @@
+graph TD;
+	DS(Dataset):::box --> |has| A:::box
+	A(Policy) -->|is_a| B(Data Use Agreement):::box
+	B --> F{what use is allowed use?}:::box1
+	B --> G{what use is prohibited?}:::box1
+	B --> H{what obligations?}:::box1
+	C -->|Yes| D(List of Countries):::box
+	D -->|uses|DD(SO-3166 or GAZ ontology):::box
+
+	F --> C{ geographically <br> restriction ? }:::box1
+	G --> C{geographically <br> restriction ? }
+	H --> C{geographically <br> restriction ? }
+
+	F --> T{ temporal <br> restriction ? }:::box1
+	G --> T{ temporal <br> restriction ? }
+	H --> T{ temporal <br> restriction ? }
+
+	T -->|Yes| P(List of Dates, Periods):::box
+	P -->|uses|PP(ISO-8601):::box
+
+	F --> X{ domain <br> restriction ? }:::box2
+	G --> X{ domain <br> restriction ? }
+	H --> X{ domain <br> restriction ? }
+
+	X -->|Yes| Z(List of domains):::box
+	Z -->|uses|ZZ(Data Use Ontology and Disease Ontology):::box
+
+	classDef box font-family:avenir,font-size:14px,fill:#B30000,stroke:#222,color:#fff,stroke-width:1px
+	classDef box1 font-family:avenir,font-size:14px,fill:orange,stroke:#222,color:#fff,stroke-width:1px
+	classDef box2 font-family:avenir,font-size:14px,fill:purple,stroke:#222,color:#fff,stroke-width:1px
+	linkStyle 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19 stroke:#B30000,stroke-width:1px,color:#B30000,font-family:avenir;