URIs now supported by ebXML Core Component Type library
- At its Seattle meeting last week, the Core Components workgroup of the
UN/CEFACT ebTWG approved the addition of two new attributes to the Identifier
type within the Core Components Technical Specification (CCTS).
Here was the CCTS Draft Jan 25th
Here was the issue.
The Core Component Types (CCTs) are a foundation of ebXML Core
Components that will likely be coded, and optimized, within high-
performance business collaboration software. Count on it. Web
services developers *will* be able to interact directly with
full-sized, enterprise implementations of ebXML if they implement
these types correctly. You can define *very* simple messages and
message choreography suitable for hand-held devices, and implement
your end in low-level code. The transactions will be globally
unambiguous without requiring *any* proprietary gateway.
Until version 1.8 of the CCTS, the Identifier.Type lacked a mechanism
for globally disambiguating and addressing, besides
"Identification.Scheme.Name", and "Identification Scheme.Agency". These
assume both parties already agree on Identification Schemes, i.e. a
controlled universe of providers of Identification Schemes with a
central namespace controller someplace. Until last week, that
namespace controller could only have been the UN/CEFACT of course.
The definition of Identifier. Type is as follows,
A character string to identify and distinguish uniquely, one instance
of an object in an identification scheme from all other objects
within the same scheme together with relevant supplementary
The previous Children elements of Identifier Type since mid-2000 have
been the following:
Identifier. Content (000102)
Identification Scheme. Name (000103)
Identification Scheme Agency. Name (000104)
Language. Code (000075)
Now you have two additional Children elements:
Identification Scheme. Unique Resource Identifier
Identification Scheme. Data. Unique Resource Identifier
Version 1.8 of the CCTS will appear this week, on the ebTWG list
I was worried about this because I am an accountant. General Ledgers and
AR/AP systems use Identifiers ubiquitously for thing such as party,
product, employee, etc. as well as charts of accounts, organization,
etc. There are internal namespaces, trading parties' namespaces as well
as public "Agency" namespaces. The need for general- purpose lists is
fundamental to the requirements of accounting software, and I am
very excited by this new URI support. It allows internal software to
use the same data dictionary as the external B2B vocabularies.
RFC 2396 URI addressing, with query component, can represent an object
in local or network applications, filesystems, SQL databases, etc. as
well as the usual SMTP, HTTP, etc. http://www.ietf.org/rfc/rfc2396.txt
These new URI's may allow people to use registries and directories for
people, companies, products, organizational units, etc. that do not
exist in value domains of the "Agencies" in the UN/CEFACT "Scheme
Agency. Name" namespace.
It also allows applications to point at an electronic transaction
on any visible location, using Identifier. Type. That is huge. We
are talking about a major pandora's box here! ebXML reliable messaging
provides the secure transport, signing and non-repudiation. We always
know this is the true solution for Peer to Peer commerce. There is
no place in the world, for two separate architectures of P2P commerce.
The autonomy, power and privacy that is built for the Global 100 ought
to be good enough for reasonable small businesses on the street and
indeed, that is all you're likely to get, so, let's wake up and use it!
The support for private, unregistered value domains exists within
smaller collaborations and trading communities who don't disclose their
"Schemes" to the public visibility, by registering as an "Agency" in
Brussels or Washington DC, etc. Companies sometimes use their own
product Ids on interactive web services with trading partners. This
usage is part of the problem domain of EBTWG and semantic support should
not be omitted.
There are issues of privacy, as well as fair access to markets of
suppliers and distribution. Users need the flexibility to select their
own providers of list information, and these metadata are necessary for
internal integration (A2A) such as transaction journals as well as B2B
Private value domains for Identifiers are essential in A2A integration;
any internal value domains such as charts of accounts, budget or
organization units, etc.
Todd Boyle CPA 9745-128th Ave NE Kirkland WA
International Accounting Services, LLC www.gldialtone.com