[oslc] Looking for input on OSLC software and contributors
Sanjay Joshi
joshisa at us.ibm.com
Fri Nov 4 08:58:20 EDT 2011
Continuing this thread of discussion, I would think that as the list
grows, it will be harder and harder to scroll and search. Perhaps, a
filtering mechanism could help based on what spec implementation is of
interest to the reader, or as Samit suggests - what consumers have been
validated for, etc ... Filtering as a feature on the page would be
useful as this page expands rapidly to match the ecosystem.
I also like the concept of somehow providing a process/capability for an
implementer to provide a high level description of their solution that
clearly indicates how OSLC is in play on the page itself or as a sub-page.
This would make this page a one-stop shop for quick perusal and
identification without multiple to/fro navigation outside of the site to
quickly review the entry. Even cooler if the site provided a linked data
story for each of these entries (perhaps an RDF form of the data on the
pages describing the implementation and this complete list of
implementations ;-)) Is this intended to be the beginnings of a OSLC
marketplace? Would be ideal for OSLC implementers to "want" to have a
presence on this page over time as a key and popular "marketing" channel
for their solution.
Regards
Sanjay Joshi
Third (3rd) Party Integrations Lead
Rational Integrations Gearbox Team
Centrelink Lab Advocate
IBM Software, Rational
Phone: 1-919-486-3204 | Mobile: 1-919-819-8866
E-mail: joshisa at us.ibm.com
Find me on: and within IBM on:
"While it can be, I will try ... " - ME
4205 S Miami Blvd
Durham, NC 27703-9141
United States
Samit Mehta/San Francisco/IBM at IBMUS
Sent by: community-bounces at open-services.net
11/03/2011 06:21 PM
To
Steve K Speicher/Raleigh/IBM at IBMUS,
cc
community at open-services.net
Subject
Re: [oslc] Looking for input on OSLC software and contributors
Building on what Steve comments, I would like to request that we also try
to capture the 3rd party integrations that have been tested with each
entry. For example, a consumer could list what providers have been tested
with the implementation. Maybe a column like "Integrations validated /
supported".
community-bounces at open-services.net wrote on 11/03/2011 04:49:45 PM:
> From: Steve K Speicher/Raleigh/IBM at IBMUS
> To: Lee J Reamsnyder/Durham/IBM at IBMUS
> Cc: community at open-services.net
> Date: 11/03/2011 04:51 PM
> Subject: Re: [oslc] Looking for input on OSLC software and contributors
> Sent by: community-bounces at open-services.net
>
> > From: Lee J Reamsnyder/Durham/IBM at IBMUS
> > To: community at open-services.net,
> > Date: 11/03/2011 01:14 PM
> > Subject: [oslc] Looking for input on OSLC software and contributors
> > Sent by: community-bounces at open-services.net
> >
> > I've
> > posted a table of OSLC consumers and providers on the OSLC website
> > (http://open-services.net/software/).
>
> A few comments on this page:
> 1) It is called "Software", why not "Implementers"? If it is software,
> then should probably add a section for things like Eclipse Lyo.
> 2) The column titled "Supported Specifications". Supported may be too
> strong a word for some implementations. Perhaps just "Implemented
Specs"
> or just "Specs" (and people will understand).
> 3) Something like a disclaimer and/or more descriptive text to introduce
> what is being presented. Like "OSLC implementations have not been
> validated by any 3rd party", etc
> 4) It would be nice if the product link actually linked to where the
> software documented/describes its OSLC support. To help "verify" that
the
> entry really does have some OSLC support described.
>
> Thanks,
> Steve Speicher | IBM Rational Software | (919) 254-0645
>
>
>
> _______________________________________________
> 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 --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20111104/6c32f6f4/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 518 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20111104/6c32f6f4/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 467 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20111104/6c32f6f4/attachment-0001.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 360 bytes
Desc: not available
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20111104/6c32f6f4/attachment.gif>
More information about the Community
mailing list