[
Lists Home |
Date Index |
Thread Index
]
UBL E-business documents are generally intended to go point-to-point
between the individual business partners (via ebXML Messaging services).
I don't think it would be at all practical to "filter" these (numerous
and voluminous) messages through a centralized Web Service.
And it's generally only the two trading partners - or a relatively small
trading community around them - who've agreed to use a particular
extension or restriction of the standard code lists. Most other folks
using UBL - or even OASIS or UN/CEFACT, the UBL standards people -
would probably remain blissfully unaware of any new currency codes, say.
Bosak's example entailed the hypothetical FQD (Free Iraqi Dollar[sic]);
forget for the moment that even if the "free" Iraqi Dollar (or Dinar)
ever were to see its way into existence, ISO 4317 would require the
first two characters of the currency code match the ISO 3166 code of
the country issuing the currency (the notable exception being the euro,
EUR), resulting in something like IQF.
Most folks in the world couldn't give a rat's ass about this new
currency and would have no need for the new code to be used or
validated. Only the two trading partners interested in such a currency
code addition would have to worry about sharing a (small) schema that
(temporarily) overrode the notion of "CurrencyCodeContentType"
transparently allowing the addition of "FQD" to all the existing ISO
4217 codes in the current "off-the-shelf" OASIS UBL CurrencyCode-1.0
schema.
William J. Kammerer
Novannet
Columbus, OH 43221-3859 . USA
+1 (614) 487-0320
----- Original Message -----
From: "Chiusano Joseph" <chiusano_joseph@bah.com>
To: "William J. Kammerer" <wkammerer@novannet.com>; "XML Developers
List" <xml-dev@lists.xml.org>
Sent: Sunday, 06 March, 2005 01:08 PM
Subject: RE: [xml-dev] Is there a way to reuse and extend an enumeration
in XML schema
Is there some way that a Web service (REST or SOAP-based) could be
available through which all UBL instances could be "filtered" - assuming
that the UBL schema that they need to conform to were listed in the
"schemaLocation" attribute at the top of the instance document - that
would "trick" the instance document into being validated against a
broader list of codes than that which is represented in the UBL schema?
So if the instance document were to include a code that was not listed
in the UBL schema as an enumeration - but would really be an extension
of such an enumeration - the remote processing could take care of it?
Let's assume for our purposes - totally hypothetically - that the Web
service would be hosted by OASIS, and the code list extensions would be
maintained and available through that Web service. Is that wacky?
Kind Regards,
Joseph Chiusano
Booz Allen Hamilton
Strategy and Technology Consultants to the World
----- Original Message -----
From: "William J. Kammerer" <wkammerer@novannet.com>
To: "XML Developers List" <xml-dev@lists.xml.org>
Sent: Sunday, 06 March, 2005 12:30 PM
Subject: Re: [xml-dev] Is there a way to reuse and extend an enumeration
in XML schema
I can't speak to Kenneth Stephen's requirements, but I'm pretty sure
that UBL wants to give users some way of extending (and restricting)
currency codes (inter alia) without modifying any of the distributed UBL
schemas. If such a "feature" requires use of "substitutionGroup," then
UBL will consider adding the appropriate infrastructure to the
"off-the-shelf" schemas for code lists (e.g., abstract="true"). See
§4.6, Code List Schema Usage, in Universal Business Language (UBL) Code
List Representation (Version: 1.1 draft 17 January 2005), at
http://lists.oasis-open.org/archives/ubl-dev/200502/pdf00000.pdf.
The UBL schema structure is indeed modular, and business document and
core component schemas do reference a separate schema for code lists.
See the OASIS Universal Business Language 1.0 page at
http://docs.oasis-open.org/ubl/cd-UBL-1.0/. §6.3 UBL Code List Schemas
include not only ISO 4217 currency codes, but also "pre-packaged" code
lists for others like the ISO 3166 Country codes. More will follow, and
it is a commonly perceived requirement among e-business folks that they
will just die if the standard code lists can't be extended to
accommodate their special business needs.
You or anyone else who could proffer an elegant solution to the code
list extensibility conundrum would be hailed as a hero in the annals of
UBL. John Bosak, chair of the OASIS UBL TC, originally requested help
on the ubl-dev mailing list, with subsequent follow-up on the "Code list
extensibility and substitution groups" and " Code list use case"
threads.
See http://lists.oasis-open.org/archives/ubl-dev/200502/msg00006.html
and http://lists.oasis-open.org/archives/ubl-dev/200503/msg00014.html.
William J. Kammerer
Novannet
Columbus, OH 43221-3859 . USA
+1 (614) 487-0320
|
