MHonArc v2.5.0b2 -->
ubl message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: NDR specification of xsd:any in UBLExtension
Hi folks,
I've moved on to a more critical analysis of
implementation guidelines and something caught my
eye in the 2006-05-25 NDR document:
http://www.oasis-open.org/committees/download.php/18372/NDR-2006-05-25-unmarked.pdf
Lines 643-646 reads as follows: Any use of
xsd:any should also allow no more than one
element in the non-UBL namespace to ease
serialization of the extending element as its own
XML instance that can then be validated, if an
implementer wishes to do so, outside the UBL validation process.
I'm thinking we should allow any number of
extension elements below the UBL extension point,
such that all systems (each of which may have
their own extensions) will find what they need from the extension point.
As a real-world example, when I define low-level
line-item detail to satisfy my legacy invoice
layouts, I'll be putting that information under
the extension point in a single child apex
element for the top of all my extra stuff. I can
then print my legacy format while simultaneously
satisfying the required UBL content for line items.
That same instance might need under the extension
point a single child apex element for the North
European Subset set of extensions so that I can
send my invoice to be paid. They get their
line-level detail and ignore my Crane extension content.
So, in this case the one instance will have two
elements, each in different namespaces, as
children of the UBLExtension element. This would
not be allowed by the sentence I quoted (if I
correctly understood the sentence).
But while I see the rule I quoted in prose, I do
not see the rule in a named and boxed rule. Can
we remove the sentence and allow the UBLExtension
element to have any number of children in non-UBL namespaces?
Thanks for considering this!
. . . . . . . . . . Ken
--
Registration open for UBL training: Montr�al, Canada 2006-08-07
Also for XSL-FO/XSLT training: Minneapolis, MN 2006-07-31/08-04
Also for UBL/XML/XSLT/XSL-FO training: Varo,Denmark 06-09-25/10-06
World-wide corporate, govt. & user group UBL, XSL, & XML training.
G. Ken Holman mailto:gkholman@CraneSoftwrights.com
Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/
Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995)
Male Cancer Awareness Aug'05 http://www.CraneSoftwrights.com/o/bc
Legal business disclaimers: http://www.CraneSoftwrights.com/legal
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]