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
>
OslcCoreMeetings20100721
(21 Jul 2010,
DaveJohnson
)
(raw view)
---+ OSLC Core Meeting July 21, 2010 ---++ Meeting logistics See the [[OslcCoreMeetings]] for more information, more dial-in numbers and on-line meeting information. * Conference Access * Toll free: 1-866-423-8350 * Toll: 1-719-387-8273 * Participant passcode: 558663 ---++ Agenda Action items from last week: * AI: Dave to move merge common properties into one list * Removed separate properties page, made Appendix A into the living registry of common resources and properties. * http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixADRAFT * AI: Dave to come up with alternative proposal before next meeting * Here's the proposal: http://open-services.net/pipermail/oslc-core_open-services.net/2010-July/000387.html Other changes to Core spec: * Minor fixes to Service Resources section and diagram * Fixes to usage of Dublin Core namespace string, always needs ending slash * Still more small fixes to do and proofreading needed Finalization plans * Proposal is that next week on July 28 we: * Declare the OSLC Core spec to be in finalization * Remove the word DRAFT from the spec and URLs * We allow only corrections and clarifications to the spec * We encourage our currently converging specs to finalize * We wait to declare the spec "final" when implementations are compete ---++ Minutes Notes from the meeting... TBD ---+++ Attendees * ArthurRyman * RobertElves * ScottBosworth * SteveSpeicher * PaulMacMahan * GrantLarsen ---+++ Topics discussed Discussed proposal to move to RDF/XML with no subset. http://open-services.net/pipermail/oslc-core_open-services.net/2010-July/000387.html Dave gave background for proposal, Robert Elves asked a lot of questions and we had a discussion of how clients and server implementations would have to behave moving forward. Robert Elves asked if this means clients should use an RDF parser to parse OSLC? We answered: yes. He commented that the RDF toolkit Jena is in "orbit" which means it has passed IP review and can be used in Eclipse sub-projects. We discussed need for both a) implementation guidance that discusses toolkits and techniques and b) Core Representation Guidance as described in the proposal. Discussed finalization and agreed that we would declare finalization at next week's meeting.
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r2 - 21 Jul 2010 - 15:31: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