You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hivemind.apache.org by hi...@jakarta.apache.org on 2004/09/10 18:59:14 UTC

[Jakarta HiveMind Wiki] Updated: NotXMLProposal

   Date: 2004-09-10T09:59:14
   Editor: MicahSchehl <mi...@schehl.com>
   Wiki: Jakarta HiveMind Wiki
   Page: NotXMLProposal
   URL: http://wiki.apache.org/jakarta-hivemind/NotXMLProposal

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -350,4 +350,5 @@
 The differences are subtle but must be learned by developers. Furthermore, there are still some open questions like encoding (character sets). 
 I think, the main problem behind "too much xml" is not the xml format itself, but the definition of verbose schemes and the shifting of programming logic to xml files. The definition of proprietary formats by each library is no solution for these problems. 
  
+MicahSchehl: XML is great because of it's wide acceptance-- but it is difficult to read and I am often overwhelmed with XML I am not familiar with.  I would like to see a project which aims to allow anyone to use syntax that they desire for configuration files.  The project would interpret the config file and generate the XML that so many other projects expect.  The generation could be done at compile time (generate XML files) or at runtime (SAX events).  The project could have default interpreters such as JavaScript or SDL.  This is just my first thoughts on this.
 

---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-cvs-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-cvs-help@jakarta.apache.org