Content Representation With A Twist

Sunday, January 20, 2008

Build a new 'programming' language that neither instructs computers but tells them what to make sure?

Just reading the lastest news on a security hole in Winamp, and still having in mind how our programming trainees tend to assume things and base their programming on that -- instead of making pretty quite sure --, having worked on knowledge representation a rather long time, with the Winamp issue a thought popped into my mind:

As long as there are minds out there trying to make any one's programs do anything they were not intended for -- and that might be for a pretty long time --, programming might initially look like it looked like since decades: instruct the computer what to do and in which order to do it. But on the second glance, having people in mind who try to abuse programs, other people who ease them to do so instead of making sure, all that programming sort of things, in my eyes, looks like being in conversion to be knowledge work, rather than lining up building blocks. That kind of knowledge work that is to make sure things are the way we'd assume them to be. So the whole program might become some sort of building where each single building block was not only lines up but verified too. So, then in fact the whole building consists of knowledge rather than basically of building blocks of assumptions.
 

The majority of my achievements in knowledge representation was to figure out two fundamental concepts, aside of a minor but even more fundamental one: The concept of recognition is after "How to recognize items by a given subset of their features?" while reorganization asks how to reorganize a given graph of knowledge representation to make it less matter/energy consuming while still representing the very same content? The minor one was how to store content by graphs at all. It's very basic but important nevertheless.

Long a while ago, I wondered whether there might be a reason to base any kind of computers instructing language on that effort. But then I didn't see any such reason, and I didn't take any further effort to figure out any such one.

However, coming to the point today to see secure programs as a building of certainities, there in fact might be a reason to convert my efforts into a new computers instructing language.

      
Updates:
none so far

No comments: