*offer these abstractions like lego bricks to build
programs close to natural language ?
*if you define the abstractions formally in cyc you will
lose the ambiguity and thats probably bad (you will narrow
the meaning to 1 strict meaning)
*make the abstractions searchable or offer related
ones to make the programming easier? (with some user interface)
*do you lose expression power by only using abstractions?
allow english entries too and see if anything gets lost
*when nesting like in "[most of [this entry]] is in english"
you will probably need a lot of reasoning power?
make a new list with the numbers 1 to 10
make a new list [x]
[x] is a list with [the numbers [1] to [10]]
make [the previous [1] lines] true
make a new list with the numbers 1 to 10
make [10] [boxes] and call it all [foo]
[every [box] in [foo]] has a number from 1 to 10]
make [ the previous [1] lines] true
make sure [no box is the same as another one]
make sure [[x] is a list containing [y]]
make an empty list in [x]
put [y] inside list [x]
[this entry] can be dangerous when [[x] is valuable]
make an empty list in [x]
doing [the command] can destroy [x]
make an empty list in [x]
doing [this] makes [ [x] is a list] true
doing [this] makes [ [x] is a variable] true
[the previous [2] lines] is most of the times true
[most of [this entry]] is written in abstractions
this
can mean: "the entry" or "all the entries for something" or
"the line of the entry" or …
most of [x]
describes a collection of elements in x so
the size is bigger than half or something
doing [x] makes [y] true
?
[x] is most of the times true
?
