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


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-ndrsc message

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

Subject: RE: [ubl-ndrsc] Schema Design Flow

Title: Schema Design Flow
Right. We assumed the root element was outside the bounds of the diagram, but I can see we need to caveat.
-----Original Message-----
From: Dave Carlson [mailto:dcarlson@ontogenics.com]
Sent: Monday, January 07, 2002 5:51 PM
To: 'UBL Design Rules (E-mail)'
Subject: Re: [ubl-ndrsc] Schema Design Flow

The diagram is helpful, thanks.  But one nitpick, I don't see how the final branch "All local" can be possible.  You always need at least one global element to represent the document root.  So an extreme case would be that the document root exposes the instance namespace, but all child elements are written without a namespace prefix (unqualified local elements).
----- Original Message -----
Sent: Monday, January 07, 2002 6:57 AM
Subject: [ubl-ndrsc] Schema Design Flow

To all,

I have noticed that as we discuss the various features of schema, we seem to struggle at times to remember which features are compatible, at least I know that I certainly do.  To help me keep it all straight, I asked two of my developers - Joe Chiusano and Jessica Glace - to put together a flowchart that shows all the interdependencies of the various features.  Although they are still just getting started on this, I wanted to share with you what they have done so far since it seems to apply to our discussions, and may also be something we want to put in our design document.



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

Powered by eList eXpress LLC