Improve regulations in TRG 7.07

lgblaumeiser · lgblaumeiser · commit 474017e4bfd4 · 2025-06-27T17:19:42.000+02:00
Signed-off-by: Lars Geyer-Blaumeiser &lt;lars.blaumeiser@cofinity-x.com&gt;
diff --git a/docs/release/trg-7/trg-7-06.md b/docs/release/trg-7/trg-7-06.md
@@ -4,6 +4,7 @@ title: TRG 7.06 - Legal notice for end user content
 
 | Status | Created     | Post-History                               |
 |--------|-------------|--------------------------------------------|
+| Draft  | 27-Jun-2025 | Remove documentation section finally       |
 | Active | 25-Apr-2024 | Updates for CC-BY-4.0 license              |
 | Active | 04-Dec-2023 | Update Shared UI Components / NPM library  |
 | Active | 13-Apr-2023 | New                                        |
@@ -53,7 +54,3 @@ Example:
 In order to align with the overall style guide, it's recommended to use the About card provided in the [Shared UI Components](https://eclipse-tractusx.github.io/portal-shared-components) via the respective [NPM library](https://www.npmjs.com/package/@catena-x/portal-shared-components) maintained by the portal product. As reference for the placement of this card in frontend apps: in the portal it has been integrated in an About page which is reachable from the footer.
 
 Regarding usage of this About card, it's recommended to add a json file to your frontend project to be imported for the real content. As some of the content can only be determined in the build pipeline, you could add a json file as reference containing placeholder values. Those placeholder values could then be replaced, by script, just before the build within the build pipeline.
-
-### Documentation
-
-This section moved to [TRG 7.07](/docs/release/trg-7/trg-7-07) and [TRG 7.08](/docs/release/trg-7/trg-7-08).
diff --git a/docs/release/trg-7/trg-7-07.md b/docs/release/trg-7/trg-7-07.md
@@ -1,29 +1,44 @@
 ---
-title: TRG 7.07 - Legal notice for non-code (e.g. documentation)
+title: TRG 7.07 - Legal notice for non-code (e.g. documentation, KITs)
 ---
 
-| Status | Created     | Post-History                 |
-|--------|-------------|------------------------------|
-| Active | 25-Apr-2024 | Updates for CC-BY-4.0 license|
-| Active | 18-Jul-2023 | Update: improved description |
-|        | 13-Apr-2023 | Initial version              |
+| Status | Created     | Post-History                  |
+|--------|-------------|-------------------------------|
+| Draft  | 27-06-2025  | Integration of non-code rules |
+| Active | 25-Apr-2024 | Updates for CC-BY-4.0 license |
+| Active | 18-Jul-2023 | Update: improved description  |
+|        | 13-Apr-2023 | Initial version               |
 
 ## Why
 
-Eclipse Tractus-X is an open source project hosted by the Eclipse Foundation licensed under the Apache License 2.0 ([Apache-2.0](https://spdx.org/licenses/Apache-2.0)). For non-code the default license is the Creative Commons Attribution 4.0 International ([CC-BY-4.0](https://spdx.org/licenses/CC-BY-4.0.html)).
+Eclipse Tractus-X is an open source project hosted by the Eclipse Foundation licensed under the Apache License 2.0
+([Apache-2.0](https://spdx.org/licenses/Apache-2.0)). For non-code the default license is the Creative Commons
+Attribution 4.0 International ([CC-BY-4.0](https://spdx.org/licenses/CC-BY-4.0.html)).
 
 The legal obligations of the content must be observed in all forms of which the content is available.
 
-All products delivered by the project—including websites, documentation, slides and help must include certain notices. Documentation might include a notice in either the pre- or post-amble, or a website might provide this information in a common footer, or a dedicated page. (From: [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#legaldoc-end-user))
+All products delivered by the project—including websites, documentation, slides, KITS and help must include certain
+notices. Documentation might include a notice in either the pre- or post-amble, or a website might provide this
+information in a common footer, or a dedicated page.
+(From: [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#legaldoc-end-user))
 
 ## Description
 
 Eclipse Tractus-X allows the following licenses: Apache-2.0 and CC-BY-4.0 for non-code.
 
-In this TRG, by non-code artifacts we mean e.g. documentation and images embedded in this documentation. All of these artifacts have to include notices about copyright, license and source location information. Excluded are the [legal documentation files](/docs/release/trg-7/trg-7-01#description).
+In this TRG, by non-code artifacts we mean e.g. documentation and images embedded in this documentation. All of these
+artifacts have to include notices about copyright, license and source location information. Excluded are the
+[legal documentation files](/docs/release/trg-7/trg-7-01#description).
 
-The CC-BY-4.0 is the default license for non-code. For some documentation it may makes sense to put it under the Apache-2.0 license, especially for technical documentation with code snippets embedded.
-There are special cases for the **KIT documentation**, that **must** be licensed under the CC-BY-4.0, see TRG 7-08.
+The CC-BY-4.0 is the default license for non-code. Deviating from the default is an exceptional case! For some
+documentation, though, it may makes sense to put it under the Apache-2.0 license, especially for technical
+documentation with code snippets embedded. For the KIT documentation it is recommended to put it under the CC-BY-4.0.
+The following KIT documentation **MUST** be licensed under the CC-BY-4.0:
+
+- Adoption View (adoption-view.md)
+
+Self-created content embedded in the listed KIT documentation files under the CC-BY-4.0, have also to be licensed
+under the CC-BY-4.0. Generally self-created artifacts like images, graphics and logos should go under the CC-BY-4.0.
 
 ## How to include legal notices
 
@@ -33,61 +48,138 @@ Attributions for non-code artifacts, like documentation files, have to be visibl
 it has to be added to the content, **NOT** in comments, metadata, or alt text (images).
 :::
 
+See also the [human-readable summary of the CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/).
+
 ### Documentation
 
-In this chapter we show an example of how to do it for a file with md format, licensed under the Apache-2.0, for other formats like slides, pdf, and others the format may be slightly different.
+For text files, like files in the markdown format, the attribution is done directly in the file as described in this
+section. The attribution is shown with an example for a CC-BY-4.0 licensed markdown file. For other formats like
+slides, pdf, and others adapt the information in an adequate way.
 
 Add a `NOTICE` section (post or preamble) into your dedicated documentation file, with the following information:
 
 ```text
 ## NOTICE
 
-This work is licensed under the [Apache-2.0](https://www.apache.org/licenses/LICENSE-2.0).
-
-- SPDX-License-Identifier: Apache-2.0
-- SPDX-FileCopyrightText: 202x {owner}[ and others]
-- SPDX-FileCopyrightText: 202xy Contributors to the Eclipse Foundation
-- Source URL: https://github.com/eclipse-tractusx/<myrepo>/<link_to_doc_or_doc_dir> (*)
-- Images: https://github.com/eclipse-tractusx/<myrepo>/<link_to_image_or_image_dir> (**)
- ```
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
 
-(*) URI or hyperlink to the Licensed Material to the extent reasonably practicable
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 202x {Owner}
+- Source URL: https://github.com/eclipse-tractusx/<myrepo>/<link_to_doc_or_doc_dir> (+)
+```
 
-(**) Only, if you include self created artifacts, see below
+(+) URI or hyperlink to the Licensed Material to the extent reasonably practicable
 
 :::tip
-If there are multiple copyright holders, insert several SPDX-FileCopyrightText lines, for each entry one line. Explanations in brackets, do not copy. PLEASE.
+If there are multiple copyright holders, insert several SPDX-FileCopyrightText lines, for each entry one line.
+Explanations in brackets, do not copy. PLEASE.
 
+```text
 - SPDX-FileCopyrightText: 2022 Owner1 (-> Owner1 created the content in 2022)
 - SPDX-FileCopyrightText: 2021 Owner2 (-> Owner2 created the content in 2021)
 - SPDX-FileCopyrightText: 2021 Contributors to the Eclipse Foundation
+```
+
 :::
 
-## Self-created content
+### Self-created content
+
+Self-created non-text content like an image should have the copyright and license information included, whereever
+possible, e.g., the information can be added at the bottom of an image.
+
+Example:
+
+```text
+COPYRIGHT(C) 202x {owner}[ and others] | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
+```
+
+If images (and other file types) cannot be attributed directly, attribution has to consider two distribution paths of
+the content.
+
+#### Embedded content in a distributed document
+
+If the file is embedded in a document, that is distributed as standalone document, e.g., as a generated PDF, the
+attribution **MUST** be done within the embedding document, either in the caption of the file, e.g., below the place
+the file is embedded, or in the notice section as described in the [previous section](#documentation). See an example
+for the notice section:
+
+```text
+## NOTICE
 
-Self-created content like images should have the copyright and license information included, where ever possible. Images should go under the CC-BY-4.0. See [TRG 7.08](/docs/release/trg-7/trg-7-08#self-created-content)
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2022 Owner1
+- Image(s): https://github.com/eclipse-tractusx/<myrepo>/<link_to_image_or_image_dir>
+- Source URL: https://github.com/eclipse-tractusx/<myrepo>/<link_to_doc_or_doc_dir>
+
+- SPDX-FileCopyrightText: 2022 Owner2
+- Diagram(s): https://github.com/eclipse-tractusx/<myrepo>/<link_to_diagram_or_diagram_dir>
+```
+
+#### Repository Content
+
+As the file is also provided in the repository and can be consumed there, the attribution **MUST** be done in the
+repository as well. This can be done with a workaround. Create a new file with the same name and the `.license` postfix
+next to the image with the following content:
+
+```text
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 202x {owner}[ and others]
+- Source URL: https://github.com/eclipse-tractusx/<myrepo>/<link_to_image_or_image_dir> (+)
+ ```
+
+ (+) URI or hyperlink to the Licensed Material to the extent reasonably practicable
+
+**Example:**
+
+```shell
+project/
+|__ docs/
+|   |__ adoption-view.md
+|   |__ img/
+|      |__ image1.jpg
+|      |__ image1.jpg.license
+|      |__ image2.png
+|      |__ image2.png.license
+|__ LICENSE
+|__ LICENSE_non-code
+```
+
+This is the recommended way of [REUSE Software](https://reuse.software/tutorial/).
+
+If multiple images need to be attributed, the REUSE Software project proposes the use of the `REUSE.toml` file format.
+This is an alternative way to specify attributions for many files that cannot be attributed directly like images. This
+file can be placed anywhere in a file system hierarchy and allows to refer to many files and provide the necessary
+attribution. As the whole concept is a bit more complex but very well described by the REUSE Software project, we refer
+at this point to the corresponding [specification](https://reuse.software/spec-3.3/#reusetoml) for further details.
 
 ### Third-party content
 
-If you embed third-party content , e.g. images, graphics, logos in your artifacts, the images have to be attributed with the following information:
+If you third-party content, e.g. images, graphics, logos in your artifacts or repositories, the images have to be attributed
+with the following information:
 
 - Title
 - Author/Copyright
 - License
 - Source
 
-#### Where to put the attribution
+The attribution **MUST** be documented as described in the [previous section](#self-created-content), i.e., within the
+embedding artifact or using an extra file to store the information. In addition, reference the third-party content in
+the repositories NOTICE file at the root level
 
-- right next to, over or under the image
-- **OR** make a clear reference to it and put the attribution in the NOTICE section
+**Example - photo with direct attribution:**
 
-**Example - photo with attribution:**
+Direct attribution
 
+```text
 ![example](@site/static/img/oss_example_Creative_Commons_10th_Birthday.jpg)
 
-Direct attribution:
-
-["Creative Commons 10th Birthday Celebration San Francisco"](http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657) by [Timothy Vollmer](http://www.flickr.com/photos/sixteenmilesofstring/) is licensed under [CC BY 4.0](http://creativecommons.org/licenses/by/4.0/)
+Attribution: ["Creative Commons 10th Birthday Celebration San Francisco"](http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657)
+by [Timothy Vollmer](http://www.flickr.com/photos/sixteenmilesofstring/) is licensed under [CC-BY-4.0](http://creativecommons.org/licenses/by/4.0/)
+```
 
 Addition for the notice section:
 
diff --git a/docs/release/trg-7/trg-7-08.md b/docs/release/trg-7/trg-7-08.md
@@ -4,112 +4,10 @@ title: TRG 7.08 - Legal notice for KIT documentation (CC-BY-4.0)
 
 | Status | Created     | Post-History                          |
 |--------|-------------|---------------------------------------|
+| Decommisioned | 27-Jun-2025 | Integrated into 7.07           |
 | Active | 25-Apr-2024 | Updates for CC-BY-4.0 license         |
 | Active | 18-Jul-2023 | CC-BY-4.0 topics moved here from 7.07 |
 
-## Why
+## Obsolete
 
-Eclipse Tractus-X is an open source project hosted by the Eclipse Foundation licensed under the Apache License 2.0 ([Apache-2.0](https://spdx.org/licenses/Apache-2.0)). For non-code the default license is the Creative Commons Attribution 4.0 International ([CC-BY-4.0](https://spdx.org/licenses/CC-BY-4.0.html)).
-
-The legal obligations of the content must be observed in all forms of which the content is available.
-
-For specifically defined KIT documentation files the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode) license is required.
-
-All products delivered by the project - including websites, documentation, and help must include certain notices. Documentation might include a notice in either the pre- or post-amble, or a website might provide this information in a common footer, or a dedicated page. (From: [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#legaldoc-end-user))
-
-## Description
-
-The CC-BY-4.0 is the default license for non-code. For some documentation it may makes sense to put it under the Apache-2.0 license, especially for technical documentation with code snippets embedded. For the KIT documentation it is recommended to put it under the CC-BY-4.0.  The following KIT documentation **MUST** be licensed under the CC-BY-4.0:
-
-- adoption-view.md(x)
-
-Self-created content embedded in the listed KIT documentation files under the CC-BY-4.0, have also to be licensed under the CC-BY-4.0.  Generally self-created artifacts like images, graphics and logos should go under the CC-BY-4.0.
-
-## How to include legal notices
-
-See also the [human-readable summary of the CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/).
-
-### Documentation
-
-Add a `NOTICE` section (post or preamble) into your dedicated documentation file, with the following information, here in md format:
-
-```text
-## NOTICE
-
-This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
-
-- SPDX-License-Identifier: CC-BY-4.0
-- SPDX-FileCopyrightText: 202x {Owner}
-- Source URL: https://github.com/eclipse-tractusx/<myrepo>/<link_to_doc_or_doc_dir> (*)
-- Images: https://github.com/eclipse-tractusx/<myrepo>/<link_to_image_or_image_dir> (**)
- ```
-
- (*) URI or hyperlink to the Licensed Material to the extent reasonably practicable
-
- (**) Only, if you include self created images, see below
-
- See [here](/docs/release/trg-7/trg-7-07#documentation) how to handle multiple copyright owners.
-
-### Self-created content
-
-Self-created content like e.g. images should have the copyright and license information included, where ever possible. Images should go under the CC-BY-4.0.
-
-Example:
-
-```text
-COPYRIGHT(C) 202x {owner}[ and others] | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0)
-```
-
-If images (and other formats) cannot be attributed directly, there is a workaround to provide the license and copyright information. Create a new file with the same name and the `.license` postfix next to the image with the following content:
-
-```text
-This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
-
-- SPDX-License-Identifier: CC-BY-4.0
-- SPDX-FileCopyrightText: 202x {owner}[ and others]
-- Source URL: https://github.com/eclipse-tractusx/<myrepo>/<link_to_image_or_image_dir> (*)
- ```
-
- (*) URI or hyperlink to the Licensed Material to the extent reasonably practicable
-
-**Example:**
-
-```shell
-project/
-|__ docs/
-|   |__ adoption-view.md
-|   |__ img/
-|      |__ image1.jpg
-|      |__ image1.jpg.license
-|      |__ image2.png
-|      |__ image2.png.license
-|__ LICENSE
-|__ LICENSE_non-code
-```
-
-This is the recommended way of [REUSE Software](https://reuse.software/tutorial/).
-
-If the images are not located in the same directory as the documentation, the notice section has to be extended for the information.
-Several lines for different locations can be added.
-
-```text
-- Images: https://github.com/eclipse-tractusx/<myrepo>/<link_to_image_or_image_dir> (*)
- ```
-
- (*) URI or hyperlink to the Licensed Material to the extent reasonably practicable
-
-### Third-party content
-
-If you embed third-party content, e.g. images, graphics, logos in your artifacts, the aerifacts have to be attributed with the following information:
-
-- Title
-- Author/Copyright
-- License
-- Source
-
-#### Where to put the attribution
-
-- right next to, over or under the artifact (e.g. the image)
-- **OR** make a clear reference to it and put the attribution in the NOTICE section
-
-Example: [TRG 7.07](/docs/release/trg-7/trg-7-07#third-party-content)
+Content has been integrated into TRG 7.07
