|
2 | 2 | title: "IT Architecture Principles and Implementation Guidelines" |
3 | 3 | subtitle: "Copernicus Land Monitoring Service" |
4 | 4 | author: "European Environment Agency (EEA)" |
5 | | -version: "1.4a" |
| 5 | +version: "1.4a" |
6 | 6 | date: "2025-03-06" |
7 | | -documentclass: scrartcl |
8 | 7 | product-name: IT Architecture Principles and Implementation Guidelines |
9 | | -toc: true # Enable the Table of Contents |
10 | | -toc-title: "Index" # Customize the title of the table of contents |
11 | | -toc-depth: 3 # Include headings up to level 3 (###) |
12 | 8 | keywords: ["Copernicus Land Monitoring Service, CLMS IT Architecture, European Environment Agency, IT Principles and Guidelines, IT Ecosystem, IT Security, EUPL Licensing, Reproducibility, Reusability, Transparency, Scalability, Maintainability, Resilient IT Solutions, Modular IT Architecture, Continuous Integration"] |
13 | | -number-sections: true |
14 | | -sitemap: true #Enables sitemap generation for web crawlers |
15 | | -tbl-colwidths: auto |
| 9 | + |
| 10 | + |
| 11 | +metadata-files: |
| 12 | + - ../../metadata/default.yml |
| 13 | + |
16 | 14 | format: |
17 | | - html: |
18 | | - css: ../styles/styles.css # Optional: Custom CSS file for styling |
19 | | - code-fold: true # Allow code blocks to be foldable |
20 | | - self-contained: true # Embed resources like CSS and images |
| 15 | + html: |
| 16 | + css: ../styles/styles.css |
21 | 17 | docx: |
22 | 18 | reference-doc: ../styles/template-guideline.docx |
23 | | - toc-location: before-body |
24 | | - toc-pagebreak: true |
25 | | - data: false |
26 | | - pdf: default |
| 19 | + pdf: default |
27 | 20 | --- |
28 | 21 |
|
29 | 22 | ```{=html} |
@@ -207,13 +200,11 @@ The CLMS is funded by the EU and supports its community with data and services. |
207 | 200 |
|
208 | 201 | | **Transparency 1:** | **Source code of client specific software to be supplied with IT solution** | |
209 | 202 | |----------------:|:------------------------------------------------------| |
210 | | -| **What:** | Source code of client specific IT solution is supplied as part of the deliverable and made publicly available under the EUPL-1.2[^1] license | |
| 203 | +| **What:** | Source code of client specific IT solution is supplied as part of the deliverable and made publicly available under the EUPL-1.2 license ^[(https://commission.europa.eu/content/european-union-public-licence_en)] | |
211 | 204 | | **Why:** | To ensure transparency, it is essential to have clear insights into the client-specific software. This enables efficient future developments and modifications | |
212 | 205 | | **Consequence:** | Source code of client specific software must be delivered with IT solution. The source code shall include Docker recipes and scripts for building the source code and be published under the EUPL-1.2 license | |
213 | 206 | | **Example:** | *Source code of all the components of the specific IT solution must be delivered. Any updates or developments of the source code shall be reflected in the EEA GitHub repository, which is the main repository of the system. Moreover, the specific client IT solutions shall be published under the EUPL-1.2 license, so the openness and transparency are ensured* | |
214 | 207 |
|
215 | | -[^1]: [European Union Public Licence - European Commission](https://commission.europa.eu/content/european-union-public-licence_en) |
216 | | - |
217 | 208 | | **Transparency 2:** | **Inline documentation of the source code** | |
218 | 209 | |----------------:|:------------------------------------------------------| |
219 | 210 | | **What:** | Source code of client specific IT solution must be documented in-line | |
|
0 commit comments