[
Lists Home |
Date Index |
Thread Index
]
[Cross-posting to OASIS/ebXML Registry TC listserv as an FYI]
Rich,
There is no single proposal for what you refer to, but rather a series
of interrelated specifications that, when taken together, comprise the
equivalent of a single proposal.
Here are the pieces:
- ISO/IEC 11179 Standard
- UN/CEFACT ebXML Core Components
- OASIS/ebXML Registry
The ISO/IEC 11179 Standard Part 5, "Naming and identification principles
for data elements", defines a standard methodology for naming data
elements.
The UN/CEFACT ebXML Core Components specification [1] "seeks to define a
flexible and interoperable way of standardizing Business Semantics".
This specification leverages the ISO/IEC 11179 standard Part 5 for its
data element naming principles. The specification is currently in the
United Nations Open Development Process Step 6 (Implementation
Verification), which is one of the later stages of approval.
The OASIS/ebXML Registry specification [2] defines, beyond its "base"
specification of an XML registry, capabilites for distributed
registries. I have been heading up the effort within the Registry TC for
the past year to implement the UN/CEFACT ebXML Core Components
specification in the Registry architecture. Once that is done, Core
Components will be able to be represented in an ebXML Registry.
Bottom line: This will enable distributed authorities (through the
distributed registries capability of ebXML Registry) to create and
maintain data element names (through Core Components, and the ISO/IEC
11179 standard Part 5) - thus enhancing interoperability.
Stay tuned...good things to come...
Kind Regards,
Joe Chiusano
Booz | Allen | Hamilton
[1] http://xml.coverpages.org/ni2002-12-19-a.html
[2] http://www.oasis-open.org/committees/regrep/
Rich Salz wrote:
>
> > If you're going to report an element and its attributes and attribute
> > values as separate events, it means jumping back and forth.
>
> When I feed C++ to my C parser, it doesn't work too well. :)
> XML requires you to look ahead to the end of the start-element.
> Yes this makes some parsing models harder to implement, and some easier.
>
> Has anyone come up with an alternate proposal that allows you to mix
> and match a document with elements that come from distributed creators?
> I don't recall seeing one go by on the list. If I missed it, please
> respost the URL. It seems to me that without distributed authority to
> create names, XML is NIXML, non-interoperable.
> /r$
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
begin:vcard
n:Chiusano;Joseph
tel;work:(703) 902-6923
x-mozilla-html:FALSE
url:www.bah.com
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
version:2.1
email;internet:chiusano_joseph@bah.com
title:Senior Consultant
fn:Joseph M. Chiusano
end:vcard
|
