OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-pre-award message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [ubl-pre-award] Agenda for UBL Pre-award SC call 14. December 2016 16.30 CEST

At 2016-12-13 11:40 -0500, G. Ken Holman wrote:
In preparation for tomorrow's teleconference, I have these observations:

At 2016-12-13 11:19 +0000, Ole Ellerbæk Madsen wrote:
2. In ?cac:TenderingCriterionRequirement? you have ?cbc:MaximumQuantity, cbc:MinimumQuantity, and cbc:MaximimQuantity? elements. We also have now an identical requirement but not only for Quantities but also for Amounts and percentages. My question is: if you needed to specify an amount or a percentage in the TenderingCriterionRequirement would you use always the QuantityType and use the unitCode attribute to specify whether the Quantity is Euros or Percentage? This doesn?t seem very canonical, does it?

There is a ticket that has been deferred:


... but the reason it was deferred is categorized as not being backward compatible. What I don't understand is that I don't see cac:TenderingCriterionRequirement in UBL 2.1, so I don't know why this would be considered not backward compatible. It looks like it is new in UBL 2.2 and so it can be changed immediately if needed.

If it were a backward compatibility issue, one could impose a business rule on the quantity to state that, from a business perspective, the unitCode must be omitted, thus making it equivalent to numeric. But it won't be enforceable in the schema. And this morning I don't think it applies here.

My mistake ... ticket 33 has to do with the values found in cac:TenderResult and so cannot be changed for backward compatibility reasons (which is exactly why it was handled as such).

So, for TenderingCriterionRequirement, this is new in UBL 2.2 and so the change can be made immediately in time for CSD01 if desired. If you don't want the confusion of someone unexpectedly adding a unit of measure, and you don't want to impose a business rule of there being no unit of measure, then I believe the value should be Numeric and not Quantity.

. . . . . . Ken

Check our site for free XML, XSLT, XSL-FO and UBL developer resources |
Streaming hands-on XSLT/XPath 2 training @US$45: http://goo.gl/Dd9qBK |
Crane Softwrights Ltd. _ _ _ _ _ _ http://www.CraneSoftwrights.com/o/ |
G Ken Holman _ _ _ _ _ _ _ _ _ _ mailto:gkholman@CraneSoftwrights.com |
Google+ blog _ _ _ _ _ http://plus.google.com/+GKenHolman-Crane/posts |
Legal business disclaimers: _ _ http://www.CraneSoftwrights.com/legal |

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]