csprd01-UBL-2.2-comment-disposition
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZAA
1
Comment Resolution Account for UBL 2.2 CSPRD01 published
http://lists.oasis-open.org/archives/ubl-comment/201701/msg00003.html
2
Prepared:2017-09-30
3
4
Comment
#
Public reviewDate providedLink to emailLink to
JIRA
CommenterComment provided / Issue raisedTC decision on resolution
5
BK01
UBL-2.2-csprd01
2017-01-31
https://lists.oasis-open.org/archives/ubl-comment/201701/msg00007.html
https://issues.oasis-open.org/browse/UBL-62
Boris Kortiak
Inability of Firefox to parse UBL XML hub documentThe n-dash entity reference is replaced with the U+2013 n-dash character.
6
CT01
UBL-2.2-csprd01
2017-02-01
https://lists.oasis-open.org/archives/ubl-comment/201702/msg00001.html
https://issues.oasis-open.org/browse/UBL-63
Clearview Trade
Package is missing a OrderReferenceAgreed to move to next release
7
CT02
UBL-2.2-csprd01
2017-02-01
https://lists.oasis-open.org/archives/ubl-comment/201702/msg00001.html
https://issues.oasis-open.org/browse/UBL-64
Clearview Trade
GoodsItem is missing a OrderLineReferenceAgreed to move to next release
8
CT03
UBL-2.2-csprd01
2017-02-01
https://lists.oasis-open.org/archives/ubl-comment/201702/msg00001.html
https://issues.oasis-open.org/browse/UBL-65
Clearview Trade
Package is missing a ContentDescription (Textual description of the content of the package)Agreed to move to next release
9
CT04
UBL-2.2-csprd01
2017-02-01
https://lists.oasis-open.org/archives/ubl-comment/201702/msg00001.html
https://issues.oasis-open.org/browse/UBL-66
Clearview Trade
Package is missing PackaingType, or PackingDescription (A text describing the type of packing, in case no code is provided, eg. “Pallet 80x135cm”)Agreed to move to next release
10
CT05
UBL-2.2-csprd01
2017-02-01
https://lists.oasis-open.org/archives/ubl-comment/201702/msg00001.html
https://issues.oasis-open.org/browse/UBL-67
Clearview Trade
General comment: The 2.1 principle of providing codes as text is not implement for the fulfillment documents.Agreed to move to next release
11
CT06
UBL-2.2-csprd01
2017-02-01
https://lists.oasis-open.org/archives/ubl-comment/201702/msg00001.html
https://issues.oasis-open.org/browse/UBL-68
Clearview Trade
General comment: The principle of having DocumentReference I all documents is missing in GoodsItemItenery, RetailEvent, TransportProgressStatus, TransportServiceRequest, TransportServiceDescription, WeightStatementAgreed to move to next release
12
CT07
UBL-2.2-csprd01
2017-02-01
https://lists.oasis-open.org/archives/ubl-comment/201702/msg00001.html
https://issues.oasis-open.org/browse/UBL-69
Clearview Trade
Pacakge is missing a StackableIndicator to indicate whether the package can be stacked or not)Agreed to move to next release
13
CT08
UBL-2.2-csprd01
2017-02-01
https://lists.oasis-open.org/archives/ubl-comment/201702/msg00001.html
https://issues.oasis-open.org/browse/UBL-70
Clearview Trade
Package is missing a PackageInstanceId (0..n) to identify each package with the barcode, eg. SSCC. This can also be considered for TransportHanlingUnit.Agreed to move to next release
14
CT09
UBL-2.2-csprd01
2017-02-01
https://lists.oasis-open.org/archives/ubl-comment/201702/msg00001.html
https://issues.oasis-open.org/browse/UBL-71
Clearview Trade
Package is missing a PickupBatchId or RampId in order to group the packages that should leave with the same truck.Agreed to move to next release
15
CT10
UBL-2.2-csprd01
2017-02-01
https://lists.oasis-open.org/archives/ubl-comment/201702/msg00001.html
https://issues.oasis-open.org/browse/UBL-72
Clearview Trade
Cac:Shipment/cac:OrigineOfOrigine should be 0..n instead of 0..1. If the product is compAgreed to move to next release
16
CT11
UBL-2.2-csprd01
2017-02-01
https://lists.oasis-open.org/archives/ubl-comment/201702/msg00001.html
https://issues.oasis-open.org/browse/UBL-73
Clearview Trade
CertificateOfOrigineApplcation is missing a way to specify the price for the service, eg. An allowanceChargeAgreed to move to next release
17
CT12
UBL-2.2-csprd01
2017-02-01
https://lists.oasis-open.org/archives/ubl-comment/201702/msg00001.html
https://issues.oasis-open.org/browse/UBL-74
Clearview Trade
CertificateOfOrigineApplication or DcoumentDistribution is missing a PickUpAddress, in case the document is printed out as paper and what to be picked up instead of sentAgreed to move to next release
18
CT13
UBL-2.2-csprd01
2017-02-01
https://lists.oasis-open.org/archives/ubl-comment/201702/msg00001.html
https://issues.oasis-open.org/browse/UBL-75
Clearview Trade
CertificateOfOrigineApplication is missing a OrderedPaperCopiesNumeric to specify the number of paper copies the consignor want to order.Agreed to move to next release
19
CT14
UBL-2.2-csprd01
2017-02-01
https://lists.oasis-open.org/archives/ubl-comment/201702/msg00001.html
https://issues.oasis-open.org/browse/UBL-76
Clearview Trade
BillOfLaden and or Waibill is missing a typeCode so it can be used as CMR and Air WaybillAgreed to move to next release
20
CK01
UBL-2.2-csprd01
2017-02-06
https://lists.oasis-open.org/archives/ubl-comment/201702/msg00005.html
https://issues.oasis-open.org/browse/UBL-77
e-SENScbc:HashAlgorithmMethod: should rather be an identifier or code value, since hash algorithms are usually refered to by URI References as specified by W3C XMLEnc. Maybe introducing HashAlgorithmMehtodIdentifier or HahsAlgorithmMethodCode alongside the now given textual representation might be a feasible solution. Consider possibly for 2.3 but nothing for 2.2
21
CK02
UBL-2.2-csprd01
2017-02-06
https://lists.oasis-open.org/archives/ubl-comment/201702/msg00005.html
https://issues.oasis-open.org/browse/UBL-78
e-SENSTender/cac:TenderedProject: current cardinality is 1..*; however since the tendered project is solely identified/referenced by the Tender/cbc:ContractFolderID the cac:TenderedProject currently serves only as a vessel for the lotIdentifier within the project (atleast for the syntax mapping done by CEN/BII). So the cardinality should rather be 0..* instead. Decided to use ContractFolderID ... no action on this ticket.
22
CE01
UBL-2.2-csprd01
2017-02-07
https://lists.oasis-open.org/archives/ubl-comment/201702/msg00007.html
https://issues.oasis-open.org/browse/UBL-79
TC AdminCover page edits from TC AdminResolved
23
EC01
UBL-2.2-csprd01
2017-03-16
https://lists.oasis-open.org/archives/ubl-comment/201703/msg00000.html
https://issues.oasis-open.org/browse/UBL-80
Eur. Comm.ContractFolderID - Should be depreacted in favour of Procurement Project ID
See also https://lists.oasis-open.org/archives/ubl-comment/201703/msg00002.html
Continue to use ContractFolderID ... no action on this ticket.
24
EC02
UBL-2.2-csprd01
2017-03-16
https://lists.oasis-open.org/archives/ubl-comment/201703/msg00000.html
https://issues.oasis-open.org/browse/UBL-81
Eur. Comm.Criterion - the Criterion element would need a "Confidentiality Indicator" (true==confidential, false == non-confidential;Agreed and the spreadsheet has been updated.
25
EC03
UBL-2.2-csprd01
2017-03-16
https://lists.oasis-open.org/archives/ubl-comment/201703/msg00000.html
https://issues.oasis-open.org/browse/UBL-82
Eur. Comm.Criterion - A new element "CriterionWeighting" (Percentage?) should be necessary to specify the weight of the Criterion in 2 phases Procurement ProceduresConcept is sufficiently expressed already. No action
26
EC04
UBL-2.2-csprd01
2017-03-16
https://lists.oasis-open.org/archives/ubl-comment/201703/msg00000.html
https://issues.oasis-open.org/browse/UBL-83
Eur. Comm.CriterionRequirement - A set of 0..n "Applicable Code" (Code + Description) would be necessary in the UBL TenderingCriterionRequirement element. This would be used by the CA to: 1) specify the CPVs for a Specific Average Turnover. See Github wiki page 2. Specific Turnover. 2) specify the type of financial ratios. See Github wiki page 3. Financial Ratios.Add to the spreadsheet "ExpectedCode" as a new BBIE 0..1 in TenderingCriterionRequirement.
27
EC05
UBL-2.2-csprd01
2017-03-16
https://lists.oasis-open.org/archives/ubl-comment/201703/msg00000.html
https://issues.oasis-open.org/browse/UBL-84
Eur. Comm.Economic Operator - The Economic Operator needs to aggregate data about related EO. The relationship needs also to be described. Proposal: define a new RelatedEO element with cardinality 0..nAlready can be expressed in UBL 2.2. No action
28
EC06
UBL-2.2-csprd01
2017-03-16
https://lists.oasis-open.org/archives/ubl-comment/201703/msg00000.html
https://issues.oasis-open.org/browse/UBL-85
Eur. Comm.Economic Operator - An element "Related Economic Operator" would be necessary inside the Economic Operator. Fields: Type of Relationship (the EO roles, in the case of the ESPD), Type of ID (see IDTypeCodeList), Type of Activity for this specific PP (free-text field);Cardinality changed for Economic Operator Party to 1..n in the Response
29
EC07
UBL-2.2-csprd01
2017-03-16
https://lists.oasis-open.org/archives/ubl-comment/201703/msg00000.html
https://issues.oasis-open.org/browse/UBL-86
Eur. Comm.ESPDType - We'll need a "ESPDType" to identify the ESPD as "Regulated" or "Self-Contained".Added QualificationApplicationTypeCode with 0..1 to QualificationApplicationRequest and QualificationApplicationResponse specifying the type of the qualification application.
30
EC08
UBL-2.2-csprd01
2017-03-16
https://lists.oasis-open.org/archives/ubl-comment/201703/msg00000.html
https://issues.oasis-open.org/browse/UBL-87
Eur. Comm.ESPDRequest - 2 new element would be necessary to specify the scoring methodology and the weighting type: WeightScoringMethodologyDescription, WeightingTypeAlready in TenderingCriterion
31
EC09
UBL-2.2-csprd01
2017-03-16
https://lists.oasis-open.org/archives/ubl-comment/201703/msg00000.html
https://issues.oasis-open.org/browse/UBL-88
Eur. Comm.Evidence - A "Confidentiality Level" code should be added; Default Proposed Business Rule: if the Criterion is indicated as confidential the Evidence should become confidential, too, even if it's confidentiality code is "Public". If the Criterion is not confidential the Evidence should be treated according to the confidentiality level (1) Secret, 2) Confidential, 3) Public)Spreadsheet modified with additional level code in evidence.
32
EC10
UBL-2.2-csprd01
2017-03-16
https://lists.oasis-open.org/archives/ubl-comment/201703/msg00000.html
https://issues.oasis-open.org/browse/UBL-89
Eur. Comm.ESPDRequest/Lots - The following data should be possible for the CA to specify referring to Lots: "LotsQuantityType", "Maximum Number of Lots", "Maximum Number Of Lots Awarded to One Tenderer"Current data model can accommodate the requirement. No action
33
EC11
UBL-2.2-csprd01
2017-03-16
https://lists.oasis-open.org/archives/ubl-comment/201703/msg00000.html
https://issues.oasis-open.org/browse/UBL-90
Eur. Comm.ESPDResponse/Lots - The EO should be able to specify the Lots to which it wishes to tenderCurrent data model can accommodate the requirement. Definition to be improved.
34
EC12
UBL-2.2-csprd01
2017-03-16
https://lists.oasis-open.org/archives/ubl-comment/201703/msg00000.html
https://issues.oasis-open.org/browse/UBL-91
Eur. Comm.Procurement Project - Should be renamed "Procurement Procedure"Current data model can accommodate the requirement. No action
35
EC13
UBL-2.2-csprd01
2017-03-16
https://lists.oasis-open.org/archives/ubl-comment/201703/msg00000.html
https://issues.oasis-open.org/browse/UBL-92
Eur. Comm.Procurement Project - The new "Procurement Procedure" would need to refer to one or more "Procurement Procedure Publication Board" elements
See also https://lists.oasis-open.org/archives/ubl-comment/201703/msg00002.html
Current data model can accommodate the requirement. No action
36
EC14
UBL-2.2-csprd01
2017-03-16
https://lists.oasis-open.org/archives/ubl-comment/201703/msg00000.html
https://issues.oasis-open.org/browse/UBL-93
Eur. Comm.Procurement Procedure Publication Board - Fields: ID, Official Name, Country, Jurisdiction Level (EU, National, Regional, Local), URL
See also https://lists.oasis-open.org/archives/ubl-comment/201703/msg00002.html
Current data model can accommodate the requirement. The DocumentTypeCode of the AdditionalDocumentReference can be used.
37
EC15
UBL-2.2-csprd01
2017-03-16
https://lists.oasis-open.org/archives/ubl-comment/201703/msg00000.html
https://issues.oasis-open.org/browse/UBL-94
Eur. Comm.Procurement Project and Procurement Project Lot - Why do we need the two? Procurement Project Lot does already refer to the Procurement Project! I understand we do in order to not repeat the ProcurementProject data and get into inconsistencies.Current data model can accommodate the requirement. No action
38
EC16
UBL-2.2-csprd01
2017-03-16
https://lists.oasis-open.org/archives/ubl-comment/201703/msg00000.html
https://issues.oasis-open.org/browse/UBL-95
Eur. Comm.Wouldn’t it make sense having the evidences out the Response, at the root level? This way two or more responses could point at the one evidence that has been specified once (thus having more “generic” evidences).Added evidence supplied to tendering criterion response
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
 
 
 
Sheet1
Sheet2
Sheet3