[oslc] What should be included in an OSLC SDK Consumer Library?

[Wolf, Timo]

Hi All

Sounds great.  We currently implementing an iPhone/iPad client in objective-c. That platform is very nice for show cases, also it is less mainstream than java or perl.

Would be great to add objective-c to the library.

In general, when mobile devices are included, the client library should provide a on device store/cache for the artifacts to support offline work.

best Timo




On 24.06.2011, at 23:14, "Dave Steinberg" <davidms at ca.ibm.com<mailto:davidms at ca.ibm.com>> wrote:


Hi Dave et al.,

If this project is aiming to land at Eclipse, it might also be a good idea to include libraries and/or examples that facilitate the use of OSLC services in Eclipse RCP clients. Consuming delegated dialogs in a Browser control comes to mind.

Also, supporting an IProgressMonitor (for reporting progress and allowing cancellation) in HTTP operations would be very nice.

Cheers,
Dave

--
Dave Steinberg
IBM Rational Software
<mailto:davidms at ca.ibm.com>davidms at ca.ibm.com<mailto:davidms at ca.ibm.com>


<graycol.gif>Dave ---06/24/2011 03:05:51 PM---On Fri, Jun 24, 2011 at 2:58 PM, Paul McMahan <pmcmahan at us.ibm.com<mailto:pmcmahan at us.ibm.com>> wrote: > Sample js/dojo code for


<ecblank.gif>
From:   <ecblank.gif>
Dave <snoopdave at gmail.com<mailto:snoopdave at gmail.com>>
<ecblank.gif>
To:     <ecblank.gif>
Paul McMahan <pmcmahan at us.ibm.com<mailto:pmcmahan at us.ibm.com>>
<ecblank.gif>
Cc:     <ecblank.gif>
community at open-services.net<mailto:community at open-services.net>, <mailto:oslc-tools-devel at lists.sourceforge.net> oslc-tools-devel at lists.sourceforge.net<mailto:oslc-tools-devel at lists.sourceforge.net>
<ecblank.gif>
Date:   <ecblank.gif>
06/24/2011 03:05 PM
<ecblank.gif>
Subject:        <ecblank.gif>
Re: [oslc] What should be included in an OSLC SDK Consumer Library?
<ecblank.gif>
Sent by:        <ecblank.gif>
community-bounces at open-services.net<mailto:community-bounces at open-services.net>
________________________________



On Fri, Jun 24, 2011 at 2:58 PM, Paul McMahan <pmcmahan at us.ibm.com<mailto:pmcmahan at us.ibm.com>> wrote:
> Sample js/dojo code for consuming UI Preview and Selection/Creation dialogs
> might also be useful.

Good point. In the plan, I proposed OSLC Client Libraries for:

  - Java
  - PHP
  - JavaScript

The JavaScript client should include some of the same things as the
Java and PHP clients, but there would be some differences, see below.
I think we need some more thought on the notion of a JavaScript client
library.

  - JavaScript client can't handle OAuth on it's own, would need some
server-side help
  - JavaScript client could include helper code for UI Preview and Delegated UI


Thanks,
Dave




> From:   Dave <snoopdave at gmail.com<mailto:snoopdave at gmail.com>>
> To:     oslc-tools-devel at lists.sourceforge.net<mailto:oslc-tools-devel at lists.sourceforge.net>,
>            <mailto:community at open-services.net> community at open-services.net<mailto:community at open-services.net>
> Date:   06/24/2011 02:03 PM
> Subject:        [oslc] What should be included in an OSLC SDK Consumer Library?
> Sent by:        <mailto:community-bounces at open-services.net> community-bounces at open-services.net<mailto:community-bounces at open-services.net>
>
>
>
> Here's another topic for discussion from the OSLC SDK proposal.
>
> <https://sourceforge.net/apps/mediawiki/oslc-tools/index.php?title=Proposal_for_OSLC_SDK> https://sourceforge.net/apps/mediawiki/oslc-tools/index.php?title=Proposal_for_OSLC_SDK
>
>
> Here are some ideas for what should be in an OSLC SDK Client Library:
>
> * HTTP Client
>  - Must support for OAuth and BASIC Auth
>  - Include and build on an existing open source HTTP client
>  - Add or augment client's OAuth and BASIC auth support
>
> * RDF toolkit
>  - Must support parsing and generating RDF/XML
>  - Include and build on an existing open source RDF toolkit
>  - Add ability to parse and generate OSLC JSON format
>
> * OSLC "object model" or some way to:
>  - Make it easy for folks to create and general OSLC resources
>  - Make it easy to get resources as objects with properties
>
> * Other ideas for client library features:
>  - Ability to validate a resource against a Resource Shape
>  - Ability to easily iterate through multi-page resources
>  - Ability to determine Creation URL to use for given resource type
>  - Ability to determine Query URL to use for given resource type
>
> * Documentation
>  - Overview and how-to sections for C.R.U.D. on resources
>  - API reference for any objects and properties introduced
>
> Does that sound like the makings of a Client Library? What else should
> be present?
>
> Other issues...
>
> For other platforms such as PHP, Python, Ruby, etc. what are the best
> choices for HTTP clients and RDF toolkits?
>
> Which of the "other platforms" are most important for OSLC adoption?
> Is PHP the #1 priority or Ruby, or Perl?
>
> Other ideas?
>
> Thanks,
> Dave
>
>
> --
> David M. Johnson
> OSLC Specification Lead
> IBM Rational Software
>
> _______________________________________________
> Community mailing list
> <mailto:Community at open-services.net> Community at open-services.net<mailto:Community at open-services.net>
> <http://open-services.net/mailman/listinfo/community_open-services.net> http://open-services.net/mailman/listinfo/community_open-services.net
>
>
>

_______________________________________________
Community mailing list
<mailto:Community at open-services.net>Community at open-services.net<mailto:Community at open-services.net>
<http://open-services.net/mailman/listinfo/community_open-services.net>http://open-services.net/mailman/listinfo/community_open-services.net


_______________________________________________
Community mailing list
Community at open-services.net<mailto:Community at open-services.net>
http://open-services.net/mailman/listinfo/community_open-services.net