From 2da5efa973dee66c12dd6f3c2a1b4dfc4f6ef887 Mon Sep 17 00:00:00 2001
From: Volker Schukai <volker.schukai@schukai.com>
Date: Thu, 5 May 2022 00:39:43 +0200
Subject: [PATCH] chore: commit save point

---
 ...nts_manager_and_run_requirement_report.xml |  13 +
 README.md                                     |  58 ++++
 application/source/commandline.go             |   8 +
 application/source/defaults.go                |   4 +-
 application/source/l10n.go                    |  53 +++-
 application/source/requirements.go            | 296 ++++++++++++++----
 application/source/util.go                    |  12 +
 application/web/index.html                    |   8 +-
 .../examples/example1/req1/00-00-001-text.md  |   7 -
 .../examples/example1/req1/001-1425.md        |  44 ---
 development/examples/example1/req1/002.md     |  31 --
 .../examples/example1/req1/002/002-01.md      | 119 -------
 .../examples/example1/req1/002/empty.md       |   0
 .../examples/example1/req1/002/noyaml.md      |   6 -
 development/examples/example1/req1/1/test1.md | 162 ++++++++++
 development/examples/example1/req1/1/test2.md | 162 ++++++++++
 development/examples/example1/req1/1/test3.md | 162 ++++++++++
 development/examples/example1/req1/1/test4.md | 162 ++++++++++
 development/examples/example1/req1/2/test1.md | 162 ++++++++++
 development/examples/example1/req1/2/test2.md | 162 ++++++++++
 development/examples/example1/req1/2/test3.md | 162 ++++++++++
 development/examples/example1/req1/2/test4.md | 162 ++++++++++
 development/examples/example1/req1/2/test5.md | 162 ++++++++++
 development/examples/example1/req1/2/test6.md | 162 ++++++++++
 development/examples/example1/req1/3/test1.md | 162 ++++++++++
 development/examples/example1/req1/3/test2.md | 162 ++++++++++
 development/examples/example1/req1/3/test3.md | 162 ++++++++++
 development/examples/example1/req1/3/test4.md | 162 ++++++++++
 development/examples/example1/req1/3/test5.md | 162 ++++++++++
 development/examples/example1/req1/3/test6.md | 162 ++++++++++
 development/examples/example1/req1/3/test7.md | 162 ++++++++++
 development/examples/example1/req1/4/test1.md | 162 ++++++++++
 development/examples/example1/req1/4/test2.md | 162 ++++++++++
 development/examples/example1/req1/4/test3.md | 162 ++++++++++
 development/examples/example1/req1/4/test4.md | 162 ++++++++++
 development/examples/example1/req1/5/test1.md | 162 ++++++++++
 development/examples/example1/req1/5/test2.md | 162 ++++++++++
 development/examples/example1/req1/6/test1.md | 162 ++++++++++
 development/examples/example1/req1/6/test2.md | 162 ++++++++++
 development/examples/example1/req999/999.md   |  25 --
 40 files changed, 4442 insertions(+), 292 deletions(-)
 create mode 100644 .idea/runConfigurations/go_build_requirements_manager_and_run_requirement_report.xml
 delete mode 100644 development/examples/example1/req1/00-00-001-text.md
 delete mode 100644 development/examples/example1/req1/001-1425.md
 delete mode 100644 development/examples/example1/req1/002.md
 delete mode 100644 development/examples/example1/req1/002/002-01.md
 delete mode 100644 development/examples/example1/req1/002/empty.md
 delete mode 100644 development/examples/example1/req1/002/noyaml.md
 create mode 100644 development/examples/example1/req1/1/test1.md
 create mode 100644 development/examples/example1/req1/1/test2.md
 create mode 100644 development/examples/example1/req1/1/test3.md
 create mode 100644 development/examples/example1/req1/1/test4.md
 create mode 100644 development/examples/example1/req1/2/test1.md
 create mode 100644 development/examples/example1/req1/2/test2.md
 create mode 100644 development/examples/example1/req1/2/test3.md
 create mode 100644 development/examples/example1/req1/2/test4.md
 create mode 100644 development/examples/example1/req1/2/test5.md
 create mode 100644 development/examples/example1/req1/2/test6.md
 create mode 100644 development/examples/example1/req1/3/test1.md
 create mode 100644 development/examples/example1/req1/3/test2.md
 create mode 100644 development/examples/example1/req1/3/test3.md
 create mode 100644 development/examples/example1/req1/3/test4.md
 create mode 100644 development/examples/example1/req1/3/test5.md
 create mode 100644 development/examples/example1/req1/3/test6.md
 create mode 100644 development/examples/example1/req1/3/test7.md
 create mode 100644 development/examples/example1/req1/4/test1.md
 create mode 100644 development/examples/example1/req1/4/test2.md
 create mode 100644 development/examples/example1/req1/4/test3.md
 create mode 100644 development/examples/example1/req1/4/test4.md
 create mode 100644 development/examples/example1/req1/5/test1.md
 create mode 100644 development/examples/example1/req1/5/test2.md
 create mode 100644 development/examples/example1/req1/6/test1.md
 create mode 100644 development/examples/example1/req1/6/test2.md
 delete mode 100644 development/examples/example1/req999/999.md

diff --git a/.idea/runConfigurations/go_build_requirements_manager_and_run_requirement_report.xml b/.idea/runConfigurations/go_build_requirements_manager_and_run_requirement_report.xml
new file mode 100644
index 0000000..12237c5
--- /dev/null
+++ b/.idea/runConfigurations/go_build_requirements_manager_and_run_requirement_report.xml
@@ -0,0 +1,13 @@
+<component name="ProjectRunConfigurationManager">
+  <configuration default="false" name="go build requirements-manager and run requirement report" type="GoApplicationRunConfiguration" factoryName="Go Application">
+    <module name="requirements-manager" />
+    <working_directory value="$PROJECT_DIR$/application/source" />
+    <parameters value="requirements report --grouped-by ID -p $PROJECT_DIR$/development/examples/example1" />
+    <kind value="DIRECTORY" />
+    <package value="gitlab.schukai.com/oss/utilities/requirements-manager" />
+    <directory value="$PROJECT_DIR$/application/source" />
+    <filePath value="$PROJECT_DIR$/application/source/main.go" />
+    <output_directory value="$PROJECT_DIR$/deployment/build" />
+    <method v="2" />
+  </configuration>
+</component>
\ No newline at end of file
diff --git a/README.md b/README.md
index f2f324c..030d076 100644
--- a/README.md
+++ b/README.md
@@ -149,6 +149,64 @@ The output is then of the type:
 
 ```
 
+### Output report
+
+```
+requirements report --grouped-by ID 
+```
+
+This command produces two tables:
+
+| Anforderung | Gesch | TIME SPENT | 
+|-------------|-------|------------|
+| ID1         | 40    | 1          |
+| ID2         | 40    | 1          |
+| ID3         | 40    | 1          |
+| ID4         | 40    | 1          |
+| ID5         | 40    | 2          |
+| ID6         | 40    | 2          |
+| ID7         | 40    | 2          |
+| ID8         | 40    | 2          |
+| ID9         | 40    | 2          |
+| ID10        | 40    | 2          |
+| ID11        | 40    | 3          |
+| ID12        | 40    | 3          |
+| ID13        | 40    | 3          |
+| ID14        | 40    | 3          |
+| ID15        | 40    | 3          |
+| ID16        | 40    | 3          |
+| ID17        | 40    | 3          |
+| ID18        | 40    | 4          |
+| ID19        | 40    | 4          |
+| ID20        | 40    | 4          |
+| ID21        | 40    | 4          |
+| ID22        | 40    | 5          |
+| ID23        | 40    | 5          |
+| ID24        | 40    | 6          |
+| ID25        | 40    | 6          |
+
+
+
+1) Groups all estimates and adds up the estimate and the booked times. This allows you to see how much time you have spent.
+
+| KEY | PLANNED VALUE | TIME SPENT | RATIO |
+|:----|---------------|------------|-------|
+| ID1 | 1000          | 75h0m0s    | 7.50  |
+
+2) This table shows for each plan value the hours needed, the mean, the variance and the standard deviation.
+
+| PLAN VALUE | TIME SPENT | MEAN | VARIANCE | STANDARD DEVIATION |
+|------------|------------|------|----------|--------------------|
+| 40         | 75h0m0s    | 3.00 | 2.08     | 1.44               |
+
+On average, we needed 3 hours in the example.
+However, we needed 6 hours for 2 requirements.
+
+The variance, or standard deviation, gives us a measure of how accurate we are. 
+The smaller the standard deviation, the better.
+
+So what decision can we derive? If a new requirement is estimated at 
+40, the hours offered should be between 3 and 5.
 
 ## Structure
 
diff --git a/application/source/commandline.go b/application/source/commandline.go
index 85f8d8a..45c82d0 100644
--- a/application/source/commandline.go
+++ b/application/source/commandline.go
@@ -20,6 +20,9 @@ type commandLineOptions struct {
 		Add struct {
 			ID string `long:"id" required:"true" description:"new requirement id"`
 		} `command:"add"`
+		Report struct {
+			GroupedBy string `long:"grouped-by" required:"false" description:"grouped by"`
+		} `command:"report"`
 	} `command:"requirements"`
 	Tasks struct {
 		Print struct {
@@ -126,6 +129,11 @@ func executeCommand() {
 	case "requirements":
 		subcommand := activeCommand.Active
 		switch subcommand.Name {
+		case "report":
+			err := printRequirementReport(config, arguments)
+			if err != nil {
+				printErrorAndExit(2, err.Error())
+			}
 		case "add":
 			config.Requirement.Template.Add = defaultNewRequirementTemplate
 			err := addRequirement(config, arguments)
diff --git a/application/source/defaults.go b/application/source/defaults.go
index 2ffbc3b..7642800 100644
--- a/application/source/defaults.go
+++ b/application/source/defaults.go
@@ -92,11 +92,11 @@ Estimation:
 
 # The time required for this requirement
 # Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
-TimeSpent:  
+Time Spent:  
 
 # who is the source of the demand
 Source: null
-Created: {{ .Created.Format "2006-02-01" }}
+Created: %%CREATED%%
 Last Update: null
 
 # the individual items as a list
diff --git a/application/source/l10n.go b/application/source/l10n.go
index cce6829..7f904fa 100644
--- a/application/source/l10n.go
+++ b/application/source/l10n.go
@@ -287,13 +287,64 @@ var l10nMap = []l10nKeyTranslation{
 			{"de", "Die Datei %s enthält strukturelle Fehler (%s). Überprüfen Sie die Datei."},
 			{"en", "the file  %s contains structural errors  (%s). Check the if necessary the file."},
 		},
-	}, {
+	},
+	{
 		"the file is empty",
 		[]l10nLocaleTranslation{
 			{"de", "Die Datei enthält keinen Inhalt."},
 			{"en", "the file is empty."},
 		},
 	},
+	{
+		"the grouping key was not found",
+		[]l10nLocaleTranslation{
+			{"de", "Der Schlüssel %s existiert nicht"},
+			{"en", "the grouping key %s was not found"},
+		},
+	},
+
+	{
+		"Ratio",
+		[]l10nLocaleTranslation{
+			{"de", "Verhältnis"},
+			{"en", "Ratio"},
+		},
+	},
+	{
+		"Standard Deviation",
+		[]l10nLocaleTranslation{
+			{"de", "Standardabweichung"},
+			{"en", "Standard Deviation"},
+		},
+	},
+	{
+		"Variance",
+		[]l10nLocaleTranslation{
+			{"de", "Varianz"},
+			{"en", "Variance"},
+		},
+	},
+	{
+		"Average",
+		[]l10nLocaleTranslation{
+			{"de", "Mittelwert"},
+			{"en", "Average"},
+		},
+	},
+	{
+		"Time Spent",
+		[]l10nLocaleTranslation{
+			{"de", "Aufwand"},
+			{"en", "Time Spent"},
+		},
+	},
+	{
+		"Estimated",
+		[]l10nLocaleTranslation{
+			{"de", "Planwert"},
+			{"en", "Estimated"},
+		},
+	},
 }
 
 func initL10n() {
diff --git a/application/source/requirements.go b/application/source/requirements.go
index 03f617c..676e6ee 100644
--- a/application/source/requirements.go
+++ b/application/source/requirements.go
@@ -3,9 +3,11 @@ package main
 import (
 	"bytes"
 	"fmt"
+	"math"
 	"os"
 	"path"
 	"reflect"
+	"strconv"
 	"strings"
 	"time"
 
@@ -19,24 +21,24 @@ type requirement struct {
 	Items    []Item    `yaml:"Items"`
 	Privacy  []Privacy `yaml:"Privacy"`
 
-	ID         string    `yaml:"ID"`
-	References []string  `yaml:"References"`
-	Type       string    `yaml:"Type"` // Display, Functional, Performance, Printing, Report, Testing and Validate
-	Title      string    `yaml:"Title"`
-	Alias      []string  `yaml:"Alias"`
-	Keywords   []string  `yaml:"Keywords"`
-	Author     []string  `yaml:"Author"`
-	Status     string    `yaml:"Status"`
-	Complexity string    `yaml:"Complexity"`
-	Difficulty string    `yaml:"Difficulty"` // Low, Medium, High
-	Priority   string    `yaml:"Priority"`   // Low, Medium, High
-	Version    string    `yaml:"Version"`
-	Milestone  string    `yaml:"Milestone"`
-	Estimation int       `yaml:"Estimation"` // 0, 1, 2, 3, 5, 8, 13, 20, 40, 100
-	TimeSpent  string    `yaml:"TimeSpent"`  // 3h2m20s
-	Source     string    `yaml:"Source"`
-	Created    time.Time `yaml:"Created"`
-	LastUpdate time.Time `yaml:"Last Update"`
+	ID         string        `yaml:"ID"`
+	References []string      `yaml:"References"`
+	Type       string        `yaml:"Type"` // Display, Functional, Performance, Printing, Report, Testing and Validate
+	Title      string        `yaml:"Title"`
+	Alias      []string      `yaml:"Alias"`
+	Keywords   []string      `yaml:"Keywords"`
+	Author     []string      `yaml:"Author"`
+	Status     string        `yaml:"Status"`
+	Complexity string        `yaml:"Complexity"`
+	Difficulty string        `yaml:"Difficulty"` // Low, Medium, High
+	Priority   string        `yaml:"Priority"`   // Low, Medium, High
+	Version    string        `yaml:"Version"`
+	Milestone  string        `yaml:"Milestone"`
+	Estimation int           `yaml:"Estimation"` // 0, 1, 2, 3, 5, 8, 13, 20, 40, 100
+	TimeSpent  time.Duration `yaml:"Time Spent"` // 3h2m20s
+	Source     string        `yaml:"Source"`
+	Created    time.Time     `yaml:"Created"`
+	LastUpdate time.Time     `yaml:"Last Update"`
 }
 
 func addRequirement(config *Configuration, arguments *commandLineOptions) error {
@@ -52,6 +54,7 @@ func addRequirement(config *Configuration, arguments *commandLineOptions) error
 
 	t := config.Requirement.Template.Add
 	t = strings.Replace(t, "%%ID%%", arguments.Requirements.Add.ID, -1)
+	t = strings.Replace(t, "%%CREATED%%", time.Now().Format("2006-01-02"), -1)
 
 	d1 := []byte(t)
 	err := os.WriteFile(p, d1, 0644)
@@ -59,50 +62,19 @@ func addRequirement(config *Configuration, arguments *commandLineOptions) error
 		return err
 	}
 
-	//t, err := template.New("requirement").Parse(config.Requirement.Template.Add)
-	//if err != nil {
-	//	return err
-	//}
-	//
-	//d := requirement{}
-	//d.ID = arguments.Requirements.Add.ID
-	//
-	//f, err := os.Create(p)
-	//if err != nil {
-	//	return err
-	//}
-	//
-	//defer f.Close()
-	//
-	//err = t.Execute(f, d)
-	//if err != nil {
-	//	return err
-	//}
-
 	return nil
 }
 
-func translateRequirementHeaders(columns []string) []string {
-
-	result := []string{}
-
-	for _, column := range columns {
-		result = append(result, printer.Sprintf(column))
-	}
-
-	return result
-
-}
-
 func buildRequirements(config *Configuration, pageMap map[string]requirement) (error, string, bool) {
 
-	buf := new(bytes.Buffer)
-
 	hasRequirements := false
 
+	buf := new(bytes.Buffer)
 	table := tablewriter.NewWriter(buf)
 
-	translateMetaColumns := translateRequirementHeaders(config.Requirement.Table.Columns)
+	columns := []string{"Estimation", "TimeSpent", "Velocity"}
+
+	translateMetaColumns := translateHeaders(columns)
 
 	table.SetHeader(translateMetaColumns)
 	table.SetBorders(tablewriter.Border{Left: true, Top: false, Right: true, Bottom: false})
@@ -186,3 +158,221 @@ func printRequirements(config *Configuration) error {
 	fmt.Println(table)
 	return err
 }
+
+func buildTimeReport(config *Configuration, arguments *commandLineOptions, pageMap map[string]requirement) (error, string, string, bool) {
+
+	groupedByKey := arguments.Requirements.Report.GroupedBy
+	if groupedByKey == "" {
+		groupedByKey = "ID"
+	}
+
+	hasReport := false
+
+	found := false
+	for t, p := range pageMap {
+		fmt.Println(t, p)
+		fields := reflect.VisibleFields(reflect.TypeOf(p))
+		for _, field := range fields {
+			if field.Name == groupedByKey {
+				found = true
+				break
+			}
+		}
+		if found {
+			break
+		}
+	}
+
+	if !found {
+		printErrorAndExit(2, "the grouping key was not found", groupedByKey)
+	}
+
+	t1 := buildTable1(groupedByKey, pageMap)
+
+	t2 := buildTable2(pageMap)
+
+	return nil, t1, t2, hasReport
+}
+
+func buildTable1(groupedByKey string, pageMap map[string]requirement) string {
+
+	estimated := map[string]float64{}
+	timeSpent := map[string]float64{}
+
+	for _, d := range pageMap {
+
+		r := reflect.ValueOf(d)
+		k := r.FieldByName(groupedByKey).String()
+
+		s := float64(d.TimeSpent.Milliseconds()) / 1000
+
+		estimated[k] += float64(d.Estimation)
+		timeSpent[k] += s
+
+	}
+
+	buf := new(bytes.Buffer)
+	table := tablewriter.NewWriter(buf)
+
+	columns := []string{"Key", "Estimated", "Time Spent", "Ratio"}
+
+	table.SetHeader(translateHeaders(columns))
+	table.SetBorders(tablewriter.Border{Left: true, Top: false, Right: true, Bottom: false})
+	table.SetCenterSeparator("|")
+
+	var tableData [][]string
+
+	for k := range estimated {
+		var row []string
+		row = append(row, k)
+		row = append(row, strconv.FormatInt(int64(estimated[k]), 10))
+		// nanosecond
+		row = append(row, time.Duration(timeSpent[k]*1000000000).String())
+
+		var ratio float64
+		ratio = 0
+		if timeSpent[k] > 0 {
+
+			e := float64(estimated[k]) * 3600
+			s := timeSpent[k]
+			ratio = s / e * 100
+
+		}
+
+		row = append(row, fmt.Sprintf("%.2f", ratio))
+		tableData = append(tableData, row)
+	}
+
+	table.AppendBulk(tableData) // Add Bulk Data
+	table.SetHeaderAlignment(tablewriter.ALIGN_LEFT)
+	table.Render()
+
+	return buf.String()
+}
+
+type timeStruct struct {
+	sum         float64
+	hour        map[int]int // [time]count
+	average     float64
+	sqrtAverage float64
+}
+
+type mathData struct {
+	count    float64
+	estimate struct {
+	}
+	time timeStruct
+}
+
+func buildTable2(pageMap map[string]requirement) string {
+
+	est := map[int]mathData{}
+
+	// inti struct
+	for _, d := range pageMap {
+		k := d.Estimation
+
+		m := mathData{}
+		m.count = 0
+		m.time = timeStruct{
+			0,
+			make(map[int]int),
+			0,
+			0,
+		}
+
+		est[k] = m
+	}
+
+	// calc sum
+	for _, d := range pageMap {
+		k := d.Estimation
+		s := est[k]
+
+		s.count++
+		sec := float64(d.TimeSpent.Milliseconds()) / 1000
+		s.time.sum += sec
+
+		h := int(math.Round(sec / 3600))
+		mh := s.time.hour
+		mh[h]++
+
+		est[k] = s
+	}
+
+	for k, s := range est {
+		//
+		a := 0.0
+		c := 0.0
+
+		for h, m := range s.time.hour {
+			a += float64(h * m)
+			//			g += math.Pow(a, 2)
+			c += float64(m)
+		}
+
+		x := est[k]
+		x.time.average = a / c
+
+		g := 0.0
+		for q, m := range s.time.hour {
+			z := float64(q) - x.time.average
+			g += math.Pow(z, 2) * float64(m)
+		}
+
+		x.time.sqrtAverage = g / c
+		est[k] = x
+
+	}
+
+	buf := new(bytes.Buffer)
+	table := tablewriter.NewWriter(buf)
+
+	columns := []string{"Estimated", "Time Spent", "Average", "Variance", "Standard Deviation"}
+
+	table.SetHeader(translateHeaders(columns))
+	table.SetBorders(tablewriter.Border{Left: true, Top: false, Right: true, Bottom: false})
+	table.SetCenterSeparator("|")
+
+	var tableData [][]string
+
+	for e, c := range est {
+
+		fmt.Println(e, c)
+
+		row := []string{}
+
+		row = append(row, fmt.Sprintf("%d", e))
+		row = append(row, time.Duration(c.time.sum*float64(time.Second)).String())
+		row = append(row, fmt.Sprintf("%.2f", c.time.average))
+		row = append(row, fmt.Sprintf("%.2f", c.time.sqrtAverage))
+		row = append(row, fmt.Sprintf("%.2f", math.Sqrt(c.time.sqrtAverage)))
+
+		tableData = append(tableData, row)
+
+	}
+
+	table.AppendBulk(tableData) // Add Bulk Data
+	table.SetHeaderAlignment(tablewriter.ALIGN_LEFT)
+	table.Render()
+
+	return buf.String()
+}
+
+func printRequirementReport(config *Configuration, arguments *commandLineOptions) error {
+
+	err, pageData := collectStructureFromFiles(config.Path)
+	if err != nil {
+		return err
+	}
+
+	err, table1, table2, _ := buildTimeReport(config, arguments, pageData)
+
+	report := ""
+	report += table1
+	report += table2
+
+	fmt.Println(report)
+
+	return nil
+}
diff --git a/application/source/util.go b/application/source/util.go
index db20f61..4d067ea 100644
--- a/application/source/util.go
+++ b/application/source/util.go
@@ -84,3 +84,15 @@ func splitYamlParts(content []byte) (error, contentRequirement) {
 	return nil, req
 
 }
+
+func translateHeaders(columns []string) []string {
+
+	result := []string{}
+
+	for _, column := range columns {
+		result = append(result, printer.Sprintf(column))
+	}
+
+	return result
+
+}
diff --git a/application/web/index.html b/application/web/index.html
index 21c1343..619a0cc 100644
--- a/application/web/index.html
+++ b/application/web/index.html
@@ -33,10 +33,10 @@
             </div>
             <ul class="list-group">
                 <li class="list-group-item"><a class="text-decoration-none link-danger" href="./reqman-linux-386">reqman-linux-386</a></li>
-                <li class="list-group-item"><a class="text-decoration-none link-danger" href="./reqman-linux-386">reqman-linux-amd64</a></li>
-                <li class="list-group-item"><a class="text-decoration-none link-danger" href="./reqman-linux-386">reqman-linux-arm</a></li>
-                <li class="list-group-item"><a class="text-decoration-none link-danger" href="./reqman-linux-386">reqman-linux-arm64</a></li>
-                <li class="list-group-item"><a class="text-decoration-none link-danger" href="./reqman-linux-386">reqman-windows</a></li>
+                <li class="list-group-item"><a class="text-decoration-none link-danger" href="./reqman-linux-amd64">reqman-linux-amd64</a></li>
+                <li class="list-group-item"><a class="text-decoration-none link-danger" href="./reqman-linux-arm">reqman-linux-arm</a></li>
+                <li class="list-group-item"><a class="text-decoration-none link-danger" href="./reqman-linux-arm64">reqman-linux-arm64</a></li>
+                <li class="list-group-item"><a class="text-decoration-none link-danger" href="./reqman-windows">reqman-windows</a></li>
             </ul>
         </div>
 
diff --git a/development/examples/example1/req1/00-00-001-text.md b/development/examples/example1/req1/00-00-001-text.md
deleted file mode 100644
index e1aef95..0000000
--- a/development/examples/example1/req1/00-00-001-text.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-ID: 1425
-
-...
-
-
-### !!{{ .ID }}!!
\ No newline at end of file
diff --git a/development/examples/example1/req1/001-1425.md b/development/examples/example1/req1/001-1425.md
deleted file mode 100644
index da3cd70..0000000
--- a/development/examples/example1/req1/001-1425.md
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
-
----
-Title: Value1
-Created: 2022-02-21
-Version: 1.0
-ID: 9999
-...
-
-### {{ .ID }} {{ .Title }}
-
-das ist ein test
-
-
-
-Here is a footnote reference,[^1] and another.[^longnote]
-
-[^1]: Here is the footnote.
-
-[^longnote]: Here's one with multiple blocks.
-
-
-This paragraph won't be part of the note, because it
-isn't indented.
-
-- [ ] das ist das erste todo 1
-- [x] 2020-12-02 das ist das erste todo 2
-  - [ ] 2020-12-03 das ist das erste todo 3 
-  - [x ] 2020-12-03 das ist das erste todo 3 
-
-
-#### Headline 1
-
-HIER IST EIN BILD
-
-![DAS IST EIN BILD](../assets/demo.png)
-
-Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet.
-
-#### Headline 2
-
-Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat.
diff --git a/development/examples/example1/req1/002.md b/development/examples/example1/req1/002.md
deleted file mode 100644
index 4b587b0..0000000
--- a/development/examples/example1/req1/002.md
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
-
----
-Key1: Value122
-Title: My Name22
-Created: 2022-02-21
-Version: 2.2.2
-ID: a1
-Last Update: 2022-04-01
----
-
-
-### {{ .ID }} {{ .Title }}
-
-Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet.
-
-
-- [ ] 2020-12-01 das ist das erste todo 1
-- [ ] 2020-12-02 das ist das erste todo 2
-- [ ] 2020-12-03 das ist das erste todo 3 sdfkjasdfk jasdkfjasd löfjasdklöfj asdkjfasdf jasdklf jasdfklöjasdfklöjasdklö
-
-
-#### Headline 1111
-
-lorem in hendrerit in vulputate velit esse moles
-
-#### Headline 2222
-
-Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat.
diff --git a/development/examples/example1/req1/002/002-01.md b/development/examples/example1/req1/002/002-01.md
deleted file mode 100644
index 0a774e9..0000000
--- a/development/examples/example1/req1/002/002-01.md
+++ /dev/null
@@ -1,119 +0,0 @@
----
-Key1: Value1
-Title: My Name
-Created: 2022-02-24
-Version: 2.0.2
-ID: 23423
-
-Items:
-  -
-    Group: A1
-    ID: Beistellung1
-    Name: Beistellung eines Bildes
-    Description: Großes Logo
-    Delivery until: 2022-12-12
-    Provided by: Me
-    Provided on: 2022-12-01
-    Type: Bild
-  -
-    ID: XXX
-    Group: Logo (klein)
-    Description: kleines Logo
-
-Privacy:
-  
-  - ID: P01
-  
-    # Purpose of the data processing,
-    # for example, shipping an order and handing it over to a shipping service provider.
-    Purposes: Versand von Daten
-  
-    # More detailed description of the reason and process of data processing.
-    Description: null
-  
-    # Who is responsible for data protection
-    Contact: null
-  
-    # But working with these categories might end up being a bad idea since doing so might
-    # mean packing different things into one. This leads to either oversimplifications or
-    # a lot of specifications within a category. It might be advisable to split some of them
-    # up or to add additional ones to make them fit your business reality.
-    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
-    Affected Groups: null
-  
-    #   
-    Category: Anschrift
-  
-    # Example: 5 years from the payment of the salary
-    Data Retention Period: null
-  
-    # On what legal basis is the data collected
-    # Special legal regulation outside the GDPR
-    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
-    # Collective agreement (e.g. company agreement, collective agreement)
-    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
-    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
-    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
-    Legal Basis: null
-  
-    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
-    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
-    # his or her agreement to personal data relating to him or her being processed.
-    Consent: null
-  
-    # Where applicable, transfers of personal data to a third country or an international organisation, including
-    # the identification of that third country or international organisation and, in the case of transfers referred
-    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
-    Transfers:
-  
-    # Where possible, a general description of the technical and organisational
-    # security measures referred to in Article 32(1).
-    TOM: null
-
----
-
-### {{ .ID }} {{ .Title }}  !?!?!?1------
-
-#### Subheading
-
-- [ ] task 1
-- [ ] task 2
-
-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-
-{{ if .Items }}
-**Items222**
-
-| ID                 | Name         |        Delivery until |                              Provided on |
-|--------------------|--------------|----------------------:|-----------------------------------------:|
-{{ range .Items
-}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} |
-{{ end }}
-
-{{ end }}
-
-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-
-Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore
-magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd
-gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing
-elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et
-accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit
-amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et
-dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd
-gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet.
-
-- [ ] 2020-12-01 das ist das erste todo 1
-- [ ] 2020-12-02 das ist das erste todo 2
-- [ ] 2020-12-03 das ist das erste todo 3 sdfkjasdfk jasdkfjasd löfjasdklöfj asdkjfasdf jasdklf jasdfklöjasdfklöjasdklö
-
-#### Headline 1111
-
-lorem in hendrerit in vulputate velit esse moles
-
-#### Headline 2222
-
-Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat
-nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis
-dolore te feugait nulla facilisi. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh
-euismod tincidunt ut laoreet dolore magna aliquam erat volutpat.
diff --git a/development/examples/example1/req1/002/empty.md b/development/examples/example1/req1/002/empty.md
deleted file mode 100644
index e69de29..0000000
diff --git a/development/examples/example1/req1/002/noyaml.md b/development/examples/example1/req1/002/noyaml.md
deleted file mode 100644
index 5c42695..0000000
--- a/development/examples/example1/req1/002/noyaml.md
+++ /dev/null
@@ -1,6 +0,0 @@
-
-
-
-## Das ist eine einfache Datei
-
-diese datei enhält keine YAML Struktur.
\ No newline at end of file
diff --git a/development/examples/example1/req1/1/test1.md b/development/examples/example1/req1/1/test1.md
new file mode 100644
index 0000000..d670d19
--- /dev/null
+++ b/development/examples/example1/req1/1/test1.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID1
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  1h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/1/test2.md b/development/examples/example1/req1/1/test2.md
new file mode 100644
index 0000000..c0a035f
--- /dev/null
+++ b/development/examples/example1/req1/1/test2.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID2
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  1h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/1/test3.md b/development/examples/example1/req1/1/test3.md
new file mode 100644
index 0000000..a673b2d
--- /dev/null
+++ b/development/examples/example1/req1/1/test3.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID3
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  1h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/1/test4.md b/development/examples/example1/req1/1/test4.md
new file mode 100644
index 0000000..b32c64e
--- /dev/null
+++ b/development/examples/example1/req1/1/test4.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID4
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  1h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/2/test1.md b/development/examples/example1/req1/2/test1.md
new file mode 100644
index 0000000..70d7973
--- /dev/null
+++ b/development/examples/example1/req1/2/test1.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID5
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  2h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/2/test2.md b/development/examples/example1/req1/2/test2.md
new file mode 100644
index 0000000..142b509
--- /dev/null
+++ b/development/examples/example1/req1/2/test2.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID6
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  2h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/2/test3.md b/development/examples/example1/req1/2/test3.md
new file mode 100644
index 0000000..925b905
--- /dev/null
+++ b/development/examples/example1/req1/2/test3.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID7
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  2h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/2/test4.md b/development/examples/example1/req1/2/test4.md
new file mode 100644
index 0000000..07c24ef
--- /dev/null
+++ b/development/examples/example1/req1/2/test4.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID8
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  2h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/2/test5.md b/development/examples/example1/req1/2/test5.md
new file mode 100644
index 0000000..eec7807
--- /dev/null
+++ b/development/examples/example1/req1/2/test5.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID9
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  2h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/2/test6.md b/development/examples/example1/req1/2/test6.md
new file mode 100644
index 0000000..9863dcb
--- /dev/null
+++ b/development/examples/example1/req1/2/test6.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID10
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  2h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/3/test1.md b/development/examples/example1/req1/3/test1.md
new file mode 100644
index 0000000..8b61077
--- /dev/null
+++ b/development/examples/example1/req1/3/test1.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID11
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  3h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/3/test2.md b/development/examples/example1/req1/3/test2.md
new file mode 100644
index 0000000..84b1909
--- /dev/null
+++ b/development/examples/example1/req1/3/test2.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID12
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  3h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/3/test3.md b/development/examples/example1/req1/3/test3.md
new file mode 100644
index 0000000..a61da67
--- /dev/null
+++ b/development/examples/example1/req1/3/test3.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID13
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  3h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/3/test4.md b/development/examples/example1/req1/3/test4.md
new file mode 100644
index 0000000..3f80e07
--- /dev/null
+++ b/development/examples/example1/req1/3/test4.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID14
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  3h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/3/test5.md b/development/examples/example1/req1/3/test5.md
new file mode 100644
index 0000000..95d1c1b
--- /dev/null
+++ b/development/examples/example1/req1/3/test5.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID15
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  3h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/3/test6.md b/development/examples/example1/req1/3/test6.md
new file mode 100644
index 0000000..96cc07f
--- /dev/null
+++ b/development/examples/example1/req1/3/test6.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID16
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  3h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/3/test7.md b/development/examples/example1/req1/3/test7.md
new file mode 100644
index 0000000..e01062b
--- /dev/null
+++ b/development/examples/example1/req1/3/test7.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID17
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  3h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/4/test1.md b/development/examples/example1/req1/4/test1.md
new file mode 100644
index 0000000..d31bfbe
--- /dev/null
+++ b/development/examples/example1/req1/4/test1.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID18
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  4h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/4/test2.md b/development/examples/example1/req1/4/test2.md
new file mode 100644
index 0000000..1ac192b
--- /dev/null
+++ b/development/examples/example1/req1/4/test2.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID19
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  4h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/4/test3.md b/development/examples/example1/req1/4/test3.md
new file mode 100644
index 0000000..519a263
--- /dev/null
+++ b/development/examples/example1/req1/4/test3.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID20
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  4h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/4/test4.md b/development/examples/example1/req1/4/test4.md
new file mode 100644
index 0000000..440d92b
--- /dev/null
+++ b/development/examples/example1/req1/4/test4.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID21
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  4h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/5/test1.md b/development/examples/example1/req1/5/test1.md
new file mode 100644
index 0000000..ee46ba3
--- /dev/null
+++ b/development/examples/example1/req1/5/test1.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID22
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  5h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/5/test2.md b/development/examples/example1/req1/5/test2.md
new file mode 100644
index 0000000..8260ba7
--- /dev/null
+++ b/development/examples/example1/req1/5/test2.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID23
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  5h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/6/test1.md b/development/examples/example1/req1/6/test1.md
new file mode 100644
index 0000000..d95706c
--- /dev/null
+++ b/development/examples/example1/req1/6/test1.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID24
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  6h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req1/6/test2.md b/development/examples/example1/req1/6/test2.md
new file mode 100644
index 0000000..8dac327
--- /dev/null
+++ b/development/examples/example1/req1/6/test2.md
@@ -0,0 +1,162 @@
+
+---
+ID: ID25
+Title: null
+
+# Reference to other requirements
+References: null
+
+# Display, Functional, Performance, Printing, Report, Testing or Validation
+Type: null
+
+Alias: null
+
+Keywords:
+  - Requirement
+
+# First and last name of the authors as a list
+Author: 
+  - null
+
+# Proposed (The requirement has been requested by an authorized source.),
+# In Progress (A business analyst is actively working on crafting the requirement.), 
+# Drafted (The initial version of the requirement has been written.), 
+# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
+# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.), 
+# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.), 
+# Deferred (An approved requirement is now planned for implementation in a later release.), 
+# Deleted (An approved requirement has been removed from the baseline.) or 
+# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
+Status: "Proposed"
+  
+# Low, Medium, Hi
+Complexity: null
+# Low, Medium, Hi
+Difficulty: null
+# Nice to have, Low, Medium, Hi or Blocker
+Priority: null 
+Version: 0.0.1
+Milestone: null
+
+# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks), 
+# 8, 13, 20, 40, 100
+Estimation: 40
+
+# The time required for this requirement
+# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
+Time Spent:  6h
+
+# who is the source of the demand
+Source: null
+Created: 2022-05-03
+Last Update: null
+
+# the individual items as a list
+Items:
+  - ID: null
+    Name: null
+    # what is it, a image, font, legal information, access data, texts, decisions, ...
+    Type: null
+    # does this belong to a group
+    Group: null
+    Description: null
+    Delivery until: null
+    # when was the project items delivered and by whom?
+    Provided on: null
+    Provided by: null
+
+# https://gdpr-info.eu/art-30-gdpr/
+Privacy:
+  - ID: null
+
+    # Purpose of the data processing, 
+    # for example, shipping an order and handing it over to a shipping service provider.
+    Purposes: null
+
+    # More detailed description of the reason and process of data processing.
+    Description: null
+
+    # Who is responsible for data protection 
+    Contact: null
+
+    # But working with these categories might end up being a bad idea since doing so might 
+    # mean packing different things into one. This leads to either oversimplifications or 
+    # a lot of specifications within a category. It might be advisable to split some of them 
+    # up or to add additional ones to make them fit your business reality.
+    # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
+    Affected Groups: null
+
+    # 
+    Category: 
+
+    # Example: 5 years from the payment of the salary   
+    Data Retention Period: null
+
+    # On what legal basis is the data collected
+    # Special legal regulation outside the GDPR
+    # Consent of the data subject (Art. 6 para. 1 a) DSG-VO)  use Consent field
+    # Collective agreement (e.g. company agreement, collective agreement)
+    # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
+    # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
+    # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
+    Legal Basis: null
+
+    # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or 
+    # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies 
+    # his or her agreement to personal data relating to him or her being processed.
+    Consent: null
+
+    # Where applicable, transfers of personal data to a third country or an international organisation, including 
+    # the identification of that third country or international organisation and, in the case of transfers referred 
+    # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
+    Transfers: 
+
+    # Where possible, a general description of the technical and organisational 
+    # security measures referred to in Article 32(1).
+    TOM: null
+
+...
+
+### {{ .Title }} - {{ .ID }}
+
+#### Subheading
+
+- [ ] task 1
+- [ ] task 2
+
+
+{{ if .Items }}
+#### Items
+
+| ID                 | Name         |        Delivery until |                              Provided on |
+|--------------------|--------------|----------------------:|-----------------------------------------:|
+{{ range .Items 
+ }}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan"  }} | 
+{{ end }}
+
+{{ end }}
+
+
+{{ if .Privacy }}
+#### Privacy
+
+{{ range .Privacy }}
+**{{ .Purpose }} ({{ .ID }})** 
+
+{{ .Description }}
+
+| | |
+|--|--|
+| Category | {{ .Category }} |  
+| Data Retention Period | {{ .DataRetentionPeriod }} |  
+| Legal Basis | {{ .LegalBasis }} |  
+| Transfers | {{ .Transfers }} |  
+{{ end }}
+
+{{ end }}
+
+
+
+
+
+
diff --git a/development/examples/example1/req999/999.md b/development/examples/example1/req999/999.md
deleted file mode 100644
index d737d68..0000000
--- a/development/examples/example1/req999/999.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-ID: 22.5
-title: Test 1
-subtitle: this is test 1
-tags: [fruit, sweet, tasty]
-percent: 100 %
-Estimation: 20
-list:
-    - entry 1
-    - entry 2
-    - entry 3
-
-
-...
-
-
-### {{ .ID }} {{ .Title }}
-
-#### Headline 1XXXX
-
-Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet.
-
-#### Headline 2XXX
-
-Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat.
-- 
GitLab