CloudMo.De™ consists of a cloud server built with a new data model called DataMo.De™, middleware called ObjectMo.De™ and a client layer called ObjectTray™.
+how we store data
DataMode is a patent-pending data model. This data model adds a potentiality to how the file is used by computer programs written to take advantage of this system. There are three things you do with data: change it, share it, and talk about it. The technology used to built the internet today is built on a hierarchial file system. Once you share or talk about data then it is public by default because the computer program that is used to display the data needs to know where the data is. What if you could store data in a non-hierarchical way. Such a system would compound the potentiality of the Data in many ways; among them are better search and increased security, that is exactly what we did.
DataMo.De is flexible. DataMode uses an augmented upgrade approach, what this means is the capability of the environment is a feature added to the file not imposed on the file therefore you can put your data into DataMode and you take it back out and put in on another file system unchanged.
To understand the technology of DataMo.De, we must first define what we mean when we use the term "Semantic." We do NOT mean "enabling machines to understand the meaning" of information (definition from wikipedia). Meaning is not an expressed goal of our technology. Our philosophy, contrary to popular information science, asserts that "meaning" is an effect that emerges from a user applying a process to data. We therefore reject the most common use of "Semantic" in computing circles, where meaning is assumed to be inherent or embedded in data and thus can be somehow extracted by machines. Our use of the term "Semantic" is intended to convey that data can be made "semantic" or recognizable (for automated and more efficient processing) and more intelligible (integrated from the ground up for social communication, organization and platform independent presentation).
Different from the ground up
The power of putting your data in DataMo.De is that it enables us to use a consistent data model across all computing activities. This offers significant and dramatic benefits. Probably what is the most dramatic of our core departures is that we do not see the "WEB (HTML, xml, etc)" as the end platform or destination for Data, therefore ours is not an attempt at a "semantic web" or to be the technologies, standards or format that make that possible. In fact our expressed goal is to create a new network that serves as a repository of data, where such data is "private by default." This PBD (private by default) network is populated by Organ-isms (organizations of isms, where ism is short for Intelligible, Semantic, Media), This PBD Network can be accessed via internet gateways but it is not the internet, that means it is not encoded via html. This means an elegant security model. If in the unlikely event your Data is ever stolen out of your application it cannot be used on any local operating system. No system is 100% secure but if you can't use what you steal then the threat of stealing is greatly diminshed.
+how we move data
ObjectMo.De is a development philosophy and framework that employs a stack of open-source and proprietary classes, libraries and components to move intelligent data around. ObjectMo.De is a stack of open-source and proprietary software components that connects and communicates your data with any device. ObjectMo.De is a standards based protocol (REST, WebSockets) that simultaneously maintains the integrity of the original data, and empowers the user with ability to precisely define who (or what) has access to their data. ObjectMo.De is more than just a set of code: it is a different way to think about writing computer programs.
Of models & moving. ObjectMo.De uses a different programming architecture, from the conventional Model-Veiw-Controller in it's development frameworks called Event-Content-Agent-Data. This architecture employs the same data model to move and manage data as DataMo.De uses to store it.
The TET offensive
The deployment costs associated with a particular data model are heavily influenced by the amount of translation between the physical and logical schema. These costs are a function of the complexity of the model (number of attributes, and number of relationships between the attributes). Traditional data storage systems optimize for storage space and for high performance access of the physical schema. This comes at a cost when this physical schema must be translated into the logical schema. This transformational process (from physical to logical when reading the data, and from logical to physical when writing the data) is a difficult problem, because the physical schema rarely maps to the logical schema in any straightforward manner. This translation / transformation model has been referred to as the "Vietnam of Computer Science", requiring significant engineering resources to accomplish in an effective and efficient manner. (Neward, Ted (2006-06-26). "The Vietnam of Computer Science". Interoperability Happens. Retrieved 2011-01-08).
Products not Theories
This is no information science theory. ObjectMo.De is a fact. We have done it. We are building industry changing products with it. The design and implementation of data models have a significant impact on getting data in, integrating data and getting data out. Advances in the data model have a significant effect on cost, performance, security and maintenance of information systems. DataMo.De is a patent-pending semantic binary model of data, where the semantics of the model are expressed as binary relationships (and collections of binary relationships) between the attributes of the model. ObjectMo.De is a stack of open-source and proprietary software components that use this model to move data around. This is not science fiction. This is market fact.
+how we present data
ObjectTray is a new metaphor for distributed computing. ObjectTray's are built with ObjectScript, a stable scripting environment for delivering innovate user experiences, natively on any platform. ObjectTray is a new metaphor for presenting data. The desktop metaphor is great for a computer that sits on your desk, but you can't take your desk in your car for a business lunch. With ObjectTray you stack objects on a tray and serve them. ObjectTray is a 'presentation' metaphor, not a workspace metaphor. ObjectTray is a set of classes and components, which provide generic functionality for sending data to/from the client layer and displaying such data on the UI.
Tray not Desktop. The idea of desktops with windows and menus as a metaphor for computer software is insufficient for today's computing environment . We use the metaphor of the Tray. A Tray is what you move things on. The Tray is intelligent and lives in a cloud so it can do a lot more than a desktop and windows ever could.
Can changing how you think really work?
Can changing how you think about data and having a consistent Data Model from the ground up, really have value? Let us say that one of our software objects is called an agent. We'll define agent as a set of instructions to "do" something with other objects. Lets say Objects are displayed in a tray. An agent "manages" the view. Lets call this agent "display.Agent". Objects are stored in a "dataSource". dataSources contain objects and instances. An instance is the relationship between objects. dataSources are classified using a simple, consistent model. This eliminates the need for "classes" of objects, with class specific data access mechanisms. A single type of agent, "fetch.Agent", retrieves objects from the dataSource. A single class of Agent displays data "display.Agent". Database performance is improved because the fetch only ever gets one kind of object, a DataMode object. And that's all it has to deliver to ObjectMoDe. It always knows what it's looking for and the "display.Agent" always knows what format the answer comes back in. A consistent data model delivers a significant improvement in performance, and the cost of making changes. One that is ubiquitous and at the same time robust enough to be used all the way out at the "display" (the part the user sees) level of software is a very significant advancement in information architecture.
What then is CloudMo.De?
CloudMo.De™ consists of a cloud server built with a new data model called DataMo.De™, middleware called ObjectMo.De™ and a client layer called ObjectTray™. Put simply, you implement all this on a development platform and you put it all in a box. This box becomes a platform on which you can build APPs. Apps are light computer (more like device) programs that can recognize and use Intelligent Data. When you shift your content into cloudMo.De™ and change your world.