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] | [Elist Home]


Subject: [ubl-lcsc] [Fwd: Re: Customizing UBL] - eduardo's response


forwarded response from eduardo

-------- Original Message --------
Subject: Re: Customizing UBL
Date: 02 Feb 2003 18:28:40 -0800
From: Eduardo Gutentag <eduardo.gutentag@sun.com>
To: Tim McGrath <tmcgrath@portcomm.com.au>
CC: Matthew Gertner <matthew@acepoint.cz>, "'Burcham, Bill'" <Bill_Burcham@stercomm.com>, "'Lisa Seaburg'" <xmlgeek@gmi.net>, ubl-lcsc@lists.oasis-open.org
References: <000801c2cab0$159275d0$bed67ac3@acepoint.cz> 3E3DC35B.40806@portcomm.com.au"><3E3DC35B.40806@portcomm.com.au>


Since I'm currently on-line I'll take a stab at responding, others
please chime in at will ;-)

On Sun, 2003-02-02 at 17:18, Tim McGrath wrote:
> Can you clarify a few technical points for me?
> 
> 1. you state that 'UBL uses explicit type defeintions for all elements' 
> (page 3).  yet when i look at a schema i see things like 'Street' as a 
> 'TextType'.  did you mean each element should have its own type e.g. 
> 'Street' should be 'StreetType'?  In your example of refinement you show 
> 'Address' being restricted.  'Address' is an aggregate and therefore a 
> complexType with its own 'AddressType'.  What if I wanted to restrict 
> 'Street'?  Can i do that?

No, not if it's defined as of type TextType, I believe. Might be wrong,
though.

> 
> 2. am i correct in thinking the concept of ur-type was introduced 
> because XSD does not allow certain derivations (such as making mandatory 
> fields optional)?  Are there other reasons for needed them?
Not that I can think of - the reason why we introduced the context of
ur-type at our last F2F was precisely to get around the XSD constraints
in terms of allowable derivations. It doesn't really get around them
in the sense that it now allows you to do what is prohibited, it just
allows you to do certain things in a disciplined manner so you can
attempt interoperability but not strict UBL compliance.

BTW, I'm not in the lcsc list, so this message will be rejected by the
mail server; you may want to forward it if you believe it's worth it.
And no, I cannot afford to join lcsc, sorry, I'm flooded enough as is
:-(

> 
> 
> Matthew Gertner wrote:
> 
> >All,
> >
> >With apologies for the delay, I am attaching a very rough and
> >preliminary draft of the documentation for customizing UBL. It is my
> >understanding that this is to be made available to users of UBL to guide
> >them in the customization process.
> >
> >The document is probably full of typographical and technical errors, and
> >lacks a reference section to point users to related documents.
> >Nonetheless, I hope it will serve at least as an outline for a future
> >release document, which seems to me to be an indispensable addition to
> >the current UBL release. I would be happy to revise the document based
> >on your and others' comments. Or someone could pick up the ball and run
> >with it...
> >
> >Finally, if you aren't interested in this, and I was wrong to send you
> >this document, just ignore it! On the other hand, if I have forgotten to
> >send it to some interested party, it is my assumption that someone in
> >the distribution list will handle dissemination at the face-to-face.
> >
> >Enjoy Denver if you are going...
> >
> >Matt
> >
> >  
> >
-- 
Eduardo Gutentag               |         e-mail: eduardo.gutentag@Sun.COM
Web Technologies and Standards |         Phone:  +1 510 550 4616 x31442
Sun Microsystems Inc.          |         1800 Harrison St. Oakland, CA 94612
W3C AC Rep / OASIS TAB Chair


-- 
regards
tim mcgrath
fremantle  western australia 6160
phone: +618 93352228  fax: +618 93352142 


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


Powered by eList eXpress LLC