The masterplan

Click on the diagram to see the full view.

Being somewhat overwhelmed on the amount of interdependent ideas I had, I decided to put them all on a diagram in order to keep a better overview of what needs to be done when. Each box displays a project I intend to finish, each bubble represents contributions I expect from the outside.

Arrow colors are supposed to help you understand the diagram, although basically, each arrow represents a dependency that needs to be fulfilled in order to be able to complete the project it is pointing to. Ideally, all dependencies would have to be fulfilled before I start working on the project that depends on them, to avoid doubling up work every time something changes fundamentally in the project fulfilling the dependency, however it appears this will not be possible (because of circular dependencies), so some compromises will have to be made.

The descriptions of the projects are as follows:
  • Project Senzor: Interfacing real life industrial hardware with XMLoverHTTP and implementing it's regulation in the package.
  • Internet XML proxy: Sortof like an XML firewall, which publishes certain XML data directly from the protected LAN, while preventing access to other XML data published within this LAN.
  • GUI XML browser - web based: Graphical User Interface for browsing XML files for common users.
  • Internet Spreadsheet: A web-based application that allows users to create spreadsheet documents, which's cells can link to other XML data over the Internet.
  • XHTML data output examples: Simple XHTML documents generated dynamically based on XML data published elsewhere.
  • Framework for creation of XML forms: Likely something based on XForms, a framework that allows easy and fast design of internet forms which provide feedback in XML.
  • Accounting software: Energy accounting software, bundled with accounting software for non-profit organizations.
  • Automatic interorganizational communication: A framework which allows standard business transactions to be preformed automatically (without unnecessary paperwork) as well as bringing together all information published by an organization using XMLoverHTTP and publishing it, or retrieving this information from other organizations using the same software.
The overall idea is to:
  1. Develop all software in frameworks to avoid doubling up any work.
  2. Approach users of software by offering software packages comparable with what is currently on the market.
  3. Introduce the XMLoverHTTP concept, allow users to be creative with it and hence generate usable content.
  4. End up with the possibility to create large-scale control loops* such as would be required for a fully integrated prototechnate.
* = An example of such a control loop would be, say you want to use your air conditioning only when there is surplus electrictiy in the power grid. Ecologically, this would be a smart move, and it wouldn't prevent you from ever using your air conditioning either. This system once complete and in widespread use, would allow you to do this quite easily.

I will reiterate that most of the technologies required to implement what is presented in the diagram already exist at the moment and that the designs are quite down to earth.

Currently, I have practical work done in project Senzor and are learning the necesary technologies I will need to create the other bits.

As a side note, I have also published my Accountability system within a Technate article, there was no peer review, which is likely attributable to the holiday time. Still I assume the article was of some use and might generate discussion.