Ken, thanks for the comments, Nair and I are just a few of many Livelink guys, such as yourself, who share our knowledge to help the rest, and I certainly get as much back and more that I give.
Enterprise Connect is a new tool and still finding its feet, not sure how many people have deployed in in eval or Prod as yet - would like to hear from those who have as my team are looking into it now for our users.
WebServices is relatively new within Livelink, although it supports standard Web Services, of which you can find lots of examples on the web. The KC has some documentation, samples and forums for Livelink Web Services.
This technology should replace the LAPI stuff as its more suited to a Enterprise 2.0/Web environment, although LAPI will still have its place, users and plenty of legacy code to keep people enployed for many years to come.
OScript is still the language for Livelink, although we are expecting OClipse - OScript plugin for Eclipse - with Livelink 10, which is more of a replacement for the Builder than anything else from what I've seen so far, but there will be lots more on this at Content World. Would have thought a plugin for Visual Studio would be coming too given a) the OT/MS relationship and b) LAPI is supported in 2 MS language types (.Net and VB) and only one which is commonly used in Eclipse - Java
As well as the WebServices layer, there is also the Java Modules layer, although this has a smaller user base than LAPI but does allow compiled code which gives you the chance to keep your code or liscence checks private etc.
As for OScript knowledge, depends what you are looking to do with the resource you recruit, if you need them to write Livelink modules then OScript is key as its likely to be about for a while to come, as well as legacy system support etc.
Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006