This wiki is locked. Future workgroup activity and specification development must take place at
our new wiki
. For more information, see
this blog post about the new governance model
and
this post about changes to the website
.
TWiki
>
Main Web
>
OslcCore
>
OslcCoreMeetings
>
OslcCoreMeeting20110824
(19 Oct 2011,
SteveSpeicher
)
(raw view)
---+ OSLC Core Meeting August 24, 2011 [[OslcCoreMeeting20110727][Previous meeting]] Link to OSLC Core spec: OslcCoreSpecification ---++ Meeting logistics How to dial-in to our telecon and login to our screen-sharing session. ---+++ Telecon Info USA Toll-Free: 888-426-6840 USA Caller Paid: 215-861-6239 Participant Code: 3292849 Other numbers: https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=3292849&accessNumber=2158616239 ---+++ Online meeting (when we need it) For IBM employees, use the following link: http://w3.ibm.com/collaboration/meeting/join/?schedid=4440645 (IBM intranet authentication required) For people outside IBM, use the following link: http://www.ibm.com/collaboration/meeting/join?id=4440645 ---++ Agenda * Workgroup news * Meeting time & frequency: proposed alt time? * 2.0 Issues * [[http://open-services.net/pipermail/oslc-core_open-services.net/2011-August/001017.html][encoding of UI preview labels]] * [[http://open-services.net/pipermail/oslc-core_open-services.net/2011-August/001022.html][json representation ambiguities]] * 3.0 content and priorities discussion * We'll talk about various priorities for Core 3.0 and OSLC in general. This will mostly be a discussion to review feedback given so far and gather information on priorities. * Proposed themes: * *Adoption* - evaluate what tasks can be done to help with general adoption of specs - tutorials, SDKs, supporting docs to spec, validating the level of OSLC support through a scale * *Simplification* - along the same theme of adoption, look for ways to continue to simplify both the number of concepts, model and overall complexity of OSLC, reducing the technical barriers to adoption. This includes alignment with other standards bodies like W3C around linked data patterns. * *Community Growth* - ways to broaden the community and solidify OSLC as an independent entity opening the door for larger community * *DevOps* - expanding the reach of ALM into operations which also has some implications of OSLC support strictly within Ops * *PLM* - exposes specification and guidance on spec usage for PLM * *ALM continued* - looking at additional scenarios needed. Think of it as a continued evolution of what we have today. * OslcCoreV3Plan * Upcoming meetings: * Sept 7 - (tentative) continued 3.0 content progress * Sept 21 - (tentative) continued 3.0 content progress ---+++ Minutes Workgroup news * AM 2.0 final * Eclipse Lyo project moving forward * Automation WG looking to revive in coming months. * Communications WG to kick off Meeting time & frequency: proposed alt time? * Wed @ 2, prob with this in UK ACTION: Steve to send out survey for better time 2.0 Issues * [[http://open-services.net/pipermail/oslc-core_open-services.net/2011-August/001017.html][encoding of UI preview labels in dcterms:title]] * Arthur: spec seems right, that valid content in HTML is in <span> but example seems * ACTION: Steve to setup meeting with implementers on proposed resolution: invite at least: Paul, Arthur, Sam, * [[http://open-services.net/pipermail/oslc-core_open-services.net/2011-August/001022.html][json representation ambiguities]] * Looking for someone to investigate these ambiguities * JohnArwe said these issues aren't major but be good to have feedback sooner than later 3.0 content and priorities discussion * We'll talk about various priorities for Core 3.0 and OSLC in general. This will mostly be a discussion to review feedback given so far and gather information on priorities. * Proposed themes: * *Adoption* - evaluate what tasks can be done to help with general adoption of specs - tutorials, SDKs, supporting docs to spec, validating the level of OSLC support through a scale * *Simplification* - along the same theme of adoption, look for ways to continue to simplify both the number of concepts, model and overall complexity of OSLC, reducing the technical barriers to adoption. This includes alignment with other standards bodies like W3C around linked data patterns. * *Community Growth* - ways to broaden the community and solidify OSLC as an independent entity opening the door for larger community * *DevOps* - expanding the reach of ALM into operations which also has some implications of OSLC support strictly within Ops * *PLM* - exposes specification and guidance on spec usage for PLM * *ALM continued* - looking at additional scenarios needed. Think of it as a continued evolution of what we have today. * Arthur: would be very valuable to have overall conceptual model of all domains and their model. Nick: this will get worse over time. * OslcCoreV3Plan * Time table of 2Q2012 for Core 3.0 seen as too soon. Look to complete towards end of 2012. Need to get feedback from key stakeholders on priorities and time tables. * JohnArwe: question of domain URI to use for SPC when not a standard domain yet: queued up for upcoming meeting Upcoming meetings: * Sept 7 - (tentative) continued 3.0 content progress * Sept 21 - (tentative) continued 3.0 content progress ---+++ Attendees SteveSpeicher (chair) NickCrossley ArthurRyman JimConallen SheehanAnderson MichaelFiedler BenjaminWilliams CharlesRankin PaulMcMahan JohnArwe ---++ Topics discussed
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r6
<
r5
<
r4
<
r3
<
r2
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r6 - 19 Oct 2011 - 16:27:50 -
SteveSpeicher
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use
Ideas, requests, problems regarding this site?
Send feedback