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

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   RE: [xml-dev] UBL

[ Lists Home | Date Index | Thread Index ]
  • To: <xml-dev@lists.xml.org>
  • Subject: RE: [xml-dev] UBL
  • From: "Chiusano Joseph" <chiusano_joseph@bah.com>
  • Date: Fri, 17 Mar 2006 16:55:14 -0500
  • Thread-index: AcZKDK0mMA+/5yisQ0y3ZmfepxaLnwAADl5w
  • Thread-topic: [xml-dev] UBL

A few clarifications:
 
"The US Federal government, e.g., has come up with their own NDR based upon the UBL NDR."
 
I know that the current effort for the US federal government's NDR is influenced by the UBL NDR, as well as others. However, it is certainly not "based up" the UBL NDR.
 
"since the ebXML schema are not themselves UBL NDR compliant"
 
Not sure what you mean by "ebXML schema", as ebXML has never included an XML vocabulary (i.e. for defining a message payload) as part of its framework. Some of the various parts of the ebXML framework themselves (e.g. ebXML Registry) have XML schemas, but there is no reason that they should be UBL NDR compliant.
 
Joe
 
Joseph Chiusano
Associate
Booz Allen Hamilton
 
700 13th St. NW, Suite 1100
Washington, DC 20005
O: 202-508-6514 
C: 202-251-0731
Visit us online@ http://www.boozallen.com
 


From: Dave Scott [mailto:dms@haplos.com]
Sent: Friday, March 17, 2006 4:48 PM
To: xml-dev@lists.xml.org
Subject: Re: [xml-dev] UBL

On Mar 17, 2006, at 8:56 AM, G. Ken Holman wrote:
I hope this helps.

This does help -- particularly the references to DSDL.  If the schema our workgroup develops must strictly follow the rules laid out in the Naming and Design Rules document, those of us who feel we really need these attributes can draft a document detailing how to layer them on top of the official schema using the techniques described there.

I'm not sure what you mean by a "custom" attribute.

I meant a "user defined attribute".  Rule ATD1 in the spec says

User defined attributes SHOULD NOT be used. When used, user defined attributes MUST only convey CCT:SupplementaryComponent information. 

This effectively prohibits any attribute definitions from an NDR compliant schema except for CCTS metadata.

I'm confronted with this issue on this particular work group.   In our organization, there is a follow the leader attitude regarding the UBL NDR.  But our organization is not alone in taking the NDR as a guiding document.  The US Federal government, e.g., has come up with their own NDR based upon the UBL NDR.  As XML practitioners, I think we're likely to find the UBL NDR a very influential document outside of UBL itself.  (As the paradigm implementation of CCTS, it's having a big influence in the ebXML world too -- which is ironic, since the ebXML schema are not themselves UBL NDR compliant.)  I guess that is why I feel this is a question for the XML community at large not just the UBL community.

Dave


On Mar 17, 2006, at 8:56 AM, G. Ken Holman wrote:

At 2006-03-16 21:46 -0600, Dave Scott wrote:
I was curious about opinions and experiences people on the list might
have regarding the UBL NDR:

-  Am I alone in finding it too be overly draconian?

The "Garden of Eden" approach to UBL declarations have allowed me to mechanically analyze the schema expressions using XSLT that I think would have otherwise not been possible (thankfully, I didn't have to try to do it otherwise).

-  What practical limitations (particularly processing limitations)
have you encountered when implementing the standard?

How often is processing impacted by schema constraint expressions?

Perhaps my biggest problem with the NDR  is the prohibition against
custom attributes.

I'm not sure what you mean by a "custom" attribute.  If you mean attributes from a foreign namespace, then a combination of ISO/IEC 19757-3 Schematron (to test the presence of the attribute) with ISO/IEC 19757-4 NVDL (to test the validity of the attribute and the validity of UBL without the attribute), perhaps even (optionally) in combination with ISO/IEC 19757-2 RELAX-NG (to express the constraints of the attribute) would seem to me to do the trick.

All without needing any blessing or accommodation by the UBL committee since this is all totally orthogonal to the UBL schema expressions.

I'm contributing to a workgroup to develop a data
standard which will be used to transmit potentially huge data sets.
Understandably, we'd like the standard to be friendly to stream
processing.  The ability to add "type" and "role" attributes in key
places in the schema would greatly aid processing the data in a way
that would only require examining the current element stack during
stream processing for our most typical use cases.

Sounds good.

The UBL proponents
on the workgroup propose requiring such items to be a first child
(rather than attribute) of the node they qualify so as to act as a
processing flag for its siblings and siblings' children.

Yuck ... I would far prefer flagging such as attributes.  Of course if the information you need to include is structured you would have to use elements.

Also, I believe you shouldn't  add
ordering constraints to your schema, burdening both the production
and validation of the data set, unless there is a semantic
motivation.

Indeed.

A couple of key individuals on the workgroup are adamant about
adhering to the UBL NDR (although not very articulate when it comes
to justifying either the individual requirements of the NDR or the
blanket decision to follow it slavishly.)

Fine ... you can (and I believe *should*) leave the UBL schema expressions created by the NBR untouched and sacrosanct.  Layer your requirements on top of a read-only schema expression using ISO/IEC 19757 DSDL http://dsdl.org parts.

Unfortunately, the
literature I've been able to turn up regarding the UBL NDR all reads
like marketing literature rather than frank evaluations of the trade- offs the NDR involves. (My best source has been the UBL mail archives
but it's fragmented and skimpy on this topic.)  Can anyone point me
to some more thoughtful evaluations of the NDR?  Or, perhaps,
implementations of CCTS that allow custom attributes?  Or, better
yet, UBL endorsed mechanisms for integrating custom attributes with
otherwise UBL NDR compliant schema?

The propositions to use DSDL layered on top of UBL schema expressions are only now being considered.  No decisions have been made and no recommendations are written down.  You will find a discussion of supplementing UBL schema expressions in:


As tools mature and experience using these evolving standards builds, I firmly believe we will be seeing wide-spread acceptance of these techniques.

I hope this helps.

. . . . . . . . . . . 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/x/
Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
Male Cancer Awareness Aug'05  http://www.CraneSoftwrights.com/x/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal


-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>


To subscribe or unsubscribe from this list use the subscription





 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS