OSLC defines a small but important set of methods for applications (or components thereof) to interact with each other. Complicated interfaces that impose a lot of requirements onto clients are unlikely to be used and are an obstacle on the way to the desired level of integration. So simplicity, stability, and standards compliance are key for such an interface, and are the driving factors behind OSLC. It shouldn't take much more than an HTTP client and an XML or JSON parser to use the interface. Resource representations must be stable and self-explanatory; assumptions and out-of-band knowledge imposed on clients must be kept to a minimum. And it shouldn't be a big effort to implement the interface.
Videos! OSLC: Open Services for Lifecycle Collaboration
AcdntlPoet 2700019V2G 3,207 Views
Here is an excellent playlist curated by our friends in IBM Rational Education highlighting valuable content surrounding OSLC, beginning with a great "Getting Started with OSLC" video: