02.07.13

Ontology 3.0

Posted in Disruptive Technologies, Enterprise Architecture, Ontology at 8:14 pm by Administrator

Ontology 3.0

Even though we are living in the time of Ontology 2.0, there is a much greater change coming, Ontology 3.0.

In Ontology 3.0, the quality issues of domain specific and purpose of ontologies are solved. They are solved by applying ontology to the development of domain ontologies. They are also solved by the adoption of standards for organizing and sharing ontologies.

Let me interject that the vision described here for Ontology 3.0 comes from projects and an Enterprise Architect’s perspective. One project involves the use of a set of integrated ontologies describing business models, Service Component Architecture (SCA), and Business Process Execution Language (BPEL).

In this project, “OTTER (Ontology Technology That Executes Real-time)”, first presented at KEOD 2011, the SCA ontology is used as an upper ontology for all components. The business ontology defines the business organization and all security access. The BPEL ontology defines the components of a business process. All of this operates on an HTTP server for full internet access.

Access to the processes and information held within the OTTER implementation are provided through individual sockets. Any individual or process accessing an OTTER server is given the specifics of a socket as determined by the security access defined in the business ontology.

Sockets are a great way to share services. Service requests can be dynamically formulated from the details available in a socket. Servers may send and receive requests that are fully described in the socket. The operations to manage the socket are the same whether operating from a browser using Javascript, an application running on a mobile device, or an application running on a server.

Ontology 3.0 delivers an ontology-based infrastructure for building systems. This is different from Ontology 2.0 that adopted the infrastructure of current business systems development. This transition simplifies the use and development of complex systems. This will open the access to ontology usage to everyone. They will only need access to sockets. They will only need to plugin!


The Enterprise Architects can see what is coming and are already preparing. They know that this will be their time. Corporations will be able to completely focus on their business, and automation will be viewed as an agile enabler. Automation will finally become the self-service contributor that the Corporate Office has always wanted it to be. –Enterprise Architects Masters of the Unseen City

youtubeClosing the Business / IT gap
.

« Previous entries Next Page » Next Page »