JDA (pronounced jay-da) is...

An Idea...

based on two beliefs.

1. By fostering the growth of an evolutionary marketplace of reusable components, we humans will become more empowered to innovate.
2. If software can be more easily taken apart and understood, our chances to stand on the shoulders of giants will improve greatly.

A Standard...

put forth based soley on HTML and Javascript.

1. Allows for the composition of javascript, HTML and Web services components. (The only reason it is based on HTML and Javascript is because it is meant to test the idea using the most popular and readily available technologies.)
2. Strives to specify as little as possible to stay true to the K.I.S.S. principle.
3. Meant to lend itself nicely to the ad-hoc copy-paste-and-tweak pattern prevalent in the good ol' days of HTML hacking. (If all you want to do is reuse components built by others, the standard allows you to not have to know Javascript.)

A New Method of Construction

OK, it's certainly not the first application of a dataflow architecture in software. However, it must be clearly stated that this is not Object-Oriented programming. Building applications using JDA is much more analogous to building hardware circuits. While designing and developing using JDA, you will find yourself opening up to new design patterns that will not only make your life easier, but also open new doors.

A Reference Implementation of IDA (Information Devices Architecture)

The technical goal of JDA is to use a set of most widely spread technologies to implement the philosophies behind IDA.