hivemind-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Jakarta HiveMind Wiki] Updated: NotXMLProposal
Date Wed, 28 Apr 2004 21:35:52 GMT
   Date: 2004-04-28T14:35:52
   Editor: <>
   Wiki: Jakarta HiveMind Wiki
   Page: NotXMLProposal

   no comment

Change Log:

@@ -182,3 +182,5 @@
 an [ developerWorks article]
that really sums up the situation while raising (for me, at least) the question: who is this
XML for: !HiveMind, or us?
 KnutWannheden: To me the crucial question is whether the module (or deployment) descriptor
should be ''descriptive'' or ''imperative'' (as seen in the make vs. Ant war).  For HiveMind
I tend to favor a descriptive form.  But it should be possible to allow both.  We'll just
have to decide which one goes into the framework and which one into the library :-)
+[ GeoffLongman]: Speaking as a Hivemind
user, XML and SDL look fine. I have not warmed up to [ YAML] at all. Using
a true scripting language like Groovy turns me off completely. Leave the descriptors as ''descriptors''
that describe or declare something and are not executables. Speaking as somebody who ''might
someday'' commit to building an Eclipse plugin for Hivemind, XML is the path of least resistance
for me. A declarative markup like SDL or [ YAML] might be ok too if the
parser support were at a level conducive to developers tools. FYI, no open source XML parsers
were suitable out of the box for [ Spindle]. Although, I'm not
a parser writing kinda guy so - Rat's I gotta run, will finish these thoughts soon.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message