Update Compliance Statement

app/docs/api/README.md

@@ -5,3 +5,5 @@ This section provides documentation to implement the SETU standards for `Purchas
 SETU provides Open API Specifications (OAS) for the message sets, which can be implemented by software systems for standardized message exchange.
 
 In the case of `Purchase to Pay`, it is also possible to use the international Peppol network infrastructure to transport SETU messages. The Peppol-based exchange of SETU messages is described in the [Setu & Peppol](./Setu-Peppol.md) documentation.
+
+For more information on the requirements for a compliant implementation, please refer to the compliance statement.

app/docs/api/compliance.md

@@ -0,0 +1,32 @@
+---
+sidebar_position: 2
+---
+
+# Compliance statement
+
+## What is compliance?
+
+1. Compliance with the SETU standards means that the organization, the system or application for exchanging information in the field of temporary labor, operates in accordance with the requirements and principles as defined in the standards. The standards are defined as the specification documents and their associated errata, as published by the SETU.
+
+## For whom/what is compliance applicable?
+
+2. **Organizations**: must recognize and acknowledge the meaning of concepts as mentioned in the standards and be able to handle them in cooperation with partners.
+3. **Systems**: must be able to exchange information conform the standard, i.e. based on the specifications, rules and prescriptions as specified in the standards.
+
+## What is compliant use of the standard? 
+
+4. A SETU message with information elements and attributes contains at least all mandatory information elements and attributes specified in the standard.
+5. A SETU message contains only information elements and attributes specified in the standard.
+6. A SETU message contains at most all information elements and attributes specified in the standard.
+7. A SETU message conforms to the corresponding schema(s) by correctly validating against this (these) schema(s).
+8. An output SETU message needs to comply with (4) to (7). The use of optional information elements and attributes specified in the standard, is determined in coordination between sender and receiver.
+9. Each incoming SETU message that meets (4) to (7) must be received. 
+10. Each incoming SETU message that meets (4) to (7) must be processed meaningfully with regard to the mandatory elements and attributes.
+11. Each incoming SETU message that meets (4) to (7) must be processed meaningfully with regard to the optional information elements and attributes, depending on the agreements between sender and receiver on these optional elements.
+12. A SETU message may contain information elements and attributes that are not yet specified in the standard, but that are proposed as a future adaptation or extension of the standard and have been authorized as such by SETU. These elements are exclusively specified in solutions to maintenance requests that are labeled 'SETU compliant'. This implies that the use of these elements and attributes does not break compliancy with the standard they are complementing.
+13. A SETU message may use one designated existing information element for customer-specific purposes that are not otherwise specified in the standard. This one element is determined by SETU. Use of this element and its attributes must not result in semantic similarity to other elements and attributes specified in the standard. Customer-specific use of this element has to be reported to SETU. When reported, use of this element and its attributes does not break compliance with the SETU standard.
+
+## What does compliance not include?
+
+14. In order to achieve compliance, it is not sufficient to have the SETU message comply with the corresponding schema used for the exchange of messages.
+15. The use of elements and attributes in messages that are specified in the corresponding schema used for the exchange of messages but are not specified in the SETU standard or "SETU compliant extensions" (as authorized by the SETU workgroup), breaks compliancy with the standard.

app/sidebars.js

@@ -148,6 +148,7 @@ module.exports = {
           label: "Setu & Peppol",
           id: 'api/Setu-Peppol',
         },
+        "api/compliance",
       ],
     },
   ],