Activated Reports

I’m not sure what to call this. It’s just an idea I just had sort of following on from yesterday’s post. What if the reports and data mining results we produce were ‘active’. In other words, what if they were set up so that programs could process them and use them. There would have to be

  1. an information backing to the reports
  2. a set of data in the reports and
  3. a presentation layout design for the reports.

The second two already tend to exist. The first one is the interesting one. It would tell you

  1. what was in the report
  2. what its context was
  3. what its relationships were, and
  4. what its meaning was, and
  5. (what its query was).

That last idea already exists in the literature. The first four ideas would need an information representation related to information oriented software development in much the same way that json is related to javascript.


The Information Backing For a Report

The information representation would include

  1. Knowledge Representation ontologies
  2. Endemes, and
  3. Endeme powered fields.

Telling you what the report was would require the first two. Telling you the context is would require all three. including the relationships would require all three. including the meaning would require all three.

I haven’t actually figured out how to do this. My plan is:

  1. build a bunch of lists of primitives – level 1.
  2. notice that some of the lists parallel each other and switch multiple lists of primitives to a single list of a class that contains the primitives as members – level 2.
  3. Activate the primitive members of the class so that they are activated fields powered by endemes. i.i make a single list of activated fields in the class with each member now characterized by an endeme in a single endene set – level 3.
  4. Move the mechanics related to the endeme set out of the class into its own class. This one I have never done, we’ll see if this works and what the results are when I do this – level 4.
  5. Build a report inside the program – level 4.
  6. Figure out an ontology system to store the report layout, data, and information – level 4.
  7. store the system in a file – level 4.
  8. Build a report generator to generate the report based on the file – level 4.




Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s