Hal, Not quite! It is a valid xhtml... but you cannot have more than one root element and be valid XML. There is also other possible issues that could come up by the parser reading history and picking up something it thought was code. It is a step in the right direction... and a great one. Yet, valid XML from the documentation I have read will have to be separated from the file. (like... dtd's, schema's, xsl's, wsdl's...) I don't think the fusebox group will get the W3C to change the standard so we can do XML our own way.
Therefore, we will have to write a parser to grab the XML data block... then pass the data block to our FuseDoc handler. This will mean the FuseDocs will lack portability. FuseDocs should work as global as possible when possible. The standard should not change from Java, PHP and CFM. This would require separation once again to meet with the universal FuseBox base standards where you can use the same standards everywhere. John >>> [EMAIL PROTECTED] 06/05/02 03:20PM >>> John, Fusedocs was always designed with the idea that once XML parsers became more prevalent, we could drop the comments tags. Thus on MX, we have: <cfxml variable="dsp_ThisFuse.cfm"> <fusedoc...> </fusedoc> </cfxml> That's perfectly valid XML. -----Original Message----- From: John Farrar [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 8:35 AM To: [EMAIL PROTECTED] Subject: Re: fusedoc type="" Slightly off focus... With web services we have wsdl's... separate files... shouldn't we do the same type of thing with fuse descriptions? Fusedocs is nice but not very accessable. It has been out for two years and it is burried inside of a file in a way that fundamemtally is not 'Valid XML'. I was thinking of working up a fdl (fuse description language) that followed the basics of fusedoc... but was separate. It even seems possible that each circuit could have the fusedocs nested together. This would work for all fuses in the root directory, nested fuse group directories (queries, action, display, etc.), and even MVC. Just a question... but I would like to see something more readily accessable and something we could write directly to with ColdFusion MX tools. John ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
