NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"> <title></title> </head> <body text="#000000" bgcolor="#ffffff"> Hi All,<br> <br> John Caron wrote:<br> <blockquote type="cite" cite="mid408D36BA.5060807@xxxxxxxxxxxxxxxx">Hi benno: <br> <br> Benno Blumenthal wrote: <br> <br> <blockquote type="cite">John Caron wrote: <br> </blockquote> <br> There will be great benefits in switching to the 1.0 spec, as you note above, esp in connecting to Digital Libaries and providing the raw data for search services. <br> <br> <blockquote type="cite">Does it include an automatic editing interface easily accessible to everyone? </blockquote> <br> yes, we are working on a editing interface to make this easy. <br> </blockquote> If one believes the hype then using W3C Schema should also allow for use of "generic" XML editing tools. <br> <br> I have used XML Spy (a commercial product) which does validate as you prepare the instance document. It lets you know via the GUI what elements and attributes (and restricted attribute values) are available at any particular level in the instance document, but I'll be the first to admit it's really a tool to help experts (not novice users) prepare documents.<br> <br> Other tools might also work. For example:<br> <br> <b></b><b><a class="stxt" href="http://www.felixgolubov.com/XMLEditor/">XAmple XML Editor</a> <i>Description from the Publisher</i></b><br> <i>Java Swing based XML editor that analyzes a given schema and then generates a document-specific graphical user interface. Unlike other XML editors, the XAmple XML editor GUI exposes not just a tree representation of the XML document but rather a logical combination of the XML document and respective XML Schema. To be able to prepare valid XML documents of significant complexity, a user is not required to be familiar with XML and XML Schema languages and to have any a-priori knowledge about the documents structural requirements.</i><br> <br> I have not tried this as yet, but I will be trying it out in conjunction with the new LAS XML schema we're developing. Anybody else have experience with this product or others?<br> <br> Roland<br> </body> </html>
thredds
archives: