On 18/03/2008, <b class="gmail_sendername">Sandy Klausner</b> <<a href="mailto:klausner@coretalk.net">klausner@coretalk.net</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Danny,<br> <br><br> "What does your vision look like?"<br> <br> <br>Again: <a href="http://www.coretalk.net">www.coretalk.net</a></blockquote><div><br>Interesting!<br><br>I've a lot of time for the mind map paradigm - in fact a few years ago spent a lot time working on a personal knowledgebase system [1] with this as the main view of a chunk of the Giant Global Graph. Cubicon sounds great!<br>
<br>But -<br>[[<br>Cubicon consists of a <em>new infrastructure</em> that gives form to a <em>community viewpoint</em> where all knowledge systems are constructed from a common set of executable design components. This <em>commonality</em> enables recombinant components to be globally represented in a language neutral expression medium. <br>
]] <br></div><br>- that bit I'm not so sure about. The thing is, everyone already has their own approach to building executable components - LAMP setups, scrappy bits of Python, J2EE monstrosities, MS/OS X/Linux desktops. How might one achieve a decent level of adoption of a new infrastructure? Surely it'll be better to look for existing common interfaces, and build against them, thereby reusing what's already out there..?<br>
<br>In other words -<br>[[<br>This automated service infrastructure will enable heterogeneous systems
to effectively communicate and initiate rapid adoption of
Service-Oriented Architecture (SOA).<br>]]<br>- something like that, only my bet would be on using (RESTful) HTTP+RDF to leverage the existing Web infrastructure, in other words go for the Semantic Web.<br><br>For my own stuff I've been gravitating towards an (almost)
lowest-common-denominator kind of abstraction based around simple
agents which will typically be comprised of a HTTP client, (access
from) a HTTP server, a local RDF model and local behaviour. The common
interface is the (Semantic) Web. Coincidentally I've recently been
looking over the old IdeaGraph code with a view to seriously
componentizing it so I can refactor it more closely to this approach. <br><br>Cheers,<br>Danny.<br><br>[1] <a href="http://web.archive.org/web/20031008162716/www.ideagraph.net/2003-06/screenshots.htm">http://web.archive.org/web/20031008162716/www.ideagraph.net/2003-06/screenshots.htm</a><br>
</div>(oops, didn't realise it'd slipped off the Web)<br><br>-- <br><a href="http://dannyayers.com">http://dannyayers.com</a><br>~<br><a href="http://blogs.talis.com/nodalities/this_weeks_semantic_web/">http://blogs.talis.com/nodalities/this_weeks_semantic_web/</a>