|
|
| Articles |
| The following documents discuss various aspects of our technology,
and compare and contrast it with the world's existing approach. |
| Overview |
| The following documents describe Aurora in overview. |
|
|
| Ambiguous Xml |
Article |
XML is ambiguous and prevents automated data transfer.
It may surprise IT managers and companies to know that they are investing large sums of money
in support of a data transfer protocol that cannot be automated. Current 'automation' is no more
automated than a switchboard operator plugging in a cable, after which electrons flow 'automatically'.
True automation, the automated handling of arbitrary and novel xml documents, is contrary to the very
nature of the protocol. |
|
| HALSI |
Article |
Human, Application, Location, Schema Independence.
Four symptoms that stand in the way of a coherent environment.
Today's dominant technologies - rdbms and xml - exhibit these symptoms strongly, and so the very technologies at the heart of Web 2.0
are fundamentally flawed, from our perspective, as integration technologies. |
|
|
|
| Core Protocols |
| The following documents describe the Aurora core protocols |
|
|
| Technology Today |
| The following articles discuss Aurora in the context of today's most popular technologies,
and illustrate our claim that rdbms and xml are fundamentally flawed, as integration technologies,
and how Aurora was invented precisely to overcome those flaws. |
| Stating the case - Aurora vs Rdbms and Xml |
Article |
| In an Orwellian irony, the world's most popular information technologies today promise
integration, yet are designed for isolation. In the following articles we discuss how the world's
most popular technologies are funamentally flawed, if data integration is the goal. Whether for a
single device, an enterprise, or the world, rdms and xml will never lead to anything but fragmentation.
Read these articles to understand why, and how Aurora differs to make true integration possible |
|
| Solvent Protocol to Global Brain |
Article |
| This brief (one page) article summarises the key steps in a quasi-formal argument that a solvent protocol,
as we consider it, is not only necessary for true integration, but that once implemented, like Ice 9,
it will lead inexorably and inevitably to a Global Brain. Unlike Kurt Vonnegut's fascinating if disturbing invention,
we hope that our solvent protocol (Aurora) will be a little more benign. Like Ice 9, it does share an affinity for water,
but this is the subject of different articles. |
| | Applications |
| Aurora is ideal for complex information environments handling unpredictable new data.
The following articles discuss the case for introducing Aurora in such environments. |
| Defence (Defence Industry) |
Article |
A single modern vehicle or aircraft may already integrate any number of different systems,
possibly from many manufacturers, into a single coherent whole. Such a process we presume to be
somewhat complex, and integrating a new sensor, device or system both complex and demanding.
Ask that vehicle to co-operate in an overall task force, possibly comprising vehicles and units from many
different countries, and the result is a complex information environment, almost certainly without a single,
common over-riding technology platform.
Introduce Aurora into that environment, and both systems integration demands for a single vehicle are greatly reduced,
while at the command level, unit integration into a system-wide whole becomes both natural and achievable. |
|
|
|