SV: [ubl] Revised discussion paper on UBL 2.0 subsets, extensions, versions, validation and interchange

["Bryan Rasmussen" <BRS@itst.dk>]

Hi Ken,

I don't think this makes any sense:

        <xs:element ref="u:Extension" minOccurs="0"/>
        <xs:element ref="u:OrderNumber"/>
        <xs:element ref="u:LineItem" maxOccurs="unbounded"/>
        <xs:element ref="u:TotalAmount"/>
        <xs:group ref="u:FutureVersions"/>

If we were allowing basically any at the end of the sequence then we would
have both the Extension as an Any, and at the end of the sequence Any
allowed? The only difference is that u:Extension is of course an element. 

Why not if that was the case use 

  	  <xs:group ref="u:FutureVersions"/>
        <xs:element ref="u:OrderNumber"/>
        <xs:element ref="u:LineItem" maxOccurs="unbounded"/>
        <xs:element ref="u:TotalAmount"/>
        <xs:group ref="u:FutureVersions"/>

or 

	  <xs:element ref="u:Extension" minOccurs="0"/>
        <xs:element ref="u:OrderNumber"/>
        <xs:element ref="u:LineItem" maxOccurs="unbounded"/>
        <xs:element ref="u:TotalAmount"/>
        <xs:element ref="u:Extension" minOccurs="0"/>

This is not an endoresement of using the methodology you've shown in your
paper which I worry will cause implementation problems, and am not completely
sure if moving the Html method of handling unknown markup to a business
markup standard is a good idea, it's somewhat untried. But that is an issue
for a later post, although I might after thinking about it further become a
fan of the solution but right now I am worried. 

Also if I understand what you're suggesting I think we could end up with
nondeterminism, for example if you had


        <xs:element ref="u:TotalAmount" minOccurs="0"/>
        <xs:group ref="u:FutureVersions"/>

With this wouldn't you end up with a situation where u:TotalAmount either has
to be validated as the default validation of the validator, prob. strict, or
skipped, and how would you know which it was?

basically this is one of the reasons for using, instead of ##any namespace,
##other namespace, however other namespace usage CAN also lead to
nondeterminism in cases where the sequence can hold elements in namespaces
other than the target namespace of the schema where xsd:any is used. I'm not
sure how often these kinds of problems would arise, obviously would need NDR
rules to keep it from happening if this methodology where to be chosen. 


Cheers,
Bryan Rasmussen


-----Oprindelig meddelelse-----
Fra: G. Ken Holman [mailto:gkholman@CraneSoftwrights.com]
Sendt: 19. juni 2006 03:26
Til: Universal Business Language
Emne: [ubl] Revised discussion paper on UBL 2.0 subsets, extensions,
versions, validation and interchange


Hello all!

I have revised my proposed subset methodology, 
detailing what I think are the approaches and 
artefacts that a subset definer must define to 
support a community of users of a subset of UBL:

http://www.oasis-open.org/committees/download.php/18810/gkholman-ubl-modeling
-0.3.zip

In that paper I've also polished up my discussion 
of my proposed minor version namespace approach, 
showing how it addresses backwards compatibility 
to allow UBL 2.0 systems to be tolerant of UBL 
2.1 instances, and how it addresses Paul's 
comments in Belgium of the need to allow a 
network of validating nodes to incrementally 
migrate from 2.0 validation to 2.1 validation 
with 2.0-based nodes tolerating 2.1 instances on the network.

This approach to minor versioning is up for 
discussion on Wednesday's teleconference.

I very much look forward to any feedback.

. . . . . . . . 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


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php