Dear
TC members
During
my review of the spreadsheets from Stephen, I found the folling issues we need
to discuss:
a) The
placements and order of the new elements. What is the order of the new
documentreferences, the new party types? Are the line items still the last in
the documents.
b)
What partytypes need to be mandatory? Is it still the buyer and seller or is it
the partytypes involved in the usecase, is it only the sender and receiver of
the documents or should they all be left optional?
c)
With the extended procurement process the sender and receiver iare no longer
always the buyer and the seller. This leaves us with a complicated business
rules to find the ID of the receiver and the sender. Some may state that theese
infomations is not relevant for other than the transporting layer, but in real
life this is not true. UBL sets no requirements to the transporting layer and at
Least in Denmark we also support transportation without header information, e.g.
via FTP. In eFaktura the routing is based on an id called BuyersReferenceId (I
my mind it should have been BuyerParty-> Id). Therefore I would like to
suggest that we put in two new BBIE, called SenderId and ReceiverId for all
documenttypes. This will make it a lot easyer to build programs to route the
messages. The reason why I suggest them as BBIE and not process instructions is
that we need to be able to reject documents without from these
fields.
Kind
regards
Peter
if it helps, my understanding is that all
entries in the procurement and common spreadsheets (and eventually also the
transportation spreadsheet)) will create one CAC and CBC schema - so i guess
that is one EDIFIX model as well.
also, please let us know what
the circular references are as they may need to be resolved.
Sylvia
Webb wrote:
Stephen,
I am having a temporary problem loading these spreadsheets into EDIFIX. The
problem is that it doesn't know if one or two data models should be created
with the Reusable and the Procurement Reusable spreadsheets. There seems to
be a circular reference. We cannot proceed any further until we get some
clarifications about what to do.
Since the Procurement Subcommittee may not be able to discuss this before
the week is over, I will request that it be placed on the Atlantic TC
meeting agenda later today.
Regards,
Sylvia
-----Original Message-----
From: Stephen Green [mailto:stephen_green@seventhproject.co.uk]
Sent: Tuesday, August 23, 2005 2:13 AM
To: ubl-psc-chair@lists.oasis-open.org
Subject: [ubl-psc-chair] Re: Request to join UBL Procurement SC Approved
Sylvia
I find I cannot upload a document to the site so in the meantime I've added
it to the main site at
http://www.oasis-open.org/apps/org/workgroup/ubl/download.php/14152/ModelSpr
eadsheets-UBL-2-0-phase-1-draft-3-20050818.zip
All the best
Steve
----- Original Message -----
From: <workgroup_mailer@lists.oasis-open.org>
To: <stephen_green@seventhproject.co.uk>
Cc: <ubl-psc-chair@lists.oasis-open.org>
Sent: Tuesday, August 23, 2005 9:10 AM
Subject: Request to join UBL Procurement SC Approved
You have been added to the roster of this group. See the OASIS TC Process
for information regarding your roles and responsbilities in Technical
Committees.
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. You may a link to this group and all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--
regards
tim mcgrath
phone: +618 93352228
postal: po box 1289 fremantle western australia 6160
DOCUMENT ENGINEERING: Analyzing and Designing Documents for Business Informatics and Web Services
http://mitpress.mit.edu/catalog/item/default.asp?sid=632C40AB-4E94-4930-A94E-22FF8CA5641F&ttype=2&tid=10476