Dear all
Here are some qualifications of the items to discuss today, thanks to Kees.
Best regards
Peter
Fra: Duvekot, Kees [mailto:kduvekot@Wehkamp.nl]
Sendt: 12. april 2012 16:24
Til: plb@ebconnect.dk
Cc: Schuijt, Edwin
Emne: RE: Meeting in the UBL PSC friday the 13th of April (scary date) 11.00 CET
Peter,
I will try to attend the meeting, but I might have a scheduling conflict.
Below you will find our response already to the questions raised by the UBL TC in RED
If you have any questions you would to discuss before this meeting then please give me a call on my mobile
(+31 626 022 911)
Kees
================
2. We have received requests for several NEW items:
http://lists.oasis-open.org/archives/ubl-psc/201204/msg00001.html
Following is a quick assessment from the TC level as input back to
PSC.
"1) Change cardinality for status in Response to 0..*"
See
This is a change from 0..1 to 0..many.
The change is backward compatible with 2.0 but not reversible
in 2.2. Is there a good reason for this? If so, what is it?
The cac:Status contains a cbc:SequenceID implying that multiple statuses can be communicated, where the sequenceID determines the order of these statuses. But this conflicts with the 0..1 cardinality of the cac:status in the cac:Response. The cac:status element is also used in the cac:TransportHandlingUnit and there it already has an cardinality of 0..*
So it would make sence to change it here also.
"2) Add InventoryReportLine->InventoryLocation (0..1)
(Definition. Specifies where the go)"
This adds an optional item.
The change is backward compatible with 2.0 but not reversible
in 2.2. Is there a good reason for this? If so, what is it?
The definition of the InventoryReport says:
Report about the quantities of each item which are or will be on stock.
But on the InventoryReportLine there is no place to determine WHERE this inventory is located. This location can be different then the location details of the RetailerCustomerParty. Therefore adding a InventoryLocation to the InventoryReportLine is a way to solve this.
InventoryLocation can be based on the cac:LocationType just like cac:StorageLocation or cac:PysicalLocation.
"3) How to exchange contact information? Should we have a party"
Incomplete sentence; we don't know what this means.
The idea was a business document to exchange party related information between party’s. These can then be used by the recipient of this document to correctly populate party related elements in other UBL documents.
"4) Add TaxTotal on lineItem"
This is presumably the addition of an optional element.
The change is backward compatible with 2.0 but not reversible
in 2.2. Is there a good reason for this? If so, what is it?
This item is related to communicating VAT information on line level. Currently there is no possibility to communicate detailed VAT information on line level. Adding a TaxTotal on LineItem will partly solve this in relation with 5).
"5) Better calculation model on line level."
UBL does not define calculation models. This is not a change
to our models or schemas and therefore needs no action from
us.
This is related to a discussion on the UBL-Dev mailinglist: http://lists.oasis-open.org/archives/ubl-dev/201112/msg00008.html
Based on that discussion it was clear to us that currently it is not possible to correctly communicate VAT information on LineItem level correctly. Also see point 4)
"6) Add OrderLineReference til LineItem"
This is presumably the addition of an optional element.
The change is backward compatible with 2.0 but not reversible
in 2.2. Is there a good reason for this? If so, what is it?
By adding the OrderLineReference on the LineItem you can use this as a reference to an other order at linelevel. For example a LineItem on a return order can point to a specific LineItem on the original order. By making this a 0..* element it can even be used to link other LineItems (but that would also require adding a “LineItemType” to the OrderLineReference (LineItem, SellerPorposeSubsituted etc) to more precisely pinpoint a specific LineItem.
The final three are for consideration in 2.2:
"7) Suggestion for new documenttype: PickingListRequest (next
version)"
"8) Suggestion for new documenttype: FulfillmentOrder (next
version)" [this should be "FulfilmentOrder"]
"9) Suggestion for a new documenttype: Catalouge Response with
updates of buyer IDs (next version)"
AGREED that items 1-6 appear to be innocuous, but they need more
discussion in the PSC to determine that the changes are necessary and
provide a motivation for each. It would be helpful to have this done
in time for the Wednesday 11 April Atlantic TC call.
======================
Dus kunnen we hier samen een antwoord opgeven?
Kees
Van: Peter L. Borresen [mailto:plb@ebconnect.dk]
Verzonden: woensdag 11 april 2012 18:40
Aan: ubl-psc@lists.oasis-open.org
CC: Duvekot, Kees; joao.frade@pwc.be
Onderwerp: Meeting in the UBL PSC friday the 13th of April (scary date) 11.00 CET
Dear all
I would like to call in for a meeting in the UBL PSC.
CONFERENCING INFO
https://www2.gotomeeting.com/join/714594514
Use your microphone and speakers (VoIP) - a headset is
recommended. Or, call in using your telephone.
Australia: +61 (0) 2 9037 1944
Austria: +43 (0) 7 2088 0034
Belgium: +32 (0) 28 08 9321
Canada: +1 (647) 977-5956
Denmark: +45 (0) 69 91 80 05
Finland: +358 (0) 931 58 1746
France: +33 (0) 182 880 780
Germany: +49 (0) 892 2061 159
Ireland: +353 (0) 15 290 180
Italy: +39 0 699 26 68 58
Netherlands: +31 (0) 208 908 267
New Zealand: +64 (0) 9 442 7358
Norway: +47 21 54 32 44
Spain: +34 911 23 0850
Sweden: +46 (0) 852 500 612
Switzerland: +41 (0) 435 0006 96
United Kingdom: +44 (0) 203 535 0611
United States: +1 (773) 945-1031
Access Code: 714-594-514
Meeting ID: 714-594-514
Audio PIN: Shown after joining the meeting
Agenda:
1) Discussion of the new items at http://lists.oasis-open.org/archives/ubl/201204/msg00002.html
2) Any other business
Best regards
Peter
Med venlig hilsen
Peter L. Borresen
Tlf: +4542502390
Ingen virus fundet i denne meddelelse.
Kontrolleret af AVG - www.avg.com
Version: 10.0.1424 / Virusdatabase: 2411/4933 - Udgivelsesdato: 12-04-2012