----- Original Message ----- From: "Murray Altheim" <[EMAIL PROTECTED]> To: <xindice-users@xml.apache.org> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, January 15, 2002 3:36 PM Subject: Re: Future of Xindice
> Tom Bradford wrote: > [...] > > Schema support > > ----------------------- > > We need to support schemas in an abstracted fashion. If we can > > architect a content model API that would allow the system to validate > > and operate against a content model without needing to know that the > > content model is based on XML Schemas or Relax NG, that would be ideal. > > Why in Xindice? There are several places where validation can occur: > 1. upon storing in the database; 2. following an XUpdate; and 3. upon > retrieving content from the database. In all three cases, the DOM nodes > to be validated are already available to the developer outside of > Xindice and can be validated using existing validation tools and techniques. > > Not that I'm going to fight the issue, but I'm rather against including > support for schema validation within the Xindice, as this is an application- > level issue (as I've described in previous messages). There are many > different types of schema validation, and different validation needs, eg., > different levels of strictness or different content validation at various > places within a processing regimen. Validation is a complicated issue that > doesn't have a one-size-fits-all type of solution. > > There are a plethora of validation options out there and I don't see that > one API could serve the variety of schema languages, structure and content > validation needs that would be within a reasonable scope of effort. You'd > be tackling the same issues that the W3C Schema WG tackled, with the > "data heads" and "document heads" needs on the table. I don't think it is impossible for one API to support multiple schema validation models if designed abstractly enough. Secondly I don't see why it is unreasonable to for users to be able to constrain the contents of the database at the document or collection level after all we've been doing it for years with relational and OO databases.Especially since there are some validation actions (e.g. validating identity constraints ) that are best left at the database level instead of making the application developer do the work if they don't want to. -- THINGS TO DO IF I BECOME AN EVIL OVERLORD #123 If I decide to hold a contest of skill open to the general public, contestants will be required to remove their hooded cloaks and shave their beards before entering. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
