Re: [ubl] SBSC items: Re: [ubl] Agenda for Pacific UBL TC call 11|12 July 2005

["Stephen Green" <stephen_green@seventhproject.co.uk>]

Sylvia, Tax XML TC,

[Please forward to the Tax XML TC, thanks.]

Greetings.

> The Tax XML TC has another question. If a vendor product claims that it
> 'supports SBS', does this really mean the product will actually prevent
the
> use of fields that are not included in the SBS profile like postbox, tax
> category, and timezoneoffset?
>

In short, ... no.

There are just two normative rules for the SBS:

1. Parties sending UBL documents to parties specified as receivers of a UBL
1.0 Small Business Subset (SBS) document or documents SHOULD NOT require the
same receiving party to process any part of the UBL document which is
external to the specified SBS.

2.  Parties specified as receivers of a UBL 1.0 Small Business Subset (SBS)
document or documents SHOULD ensure that their systems appropriately process
at least every document part that is specified in the SBS.


This means that anything can be added to the subset, as long as
businesses do not rely on such extra-subset data being processed
automatically in a default SBS collaboration (unless additionally
specified and/or agreed). This allows software to add to its UBL
support, beyond default SBS support, but adds caution as to what
it can reasonably expect other SBS-based software to 'understand'.

So software may support the SBS in two ways (both necessary to
claim adherance to the SBS rules):

1. in how it sends messages qualified by how it requires that
receiving software receive messages

2. in how it receives messages

To elaborate:

1.  "in how it sends messages...":  messages may include more than the
SBS ...

BUT

"...qualified by how it requires that receiving software receive messages":
provided it is accepted that, unless a trading agreement specifies otherwise
by
further qualifying subset use, anything extra to the subset such as postbox,
etc,
could be ignored by the receiving software and so anything critical to the
process should be sent (if possible) as content of those entities specified
by the SBS. It might be, for instance, that, using the example of postbox,
the
other party's software will not be able to send the 'postbox' details back
in
the addresses in return documents. One party might send an Order with
the Postbox in the Address but the other party might only be able to send
back an Invoice (or OrderResponse, etc) without Postbox in the Address.
This affects how postbox is included in the message sent: it might be OK
if the Order is not the primary source of the Address (if the other party
already has the address in their system) and can send it in back in
AddressLine.Line.

2. "in how it receives messages": UBL 1.0 SBS software in catering for
received messages only NEED cater for the entities in the SBS but MAY
cater for more (as much more as it like up to complete UBL and/or
customisations). It might be that it chooses to throw an 'exception' for
data
additional to the SBS so that this can be highlighted and the document ,
say,
extracted for human processing. This would then be, literally, 'the
exception
rather than the rule'.

I hope this is clear and helps.

All the best

Stephen Green



----- Original Message ----- 
From: "Sylvia Webb" <swebb@gefeg.com>
To: "'Stephen Green'" <stephen_green@seventhproject.co.uk>;
<ubl@lists.oasis-open.org>
Cc: <tax@lists.oasis-open.org>
Sent: Tuesday, August 02, 2005 1:43 AM
Subject: RE: [ubl] SBSC items: Re: [ubl] Agenda for Pacific UBL TC call
11|12 July 2005


> Thanks for the response Stephen.
>
> The Tax XML TC has another question. If a vendor product claims that it
> 'supports SBS', does this really mean the product will actually prevent
the
> use of fields that are not included in the SBS profile like postbox, tax
> category, and timezoneoffset?
>
> Regards,
> Sylvia
>
> -----Original Message-----
> From: Stephen Green [mailto:stephen_green@seventhproject.co.uk]
> Sent: Monday, August 01, 2005 3:46 AM
> To: ubl@lists.oasis-open.org
> Subject: Re: [ubl] SBSC items: Re: [ubl] Agenda for Pacific UBL TC call
> 11|12 July 2005
>
> Sylvia / Tax XML TC
>
> Many thanks indeed for taking some time to look at the UBL Small Business
> Subset (SBS) for the UBL 1.0 Invoice.
>
> I attach a spreadsheet file (zipped with extension changed from .zip to
> .zzz) of the full subset for UBL 1.0. This includes the subset-designated
> entities and those left out of the subset, as requested. This is actually
> the file included in the UBL 1.0 SBS committee draft package.
>
> In answer to question 2, the attached file is that produced for UBL 1.0 so
> the latest additions have limited affect. It will be a further decision,
> soon needing to be made, as to whether the Tax XML requested additions to
> UBL 2.0 should be designated as part of a UBL 2.0 SBS. I'd just point out,
> though, that because an entity isn't designated part of the SBS doesn't
mean
> it can't be included in the messages; it just means that a party declaring
> that they use the SBS are saying that, unless otherwise stated, they do
not
> guarantee that their software will automatically process such data. (It
> could, however, be added to their trading agreement that they will process
> such-and-such entities in addition to the subset and this could be stated
in
> prose or the like and added as a further reference in the ebBP or
equivalent
> documentation.)
>
> In short, what needs to be in the UBL 1.0 SBS (about to start public
review)
> and what needs to be in the future UBL 2.0 SBS are two separate matters.
> Hopefully they will be as similar as possible to maximise interoperability
> in implementations. If there is the need for * minimal * UBL 1.0 Invoice
> implementations to process certain parts of UBL 1.0 which aren't yet
> included in the SBS we need to add those to the 1.0 public review
comments.
>
> Many thanks.
>
> All the best
>
> Stephen Green
>
>
>
>
> ----- Original Message -----
> From: "Sylvia Webb" <swebb@gefeg.com>
> To: "'Stephen Green'" <stephen_green@seventhproject.co.uk>;
> <ubl@lists.oasis-open.org>
> Sent: Friday, July 29, 2005 12:13 AM
> Subject: RE: [ubl] SBSC items: Re: [ubl] Agenda for Pacific UBL TC call
> 11|12 July 2005
>
>
> > Stephen,
> >
> > The TaxXML TC met today and discussed review of the SBS Invoice
> spreadsheets
> > that you prepared. They will meet within the next two weeks to discuss
the
> > spreadsheets in detail.  They have a couple of initial questions:
> >
> > 1) How do they know what has been removed from the UBL 1.0 Invoice to
> create
> > the SBS Invoice? The spreadsheet only appears to contain the SBS subset.
> > 2) Is there a need to re-subset the SBS Invoice to align it with the
> TaxXML
> > recommendations in the Issues list?
> >
> > Thanks,
> > Sylvia
> >
> > -----Original Message-----
> > From: Stephen Green [mailto:stephen_green@seventhproject.co.uk]
> > Sent: Sunday, July 10, 2005 11:10 PM
> > To: ubl@lists.oasis-open.org
> > Subject: [ubl] SBSC items: Re: [ubl] Agenda for Pacific UBL TC call
11|12
> > July 2005
> >
> > Here, for two action items, attached are:
> >
> > 1. SBSC schedule (SBSC added items highlighted) 2. UBL 1.0 SBS Invoice
> > spreadsheets for Tax XML
> >
> > All the best
> >
> > Steve
> >
> > ----- Original Message -----
> > From: <jon.bosak@sun.com>
> > To: <ubl@lists.oasis-open.org>
> > Sent: Monday, July 11, 2005 1:28 AM
> > Subject: [ubl] Agenda for Pacific UBL TC call 11|12 July 2005
> >
> >
> > > Western hemisphere participants: note that this meeting takes
> > > place Monday evening in your time zones.
> > >
> > > AGENDA FOR PACIFIC UBL TC MEETING
> > > 00H30 - 02H30 UTC TUESDAY 12 JULY 2005
> > >    17h30 - 19h30 Mon San Francisco
> > >    20h30 - 22h30 Mon Washington
> > >    08h30 - 10h30 Tue Hong Kong, Singapore, Perth, Beijing
> > >    09h30 - 11h30 Tue Seoul, Tokyo
> > >    10h30 - 12h30 Tue Sydney
> > >    #############################################
> > >    STANDING INFORMATION FOR UBL CONFERENCE CALLS
> > >    U.S. domestic toll-free number: (866)839-8145
> > >    Int. access/caller paid number: (865)524-6352
> > >    Access code: 5705229
> > >    #############################################
> > >
> > > STANDING ITEMS
> > >
> > >    Additions to the calendar
(http://ibiblio.org/bosak/ubl/calendar.htm)
> > >    Liaison reports
> > >    Subcommittee reports
> > >    Team reports
> > >    Review of Eurasia and Atlantic TC minutes
> > >
> > > REVIEW OF ACTION ITEMS FROM LAST MEETING (28 JUNE)
> > >
> > >    PENDING ACTION: StephenG to provide an SBS timeline for the UBL
> > >    2.0 schedule.
> > >
> > >    PENDING ACTION: JonB to schedule a discussion of CCTS
> > >    compliance that will include MarkC and MichaelD.
> > >
> > >       Status: This is waiting MarkC's return from vacation.  The
> > >       question (which arose out of email) is: in what way is 1.0
> > >       not CCTS compliant, and how can we ensure that 2.0 is
> > >       compliant?  Issues include ACCs and CC types.
> > >
> > >       TimM: This may have been [or may be] overtaken by the UN/UBL
> > >       and Reusable architecture discussions; perhaps we should
> > >       constitute a CCTS Compliance Review team.
> > >
> > >       JonB: Let's pick this up when we meet again week after next.
> > >
> > >    PENDING ACTION: To schedule the preparation of spreadsheets for
> > >    Tax XML after we see the outcome of the Tax XML TC meeting this
> > >    week [the week of 27 June].
> > >
> > >    PENDING ACTION: SylviaW to produce a row on "Tax XML TC
> > >    collaboration" for inclusion in the UBL 2.0 schedule before the
> > >    Pacific call 11|12 July.
> > >
> > >    PENDING ACTION: SylviaW to find out where we stand with payment
> > >    terms and payment means, TimM to respond to Oriol.
> > >
> > > UBL 2.0 SCHEDULING
> > >
> > >    I owe the group an update that includes all the input so far.
> > >    Hopefully I will have this out to you before the call.
> > >
> > > CONTENT WORK
> > >
> > >    Further work on the issues list.
> > >
> > > Jon Bosak
> > > Chair, OASIS UBL TC
> > >
> > > ---------------------------------------------------------------------
> > > 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
> >
>
>