Welcome triscabor
My first goal was to aggregate a ton of supporting data to kick things off. I've done that by writing a few tools and applications to scrape numerous job sites ...
Reminds me of what I just built today, with somewhat surprising results...
A chat bot tool kit (http://www.chatbot.tk) to scrape a major search engine to get its responses.
Object Oriented classes are best, I think, but here is some pseudo code :
/* 1. Pick up writing instrument and blank piece of paper. */
function get(pen,paper){}
/* 2. Lay paper out flat on a smooth, hard surface. */
function put(paper){}
/* 3. With writing instrument, draw in a left to right fashion (assuming english or latin language), individual characters that form each word, followed by appropriate punctuation. */
/* 4. Continue writing until there is no space on the current line, then move down to the next line and continue. */
function print(pen,text,paper){}
/* 5. Repeat this until the writing is complete. If there is no more paper left, go to step 1. */
var pen,text,paper;
for loop {
function get(pen,paper){}
function put(paper){}
function print(pen,text,paper){}
} loop
I hope this helps you think about your knowledge base and inference engine design.
_________________________________________________________________________
If this is your requirement then I'm afraid there is no solution generally available to the public, many institutions/ corporations are working on the problem and it comes under the banner of AGI.
Perhaps my last comment wan't that constructive lol, I've been trying to get out of the habbit of spurting loads of information when not required.
Although a total solution to your requirements doesn't exist, this forum is a good place to get/ build ideas towards finding a solution. We are all working on various incarnations of AGI's.
As you can see, loads of helpful input already.
If your long term goal was not achievable then we would all be wasting our time and efforts, so ignore what I said and start breaking the problem down.
A semantic tree perhaps like Ranch says, break each task down into it's constituent parts, start at a high resolution then work to finer detail eventually arriving at servo/ machine level instructions. Even building a simple parsed language to hold the order/ instructions that can easily be converted at a later date into any format as your ideas develop. Start getting the nuts and bolts down.
Function Pickup_Object (x)
Look_for (x) - (see below)
Right_Grasp (x)
Lift (x)
End Function
Function Look_For (z)
Load_object_pattern (z)
Seek_Surface
Scan_for_pattten (z)
End Function
Edit: Oh! which is just what 8plan.net said... I must read all comments before I spout lol.
Here is some more sample data:
{"data":[{"jobs":[
{"whitecollar":[
{"id":0,"title":"Office Assistant"},
{"id":1,"title":"Office Manager"},
{"id":2,"title":"Executive"}
]},
{"bluecollar":[
{"id":0,"title":"Fast Food Worker"}
{"id":1,"title":"Gas Station Attendant"}
]}]
},{"outsourced":[
{"id":0,"title":"Office Assistant"},
{"id":1,"title":"Office Manager"},
{"id":2,"title":"Executive"}
]
}]}
;)