extended FAT reports paragraph

docs/modules/ROOT/pages/how-to-map-existing-data-models.adoc

@@ -249,7 +249,7 @@ A comprehensive mapping package typically includes:
 * *Technical Mapping Files:* This contains all the mapping code files (XSLT[ref], RML[ref], SPARQLAnything[ref], etc. depending on the chosen mapping technology) for data transformation, allowing for the practical application of the conceptual designs.
 * *Additional Mapping Resources:* Such as controlled lists, value mappings, or correspondence tables, which are crucial for the correct interpretation and application of the RML code. These are stored in a dedicated resources subfolder.
 * *Test Data Sets:* Carefully selected and representative XML files that cover various scenarios and cases. These test datasets are crucial for ensuring that the mappings perform as expected across a range of real-world data.
-* *Factory Acceptance Testing (FAT) Reports:* Document the testing outcomes based on the SPARQL and SHACL validations to guarantee that the mappings meet the expected standards before deployment.
+* *Factory Acceptance Testing (FAT) Reports:* Document the testing outcomes based on the SPARQL and SHACL validations to guarantee that the mappings meet the expected standards before deployment. The generation of these reports should be supported by automation, as manual generation would involve too much effort and costs.
 * *Tests Used for FAT Reports:* The package also incorporates the actual SPARQL assertions and SHACL shapes used in generating the FAT reports, providing a complete view of the validation process.
 * *Descriptive Metadata:* Contains essential data about the mapping package, such as identification, title, description, and versions of the mapping, ontology, and source schemas. This metadata aids in the management and application of the package.
 This package is designed to be self-contained, ensuring that it can be immediately integrated and operational within various data transformation pipelines. The included components support not only the application, but also the governance of the mappings, ensuring they are maintained and utilised correctly in diverse IT environments. This systematic packaging addresses critical needs for usability, maintainability, and standardisation, which are essential for widespread adoption and operational success in data transformation initiatives.