March 26th 2008 - The Big Day for the AAAI 2008 Spring Symposia
Updated: April 15th 2008
March 26th was the start of the AAAI 2008 Spring Symposia.
From the Symposia program schedule page:
Links - Ontologies and Organizations
The general definition of ontology at Wikipedia ( versus the computer science definition given in the main link ) is "a study of conceptions of reality and the nature of being". In some ways, the general definition is more appropriate to modeling organizations - the target audience for an organizational ontology is people, not computers.
The shortest and most intuitive definition of term ontology is 'a description of things that be'. For most purposes, it may be the best definition.
Defining Rule Based Systems
Revised: Sept 25,2007
Modeling the Subject of "Rule-Based Systems"
Definitions can be seen assertions about relationship between well-defined terms, in other words things are defined in terms of other things. The terms and relationships associated with "rule-based systems" are ill-defined and make a rigorous definition nearly impossible to achieve.
AI Meets Business Rules and Process Management
The AAAI seems to be rumbling to life. An extended quote from their call for participation in the upcoming AAAI 2008 Spring Symposium Series ( with a few explanatory links inserted ):
Introduction to the OASIS SOA Reference Architecture
Why the SOA Reference Architecture ?
The OASIS SOA Reference Architecture is one of the best introductions to SOA, providing a complete, consistent and largely non-technical set of concepts and definitions for SOA technology. It may be the easiest way to understand SOA without digging through volumes of arcane technical standards and XML specifications.
A Business Rules Heresy
Do business rules need to be rigidly enforced ?
Advances in information technology in the last 20 years have made it easier to purchase products and services. Although the impact of information technology has been stunning, I doubt if many customers would assert that technology has made it easier to deal with rigid customer support policies and processes, quite the opposite. It can take months to correct a business process or system processing error. This is often the result of overly constrained systems that cannot adapt to changing customer requirements or circumstances.
