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
>
OslcCoreMeeting20110601
(01 Jun 2011,
DaveJohnson
)
(raw view)
---+ OSLC Core Meeting June 1, 2011 [[OslcCoreMeeting20110518][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: 6867265# * Other numbers: * [[https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=6867265&accessNumber=2158616239]] ---+++ Online meeting (if we need it) * For IBM employees, use the following link: * [[https://lli.ibm.com/meeting/join/?schedid=4446009]] (IBM intranet authentication required) * For people outside IBM, use the following link: * [[https://apps.lotuslive.com/meetings/join?id=4446009]] ---++ Agenda * Community News: Innovate * OslcAtInnovate2011 * [[http://stevespeicher.blogspot.com/2011/05/oslc-at-innovate-2011-conference.html]] * Schedule for June: * June 15: OslcTrackedResourceSet (formerly known as Change Logs) * June 29: BaselinesInOslc (new proposal on the way) * Going FINAL! * All issues are closed * [[http://open-services.net/pipermail/oslc-core_open-services.net/2011-May/000985.html]] * RDF vocabulary is in place * Move to declare the spec final ---++ Minutes Attendees and notes from the meeting ---+++ Attendees Dave Johnson Nick Crossly Steve Speicher Scott Bosworth John Arwe Arthur Ryman Ben Williams Ian Green ---+++ Topics discussed Community News Schedule for June Going FINAL - yes, pending UI Preview predicates to vocabulary What's next? *Arthur:* OSLC specs define vocabularies and protocols for specific scenarios Vocabularies have a life of their own, can show up in indexes, triplestores, and other vocabularies Should have REST spec and vocabulary spec for each domain, separately versioned *Dave:* Yes, "defining OSLC resources" should be recast as "defining OSLC vocabularies" But, do we really need separately versioned specs *Scott:* I've always thought we could have a Core spec that defines the REST API and domain specs that define vocabularies *Ian:* Like the idea of vocabularies, not sure about separate versioning *Scott:* Roadmap this summer? retrospective ---+++ Action Items Setup workgroup session(s) to cover: - Retrospective on Core v2 effort - Ideas for improving the Core spec - Straw man proposal(s) for Core v3 spec
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r3 - 01 Jun 2011 - 14:51:38 -
DaveJohnson
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