To use the OSLC interfaces effectively, client programmers need an easy way to get 3GL language bindings to program against the interface. In practice, most ALM tools, which are the prime candidates to use the interfaces, would benefit from either a Java or C# binding. I can imagine two ways of getting these bindings:
a) For each interface, someone in the community, or a group of members, produce the binding by hand and maintain it as the interface evolves b) Clients use a set of commonly available tools to generate bindings Can someone from each workgroup comment, please, on how this can be addressed for the interface under development? Which language bindings are of interest (testing my hypothesis that Java and C# will suffice for most of the community)? Andy Berner Lead Architect, ISV Technical Enablement and Strategy IBM Rational Business Development 972 561-6599 [email protected] Ready for IBM Rational software partner program - http://www.ibm.com/isv/rational/readyfor.html
