[OSLC] Generating language bindings for the OSLC interfaces

Paul McMahan pmcmahan at us.ibm.com
Wed Feb 3 13:10:48 EST 2010


I've had some success using JAXB to generate a java binding from an XML
schema which describes various OSLC resources and service description
documents.  The binding basically maps XML to/from POJO.  From what I
understand there are similar tools for other languages.  So I'm interested
in the idea of using tools to generate bindings for the resources and
service documents that flow across the standard GET/PUT/POST/DELETE calls.
I'm curious how this approach might work in terms of RDF schema since it
has advantages over XML schema, and whether its applicable for
representations other than XML.


Best wishes,
Paul McMahan
Rational Quality Management
pmcmahan at us.ibm.com



                                                                           
             Martin                                                        
             Nally/Raleigh/IBM                                             
             @IBMUS                                                     To 
             Sent by:                  Steve K Speicher/Raleigh/IBM at IBMUS  
             community-bounces                                          cc 
             @open-services.ne         community at open-services.net,        
             t                         community-bounces at open-services.net 
                                                                   Subject 
                                       Re: [OSLC] Generating language      
             02/03/2010 12:17          bindings for the OSLC interfaces    
             PM                                                            
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




Has anyone outlined what those bindings would look like? Don't all the
languages already have API for GET/PUT/POST/DELETE? The goal of a
REST-based design would be that there is nothing beyond this except the
ability to understand the domain-specific resource formats. An RDF library
might be useful for this. What else would be useful?

Best regards, Martin

Martin Nally, IBM Fellow
CTO and VP, IBM Rational
tel: (949)544-4691


(Embedded image moved to file: pic10293.gif)Inactive hide details for Steve
K Speicher---02/03/2010 08:29:16 AM---Andy, For CM domain I see it playing
out as #1 as most ofSteve K Speicher---02/03/2010 08:29:16 AM---Andy, For
CM domain I see it playing out as #1 as most of the interfaces define
                                                                           
 (Embedded      (Embedded image moved to file: pic30196.gif)               
 image moved to Steve K Speicher/Raleigh/IBM at IBMUS                         
 file:                                                                     
 pic28856.gif)                                                             
 From:                                                                     
                                                                           
 (Embedded      (Embedded image moved to file: pic10400.gif)               
 image moved to community at open-services.net                                
 file:                                                                     
 pic20291.gif)                                                             
 To:                                                                       
                                                                           
 (Embedded      (Embedded image moved to file: pic28662.gif)               
 image moved to 02/03/2010 08:29 AM                                        
 file:                                                                     
 pic19343.gif)                                                             
 Date:                                                                     
                                                                           
 (Embedded      (Embedded image moved to file: pic04625.gif)               
 image moved to Re: [OSLC] Generating language bindings for the OSLC       
 file:          interfaces                                                 
 pic14108.gif)                                                             
 Subject:                                                                  
                                                                           
 (Embedded      (Embedded image moved to file: pic25262.gif)               
 image moved to community-bounces at open-services.net                        
 file:                                                                     
 pic00816.gif)                                                             
 Sent by:                                                                  
                                                                           






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
_______________________________________________
Community mailing list
Community at open-services.net
http://open-services.net/mailman/listinfo/community_open-services.net

_______________________________________________
Community mailing list
Community at open-services.net
http://open-services.net/mailman/listinfo/community_open-services.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic10293.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20100203/994b77f5/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic28856.gif
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20100203/994b77f5/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic30196.gif
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20100203/994b77f5/attachment-0002.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic20291.gif
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20100203/994b77f5/attachment-0003.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic10400.gif
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20100203/994b77f5/attachment-0004.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic19343.gif
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20100203/994b77f5/attachment-0005.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic28662.gif
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20100203/994b77f5/attachment-0006.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic14108.gif
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20100203/994b77f5/attachment-0007.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic04625.gif
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20100203/994b77f5/attachment-0008.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic00816.gif
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20100203/994b77f5/attachment-0009.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic25262.gif
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20100203/994b77f5/attachment-0010.gif>


More information about the Community mailing list