<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Dec 29, 2008, at 12:10 PM, Michael Keith wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br><blockquote type="cite">The difference is that in the case of web.xml or orm.xml, there is<br></blockquote><blockquote type="cite">exactly one document that contains the whole schema, and the developer<br></blockquote><blockquote type="cite">does not need to use XML namespaces. Whereas in web beans, the schema<br></blockquote><blockquote type="cite">is partitioned between multiple files, and there is a requirement that<br></blockquote><blockquote type="cite">the XML author understand namespaces.<br></blockquote><br>Right. I meant a single canonical specification-defined schema that can<br>be used as a reference by any and everyone that creates a config file.</div></blockquote><div><br></div>The library component configuration needs validation because Web Beans is solving a meta-configuration problem. The validation of the meta-syntax itself is less important and less useful than validating the configured objects themselves.</div><div><br></div><div>The spec's Admin example shows the value and need of validating the object's custom configuration.</div><div><br></div><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 8px/normal Courier; "><myapp:Admin><span style="font: 12.0px Helvetica"> </span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 8px/normal Courier; "> <ApplicationScoped/><span style="font: 12.0px Helvetica"> </span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 8px/normal Courier; "> <myapp:username>gavin</myapp:username><span style="font: 12.0px Helvetica"> </span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 8px/normal Courier; "> <myapp:name><span style="font: 12.0px Helvetica"> </span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 8px/normal Courier; "> <myapp:Name><span style="font: 12.0px Helvetica"> </span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 8px/normal Courier; "> <myapp:firstName>Gavin</myapp:firstName><span style="font: 12.0px Helvetica"> </span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 8px/normal Courier; "> <myapp:lastName>King</myapp:lastName><span style="font: 12.0px Helvetica"> </span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 8px/normal Courier; "> </myapp:Name><span style="font: 12.0px Helvetica"> </span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 8px/normal Courier; "> </myapp:name><span style="font: 12.0px Helvetica"> </span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 8px/normal Courier; "><font class="Apple-style-span" face="Helvetica" size="3"><span class="Apple-style-span" style="font-size: 12px;"></myapp:Admin></span></font></div><div><br></div><div>If the meta-syntax were changed to a DTD style as you're proposing, it would be easier to validate the meta-syntax, but impossible to validate the component's configuration. Consider converting the example to JSF 1.2 model configuration as an example DTD syntax. True, it's easy to validate the JSF model syntax, but it's not possible to validate the model parameters. You lose out. The result is not simpler, nor more readable, nor more robust, despite its DTD style.</div><div><br></div><div>Validation of the component's configuration is ultimately the problem that needs solving. Validating the meta-syntax is just housekeeping.</div><br><blockquote type="cite"><div>If I correctly understand your above description/expectation of schema <br>generation, then knowing the schema(s) being generated and then finding, <br>referencing and using them would actually add an additional level of <br>difficulty, I would think.</div></blockquote><div><br></div>Only if the library developer creates the schema. I'd think the schema would be optional. If it doesn't exist, then the library components won't be validated, but they can still be configured.</div><div><br></div><div>-- Scott<br><blockquote type="cite"><div><br></div></blockquote></div></body></html>