Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 57926 invoked from network); 14 Jan 2007 22:06:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Jan 2007 22:06:35 -0000 Received: (qmail 91308 invoked by uid 500); 14 Jan 2007 22:06:40 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 91264 invoked by uid 500); 14 Jan 2007 22:06:40 -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 91253 invoked by uid 99); 14 Jan 2007 22:06:40 -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 14:06:40 -0800 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=MAILTO_TO_SPAM_ADDR,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of ammulder@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 14:06:31 -0800 Received: by nf-out-0910.google.com with SMTP id k27so1865520nfc for ; Sun, 14 Jan 2007 14:06:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=uXiteMxmFKF4VKP0zgo7xcR9uXvb+vaINH5DFI3eYSkk5s7n+CXrDqFhybJ+ipHXLaFupR/OJswBvAKn6KOQIFh8H0/kEuwUtNTeTBK1UDXFFGTuq6cNPGmkhfh5ORpHzWcvX9bQjioTWIQf7p238oC60gQJVwPOhCrmp63T/GU= Received: by 10.82.172.15 with SMTP id u15mr487029bue.1168812369478; Sun, 14 Jan 2007 14:06:09 -0800 (PST) Received: by 10.82.120.2 with HTTP; Sun, 14 Jan 2007 14:06:09 -0800 (PST) Message-ID: <74e15baa0701141406r3b81a186pcc101c3ed9fe5ff@mail.gmail.com> Date: Sun, 14 Jan 2007 17:06:09 -0500 From: "Aaron Mulder" Sender: ammulder@gmail.com To: dev@geronimo.apache.org Subject: Re: Reason for sequence in XSD's In-Reply-To: <73a75e430701140852i5d71a3bfm1e2100d19683b78c@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1f52a95c0701120647g75d2a840oc4e1bfde1fcbb711@mail.gmail.com> <73a75e430701140852i5d71a3bfm1e2100d19683b78c@mail.gmail.com> X-Google-Sender-Auth: a4625ef7dac8c252 X-Virus-Checked: Checked by ClamAV on apache.org We have seen a number of errors on the user list that turned out to be plans with elements in the wrong order. I'd have preferred if there wasn't a specific order I think, but I don't feel strongly enough to want to change all the schemas. Thanks, Aaron On 1/14/07, Jason Warner wrote: > > > > > > >> > > >> 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. > >