[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: VS: Deadline for submission of changes for UBL 2.2 Pre-Award is approaching (May 31st)
Good evening, Jan André. The UBL TC has discussed your requirement posted to the UBL Comment List by Ole Madsen. The tracking ticket for this issue is here: https://issues.oasis-open.org/browse/UBL-22?filter=12972 We have concluded that the existing UBL Application Response document is probably already suitable to meet your needs. We have interpreted your requirement to address the technical part of the document delivery. We invite you to consider its use in UBL 2.2's upcoming first public review. If you find that it cannot meet your need, you are welcome to post again to the UBL Comment List with your observations. On behalf of the committee, I thank you for your interest in UBL and for your submission through Ole. We ask you to please submit future comments to the UBL Comment list personally and not through other parties. . . . . . . . . Ken At 2016-05-13 07:08 +0000, Ole Ellerbæk Madsen wrote:
Translated by Google from Norwegian: We have had a discussion about which messages should be able to handle information when something goes wrong in an electronic filing. Trdm045: http://docs.oasis-open.org/ubl/prd2-UBL-2.1/xsd/maindoc/UBL-TenderReceipt-2.1.xsd is basically a message which is located on the business layer and can in theory be sent several times and may be used. My question is about the feedback to UBL 2.2 might include such additions to this trdm? What we may need is three new fields: 1. Treatment Status (OK, Error, Warning) (S0001 / S0002 / S0003) 2. Field of reason code example describes: a) The offer came too late (T0001). b) The offer can not be read (T0002) c) certificate is not valid (T0003) d) There is no agreement between the sender's identity and certificate (T0004) e) The missing documents (T0005) f) etc. (T ...). 3. Text field to be read by a human showing error code. Fra: Mærøe, Jan André [mailto:jan.andre.maroe@difi.no] Sendt: 13. maj 2016 08:45 Til: Ole Ellerbæk Madsen Cc: Cook, Steinar Overbeck; 'siw.meckelborg@edisys.no' Emne: SV: Deadline for submission of changes for UBL 2.2 Pre-Award is approaching (May 31st) Hei Ole Vi har hatt en diskusjon om hvilke meldinger som skal kunne håndtere informasjon når noe går galt i en elektronisk innlevering. Trdm045: <http://docs.oasis-open.org/ubl/prd2-UBL-2.1/xsd/maindoc/UBL-TenderReceipt-2.1.xsd>http://docs.oasis-open.org/ubl/prd2-UBL-2.1/xsd/maindoc/UBL-TenderReceipt-2.1.xsd er i utgangspunktet en melding som ligger på businesslaget og kan i teorien sendes flere ganger og kan eventuelt benyttes. Mitt spørsmål er om den tilbakemeldingen til UBL 2.2 kan inneholde slike tillegg til denne trdm? Det vi eventuelt trenger er 3 nye felt: * Behandlingsstatus (Ok, Feil, Advarsel) (S0001/S0002/S0003) * Felt for årsakskode som eksempel beskriver: a) Tilbudet kom for sent (T0001). b) Tilbudet kan ikke leses (T0002) c) Sertifikatet er ikke gyldig (T0003) d) Det er ikke overensstemmelse mellom avsenders identitet og sertifikatet (T0004) e) Det mangler dokumenter (T0005) f) osv. (T?.) * Tekstfelt som skal leses av et menneske som viser feilmeldingskoden. BII trdm: Fra: Ole Ellerbæk Madsen [<mailto:olema@digst.dk>mailto:olema@digst.dk] Sendt: 12. mai 2016 16:40 Til: Mærøe, Jan André <<mailto:jan.andre.maroe@difi.no>jan.andre.maroe@difi.no>; Cook, Steinar Overbeck <<mailto:SteinarOverbeck.Cook@difi.no>SteinarOverbeck.Cook@difi.no> Emne: VS: Deadline for submission of changes for UBL 2.2 Pre-Award is approaching (May 31st) Hi Steinar and Jan Do DIFI have input to UBL 2.2 please send it to me as well. Best Regards Ole Fra: <mailto:ubl-pre-award@lists.oasis-open.org>ubl-pre-award@lists.oasis-open.org [mailto:ubl-pre-award@lists.oasis-open.org] På vegne af Ole Ellerbæk Madsen Sendt: 12. maj 2016 11:40 Til: <mailto:ubl-pre-award@lists.oasis-open.org>ubl-pre-award@lists.oasis-open.org Emne: [ubl-pre-award] Deadline for submission of changes for UBL 2.2 Pre-Award is approaching (May 31st) All, As you might be aware the UBL TC is aiming to release a new version of UBL every 3 years as stated in the UBL Maintenance Governance Procedures [1] As the last release of the UBL standard (version 2.1) was published in late 2013 and the next release is targeted for late 2016 publication. Given the timelines that are needed to meet this targeted publication date, the deadline for submitting new additions to the UBL standard is set for May 31st 2016. This email is a reminder for this deadline. If you have any new addition request to UBL related to Pre-Award then please use the following procedure for submitting them to the UBL Pre-Award Subcommittee. <https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=ubl>https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=ubl Ole Madsen Chair UBL Pre-Award Procurement Subcommittee [1] <http://docs.oasis-open.org/ubl/UBL-Governance/v1.0/cn01/UBL-Governance-v1.0-cn01.html>http://docs.oasis-open.org/ubl/UBL-Governance/v1.0/cn01/UBL-Governance-v1.0-cn01.html
-- Check our site for free XML, XSLT, XSL-FO and UBL developer resources | Streaming hands-on XSLT/XPath 2 training @US$45: http://goo.gl/Dd9qBK | Crane Softwrights Ltd. _ _ _ _ _ _ http://www.CraneSoftwrights.com/o/ | G Ken Holman _ _ _ _ _ _ _ _ _ _ mailto:gkholman@CraneSoftwrights.com | Google+ blog _ _ _ _ _ http://plus.google.com/+GKenHolman-Crane/posts | Legal business disclaimers: _ _ http://www.CraneSoftwrights.com/legal | --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]