Re: [ubl] Your 15 day Public Review of UBL v2.1 CSPRD03 has been announced

[joao.frade@pwc.be]

Dear Chet, Dear Ken, Dear Tim, Dear all,

I am responding to the Public Review of UBL v2.1 CSPRD03, launched on 15 March 2013.

As you may know, I am supporting the European Commission digitising pre-award processes using UBL. In this context, we have been reviewing all XSDs connect with pre-award e-Procurement. We have therefore piloted the use of UBL documents for submitting tenders in electronic format. Our tests showed that the most important features are provided but there are still a few issues to be resolved. I would therefore like to report the following 4 issues on behalf of the European Commission:

        1. In the UBL-Tender-2.1.xsd, there is no way to link a DocumentReference to a specific Lot.

The lots can be specified by using the following element:

Tender/cac:TenderedProject/cac:ProcurementProjectLot

However, in the document reference:

Tender/cac:DocumentReference

there is no (child or other) element that can be used to link the document to a specific Lot.

        2. In the UBL-Tender-2.1.xsd, there is no way to specify the envelope type associated to a document.

In the document reference:

Tender/cac:DocumentReference

there is no (child or other) element to specify the envelope type, i.e. if the document belongs to the financial or to the technical envelope of the tender (very common in EU tenders).

        3. In the UBL-Tender-2.1.xsd, there is no way to specify the envelope type associated to a document.

In the context of restricted procedures, it would be helpful to have an element to specify the related qualification xml document. In this type of procedure the qualification document is sent before the tender, in the tender.xml we should be able to specify the link with the previously sent qualification.

        4. In the UBL-TendererQualification-2.1, the cardinality of Completed tasks for evidences should be 0..n instead of 0..1

The cardinality of the field:

../cac:CompletedTasks/cac:EvidenceSupplied

should be 0..n, as several evidences might be needed for the completed tasks.
The other similar fields in the same xsd:

../cac:TechnicalCapability/cac:EvidenceSupplied
../cac:FinancialCapability/cac:EvidenceSupplied

already have a 0..n cardinality.

I would appreciate it if you could acknowledge receipt of these comments as described in OASIS’ requirements for handling comments.

Thank you very much in advance.

With kind regards,

João

Joao Frade
PwC | Senior Manager
Direct: +32 2 7109284 | Mobile: +32 477 842292 | Fax: +32 2 7107224
Email: joao.frade@pwc.be
PwC Enterprise Advisory cvba/scrl
Firm legal information, click here




From:        Chet Ensign <chet.ensign@oasis-open.org>
To:        ubl@lists.oasis-open.org
Date:        15/03/2013 23:11
Subject:        [ubl] Your 15 day Public Review of UBL v2.1 CSPRD03 has been announced
Sent by:        <ubl@lists.oasis-open.org>

---

Members of the UBL TC,

Your 15 day public review for UBL v2.1 has been announced. The review ends
on 02 April 2013. You can find the announcement at https://www.oasis-open.org/news/announcements/15-day-public-review-for-universal-business-language-v2-1.

Please consider forwarding this announcement on to other parties who may
be interested in the work. In my experience, TCs that actively solicit
outside review get more and better quality feedback on their specifications.

Also, please keep in mind the OASIS requirements for handling comments
[1]. Non-TC member feedback can only be submitted to the TC's comment list
ubl-comment@lists.oasis-open.org. The TC must have someone subscribed to
this mail list to monitor comments. All submitted comments must be acknowledged
by the TC. In addition, the TC needs to maintain a log of comments received
and their resolutions. The comment resolution log will need to be avaiable
when you begin your next public review. A simple comment resolution log
template is available in OpenDocument [2] and Office [3] format. 

Let me know if you have any questions regarding the review or next steps.

=== Additional references:
[1] https://www.oasis-open.org/resources/tcadmin/handling-the-comments-received-during-a-public-review

[2] https://www.oasis-open.org/sites/www.oasis-open.org/files/Simple-comment-resolution-log-template_0.ods

[3] https://www.oasis-open.org/sites/www.oasis-open.org/files/Simple-comment-resolution-log-template_0.xls

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393






---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php




*Professional Mail*

*Professional Mail*------------------------------------------------------------------------------------------
This e-mail is intended only for the person to whom it is addressed.
If an addressing or transmission error has misdirected this e-mail,
please notify the author by replying to this e-mail. If you are not
the intended recipient you must not use, disclose, copy, print or
rely on this e-mail.
 
PwC may monitor outgoing and incoming e-mails and
other telecommunications on its e-mail and telecommunications systems.
------------------------------------------------------------------------------------------