I can't see any use for per-document schemas in my application(s), but if others see the use in it who am I to dispute that. I would think that per-collection validation would be more the norm, so that any attempt to support per-document validation would be in addition to (and not instead of) per-collection validation.
Did the discussions of the past yield any results? Was there a consensus on a preferred direction, even if nobody has worked on it yet? I would be willing to take a look at some implementations if someone can point me to discussions of how the desired functionality should work. - Tim > -----Original Message----- > From: Kimbro Staken [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 03, 2002 12:57 PM > To: [EMAIL PROTECTED] > Subject: Re: XSD or DTD validation? > > > We've discussed this a lot in the past, but there isn't > currently any work > going on for it. We had always talked about having an entire > collection > constrained to a particular schema. This may or may not be > the right way > to do things, I'm not sure. An argument can easily be made for per > document schemas, but then you lose some of the optimization > facilities > you'd have with a full collection schema. > > On Wednesday, January 2, 2002, at 09:32 PM, Timothy M. Dean wrote: > > > I was also curious about the same thing. I would be willing to > > contribute to this effort if necessary. Has anyone else given much > > thought to this idea? > > > > - Tim > > > > -----Original Message----- > > From: Jerry Wang [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, January 02, 2002 6:33 PM > > To: [EMAIL PROTECTED] > > Subject: XSD or DTD validation? > > > > > > Any plan to support XSD or DTD validation when creating or updating > > document? I think it will be good for example we bound each > collection > > with an XSD or DTD. > > > > -Jerry Wang > > Elegant Solution Consulting Inc. > > > > > > > > > > > Kimbro Staken > XML Database Software, Consulting and Writing > http://www.xmldatabases.org/ > >
