Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 94296 invoked from network); 14 Jan 2007 16:53:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Jan 2007 16:53:03 -0000 Received: (qmail 61320 invoked by uid 500); 14 Jan 2007 16:53:07 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 61274 invoked by uid 500); 14 Jan 2007 16:53:07 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 61262 invoked by uid 99); 14 Jan 2007 16:53:07 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Jan 2007 08:53:07 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of jaw981@gmail.com designates 64.233.182.184 as permitted sender) Received: from [64.233.182.184] (HELO nf-out-0910.google.com) (64.233.182.184) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Jan 2007 08:52:58 -0800 Received: by nf-out-0910.google.com with SMTP id k27so1800875nfc for ; Sun, 14 Jan 2007 08:52:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=DNIO2ha0ig9DLWX/TrVTrqOH6XRzotsFDjxDVEvSkdMAX9lJgs6P5Ua5je48vytWMn6ndWSJ+EgeKL0PJUR7ZIA0q3iSxGDvn9c4MeXua0hpA4OXyqLD0/f8UAk3Ls9RqjhG0WhKnSt5LvIc4I0TF0BzBY+GFvadchoVHHbisHE= Received: by 10.82.167.5 with SMTP id p5mr442189bue.1168793556418; Sun, 14 Jan 2007 08:52:36 -0800 (PST) Received: by 10.82.151.7 with HTTP; Sun, 14 Jan 2007 08:52:36 -0800 (PST) Message-ID: <73a75e430701140852i5d71a3bfm1e2100d19683b78c@mail.gmail.com> Date: Sun, 14 Jan 2007 11:52:36 -0500 From: "Jason Warner" To: dev@geronimo.apache.org Subject: Re: Reason for sequence in XSD's In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_57159_28976494.1168793556109" References: <1f52a95c0701120647g75d2a840oc4e1bfde1fcbb711@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_57159_28976494.1168793556109 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline > > >> > >> Anyone got an idea, why it is so? I hope I am not missing something > >> important here. > > >I think it was mostly my preference plus a vague attempt to imitate > >the spec schemas. It's definitely not written in stone :-) Maybe we > >should see what other people like. I think it is generally easier to pick up and learn and if there is a set order to the elements. Also, I think it makes it easier to go from one document to another if you know where to look in the document for the specific element you might be looking for. Is there a specific reason to not have a set order? I'm having trouble imagining a case where it would be necessary to change the order of the elements. ------=_Part_57159_28976494.1168793556109 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

>>
>> Anyone got an idea, why it is so? I hope I am not missing something
>> important here.

>I think it was mostly my preference plus a vague attempt to imitate
>the spec schemas.  It's definitely not written in stone :-)  Maybe we
>should see what other people like.

 
I think it is generally easier to pick up and learn and if there is a set order to the elements.  Also, I think it makes it easier to go from one document to another if you know where to look in the document for the specific element you might be looking for.  Is there a specific reason to not have a set order?  I'm having trouble imagining a case where it would be necessary to change the order of the elements.

------=_Part_57159_28976494.1168793556109--