From 77cfb079156e24936d0a3e778c5a185efc835248 Mon Sep 17 00:00:00 2001 From: Chiara Braghin Date: Sun, 19 May 2024 09:18:35 +0200 Subject: [PATCH] sistemate parentesi nelle politiche di ex 3.1 --- pipeline_template_example.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pipeline_template_example.tex b/pipeline_template_example.tex index 42423c4..6b6dc19 100644 --- a/pipeline_template_example.tex +++ b/pipeline_template_example.tex @@ -63,8 +63,8 @@ % 5° NODO % The fourth stage consists of vertex \vi{6}, managing data storage. Data protection annotation \myLambda(\vi{6}) refers to policies \p{3} and \p{4}, which apply different data transformations depending on the relation between the dataset and the service region. -If the service region is the dataset origin (\p{3}: $\{(service\_region=dataset\_origin)\}$) , the dataset is anonymized at level $l_0$ (\tp{0}). -If the service region is in a partner region (\p{4}: $\{(service,region={NY,NH})\}$), the dataset is anonymized at level $l_1$ (\tp{1}). +If the service region is the dataset origin (condition $(service\_region=dataset\_origin)$ in \p{3}) , the dataset is anonymized at level $l_0$ (\tp{0}). +If the service region is in a partner region (condition $(service\_region=\{NY,NH\})$ in \p{4}), the dataset is anonymized at level $l_1$ (\tp{1}). Functional requirement \F{7} prescribes a dataset as input and the URI of the stored data as output. % 6° NODO %