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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-lcsc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [ubl-lcsc] [code:ascii-art] Straw-man 2 Code list proposal - candidate final


At 2003-09-11 02:34 +0800, Chin Chee-Kai wrote:
>Comments on ASCII Art in File "code-strawman2-20030908.html"

Here is a copy as written:


     Order-Cancellation.xsd
         |               |
         |               v
         |       UBL-Reusable.xsd
         |          |       |||
Cmn-Agg-Types.xsd  |       vvv
         |          |  Each-Code-List.xsd
         |          |   Each-Code-List.xsd
         |          |    Each-Code-List.xsd
         |          |         |||
         v          v         vvv
         Core-Component-Types.xsd


>3.   May be it is just the drawing, the "Cmn-Agg-Types.xsd"
>that presumably means "Common Aggregate Types" is
>"UBL-Reusable.xsd" itself.

Agreed ... I see that now.

>So suggest removing "Cmn-Agg-Types.xsd"
>but retain the vertical arrow.

Agreed.

>Also, "Order-Cancellation.xsd" itself can, and does, have
>use of code lists directly (e.g. "StatusCode".  This field
>itself currently has dependency on UBL-Reusable.xsd directly,
>but the dependency will be "swung over" to the new code list
>namespaces once they are created after this exercise).
>
>So the ASCII art could also reflect additional direct vertical
>arrows from "Order-Cancellation.xsd" to "Each-Code-List.xsd".

I disagree here.

Looking at Order-Cancellation.xsd I see, for example:

    ref="cat:StatusCode"

... and in UBL-Reusable.xsd I see:

     <xsd:element name="StatusCode" type="status:DerivedCodeType"/>

(but using the old name; we agreed on the above DerivedCodeType name at the 
LCSC meeting).

But I do not see the need to reference status:DerivedCodeType in 
Order-Cancellation and the validation I have done illustrates there is no 
need for the Order-Cancellation model to reference the status: namespace.

Therefore, I think the resulting ASCII art should look like:

     Order-Cancellation.xsd
         |               |
         |               v
         |       UBL-Reusable.xsd
         |          |       |||
         |          |       vvv
         |          |  Each-Code-List.xsd
         |          |   Each-Code-List.xsd
         |          |    Each-Code-List.xsd
         |          |         |||
         v          v         vvv
         Core-Component-Types.xsd


Thank you for helping to better understand the relationship between Common 
Aggregate types and Reusable, Chee-Kai!

............................ Ken

--
Next public European delivery:  3-day XSLT/2-day XSL-FO 2003-09-22
Next public US delivery:        3-day XSLT/2-day XSL-FO 2003-10-13
Instructor-led on-site corporate, government & user group training
for XSLT and XSL-FO world-wide:  please contact us for the details

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)
ISBN 0-13-065196-6                       Definitive XSLT and XPath
ISBN 0-13-140374-5                               Definitive XSL-FO
ISBN 1-894049-08-X   Practical Transformation Using XSLT and XPath
ISBN 1-894049-11-X               Practical Formatting Using XSL-FO
Member of the XML Guild of Practitioners:     http://XMLGuild.info
Male Breast Cancer Awareness  http://www.CraneSoftwrights.com/o/bc



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]