MHonArc v2.5.0b2 -->
ubl message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: SV: [ubl] Use of LineStatusCode
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
>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]