Altova Mailing List Archives>Archive Index >xmlschema-dev Archive Home >Recent entries >Thread Prev - Re: Schema limits and ordering >Thread Next - Re: Schema limits and ordering Re: Schema limits and orderingTo: "Michael Kay" <mhk@---.--.-->, "'Henry S. Thompson'" <ht@---.--.--.-->, "'Stuart Gilbert'" <Stu@------.------.----> Date: 6/5/2004 11:32:00 PM I personally like unordered. For the xml to object tools, it more closely matches a one to one relationship. Notice, the set methods on objects or beans don't need to be set in any particular order. Of course this is only one use case, and I know of others where I prefer to have order. It is something that would be nice to be optional. thanks, dean ----- Original Message ----- From: "Michael Kay" <mhk@m...> To: "'Henry S. Thompson'" <ht@i...>; "'Stuart Gilbert'" <Stu@B...> Cc: <xmlschema-dev@w...> Sent: Saturday, June 05, 2004 3:04 PM Subject: RE: Schema limits and ordering > > > If order doesn't matter, pick an order and enforce it. > > > > Both human authors and machines have no trouble with such discipline, > > _and_ it makes the resulting documents easier to read. > > Hmmm: I'm ALWAYS making mistakes with entering data against a schema that > arbitrarily requires date before author, when somehow author before date > seems more natural. (And yes, I do use tools that prompt me, but I can never > remember to stop typing and wait for the prompt). > > I know why the technology has this restriction, but I think trying to > promote it as a benefit is stretching a point! > > Michael Kay > > From Stu@B... Sun Jun 6 08:04:39 2004 Return-Path: <Stu@ | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
