[oslc] Possible OSLC priorities and themes for 2011

[Scott Rich]

Similarly, I would like to see an overview of the specifications, focusing 
on the interconnections between them.  I think the scope of the specs has 
grown to the point that it has become hard to approach.  An overview along 
with some of the basic architectural principles and "rules of the road" 
extracted from the Core spec would be a great entry point.  I think doing 
this would also force some issues around consistency in cross-spec links, 
e.g. how strongly they should be typed, consistency in bi-directional 
links, etc.

Thanks,
Scott

---------------------------------------------------------------
Scott Rich, Distinguished Engineer
IBM Rational Chief Technical Officer for Northeast Europe
srich at ch.ibm.com



From:   Olivier Berger <olivier.berger at it-sudparis.eu>
To:     Dave <snoopdave at gmail.com>
Cc:     community at open-services.net
Date:   10/05/2010 09:48 AM
Subject:        Re: [oslc] Possible OSLC priorities and themes for 2011
Sent by:        community-bounces at open-services.net



Hi.

Le lundi 04 octobre 2010 à 18:13 -0400, Dave a écrit :

> 1) Adoption of specs: these are things that help folks adopt OSLC,
> both users and consumers. This includes tutorials, documentation,
> clients, test suites and reference implementations.
> 

Reference implementations would be great, if freely usable (FLOSS
licens ?)

Test suites and example code, in many languages, and under FLOSS
licences is definitely something that I see would be very important in
ensuring people can learn from code.

> 2) Guidance

OSLC specs can be frightening (dunno how printed versions would look
like, but certainly becoming a nice little book now) : it looks as if
many things need to be learned and implemented up-front, whereas, to be
OSLC-Core compliant, just a few things are really "MUST" specs, IMHO.
That's particularly the case when people imagine that they have to learn
REST and AJAX, XML/RDF and JSON all at once for instance (and when they
don't have experience with either of these for example if coming from a
traditional LAMP background).

Some kind of "tutorial" clearly helping learn OSLC specs, starting with
mandatory aspects and going along "decreasing" priorities of various
specs requirements would be very much appreciated, I think.

At least, that's what we have received as a common feedback during the
recently help Paris OSLC meetup next to OWF 2010 [0]

Hope this helps.

[0] 
http://www-public.it-sudparis.eu/~berger_o/weblog/2010/10/04/quick-report-from-oslc-meetup-in-paris-last-week/


-- 
Olivier BERGER <olivier.berger at it-sudparis.eu>
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingénieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)


_______________________________________________
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/20101005/257884e6/attachment-0001.html>