Re: AnyType in UBL?

["Stephen Green" <stephen_green@bristol-city.gov.uk>]

Folks

It has recently been pointed out that there is a problem with the definiiton
for CompanyID in a PartyTaxScheme which says it shouldn't be used for
registration IDs. Is this the same problem? If so, it's likely to be discussed
today in the TC meeting and may be a candidate for improvement in
the next UBL release via the European Union's IDA's submission. Perhaps,
if this is the problem, one should hold off from anything hasty until it
is known how this is to be fixed (if it's agreed that it needs fixing).

I gather it is still being used for registration IDs and indeed the UBL examples
use it this way ('Joinery' Invoice example) as far as I remember. Maybe the
definition is wrong, I'm not sure.

All the best

Stephen Green


>>> "David Webber (XML)" <david@drrw.info> 18/04/05 13:40:45 >>>
Aron,

Generally "back door" features are what got EDI into trouble
because then you have unsupported extensions to the base
standard - and interoperability plunges.

OAGi have created UserAreas in their BODs to carry local
information customizations.

Sounds like you have a use case though for tax numbers that
should be considered for UBL as a whole.  This is the path
I would expect where items placed in UserAreas are then
promoted to the overall UBL schema as their broader use
becomes self evident.

DW

----- Original Message ----- 
From: "Szabó Áron" <aron@ik.bme.hu>
To: <ubl-dev@lists.oasis-open.org>
Sent: Monday, April 18, 2005 7:38 AM
Subject: Re: AnyType in UBL?


>
> Dear Members,
>
> sorry, I was not so precise. I meant a "Note" element could be inserted
into
> each element. E.g. it is now impossible to insert Hungarian Tax Number and
> Community Tax Number in one invoice (in PartyTaxScheme element), but an
> extra "Note" element could solve this problem (in PartyTaxScheme), or
there
> are also other elements that are used in invoices at companies such as
> "ordering numbers", "arrival/onset number of goods" etc. Some of these are
> present in other UBL messages (e.g. Order) but also invoices should
contain
> these information (based on company requirements).
>
> Aron
>
> ---
> Can you clarify why you would need this?
> and why would a character type field not suite?
> David
>
> ----------------------------------------------------
> Aron Szabo, M. Sc.
> Research Associate,
> Center of Information Technology
> Budapest University of Technology and Economics
>
>
>