Home. 
Search
.

transparent
transparent
transparent
  Library.Mailing List Archive

Altova Mailing List Archives


Re: [xml-dev] Here's why it's not always a good idea to embed validationinformation (e.g., schemaLocation) in instance documents

From: Richard Salz <rsalz@--.---.--->
To: John Snelson <john.snelson@------.--->
Date: 1/6/2009 10:09:00 PM
> Your presentation looks good, but I'm not sure it goes far enough. Was 
> there ever a good reason to embed validation information in an instance 
> document? Isn't that fundamentally backwards, like trusting a thief 
> because /he says/ he's not a thief?

Sometimes you might have reason to trust the sender. Or the implications 
of getting it wrong if you do trust him may not matter.  Or the cost of 
doing out of band configuration may exceed the costs of getting the trust 
wrong.  For example, if you are building generic XML stuff (like, say an 
appliance :).

We support schemaLocation.  But we also have a configuration operation 
that passes the URL's through a set of rewrite rules so that, e.g., you 
can rewrite remote schema to a local version that you trust.

        /r$

--
Visiting Member, IBM Academy
STSM, DataPower Chief Programmer
WebSphere DataPower SOA Appliances
http://www.ibm.com/software/integration/datapower/


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent
transparent
 
Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site
 
Use of this site is governed by our Terms & Conditions and Privacy Policy Copyright 2005-2012 Altova. All Rights Reserved.
transparentGSA