Thursday, June 10, 2010

Domains of Information

I have a hypothesis that each application/database and stand alone databases are "contained" information domains, and contain sets of data elements that define their context.
If my hypothesis is correct then each of these domains could be described with an ontology, where by the context and definition of the data sets would be shared by the community that is the primary user/consumer of the information within the database.

Each database within a company would have it's own primary ontology, which is nothing more than fully described database schema. Since the guiding rules of relational theory state that you should be at a 3rd Normal rationalization, then the primary ontology is created on this definition of the schema.

Taking this further we can envision that each database is its own domain with its own ontlogy, with the enterprise having sets of ontologies. I am using the term "sets" to mean a collection of ontologies that may be reflective of similar context within combined user communities of interest. This concept provides a method for describing and cataloging information sources across the enterprise. The individual information sources are defined within the context and rules of the primary ontology, meaning that the data within the information source is defined based on the primary community for which the database was developed for.

If we catalog all information sources within a company, and we have formal ontologies for each of these information sources, it becomes evident that we can evaluate the business value of these information sources based on the business value chains that are defined by the organization or company.

So have I sparked any thoughts or comments yet?

I will continue to build this idea in future posts, I would value your input...

No comments:

Post a Comment