I almost appended this as a comment to a previous post, but I decided it was important enough to elevate to the top level. I received this email from a person who wishes to remain anonymous but who has at least some first-hand knowledge of OKI:
I didn't want to publicly disparage the OKI project but privately I have severe doubts at its role in edu software development. I can't think of any comparable edu project to OKI in terms of hype and funding.
Sakai is using some of the OKI OSIDs but they also acknowledge that they need to go far and beyond OKI and have thus created their own set of Sakai APIs. Furthermore, as you alluded to in your post, this is not lightweight development at all. My biggest fear about all of these recent Mellon-funded edu tech projects is the immense barrier to entry because of the development difficulty. I fear that only the elite, the MITs, UMiches, Stanfords, will be able to contribute and play in this field.
This strikes me as a very serious concern. In our quest for technical standards of interoperability, are we losing sight of loose coupling? Are we trying to over-engineer something that perhaps would work best through organic growth?