Re: [ubl-dev] Custom order information

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

Hi Frank

My suggestion would be to only customise
if really necessary and use a subset
definition to mask out what you don't need.
The subset definition need only be a list
of the XPaths of everything you wish to
specify as needed and one or two rules
to say how the list of XPaths must be used.
The UBL TC have done this with a subset
we call the Small Business Subset (SBS)
and the rules used may be relevant to you.
The customisation, if necessary (I say that
because the customisation would typically
need more maintenance than the subset list
but that is a personal opinion I suppose),
could be made first then the subset.
The SBS is still in progress for UBL 1.0
(you might even find it useful) but is nearly
through to its second public review (most
of the content and methodology/rules
content have already been reviewed and
agreed). The latest package is at
http://www.oasis-open.org/committees/download.php/15800/UBL-1-0-SBS-1-0-cd2d.zip
Customisation is likely to be a better
experience with UBL 2 though (an SBS
for UBL 2 is taking shape too), if you don't
mind the wait for it - though a public
review of the content appears to be imminent.
Much of the above is personal opinion and
I'm afraid I have to disclaim to the effect
that you only take the advice at your own risk.

All the best and good luck with UBL !

Stephen Green


----- Original Message ----- 
From: "Franck de Bruijn" <franck.de.bruijn@zonnet.nl>
To: <ubl-dev@lists.oasis-open.org>
Sent: Tuesday, January 03, 2006 7:26 PM
Subject: RE: [ubl-dev] Custom order information


> Thanks for your replies.
>
> I just started to investigate UBL and was just wondering about this
> particular issue of how to include non-standard ordering information.
> Customization of the schemas is probably then the best way to go using as
> much as possible to the already existing types as Kenneth already pointed
> out.
>
> This brings me to another question.
>
> For a new project we are going to use UBL to establish an ordering
interface
> between two parties. These parties have agreed on what information is to
be
> supplied in the order XML and also what not to supply.
>
> What's now the best approach?
> * customize the UBL schemas where:
>   - superfluous optional fields are removed
>   - some optional field are made mandatory
> * use the standard UBL schemas and execute extra validation rules upon
> receipt of the order XML?
>
> Thanks in advance,
> Franck
>
>
> ---------------------------------------------------------------------
> This publicly archived list supports open discussion on implementing the
UBL OASIS Standard. To minimize spam in the
> archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Alternately, using email: list-[un]subscribe@lists.oasis-open.org
> List archives: http://lists.oasis-open.org/archives/ubl-dev/
> Committee homepage: http://www.oasis-open.org/committees/ubl/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
> Join OASIS: http://www.oasis-open.org/join/
>