jducoeur

Totally agreed; the issue is mainly that the problem space is so large. I'd like us to have a general mechanism whereby users can relatively easily create representations of APIs inside Querki, and then use them in a natural way. But different APIs are going to call for different modes of interaction -- not to mention the plethora of different possible protocols, of which we'll probably have to pick one or two to support first.

So basically, I'm trying to get even a faint sense of where we might start with this. We can't do everything, and initially we'll probably only be able to do a little, so the question is, what would be the most useful subset?