diff --git a/guides/shared/links.adoc b/guides/shared/links.adoc index 7901a042..e029e5b9 100644 --- a/guides/shared/links.adoc +++ b/guides/shared/links.adoc @@ -22,6 +22,7 @@ :P013: https://docs.peppol.eu/pracc/profiles/p013/index.html[P013 Invitation to Tender] //PEPPOL Transactions Preaward +:T003: https://docs.peppol.eu/pracc/transactions/T003/index.html[T003 - Tender Status Inquiry] :T004: https://docs.peppol.eu/pracc/transactions/T004/index.html[T004 Call for Tenders] :T024: https://docs.peppol.eu/pracc/transactions/T024/index.html[T024 Invitation to tender] diff --git a/guides/transactions/T004/descriptions/attachment.adoc b/guides/transactions/T004/descriptions/attachment.adoc index b0306ab6..5abbb1dc 100644 --- a/guides/transactions/T004/descriptions/attachment.adoc +++ b/guides/transactions/T004/descriptions/attachment.adoc @@ -2,11 +2,14 @@ Using this transaction, the information of the tendering process and the details of the procurement project are described in unstructured files. The call for tenders reference the unstructured files so it is possible to access them through their URI. -The `cac:AdditionalDocumentReference` class contains references to all the files for the tenderers to prepare their bids. The mandatory `cbc:ID` element contains an identifier of the file, and the `cac:DocumentStatusCode` is used to inform the tenderer about the action that has to be done with the current document. +The `cac:AdditionalDocumentReference` class contains references to all the files for the tenderers to prepare their bids. The mandatory `cbc:ID` element contains an identifier of the file, and the `cac:DocumentStatusCode` is used to inform the tenderers about the action that has to be done with the current document. -Find below an example on how to define a provided document reference based on the e-SENS pilot project. +Find below an example on how to define a document reference that provides a document for reading purposes only. -In this example, the contents of the coded elements DocumentTypeCode and DocumentStatusCode have been defined following the e-SENS project coded values. +In this example, the contents of the coded elements DocumentTypeCode and DocumentStatusCode have been defined following the coded values of `documentTypeCode`: + +* The code `Provided` or `Pro` is used to indicate that a document is provided as part of an Invitation to Tender or tender. It must include a physical attachment. The value `No Return (NR)` of the codelist `documentStatusCode` indicates that the document must not be returned during the bid or tender (e.g. the encryption certificate to encrypt a tender) +* The code `Required` or `Req` is used to indicate that a document must be created by the economic operator as part of the bid or tender (e.g. a template that need to be filled). As documents that are classified as `Required` must be returned, they cannot use the value `No Return (NR)` of the codelist `documentStatusCode`. The remaining values of that codelist however, could indicate that document MUST be returned but no signature is required (e.g. `Return without signature (RWOS)`) or that an advanced signature is required. [source,xml,indent=0] diff --git a/guides/transactions/T004/descriptions/index.adoc b/guides/transactions/T004/descriptions/index.adoc index e0e51e97..4449a0e3 100644 --- a/guides/transactions/T004/descriptions/index.adoc +++ b/guides/transactions/T004/descriptions/index.adoc @@ -13,6 +13,7 @@ include::attachment.adoc[] include::espd.adoc[] + include::transport-encryption.adoc[] :leveloffset: -1 diff --git a/guides/transactions/T004/descriptions/transport-encryption.adoc b/guides/transactions/T004/descriptions/transport-encryption.adoc index 75d7eadb..94f14554 100644 --- a/guides/transactions/T004/descriptions/transport-encryption.adoc +++ b/guides/transactions/T004/descriptions/transport-encryption.adoc @@ -29,13 +29,30 @@ Value supplied by tendering system of the CA. Is not necessarily populated with | Provided document name | 1..1 | cac:Attachment/cac:ExternalReference/cbc:FileName | Name of a document that is provided as part of a tender or call for tenders. The extension of the file MUST be “cer”. |=== +Alternatively a provided document URI could be used to reference the encryption certificate. + +[cols="3,2,3,4"] +|=== + +| Provided document URI | 1..1 | cac:Attachment/cac:ExternalReference/cbc:URI | A URI to the document provided inside the ASIC-E package. The extension of the file MUST be “cer”. +|=== + [source,xml,indent=0] -.Example of the CfT (partly) for transporting the encryption certificate +.Example of the CfT (partly) for transporting the encryption certificate with cbc:FileName ---- include::../{xml-doc-file}[tags=AdditionalDocumentReference1] ---- + +[source,xml,indent=0] +.Example of the CfT (partly) for transporting the encryption certificate with cbc:URI + +---- +include::../{xml-doc-file}[tags=AdditionalDocumentReference4] + +---- + //http://wiki.ds.unipi.gr/download/attachments/31425187/20170127%20-%20CfT.xml?version=1&modificationDate=1485523756000&api=v2[20170127 - CfT.xml] diff --git a/guides/transactions/T004/files/call-for-tenders-instance-doc.xml b/guides/transactions/T004/files/call-for-tenders-instance-doc.xml index 466fa339..7e5a9c80 100644 --- a/guides/transactions/T004/files/call-for-tenders-instance-doc.xml +++ b/guides/transactions/T004/files/call-for-tenders-instance-doc.xml @@ -12,7 +12,7 @@ 1 - tenderenckey.cer + TenderEncryptionCertificate 2016-06-27+02:00 PRO NR @@ -24,6 +24,20 @@ + + + TenderEncryptionCertificate + 2016-06-27+02:00 + PRO + NR + + + cid:tenderenckey.cer + application/pkix-cert + + + + Bekanntmachung diff --git a/guides/transactions/T004/files/call-for-tenders-instance.xml b/guides/transactions/T004/files/call-for-tenders-instance.xml index b54ffd04..f8ca5ba9 100644 --- a/guides/transactions/T004/files/call-for-tenders-instance.xml +++ b/guides/transactions/T004/files/call-for-tenders-instance.xml @@ -12,13 +12,14 @@ 13:32:12+02:00 1 - tenderenckey.cer + TenderEncryptionCertificate 2016-06-27+02:00 PRO NR cid:tenderenckey.cer + application/pkix-cert diff --git a/guides/transactions/T024/descriptions/attachment.adoc b/guides/transactions/T024/descriptions/attachment.adoc index 5c704016..530d8a31 100644 --- a/guides/transactions/T024/descriptions/attachment.adoc +++ b/guides/transactions/T024/descriptions/attachment.adoc @@ -4,9 +4,12 @@ Using this transaction, the information of the tendering process and the details The `cac:AdditionalDocumentReference` class contains references to all the files for the tenderers to prepare their bids. The mandatory `cbc:ID` element contains an identifier of the file, and the `cac:DocumentStatusCode` is used to inform the tenderers about the action that has to be done with the current document. -Find below an example on how to define a provided document reference. +Find below an example on how to define a document reference that provides a document for reading purposes only. -In this example, the contents of the coded elements DocumentTypeCode and DocumentStatusCode have been defined following the coded values of `documentTypeCode` to indicate if a document is provided for reading and information or required for return as part of the bid (e.g. a template that need to be filled). +In this example, the contents of the coded elements DocumentTypeCode and DocumentStatusCode have been defined following the coded values of `documentTypeCode`: + +* The code `Provided` or `Pro` is used to indicate that a document is provided as part of an Invitation to Tender or tender. It must include a physical attachment. The value `No Return (NR)` of the codelist `documentStatusCode` indicates that the document must not be returned during the bid or tender (e.g. the encryption certificate to encrypt a tender) +* The code `Required` or `Req` is used to indicate that a document must be created by the economic operator as part of the bid or tender (e.g. a template that need to be filled). As documents that are classified as `Required` must be returned, they cannot use the value `No Return (NR)` of the codelist `documentStatusCode`. The remaining values of that codelist however, could indicate that document MUST be returned but no signature is required (e.g. `Return without signature (RWOS)`) or that an advanced signature is required. [source,xml,indent=0] diff --git a/guides/transactions/T024/descriptions/index.adoc b/guides/transactions/T024/descriptions/index.adoc index e0e51e97..5b59c00b 100644 --- a/guides/transactions/T024/descriptions/index.adoc +++ b/guides/transactions/T024/descriptions/index.adoc @@ -11,7 +11,7 @@ include::tendering-process.adoc[] include::attachment.adoc[] -include::espd.adoc[] +//include::espd.adoc[] include::transport-encryption.adoc[] diff --git a/guides/transactions/T024/descriptions/procurement-project.adoc b/guides/transactions/T024/descriptions/procurement-project.adoc index 432f9963..ccd4ec44 100644 --- a/guides/transactions/T024/descriptions/procurement-project.adoc +++ b/guides/transactions/T024/descriptions/procurement-project.adoc @@ -23,13 +23,13 @@ include::../{xml-doc-file}[tags=ProcurementProject] ---- -== Invitation to tender with lots +== Invitation to Tender with lots When the Invitation to Tender has to be split into lots, the `cac:ProcurementProject` class must define the overall summary of the project and there must be a `cac:ProcurementProjectLot` class per each lot. The `cac:ProcurementProjectLot` class only requires to define the lot identifier and the name of the Lot. All the details on the lot are described as unstructured documents referred from the `cac:AdditionalDocumentReference` class. -The details of each lot are described using unstructured documents referred into this invitation to tender. +The details of each lot are described using unstructured documents referred in the Invitation to Tender. [source,xml,indent=0] .{name-trans-short} with lots diff --git a/guides/transactions/T024/descriptions/transport-encryption.adoc b/guides/transactions/T024/descriptions/transport-encryption.adoc index 63dcf7d3..8d4774a9 100644 --- a/guides/transactions/T024/descriptions/transport-encryption.adoc +++ b/guides/transactions/T024/descriptions/transport-encryption.adoc @@ -3,11 +3,13 @@ == Introduction -The Invitation to Tender (ItT) business document is used by the contracting authority to provide a qualified economic operator with the latest updated procurement documents. Sending the invitation to tender to any of the remaining economic operators determines the final step of the procurement procedure. Besides transporting procurement documents it MUST be used to transport the encryption certificate needed by the economic operator to encrypt his tender for submission. -#Since the invitation to tender is also used to sent out business document changes after the tenderer has requested for status-updates (by sending a status-update-inquiry), any Invitation to tender MUST contain the encryption certificate needed by the economic operator to encrypt his tender for submission. +The Invitation to Tender (ItT) business document is used by the contracting authority to provide a qualified economic operator with the latest updated procurement documents. Sending the Invitation to Tender to any of the remaining economic operators determines the second step of the restricted procurement procedure. Besides transporting procurement documents it MUST be used to transport the encryption certificate needed by the economic operator to encrypt his tender for submission. + +Since the Invitation to Tender is also used to sent out business document changes after a {T003} (by sending a status-update-inquiry), any Invitation to Tender MUST contain the encryption certificate needed by the economic operator to encrypt his tender for submission. + == Encryption certificate -The encryption certificate MUST be transported as an attachment within the invitation to tender's'ASIC. The Invitation to tender business document contains metadata regarding all attachments thus also for the tender encryption certificate. +The encryption certificate MUST be transported as an attachment within the Invitation to Tender's'ASIC. The Invitation to Tender business document contains metadata regarding all attachments thus also for the tender encryption certificate. This metadata is resembled by the UBL container cac:AdditionalDocumentReference. In the case of the encryption certificate this container MUST contain the elements and values mentioned in the table below. @@ -29,13 +31,29 @@ Value supplied by tendering system of the CA. Is not necessarily populated with | Provided document name | 1..1 | cac:Attachment/cac:ExternalReference/cbc:FileName | Name of a document that is provided as part of a tender or call for tenders. The extension of the file MUST be “cer”. |=== +Alternatively a provided document URI could be used to reference the encryption certificate. + +[cols="3,2,3,4"] +|=== + +| Provided document URI | 1..1 | cac:Attachment/cac:ExternalReference/cbc:URI | A URI to the document provided inside the ASIC-E package. The extension of the file MUST be “cer”. +|=== + [source,xml,indent=0] -.Example of the CfT (partly) for transporting the encryption certificate +.Example of the CfT (partly) for transporting the encryption certificate with cbc:FileName ---- include::../{xml-doc-file}[tags=AdditionalDocumentReference1] ---- +[source,xml,indent=0] +.Example of the CfT (partly) for transporting the encryption certificate with cbc:URI + +---- +include::../{xml-doc-file}[tags=AdditionalDocumentReference4] + +---- + //http://wiki.ds.unipi.gr/download/attachments/31425187/20170127%20-%20CfT.xml?version=1&modificationDate=1485523756000&api=v2[20170127 - CfT.xml] diff --git a/guides/transactions/T024/files/invitation-to-tender-instance-doc.xml b/guides/transactions/T024/files/invitation-to-tender-instance-doc.xml index 57ed0b48..2c3f8ea8 100644 --- a/guides/transactions/T024/files/invitation-to-tender-instance-doc.xml +++ b/guides/transactions/T024/files/invitation-to-tender-instance-doc.xml @@ -12,7 +12,7 @@ 1 - tenderenckey.cer + TenderEncryptionCertificate 2016-06-27+02:00 PRO NR @@ -24,6 +24,20 @@ + + + TenderEncryptionCertificate + 2016-06-27+02:00 + PRO + NR + + + cid:tenderenckey.cer + application/pkix-cert + + + + Invitation to Tender diff --git a/guides/transactions/T024/files/invitation-to-tender-instance.xml b/guides/transactions/T024/files/invitation-to-tender-instance.xml index 0d4707af..7bcb3d3e 100644 --- a/guides/transactions/T024/files/invitation-to-tender-instance.xml +++ b/guides/transactions/T024/files/invitation-to-tender-instance.xml @@ -12,13 +12,14 @@ 13:32:12+02:00 1 - tenderenckey.cer + TenderEncryptionCertificate 2016-06-27+02:00 PRO NR cid:tenderenckey.cer + application/pkix-cert diff --git a/structure/syntax/CallForTenders.xml b/structure/syntax/CallForTenders.xml index 3e9d1e24..ef7d7856 100644 --- a/structure/syntax/CallForTenders.xml +++ b/structure/syntax/CallForTenders.xml @@ -212,14 +212,14 @@ cbc:MimeCode Document mime type code - Stands for + A code specifying the type of the document. The mime type of the file that and allows finding the correct application to open the document at the download sink. MUST be 'application/pkix-cert' for the encryption certificate. Code cbc:FileName Provided document name - Name of a document that is provided as part of a tender or call for tender. + Name of a document that is provided as part of the Call for Tender. The extension of the file MUST be 'cer' for the encryption certificate. PEPPOL-T004-R035 Text diff --git a/structure/syntax/InvitationToTender.xml b/structure/syntax/InvitationToTender.xml index 181f8b52..2306e143 100644 --- a/structure/syntax/InvitationToTender.xml +++ b/structure/syntax/InvitationToTender.xml @@ -212,14 +212,14 @@ cbc:MimeCode Document mime type code - Stands for the document type and allows finding the correct application to open the document at the download sink. + A code specifying the type of the document. The mime type of the file that and allows finding the correct application to open the document at the download sink. MUST be 'application/pkix-cert' for the encryption certificate. Code cbc:FileName Provided document name - Name of a document that is provided as part of the invitation to tender. + Name of a document that is provided as part of the invitation to tender. The extension of the file MUST be 'cer' for the encryption certificate. PEPPOL-T024-R035 Text