hivemind-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Jakarta HiveMind Wiki] Updated: NotXMLProposal
Date Wed, 05 May 2004 02:54:20 GMT
   Date: 2004-05-04T19:54:20
   Editor: <>
   Wiki: Jakarta HiveMind Wiki
   Page: NotXMLProposal

   no comment

Change Log:

@@ -307,3 +307,6 @@
 HarishKrishnaswamy: Couple things I forgot to mention: Producing HiveDoc is just as simple
because the comments could be a part of the AST and we could annotate them for HiveDoc. And
secondly, with this approach I don't think we need a special tool like Spindle for the descriptors;
the eclipse scrapbook page is good enough, IMO.
 I certainly like the SDL far better than XML for reasons I have already mentioned, but my
point of using scripting language was to save us the trouble of creating another language
and make it more easily adoptable. If I were new to HiveMind, I wouldn't want to worry about
the schema and factory and friends. I would simply want to say here's my service point and
here's the implementation, you do your thing and get me the service. Or here's the configuration
point and here's all the contributions. Don't get me wrong, I still like all the concepts
in HiveMind, its just the usage ;) And just to make it clear, there are no flames here!
+ColinSampaleanu: I don't know if you're looking for outside opinions, but I hate the idea
of inventing a new format like SDL. I agree it's a a bit cleaner and easier to type than XML,
but ultimately it doesn't seem to me the gain is that great that it makes up for the fact
that it's completely proprietary and nobody is able to leverage the work of anybody else (i.e.
other tools able to read the same format). For this reason, YAML or even a scrpting solution
like Groovy or BeanShell are preferable to me, along with XML which should remain a standby.

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

View raw message