OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tax message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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


This is a good question. I will ask Stephen Green.  

GEFEG's position about SBS is that it is an implementation guide, not a
standard. We provide support for the full UBL standard with capability to
create trading partner specific guidelines.

I am attaching additional background on the SBS profiles.


-----Original Message-----
From: Walter Hamscher [mailto:walter@hamscher.com] 
Sent: Monday, August 01, 2005 7:59 AM
To: tax@lists.oasis-open.org
Subject: RE: [tax] FW: [ubl] SBSC items: Re: [ubl] Agenda for Pacific UBL TC
call 11|12 July 2005

Thanks for this Sylvia - Sorry for being dense here but I have to admit it
raises more questions for me - 3 minutes inspection reveals that for a small
business, Postbox isn't included in the data model... Nor timezoneoffset...
Nor Tax Category... Can someone interpret for me does this really mean that
a vendor product that says it 'supports SBS' is actually going to prevent
the use of these fields?

Walter Hamscher | www.hamscher.com | Vice Chair, XBRL International |
Consultant to PricewaterhouseCoopers

-----Original Message-----
From: Sylvia Webb [mailto:swebb@gefeg.com]
Sent: Monday, August 01, 2005 8:19 AM
To: tax@lists.oasis-open.org
Subject: [tax] FW: [ubl] SBSC items: Re: [ubl] Agenda for Pacific UBL TC
call 11|12 July 2005


Please read my questions to Stephen at the bottom of this email first, then
read his response. Stephen is Chair of the SBS subcommittee.


-----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

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>;
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
> 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
> 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
> 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.
> >
> > 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
> >    #############################################
> >    U.S. domestic toll-free number: (866)839-8145
> >    Int. access/caller paid number: (865)524-6352
> >    Access code: 5705229
> >    #############################################
> >
> >
> >    Additions to the calendar (http://ibiblio.org/bosak/ubl/calendar.htm)
> >    Liaison reports
> >    Subcommittee reports
> >    Team reports
> >    Review of Eurasia and Atlantic TC minutes
> >
> >
> >    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.
> >
> >
> >    I owe the group an update that includes all the input so far.
> >    Hopefully I will have this out to you before the call.
> >
> >
> >    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
> > at:
> > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.p
> > hp
> >
> ---------------------------------------------------------------------
> 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
> 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

--- Begin Message ---

Stephen Green and G. Ken Holman are pleased to submit the following
as a charter for the UBL Small Business SubCommittee (SBSC).
(log of changes from previous version attached)

SBSC Charter (Date: Feb 2005):

1. To liaise with small business industry and organizations responsible for 
e-commerce systems on smaller scales than those requiring the full scope of 
UBL features and functionality.

2. To rapidly develop, document and maintain a formal subset of published 
UBL deliverables as a limited scope of UBL features and functionality.

3. To foster implementations of this subset through coordination, 
guidance and responsiveness to queries, in order to test the viability of 
such UBL limitations in real-world scenarios.

4. To discover general principles for the development and selection of UBL 
facilities and for the adaptations of human interface presentations (output 
and input) of the small business subset

5. To liaise regarding the small business subset as required with other 
subcommittees in UBL

Possible deliverables:

1. Small business subset

2. Machine-processable expressions of the small business subset

3. User documentation of the small business subset

4. Principles of the development and selection of UBL facilities 
and of the adaptations of human interface presentations (output 
and input) for the small business subset

5. Catalogue of known implementations of the small business subset

Scope of work:

This committee's work is not undertaken to change any definition of UBL 
semantics or grammatical constraints expressed in the normative UBL W3C 

Through analysis of real-world requirements for small business 
users of UBL, this committee will document in both human- and 
machine-readable fashions a subset of UBL components decided to be of use 
in the transactions characterized by such users.

At no time will instances conforming to this subset of UBL ever not 
conform to the complete version of UBL from which the subset is derived.

Manner and schedule of work:

The work of the subcommittee will be primarily through a mail list set up 
on OASIS for subcommittee work. Access by the public will be through an 
openly available mail list archive.

A library of intermediate work materials (links, files, meeting minutes, 
examples, etc.) will be maintained through the subcommittee web site and 
will be open for public access.

The pace of development will attempt to keep up with the release of new 
UBL document models and input from the user community.

Teleconferences will be scheduled on a regular basis (perhaps as often as 
every week or two) using the standard teleconference line.

Many thanks.

Stephen Green


To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/ubl/members/leave_workgroup.php.
--- End Message ---
--- Begin Message ---

UBL 1.0 Small Business Subset

version 0.5

[The message provides a single reference for published
artefacts for UBL 1.0 SBS 0.5]

The subset leads to instances compliant with the
UBL 1.0 cd (specification) Schemas so XSD Schemas
are, in this subset version, not part of its specification.
In other words, no new namespaces are defined.

Subset Definition Files

The subset is comprised of elements and attributes listed
by their XPath addresses in files posted at the following

zip: http://lists.oasis-open.org/archives/ubl-hisc/200501/bin00000.bin
(file may be downloaded, saved and renamed with extension .zip
before opening as a zipped file)

The covering message for this distribution is found at:

Example / Template Files

The following sets of examples of filled and empty 
UBL 1.0 SBS 0.5 compliant documents are available:

Examples with local filename Schema locations:

zip: http://lists.oasis-open.org/archives/ubl-dev/200501/zip00000.zip

Examples with full persistent UBL urls for Schema locations:

zip: http://lists.oasis-open.org/archives/ubl-dev/200501/zip00003.zip

Note: the urls of the latter files point to the fully documented Schemas
of UBL 1.0

The subset example files do not indicate where elements
are repeatable and for this references should be made to
the UBL 1.0 specification and Schemas. No cardinalities
are resticted in UBL 1.0 SBS 0.5


The subset was modelled by Stephen Green based on both
the original development of UBL up to version 1.0 and with
special reference to the e-procurement model of the HM UK
Government Office of Government Commerce 

The subset was temporarily defined in XSD using XML Spy (2005)
courtesy of Altova (UBL TC licence), MS WordPad and the UBLish tool (see

The XPath subset definition were generated by G.Ken Holman
from the intermediary Schemas.

UBLish Tool:

Name:            UBLish
Version:         v1.0.10
Official Title:  UBLish v1.0.10
Owner Company:   SoftML
Brief Functions: UBL Schema generation, customized schema generation,
                 spreadsheet-schema conversion, schema element/type
Logo URL:        http://softml.net/jedi/ubl/sw/UBLish/UBLish-Logo.gif 
Requires:        XPS v3.4p or above (from SoftML, http://SoftML.Net/xps)
Platform:        Microsoft Windows 2000, XP Pro, XP, 98
Usage Terms:     No usage charge.  Refer to UBLish terms for details.
                 XPS integration engine licensed separately.  
Download URL:
Page content:    Download, XPS, Installation, Feature Movie


--- End Message ---
--- Begin Message ---

My personal view of the UBL SmallBusinessSubset:

UBL 1.0's Small Business Subset (SBS) now in development at version 0.5
results in a radical (up to 99%!) reduction in the number of overall
and attributes to support (though of course there is much repetition of
the underlying common structures in the full UBL documents). The subset
starts to guide a developer of the type of application used by a small
(perhaps from a sophisticated spreadsheet to a typical finance application)
into what elements and attributes and their structures to support as a 
minimal yet acceptable implementation of UBL. It seeks to establish some
commonality across such applications, necessary for certain types of
electronic trading, by giving the opportunity for applications to conform to
an agreed subset appropriate to their needs. The acceptance of this kind
of UBL support from the wider UBL developer community may result in
applications for larger businesses being designed to better cater for the
limitations small business applications may face. Besides this, there may be
scope, hopefully, for ebXML CPPs/CPAs and related standards to specify the
requirement to use a subset such the SmallBusinessSubset in trading

One outcome of the subset's development is the ability to provide designed
example instances, either as empty templates or as filled examples to aid
a user in producing a valid UBL document.

The attached zipped file contains sets of such instances which comply with
the 0.5 version of the Small Business Subset. Note: there is no difference
the namespaces of the subset example instance from a UBL-proper instance.

Compliance, as presently proposed, allows further elements from UBL to be
included in a document but with the understanding that a similarly compliant
receiving application MAY ignore such elements which are not included in
the subset. On the other hand, elements which the subset does include
SHOULD NOT be ignored unless the application has good reason to do so.
These rules should provide a certain degree of confidence that a UBL message
will be understood even by a low-end conformant application. Some sort
of exception handling could be built into applications to detect
elements and present these visually for a user to make necessary decisions.

Just how well the existing subset can meet the above function remains to be
judged but efforts have been made to conform to models developed for
such purposes as well as the historical benefit of years of development
gone into the existing set of UBL documents from which the subset is

It would be good to receive comment from domain 'experts' on the content 
of the attached documents and their appropriateness for small businesses. 
Thank you.


Stephen Green


>>> "G. Ken Holman" <gkholman@CraneSoftwrights.com> 25/01/05 14:21:01 >>>
Good day, all,

I've just posted a revision to the proposed Universal Business Language 1.0 
Small Business Subset 0.5 XPath files:


Public comments and feedback are welcome ... please use this mail list to 
offer your input.

................. Ken

World-wide on-site corporate, govt. & user group XML/XSL training.
G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com 
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/u/ 
Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
Male Breast Cancer Awareness  http://www.CraneSoftwrights.com/u/bc 
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal 


--- End Message ---
--- Begin Message ---
Greetings UBL-Dev Folks,

Just to inform that there has been progress with the subset
perviously known as UBL Lite. It will have a full set of UBL
documents (one missing at present is Order Change but
hopefully to be remedied soon) and a new means of 
definition as well as a new name.

The new name is to be UBL 1.0 Small Business Subset (plus
subset version number). An abbreviation would be UBL SBS 
but if other subsets follow there may be more need for use of 
the full name.

The new means of definition is a set of XPaths for all elements 
and attributes of each document. Version 0.4
(hopefully to become 1.0 on approval) is found at


A few changes of note are:-

Each document uses its own set of common library
components so these can be different say for an Order
as for an Invoice. This radically reduces the possible size
of each document. There are only about 120 elements
and attributes in a typical document compared with some
8 to 10,000 possibilities in a completely general UBL document.
It would mean that a set of spreadsheet subset specs would require
a separate 'Reusable' spreadsheet or table for each document
besides the document spreadsheet or table.

The Order now includes details for a credit card (or other card)
payment means.

The Invoice lines have OrderLineReference to allow for three-way
matching with Order, etc. This could be omitted since the rule
is that subset entities SHOULD NOT be ignored rather than 
MUST NOT be ignored. A reminder here that the other rule is that
entites outside the subset may be used but MAY be ignored by
the receiving application (unless agreement has been reached 
otherwise) for subset compliance. This allows reduction in the
complexity of compliance without reducing the opportunities
for adding complexity where mutual agreement allows.

The ReceiptAdvice and DespatchAdvice do add complexity
to the other documents a litlle in that they require more
line level data (which is an aspect of their normal function).
This is mainly the addition of OrderLineReference to the
Invoice since it has already to be present in the Advice
documents (and some would argue that it is an important
part of even a simple order/invoice electronic trading
process though not all small business apps support it).

There is now also minimal DeliveryTerms in the Order/OrderResponse
and minimal PaymentTerms in the Invoice.

For details of cardinality, of course, one has to refer to the
full UBL Schemas and none of the subsets alter the

Please see also 

for background on developments:



Comments welcome

All the best

Stephen Green

--- End Message ---

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]