[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Comments of the European Commission, DG Informatics, on UBL package version 2.1
Dear UBL TC,
I am hereby sending you the comments of the European Commission, DG Informatics (DIGIT), on the recently released UBL package (version 2.1) for public review.
DIGIT is a user of UBL 2.0, its e-Procurement infrastructure (e-PRIOR) makes available a number of e-Procurement services to the Suppliers of the European Commission based on UBL 2.0 documents. Some of the issues below are blocking and need urgent solving. Our comments are all on the XSDs included in this package. Thank you very much in advance for considering our comments.
We would appreciate it, if you could confirm receipt of our 18 comments and let us know whether they will be incorporated in the revised version of this specification. We remain available to further clarify these comments and expand on them either orally or by e-mail.
Please do not hesitate to contact me should you require additional information.
With best regards,
João Rodrigues Frade
+32 2 299 4183
Regarding the Catalogue document:
1 - The "AllowanceCharge" element should be present under the CatalogueLine\RequiredItemLocationQuantity\Price
2 - The "RequiredItem LocationQuantity" or the "Price" element should have a child element which allows us to express the price of an item as a percentage of the price of another item e.g. as it already happens in some Calls for Tender of the European Institutions
3 - At the European Commission, some prices are defined for entire regions of the globe (e.g. Europe of USA) instead of countries. We therefore require a child element like "WorldRegion" within "ApplicableTerritoryAddress" to hold this information
Regarding the Order document:
4 - The "WarrantyInformation" element should be present under OrderLine/LineItem (as it happens in the Catalogue)
Regarding the AttachedDocument document:
5 - The "ParentVersionID" should be added as child element
6 - A "ParentLineID" element should also be added as child element
7- A "FileName" element should also be added as child element
Regarding the CreditNote document:
8- To be aligned with the Invoice there should be at least the "OrderLineReference" under the "CreditNoteLine"
9 – It would be easier for implementers if the "CreditNote" and "Invoice" are aligned at header and line level and this is not yet the case
Regarding the RequestForQuotation document:
10- We would appreciate it, if you could make the "SubmissionDueDate" element part of the cac: (instead of cbc:) with a "DocumentReference" and a "DueDate". This would enable additional flexibility in the document flow. For this same reason, this element should be unbounded in the RequestForQuotation document
Regarding the Quotation document:
11 – There should be a reference to a "RequestLineReference" at "QuotationLine" level
Regarding the "DocumentReference" element:
12 - "VersionID" should be added as child element
13- It would be useful to add the "Contract" element as child since this information is sometimes missing when we cross-reference documents
14- It would be useful to add the "LifeStatusCode" element as child since this information is sometimes used when we cross-reference documents
15- "Description" should be added as child element
Regarding the "ContractType" element:
16 - "VersionID" should be added as child element
17 - "Description" should be added as child element
18 - We would like to add an optional element like "Contract Lot" with children elements such as "Name", "Description", "MarketProcedureID" and "MarketProcedureType"