[OSLC] Generating language bindings for the OSLC interfaces

[Steve K Speicher]

Andy,

For CM domain I see it playing out as #1 as most of the interfaces define 
deeper semantics on REST style hat can't be exposed easily in most 
commonly available tools that I'm aware of.   We see this now with Eclipse 
Mylyn and their exposure of a consumer Java API.  I see JavaScript 
bindings to be of interest as well.  I have not heard of any C#/C++ 
requests as of yet, though PHP (as a service provider) I have.  Now 
speaking for Rational products that use the CM interfaces, we utilize 
common code (both Java and JS) which has been manually developed.

Regards,
Steve Speicher | IBM Rational Software | (919) 254-0645


ajberner at us.ibm.com wrote on 02/03/2010 05:14:14 AM:

> 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
> ajberner at us.ibm.com
> 
> Ready for IBM Rational software partner program -
> http://www.ibm.com/isv/rational/readyfor.html
> 
> 
> _______________________________________________
> Community mailing list
> Community at open-services.net
> http://open-services.net/mailman/listinfo/community_open-services.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20100203/d85d6106/attachment-0003.html>