Conversation
app/docs/notes/Setu-Peppol.md
Outdated
|
|
||
| # Sending SETU Messages via PEPPOL | ||
|
|
||
| SETU standards define the _content_ and structure of messages for the temporary staffing industry in the Netherlands. While SETU specifies _what_ information is exchanged, **it is now also possible** to use the international **PEPPOL network** for the actual _transport_ of these messages, alongside other existing methods. PEPPOL (Pan-European Public Procurement Online) provides a standardized, secure way for organizations to exchange electronic business documents using a 'four-corner model' involving certified Access Points (APs). |
There was a problem hiding this comment.
Please remove: 'now also'. The text can be: 'it is possible to ...'
I think we don't have to use bold font for 'it is now possible' and 'PEPPOL network' here. No need to emphasize on that. We can use regular font.
app/docs/notes/Setu-Peppol.md
Outdated
|
|
||
| # Sending SETU Messages via PEPPOL | ||
|
|
||
| SETU standards define the _content_ and structure of messages for the temporary staffing industry in the Netherlands. While SETU specifies _what_ information is exchanged, **it is now also possible** to use the international **PEPPOL network** for the actual _transport_ of these messages, alongside other existing methods. PEPPOL (Pan-European Public Procurement Online) provides a standardized, secure way for organizations to exchange electronic business documents using a 'four-corner model' involving certified Access Points (APs). |
There was a problem hiding this comment.
Add link to 'https://peppol.org/' to the first use of 'PEPPOL'
app/docs/notes/Setu-Peppol.md
Outdated
|
|
||
| ## SETU and PEPPOL | ||
|
|
||
| Through agreements between SETU and the Dutch Peppol Authority (NPa), standard SETU XML messages can now be sent using the PEPPOL network infrastructure. |
There was a problem hiding this comment.
Add link to https://www.peppolautoriteit.nl/ for first use of 'Dutch Peppol Authority' here.
app/docs/notes/Setu-Peppol.md
Outdated
|
|
||
| Through agreements between SETU and the Dutch Peppol Authority (NPa), standard SETU XML messages can now be sent using the PEPPOL network infrastructure. | ||
|
|
||
| To enable this, specific **Document Type Identifiers** have been officially registered within the PEPPOL network for the various SETU message types. These identifiers are crucial for the **identification and processing** of the messages within the network. They ensure that the receiving system recognizes the type of SETU message and can process its content accordingly. **The image below provides an example overview of the Document Type Identifiers assigned to SETU messages. For the complete, authoritative list, please refer to the official PEPPOL Codelists page mentioned below.** |
There was a problem hiding this comment.
'have been officially' --> 'are'
app/docs/notes/Setu-Peppol.md
Outdated
|
|
||
| Through agreements between SETU and the Dutch Peppol Authority (NPa), standard SETU XML messages can now be sent using the PEPPOL network infrastructure. | ||
|
|
||
| To enable this, specific **Document Type Identifiers** have been officially registered within the PEPPOL network for the various SETU message types. These identifiers are crucial for the **identification and processing** of the messages within the network. They ensure that the receiving system recognizes the type of SETU message and can process its content accordingly. **The image below provides an example overview of the Document Type Identifiers assigned to SETU messages. For the complete, authoritative list, please refer to the official PEPPOL Codelists page mentioned below.** |
There was a problem hiding this comment.
Add direct link to https://docs.peppol.eu/edelivery/codelists/ for 'PEPPOL Codelists' here
app/docs/notes/Setu-Peppol.md
Outdated
| To send or receive SETU messages via the PEPPOL network: | ||
|
|
||
| 1. **Connect to a PEPPOL Access Point Provider:** Your organization needs a connection to the PEPPOL network via a certified PEPPOL Access Point (AP) provider. You can find a list of providers operating in the Netherlands via the NPa website. While technically possible, implementing your own AP is significantly more complex. | ||
| 2. **Use the Correct Document Type Identifiers:** Ensure that your software and/or your Access Point provider are configured to use the correct, officially registered Document Type Identifiers for the specific SETU messages you intend to exchange. This Document Type Identifier should be included within the PEPPOL envelope when sending the message. The complete, authoritative list of all official PEPPOL Document Type Identifiers (including those for SETU) is maintained on the [official PEPPOL Codelists page](https://docs.peppol.eu/edelivery/codelists/). Refer to the image example above for the SETU-specific identifiers. |
There was a problem hiding this comment.
Remove this sentence 'Refer to the image example above for the SETU-specific identifiers.'
app/docs/notes/Setu-Peppol.md
Outdated
|
|
||
| 1. **Connect to a PEPPOL Access Point Provider:** Your organization needs a connection to the PEPPOL network via a certified PEPPOL Access Point (AP) provider. You can find a list of providers operating in the Netherlands via the NPa website. While technically possible, implementing your own AP is significantly more complex. | ||
| 2. **Use the Correct Document Type Identifiers:** Ensure that your software and/or your Access Point provider are configured to use the correct, officially registered Document Type Identifiers for the specific SETU messages you intend to exchange. This Document Type Identifier should be included within the PEPPOL envelope when sending the message. The complete, authoritative list of all official PEPPOL Document Type Identifiers (including those for SETU) is maintained on the [official PEPPOL Codelists page](https://docs.peppol.eu/edelivery/codelists/). Refer to the image example above for the SETU-specific identifiers. | ||
| 3. **Agree with Trading Partners:** Coordinate with your business partners to confirm that you will be exchanging SETU messages using the PEPPOL network. |
There was a problem hiding this comment.
Trading partners is the term used by PEPPOL. Let's use SETU terminology here: staffing customers and/or staffing suppliers or use the neutral term business partners
app/docs/notes/Setu-Peppol.md
Outdated
| 2. **Use the Correct Document Type Identifiers:** Ensure that your software and/or your Access Point provider are configured to use the correct, officially registered Document Type Identifiers for the specific SETU messages you intend to exchange. This Document Type Identifier should be included within the PEPPOL envelope when sending the message. The complete, authoritative list of all official PEPPOL Document Type Identifiers (including those for SETU) is maintained on the [official PEPPOL Codelists page](https://docs.peppol.eu/edelivery/codelists/). Refer to the image example above for the SETU-specific identifiers. | ||
| 3. **Agree with Trading Partners:** Coordinate with your business partners to confirm that you will be exchanging SETU messages using the PEPPOL network. | ||
|
|
||
| ## Support |
There was a problem hiding this comment.
Very good and clear section
app/docs/notes/Setu-Peppol.md
Outdated
| @@ -0,0 +1,29 @@ | |||
|
|
|||
| # Sending SETU Messages via PEPPOL | |||
There was a problem hiding this comment.
Don't use PEPPOL. with full caps. The official writing is Peppol. Find + replace in whole document
app/sidebars.js
Outdated
| } | ||
| ] | ||
| }, | ||
| { |
There was a problem hiding this comment.
I think it is best to put this doc about Peppol directly under and as last item in the menu category 'API documentation'.
For that we also need to update the category page. It now describes the HTTP methods, which is not needed because it is general knowledge. This category page can instead explain that for the SETU messages we have the option to implement the OAS specifications provided by SETU and for the Purchase to Pay messages the PEPPOL infrastructure is also an option.
There is one note regarding the PUT operation on this page. Let's move that to a seperate new page under the usage notes section. Very minimal, very short, only about this interpretation of the PUT operation.
3 participants
No description provided.