[Oslc-steeringcommittee] OSLC Steering Committee Panels at Innovate 2013

[Ersch, Rainer]

Hi Sean,
I like your session proposals very much. I would suggest only a slight change in the line:
    from:              "1. make software integrations easier and more robust,"
    modify to:       "1. make software & system engineering integrations easier and more robust,"

I'm available for both, if it's not on Thursday. We should not run the session against each other (at the same time).
I like evening sessions (e.g. BOFs), because people are not rushing so much anymore, from one session to another.
We could call it "OSLC Café" like the "Jazz Café" in previous years.
If we want to go for BOFs, Monday and Tuesday evening would be the choices. Maybe we can have a mix too:
One regular session during the day and one evening session.
I would not distinguish too much between ALM and System. Just leave it to the audience which topics are more interesting.
We should prepare a presentation about the OASIS transition status to start with, and focus, but not limit, the discussion to organizational topics. Technical topics (RDF syntax and such) are hard to explain in such open sessions, due to different levels of knowledge in the audience. Nevertheless, we should have technical experts (e.g. WG leads) present to address technical topics or connect them with the interested parties for offline discussions.
We should also spend some time to explain how people can get involved in OSLC. The ultimate goal of the sessions should be to recruit some members for the active participation in the workgroups.

Bye and have a nice day
Rainer







From: Oslc-steeringcommittee [mailto:oslc-steeringcommittee-bounces at open-services.net] On Behalf Of Sean Kennedy
Sent: Tuesday, January 15, 2013 4:35 PM
To: oslc-steeringcommittee at open-services.net
Subject: [Oslc-steeringcommittee] OSLC Steering Committee Panels at Innovate 2013


Hello OSLC Steering Committee members:

I have submitted two "place holder" sessions for Innovate 2013. One for the Lifecycle Management track, and one for the Systems Engineering track.
They are basically the same idea, though the first takes an ALM slant while the second focuses on systems engineering.

Here is the abstract (it is common for both):
The "integration problem" is one faced by all businesses and is often solved in an unsatisfactory manner. e.g.: tight coupling makes changes difficult; multiple copies of data can slow down workflows, increase storage requirements, and worse; problem determination and resolution in such systems can be quite costly. Through OSLC, industry experts have gathered together for public discussion of common problems and solutions, and have published open specifications to:
1. make software integrations easier and more robust, and
2. expose more lifecycle data so that it can be effectively used.
Join members of the OSLC Steering Committee for an insightful discussion covering the common problems faced by software teams, the solutions available to those teams today, and a look ahead to what stubborn problems are the next to be tackled.

This is the common presentation outline:
The panel discussion will be directed by the moderator, asking prepared and previously submitted questions, and taking questions from the audience.

Improvements to the abstract are certainly welcome, but it is probably more important that you confirm you'd like to participate in one (or both) of these panels.
My initial (and maybe simplistic) assignments are:
Me as the moderator for both.
ALM Panel: Dave, Mik, and John
SSE Panel: Rainer, Andreas, and Bola

Best regards,

Sean Kennedy

________________________________






OSLC: Lifecycle integration inspired by the web -- http://open-services.net/
Eclipse Lyo: Enabling tool integration with OSLC -- http://eclipse.org/lyo/

There is nothing more powerful than an idea whose time has come. -- Victor Hugo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-steeringcommittee_open-services.net/attachments/20130115/1ec35499/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 166 bytes
Desc: image002.png
URL: <http://open-services.net/pipermail/oslc-steeringcommittee_open-services.net/attachments/20130115/1ec35499/attachment.png>