Re: SV: [ubl] Use of LineStatusCode

[Mark Leitch <ml@tritorr.com>]

Title: Re: SV: [ubl] Use of LineStatusCode

Stephen

As per my previous email, many of the changes we have made have been to correct previous errors e.g.

• copying and pasting of elements from documents where they are relevant others where they are not
• transference of elements from documents to their proper place in the procurement library
• transference of elements from documents and the procurement library to their proper place in the common library.
  

Many of these, I think, come from misunderstandings of the OGC model and of the joint OGC/IDA submission to UBL 2.0 in Hangzhou.

I am also of the opinion that the additions we have made are valuable and have been well considered by the group from business and from technical points of view.  Re. the latter, I personally have relied heavily if not entirely on the extensive knowledge of 1.0 of Tim and Peter.  Nothing has changed from 1.0 without their assessment of its technical impact.  This, I believe, is also true of the changes resulting from many days of workshops in Copenhagen.

With respect to the your final point, we have not disregarded the expensive investment to date; I hope and believe that we have improved the investment.  But as with all investments, sometimes parts of the portfolio don’t perform as well as others and, to carry on the metaphor further than it should probably go, Tim and Peter have analysed and been party to all changes.

If this approach is not correct (and, frankly, within the timescales I can’t see what alternative approach we could have taken), I need to know now;

1. because we will have to alter the 2.0 schedule and
2. I have to start managing expectations of UBL 2.0 (and any UNCEFACT implications) at OGC, particularly with Zanzibar looming.
   

Regards, Mark

Mark Leitch




> From: Stephen Green <stephen_green@bristol-city.gov.uk>
> Date: Wed, 26 Oct 2005 15:51:16 +0100
> To: <mhb@itst.dk>, <ubl@lists.oasis-open.org>
> Subject: 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
> 
> 
>