[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: AW: SV: [ubl] Use of LineStatusCode
-----Ursprüngliche Nachricht----- Von: Michael Dill [mailto:dill@gefeg.com] Gesendet: Freitag, 28. Oktober 2005 00:05 An: ubl@lists.oasis-open.org Betreff: SV: [ubl] Use of LineStatusCode Hi Peter, indeed - i.e. admin meta data in the maintenance master of UBL: with which ID a change has been implemented; the ID refers to decision lists of accepted ChangeRequest (where details could be found) second: such a stuff is important for the maintenance agency to understand, what the reasons of a change were, especially in case of a request to change that; the lessons to do so came 15 years ago from the first, badly documented changes in EDIFACT;-), where wrong directories were released and five years later users realized that and complained;-) Michael btw: a not unknown author wrote 150 years ago: the history has some repetitions; the original first occurence is a tragedy and the repetition is a comedy. -----Ursprüngliche Nachricht----- Von: Peter Larsen Borresen [mailto:plb@itst.dk] Gesendet: Donnerstag, 27. Oktober 2005 10:14 An: ubl@lists.oasis-open.org Betreff: SV: SV: [ubl] Use of LineStatusCode Hi Stephen, all I think we have a problem, if we have elements in our schemas that not even the publisher (us, the UBL TC) knows the meaning of. There must be someone here on this list that should be able to explain the idea of having LineStatusCode on invoiceLine and DespatchLine or someone who knows somesone who knows. My job the year after we have released the standard will be to explain it to other people and I don't like the scenario telling people "well, it's there because someone placed it there for a reason we don't know". /Peter -----Oprindelig meddelelse----- Fra: Stephen Green [mailto:stephen_green@bristol-city.gov.uk] Sendt: 26. oktober 2005 16:51 Til: Mikkel Hippe Brun; ubl@lists.oasis-open.org Emne: Re: SV: [ubl] Use of LineStatusCode Mikkel, all I have a problem with this because much work has gone on to establish UBL 1.0 and we don't have all the participants in constant contact. I wouldn't want (nor I suspect would you) to have to constantly watch UBL in future to see if I need to contend for already well considered content in case it gets removed without equal consideration and as many public reviews, liaison gap analyses, pleanries, etc as it took to get it there. There are many things to consider such as customisations, etc which have to be maintained and besides, none of has all the combined knowledge involved in UBL 1.0 and it is very easy to miss something (like a BIE association where we didn't expect it). I'd have to vote against a UBL 2.0 pr release that disregarded all the expensive investment to date like that. All the best Steve >>> Mikkel Hippe Brun <mhb@itst.dk> 26/10/05 14:58:29 >>> Dear all, Regarding status codes. We have discussed the use of status codes in the Catalogue work. I have argued that status codes should be mandatory. The reason being that implementers will otherwise have to handle the situation where the status code is not present as a special case. This adds an implicit "null" value to the code-list, which is undefined. Lets help implementers whenever possible. In my opinion LineStatusCode should be removed if someone cannot come up with a good explanation and business case for its use. - Regards Mikkel > -----Oprindelig meddelelse----- > Fra: Peter Larsen Borresen > Sendt: 26. oktober 2005 15:04 > Til: 'ubl@lists.oasis-open.org' > Emne: [ubl] Use of LineStatusCode > > > Dear TC members > > I have understood the use of LineStatusCode as a code to understand > whether the line is original, has been copied or updated. > > Can anyone explain to me why we have LineStatusCode in invoice line > documents and despatch line? These are not surposed to be updated. > > Kind regards > > Peter > > --------------------------------------------------------------------- > 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_workgr > oups.php > --------------------------------------------------------------------- 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 --------------------------------------------------------------------- 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 --------------------------------------------------------------------- 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]