[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: SV: [ubl] NDR specification of xsd:any in UBLExtension
Hi Ken, I think in this case I would rather like there to be an unbounded number or extension elements as opposed to an unbounded number of children of a single extension element, and if we can't have an unbounded number of extension elements then I would rather have just one extension element with one child. Reasons are as follows: 1. Ease of processing, I basically envisioned the workflow of receiving a document with an extension as getting out the single child of the extension sending that on to a seperate validation process/extension handling process and at the end assembling the results. This could be done with multiple children but then this should be specified that every child of extension should be considered as a serializable xml instance. I think there will be more work to get developers to understand multiple children than there will be to get them to understand one child - that is of course just personal opinion without any stats to back it up. I suppose that there is also an element of conservatism in my opinion on this matter. 2. The discussion in Brussels included such concepts as identifying the reason for an extension etc. Reasons are supposed to be bound to the extension element IIRC, not to the children (I'm not sure exactly what was decided on this because it was decided on way at one point and then changed, so it could be that it is elements under the UBLExtension element, or another element that is a following-sibling of the UBLExtension element or that it is attributes [new attributes though are disallowed IIRC so I suppose that it is not attributes]). The scenario you discuss here is of two children of the extension node having basically incompatible reasons for extending the document. Cheers, Bryan Rasmussen -----Oprindelig meddelelse----- Fra: G. Ken Holman [mailto:gkholman@CraneSoftwrights.com] Sendt: 20. juni 2006 23:26 Til: Universal Business Language Emne: [ubl] 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-unmark ed.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 --------------------------------------------------------------------- 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]