Documents
Resources
Learning Center
Upload
Plans & pricing Sign in
Sign Out

ubl-psc meeting - OASIS

VIEWS: 15 PAGES: 270

									Sheet


Resolved Issues (PRD01)


PRD02 Issues

ubl-psc meeting

PRD03 Issues




Latest updated of this document
Modified sheet
Description
It contains the list of issues received before than the first public review. To know which
issues gave been implemented in the UBL-2.1-PRD1-20100925 package, look at the
column "Status" and look for issues marked as "Done".
It contains the list of issues received during the first public review + the pending issues from
"Resolved Issues (PRD01)" sheet. The issues having yellow background colour will be
including in PRD2.
It contains the list of issues raised and resolved during the ubl-psc F2F (Copenhagen, 24th
november 2010). All issues will be in PRD2

It contains the list of issues that still have to be discussed. The will be included in PRD2.




10th may 2011
PRD02 Issues, PRD03 Issues
Submitter          Email                       Date      Category     Resolution
                                               Submitted              Team
Dave Fitzpatrick   fitzpatrick_david@bah.com        03/06 Transport   TSC
(EFM project)

Dave Fitzpatrick   fitzpatrick_david@bah.com        03/06 Transport   TSC
(EFM project)




Dave Fitzpatrick   fitzpatrick_david@bah.com        03/06 Transport   TSC
(EFM project)




David Webber       david@drrw.info                  05/08 ubl-dev     Oriol, Sven




CODICE             oriol@invinet.org               Nov-09             Oriol, Martin,
                                                                      Tim, Sven
                                                 Roberto, Tim,
Roberto Cisternino roberto@javest.com   Mar-10   Andy
Roberto Cisternino roberto@javest.com   Mar-10   Roberto, Tim




                                                 Roberto, Tim,
Roberto Cisternino roberto@javest.com   Mar-10   Andy

                                                 Roberto, Tim,
Roberto Cisternino roberto@javest.com   Mar-10   Andy




                                                 Roberto, Tim,
Roberto Cisternino roberto@javest.com   Mar-10   Andy




                                                 Roberto, Tim,
Roberto Cisternino roberto@javest.com   Mar-10   Andy
                                                 Roberto, Tim,
Roberto Cisternino roberto@javest.com   Mar-10   Andy




                                                 Roberto,
Roberto Cisternino roberto@javest.com   Apr-10   Sven
CODICE             oriol@invinet.org    sep-10   Arianna, Oriol




JRF               joao.frade@pwc.be     sep-10   Tim, Joao,
                                                 Oriol




                                                 Arianna,
ubl-itlsc                               oct-10   Martin



                                                 Arianna,
ubl-itlsc                               oct-10   Martin



                                                 Arianna,
ubl-itlsc                               oct-10   Martin
                                                 Tim, Joao,
                                                 Oriol

ubl-itlsc                               Nov-10
Georg Birgisson      Nov-10

Oriol Bausà          Feb-11




Roberto Cisternino   Mar-11



ubl-psc              Mar-11
Ken Holman      Apr-11




Stephen Green   may-11
Issue Type                                         Issue

New           Desire to define size constraints on XML elements.
Requirement

Bug           Business processes to be revised and completed according to the existing
              business practices. For example: the freight forwarding instructions between
              the shipper and the freight forwarder has to be complemented by the
              shipping instructions to the actual carrier - the certificate of origin process
              has no direct relationship with the bill of lading


New           UBL 2.0 transport messages are standalone xml schemas with each based
Requirement   upon the same data dictionaries. These transport messages need to be
              related to each other via some kind of context or process. There should be
              a higher level \"dialogue\" that presents how these messages may be used
              together in a more global business transaction.

New           In looking at the Catalogue XSD - when you generate a complete XML
Requirement   instance per the XSD schema - you get a 2.1MB transaction!!!

              Clearly - noone is sending 2.1MB to describe one catalogue item (least I
              hope not!).

              So - when I look at the content - most all of it relates to static CONTRACT
              related information - that really could be placed into a separate and new
              UBL transaction - and then simply referenced by an ID.

              This would introduce a new process flow into the information equation - but
              seems entirely logical. So if I need to know the contract conditions relating
              to an item - I can request that.

              The design decision to burden the catalogue exchange with Contract related
              content (which makes up 90%) - seems counter intuitive - when that could
              be sent separately on request once - instead of everytime the catalogue
              entry is updated.

              Not only that - but I strongly suspect the Contract information is repetitive -
              so one contract could cover most all the items in the catalogue - again -
              dramatically reducing information exchange volume.

              The contract information can then also be aligned to local tax regulations
              more closely - such as EU VAT - and serve better fit to purpose roles.
New           Create New Document Model Tender Envelope to wrap Tender documents.
Document
Model
Add BBIE to   In "TransportMeans" other JourneyIDs with specified who is the
ABIE          issuer/owner should be added.
               In "TransportMeans" there is already a "OwnerParty" but it seems to generic
               for expressing an important info like the shipping line.
                 The definition of this party could be tricky as usually we require a
               specific "ShippingLineCode" and "ShippingLineName" information, for
               instance.
                 I would suggest to provide a wrapper of the plain Party aggregate (like
               we have for the AccountingCustomerParty in the Invoice)
                 For instance:
                 OwnerParty:
                 - CarrierCode 0..1 (e.g. SCL)
                 - CarrierShortName 0..1 (e.g. SAFMARINE)
                 - CarrierGroupCode 0..1 (e.g. MSK)
                 - CarrierGroupName 0..1 (e.g. MAERSK)
                 - JointServiceGroupCode 0..1 (e.g. UFS)
                 - JointServiceGroupname 0..1 (e.g. United Feeder Services)
                 - Party 0..1
                 - OperativeContact 0..1

Additional       NOTE: the Party still provides the possibility to specify the legal
requirement    name of the carrier and other possible info.




               In "TransportMeans", if not already available upper in the hieararchy (in a
Add ASBIE to   better place), there could be the requirement of the following additional
ABIE           info: add a "Customs Forwarder" 0..1
               In "TransportMeans", if not already available upper in the hieararchy (in a
Add ASBIE to   better place), there could be the requirement of the following additional
ABIE           info: add a "MTOParty" (Multimodal transport operator) 0..1


              In "TransportMeans" the "RoadTransport" is no more identified by a single
              Plate ID information.
              For security reasons the Driver Surname and name or License to Drive ID
              could be required together the Plate ID.
              I suggest to enhance this part:
              - by changing the "LicensePlateID" into "TruckPlateID"
Change BBIE - by adding a "DriverParty" or a "Person"
name and add NOTE: the License to drive (if required) can be specified on either a
ASBIE to ABIE Party or Person aggregates.




              In "TransportMeans" the "RailTransport" requires more information.
Change BBIE I suggest to:
name and add - Change the "RailCarID" name to "CargoWaggonID"
ASBIE to ABIE - Add a DocumentReference to reference a specific Raylways document.
               In "TransportMeans" the "MaritimeTransport" requires more information.
               I suggest to add an "InternationalRadioCallSignID" (0..1). This is a more
Add ASBIE to   common Vessel identification used in the shipping chain. This is a unique
ABIE           identifier available from ITU where every Ship has a radio call sign ID.

              The actual Statement seems to be too much oriented to the
              outstanding invoices, so it is difficult to specify Collected payments
              (settled invoices).
Add ASBIE to I would suggest to add cac:CollectedPayment (0..n) with a structure like the
ABIE          cac:PrepaidPayment.
Add ASBIE to Add a Qualification Resolution class (0..n) into Unawarded Notification as
document type the new Directive mandates notify about the awarding to the tenderers
              excluded during the admission and exclusion phase, informing them again
              about the reasons for the exclusion.




Add ASBIE to
ABIE           Regarding the "ContractType" element: we would like to add an optional
               element like "Contract Lot" with children elements such as "Name",
               "Description", "MarketProcedureID" and "MarketProcedureType"




               The code list UNECE_DutyorTaxorFeeCategoryCode_D09B should be
code list      suggested for the cac:TaxCategory/cbc:ID.



               The code list UNECE_DutyTaxFeeTypeCode_D09B should be suggested
code list      for the cac:TaxScheme/cbc:ID.



              The code list EDIFICASEU_TaxExemptionReason_D09B should be
code list     suggested for the cbc:TaxExemptionReasonCode.
              Into building or huge procurements there are work phases and thus also
              invoices are referencing one or more phases of the work. Also invoices
Add BBIE to   could be issued at the end of each phase. The invoice should contain a
document type reference ID to the Work Progress phase
              In Invoice, the definition of cbc:AccountinCost should change for "The
              Buyer's reference, such as accounting code, applied to the Invoice as a
              whole, expressed as text." and the definition of cbc:AccountingCostCode
Change        should change for "The Buyer's reference, such as accounting code applied
definition    to the Invoice as a whole.".
Add BBIE to   Person class: In Spain we have a second surname. I'd suggest to add a
ABIE          MotherSurname or SecondSurname in Person.

              1) Add a new ABIE named "WithholdingTaxTotal" after the "TaxTotal"

              2) Add the new "WithholdingTaxTotal" ABIE under the cac:InvoiceLine after
              the "TaxTotal" (this will be used to identify those line items subject to
              withholding tax)

              The proposed definition for WithholdingTaxTotal is: "An association to
              Withholding Tax Total."
New ABIE
              Addition of document-wide signature elements to the five document
Add ABIE to   types that currently lack them: (CallForTenders, CatalogueRequest,
document      ContractAwardNotice, ContractNotice, PriorInformationNotice)
model
             In a recent UBL-Dev exchange, I noted the absence of a starting date for
             the acceptable period for responding to an RFQ:
               http://lists.oasis-open.org/archives/ubl-dev/201104/msg00001.html
             The end of the acceptable period is <SubmissionDueDate>. I'm guessing
             the assumption is that the response is immediately allowed to be submitted.
             I don't have a lot of experience with RFQs but I could imagine the requester
             not being prepared to accept RFQs until a particular acceptable starting
             date, not necessarily immediately. Do we need another BBIE to indicate
             that acceptable starting date?
             I'll assume so, otherwise ignore the rest of the post.
             Since what we have isn't labeled an "end" date, I don't think we should
             name the new item a "start" date. I don't know what the antipode of "due" is
             ... perhaps <SubmissionAcceptableDate> or <SubmissionAllowedDate>
             would be appropriate.
             In UBL 2.x there is an XPath BBIE which allows an XPath expression
             to be included in a UBL document. It is used in the DocumentReference. I
             suggest to add a new ABIE in order to allow implementers to replace the
             use of this XPath BBIE with the use of rather more rigorous XQuery
             expressions which are able to include XPath 2.0(+) expressions (a subset of
Add new ABIE XQuery 1.0+) but are less ambiguous with regard to namespace bindings
and ASBIE    and versions.
 Recommendation           Clarification         Disposition

Section 1.6,                              Customization
Customization, should                     guildeslines section 3.4
offer guidance on how                     must be updated with an
and when to place size                    example




                                          Being process by TSC




                                          Being process by TSC
                                          To be review in
If you create a new                       conjountion with the
transaction                               preawarding message
interchange as a                          Contract. A contract must
supplemental pathway -                    be able to refer to a
should be possible to                     catalogue and vice versa
run those in parallel -                   (thte exists a referece
and since the core                        today, but it must be
components are all the                    reviewet after the contract
same - would allow                        has been designed)
people to use simple
XSLT to morph to/from
as needed.
JourneyID: This is the
Carrier and/or Trade Service
"JourneyID", fine, but there
are often a different
JourneyIDs:
         - used within
consortium of carriers (e.g.
United FeederServices, Inc.)
           NOTE:In this case
a Ship (or other means) is
operating as part of an
alliance, but each party has
a different Journey
ID (very bad yes!)
         - used by
Container/goods terminals.
           NOTE: Container
terminals are a good sample
as mny different carriers are
visiting a terminal, thus
using different
JourneyIDs that cannot be
unique from the Terminal
point of
view (every carrier has its
voy counter and syntax)
              That's why it is
important to keep the
relationship
between different Journey
IDs.                           TSC
                               For public review.

Should be named
"CustomsForwarderParty",
anyway I am not really sure
this party is needed here...
As I mentioned it should be
located in other context.      TSC


                            TSC
LicensePlateID cannot be
renamed for backward
compatibility with UBL 2.0.
I would suggest to add a
DriverPerson derivated from
cac:Person.
This way the LicensePlateID
will be used to express the
truck plate ID and the
license to drive ID will be
expressed as part of the    TSC


RailCarID cannot be
renamed...for backward
compatibility with UBL 2.0.
The DocumentReference for
rail are called "Rail
Memorandum"                 TSC
                        I provide a sample vessel
                        code list where either the
                        mentioned "radio call sign
                        ID" and the "IMO Ship ID"
                        are used for Vessels:
                        http://www.contshipitalia.co
                        m/servlet/DownloadShipping TSC

                                                  The recommedation was
This                                              approved. Roberto and
CollectedPayment                                  Georg will define the
should be on Line                                 structure of
Items.                                            CollectedPayment ABIE
                                                  This issue was
                                                  postponed; a new input
                                                  arrived and it could erase
                                                  this issue:
                                                  "UnawardedNotification
                                                  and AwardedNotificatio
                                                  should be merged in a
                                                  single document".


Contract supports
subdivision                                       For prd2.
                                                  Approved. Put the
                                                  reference inside the
                                                  documentation (in
                                                  Example column; if
                                                  available, put the link).
                                                  Approved. Put the
                                                  reference inside the
                                                  documentation (in
                                                  Example column; if
                                                  available, put the link).
                                                  Waiting feedback from
                                                  Martin. Put the reference
                                                  inside the documentation
                                                  (in Example column; if
                                                  available, put the link).


see issue 64 in PRD02
Issues sheet                                      For prd2.
The business case is that
there is a common
requirement to make
reference to the other
parties unqualified
reference. On printed
documents this is often
called "Your refernece" the
nature of the reference can
be pretty much anything
such as project number or
whatever. There are several
qualified reference elments
that are usefule but the need
is to hava an unqualified
one.

One possible mapping for
this is to use the
AccountingCost element,
based on the logic that the
purpost of the unqualified
reference is to enable
accounting key allocation.

I suggest that in order to
make this mapping more
clear, we change the
definition of the following
element in the following way.
This is backward compatible
because it still point to the
use of the accounting code,
Please, see email
http://lists.oasis-
open.org/archives/ubl-
comment/201105/msg00001
.html for full explanation and
proposal.
                       Status                            Action




Resolution team is working on. It will be discussed in
Ankara.
waiting for feedback from Georg and Roberto




To do.




To do.




To do.
Under discussion by mail. We have a feedback from
Peter that says: "in OIOUBL the
reference is expressed as
AccountingCustomerParty/Party/Contact/ID"
Under discussion by mail. See Tim's proposal sent by
mail on 23/02/2011 01:45
Under discussion by mail
                      Remark                              Action   Schema
                                                           no      reviewer




Ken says:
I've found thousands of elements related to
<cac:ContractorCustomerParty> through both the
document level and the line level ... but I have not
found any explicit contract information whatsoever ...
only information describing a *reference* to a
contract. The party information is necessarily
extensive because of the options offered to describe
agents, legal entities, etc.

But as for simplifying the contract information per se,
I don't see where. Note that my analysis is only
based on a search of the term "contract" in element
names in the XPath files ... of course I may be
overlooking the contract information you are
referring to.

So, can you cite for me which contract information
you think should be removed from Catalogue when
people are defining their own customizations of
UBL? Of course this cannot be "removed" in the
UBL 2.1 specification, but for a reader of this mail
list archive, they should know that any optional item
in UBL can of course be deprecated by a
customization that dictates to its community of users
Issues from ubl-psc meeting in CPH (november 2010)
In Invoice change InvoiceDueDate for DueDate.

Add OriginatorDocumentReference to CreditNote


Add Delivery, DeliveryTerms, PaymentMeans and PaymentTerms to CreditNote
Compare DebitNote with CreditNote and Invoice. Also for SelfBillInvoice and SelBillCreditNote



FreeOfChargeIndicator,InvoicePeriod, OrderLineReference, OriginatorParty, PaymentTerms, DeliveryTerms
must be added in CreditNoteLine
Compare DebitNoteLine with CreditNoteLine and InvoiceLine.

A new ABIE must be created: DependentPriceReference. It has: Percentage (0..1, BBIE), Location_Address
(0..1, ASBIE), Dependent_LineReference (0..1, ASBIE)
Add DependentPriceReference ABIE to ItemLocationQuantity (0..1).


Results of comparison between DebitNote and Invoice/CreditNote:
1- AllowanceCharge is present in Invoice and CreditNote, it is missing in DebitNote. It should be added to
DebitNote;
2- LegalMonetaryTotal is present in Invoice and CreditNote, it is missing in DebitNote where
RequestedMonetaryTotal is present. LegalMonetaryTotal and RequestedMonetaryTotal have equivalent
meaning: no changes should be needed;
3- PrepaidPayment is present in Invoice and DebitNote, it is missing in CreditNote. It is NOT needed to add it
to CreditNote (it was decided in CPH-meeting);
4- Delivery, DeliveryTerms, PaymentMeans and PaymentTerms are present in Invoice and will be added to
CreditNote, while they are missing in DebitNote. They should be added to DebitNote.

Results of comparison between SelfBilledInvoice and SelfBilledCreditNote:
1- PaymentCurrencyCode and PaymentAlternativeCurrencyCode are present in SelfBilledInvoice, they are
missing in SelBilledCreditNote They should be added to SelBilledCreditNote;
2- StatementDocumentReference and OriginatorDocumentReference are present in SelfBilledInvoice, they
are missing in SelBilledCreditNote They should be added to SelBilledCreditNote;
3- Delivery, DeliveryTerms, PaymentMeans and PaymentTerms are present in SelfBilledInvoice, they are
missing in SelBilledCreditNote They should be added to SelBilledCreditNote;
4- PrepaidPayment is present in SelfBilledInvoice, it is missing in SelBilledCreditNote. It is NOT needed to add
it to SelBilledCreditNote (like CreditNote)
5- PaymentExchangeRate and PaymentAlternativeExchangeRate are present in SelfBilledInvoice, they are
missing in SelBilledCreditNote They should be added to SelBilledCreditNote;

Results of comparison between DebitNoteLine and CreditNoteLine:
1- AllowanceCharge is present in Invoice and CreditNoteLine, it is missing in DebitNoteLine. It should be
added to DebitNote.

Results of comparison between SelfBillInvoice and Invoice:
1- DueDate is missing in SelfBillInvoice; it is NOT needed to added it in SelfBilled invoice, since it SelfBilled
invoice, since it;
2- StatmentDocumentReference is present in SelfBilledInvoice but it is missing in Invoice; it should be added
to Invoice, CreditNote and DebitNote
Status
Done.
Done. Originator_DocumentReference has been
added to CreditNote (0..n).
Delivery, DeliveryTerms, PaymentMeans and
PaymentTerms ha been added to CreditNote
(0..n).
see row 13 and 15

Done. FreeOfChargeIndicator (0..1), InvoicePeriod
(0..n), OrderLineReference (0..n), OriginatorParty
(0..1), PaymentTerms (0..n), DeliveryTerms (0..n)
has been added in CreditNoteLine
see row 17


Done.
Done.




Done. AllowanceCharge, Delivery, DeliveryTerms,
PaymentMeans and PaymentTerms has been
added to DebitNote (0..n).




Done. PaymentCurrencyCode (0..1),
PaymentAlternativeCurrencyCode (0..1),
StatementDocumentReference (0..n),
OriginatorDocumentReference (0..n), Delivery
(0..n), DeliveryTerms (0..n), PaymentMeans (0..n),
PaymentTerms (0..n), PaymentExchangeRate
(0..1), PaymentAlternativeExchangeRate (0..1)
added to SelfBilledCreditNote.


Done. AllowanceCharge has been added to
CreditNoteLine (0..n).




Done. Statment_DocumentReference has been
added to CreditNote, Invoice and DebitNote (0..n).
Submitter          Email                           Date Category
                                               Submitted
Dave Fitzpatrick   fitzpatrick_david@bah.com       03/06 Transport
(EFM project)

Dave Fitzpatrick   fitzpatrick_david@bah.com       03/06 Transport
(EFM project)




Dave Fitzpatrick   fitzpatrick_david@bah.com       03/06 Transport
(EFM project)




David Webber       david@drrw.info                 05/08 ubl-dev
Daniel Toffeti   dtoffe@yahoo.com.ar      11/08 ubl-dev




Nick Hoggard     Nicholas.Hoggard@gen-    12/08 ubl-dev
                 i.co.nz




BII wg1          georg@eykur.is          Sep-09




BII wg1          georg@eykur.is          Sep-09
                                                 Financial




Roberto Cisternino roberto@javest.com   Mar-09
                                                 Financial/Tax




Roberto Cisternino roberto@javest.com   aug-09
JRF                joao.frade@pwc.be    Nov-09
ubl-psc                                 Nov-09

CODICE            oriol@invinet.org     Nov-09




CODICE            oriol@invinet.org     Nov-09

CODICE            oriol@invinet.org     Nov-09




Roberto Cisternino roberto@javest.com   Mar-10


Roberto Cisternino roberto@javest.com   Mar-10




Roberto Cisternino roberto@javest.com   Mar-10
Roberto Cisternino roberto@javest.com   Mar-10




Roberto Cisternino roberto@javest.com   Mar-10
Roberto Cisternino roberto@javest.com   Mar-10




Roberto Cisternino roberto@javest.com   Mar-10


Roberto Cisternino roberto@javest.com   Mar-10




Roberto Cisternino roberto@javest.com   Mar-10




Roberto Cisternino roberto@javest.com   Mar-10
Roberto Cisternino roberto@javest.com   Mar-10




Roberto Cisternino roberto@javest.com   Mar-10
JRF                joao.frade@pwc.be



                                        Mar-10




ubl-psc                                 Mar-10


ubl-psc                                 Mar-10




ubl-psc                                 Mar-10




ubl-psc                                 Mar-10




ubl-psc                                 Mar-10
ubl-psc                                 Mar-10




Roberto Cisternino roberto@javest.com   Apr-10




Roberto Cisternino roberto@javest.com   Apr-10



Roberto Cisternino roberto@javest.com   Apr-10
JRF                joao.frade@pwc.be

                                        may-10
JRF               joao.frade@pwc.be



                                        may-10
JRF               joao.frade@pwc.be




                                        may-10
JRF               joao.frade@pwc.be




                                        may-10
JRF      joao.frade@pwc.be




                             may-10
CODICE   oriol@invinet.org   sep-10




CODICE   oriol@invinet.org   sep-10




CODICE   oriol@invinet.org   sep-10




JRF      joao.frade@pwc.be   sep-10




JRF      joao.frade@pwc.be   sep-10



JRF      joao.frade@pwc.be   sep-10



JRF      joao.frade@pwc.be   sep-10

JRF      joao.frade@pwc.be   sep-10

JRF      joao.frade@pwc.be   sep-10

JRF      joao.frade@pwc.be   sep-10
JRF               joao.frade@pwc.be         sep-10



JRF               joao.frade@pwc.be         sep-10


JRF               joao.frade@pwc.be         sep-10




JRF               joao.frade@pwc.be         sep-10


JRF               joao.frade@pwc.be         sep-10


JRF               joao.frade@pwc.be         sep-10


JRF               joao.frade@pwc.be         sep-10


JRF               joao.frade@pwc.be         sep-10




JRF               joao.frade@pwc.be         sep-10

JRF               joao.frade@pwc.be         sep-10

JRF               joao.frade@pwc.be         sep-10




Martin Forsberg   martin.forsberg@ecru.se   oct-10


Martin Forsberg   martin.forsberg@ecru.se   oct-10


Martin Forsberg   martin.forsberg@ecru.se   oct-10



Ole Madsen        olem@itst.dk              oct-10
Ole Madsen   olem@itst.dk   oct-10




Ole Madsen   olem@itst.dk   oct-10




Ole Madsen   olem@itst.dk   oct-10


Ole Madsen   olem@itst.dk   oct-10




Ole Madsen   olem@itst.dk   oct-10


Ole Madsen   olem@itst.dk   oct-10

Ole Madsen   olem@itst.dk   oct-10
Ole Madsen   olem@itst.dk   oct-10



Ole Madsen   olem@itst.dk   oct-10




Ole Madsen   olem@itst.dk   oct-10




ubl-itlsc                   oct-10




ubl-itlsc                   oct-10




ubl-itlsc                   oct-10




ubl-itlsc                   oct-10
ubl-itlsc                                   oct-10



Martin Forsberg   martin.forsberg@ecru.se   Nov-10



Martin Forsberg   martin.forsberg@ecru.se   Nov-10

Martin Forsberg   martin.forsberg@ecru.se   Nov-10



ubl-itlsc                                   Nov-10

Arianna Brutti                              Nov-10

Arianna Brutti                              Nov-10




Arianna Brutti                              Nov-10



Arianna Brutti                              Nov-10
Georg Birgisson   Nov-10

ubl-tsc           Mar-11

ubl-tsc           Mar-11



ubl-tsc           Mar-11


ubl-tsc           Mar-11
ubl-tsc           Mar-11

ubl-tsc           Mar-11
ubl-tsc           Mar-11


ubl-tsc           Mar-11
ubl-tsc           Mar-11
ubl-tsc   Mar-11


ubl-tsc   Mar-11

ubl-tsc   Mar-11



ubl-tsc   Mar-11

ubl-tsc   Mar-11

ubl-tsc   Mar-11



ubl-tsc   Mar-11

ubl-tsc   Mar-11




ubl-tsc   Mar-11
ubl-tsc   Mar-11
ubl-tsc   Mar-11

ubl-tsc   Mar-11

ubl-tsc   Mar-11


ubl-tsc   Mar-11

ubl-tsc   Mar-11


ubl-tsc   Mar-11

ubl-tsc   Mar-11

ubl-tsc   Mar-11


ubl-tsc   Mar-11

ubl-tsc   Mar-11

ubl-tsc   Mar-11
ubl-tsc   Mar-11

ubl-tsc   Mar-11



ubl-tsc   Mar-11



ubl-tsc   Mar-11



ubl-tsc   Mar-11




ubl-tsc   Mar-11

ubl-tsc   Mar-11



ubl-tsc   Mar-11




ubl-tsc   Mar-11

ubl-tsc   Mar-11

ubl-tsc   may-11

ubl-tsc   may-11



ubl-tsc   may-11
Resolution Team   Issue Type

TSC               New Requirement


TSC               Bug




TSC               New Requirement




Oriol, Sven       New Requirement
Oriol, Ken         New Requirement




Oriol, Peter       New Requirement




Georg, Tim, Andy   New Requirement




Georg, Joao        New Requirement
Georg, Roberto   Addition




Peter, Roberto   Addition




                 General
Sven                  Change cardinality

Oriol, Arianna        MissingField




                      New Requirement

Oriol, Martin, Tim,   New Document Model
Sven




Roberto, Peter, Tim   Add BBIE to ABIE


Roberto, Peter, Tim   Add BBIE to ABIE




Roberto, Peter        Change definition
Roberto, Oriol       Add BBIE to ABIE




Roberto, Tim, Andy   Add BBIE to ABIE
                     Additional
Roberto, Tim         requirement




Roberto, Tim, Andy   Add ASBIE to ABIE


Roberto, Tim, Andy   Add ASBIE to ABIE




                     Change BBIE name
                     and add ASBIE to
Roberto, Tim, Andy   ABIE




                     Change BBIE name
                     and add ASBIE to
Roberto, Tim, Andy   ABIE
Roberto, Tim, Andy   Add ASBIE to ABIE




                     Add ASBIE to ABIE
                     Add BBIE to ABIE




                     Change element
Peter, Tim           name


Arianna              Qualified element




Arianna              Qualified element




Arianna              Qualified element




Arianna              Qualified element
Arianna         Qualified element




                Add BBIE to
Arianna         document type




Roberto, Sven   Add ASBIE to ABIE



Roberto, Sven   Add association
Sven, Joao      Add BBIE to
                document type

Sven, Joao      Add BBIE to
                document type



Sven, Joao      Add BBIE to
                document type




Tim, Joao       Add ASBIE to ABIE
Arianna          Add ASBIE to ABIE




Arianna, Oriol   Add ASBIE to ABIE




Arianna, Oriol   Add ASBIE to
                 document type




Arianna, Oriol   Add ASBIE to
                 document type




Tim, Joao        Add ASBIE to ABIE




Oriol, Joao      Add ASBIE to ABIE



Joao, Tim        Add BBIE to ABIE



Arianna          Add BBIE to ABIE

Joao, Sven       Add BBIE to
                 document type
Joao, Sven       Add BBIE to
                 document type
Joao, Sven       Add BBIE to
                 document type
                   Add ASBIE to ABIE



                   Requirement


                   Change ABIE




Arianna, Joao      Add ASBIE to ABIE


Sven, Joao         Add BBIE to ABIE


Sven, Joao         Add ASBIE to ABIE


Sven, Joao         Add BBIE to ABIE


Sven, Joao         Add BBIE to ABIE




Peter, Joao        Add BBIE to ABIE

Peter, Joao        Add BBIE to ABIE

Tim, Joao, Oriol   Add ASBIE to ABIE




                   Add BBIE to
Oriol, Martin      document type


Oriol, Martin      Correct description


Oriol, Martin      Change cardinality



Ole, Arianna       Change BBIE name.
Ole, Arianna   Change BBIE name.




Ole, Arianna   New ABIE.




Ole, Arianna   Change BBIE name.


Ole, Arianna   Change BBIE name.




Ole, Arianna   Change BBIE name.


Ole, Arianna   Correct BBIE name.

Ole, Arianna   Add BBIE to ABIE.
Ole, Arianna      Add BBIEs to ABIE.



Ole, Arianna      Add BBIEs to ABIE.




Ole, Arianna      Change ABIE




Oriol, Arianna    Add BBIE to ABIE




                  Add ABIE to
                  document type




Arianna, Martin   code list




Arianna, Martin   code list
Arianna, Martin    code list



                   Add BBIE to ABIE



                   Add BBIE to ABIE
                   Add BBIE to
                   document type
Tim, Joao, Oriol

                   Add BBIE to
                   document type
                   Add ASBIE to
                   document type

                   Add BBIE to ABIE




Arianna, Ole       Move BBIEs



Arianna, Ole       Change cardinality
Change definition

Change cardinality
Add BBIE and
ASBIEs to ABIE


Add BBIE and
ASBIEs to ABIE


New ABIE.
Change cardinality

Add ASBIEs to ABIE
Add ASBIE to ABIE


New ABIE.
Add BBIE to ABIE
Add BBIEs to ABIE


New ABIE.

Add BIEs to ABIE



Remove BBIE

Add ASBIEs to ABIEs

Add ASBIEs to ABIEs



New ABIE.

Add BIEs to ABIE




New ABIE.
Remove ABIE
Change ABIE name

Change BBIE name

Change BBIE name


Change cardinality

Add BBIEs to ABIE

Update Document
Model

New Document Model

New Document Model

Update Document
Model

Change ASBIE

Change ASBIE
Change BBIE in ABIE
Change document
name


Move ASBIEs in
Document Models


Add BBIEs to
Document Models


Add BBIEs to
Document Models




New ABIE.
Add ASBIE to
Document Models


Add BBIEs to
Document Models




New ABIE.
Add ASBIE to
Document Models

Remove ABIE

Add BBIEs to ABIE



Change ABIEs
                                     Issue                                         Recommendation

Desire to define size constraints on XML elements.                                Section 1.6,
                                                                                  Customization, should
                                                                                  offer guidance on how
Business processes to be revised and completed according to the existing          and when to place size
business practices. For example: the freight forwarding instructions between
the shipper and the freight forwarder has to be complemented by the
shipping instructions to the actual carrier - the certificate of origin process
has no direct relationship with the bill of lading
UBL 2.0 transport messages are standalone xml schemas with each based
upon the same data dictionaries. These transport messages need to be
related to each other via some kind of context or process. There should be
a higher level \"dialogue\" that presents how these messages may be used
together in a more global business transaction.

In looking at the Catalogue XSD - when you generate a complete XML
instance per the XSD schema - you get a 2.1MB transaction!!!                      If you create a new
                                                                                  transaction
Clearly - noone is sending 2.1MB to describe one catalogue item (least I          interchange as a
hope not!).                                                                       supplemental pathway -
                                                                                  should be possible to
So - when I look at the content - most all of it relates to static CONTRACT       run those in parallel -
related information - that really could be placed into a separate and new         and since the core
UBL transaction - and then simply referenced by an ID.                            components are all the
                                                                                  same - would allow
This would introduce a new process flow into the information equation - but       people to use simple
seems entirely logical. So if I need to know the contract conditions relating     XSLT to morph to/from
to an item - I can request that.                                                  as needed.

The design decision to burden the catalogue exchange with Contract related
content (which makes up 90%) - seems counter intuitive - when that could
be sent separately on request once - instead of everytime the catalogue
entry is updated.

Not only that - but I strongly suspect the Contract information is repetitive -
so one contract could cover most all the items in the catalogue - again -
dramatically reducing information exchange volume.

The contract information can then also be aligned to local tax regulations
more closely - such as EU VAT - and serve better fit to purpose roles.
  I had a problem trying to generate JAXB Bindings for OASIS UBLv2
(http://www.oasis-open.org/specs/#ublv2.0) in the Netbeans IDE (version
6.5 rc2). The problem is with some quoted strings, in some strings the
quoting is done with opening and closing double quotes with an
hexadecimal encoding of E2 80 9C and E2 80 9D, while in the rest of the
UBL documents hexa 22 is used for a straight double quote.
    The three byte quotes seems to be valid UTF-8 since they are displayed
with the proper glyph in other text editors, and people from the ubl-dev list
confirmed this. But I'm getting an error "unmappable character for encoding
UTF-8" and the offending strings are displayed as: ?VISA?, ?MasterCard?,
etc. in the error output window in Netbeans.
   The problem seems to appear only within CommonAggregateComponents-
2,
in CardAccountType and CountryType. After suggestion from a ubl-dev list
member, I tried with the runtime xsdrt in (http://docs.oasis-open.org/ubl/os-
UBL-2.0/xsdrt/) and the problem dissappeared.
  I had a problem trying to generate JAXB Bindings for OASIS UBLv2
(http://www.oasis-open.org/specs/#ublv2.0) in the Netbeans IDE (version
6.5 rc2). The problem is with some quoted strings, in some strings the
quoting is done with opening and closing double quotes with an
hexadecimal encoding of E2 80 9C and E2 80 9D, while in the rest of the
UBL documents hexa 22 is used for a straight double quote.
    The three byte quotes seems to be valid UTF-8 since they are displayed
with the proper glyph in other text editors, and people from the ubl-dev list
confirmed this. But I'm getting an error "unmappable character for encoding
UTF-8" and the offending strings are displayed as: ?VISA?, ?MasterCard?,
etc. in the error output window in Netbeans.
   The problem seems to appear only within CommonAggregateComponents-
2,


I'm currently using the UBL 2.0 specification as part of an integration project.
So far we have avoided the need to customise the specifications in any way,
however I'm struggling with finding the correct location to populate the Head
Office Party details for the Seller Customer Party or Accounting Supplier
Party elements of the Invoice schema.



There is no support for bar code identifications. Bar codes are usually based
on existing numbers such as a particular standard ID number (GTIN) but the
encoding can be based on different standards such as EAN13, EAN128
various US code schemas and more frequently 2D codes. There is different
bar coding for different packaging levels. (need in the Catalogue)




The Application Response document does not support appeal information.
Supporting the ISO20022 End-to-End Identifier                             Add an "Invoicing
                                                                          Party_ Reference" to
                                                                          the Invoce,
                                                                          FreightInvoice,
                                                                          CreditNote. (header
                                                                          and line items)
                                                                          The
                                                                          InvoicingPartyReferen
                                                                          ce is currently
                                                                          available only in the
                                                                          root of the UBL-
                                                                          RemittanceAdvice-2.0
                                                                          but it should be
                                                                          available also in the
                                                                          RemittanceAdviceLine
                                                                          just like
                                                                          BillingReference.
                                                                          The
                                                                          InvoicingPartyReferen
                                                                          ce (The Invoicing
                                                                          Party's reference to
                                                                          the payment,
                                                                          previously requested
                                                                          of the Payer to
                                                                          accompany
                                                                          remittance.), is
                                                                          pratically the End-to-
                                                                          End Identifier required
                                                                          by the banking sector
                                                                          for payment
                                                                          reconciliation with
                                                                          invoice/s.
The Tax ID (fiscal code) of the financial account owner is requested if   By adding the
                                                                          Maybe the PayerParty
different from the debtor (Customer). Requested by the Italian P.A.       should be added to the
                                                                          FinancialAccount to
                                                                          have the ability to add
                                                                          a Tax ID (under
                                                                          PartyTaxScheme)

                                                                          See also FIRTG.05




It is not possible to provide structured Invoice Dispute Information
Evaluate if the cardinality of DocumentReference in DocumentResponse
should be 1..n.
It was decided to remove LegalForm in class TendererQualification because
there is a legal form inside the Party Legal Entity Class. The problem is that
in Tenderer Qualification there is no Party class associated, so this element
Legal Form stating the form that can be taken by the tenderer is required as
it was.

Add a FundingProgramCode in Tendering Terms in order to specify if the
contract has fundings from the EC, national level, …
Create New Document Model Tender Envelope to wrap Tender documents.




The RemittanceAdviceLine is missing a cbc:InvoicingPartyReference
The cbc:InvoicingPartyReference available in the root is not sufficient.
The Invoice (and FreightInvoice) head and the Invoice Line are missing the
cbc:InvoicingPartyReference for the same reason above described for the
Remittance Advice.




In "Statement Line", change the definition of
BalanceBroughtForwardIndicator.
In PartyLegalEntity add a new "CorporateStockNote" information entity after
"CorporateStockAmount". Definition: Additional information related to the
Corporate Stock Amount.




In "TransportMeans" other JourneyIDs with specified who is the
issuer/owner should be added.
In "TransportMeans" there is already a "OwnerParty" but it seems to generic
for expressing an important info like the shipping line.
  The definition of this party could be tricky as usually we require a
specific "ShippingLineCode" and "ShippingLineName" information, for
instance.
  I would suggest to provide a wrapper of the plain Party aggregate (like
we have for the AccountingCustomerParty in the Invoice)
  For instance:
  OwnerParty:
  - CarrierCode 0..1 (e.g. SCL)
  - CarrierShortName 0..1 (e.g. SAFMARINE)
  - CarrierGroupCode 0..1 (e.g. MSK)
  - CarrierGroupName 0..1 (e.g. MAERSK)
  - JointServiceGroupCode 0..1 (e.g. UFS)
  - JointServiceGroupname 0..1 (e.g. United Feeder Services)
  - Party 0..1
  - OperativeContact 0..1

  NOTE: the Party still provides the possibility to specify the legal
name of the carrier and other possible info.




In "TransportMeans", if not already available upper in the hieararchy (in a
better place), there could be the requirement of the following additional
info: add a "Customs Forwarder" 0..1
In "TransportMeans", if not already available upper in the hieararchy (in a
better place), there could be the requirement of the following additional
info: add a "MTOParty" (Multimodal transport operator) 0..1


In "TransportMeans" the "RoadTransport" is no more identified by a single
Plate ID information.
For security reasons the Driver Surname and name or License to Drive ID
could be required together the Plate ID.
I suggest to enhance this part:
- by changing the "LicensePlateID" into "TruckPlateID"
- by adding a "DriverParty" or a "Person"
NOTE: the License to drive (if required) can be specified on either a
Party or Person aggregates.




In "TransportMeans" the "RailTransport" requires more information.
I suggest to:
- Change the "RailCarID" name to "CargoWaggonID"
- Add a DocumentReference to reference a specific Raylways document.
In "TransportMeans" the "MaritimeTransport" requires more information.
I suggest to add an "InternationalRadioCallSignID" (0..1). This is a more
common Vessel identification used in the shipping chain. This is a unique
identifier available from ITU where every Ship has a radio call sign ID.



In Person: There is a missing a "PersonIdentity" information to be used to   We should add
precisely identify a person. The PersonIdentity could be:                    IdentityDocumentRefer
- IdentityDocumentReference 0..1                                             ence to express for
  Samples:                                                                   instance a license to
  - license to drive                                                         drive and the date of
  - passport number                                                          issue. (0..1)
  - SSN (Social Security Number)                                             Cardinality seems to
  - Fiscal Code                                                              be 0..1 as a single
  - ...                                                                      identity document is
                                                                             usually provided by a
- Also a "DigitalIdentity" could be important as it is an actual             person to an authority
information worldwide.                                                       or bank.
Add versionID to DocumentReference as optional element.




In PartyLegalEntity CompanyTypeCode should changes for
BusinessClassificationScheme.


In ForecastException PurposeCode should be qualified.




In ProcessJustification ReasonCode should be qualified.




ResultCode should be qualified wherever it is used.




ResolutionCode should be qualified wherever it is used.
In ProcurementProject TypeCode and SubTypeCode should be qualified
(suggested qualifier: Procurement).
Add a new BIE in the root of Statement: cbc:StatementTypeCode (0..1). The
"Statement of Account" can be sent by the Supplier/Creditor to the
Buyer/Debtor into different forms, for instance could be a list of outstanding
invoices or a full statement for a period (already settled, to be settled and
overdue payments). But here there are further cases.

The actual Statement seems to be too much oriented to the
outstanding invoices, so it is difficult to specify Collected payments           This
(settled invoices).                                                              CollectedPayment
I would suggest to add cac:CollectedPayment (0..n) with a structure like the     should be on Line
cac:PrepaidPayment.                                                              Items.
AllowanceCharge should be also in the Statement Line as we should allow
the possibility to specify an allowance amount related to a line and its
referenced invoices. Without these changes the UBL Statement will be far
from actual
Add ParentVersionID to AttachedDocument as optional element.


We would like to have the possibility to specify in the “AttachedDocument” a
“LineID” or “ItemID” so that attachments can be added to a specific item e.g.
in the Catalogue. This element should also be optional.


AttachedDocument does not allow that the attachment is added to a line of
the document. This means that every attachment must be attached to the
(all) document. However, we would like to use it to carry attachments to a
specific Line in the Catalogue. Therefore, we would like to add the “LineID”
in this document. This element should be optional.



At the European Commission, some contracts define prices for regions of
the globe such as Europe, North America… We currently cannot represent
this in the current structure of
Catalogue/CatalogueLine/RequiredItemLocationQuantity element. We
therefore would like to add a new optional element which enables the
specification of a “region of the globe”, Within it, we could have several
“ApplicableTerritoryAddress” elements.
When Ordering an item, we need to specify the “WarrantyValidatyPeriod” in
the Order/OrderLine. Currently this element is not present. Can you please
let us know of a workaround? Could you please add this element to the
OrderLine in 2.1




Add ASBIE TenderResult. Contract Formalization_ Period (0..1)
in Tender Result class to enable information to the awarded party in the
Contract Award Notice document and in Awarded Notification about the
period of time he has to formalize the contract.


Add an Additional Document Reference class (0..n) in Awarded Notification
and Unawarded Notification to allow the inclusion of annex documents such
as the minutes of the awarding process meetings.




Add a Qualification Resolution class (0..n) into Unawarded Notification as
the new Directive mandates notify about the awarding to the tenderers
excluded during the admission and exclusion phase, informing them again
about the reasons for the exclusion.




The "AllowanceCharge" element should be added to
the CatalogueLine\RequiredItemLocationQuantity.


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.
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
The "WarrantyInformation" element should be present under
OrderLine/LineItem (as it happens in the Catalogue)
In the AttachedDocument the "ParentVersionID" should be added as child
element
In the AttachedDocument the "ParentLineID" should be added as child
element



In the AttachedDocument the "FileName" should be added as child element
The CreditNote document should be aligned with the Invoice there should
be at least the "OrderLineReference" under the "CreditNoteLine"

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 RequestForQuotation document: 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: there should be a reference to a
"RequestLineReference" at "QuotationLine" level

Regarding "DocumentReference" element "VersionID" should be added as
child element
Regarding "DocumentReference" element. it would be useful to add the
"Contract" element as child since this information is sometimes missing
when we cross-reference documents
Regarding "DocumentReference" element: it would be useful to add the
"LifeStatusCode" element as child since this information is sometimes used
when we cross-reference documents



Regarding "DocumentReference" element: "Description" should be added
as child element
Regarding the "ContractType" element: "VersionID" should be added as
child element
Regarding the "ContractType" element: "Description" should be added as
child element

Regarding the "ContractType" element: we would like to add an optional
element like "Contract Lot" with children elements such as "Name",                Contract supports
"Description", "MarketProcedureID" and "MarketProcedureType"                      subdivision

In a Contract Notice, you often want to refer to the call for tender-document.
That makes it possible for a reader of a notice to easily find and/or
download the documents. We cannot find this document reference in the
current model and propose to add the information element.

 In Contract Notice the definition or Originator_ Customer Party is “The
party who originated Order.” which looks like a copy-paste-error
The association to location from the Procurement Project has today a 0..1
cardinality. We request it to be changed to 0..unbounded
ASBIE Procurement Project. Realized_ Location. Location

In the SubscriberConsumption the EnergyWaterSupplyID should change for
ConsumptionID because it should not be limited to WaterEnergy. This is the
ID of the specification. Cardinality should be 0..1.
In the SubscriberConsumption the EnergyWaterSupplyCode should change
for SpecificationTypeCode because it should not be limited to WaterEnergy.
In addition this is the spcification type code. Cardinality should be 0..1.




                                                                              Stick to the name:
We would like a new class EnergyTaxReport to hold a report of energy          EnergyTaxReport, as
taxes. It should have: cbc:TaxEnergyAmount (0..1),                            the legal requierement
cbc:TaxEnergyOnAccountAmount (0..1), cbc:TaxEnergyBalanceAmount               for having this report
(0..1), cac:TaxScheme (1..1)                                                  relates to energy.




                                                                     In generel all instanses
EstimatedConsumptedQuantity changes for EstimatedConsumedQuantity in of this "consumpted"
order to be consistent with that term in OnAccountPayment and        should be verified /
ConsumptionReport classes. Should be "Consumed".                     replaced!

In UnstructuredPrice the PriceAmountQuantity should change name to
PriceAmount and must be of type Amount.


In UnstructuredPrice the TimeAmountQuantity should change name to
TimeAmount and must be of type Text (could also be Time, but definitely
not quantity).


RoarningPartner changes for RoamingPartner.
TelecommunicationsService.ID is missing. There must be a field for stating
the ID for the current service instanse
                                                                               We should have a
                                                                               more flexible structure
                                                                               in order to support
                                                                               different cases …so I
                                                                               am thinking about
                                                                               something like the
                                                                               AdditionalItemProperty
                                                                               . The ABIE could be
                                                                               MeterProperty
                                                                               (cardinality 0..n) and
                                                                               its BBIEs should be
Need for a few more fields in UtilityMeter class. This is a request from the   Name (0..1),
danish hearing. The fields are needed in order to handel a typical correction, NameCode (0..1),
bound to the actual Utility meter. The fields are: ActualHeatingQuantity       Value (0..1),
(0..1), EstimatedHeatingQuantity (0..1), HeatingCorrection (0..1) and          ValueQuantity (0..1),
TotalMeasuredQuantity (0..1).                                                  ValueQualifier (0..1).


Need for two more fields in ConsumptionHistory. This is a request from the
danish hearing. The fields are: MeterNumber (0..1), Amount (0..1).

The role of ExtendedTelecommunications has been unclear. We have had
some iterations around this class and its placement within the
UtilityStatement structure. It seems you have a overlab between this class at
top-level and under consumption. In DK we have decided to exlude the one
at toplevel, and use
SubscriberConsumption.Consumption.TelecommunicationsSupply instead.



In PartyLegalEntity add a new "SoleProprietorshipIndicator" information
entity. Definition: an indicator to state if the company is owned and
controlled by one person (true) or more (false).


The Invoice is subject to legal notes related to the whole document and not
to line items. So we would add a new ABIE "LegalNote". It is required to
mention a legal reference and an optional textual note. The fields are: Note
(0..n), LegalReference (1..1).



The code list UNECE_DutyorTaxorFeeCategoryCode_D09B should be
suggested for the cac:TaxCategory/cbc:ID.



The code list UNECE_DutyTaxFeeTypeCode_D09B should be suggested
for the cac:TaxScheme/cbc:ID.
The code list EDIFICASEU_TaxExemptionReason_D09B should be
suggested for the cbc:TaxExemptionReasonCode.


In procurement project, add Procurement Project. Requested_ Delivery
Date. Date. The requested delivery date for this procurement project.


In procurement project, Procurement Project. Estimated_ Overall Contract.
Quantity. The estimated overall quantity for this procurement project.
In contract notice, add Contract Notice. Requested_ Publication Date. Date.
The requested publication date of this Contract Notice.
Into building or huge procurements there are work phases and thus also
invoices are referencing one or more phases of the work. Also invoices
could be issued at the end of each phase. The invoice should contain a
reference ID to the Work Progress phase                                     see issue 64

Add cac:AdditionalDocumentReference in the TendererQualification.

Add cbc:Description to cac:ExternalReference




In MeterType there are cbc:MeterReadingMethod,
cbc:MeterReadingMethodCode and cbc:MeterReadingComments. They
should be moved in MeterRedingtype because we can specificy more than
one reading and maybe that they have been made in different way.
We have Consumption in SubscriberConsumption and in
SupplierConsumption. I would suggest to change cardinality to make
SubscriberConsumption.Consumption optional (0..1), while
SupplierConsumption.Consumption is mandatory (1..1, as is).
In Invoice, the definition of cbc:AccountinCost should change for "The
Buyer's reference, such as accounting code, applied to the Invoice as a
whole, expressed as text." and the definition of cbc:AccountingCostCode
should change for "The Buyer's reference, such as accounting code applied
to the Invoice as a whole.".
In Address the cardinality of ASBIE LocationCoordinate changes from 0..1
to 0..n.
In Delivery, add: ReleaseID (BBIE 0..1), Carrier_Party (ASBIE 0..1),
Notify_Party (ASBIE 0..n).
In Despatch, add: ReleaseID (BBIE 0..1), Despatch_Location (ASBIE 0..1),
Carrier_Party (ASBIE 0..1), Notify_Party (ASBIE 0..n),
EstimatedDespatch_Period (ASBIE 0..1), RequestedDespatch_Period
(ASBIE 0..1).

Define a new ABIE called EnvironmentalEmission. It has following BBIEs:
EnvironmentalEmissionType (1..1), Value (1..1), Description (0..n).
In GoodsItem, cardinality of BBIE ID changes from 1..1 to 0..1
In GoodsItem, add following ASBIEs: Measurement_Dimension (0..n),
Containing_Package (0..n), Shipment_DocumentReference (0..1).
In Package add the ASBIE Containing_ Transport Equipment (0..1)
Define a new ABIE called NotificationRequirement. It has following BIEs:
NotificationType (BBIE 1..1), Notify_Party (ASBIE 0..n), PreEvent_Period
(ASBIE 0..1), PostEvent_Period (ASBIE 0..1).
In PaymentTerms add BBIE Payment Terms Details URI (0..1).
In Person add following BBIEs: NationalityID (0..1), GenderCode (0..1),
BirthDate (0..1)
Define a new ABIE called TransportContract. It has following BIEs:
NominationDate (BBIE 0..1), NominationTime (BBIE 0..1), Note (BBIE 0..n),
Contract (ASBIE 1..1).
In TransportEquipment add PowerIndicator (BBIE 0..1) and Shipment_
Document Reference (ASBIE 0..1).



In TransportExecutionTerms remove the BBIE EnvironmentalDescription
In TransportExecutionTerms add following ASBIEs: Delivery Terms (0..n),
EnvironmentalEmission (0..n), NotificationRequirement (0..n).
In TransportHandlingUnit add following ASBIEs: TransportMeans (0..n),
Shipment_ Document Reference (0..n), Status (0..n).
Define a new ABIE called TransportLocation. It has following ASBIEs:
Planned Departure_Period (0..1), Planned Arrival_Period (0..1), Estimated
Departure_ Period (0..1), Estimated Arrival_ Period (0..1), Actual Departure
(0..1), Actual Arrival (0..1), Location (0..1)
In TransportMeans add following BIEs: TransportMeansTypeCode (BBIE
0..1), Operator_Party (0..n).
Define a new ABIE called Transport Schedule. It has following ASBIEs:
SequenceNumber (BBIE 1..1), ReferenceDate (BBIE 1..1), ReferenceTime
(BBIE 1..1), Reliability (BBIE 0..1), Remarks (BBIE 0..n), Status_Location
(ABIE 1..1), EstimatedArrival_Period (ASBIE 0..1), EstimatedDeparture_
Period (ASBIE 0..1), Actual Arrival (ASBIE 0..1), ActualDepartureTransport
Event (ASBIE 0..1)
Remove the TransportStatus ABIE.
The TransportItemStatus ABIE changes name for TransportStatus
In the new TransportStatus change name of BBIE from
TransportItemTimeDeviation to TimeDeviation
In the new TransportStatus change name of BBIE from
TransportItemConditionDeviation to ConditionDeviation
In the new TransportStatus change cardinality of ASBIE Status_ Location
from 1..1 to 0..1 and of ASBIE Referenced_ Transport Handling Unit from 1
to 0..n
In TransportationService add following BBIEs: NominationDate (0..1) and
NominationTime (0..1).
In TransportExecutionPlan add following ABIEs: Shipment_ Document
Reference (0..n), Transport User Response Deadline_ Period (0..n),
Transport Service Provider Response Deadline_ Period (0..n)

The TransportServiceDescription document has been made.

The GoodsItemItinerary document has been made.
In TransportExecutionStatus, add the BBIEs: ID ( 0..1) and Transport
Execution Plan Reference (0..1), remove the ASBIE Transport Execution
Plan_ Document Reference.
In Consignment the ASBIE Transport_Contract has to be changed for
TransportContract.
In TransportExecutionPlan the ASBIE Transport_Contract has to be
changed for TransportContract.
In Status the BBIE Reference_ Date changes for BBIE ReferenceDate and
the BBIE Reference_ Time changes for ReferenceTime.
Change document name from Transport Operation Status to Transport
Progress Status


Signature ASBIE has been moved before Party ASBIEs in following
documents: TransportExecutionPlan and TransportExecutionStatus.
In the documents TransportExecutionPlan, TransportExecutionStatus,
TransportProgressStatus and GoodsItemItinerary following BBIEs have
been added: ProfileExecutionIdentifier (0..1), CopyIndicator (0..1), UUID
(0..1), Note (0..n).

In the document TransportServiceDescription following BBIEs have been
added: ProfileExecutionIdentifier (0..1), CopyIndicator (0..1), UUID (0..1),
IssueDate (0..1), IssueTime (0..1) and Note (0..n).

Define a new ABIE called Transport Segment. It has following ASBIEs:
SequenceNumber (BBIE 1..1), TransportExecutionPlanReferenceID (BBIE
1..1), TransportModeCode (BBIE 0..1), TransportMeansTypeCode (BBIE
0..1), TransportationService (ASBIE 1..1), TransportServiceProvider_ Party
(ASBIE 1..1), Carrying_ TransportEquimpent (ASBIE 0..1), Carrying_
Package (ASBIE 0..1), Carrying_ TransportMeans (ASBIE 0..1), Departure_
TransportLocation (ASBIE 0..1), Intermediate_ TransportLocation (ASBIE
0..n), Arrival_ TransportLocation (ASBIE 0..1).
In the document Transport Progress Status the TransportSchedule (ASBIE
0..n) has been added.


In the documents TransportExecutionStatus the ReferenceDate (BBIE 0..1)
and ReferenceTime (BBIE 0..1) have been added.
Define a new ABIE called ServicePoint. It has following ASBIEs:
SequenceNumberID (BBIE 1..1), TransportModeCode (BBIE 0..1),
Remarks (BBIE 0..n), ServicePoint_ Location (ASBIE 0..1),
TransportMeans (ASBIE 0..1), Planned Departure_ Period (ASBIE 0..1),
Planned Arrival_ Period (ASBIE 0..1), Planned Despatch_ Period (ASBIE
0..1), Delivery_ Period (ASBIE 0..1).
In the document TransportServiceDescription the ServicePoint (ASBIE 0..n)
has been added.

Remove the TransportContract ABIE.

Add Nomination Date and Nomination Time into the existing Contract ABIE
Change Consignment.TransportContract ASBIE for
Consignment.Transport_Contract.Contract (as it is in version 2.0).
Change TransportExecutionPlan.TransportContract ASBIE for
TransportExecutionPlan.Transport_Contract.Contract.
Clarification         Disposition                         Status

                Customization
                guildeslines need to have
                a section on field length
                restrictions (using TDED).




                Being process by TSC




                Being process by TSC
                To be review in
                conjountion with the
                preawarding message
                Contract. A contract must
                be able to refer to a
                catalogue and vice versa
                (thte exists a referece
                today, but it must be
                reviewet after the contract
                has been designed)




                                              no action
                             Ask Ken Holman how to
                             use quote properly




                                                          See the email forwarded by Tim on 17 september 09
Thank you for the response   Add a new ABIE called
to my query last week.       Corporate information and
Unfortunately the            add a new ASBIE to it in
branch making the sale is    PartyLegalEntiry
both the legal address for
the sale, and the
accounting address. Most
of the branches are
individually owned, though
they are each grouped into                                To be checked. Maybe it is resolved
                             Add Barcode ABIE to
                             ItemIdentification and to
                             ItemInstance and to
                             LotIdentification. Talk to
                             an expert to define the
                             Barcode structure.


                             Resolved. Application
                             Response supports the
                             information

                                                          No action to do.
Straight Through Processing Resolved by issue 17      No action to do
(STP) Reconciliation (End-to-
End Identifier)
*********************************
********************************
The Credit Initiation and
Direct Debit messages
specify one reference that is
intended to be passed
through the end-to-end
payment settlement
process. This element is the
End-to-End Identifier. (AKA:
primary customer reference)

Which information items is
best suited for the End-to-
End Identifier ?

In the UBL-
RemittanceAdvice-2.0 we
have two places:

a) When the ID is assigned
by the Debtor:
   cbc:ID
(An identifier for the
Remittance Advice assigned
by the Debtor)

b) When the ID is assigned
by the Creditor in the Invoice
 When a Financial Account Resolved by disposition     No action required.
has to be used it is often     on issue 28
required to provide an
identity document along with
the account (this is also in
line with ISO20022). In Italy
the personal fiscal code is
asked to be specified (C.F.).
ISO20022 solves this issue
providing the equivalent
aggregate of the UBL
Person which is providing
the possibility to specify an
"IdentityDocumentReference
" (see issue 28)


                              Resolved. Use
                              Application Response.   No action to do.
                              Approved                    Done. Cardinality has been updated (1..n).
This legal form is stated by Rejected. It is already
CompanyType in                resolved.
TendererQualification.Tende
rerPartyQualification.MainQ
ualifinParty.Party.PartyLegal
Entity                                                    No action required.
                              Accepted. Oriol will        Done. FundingProgramCode added in
                              provide a code list.        TenderingTerms.

                                                          Resolution team is working on
This reference is issued by
the payee (seller/vendor)
and the payer is requested
to accompany the
remittance with these
reference.
There could be more than
one reference for multi-
invoice reconciliation
with payments
and this reference is not
strictly 1-to-1 with a payment
or with an
invoice, so it is up to the      Resolved. Add
payee                            cbc:InvoicingPartyReferen
to specify such reference in     ce to cac:PaymentTerms
the remittance head or for       and to                    Done. cbc:InvoicingPartyReference added to
each remittance line.            cac:RemittanceAdviceLin cac:PaymentTerms and to
                                 e.                        cac:RemittanceAdviceLine (cardinality 0..1)


                                 Resolved by issue 17     No action required.



Actual Definition: If true,
indicates that the Statement
Line contains a balance
brought forward.
Proposed Definition: If true,
indicates that the Statement
Line has a balance
outstanding from the
previous bill(s)              Accepted.                   Done. Definition has been updated.
                                                     Done.
                                                     1) The ABIE ShareholderParty has been defined. Its
                                                     BIEs are: Partecipation (0..1, BBIE), Party (0..1,
                                                     ABIE).
                                                     2) The ABIE PartyLegalEntity has been updated.
                                                     Now, its BIEs are: Registration_ Name (0..1, BBIE),
                                                     CompanyID (o..1, BBIE), Registration_ Date( 0..1,
                                                     BBIE), Registration Expiration_ Date (0..1, BBIE),
                                                     Company Legal Form Code (0..1, BBIE), Sole
                           Resolution team review    Proprietorship Indicator (0..1, BBIE), Company
                           the PartyLegalEntity      Liquidation Status Code (0..1, BBIE), Corporate
Example:                   structure (see email with Stock_ Amount (0..1, BBIE), Fully Paid Shares
CorporateStockAmount =     subject "New              Indicator (0..1, BBIE), Registration_ Address (0..1,
1.000.000 EUR              PartyLegalEntity" sent by ASBIE), Corporate Registration Scheme (0..1,
CorporateStockNote = Fully Roberto on 2010-12-17     ASBIE), Head_ Party(0..1, ASBIE), Shareholeder
paid-up capita             and following).           Party (0..n, ASBIE).

JourneyID: This is the
Carrier and/or Trade Service
"JourneyID", fine, but there
are often a different
JourneyIDs:
         - used within
consortium of carriers (e.g.
United FeederServices, Inc.)
           NOTE:In this case
a Ship (or other means) is
operating as part of an
alliance, but each party has
a different Journey
ID (very bad yes!)
         - used by
Container/goods terminals.
           NOTE: Container
terminals are a good sample
as mny different carriers are
visiting a terminal, thus
using different
JourneyIDs that cannot be
unique from the Terminal
point of
view (every carrier has its
voy counter and syntax)
              That's why it is
important to keep the
relationship
between different Journey
IDs.                           TSC
                               For public review.   Postponed.

Should be named
"CustomsForwarderParty",
anyway I am not really sure
this party is needed here...
As I mentioned it should be
located in other context.      TSC


                            TSC
LicensePlateID cannot be
renamed for backward
compatibility with UBL 2.0.
I would suggest to add a
DriverPerson derivated from
cac:Person.
This way the LicensePlateID
will be used to express the
truck plate ID and the
license to drive ID will be
expressed as part of the    TSC


RailCarID cannot be
renamed...for backward
compatibility with UBL 2.0.
The DocumentReference for
rail are called "Rail
Memorandum"                 TSC
I provide a sample vessel
code list where either the
mentioned "radio call sign
ID" and the "IMO Ship ID"
are used for Vessels:
http://www.contshipitalia.co
m/servlet/DownloadShipping TSC




                             Approved. Add
                             Identity_DocumentRefern Done. IdentityDocumentRefernce has been added to
                             ce ASBIE to Person.     Person (cardinality 0..1).
There are documents which
are not subject to versioning
e.g. the Invoice but for some
others the version is actually                             Done. Version has been added to
almost mandatory e.g.          Approved.                   DocumentReference (cardinality 0..1).

                             Resolution team proposed
                             a new structure for
                             PartyLegalEntity. See
                             email from               see Issue 20.
                             Approved.                    Done. PurposeCode has been qualified as
                             The qualifier is "Forecast". ForecastPurpuseCode

                             Approved.
                             The qualifier is "Process". Done. ReasonCode has been qualified as
                             Also "Reason" should be ProcessReasonCode and Reason has been qualified
                             qualified.                  as ProcessReason

                             Approved.
                             ResultCode is in:             Done. ResultOfVerification.ResultCode has been
                             ResultOfVerification - the    qualified as
                             qualifier is 'Validation';    ResultOfVerification.ValidationResultCode and
                             TenderResult - qualifier is   TenderResult.ResultCode has been qualified as
                             'Tender'.                     TenderResult.TenderResultCode
                             Approved.
                             ResolutionCode is in
                             ExceptionCriteriaLine.
                             The qualifier is              Done. ResolutionCode has been qualified as
                             "Exception".                  ExceptionResolutionCode.
                           Approved.
                           The qualifier are
                           "Procurement" . Actually
                           SubTypeCode has 'Sub'
                           as qualifier and 'Type' as
                           Property Term                Done. ProcurementProject. Type Code changed for
                           Possessive Noun …            ProcurementProject. Procurement_ Type Code and
                           maybe the latter should      ProcurementProject. Sub_ Type Code changed for
                           be 'Sub Type'.               ProcurementProject. Procurement Sub_ Type Code




                                                        Done. The BBIE StatementTypeCode has been
                           Approved.                    defined and added to Statement document.

                           The recommedation was
                           approved. Roberto and
                           Georg will define the
                           structure of
                           CollectedPayment ABIE        waiting for feedback from Georg and Roberto
Statements are usually sent
each month to each
customer to summarize                                   Done. AllowanceCharge has been added (0..n) to
account activity. Statements Approved.                  StatementLine.
                             Approved. Add
                             ParentDocumentVersionI     Done. ParentDocument_ Version (0..1) has been
                             D.                         added to AttachedDocument.


                           Approved. Add a
                           ParentDocument_LineRef Done.ParentDocument_LineReference (0..n) has
                           erence ASBIE (0..n)    been added to AttachedDocument.




                           Resolved by issue 40.        No action to do.




                           Rejected. Already
                           present in address.          No action to do.
                            Rejected. The issue was
                            resolved (resolution was
                            adding
                            WarrantyValidityPeriod to
                            LineItem - see issue 195
                            in Resolved Issue
                            (PRD01)).                   No action.
                            Approved.
                            The
                            ContractFormalization_Pe
                            riod must be added          Done. ContractFormalization_Period has been added
                            before than                 (0..1) to TenderResult. Definition: information about
                            SubcontractTerms.           the period to formalize the contract.
                            Approved.
                            The AdditionalDocument      Done. Additional_DocumentReference has been
                            must be added below         added (0..n) to Awarded Notification and Unawarded
                            MinutesDocumentReferen      Notification. Definition: Information about a document
                            ce ASBIE                    referred to in another document. It can be used to
                                                        include annex documents such as the minutes of the
                                                        awarding process meetings.
                             This issue was
                             postponed; a new input
                             arrived and it could erase
                             this issue:
                             "UnawardedNotification
                             and AwardedNotificatio
                             should be merged in a
As in the Invoice and Order, single document".          For ubl-psc F2F in Copenhagen.
it is needed to specify
charges which
are                                                     Done. AllowanceCharge has been added (0..n) to
not embedded in the price, Approved.                    ItemLocationQuantity.

                            Resolved. See line 9-10
                            in ubl-psc meeting
                            spreadsheet.                Done. See line 9-10 in ubl-psc meeting spreadsheet.


                            Resolved. Region is in
                            Address                     No action to do.
                                                        Done. Warranty_Information has been added (0..n)
                            Approved                    to LineItem.

                            Approved                    No action to do. Resolved by issue 39.

                            Approved                    No action to do. Resolved by issue 40.
                            Rejected. Already
                            implemented: FileName
                            has been added to
                            ExternalReference           No action to do.
                          Issues 2-7 in ubl-psc meeting sheet must be
Resolved.                 implemented.


Resolved.                 No action to do.


Rejected.
"SubmissionDueDate" is
already present in
RequestForQuotation.      No action to do.

                          Done. A Request_ LineReference (0..1) has been
Approved.                 added to QuotationLine.


Approved.                 Resolved by the issue 29. No action to do.

Approved. Add VersionID   Done. Version has been added to Contract
to Contract.              (cardinality 0..1).
Approved. Add
Document_StatusCode to    Done. Document StatusCode has been added to
DocumentReference         DocumentReference (0..1).


Approved. Add
Document_Description      Done. Document_ Description has been added to
(0..n).                   DocumentReference (0..n).

Resolved by issue 59.     No action to do.
                          Done. Description has been added to Contract
Approved.                 (0..n).



For prd2.                 Postponed.

Approved. Add
CallForTender_Document
Reference (0..1) in      Done. CallForTender_DocumentReference (0..1) in
TenderingTerms.          TenderingTerms.
Approved. New
definition: "A party who
originally requested the Done. Definition has been updated.


Approved                  Done. Cardinality has been updated.

                          Done. In the SubscriberConsumption the
                          EnergyWaterSupplyID has been removed and
Approved.                 ConsumptionID has been added (cardinality 0..1).
The SpecificationTypeCode
indicates if the specifiction is
an: Onaccount,
YearlyStatement,
FinalSettlement, Statement,
MonthlyStatement,
QuarterlyStatement,
SixMonthStatement,
CurrentStatement,
RelocationSettlement,                                   Done. In the SubscriberConsumption the
ExtraordinaryStatement,                                 EnergyWaterSupplyCode has been removed and
Regulation, Cancellation,                               SpecificationTypeCode has been added (cardinality
Assorted.                        Approved.              0..1).


                                                        Done
                                                        1) A new class EnergyTaxReport to hold a report of
                                                        energy taxes. It should have: cbc:TaxEnergyAmount
                                                        (0..1), cbc:TaxEnergyOnAccountAmount (0..1),
                                                        cbc:TaxEnergyBalanceAmount (0..1),
                                                        cac:TaxScheme (1..1)
                                                        2) An ASBIE from EnergyWaterSupply to
                              Approved.                 EnergyTaxReport has been added (0..n).

                              Approved.
                              1) Change
                              EstimatedConsumptedQu
                              antity for                Done
                              EstimatedConsumedQua      1) In OnAccountPaymen
                              ntity.                    EstimatedConsumptedQuantity changed for
                              2) Change                 EstimatedConsumedQuantity.
                              TotalConsumptedQuantity   2) In ConsumptionReportReference
                              for                       TotalConsumptedQuantity changed for
                              TotalConsumedQuantity.    TotalConsumedQuantity.
                                                        Done. In the UnstructuredPrice the
                                                        PriceAmountQuantity.Quantity has been removed
                              Approved.                 and PriceAmount.Amount has been added (0..1)
                              The change name for
                              Time is approved. Not
                              sure about the choice of Done. In the UnstructuredPrice the
                              the type: it's a question for TimeAmountQuantity.Quantity has been removed
                              the ubl-psc.                  and TimeAmount.text has been added (0..1)
                                                            Done. Name has been updated and cardinality of
                                                            ASBIE from TelecommunicationsService to
                              Approved.                     RoamingPartner changes for 0..n

                              Approved.                 Done. Identifier has been added (0..1)
                                                        Done
                                                        1) The ABIE MeterProperty has been defined. Its
                                                        BBIEs are Name (0..1), NameCode (0..1), Value
                                                        (0..n), ValueQuantity (0..1), ValueQualifier (0..n).
                            Recommendation              2) The ASBIE from UtilityMeter to MeterProperty has
                            approved                    been added (0..n).


                                                        Done. MeterNumber (0..1) and Amount (0..1) have
                            Approved.                   been added to ConsumptionHistory.




                                                        Done. The ASBIE from UtilityStatement and
                                                        ExtendedTelecommunicationSupply has been
                            Approved.                   removed.
                            Rejected.
                            Information like "sole
                            propertorship" is part of
                            CompanyType. Examples
                            should be added for
                            clarifyng.

This italian requirement is
related to the reverse charge
case which is already
satisfied by the TaxCategory Rejected. Already
(see UN/ECE codelist)         satisfied.                No action to do.




                            Approved




                            Approved
waiting feedback from
Martin
Approved. Add
RequestedDeliveryDate to   Done. Requested_ DeliveryDate has been added
ProcurementProject.        (0..1) to ProcurementProject.
Approved. Add
Estimated_OverallContrac
t.Quantity to              Done. Estimated_OverallContrac has been added
ProcurementProject.        (0..1) to ProcurementProject.
                           Done. Requested_ Publication Date has been added
Approved.                  (0..1) to ContractNotice.



For prd2.                  Postponed.
                           Done. AdditionalDocumentReference has been
Approved                   added to TendererQualification (0..n).
                           Done. Description has been added to
Approved                   ExternalReference (0..n).

                           Done
                           1) MeterReadingMethod (0..1),
                           MeterReadingMethodCode (0..1) and
                           MeterReadingComments (..n) has been added to
                           MeterReding.
                           2) MeterReadingMethod, MeterReadingMethodCode
                           and MeterReadingComments has been removed
Approved                   from Meter

                           Done. Cardinality of ASBIE from
                           SubscriberConsumption to Consumption changed for
Approved                   (0..1)
The business case is that
there is a common
requirement to make
reference to the other
parties unqualified
reference. On printed
documents this is often
called "Your refernece" the
nature of the reference can
be pretty much anything
such as project number or
whatever. There are several
qualified reference elments
that are usefule but the need
is to hava an unqualified
one.

One possible mapping for
this is to use the
AccountingCost element,
based on the logic that the
purpost of the unqualified
reference is to enable
accounting key allocation.

I suggest that in order to
make this mapping more
clear, we change the
definition of the following
element in the following way.   Under discussion by mail. We have a feedback from
This is backward compatible     Peter that says: "in OIOUBL the
because it still point to the   reference is expressed as
use of the accounting code,     AccountingCustomerParty/Party/Contact/ID"

                                Done.

                                Done.



                                Done


                                Done
                                Done

                                Done
                                Done


                                Done
                                Done
                             Done


                             Done. Revised by issue 133.

                             Done
To be removed from PRD02
(will be replaced by ASBIE
to Environmental Profile
ABIE)                        Done

                             Done

                             Done



                             Done

                             Done




                             Done
                             Done
                             Done

                             Done

                             Done


                             Done

                             Done


                             Done

                             Done

                             Done


                             Done

                             Done. Revised by issue 135.

                             Done. Revised by issue 135.
                              Done

                              Done

These changes make tsc-
documents alligned with the
psc document template         Done

These changes make tsc-
documents alligned with the
psc document template         Done

These changes make tsc-
documents alligned with the
psc document template         Done




                              Done

                              Done

These changes make tsc-
documents alligned with the
psc document template         Done




                              Done

                              Done
Needed for backward
compatibility                 Done
Needed for backward
compatibility                 Done


Needed for backward
compatibility
Action                         Remark                              Action
                                                                    no




         Ken says:
         I've found thousands of elements related to
         <cac:ContractorCustomerParty> through both the
         document level and the line level ... but I have not
         found any explicit contract information whatsoever ...
         only information describing a *reference* to a
         contract. The party information is necessarily
         extensive because of the options offered to describe
         agents, legal entities, etc.

         But as for simplifying the contract information per se,
         I don't see where. Note that my analysis is only
         based on a search of the term "contract" in element
         names in the XPath files ... of course I may be
         overlooking the contract information you are
         referring to.

         So, can you cite for me which contract information
         you think should be removed from Catalogue when
         people are defining their own customizations of
         UBL? Of course this cannot be "removed" in the
         UBL 2.1 specification, but for a reader of this mail
         list archive, they should know that any optional item
         in UBL can of course be deprecated by a
         customization that dictates to its community of users
                                             ItemIdentification can already support any type of
                                             barcode. For example..<cac:Item>
                                             <cbc:Name>Blackboard</cbc:Name>
                                             <cac:SellersItemIdentification>
                                             <cbc:ID
                                             schemeID=”GTIN">5712345780121</cbc:ID>
Update definition and examples to indicate   </cac:SellersItemIdentification>
use for Barcodes.                            </cac:Item>




No action to do.
No action to do
Waiting for code list.




No action required.
Schema
reviewer
Sven




Tim
Peter




Oriol




Sven




Tim
Peter
Oriol




Sven




Tim




Peter




Oriol




Sven
Tim




Peter




Oriol


Sven




Tim
Peter




Oriol




Sven



Tim




Peter
Oriol


Sven


Tim


Peter




Oriol



Tim




Sven


Tim


Peter



Oriol
Sven




Tim




Peter


Oriol




Sven


Tim

Peter
Oriol



Sven




Tim
Peter



Oriol

Sven




Tim

Peter




Oriol



Sven
Roberto

Andy



Roberto


Andy
Roberto

Andy
Roberto


Andy
Roberto


Andy

Roberto



Andy

Roberto

Andy



Roberto

Andy




Roberto
Andy
Roberto

Andy




Roberto

Andy


Roberto

Andy

Roberto


Andy

Roberto

Andy
Roberto

Andy



Roberto



Andy




Roberto

Andy



Roberto




Andy

Roberto
Submitter               Email                       Date Submitted         Category

Leong Jern-Kuan         jernkuan@crimsonlogic.com                    01/06 Transport




UN/CEFACT TBG3          dvankemmel@wanadoo.fr                        02/06 Transport
(Chair Dominique
Vankemmel)



UN/CEFACT TBG3          dvankemmel@wanadoo.fr                        02/06 Transport
(Chair Dominique
Vankemmel)

UN/CEFACT TBG3          dvankemmel@wanadoo.fr                        02/06 Transport
(Chair Dominique
Vankemmel)
UN/CEFACT TBG3          dvankemmel@wanadoo.fr                        02/06 Transport
(Chair Dominique
Vankemmel)

Dave Fitzpatrick (EFM   fitzpatrick_david@bah.com                    03/06 Transport
project)



Dave Fitzpatrick (EFM   fitzpatrick_david@bah.com                    03/06 Transport
project)


Dave Fitzpatrick (EFM   fitzpatrick_david@bah.com                    03/06 Transport
project)




Dave Fitzpatrick (EFM   fitzpatrick_david@bah.com                    03/06 Transport
project)




Dave Fitzpatrick (EFM   fitzpatrick_david@bah.com                    03/06 Transport
project)
Dave Fitzpatrick (EFM   fitzpatrick_david@bah.com      03/06 Transport
project)                                                     and
                                                             Procurement


Stepehn Green           stephen.green@systml.co.uk     06/07




UBL Italia              roberto.cisternino@gmail.com   39356
Ian Jones     ian.c.jones@bt.com   11/07




Sweden SFTI   soren@ooidata.se     02/08


Sweden SFTI   soren@ooidata.se     02/08




Sweden SFTI   soren@ooidata.se     02/08

Sweden SFTI   soren@ooidata.se     02/08



Sweden SFTI   soren@ooidata.se     02/08

Sweden SFTI   soren@ooidata.se     02/08
Sweden SFTI    soren@ooidata.se             02/08


G.Ken Holman   gkholman@CraneSoftwrights.   04/08
               com




David Webber   david@drrw.info              05/08 ubl-dev
Daniel Toffeti   dtoffe@yahoo.com.ar   11/08 ubl-dev
Nick Hoggard   Nicholas.Hoggard@gen-        12/08 ubl-dev
               i.co.nz




G.Ken Holman   gkholman@CraneSoftwrights.   01/09
               com
Stephen Green   stephen.green@documentengi   01/09
                neeringservices.com
Martin Kempe    kempus@web.de   01/09 ubl-dev




G. Ken Holman                   01/09
Ian Jones             ian.c.jones@bt.com      11/07




Ole Ellerbæk Madsen   olem@itst.dk         4/16/2009


Ole Ellerbæk Madsen   olem@itst.dk         4/16/2009


Ole Ellerbæk Madsen   olem@itst.dk         4/16/2009

Ole Ellerbæk Madsen   olem@itst.dk         4/16/2009


Ole Ellerbæk Madsen   olem@itst.dk         4/16/2009




Ole Ellerbæk Madsen   olem@itst.dk         4/16/2009
Ole Ellerbæk Madsen   olem@itst.dk             4/16/2009



Ole Ellerbæk Madsen   olem@itst.dk             4/16/2009

Ole Ellerbæk Madsen   olem@itst.dk             4/16/2009


Ole Ellerbæk Madsen   olem@itst.dk             4/16/2009




Peter L. Borresen     plb@ebconnect.dk         4/16/2009




Peter L. Borresen     plb@ebconnect.dk         4/16/2009
Arianna Brutti        arianna.brutti@enea.it   4/17/2009



Arianna Brutti        arianna.brutti@enea.it   4/17/2009



Arianna Brutti        arianna.brutti@enea.it   4/17/2009




Arianna Brutti        arianna.brutti@enea.it   4/17/2009



Peter L. Borresen     plb@ebconnect.dk
Oriol




BII wg1   georg@eykur.is   Sep-09

BII wg1   georg@eykur.is   Sep-09


BII wg1   georg@eykur.is   Sep-09

BII wg1   georg@eykur.is   Sep-09




BII wg1   georg@eykur.is   Sep-09



BII wg1   georg@eykur.is   Sep-09
BII wg1   georg@eykur.is   Sep-09

BII wg1   georg@eykur.is   Sep-09

BII wg1   georg@eykur.is   Sep-09
BII wg1   georg@eykur.is   Sep-09




BII wg1   georg@eykur.is   Sep-09




BII wg1   georg@eykur.is   Sep-09

BII wg1   georg@eykur.is   Sep-09

BII wg1   georg@eykur.is   Sep-09



BII wg1   georg@eykur.is   Sep-09
BII wg1   georg@eykur.is   Sep-09




BII wg1   georg@eykur.is   Sep-09

BII wg1   georg@eykur.is   Sep-09

BII wg1   georg@eykur.is   Sep-09

BII wg1   georg@eykur.is   Sep-09

BII wg1   georg@eykur.is   Sep-09


BII wg1   georg@eykur.is   Sep-09


BII wg1   georg@eykur.is   Sep-09



BII wg1   georg@eykur.is   Sep-09


BII wg1   georg@eykur.is   Sep-09


BII wg1   georg@eykur.is   Sep-09


BII wg1   georg@eykur.is   Sep-09

BII wg1   georg@eykur.is   Sep-09


BII wg1   georg@eykur.is   Sep-09




BII wg1   georg@eykur.is   Sep-09
BII wg1   georg@eykur.is      Sep-09




BII wg1   georg@eykur.is      Sep-09

BII wg1   georg@eykur.is      Sep-09

BII wg1   georg@eykur.is      Sep-09




BII wg1   georg@eykur.is      Sep-09

JRF       joao.frade@pwc.be   Nov-09



JRF       joao.frade@pwc.be   Nov-09
JRF       joao.frade@pwc.be   Nov-09


ubl-psc                       Nov-09


ubl-psc                       Nov-09

CODICE    oriol@invinet.org   Nov-09

CODICE    oriol@invinet.org   Nov-09




CODICE    oriol@invinet.org   Nov-09




CODICE    oriol@invinet.org   Nov-09
CODICE   oriol@invinet.org   Nov-09




CODICE   oriol@invinet.org   Nov-09

CODICE   oriol@invinet.org   Nov-09

CODICE   oriol@invinet.org   Nov-09


CODICE   oriol@invinet.org   Nov-09

CODICE   oriol@invinet.org   Nov-09

CODICE   oriol@invinet.org   Nov-09


CODICE   oriol@invinet.org   Nov-09


CODICE   oriol@invinet.org   Nov-09

CODICE   oriol@invinet.org   Nov-09


CODICE   oriol@invinet.org   Nov-09




CODICE   oriol@invinet.org   Nov-09

CODICE   oriol@invinet.org   Nov-09

CODICE   oriol@invinet.org   Nov-09
CODICE   oriol@invinet.org   Nov-09

CODICE   oriol@invinet.org   Nov-09



CODICE   oriol@invinet.org   Nov-09


CODICE   oriol@invinet.org   Nov-09

CODICE   oriol@invinet.org   Nov-09


CODICE   oriol@invinet.org   Nov-09




CODICE   oriol@invinet.org   Nov-09




CODICE   oriol@invinet.org   Nov-09

CODICE   oriol@invinet.org   Nov-09

CODICE   oriol@invinet.org   Nov-09
CODICE    oriol@invinet.org   Nov-09


CODICE    oriol@invinet.org   Nov-09

CODICE    oriol@invinet.org   Nov-09

CODICE    oriol@invinet.org   Nov-09




INVINET   oriol@invinet.org   Nov-09
INVINET   oriol@invinet.org   Nov-09




CODICE    oriol@invinet.org   Nov-09




CODICE    oriol@invinet.org   Nov-09


CODICE    oriol@invinet.org   Nov-09
CODICE   oriol@invinet.org        Nov-09




CODICE   oriol@invinet.org        Nov-09

CODICE   oriol@invinet.org        Nov-09


eBiz     arianna.brutti@enea.it   Dec-09




eBIZ     arianna.brutti@enea.it   Dec-09


eBIZ     arianna.brutti@enea.it   Dec-09


eBIZ     arianna.brutti@enea.it   Dec-09




CODICE   oriol@invinet.org        Jan-10

CODICE   oriol@invinet.org        Jan-10



CODICE   oriol@invinet.org        Jan-10


CODICE   oriol@invinet.org        Jan-10


CODICE   oriol@invinet.org        Jan-10
CODICE    oriol@invinet.org   Jan-10

CODICE    oriol@invinet.org   Jan-10


CODICE    oriol@invinet.org   Jan-10


CODICE    oriol@invinet.org   Jan-10




CODICE    oriol@invinet.org   Jan-10




CODICE    oriol@invinet.org   Jan-10

CODICE    oriol@invinet.org   Jan-10


ubl-psc                       Feb-10

ubl-psc                       Feb-10
ubl-psc                       Feb-10

ubl-psc                       Feb-10

ubl-psc                       Feb-10


ubl-psc                       Feb-10

ubl-psc                       Feb-10

ubl-psc                       Feb-10


ubl-psc                       Feb-10
ubl-psc                                   Feb-10



ubl-psc                                   Feb-10

ubl-psc                                   Feb-10

ubl-psc                                   Feb-10

ubl-psc                                   Feb-10

ubl-psc                                   Feb-10


ubl-psc                                   Feb-10


CODICE                                    Feb-10

ubl-psc                                   Feb-10

ubl-tsc                                   Feb-10

ubl-tsc                                   Feb-10


ubl-tsc                                   Feb-10


CODICE               oriol@invinet.org    Mar-10



CODICE               oriol@invinet.org    Mar-10

CODICE               oriol@invinet.org    Mar-10

CODICE               oriol@invinet.org    Mar-10

CODICE               oriol@invinet.org    Mar-10

Roberto Cisternino   roberto@javest.com   Mar-10



Roberto Cisternino   roberto@javest.com   Mar-10


Roberto Cisternino   roberto@javest.com   Mar-10
Roberto Cisternino   roberto@javest.com   Mar-10



Roberto Cisternino   roberto@javest.com   Mar-10




Roberto Cisternino   roberto@javest.com   Mar-10




Roberto Cisternino   roberto@javest.com   Mar-10



Roberto Cisternino   roberto@javest.com   Mar-10


Roberto Cisternino   roberto@javest.com   Mar-10




Roberto Cisternino   roberto@javest.com   Mar-10
Roberto Cisternino   roberto@javest.com   Mar-10




Roberto Cisternino   roberto@javest.com   Mar-10




Roberto Cisternino   roberto@javest.com   Mar-10




Roberto Cisternino   roberto@javest.com   Mar-10
Roberto Cisternino   roberto@javest.com   Mar-10


Roberto Cisternino   roberto@javest.com   Mar-10




Roberto Cisternino   roberto@javest.com   Mar-10




Roberto Cisternino   roberto@javest.com   Mar-10




Roberto Cisternino   roberto@javest.com   Mar-10




Roberto Cisternino   roberto@javest.com   Mar-10
Peter L. Borresen    plb@ebconnect.dk


                                          Mar-10
Peter L. Borresen    plb@ebconnect.dk

                                          Mar-10
JRF                  joao.frade@pwc.be




                                          Mar-10
JRF                  joao.frade@pwc.be


                                                       Mar-10
JRF                  joao.frade@pwc.be




                                                       Mar-10
Arianna Brutti       arianna.brutti@enea.it




                                                       Mar-10

ubl-psc                                                Mar-10
ubl-psc                                                Mar-10
ubl-psc                                                Mar-10
ubl-psc                                                Mar-10
ubl-psc                                                Mar-10

ubl-psc                                                Mar-10




Roberto Cisternino   roberto@javest.com                Apr-10




Roberto Cisternino   roberto@javest.com                Apr-10




Roberto Cisternino   roberto@javest.com                Apr-10
JRF                  joao.frade@pwc.be        may-10
JRF                  joao.frade@pwc.be


                                              may-10
JRF   joao.frade@pwc.be




                          may-10
JRF   joao.frade@pwc.be




                          may-10
JRF   joao.frade@pwc.be


                          may-10
Issue Type                                            Issue

Bug               Critical : Transport Library. Certificate of Origin Document type. 1.
                  ExporterParty and ImporterParty are at the wrong ABIE namly Certificate of
                  Origin. 2. EndorserParty is already at Certificate of Origin Application ASBIE



General           Limited scope regarding transportation: covering only sea/river transport,
                  focused on the relations between the shipper/exporter/consignor and the
                  freight forwarding agent and not including the parties involved in the actual
                  movement of the consignments of the goods.


General           Business process: has to be revised and completed according to the
                  existing business practices.



General           Semantic definitions of documents description ( documents types chapter
                  5.10) need to be aligned with the existing EDIFACT standards code list in
                  UNCL (ref: data element 1001 document/message name)
General           Although TBG3 appreciates the UBL development for ocean transport, the
                  UBL deliverables should be further extended to multimodal transport with
                  the collaboration of TBG3 business experts.

New Requirement   Desire to define size constraints on XML elements.




General           It is unclear how UBL 2.0 transport messages can be defined to express the
                  constraints described in the UNTDED. While this may be characterized as a
                  customization; this is an important consideration to achieve semantic
                  interoperability.
Bug               The relationship of Consignment and Shipment is on-to-many. However, it
                  should be many-to-many. Just as a consignment can be shipped in many
                  shipments, many consignments can be consolidated into one shipment.



Bug               Business processes to be revised and completed according to the existing
                  business practices. For example: the freight forwarding instructions between
                  the shipper and the freight forwarder has to be complemented by the
                  shipping instructions to the actual carrier - the certificate of origin process
                  has no direct relationship with the bill of lading
New Requirement   UBL 2.0 transport messages are standalone xml schemas with each based
                  upon the same data dictionaries. These transport messages need to be
                  related to each other via some kind of context or process. There should be
                  a higher level \"dialogue\" that presents how these messages may be used
                  together in a more global business transaction.
MissingField      Believe there is no way to record discrepancies for quantities received.
                  There is a need for a discrepancy identifier, date, and notes, and each
                  discrepancy should be linked to a PO or line item, and have the name of the
                  person verifying the dicrepancy and its status. The discrepancy should be
                  more generic than just rejected, which is available in UBL.
                  As pointed out to me by Luca Reginato in Italy, we have an
New Requirement   inconsistency between the document types in that in most
                  of them PaymentMeans has minimum occurance 0 and maximum
                  occurance unbounded, which is great as PaymentDueDate can
                  be automated even when there are multiple payment due dates
                  by using multiple PaymentMeans occurances. So far so good.
                  However it is quite a general requirement to use the
                  OrderResponse document as a key document (usually calling it
                  'order confirmation' or 'order acknowledgement') as with
                  what is called 'punch out' and similar common practises.
                  In such cases the OrderResponse is the primary document from
                  the seller (or seller's agent) and so it there is a strong
                  requirement to include here the payment information such
                  as a Payment Due Date or set of Payment Due Dates. The
                  inconsistency is that in UBL 2.0, although the need for such
                  payment requirement information is acknowledge by the
                  inclusion of PaymentMeans, it is only, in the OrderResponse
                  with the allowance of zero or one occurances (hence only a
                  single payment due date at most).

                  I do accept that fixing this would be quite a challenge as
                  it may involve a backwards compatibility issue. Maybe there
                  is a way to fix it by creating a new ASBIE and ABIE which
                  has multiple occurances and appending it to the Order Response.
                  Otherwise it would seem implementers making primary use of
                  the OrderResponse in this way have to 1. create their own
                  extension which reduces the opportunities for interoperability
                  or 2. use a document such as Invoice in situations where this
                  is otherwise deemed as unnecessary (and therefore more expense
                  is imposed which doesn't necessarily bring a proportional
                  return on investment perhaps) or 3. do without the automation
                  of the payment due dates and just use a note or description.
                  I think 3. is unsatisfactory as it should be a major benefit
New Requirement   Regarding the use of Payment Terms for staged payment terms e.g.
                  o Payment Terms 1 pay €100 in 30 days
                  o Payment Terms 2 pay €200 in the next 30 days
                  o Payment Terms 3 pay x% of the remainder in the next 30 days
                  o Payment Terms 4 pay remainder in the next 30 days
New Requirement   I am still struggling to understand how we could build a UBL Order message
                  with sub components. From Tim McGrath's e-mail I believe we may need to
                  handle all of his scenarios as we deal with a very large product set that may
                  be assembled in a number of ways. Some components will be sold as both
                  an individual order line item and as a sub-line both priced and un-priced.
                  This is our challenge - we have many business operating units that can mix
                  and match components in different ways and they want to become even
                  more flexible so a simple "this is the only way" solution is not possible.
                  Following from Tim's suggestion I have looked at the catalogue message
                  and I can see how that gives a Bill of Materials structure but that does not
                  solve my problem as the users may not wish to create individual catalogue
                  entries for each of the possible combinations. My users requirement is for
                  the BOM to be in the order/invoice as that is the model they understand and
                  are comfortable with and do not wish to invest in catalogue messages at this
                  time.

                       I know very little about UBL and I am acting as an intermediary so I
                  may have missed Tim's point - what we really need is simple examples of
                  how we would build UBL messages that support as a minimum Tim's
                  scenarios. I have a fear that we will actually need an open end BOM
                  structure as in the past I worked on an EDI Invoice that had a 6 layer line
                  item structure to accurately reflect the data needed and could contain over
                  100,000 item lines in 1 invoice.




New Requirement   ”... amounts must be positive”: In situations where sellers bundle offers like
                  "buy 3 pieces of item X, and you'll get 1 item Y free of charge", we wish all
                  items to be explicitly listed on order line
New Requirement   Order currency does not always give the full picture. If ordering in a foreign
                  currency, the relation to the buyer's domestic currency and, more precisely,
                  the exchange rate to apply may additionally be stated.




New Requirement   Order/Delivery/Requested Delivery_Period: Period start/end dates are not
                  sufficient, also start/end time is needed
New Requirement   An invoice addressee (invoice to) is missing



New Requirement   Order/OrderLine/Line Item/Delivery: Delivery address is sometimes required
                  on line level (seems to be commonly used in construction)
New Requirement   Order/OrderLine/Line Item/Delivery/Requested Delivery_Period: Period
                  start/end dates are not sufficient, also start/end time is needed
New Requirement   Order/OrderLine/Line Item/Delivery/Requested Delivery_Period: one
                  occurrence of period start/end dates/times is not sufficient if Partial Delivery
                  Indicator=true
New Requirement




                  Note that in deployment I would constrain the item property names to a controlled vocabulary s
New Requirement   In looking at the Catalogue XSD - when you generate a complete XML
                  instance per the XSD schema - you get a 2.1MB transaction!!!

                  Clearly - noone is sending 2.1MB to describe one catalogue item (least I
                  hope not!).

                  So - when I look at the content - most all of it relates to static CONTRACT
                  related information - that really could be placed into a separate and new
                  UBL transaction - and then simply referenced by an ID.

                  This would introduce a new process flow into the information equation - but
                  seems entirely logical. So if I need to know the contract conditions relating
                  to an item - I can request that.

                  The design decision to burden the catalogue exchange with Contract related
                  content (which makes up 90%) - seems counter intuitive - when that could
                  be sent separately on request once - instead of everytime the catalogue
                  entry is updated.

                  Not only that - but I strongly suspect the Contract information is repetitive -
                  so one contract could cover most all the items in the catalogue - again -
                  dramatically reducing information exchange volume.

                  The contract information can then also be aligned to local tax regulations
                  more closely - such as EU VAT - and serve better fit to purpose roles.
New Requirement     I had a problem trying to generate JAXB Bindings for OASIS UBLv2
                  (http://www.oasis-open.org/specs/#ublv2.0) in the Netbeans IDE (version
                  6.5 rc2). The problem is with some quoted strings, in some strings the
                  quoting is done with opening and closing double quotes with an
                  hexadecimal encoding of E2 80 9C and E2 80 9D, while in the rest of the
                  UBL documents hexa 22 is used for a straight double quote.
                      The three byte quotes seems to be valid UTF-8 since they are displayed
                  with the proper glyph in other text editors, and people from the ubl-dev list
                  confirmed this. But I'm getting an error "unmappable character for encoding
                  UTF-8" and the offending strings are displayed as: ?VISA?, ?MasterCard?,
                  etc. in the error output window in Netbeans.
                     The problem seems to appear only within CommonAggregateComponents-
                  2,
                  in CardAccountType and CountryType. After suggestion from a ubl-dev list
                  member, I tried with the runtime xsdrt in (http://docs.oasis-open.org/ubl/os-
                  UBL-2.0/xsdrt/) and the problem dissappeared.
                    I had a problem trying to generate JAXB Bindings for OASIS UBLv2
                  (http://www.oasis-open.org/specs/#ublv2.0) in the Netbeans IDE (version
                  6.5 rc2). The problem is with some quoted strings, in some strings the
                  quoting is done with opening and closing double quotes with an
                  hexadecimal encoding of E2 80 9C and E2 80 9D, while in the rest of the
                  UBL documents hexa 22 is used for a straight double quote.
                      The three byte quotes seems to be valid UTF-8 since they are displayed
New Requirement

                  I'm currently using the UBL 2.0 specification as part of an integration project.
                  So far we have avoided the need to customise the specifications in any way,
                  however I'm struggling with finding the correct location to populate the Head
                  Office Party details for the Seller Customer Party or Accounting Supplier
                  Party elements of the Invoice schema.



                  The scenario we working through is that the Seller Customer Party is a
                  branch of a larger organisation. It is important to us to know the
                  organisation that the branch is affiliated with, however it is not immediately
                  obvious how to achieve this using the standard UBL specs.



                  Does anybody have any suggestions on how this could be approached?




New Requirement
                  But I'm still thinking for UBL 2.1 we should consider not having qualified data
                  types in order to formally decouple code list conformance from the schema
                  conformance.
New Requirement   Prior to UBL TC discussion of this, I thought I'd better add my own two cents
                  worth: I realise the ordering process doesn't attempt or claim to show all the
                  aspects of real-life use of the UBL ordering documents (e.g. no attempt to
                  show that an order can be cancelled prior to order response). I agree my
                  diagram version does seem to remove some possibilities but does this
                  matter
                  if it is a clarification? Maybe the things it removes can be added back in
                  without obscuring anything. At the same time it should be considered
                  1. include a cancellation before the order response
                  2. there is a cycle (pointed out as we tried to use this diagram in TAG TC)
                  which might need consideration - going from order 'modified' to order
                  change and back to possible modification and so on - is this realistic?
                  The aim with my modified diagram is only to improve the clarity (with paths
                  through the process not sharing so many steps - different paths having their
                  own steps , even if those steps have the same names). I didn't attend to
                  create
                  a profile as such. Nothing should be missing that is in the original,
                  just clearer
                  paths. Maybe add order cancellation prior to response and qualify the
                  loop(s).
New Requirement   I am working on extending UBL for my purposes. I want to describe a
                  transport consisting of two phases within one document (forwarding
                  instructions). Therefore I used "cac:ShipmentStage" within the shipment
                  declarations. But I found that you can only store the actual time spend at the
                  individual track. Is that right? I want to define "estimatedDeliveryTime" and
                  "requestedDeliveryTime" for every part of an ongoing transport. Right now, I
                  am only able to make such specific time declarations in the global definition
                  of the transport within the "cac:delivery" element.




                  Transport Mode Code has a listID of UN/ECE Rec 16 and it should be rec
                  19
                         I am still struggling to understand how we could build a UBL Order message
                         with sub components. From Tim McGrath's e-mail I believe we may need to
                         handle all of his scenarios as we deal with a very large product set that may
                         be assembled in a number of ways. Some components will be sold as both
                         an individual order line item and as a sub-line both priced and un-priced.
                         This is our challenge - we have many business operating units that can mix
                         and match components in different ways and they want to become even
                         more flexible so a simple "this is the only way" solution is not possible.
                         Following from Tim's suggestion I have looked at the catalogue message
                         and I can see how that gives a Bill of Materials structure but that does not
                         solve my problem as the users may not wish to create individual catalogue
                         entries for each of the possible combinations. My users requirement is for
                         the BOM to be in the order/invoice as that is the model they understand and
                         are comfortable with and do not wish to invest in catalogue messages at this
                         time.

                              I know very little about UBL and I am acting as an intermediary so I
                         may have missed Tim's point - what we really need is simple examples of
                         how we would build UBL messages that support as a minimum Tim's
                         scenarios. I have a fear that we will actually need an open end BOM
                         structure as in the past I worked on an EDI Invoice that had a 6 layer line
                         item structure to accurately reflect the data needed and could contain over
                         100,000 item lines in 1 invoice.
MissingField

                         BuyerCustomerParty is missing in CreditNote
Explanation is missing

                         What is Response.ReferenceID used for
                         RequestForQuotation is missing a DueDate
MissingField
New Requirement

                         Severity/Privacy classifiaction is missing on line level as well as header level
New Requirement



                         Secret/confidential classification is missing on live level as well as header level
New requirement
                         Ouatation.quotationLine.AlternateLineItem is missing
New Requirement


                  Ouatation.quotationLine.OptilnalIndication is missing
missingField
                  CreditNote.CreditNoteLine.AllowanceCharge is missing
missingField

                  Reminder.ReminderLine.AllowanceCharge is missing
New Requirement



                  PaymentTerms is missing a Factoring Indicator
New Requirement




                  PaymentTerms is missing a Factoring Message
missingField      Cardinality of signatura should be 0..* in stead of 1..0
New Requirement   I suggest to add the element cbc:DocumentType in the Order document
                  header and in the element cac:OrderReference.


New Requirement


                  I suggest to add the element cac:DocumentReference in the Catalogue document header.
New Requirement   Cardinality of OrderLine.Note and LineItem.Note 0..* instead of 0 ..1




New Requirement   I suggest to add an attribute "name" to the element cbc:Keyword



MissingField



                  Exchange rate is missing on linelevel in a invoice.
HashAlgorithmMethod missing
in Document reference




MissingField
                              The invoice line in UBL does not provide for specification of invoicing period that applies to the
New Requirement

                              In Invoice, support for specifying payment terms for tax. A particular tax may have to be paid im
New Requirement
                              In Invoice, provide for shipment information including number of parcels, gross weight and cube
New Requirement



                              To facilitate split payment in invoices there needs to be a clear link between each payment and
MissingField

                              In Order, need possibility to provide catalogue reference at header level.
New Requirement               Order should provide for stating payment terms at least basic information such as textual note.
MissingField
                              The Catalogue related data models do not show the required element for Catalogue transaction
MissingField
                              The item instance class does not specifically provide for Best before dates (need in the Catalog
New Requirement
                              There is no certification info on the item. Some item may be certified by different certifications b
New Requirement

                  Hierarchical packing structure, upwards and downwards, and their
                  measurements and markings. The catalogue line level is the sales unit to
                  which the price referrers.
                  1- Sales units contain items but there may be different quantity of items in a
                  sales unit. E.g. paint that is sold in 1L, 5L, 10L and 100L units. It is always
                  the same paint but prices pr. Litre vary greatly with packaging sizes.
                  2- The item is usually packed into different box levels and any one of those
                  may be the sales unit.
                  3- Different parts of the logistics chain use different packaging levels and
                  need to identify them.
                  4- The item pack can also be broken up. E.g. toothbrushes are usually
                  stocked and moved in boxes or at minimum in cartons but small vendors
                  may actually get deliveries pr. piece and end point sales is pr. piece.
                  5- Packing Levels (attempt to structure but not complete. A class may not
                  use it self as a direct subclass)
                     • Item packaging (packaging)
                            o Packaging description (common class)
                               a- Measurements
                               b- Type
                               c- Markings
                               d- Content
                            o Upper level packaging (Common class)
                               a- Packaging description (common class)
                               b- Upper level packaging (common class)
                            o Lower level packaging (common class)
                               a- Packaging description (common class)
                               b- Lower level packaging (common class)

New Requirement   There is no support for bar code identifications. Bar codes are usually based
                  on existing numbers such as a particular standard ID number (GTIN) but the
                  encoding can be based on different standards such as EAN13, EAN128
                  various US code schemas and more frequently 2D codes. There is different
                  bar coding for different packaging levels. (need in the Catalogue)

New Requirement
                  In Catalogue, the actual version ID does not seem to have relevance to the action, that is, it do
New Requirement
                  In Catalogue, need possibility to provide certification and environmental info.
New Requirement


                  DELETED.
MissingField

                  Catalogue delete request requires effective date.
New Requirement      In Catalogue Request, specification of item information requests differ from
                     the other docs in the way that in requests the need is often to provide
                     ranges i.e. a laptop should:
                       o Have a hard drive with minimum 300 Gb
                       o Screen size between 15 and 17 inches.

New Requirement
                     In Catalogue Request, there may also be a need to specify the importance of an attribute such
New Requirement
                     In Catalogue Request, possibility of ranges also must apply to classification codes such as UN/
New Requirement
                     In Catalogue Request, the additional attribute class needs to allow for sequencing of both attrib
New Requirement
                     The Application Response document does not support appeal information.
New Requirement

                     The Application Response document does not provide for specifying the sender and the receiv
Change cardinality

                     In the Application Response the Response reference identifier should not be mandatory. In the
MissingField         The Application Response document does not provide an effective date,
                     e.g. when the document is used for accepts the effective date of the
                     acceptance may be later than the issue date. For example a new catalogue
                     may be accepted but effective from end of month.
MissingField         In Quote document, support for quote request reference on quote line.


MissingField

                     The Quote Request document does not support specification of a due date for the quote.
MissingField

                     The Quote Request does not support requested validity period for the quote.
MissingField         The Quote Request does not support buyer info. Assumes originator is the
                     same as buyer.
Change cardinality   In the Statement document, the payment means class is 0..1, but in invoice
                     it is 0..n. The logic for allowing multiple payments means classes applies
                     equally to the statement as to the invoice.
New Requirement      In the Pary class, there is a need to be able to provide information about
                     parties such as their type (e.g. Government, military, private, Law etc.),
                     their activities (e.g. manufacturing, health etc.) as well as company dossier
                     type of information (e.g. number of employees, turnover, form of
                     incorporation etc.). This could be a new common class that could be
                     included in the party classes on an appropriate level.
New Requirement      In the Party class, it is not possible to give general party information such as
                     company telephone, company email, fax etc.. Currently it is only possible to
                     give such information for contacts and persons within the party contact or
                     person.
New Requirement




                     In the Party class, it is inconvenient not being able to give a contacts title of
                     function class. Using the person class creates confusion because then both
                     classes contain the name so what name is what?
MissingField
                     The Attachment class should provide for electronic signature.
General              UBL does not provide for information about compression algorithm for
                     attached files.
General



                     The structure of quantities, units and packaging in relation to price needs
                     further clarification.
New Requirement      UBL document should provide for using VAT inclusive price and amounts.

General              The InvoiceLine and CreditNoteLine should be identical to allow the
                     cancelling of the Invoice. Currently, this is not the case, e.g.
                     AllowanceCharges are present in the InvoiceLine but not in the
                     CreditNoteLine.
General              It is not possible to provide structured Invoice Dispute Information
General              No toolbox messages are present e.g. Status Request/ Response


MissingField         DocumentResponse needs DocumentStatusCode.


Change cardinality   Evaluate if the cardinality of DocumentReference in DocumentResponse
                     should be 1..n.
MissingField         Maintain RoleCode in Contracting Party Type as the contracting party can
                     act on behalf of another party.
MissingField         It was decided to remove LegalForm in class TendererQualification because
                     there is a legal form inside the Party Legal Entity Class. The problem is that
                     in Tenderer Qualification there is no Party class associated, so this element
                     Legal Form stating the form that can be taken by the tenderer is required as
                     it was.
MissingField         In Brussels it was decided to remove VariantsConstraintIndicator from
                     Tendering Terms and add a MaximumVariant Quantity, nevertheless you
                     need to maintain the VariantConstraintIndicator in order to indicate that
                     variants are allowed but you do not constraint the number of variants.

Change name          Change GovernmentProcurementContraintIndicator to
                     GovernmentProcurementAgreementConstraintIndicator
New class         It was decided in Brussels to remove the class QualificationResolution and
                  add all the BBIES of that class into the Qualification Response Document.
                  The problem is that this class should be 0..n in order to admit or reject a
                  tenderer to a given lot.
                  Change Admission Indicator to AdmissionCode
                  Add identifier for a lot 0..1 in the class
                  Add Exclusion reason 0..n




New Requirement   Add a FundingProgramCode in Tendering Terms in order to specify if the
                  contract has fundings from the EC, national level, …
New Requirement   Add PenaltyClauses textual field in Tendering Terms to specify penalty
                  clauses.
Change name       Change name Fee Amount for Required_Fee Amount in Tendering Terms


New Requirement   Add AcceptedVariantsDescription textual BBIE in Tendering Terms to
                  specify the things for which variants are accepted.
New Requirement   Add Contractual DocumentReference class in Tendering Terms to specify
                  which documents are going to be part of the final contract.
New Requirement   Add a ContractAcceptance Period class in Tendering Terms in order to
                  specify the period of time the Contracting Authority has to accept the
                  contract.
New Requirement   Add Participation Request Reception Period in TenderingProcess


New Requirement   Add FeeDescription and FeeAmount in TenderedProject Class to being able
                  to specify fees per tendered project.
New Requirement   Add Technical Committee Person 0..n in Awarding Terms to be able to
                  describe the name and role for the people that conform the technical expert
                  committee.
New Requirement   Add ProjectJointVentureQualifyingParty 0..n in Tenderer Party Qualification
                  to specify the different companies that bid together as a consortia and
                  rename the OtherQualifyingParty to SubcontractorQualifyingParty.


New Requirement   Add WinningJointVentureQualifyingParty 0..n in Tender Result to specify the
                  parts participating in a consortia in the awarding document.
New Requirement   Add ProjectJointVentureParty 0..n in Tender Document to describe the
                  participants in a consortia.
New Requirement   Add MinutesDocumentReference 0..1 in Tenderer Qualification Response to
                  be able to add the minutes in the qualification response.
New Requirement   Add Note in Tenderer Qualification Response 0..n at header level

New Requirement   Move Original ID from FrameworkAgreement to Tendering Process
                  OriginalContractingSystemID, it is the ID of the original contract when in a
                  Framework agreement or DPS.

New Requirement   Removed Subject and renamed Content with Note in the following
                  documents: Tenderer QualificationReponse, TenderReceipt, Unawarded
                  Notice, and Awarded Notice
Remove element    Remove ReopeningIndicator from FrameworkAgreement.

New Requirement   Change DurationMeasure for DurationPeriod in FrameworkAgreement class


New Requirement   Added Class ImmobilizedSecurity for Guarantee document.Information
                  about an immobilized security to be used as a guarantee.




New Requirement   Added Class Regulation for Guarantee processes, to enable description of
                  the applicable regulation.




                  Remove Global Indicator from the Guarante Certificate main document.

                  Rename Contract Name Text in Guarantee Certificat to Purpose.

                  Add ApplicableRegulation ASBIE in Guarantee Certificate document
                  pointing to Regulation Class.
                     Rename Document Reference in Guarantee Certifciate to Guarantee
                     Document Reference

                     Add Immobilized Security Class in Guarantee Certificate

New Document Model   Add Document Model Guarantee identical to Guarantee Certifciate except it
                     has no GuaranteeDocumentReference.
New Document Model   Add Document model Guarantee Certificat Request to enable request of
                     guarantee certificate.




                     Remove ASBIE Signature from the Document Reference and Attachment
                     classes. It has no sense to get the signature information of the referred
                     document modeled into the "container" class.
New Requirement   When a third party is creating a document such as a qualification document
                  and validates the signatures of the attached document, a placeholder for the
                  result of the verification is required.




New Requirement   In the signature process of an XML UBL document, the signature ABIE can
                  be used to identify where the Signature XAdES or XML Dsig is placed. This
                  means that most of the elements of the actual Signature class are useless.
                  For instance, the CanonicalizationMethod should not be used if a complete
                  XML DSig is going to be used. The requirement here is to make the
                  Signatory Party optional. If using a XAdES signature, the certificate comes
                  often with the own signature so it is not necessary to inform that in the
                  Signatory Party, avoiding confusions of whether who is the signor of the
                  document,
New Requirement   Add ASBIE ParticipationRequestReceptionPeriod in Class Tendering
                  Process to enable the definition of the period for participation request
                  reception.
New Requirement   If an auction has to be run at the end of the process, each Awarding Criteria
                  has to define its minimum improvement bid textually.
New Requirement          When defining an auction in a call for tenders, the user has to describe
                         different things textually such as

                         - Textual description of the information available for tenderers during the
                         auction
                         - Textual description of the auction process
                         - Textual description of the conditions under which the tenderers will be able
                         to bid
                         - Electronic device and connection technical specifications used for the
                         auction
                         - URI for the used electronic device.
New Document Model       Create New Document Model Tender Envelope to wrap Tender documents.

Change name              In Tendering Terms Change the name of Awarding Criteria Type Code to
                         Awarding Criteria Method Code as the Awarding Criteria Type Code is the
                         Code for the Awarding criteria type in the class Awarding Criteria
Review Document Model    Invetory Report is a new document model proposed by eBIZ-TCF. It is a
                         report about the quantities on stock and it was created to make the retailer
                         able to send this information to the producer. Now, eBIZ-TCF has a further
                         needed: to make the producer able to send information about the availability
                         of goods. I think that the InventoryReport can be used both case. Only few
                         changes should be made; see issue 131-132-133.

Change field             In InvetoryReport there are InvetoryDate and InventoryTime. Remove these
                         field and add InvetoryPeriod.

Add field                In InvetoryReportLine add ActualDate or AvailabilityDate. It is the date from
                         which the goods will be available. It must be used only if the goods are not
                         in the magazine when the document is issued.
Add field                In InvetoryReportLine add AvailabilityIndicator. It is an indicator that
                         classifies the availability level of the good (for example: green, article in
                         available; yellow, incoming available; red, lost).
                         Adding two new qualified party ASBIE in the class Tendering Terms in order
                         to be able to point to the Contract Responsible Party (0..1 Party responsible
                         for the execution of the contract) and the TenderEvaluation Party (0..n Party
                         responsible for the evaluation of the received tenders in the contracting
Add fields               authority.

Add field                Add a Description BBIE in Appeal Terms ABIE
                         Add an Open Tender ID (0..1) and a ProcurementProject Lot ID (0..n)
                         BBIES in the Tender Preparation class in order to enable the relationship
                         between a Tender Preparation and the Open event (the first field) and the
Add field                identification of the lot or lots this tender can be used for.

                         Add a Template Document Reference class in Tender Requirement (0..1) in
Add field                order to enable the provision of templates to fulfill such a requirement.

Same name for ABIE and   There is an issue because there is an ABIE and a main document with the
document                 same name: Tenderer Qualificaction
                  The Process Justification ABIE should be modified. Currently it has a list of
                  different indicators defining the reason why the contracting authority has
                  followed a particular tendering procedure for the awarding of a contract. The
                  issue is that this list of reasons has changed in the new Directive, so it is
                  better just getting rid of the indicators and creating a 0..1 Reason, Code to
Modify ABIE       enable the binding to an external code list defining the list of codes.
                  Remove BBIE Completed Task Code in Completed Task as there is not a
Remove element    coded list of completed tasks.
                  Change name of TypeCode BBIE in Tenderer Requirement. Use
                  Requirement_ Type Code instead to better describe the Type Code for this
Change name       BBIE.
                  Remove Language Code BBIE in Evidence class because cac:Language
                  should be in Document Reference class, which is an association inside
Remove element    Evidence Class.
                  In TenderPreparation, change the name of the TenderID &
                  TenderTypeCode BBIEs, using TenderEnvelopeID &
                  TenderEnvelopeTypeCode instead due to the fact that what we are defining
                  in this class are the envelopes (or sets of documents) to be provided by the
Change name       tenderer.

                  New class Contract Execution Requirement. Instead of Contract Execution_
                  Tender Requirement ASBIE in Tendering Terms, create an ASBIE 0..n with
                  this new class. The reason is that the Tender Requirement class do not fit
                  into the elements that need to be defined when explaining the contract
                  execution requirement, mostly when mapping this to the OJEU, where
                  specific execution terms such as Execution Reserved to Protected
                  Workshop or things like this have to be defined. Elements in this new class
New class         are Name, ExecutionRequirement Code and Description.
                  Add BBIE RequiredCurriculaIndicator in Tendering Terms (0..1) as required
New property      by OJEU.

                  Remove BBIE EffectiveDate and EffectiveTime from ApplicationResponse
Remove element    and add them to Response ABIE.

Remove element    Remove StatusCode from DocumentResponse ABIE.
Change name       In all documents, change ContractFileID for ContractFolderID.

Remove element    In Catalogue, remove BBIE TransactionID.

Add association   In Catalogue, add ASBIE SourceCatalogueReference.

                  In DebitNote, add BuyerCustomerParty and SellerSupplierParty, in order to
Add element       allign it with other billing documents.
                  In OrderChange, add ASBIE to PaymentTerms in order to allign it to other
Add element       order documents.
                  In OrderResponse, add ASBIE to PaymentTerms in order to allign it to other
Add element       order documents.

                  Add PaymentPurposeCode BBIE in InvoiceLine, CreditNoteLine,
Add element       DebitNoteLine.
                           Remove PaymentPurposeCode BBIE in Reminder, RemittanceAdvice,
Remove element             Statment.


                           Remove HighestSecurityClassificationCode and HighestPrivacyCode from
Remove element             RFQ

Change element             In RFQ, change QuotationDueDate for SubmissionDueDate.

Remove element             Remove PaymentPurposeCode from Statment.
                           Change StatusRequest for DocumentStatusRequest and change
Change document name       StatusResponse for DocumentStatus.

Change elements sequence   Allign TenderResponse to psc document template.

                           In OnAccountPayment, remove Period and PlannedSettlement and add
Remove and add element     PaymentTerms.


New ABIE                   Define a new ABIE called Renewal and add it to Contract Extension.

Change element name        In all documents, change CollaborationID for ProfileExecutionID.

Add association            Add a 0..1 association from Location to Location Coordinate.

Add association            Add a 0..1 association from SubsidiaryLocation to Location Coordinate.

                           Include Reference Date, Reference Time and Reliability Percent in
Add BBIEs to ABIE          Transport Status
                           In the TenderingTerms ABIE the AppealTerms ASBIE is missing. We
                           should add this ASBIE there after the ContractAcceptancePeriod and before
Add association            the Language with 0..1 cardinality.
                           In TendererQualificationRequest a BBIE called LegalForm as the first
                           property is missing. This BBIE is used to inform the Official Journals about
                           the legal form requested for potential the tenderers and should be 0..n as it
Add BBIEs to ABIE          is textual
                           Element TypeCode in ProcurementProject should be optional. 0..1 instead
Change cardinality         of mandatory
                           UBL maindoc TenderReceipt has two Note elements in the root. the last one
Remove element             should be removed
                           UBL maindoc TenderReceipt requires a ASBIE Tender_
Add association            DocumentReference (0..n) to enable pointing to the received tenders.
                           In TransportExecutionPlan, "CommisionMonetaryTotal" should be
Typing error               "CommissionMonetaryTotal".
                           In UBL-TransportExecutionPlan all flags (indicators) seems to be wrong in
                           the naming (also very long). Maybe I am wrong, but this seems a wrong
                           generation rule.
Wrong element's names.

                           In "PartyLegalEntity" the "StakeholderParty" definition has several typing
Typing error               mistakes.
                        The RemittanceAdviceLine is missing a cbc:InvoicingPartyReference
Add association         The cbc:InvoicingPartyReference available in the root is not sufficient.

                        The Invoice (and FreightInvoice) head and the Invoice Line are missing the
                        cbc:InvoicingPartyReference
Add association         for the same reason above described for the Remittance Advice.

                        In Party ABIE:
                        1) The OutsourcedServiceProviderParty is not a correct business term and
                        is changing the intended meaning.
                          It should be "OutsourcingServiceProviderParty" or just
                        "ServiceProviderParty"
                        2) The definition is to be defined:
                         Proposal: An association to a service provider party who acts as an
                        outsourcer.
Change element's name   3) Probably it could be better to change the cardinality as 0..n




                        In "Statement Line", change the definition of
Change definition       BalanceBroughtForwardIndicator.


                        In "TradeFinancing" the cardinality of "FinancingInstrumentCode" should be
Change cardinality      0..1 (or even 1..1) instead of 0..n.
                        In "TradeFinancing" move "ClauseCode" after "Clause". This is usally what
                        we did with other couples of textual and coded info
Move element


                        In PartyLegalEntity add a new "CorporateStockNote" information entity after
                        "CorporateStockAmount". Definition: Additional information related to the
Add association         Corporate Stock Amount.
                         In TaxTotal definition of "TaxIncludedIndicator" is incomplete. It shoud
Change definition        explain its difference from the TaxEvidenceIndicator.




                         In "TransportMeans" other JourneyIDs with specified who is the
Add BBIE to ABIE         issuer/owner should be added.

                         In "TransportMeans" an important information is the Trade Service which is
                         a coded information showing which is the regular service provided by that
                         carrier/transport mean. Add a "TradeServiceCode" and a
Add BBIEs to ABIE        "TradeServiceName".
                         In "TransportMeans" there is already a "OwnerParty" but it seems to generic
                         for expressing an important info like the shipping line.
                           The definition of this party could be tricky as usually we require a
                         specific "ShippingLineCode" and "ShippingLineName" information, for
                         instance.
                           I would suggest to provide a wrapper of the plain Party aggregate (like
                         we have for the AccountingCustomerParty in the Invoice)
                           For instance:
                           OwnerParty:
                           - CarrierCode 0..1 (e.g. SCL)
                           - CarrierShortName 0..1 (e.g. SAFMARINE)
                           - CarrierGroupCode 0..1 (e.g. MSK)
                           - CarrierGroupName 0..1 (e.g. MAERSK)
                           - JointServiceGroupCode 0..1 (e.g. UFS)
                           - JointServiceGroupname 0..1 (e.g. United Feeder Services)
                           - Party 0..1
                           - OperativeContact 0..1

                           NOTE: the Party still provides the possibility to specify the legal
Additional requirement   name of the carrier and other possible info.
                         In "TransportMeans", if not already available upper in the hieararchy (in a
                         better place), there could be the requirement of the following additional
Add association          info: add a "Customs Forwarder" 0..1
                         In "TransportMeans", if not already available upper in the hieararchy (in a
                         better place), there could be the requirement of the following additional
Add association          info: add a "MTOParty" (Multimodal transport operator) 0..1

                         In "TransportMeans" the "RoadTransport" is no more identified by a single
                         Plate ID information.
                         For security reasons the Driver Surname and name or License to Drive ID
                         could be required together the Plate ID.
                         I suggest to enhance this part:
                         - by changing the "LicensePlateID" into "TruckPlateID"
                         - by adding a "DriverParty" or a "Person"
                         NOTE: the License to drive (if required) can be specified on either a
Add association          Party or Person aggregates.

                         In "TransportMeans" the "RailTransport" requires more information.
                         I suggest to:
                         - Change the "RailCarID" name to "CargoWaggonID"
Add association          - Add a DocumentReference to reference a specific Raylways document.

                         In "TransportMeans" the "MaritimeTransport" requires more information.
                         I suggest to add an "InternationalRadioCallSignID" (0..1). This is a more
                         common Vessel identification used in the shipping chain. This is a unique
Add association          identifier available from ITU where every Ship has a radio call sign ID.

                         In Person: There is a missing a "PersonIdentity" information to be used to
                         precisely identify a person. The PersonIdentity could be:
                         - IdentityDocumentReference 0..1
                           Samples:
                           - license to drive
                           - passport number
                           - SSN (Social Security Number)
                           - Fiscal Code
                           - ...

                         - Also a "DigitalIdentity" could be important as it is an actual
Add association          information worldwide.
Move element             In the RequestForQuotation, move the RequestedValidityPeriod so it aligns
                         with the order, that is between the lineCountNumeric and
                         AdditionalDocumentReference

Change cardinality and   OptionalIndicator in RequestForQuotation must be optional and perhaps
element's name           renamed to OptionalLineItemIndicator

Add BBIE to ABIE         As part of the “AllowanceCharge” element we should have the possibility to
                         specify a “PerUnitAmount”. This would be an optional element which when
                         used would mean that the “Amount” of the “Allowance Charge” is equal to
                         the PerUnitAmount * the Quantity of Items at the specific line level or, when
                         used at the header level, the total number of items.
Add BBIE to ABIE            We should be able to specify the Item’s warranty terms in the Order
                            message. This means that we should add the “WarrantyValidityPeriod” and
                            perhaps “WarrantyParty” to the Order Line.

Add BBIE to ABIE            Add versionID to DocumentReference as optional element.




Change ABIE                 In copenhagen we decided to introduce a new document, Stock Availability
                            Report, having the same structure of Inventory Report ... the only difference
                            is the direction (S.A.R .comes from seller to retailer, I.R. comes from
                            Retailer to Seller).
                            So now we have that the Stock Availability Report has an
                            InventoryReportLine ASBIE ... in my opinion it sounds strange. I think that
                            the best choice could be have an ABIE "ReportLine" and to qualify it:
                            "Invetory" qualifier in I. R. and "Stock Availability" qualifier in S.A.R.
                            In PartyLegalEntity CompanyTypeCode should changes for
Change element name         BusinessClassificationScheme.
Qualified element           In ForecastException PurposeCode should be qualified.
Qualified element           In ProcessJustification ReasonCode should be qualified.
Qualified element           ResultCode should be qualified wherever it is used.
Qualified element           ResolutionCode should be qualified wherever it is used.
                            In ProcurementProject TypeCode and SubTypeCode should be qualified
Qualified element           (suggested qualifier: Procurement).


                            Add a new BIE in the root of Statement: cbc:StatementTypeCode (0..1). The
                            "Statement of Account" can be sent by the Supplier/Creditor to the
                            Buyer/Debtor into different forms, for instance could be a list of outstanding
                            invoices or a full statement for a period (already settled, to be settled and
Add BBIE                    overdue payments). But here there are further cases.
                            The actual Statement seems to be too much oriented to the
                            outstanding invoices, so it is difficult to specify Collected payments
                            (settled invoices).
                            I would suggest to add cac:CollectedPayment (0..n) with a structure like the
Add association             cac:PrepaidPayment.

                            AllowanceCharge should be also in the Statement Line as we should allow
                            the possibility to specify an allowance amount related to a line and its
                            referenced invoices.
                            Without these changes the UBL Statement will be far from actual
Add association             uses.
Add BBIE to document type   Add ParentVersionID to AttachedDocument as optional element.
Add BBIE to document type   We would like to have the possibility to specify in the “AttachedDocument” a
                            “LineID” or “ItemID” so that attachments can be added to a specific item e.g.
                            in the Catalogue. This element should also be optional.
Add BBIE to document type   AttachedDocument does not allow that the attachment is added to a line of
                            the document. This means that every attachment must be attached to the
                            (all) document. However, we would like to use it to carry attachments to a
                            specific Line in the Catalogue. Therefore, we would like to add the “LineID”
                            in this document. This element should be optional.

Add ASBIE to ABIE           At the European Commission, some contracts define prices for regions of
                            the globe such as Europe, North America… We currently cannot represent
                            this in the current structure of
                            Catalogue/CatalogueLine/RequiredItemLocationQuantity element. We
                            therefore would like to add a new optional element which enables the
                            specification of a “region of the globe”, Within it, we could have several
                            “ApplicableTerritoryAddress” elements.
Add ASBIE to ABIE           When Ordering an item, we need to specify the “WarrantyValidatyPeriod” in
                            the Order/OrderLine. Currently this element is not present. Can you please
                            let us know of a workaround? Could you please add this element to the
                            OrderLine in 2.1
   Recommendation                           Clarification

1. ExporterParty and
ImporterParty should be at
the Certificate of Origin
Application ASBIE. 2.
Removal of EndorserParty
at Certificate of Origin.




                               For example: the freight forwarding
                               instructions between the shipper and the
                               freight forwarder has to be complemented
                               by the shipping instructions to the actual
                               carrier; the certificate of origin process



the UBL deliverables
should be further extended
to multimodal transport with
the collaboration of TBG3
business experts.
Section 1.6, Customization,
should offer guidance on
how and when to place size
constraints on a given xml
element. In particular this




Change the relationship to
many-to-many
The same thing should apply for
OrderResponse and OrderChange
Peter says: I understand
your strugle. Items are in
UBL seem as information
about what is traded. The
focus has been on
identifing the item, not to
model its content. In a UBL
Order every Item is
attached throug a lineItem,
that also can contain a
price. Where an Item
specifies "What", an
lineItem specifies the claim
details used in the
transaction (How many,
when do I want it, to what
price, etc). If you have a
need for structured
information about the item
without price information
there are the following
posibillities:

1) Set up your own name-
value specification in
AdditionalItemProperty and
ItemPropertyGroup
2) Use a new
documenttype, like BOM in
the
ItemSpecificationDocument
Reference
”… amounts must be non-
3) Use a catalog document soren@ooidata.se
negative"

Add an option to state        soren@ooidata.se
buyer's domestic currency
(or something to that effect)
and add exchange rate
information for the domestic
and order document
currencies
Add Requested                 soren@ooidata.se
Delivery_Period Time
Add an address to receiver soren@ooidata.se
of invoice when different
from the Customer Party

Add delivery address on        soren@ooidata.se
line (cardinality 0..1)
Add Requested                  soren@ooidata.se
Delivery_Period Time
Change cardinality to           soren@ooidata.se
0..unbounded




I'm going to suggest in 2.1 that we add an optional ID to ItemProperty so that the Name can be textual and the ID be from a con

If you create a new
transaction interchange as
a supplemental pathway -
should be possible to run
those in parallel - and since
the core components are all
the same - would allow
people to use simple XSLT
to morph to/from as
needed.
Thank you for the response to my query
last week. Unfortunately the
branch making the sale is both the legal
address for the sale, and the
accounting address. Most of the
branches are individually owned, though
they are each grouped into one of 10
parent organisations.

- Parent 1 (This is the level I'm unsure of
how to model)
-- Branch 1 (Seller Customer Party /
Accounting Supplier Party)
-- Branch 2
- Parent 2
-- Branch 3
... etc

I suspect that you are correct in your
comment that I will need to use
the UBL Extensions to achieve this - I just
thought I might be missing
something as the concept of Head Office
Party is not uncommon. I'm sure
that I could use one of the other party
elements that you mentioned, but
I'm concerned that using one that doesn't
quite fit will cause problems
in future if any of these partner
organisations start using UBL for
their own purposes.
Revised diagram at
http://lists.oasis-
open.org/archives/ubl/2009
01/jpg00000.jpg
                          From Mark Brown
                          (mark_brown@toll.com.au)...
                          Unfortunately we encountered the same
                          problem for Actual Dates.
                          Our solution was to extend the UBL (a
                          Toll Version of UBL 2.0). This is only used
                          internally. The extension created a new
                          element group
                          "TollShipmentStage" with a very simply
                          structure.
                          ATD =
                          Manifest/ManifestDetail/cac:Shipment/cac
                          :ShipmentStage[0]/cac:TollShipmentStag
                          e/cac:Period[0]/cbc:StartDate
                          ATA =
                          Manifest/ManifestDetail/cac:Shipment/cac
                          :ShipmentStage[0]/cac:TollShipmentStag
                          e/cac:Period[0]/cbc:EndDate

                        Externally to trading partners we utilise
                        the use of agreed qualifiers.
                        e.g
                        ETD =
                        ns:BillOfLading/cac:Shipment/cac:Shipme
                        ntStage[0]/cac:TransitPeriod/cbc:StartDat
                        e
                            =
                        ns:BillOfLading/cac:Shipment/cac:Shipme
                        ntStage[0]/cac:TransitPeriod/cbc:Descripti
                        onCode[0]/*body = "ESTIMATED"
                        ETA =
                        ns:BillOfLading/cac:Shipment/cac:Shipme
Change QDT (spreadsheet ntStage[0]/cac:TransitPeriod/cbc:EndDate
and schema) to correct
recommendation number
             Items are in UBL seem as
            information about what is
            traded. The focus has been
            on identifing the item, not to
            model its content. In a UBL
            Order every Item is
            attached throug a lineItem,
            that also can contain a
            price. Where an Item
            specifies "What", an
            lineItem specifies the claim
            details used in the
            transaction (How many,
            when do I want it, to what
            price, etc). If you have a
            need for structured
            information about the item
            without price information
            there are the following
            posibillities:

            1) Set up your own name-
            value specification in
            AdditionalItemProperty and
            ItemPropertyGroup
            2) Use a new
            documenttype, like BOM in
            the
            ItemSpecificationDocument
            Reference
            3) Use a catalog document
            as Tim suggested.
            Makes Creditnote more
            compliant with an iinvoice

                                             Definition: Identifies the section (or line) of
                                             the document to which the response
                                             applies.




s header level
                                             Used to give the buyer a secondary
                                             choise
                               Used to specified whether a line is
                               required


Allign with invoice

Used to speciy charges.
Perhaps a surcharge class
is better.
There is missing a fixed
element to see whether
facturing is used.
InvoiceTypeCode must be
used instead.
Legal requirement for using
factoring




This field should be used to
specify the order type, for
example basic order,
blanket order, …
This field can be used, for
example, to specify the
reference to a Price List or
to another Catalogue.




In case of clothes article,
for example, "season"
could be a value for this
attribute.
icing period that applies to the particular line. Example of use is when there is a line for as subscription service.


ular tax may have to be paid immediately or later. Example is IT case where codes [D]: IVA ad esigibilità DIFFERITA (postponed) and [I]: IVA

parcels, gross weight and cube.




nk between each payment and its due date and payment means. To facilitate this a payment amount element should be added to the payme




ormation such as textual note.

ment for Catalogue transaction ID.

fore dates (need in the Catalogue).

ified by different certifications bodies and such certification may be important or even mandatory in some industries such as healthcare. (nee
ance to the action, that is, it does not mater if the version is 1.0, 2.0 or 3.0 the action is always the same. We could use more positive control


                                            This issue was: "In Catalogue, need
                                            possibility to provide physical attributes
                                            and package levels.". It was deleted
                                            because of it is the same of issue 59.
mportance of an attribute such as required, favourable. Further if the specification is being made in a tendering situation there may be a need

assification codes such as UN/SPSC but probably not because the classes are not that specific.

w for sequencing of both attributes and attribute groups. Used so that attributes can be processes in logical order e.g. in order of importance




ying the sender and the receiver roles. Since this is a generic document the sender and the receiver may have different roles such as buyer


hould not be mandatory. In the application response the document that is being responded to is identified in a separate document reference




a due date for the quote.
Provide a guideline
add a class:

 Qualification Resolution.
Details
 Qualification Resolution.
Admission Code. Code
 Qualification Resolution.
Procurement Project Lot
Identifier. Identifier
 Qualification Resolution.
Exclusion Reason. Text
 Qualification Resolution.
Resolution. Text
 Qualification Resolution.
Resolution Date. Date
 Qualification Resolution.
Resolution Time. Time
Immobilized Security.
Details
Immobilized Security.
Immobilization Certificate
Identifier. Identifier  0..1
Immobilized Security.
Security Identifier. Identifier
0..1
Immobilized Security. Issue
Date. Date 0..1
Immobilized Security. Face
Value. Amount 0..1
Immobilized Security.
Market Value. Amount
0..1
Immobilized Security.
Shares Number. Quantity
0..1
Immobilized Security.
Issuer_ Party. Party Party
0..1
Regulation Regulation.
Details
Regulation. Name. Text
1
Regulation. Legal
Reference. Text 0..1
Regulation. Ontology URI.
Identifier 0..1
Guarantee Certificate
Request. Details
Guarantee Certificate
Request. UBL Version
Identifier. Identifier
Guarantee Certificate
Request. Customization
Identifier. Identifier
Guarantee Certificate
Request. Profile Identifier.
Identifier
Guarantee Certificate
Request. Identifier
Guarantee Certificate
Request. Copy_ Indicator.
Indicator
Guarantee Certificate
Request. UUID. Identifier
Guarantee Certificate
Request. Contract File
Identifier. Identifier
Guarantee Certificate
Request. Issue Date. Date
Guarantee Certificate
Request. Issue Time. Time
Guarantee Certificate
Request. Guarantee Type.
Code
Guarantee Certificate
Request. Purpose. Text
Guarantee Certificate
Request. Liability. Amount
Guarantee Certificate
Add new class
ResultOfVerification and
add an ASBIE in the
Signature class. This will
require the removal of three
properties for the Signature
Class:

Signature. Details
Signature. Identifier
Signature. Note. Text
Signature. Canonicalization
Method. Text
Signature. Signature
Method. Text
Signature. Signatory_
Party. Party
Signature. Digital
Signature_ Attachment.
Attachment
Signature. Original_
Document Reference.
Document Reference



Result Of Verification.
Details
Result Of Verification.
Validator Identifier.
Identifier
Result Of Verification.
Change Result Code.
Validate cardinality for Code
Signatory Party in Signature
being optional, from 1 to
0..1




Add Participation Request
Reception_ Period in
Tendering Process.
Add BBIE Minimum
Improvement Bid. Text in
Awarding Criteria
Instead of using two BBIES
inTenderingProcess.,
create a class ABIE with alll
the required components
for the definition of an
Auction
This reference is issued by the payee
(seller/vendor)
and the payer is requested to accompany
the remittance with these reference.
There could be more than one reference
for multi-invoice reconciliation
with payments
and this reference is not strictly 1-to-1 with
a payment or with an
invoice, so it is up to the payee
to specify such reference in the
remittance head or for each remittance
line.




Actual Definition: If true, indicates that the
Statement Line contains a balance
brought forward.
Proposed Definition: If true, indicates that
the Statement Line has a balance
outstanding from the previous bill(s)
We have already theTradeFinancing
inside PaymentMeans so we
have already the chance of having
different financing means.




Example:
CorporateStockAmount = 1.000.000 EUR
CorporateStockNote = Fully paid-up
capita
JourneyID: This is the Carrier and/or
Trade Service "JourneyID", fine, but there
are often a different JourneyIDs:
         - used within consortium of
carriers (e.g. United FeederServices, Inc.)
           NOTE:In this case a Ship (or
other means) is operating as part of an
alliance, but each party has a different
Journey
ID (very bad yes!)
         - used by Container/goods
terminals.
           NOTE: Container terminals are a
good sample as mny different carriers are
visiting a terminal, thus using different
JourneyIDs that cannot be unique from
the Terminal point of
view (every carrier has its voy counter and
syntax)
              That's why it is important to
keep the relationship
between different Journey IDs.
There are documents which are not
subject to versioning e.g. the Invoice but
for some others the version is actually
almost mandatory e.g. Catalogue.
               Disposition                                     Status

accepted recommendation
                                              Done (EndorserParty removed from
                                              CertificateOfOrigin and ExporterParty
                                              and ImporterParty should be at the
                                              Certificate of Origin Application ABIE).




Customization guildeslines need to have a
section on field length restrictions (using
TDED).

Can't be part of the UBL Schema. No action


                                            Resolved.
Change cardinality Shipment:Consignment
in 1:n. Check with the Transportation group
if we can add Shipment to Consignment.
Check the difference between shipment and
consignment.                                Done: the cardinality
                                            (Shipment:Consigned) changed for 1:n.
Add Quantity discrepancy code to
ReceiptLine.

                                              Done (QuantityDiscrepancyCode added
                                              to ReceiptLine).
Change the cardinality in 0..n in all order
document .




                                              Done (cardinality of PaymentMeans
                                              changed to 0..n in Order,
                                              OrderResponse and OrderChange).
Use PaymentTerms as payment plan.
Percentage needs to be asdded to
PaymentTerms. Roberto will make a
testbed of this approach                      Resolved at the meeting in Allerød
                                              (PaymentPercent added to
                                              PaymentTerms).
Add subLineItem to LineItem in all billing
document. For example subInvoiceLine in
InvoiceLine with cardinality 0..n.




                                                Done (SubCreditNoteLine added in
                                                CreditNoteLine. SubDebitNoteLine
                                                added in DebitNoteLine. SubInvoiceLine
                                                added in InvoiceLine).
Rejected. No action. This is an issue for the
further customization to deal with.

In the Order, Order Response and Order
Change add the exchange rate for each
currency code (see the Invoice as
example).                                       Done (TaxExchange Rate,
                                                PricingExchangeRate,
                                                PaymentExchangeRate added in Order,
                                                OrderResponse and OrderChange).
No action. Not an UBL issue.
                                                Resolved.
No action. Not an UBL issue.


                                                Resolved.
No action. Not an UBL issue.
                                                Resolved.
No action. Not an UBL issue.
                                                Resolved.
No action. Not an UBL issue.

                                              Resolved.
Initial solution (rejected): add
CarashtiristicTypeCode to ItemProperty.
New proposal from Georg: adding
Item.Property.Code. Use same element
name as for .name to clearly show that this
is same information, only coded. Not to use
Characteristics term since it conflicts in
meaning with the property term.               Done (NameCode and Value Qualifier
                                              added to ItemProperty).
To be review in conjountion with the
preawarding message Contract. A contract
must be able to refer to a catalogue and
vice versa (thte exists a referece today, but
it must be reviewet after the contract has
been designed)




                                           no action
Ask Ken Holman how to use quote properly




                                           See the email forwarded by Tim on 17
                                           september 09
Add a new ABIE called Corporate
information and add a new ASBIE to it in
PartyLegalEntiry




                                           Peter to email about
                                           SellerCustomerParty
Agreed not to use qualified datatypes.


                                           Resolved.
Add an OrderResponseCode in
OrderResponse.




                              Done (OrderResponseCode added in the
                              OrderResponse).
Add estimated and required Date and Time
to shipment stage




                                           Done (EstimatedDeliveryDate,
                                           EstimatedDeliveryTime,
                                           RequiredDeliveryDate,
                                           RequiredDeliveryTime have been added
                                           to ShipmentStage).
Correct it

                                           Done(the spreadsheet UBL-qDT-2.0 has
                                           been updated ).
Add subLineItem to LineItem, similar for the
billing lines.




                                                 Done (SubLineItem added in LineItem).
accept                                           Done (BuyerCustomerParty and
                                                 SellerSupplierParty added in CreditNote
                                                 and SelfBilledCreditNote).


                                                 Done (definition updated).
Check if it is the same think of
submissiondate.                                  Done (it is the same issue of 74).
Add PrivacyCode on header and line level         Done (PrivacyCode added in RFQ Line
(on document level it is qualified with          and HighestPrivacyCode added in RFQ).
highest.                                         Partially undone by issue 156.
Add SecuretyClassificationCode on header
and line level. On document level it qualified   Done (SecurityClassificationCode added
with highest.                                    in RFQ Line and
                                                 HighestSecurityClassificationCode added
                                                 in RFQ). Partilly undone by issue 156.
Accepted                                         Done (AlternativeLineItem added to
                                                 QuotationLine).
Add OptionalIndicator RFQ Line 1..1.
Description: an indicator to identify wheter
rfq line is optional in the quotation.         Done (OptionalIndicator added to
                                               RequestForQuotationLine).
Accepted                                       Done (AllowanceCharge added to
                                               CreditNoteLine).
Add PenaltySurchagePercent and Amount
in the ReminderLine                            Done (Penalty_ Surcharge Percent and
                                               Amount added to RemainderLine).
Discussed with Georg and Roberto. No
action required.


                                               Resolved.
Discussed with Georg and Roberto and
then with Roberto and Oriol. The first
disposition "add FactoringTerms to
PaymentTerms" was changed in "Add a            Done (Add a new ABIE TradeFinancing
new ABIE TradeFinancing to common              to the common library. Add it in
library and add it to PaymentTerms".           PaymentTerms).
Rejected. No action required.                  Resolved.
added as OrderType, InvoiceType.

                                               Done (OrderTypeCode added to Order
                                               and OrderReference).
accept

                                               Done (DocumentReference added to
                                               Catalogue).
<all notes should be 0..n
                                               Done (cardinality changed in OrderLine,
                                               LineItem, CreditNoteLine, DebitNoteLine,
                                               DespatchLine, InvoiceLine,
                                               QuotationLine, ReminderLine,
                                               RequestForQuotationLine,
                                               StatementLine. Furthermore cardinality
                                               of Note updated in
                                               ClassificationScheme, Contact and
                                               Signature).
Add KeyWordItemProperty to
CatalogueLine
                                               Done (KeywordItemProperty added in
                                               CatalogueLine).
Add association between Price and
ExchangeRate 0..1 and definition is: to
define the exchange rate if the exchange
rate differs from the document level           Done (PricingExchangeRate added in
exchange rate.                                 Price).
Agree to apply the HashAlgoritm to
ExternalReference. Add MimeCode, Format      Done (HashAlgorithmMethod,
and EncodingCode, CarachterSetCode,          MimeCode, FormatCode,
URI, FileName to ExternaleReference. Add     EncodingCode, CharacterSetCode and
LanguageCode, LocaleCode, IssueTime,         FileName added in ExternalReference.
IssuingParty, ValidityPeriod, Signature to   IssueTime, LanguageID, LocaleCode,
DocumentReference (see issue 122)            ValidityPeriod and IssuerParty added in
                                             DocumentReference).
Add InvoicePeriod to InvoiceLine.            Done (InvoicePeriod added to
                                             InvoiceLine).
This is a functionally of Invoicing Party in
business process. It is not a requirements in
the document. Rejected.                       Resolved.
Add Shipment class to Delivery class.         Done (Shipment added in Delivery -
                                              cardinality 0..1).
Add PenaltyAmount,                            Done (added PenaltyAmount,
SettlementDiscountAmount,                     SettlementDiscountAmount,
PaymnetDueDate and InstallmentDueDate PaymentDueDate and
in PaymentTerms. Add InvoiceDueDate in InstallmentDueDate in PaymentTerms.
Invoice.                                      Added InvoiceDueDate in Invoice.)
Add CatalogueReference to Order.
                                             Done (CatalogueReference added in
                                             Order - cardinality 0..1)
Agree to add PaymentTerms to Order.          Done (PaymentTerms added in Order).
Add TransactionId to Catalogue.              Done (TransactionID added in
                                             Catalogue). Undone by issue 148.
Add BestBeforeDate to ItemInstance.          Done (BestBeforeDate added in
                                             ItemInstance).
Add Certificate 0..n to Item                 Done (created the Certificate ABIE and
                                             added it in Item).
Add Package 1..0 to ItemLocationQuantity
and recommende RetailPrice to Package




                                             Done (Package added in
                                             ItemLocationQuantity).
Add Barcode ABIE to ItemIdentification and
to ItemInstance and to LotIdentification.
Talk to an expert to define the Barcode
structure.

                                             to be update by Arianna
Add an Action Indicator.                     Done(ActionCode has been added to
                                             Catalogue).
Done by adding Certificate 0..n to Item      Done: Peter asked to Jan Marøe about
                                             what is needed for environmental info.



                                             Deleted (it is the same of issue 59).
Add EffectiveDate and Time to Catalogue
Deletion.                                    Done (EffectiveDate and EffectiveTime
                                             have been added to CatalogueDeletion)
See Oriol excel file related to ItemProperty
                                               Done (NameCode, ValueQuantity,
                                               ValueQualifier, ImportanceCode and
                                               RangeDimension have been added to
                                               ItemProperty; changed cardinality of
                                               Name and Value).
See Oriol excel file related to ItemProperty   Done (ImportanceCode added in
                                               ItemPropertyGroup)
See Oriol excel file related to ItemProperty
                                               Done (see item 65)
No action.                                     Done by adding ImportanceCode to
                                               ItemProperty (see item 65).
Add new document called InvoiceDispute
and we add Appeal BBIE to it                 To do.
Rejected. The roles are already specified in
context of the parent business document.
                                             Resolved.
Accepted.
                                             Done (cardinality of DocumentResponse
                                             has been changed).
Accepted. Add Effective Date and Time.       Done (EffectiveDate and EffectiveTime
                                             have been added to
                                             ApplicationResponse). Undone by issue
                                             146.
Accepted. Add
RequesteForQuotationLineID in                Done (RequesteForQuotationLineID
QuotationLine                                added in QuotationLine).
Add QuotationSubmissionDate to               Done (QuotationSubmissionDate added
RequestForQuotation ABIE                     in RequestForQuotation - cardinality
                                             0..1).
Accepted. Add a RequestedValidityPeriod.
                                             Done (RequestedValidityPeriod added in
                                             Request For Quotation - cardinality 0..1).
Accepted. Add a BuyerCustomerParty to        Done (BuyerCustomerParty added in
RequestForQuotation.                         Request For Quotation).
Accepted.
                                             Done (cardinality of PaymentMeans
                                             changed to 0..n in Statement).
Remap and address other structure




                                               Resolved.
Add Contact to Person (0..1). Person in
Party 0..n.                                    Done (Contact added in Person;
                                               cardinality of Person in Party changed to
                                               0..n).
Update definition of ASBIE Contact in
Party: contact information related to the
party. Update definition of ASBIE Contact in
Person: contact information related to
person. Update the definition of Name
within contact to say it is recomanded this is
not to be used for person name but for
functional names.                              Done (three definitions updated).
Accepted. Rejected (see issue 122)             Done (Signature added to Attachment -
                                               cardinality 0..n)
check if compression alghoritm is always
covered inside BinaryObjectType                Covered by EncodingType.
Recommende that implemeter such as BII
and PEPPOL, … formalize calculation
models for the relationships between these
objcts and aim to provide reference
implementation for use by other groups.

Add TaxIncludedIndicator to TaxTotal        Done (TaxIncludedIndicator add in
                                            TaxTotal).
Add AllowanceCharge to CreditNoteLine

                                            Done (AllowanceCharge added in
                                            CreditNoteLine).

Create two new spreadsheet and allign it    The StatusRequest has been approved
with Transport                              during the psc meeting. The
                                            StatusResponse is under revision.
Add DocumentStatusCode to                   Done (DocumentStatusCode added in
DocumentResponse.                           DocumentResponse). Undone by issue
                                            147.


Rejectede as the LegalParty describes who
the Contracting Party acts on behalf      Resolved. No action to do.
Accepted. Add LegalForm in
TenderQualification.


                                            Updated by Arianna. To check with Oriol.
Accepted.


                                            Done. VariantConstraintIndicator added
                                            in TenderingTerms.
Accepted.
                                            Done.
Accepted.




                                            Done (AdmissionIndicator changed to
                                            AdmissioneCode;
                                            ProcurementProjectLotID and Exclusion
                                            reason added). To chek with Oriol.
Accepted. Oriol will provide a code list.   Done. FundingProgramCode added in
                                            TenderingTerms.
Accepted.                                   Done. PenaltyCaluses added in
                                            TenderingTerms.
Accepted.                                   Done. The change was in
                                            ProcurementProject, not in
                                            TenderingTerms.
Accepted.                                   Done. AcceptedVariantsDescription
                                            added in TenderingTerms.
Accepted.                                   Done. ContractualDocumentReference
                                            added in TenderingTerms.
Accepted.
                                            Done. ContractAcceptancePeriod added
                                            in TenderigTerms.
Accepted.                                   Done.
                                            ParticipationRequestReceptionPeriod
                                            added in TenderingProcess.
Accepted.                                   Done. FeeAmount and FeeDescription
                                            added in TenderedProject.
Accepted.
                                            Done. TechnicalCommitteePerson added
                                            in AwardingTerms.
Add a CompanyTypeCode in
PartyLegalEntity and StackholderParty 0..n
to PartyLegalEntity: list of stackhoders who Done (CompanyTypeCode and
founds the consorptium. Accept qualifying StackholderPary added to
party                                        PartyLegalEntity).
see previous item
                                             see previous issue
see previous item
                                             see previous issue
Add ResolutionDocumentReference.
                                             Done. ResolutionDocumentReferece
                                             added in TenderQualificationResponse.
Accepted.                                        Done. Note added in
                                                 TenderQualificationResponse header.
A definition of OriginalId is needed. Oriol will Done. OriginalId removed from
provide it.                                      FrameworkAgreement.
                                                 OriginalContractingSystemIdentifier
                                                 added in TenderingProcess.
Accepted.                                        Done (TendereQualificationResponse,
                                                 Tender Receipt, UnawardedNotification
                                                 and Awardednotification updated).
Accepted.                                        Done (ReopeningIndicator removed from
                                                 FrameworkAgreement).
Accepted.                                        Done (DurationMeasure removed and
                                                 DurationPeriod added in
                                                 FrameworkAgreement).
Accepted.




                                             Done (ImmobilizedSecurety ABIE added
                                             to Common Library). Description are
                                             missing.
Accepted.




                                             Done (Regulation ABIE added to
                                             CommonLibrary)
Accepted.                                    Done (Global Indicator removed from the
                                             Guarante Certificate).
Accepted.                                    Done (ContractName renamed it
                                             Purpose).
Accepted.                                    Done (ApplicableRegulation added to
                                             GuaranteeCertificate).
Accepeted                                Done (LegalDocumentReference
                                         renamed it
                                         GuaranteeDocumentReference).
Accepted.                                Done (ImmobilizedSecurety added to
                                         GuaranteeCertificate).
Accepted but Tim has to approve the name Done (Guarantee document has been
                                         created).
Accepted. A collaboration diagram is
needed.




                                        Done.
Original issue is rejected.

                                        Done.
To discuss with Tim.




                       Done (ValidationDate, ValidationTime
                       and ValidatorID removed from Signature,
                       Result Of Verification added in
                       Signature).
Accepted.




                       Done (cardinality changed).
Accepted.

                       Done (it is the same issue 101).
Accepted.
                       Done (MinimumImprovementBid added
                       to AwardingCriteria).
Accepted.




                                           Done (Auction added in
                                           TenderingProcess and
                                           AuctionJustificationDescription
                                           AuctionConstraint Indicator removed
                                           from).
Postponed.

Allign with the original request.
                                           Done (name changed in
                                           AwardingMethodTypeCode).




Accepted                                   Done (InventoryDate and InventoryTime
                                           removed. InventoryPeriod added in
                                           InventoryReport).
Accepted AvailabilityDate.
                                           Done (AvailabilityDate added in
                                           InventoryReportLine).
Accepted AvailabilityStatusCode. Provide a
code list                                  Done (AvailabilityStatusCode added in
                                           InventoryReportLine).


                                           Done (ContractResponsibleParty and
                                           TenderEvaluationParty added in
Accepted                                   TenderingTerms).
                                           Done (Description added in
Accepted                                   AppealTerms).

                                           Done (OpenTenderID and
                                           ProcurementProjectLotID added in
Accepted                                   TenderPreparation).

                                           Done (TemplateDocumentReference
Accepted                                   added in TenderRequirement).
                                           Done (TendererQualification changed for
Change the name of ABIE in                 TendererQualificationRequest. Updated
TendererQualificationRequest.              ASBIEs in TenderingTerms).
Accepted. Add ReasonCode and Reason   Done (ReasoneCode and Reason added
(as text)                             in ProcessJustification).
                                      Done (CompletedTaskTypeCode
Accepted                              removed from CompletedTask).

Accepted. Change in
TendererRequirement_ TypeCode         Done (no change was need).

                                      Done (LanguageCode removed from
Accepted                              Evidence).

                                      Done (in TenderPreparation, TenderID
                                      changed for TenderEnvelopeID and
                                      TenderTypeCode changed for
Accepted                              TenderEnvelopeTypeCode).



                                      Done (ContractExecutionRequirement
                                      added to CommonLibrary. In
                                      TenderingTerms, ASBIE
                                      ContractExecutionTenderRequirement
                                      changed for
Accepted                              ContractExecutionRequirement).
                                      Done (RequiredCurriculaIndicator added
Accepted                              in TenderingTerms).
                                      Done (EffectiveDate and EffectiveTime
                                      removed from Application Response and
Proposed and approved in CPH f2f.     added to Response).
                                      Done (StatusCode removed from
Proposed and approved in CPH f2f.     DocumentResponse).
Proposed and approved in CPH f2f.     Done.
                                      Done (TransactionID removed from
Proposed and approved in CPH f2f.     Catalogue).
                                      Done (SourceCatalogueReference
Proposed and approved in CPH f2f.     added to Catalogue).

                                      Done (BuyerCustomerParty and
Proposed and approved in CPH f2f.     SellerSupplierParty added in DebitNote).
                                      Done (PaymentTerms added to
Proposed and approved in CPH f2f.     OrderChange).
                                      Done (PaymentTerms added to
Proposed and approved in CPH f2f.     OrderResponse).
                                      Done (PaymentPurposeCode added to
                                      InvoiceLine, CreditNoteLine,
Proposed and approved in CPH f2f.     DebitNoteLine).
                                               Done (PaymentPurposeCode from
Proposed and approved in CPH f2f.              Reminder, RemittanceAdvice, Statment).

                                               Done (HighestSecurityClassificationCode
                                               and HighestPrivacyCode removed from
Proposed and approved in CPH f2f.              RFQ).
                                               Done (QuotationDueDate changed for
Proposed and approved in CPH f2f.              SubmissionDueDate).
                                               Done (PaymentPurposeCode removed
Proposed and approved in CPH f2f.              from Statment).

Proposed and approved in CPH f2f.              Done (documents renamed).
                                               Done (Signature ASBIe was moved
Proposed and approved in CPH f2f.              before SenderParty).
                                               Done (Period and PlannedSettlement
                                               ASBIE removed and PaymentTerms
Proposed and approved in CPH f2f.              added to OnAccountPayment).
                                               Done (ABIE Renewal added to
                                               CommonLibrary. ASBIE added to
Proposed and approved in CPH f2f.              Contract Extension).
                                               Done (CollaborationID changed for
Appoved by email discussion                    ProfileExecutionID ).
                                               Done (Location Coordinate added to
Appoved by email discussion                    Location).
                                               Done (Location Coordinate added to
Appoved by email discussion                    SubsidiaryLocation).
                                               Done (ReferenceDate, ReferenceTime
                                               and ReliabilityPercent added in Transport
Appoved by email discussion                    Status ).

                                               Done (AppealTerms added to
Approved.                                      TenderingTerms).


                                               Done (LegalForm added to library and to
Approved.                                      TenderQualificationRequest).
                                               Done (cardinality of TypeCode changed
Approved.                                      for 0..1)
                                               Done (last occurence of Note element
Approved.                                      removed)
                                               Done (TenderDocumentReference
Approved.                                      added before Signature).

Appoved.                                       Done (the qualifier has been corrected).


                                               Done ("TransportExecutionPlan"
Approved.                                      removed from property term)

Approved. Change for: "An association to
the list of stackhoders in the consorptium."   Done (description updated).
For public review.                          Postponed.



For public review.                          Postponed.




Remove OutsourcedServiceProviderParty.
Change definition of ServiceProviderParty
for:"An association to a another party
provide a service to this party." Change    Done (OutsourcedServiceProviderParty
cardinality.                                removed. Added ServiceProviderParty).




For public review.                          Postponed.



Approved.                                   Done (cardinality changed for 0..1)


Rejected.                                   No action required.




For public review.                          Postponed.
Definition: An indicator to tell whether tax is
included in the calculation                     Done (definition updated).




For public review.                            Postponed.

Approved. Cardinality 0..1.
"TradeServiceCode" def: Information
showing the regular service provided by       Done (TradeServiceCode added to
carrier.                                      TransportMeans).




For public review.                            Postponed.
For public review.   Postponed.


For public review.   Postponed.




For public review.   Postponed.




For public review.   Postponed.




For public review.   Postponed.




For public review.   Postponed.
Approved.


                     Done (element moved).
Approved
                     Done (element renamed and cardinality
                     changed for 0..1)




                     Done (PerUnitAmount added to
                     AllowanceCharge). To check if it is in the
Approved             right position.
Add the “WarrantyValidityPeriod” and
perhaps “WarrantyParty” to the LineItem (so Done (WarrantyValidityPeriod and
it will follow the whole ordering phase).   WarrantyParty added to LineItem).




For public review.                         Postponed.
Change the line name in
StockAvailabilityReport



                                           Done (InventoryReportLine removed
                                           from StockAvailabilityReport.
                                           StockAvailabilityReport line added to the
                                           library and to StockAvailabilityReport).

For public review.                         Postponed.
For public review.                         Postponed.
For public review.                         Postponed.
For public review.                         Postponed.
For public review.                         Postponed.

For public review.                         Postponed.




For public review.                         Postponed.




For public review.                         Postponed.




For public review.                         Postponed.
For public review.                         Postponed.



For public review.                         Postponed.
For public review.   Postponed.




For public review.   Postponed.



For public review.   Postponed.
                   Action                                   Remark                    Action
                                                                                       no




Change in next major release: 1. ExporterParty and ImporterParty should be at the Certificate of Origin Application ASBIE. 2. R




No action is required on the library




No action is required on the library


No action is required on the library




No action is required on the library
                                         Mark Leitch sais: As far as I can see,
                                         there is only one UBL 2.0 document
                                         that has unbounded Payment Means
                                         and that is the Invoice itself; the other
                                         five documents that have Payment
                                         Means (Quotation, Order, Order
                                         Change, Order Response and Self
                                         Billed Invoice) all have 0..1 Payment
                                         Means. Note: Payment Means is also
                                         in AllowanceCharge (0..n), Statement
                                         (0..1), StatementLine (0..1),
                                         Remittance Advice (0..1), Reminder
                                         (0..n), but not relevant to this
                                         conversation.

                                         As far as I can remember, the
                                         unbounded Payment Means in Invoice
                                         was a Swedish requirement for
                                         situations where an Invoice could be
                                         settled via a bank or via the Giro
                                         system; it wasn't to facilitate multiple
                                         due dates. I do have to say, however
                                         (and the NES customisation has
                                         proved this), having the due date only
                                         available in Payment Means is a real
                                         pain ! In NES we have to use a
                                         Payment Means Code "1" just to get
                                         access to the due date for the Invoice
                                         where the due date is not Payment
                                         Means specific.

                                         "Traditionally" we have thought of the
                                         Quotation document as the carrier for




Add the PaymentSettlements PaymentPlan
to the billing documents.
Martin Forsberg has suggested to use
parentreference in stead of sublines. It
was agreed that a recursive sloution is
the best here unless Martin can come
up with good arbeuments against it.
Peter and Arianna will ask Martin in
Rome. Recursion is used by UBL so
this is consistent.
Ken says:
I've found thousands of elements
related to
<cac:ContractorCustomerParty>
through both the document level and
the line level ... but I have not found
any explicit contract information
whatsoever ... only information
describing a *reference* to a contract.
The party information is necessarily
extensive because of the options
offered to describe agents, legal
entities, etc.

But as for simplifying the contract
information per se, I don't see where.
Note that my analysis is only based on
a search of the term "contract" in
element names in the XPath files ... of
course I may be overlooking the
contract information you are referring
to.

So, can you cite for me which contract
information you think should be
removed from Catalogue when people
are defining their own customizations
of UBL? Of course this cannot be
"removed" in the UBL 2.1
specification, but for a reader of this
mail list archive, they should know that
any optional item in UBL can of course
be deprecated by a customization that
UN/TDED Code for OrderType should
be CL 1225 (suggestion from Martin).
Check cardinalty and description

Check cardinalty and description.
Check cardinality and definition.




                                    UN/TDED Code for OrderType should
                                    be CL 1001 (suggestion from Martin).
Check cardinality




Check cardinalities and definition of
elements in the new ABIE Certificate.
Check the recommendation.




Waiting for the Barcode structure.
Check cardinality
Check cardinality




Check definition
Waiting for code list.




Check definition.
UN/TDED Code for
AvailabilityStatusCode should be CL
7011 (suggestion from Arianna).
of Origin Application ASBIE. 2. Removal of EndorserParty at Certificate of Origin.
                                                                                                                                      New documents




Project    Submitter           Email                    Process             Collaboration          Proposed document Name Definition                                PSC Proposed doument Name   Comment          Status
                                                                                                                          UtilitySpecification is a kind of
                                                                                                                          attachment document used for
                                                                                                                          specifying the extended informations
                                                                                                                          needed by the Utility sector in addition
                                                                                                                          to a standard invoice.
                                                                                                                          UTS is therefore a supplement to an
                                                                                                                          OIOUBL Invoice or CreditNote.
                                                                                                                          UTS is issued as a selfcontained
                                                                                                                          OIOUBL document using af dedicated
Utillity   Peter L. Borresen   plb@ebconnect.dk         Procurement         Billing                UtillitySpecification  OIOUBL profile.                           UtillityStatement
                                                                                                                          The document used for a Contracting
                                                                                                                          Authority to define the procurement
                                                                                                                          project to buy goods, services or works
Codice     Oriol Bausà         oriol@invinet.org        Procurement         Tendering              CallForTenders         during an specified period.
                                                                                                                          The document used for a Contracting
                                                                                                                          Authority to announce the project to buy
Codice     Oriol Bausà         oriol@invinet.org        Procurement         Tendering              ContractNotice         goods, services or works.
                                                                                                                          The document used for a Contracting
                                                                                                                          Authority to declare the intention to buy
                                                                                                                          goods, services or works during an
Codice     Oriol Bausà         oriol@invinet.org        Procurement         Tendering              PriorInformationNotice specified period.

                                                                                                                               The document published by a
                                                                                                                               Contracting Authority to announce the
Codice     Oriol Bausà         oriol@invinet.org        Procurement         Tendering              ContractAwardNotice         awarding of a procurement project.
                                                                                                                               A message which the procuring
                                                                                                                               organization sends to an economic
                                                                                                                               operator in order to notify its admision
                                                                                                                               or exclusion to/from the tendering
Codice     Oriol Bausà         oriol@invinet.org        Procurement         Tendering              QualificationResponse       process
                                                                                                                               A message sent by the Contracting
                                                                                                                               Authority to an Economic Operator
Codice     Oriol Bausà         oriol@invinet.org        Procurement         Tendering              InvitationToTender          inviting him to tender
                                                                                                                               A document to notify the deposit of a
Codice     Oriol Bausà         oriol@invinet.org        Procurement         Tendering              GuaranteeCertificate        guarantee.
                                                                                                                               A message which a tenderer offers a
                                                                                                                               tender to the tendering organization for
Codice     Oriol Bausà         oriol@invinet.org        Procurement         Tendering              Tender                      bid.

                                                                                                                               A document used for the Tenderer to
Codice     Oriol Bausà         oriol@invinet.org        Procurement         Tendering              Qualification               Projected demand for anown condition.
                                                                                                                               declare things about his item sourced
                                                                            Collaborative                                      at a seller location and consumed at a
                                                                            Planning, Forecasting                              buyer location
iSURF      Yildiray Kabak      yildiray@srdc.com.tr     Procurement         and Replenishment     Forecast

                                                                                                                               A set of proposed changes to a
                                                                                                                               forecast, as the result of, for example,
                                                                                                                               promotional activity, weather,
                                                                            Collaborative                                      distribution or transportation issues, or
                                                                            Planning, Forecasting                              replanning
iSURF      Yildiray Kabak      yildiray@srdc.com.tr     Procurement         and Replenishment     Forecast Revision
                                                                                                                               Actual product movement observed,
                                                                                                                               which may include on-hand
                                                                            Collaborative                                      quantities, distribution center (DC)
                                                                            Planning, Forecasting                              withdrawals, or Point-of-Sale (POS)
iSURF      Yildiray Kabak      yildiray@srdc.com.tr     Procurement         and Replenishment     Product Activity
                                                                                                                               A collection of values gathered for key
                                                                                                                               performance metrics in the
                                                                                                                               trading partner relationship, such as
                                                                                                                               forecast error, sales growth, or the
                                                                            Collaborative                                      number of
                                                                            Planning, Forecasting                              emergency orders
iSURF      Yildiray Kabak      yildiray@srdc.com.tr     Procurement         and Replenishment     Performance History

                                                                                                                               Indication of a variance from trading
                                                                                                                               partner guidelines for changes in a
                                                                            Collaborative                                      forecast, differences between partner
                                                                            Planning, Forecasting                              forecasts, or key performance metrics
iSURF      Yildiray Kabak      yildiray@srdc.com.tr     Procurement         and Replenishment     Exception Notification       (e.g., forecast error, overstock)
                                                                                                                               Definition of the threshold for variances
                                                                            Collaborative                                      beyond which an exception
                                                                            Planning, Forecasting                              message should be triggered
iSURF      Yildiray Kabak      yildiray@srdc.com.tr     Procurement         and Replenishment     Exception Criteria
                                                                                                                               Parameters to guide the collaborative
                                                                                                                               replenishment process for an
                                                                            Collaborative                                      item sourced at a seller location and
                                                                            Planning, Forecasting                              consumed at a buyer location
iSURF      Yildiray Kabak      yildiray@srdc.com.tr     Procurement         and Replenishment     Item Location Profile
                                                                                                                               Description of a promotion, inventory
                                                                                                                               policy change, or other planned event,
                                                                                                                               along
                                                                            Collaborative                                      with its expected and actual impacts on
                                                                            Planning, Forecasting                              the supply chain
iSURF      Yildiray Kabak      yildiray@srdc.com.tr     Procurement         and Replenishment     Event
                                                                                                                               One trading partner’s request to the
                                                                                                                               other to send product
                                                                                                                               activity, forecast, or performance data,
                                                                            Collaborative                                      when the partner does not
                                                                            Planning, Forecasting                              automatically send data
iSURF      Yildiray Kabak      yildiray@srdc.com.tr     Procurement         and Replenishment     Item Information Request

                                                                                                                               This document type defines the
                                                                                                                               business need, lifecycle, structure and
                                                                                                                               content of messages that communicate
                                                                                                                               information about retail events (such as
                                                                            Collaborative                                      promotions, product introductions,
                                                                            Planning, Forecasting                              community or environmental events)
iSURF      Yildiray Kabak      yildiray@srdc.com.tr     Procurement         and Replenishment     Retail Event                 that affect supply or demand
                                                                                                                                                                                                The Sales
                                                                                                                               Daily sales report sent by retailer.This                         Report has
                                                                                                                               document contains the information                                been
                                                                                                                               about the sales at a certain location, on                        removed
                                                                                                                               a certain day, for a certain item and                            from the list
                                                                                                                               with a certain price (one line per price                         of new
                                                                                                                               really paid).                                                    documents
                                                                                                                               The payload is the quantity of that item                         because the
                                                                            Cyclic replenishment                               at that price. The information is used                           Product
                                                                            program (CRP),                                     for the planning of deliveries in "vendor                        Activity (that
                                                                            Classical preorder,                                managed inventory" (VMI) or for the                              is more
                                                                            Vendor managed                                     issuing of a concession invoice, if such                         generic)
eBiz       Arianna Brutti      arianna.brutti@enea.it   Marketing & sales   inventory (VMI)        Sales report                financial model is chosen.                                       covers it.
                                                                                                                                                                                                The
                                                                                                                                                                                                Inventory
                                                                                                                                                                                                Movement
                                                                                                                                                                                                Report has
                                                                                                                                                                                                been
                                                                                                                                                                                                removed
                                                                                                                             Report of movement of goods between                                from the list
                                                                                                                             the locations of a retailer.This                                   of new
                                                                                                                             document is used to provide                                        documents
                                                                                                                             information about movement of a                                    because the
                                                                                                                             certain quantity of items between the                              Product
                                                                            Cyclic replenishment                             locations of a retailer. The ship-to and                           Activity (that
                                                                            program (CRP),                                   the ship-from branch are mentioned.                                is more
                                                                            Vendor managed                                   The information is normally provided                               generic)
eBiz       Arianna Brutti      arianna.brutti@enea.it   Marketing & sales   inventory (VMI)        Inventory movement report when the items are shipped.                                        covers it.

                                                                                                                               Report about the quantities on
                                                                                                                               stock.The message is used to provide
                                                                                                                               information about the quantities of
                                                                                                                               each item which are or will be on
                                                                            Cyclic replenishment                               stock. It can be exchaged between
eBiz       Arianna Brutti      arianna.brutti@enea.it   Marketing & sales   program (CRP)          Inventory report            business partner in both direction.
                                                                                                                               This document is used in the context of
                                                                                                                               the "vendor managed inventory" (VMI)
                                                                                                                               scenario to initiate a return of goods.
                                                                                                                               The producer is requesting products
                                                                                                                               which are badly sold either for use in
                                                                            Vendor managed                                     other places or just to free the area
eBiz       Arianna Brutti      arianna.brutti@enea.it   Marketing & sales   inventory (VMI)        Instruction for returns     from it.
EC         JRF                 joao.frade@pwc.be                                                   Status Request
EC         JRF                 joao.frade@pwc.be                                                   Status Response




                                                                                                                                          Side 257
                                         New ABIEs
Project    Submitter           Email              Process




Utillity   Peter L. Borresen   plb@ebconnect.dk   Procurement




Utillity   Peter L. Borresen   plb@ebconnect.dk   Procurement

Utillity   Peter L. Borresen   plb@ebconnect.dk   Procurement
Utillity   Peter L. Borresen   plb@ebconnect.dk   Procurement
Utillity   Peter L. Borresen   plb@ebconnect.dk   Procurement




Utillity   Peter L. Borresen   plb@ebconnect.dk   Procurement
Utillity   Peter L. Borresen   plb@ebconnect.dk   Procurement

Utillity   Peter L. Borresen   plb@ebconnect.dk   Procurement

Utillity   Peter L. Borresen   plb@ebconnect.dk   Procurement

Utillity   Peter L. Borresen   plb@ebconnect.dk   Procurement

Utillity   Peter L. Borresen   plb@ebconnect.dk   Procurement
Utillity   Peter L. Borresen   plb@ebconnect.dk   Procurement
Utillity   Peter L. Borresen   plb@ebconnect.dk   Procurement




Utillity   Peter L. Borresen   plb@ebconnect.dk   Procurement

Utillity   Peter L. Borresen   plb@ebconnect.dk   Procurement



                                           Side 258
                                           New ABIEs

Utillity   Peter L. Borresen   plb@ebconnect.dk    Procurement


Utillity   Peter L. Borresen   plb@ebconnect.dk    Procurement
Utillity   Peter L. Borresen   plb@ebconnect.dk    Procurement

Utillity   Peter L. Borresen   plb@ebconnect.dk    Procurement

Codice     Oriol Bausà         oriol@invinet.org   Procurement

Codice     Oriol Bausà         oriol@invinet.org   Procurement
Codice     Oriol Bausà         oriol@invinet.org   Procurement
Codice     Oriol Bausà         oriol@invinet.org   Procurement
Codice     Oriol Bausà         oriol@invinet.org   Procurement

Codice     Oriol Bausà         oriol@invinet.org   Procurement

Codice     Oriol Bausà         oriol@invinet.org   Procurement

Codice     Oriol Bausà         oriol@invinet.org   Procurement



Codice     Oriol Bausà         oriol@invinet.org   Procurement

Codice     Oriol Bausà         oriol@invinet.org   Procurement

Codice     Oriol Bausà         oriol@invinet.org   Procurement

Codice     Oriol Bausà         oriol@invinet.org   Procurement


Codice     Oriol Bausà         oriol@invinet.org   Procurement

Codice     Oriol Bausà         oriol@invinet.org   Procurement

Codice     Oriol Bausà         oriol@invinet.org   Procurement
Codice     Oriol Bausà         oriol@invinet.org   Procurement
Codice     Oriol Bausà         oriol@invinet.org   Procurement

Codice     Oriol Bausà         oriol@invinet.org   Procurement
Codice     Oriol Bausà         oriol@invinet.org   Procurement

Codice     Oriol Bausà         oriol@invinet.org   Procurement



Codice     Oriol Bausà         oriol@invinet.org   Procurement
Codice     Oriol Bausà         oriol@invinet.org   Procurement

Codice     Oriol Bausà         oriol@invinet.org   Procurement
Codice     Oriol Bausà         oriol@invinet.org   Procurement
Codice     Oriol Bausà         oriol@invinet.org   Procurement




                                             Side 259
                                    New ABIEs


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement




iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement




iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement



                                      Side 260
                                     New ABIEs


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


iSURF   Yildiray Kabak   yildiray@srdc.com.tr Procurement


eBiz    Arianna Brutti                        M
                         arianna.brutti@enea.it arketing & sales


eBiz    Arianna Brutti                        M
                         arianna.brutti@enea.it arketing & sales



eBiz    Arianna Brutti                        M
                         arianna.brutti@enea.it arketing & sales




eBiz    Arianna Brutti                        M
                         arianna.brutti@enea.it arketing & sales




eBiz    Arianna Brutti                        M
                         arianna.brutti@enea.it arketing & sales




                                       Side 261
                                        New ABIEs
Collaboration   Proposed ABIE name




Billing         Utility Specification




Billing         Chargeable Consumption

Billing         Consumption Point
Billing         Meter
Billing         Meter Reading




                Chargeable Consumption
Billing         Line
Billing         Utility Item

Billing         Unstructured Price

Billing         Consumption Report
                Consumption Report
Billing         Reference
                Development In
Billing         Consumption
Billing         On Account Payment
Billing         Energy Tax




Billing         Consumption Average

Billing         Correction



                                         Side 262
                                  New ABIEs

Billing     Extended Specification


Billing     Tele Specification Line
Billing     Call

Billing     Duty

Tendering   Qualification Resolution
            Capability
Tendering
Tendering   Requirement
Tendering   Tendering Terms
Tendering   Appeal Terms

Tendering   Awarding Criteria

Tendering   Evaluation Criteria

Tendering   Tender Qualification



Tendering   Request for Tender Line

Tendering   Event

Tendering   Completed Task

Tendering   Contract Prolongation


Tendering   Required Guarantee

Tendering   Framework Agreement

Tendering   Award Justification
Tendering   Tenderer Party
Tendering   Tender Line

Tendering   Short List
Tendering   Motivation

Tendering   Procurement Project



Tendering   Business Profile
Tendering   Power of Attorney

Tendering   Tendering Process
Tendering   Tender Result
Tendering   Subcontract Terms




                                   Side 263
                                               New ABIEs
Collaborative Planning,   ActivityDataItem
Forecasting and
Replenishment
Collaborative Planning,   DataItem
Forecasting and
Replenishment
Collaborative Planning,   EventComment
Forecasting and
Replenishment
Collaborative Planning,   EventLineItem
Forecasting and
Replenishment
Collaborative Planning,   EventTactic
Forecasting and
Replenishment
Collaborative Planning,   EventTacticEnumeration
Forecasting and
Replenishment
Collaborative Planning,   ExceptionCriterion
Forecasting and
Replenishment
Collaborative Planning,   ExceptionNotificationDataIte
Forecasting and           m
Replenishment
Collaborative Planning,   ForecastAccuracyException
Forecasting and
Replenishment
                          ForecastAccuracyException
                          Criterion
Collaborative Planning,
Forecasting and
Replenishment
Collaborative Planning,   ForecastComparisonExcepti
Forecasting and           on
Replenishment
                          ForecastComparisonExcepti
                          onCriterion
Collaborative Planning,
Forecasting and
Replenishment
Collaborative Planning,   Impact
Forecasting and
Replenishment
Collaborative Planning,   InformationRequestTradeIte
Forecasting and           m
Replenishment
Collaborative Planning,   ItemManagementProfile
Forecasting and
Replenishment
Collaborative Planning,   MiscellaneousEvent
Forecasting and
Replenishment
Collaborative Planning,   PerformanceDataItem
Forecasting and
Replenishment



                                                Side 264
                                             New ABIEs
Collaborative Planning,   RetailPlannedImpact
Forecasting and
Replenishment
Collaborative Planning,   PromotionalEvent
Forecasting and
Replenishment
Collaborative Planning,   PromotionalEventLineItem
Forecasting and
Replenishment
Collaborative Planning,   PromotionalSpecification
Forecasting and
Replenishment
Collaborative Planning,   RevisionDataItem
Forecasting and
Replenishment
Collaborative Planning,   TradeItem
Forecasting and
Replenishment


                          InstructionForReturnsLine
Vendor managed inventory (VMI)


                           InventoryMovementLine
Cyclic replenishment program (CRP), Vendor managed inventory (VMI)



                           InventoryReportLine
Cyclic replenishment program (CRP)




                           SalesItem
Cyclic replenishment program (CRP), Classical preorder, Vendor managed inventory (VMI)




                           SalesReportLine
Cyclic replenishment program (CRP), Classical preorder, Vendor managed inventory (VMI)




                                                 Side 265
                                                New ABIEs
Definition                                                PSC Proposed ABIE Name   Reuse
UtilitySpecification is the root-element for the
document "OIOUBL UtilitySpecification (UTS)".
UTS is a kind of attachment document used for
specifying the extended informations needed by the
Utility sector in addition to a standard invoice.
UTS is therefore a supplement to an OIOUBL Invoice
or CreditNote.
UTS is issued as a selfcontained OIOUBL document
using af dedicated OIOUBL profile.
UTS is build to comply with the Danish Legal
requirements for the utility sector.
UTS is a replacement for the eailier OIOXML FSV
specification used within Denmark.

This class contain the specification for the
consumptionpoint. Is there a need for specify more
than one consumptionpoint, then use one
UtilityChargeableConsumption for each
consumptionpoint, so you have several instance of
UtilityChargeableConsumption. This could for exampel
be a big company, there have severals branches.
Content information about UtilityConsumptionPoint
and about metering
Information about Meter(s) and meteringdata
Readings of the meterstand on the current meter

Specification of óne product. If you need to specifier
more than one product, you must specifier one
ChargeableConsumptionLine for each product. This
could for exampel be necesarry if the customer have
to pay both for the cables and the internet connection.
Informations about a product of consumption
This class is a alternative to the class Price, and it
contain a Tele line
Staticstisc about the consumers consumption and the
development in comsumption.
Informations about ealiere reports, for exampel last
years consumption

Informations about the consumption developement.
The coming planned a conto payments
Informations about specific enery tax and duties.
The Average price included VAT.
This clas are suplementary utility specifications, that
depending of type of Utility and scenario, needs to be
present on a UtilitySpecification, in order to meet the
legal requirement and/or to give the Buyer proper
informations. Note that these suplementary
specifications are related to one common
ConsumptionPoint as specified in
UtilityChargeableConsumption/ConsumptionPoint
above.
The specification of correction, for examples heating
correction.



                                                  Side 266
                                                  New ABIEs

The class contain the detailed / extended specification.
This class contain a tele specifikation on line level.
Here you can make up unitprice /itemprice related
each service.
Informations about each call
Specification of duties - both call duties and time
duties.
The result of economic operator evaluation in this
tendering process, such as accepted or rejected.
Criteria that should be required to a tenderer in order
to evaluate its capacity.
An action or statement that is imperative
General tendering terms for this tendering process
Information about the terms to present an appeal.
Criteria that should be required in order to evaluate a
party capacity.
Criteria that should be required to a tenderer in order
to evaluate its capacity.
The evaluation that the Contracting Authority party
requests to fulfill to the tenderers.
The goods or the service which is the subject to be
procured in the tendering process. 16FEB06 - Specific
goods or services expected to be delivered in this
tendering process.
A significant occurrence or happening related to an
object process, or person.
Completion of a mental or physical effort to a specific
purpose in the tendering process.
Information about the possible extensions of a
contract.
The Information about the bond guarantee of a tender
or bid submitter to actually enter into a contract if they
are the successful bidder.
The information about a tendering framework
agreement.
Information needed to justify certain tendering
processes
Information about a tenderer.
Reference to a line on a document
Information about the creation of a short list for a
tendering process
Information about the motivation for an action.
An endeavour carefully planned to achieve a
procurement of goods, works and service.

Distinctive features or characteristics required for a
business in the tendering process such as number of
employees, number of operating units, business type.
Information about the power of attorney.
The process of a formal offer and response to execute
work or supply goods at a stated price.
The result of the bid opening in the tendering process
Information about the subcontract of a contract.




                                                   Side 267
                                                 New ABIEs
This class links a Time Period, Measurement for the
quantity involved, and to Collaborative Trade Item for
the required product.
A forecast data item


This information on EventComment for RetailEvent


Information about an Event Line item


Information about an event tactic.


Information about an event tactic aggregate of
enumerated valued aggregates.

Exception Criterion define the threshold for variances,
beyond which an exception message should be
triggered.
A Exception Notification data item


This class identifies the exception as a Forecast
Accuracy Exception

Establishes the criterion for one of the three types of
exceptions. This class provides criteria for the kind of
Forecast exception, the identification of the purpose of
the Forecast, the source of data and the time basis
criteria for the exception.
This class identifies the exception as a Forecast
accuracy exception

Establishes the criterion for one of the three types of
exceptions. This class provides criteria for the kind of
forecast exception, the identification of the purpose of
the forecast, the source of data and the time basis
criteria for the exception.
This class links the event impact code list to the
threshold values used to measure the actual impact or
planned impact.
A request to trading partner for item information.


CPFR profile for one or many items in the item
location profile

Information on MiscellenaousEvent for RetailEvent


A Performance History data item




                                                    Side 268
                                                  New ABIEs
Effect of the discrete activity affecting supply or
demand in the supply chain (eg. Promotion, inventory
policy change)
This information on promotional event for RetailEvent


This information on line item in a promotional event for
RetailEvent

A specification for a promotion


Information about a forecast revision data item


Information about a trade item


Information about an Instruction For Returns Line. It
should contain information about the item and the
quantity that have to be returned
Information about an Inventory Movement Line. It
should contain information about the item and the
moved quantity.
Information about an Inventory Report Line. It should
contain information about the item, the quantity that is
currently on stock and the amount of the stock
quantity.
Information about quantity and prices related to the
sales of a certain item. The prices should be: the
effective sales price exclusive of taxes, the regular
price exclusive of taxes, the effective sales price
inclusive of taxes and the regular price inclusive of
taxes.
Information about a Sales Report Line. It should
contain the sales date, information about the place
where the goods are been sold (sales location) and
information about quantity and prices related to the
sales of a certain item (SalesItem).




                                                   Side 269
                   New ABIEs
Comment   Status




                    Side 270

								
To top