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
>
OslcCoreMeeting20101124
(24 Nov 2010,
DaveJohnson
)
(raw view)
---+ OSLC Core Meeting November 24, 2010 [[OslcCoreMeeting20101117][Last week's meeting]] Link to OSLC Core spec: OslcCoreSpecification ---++ 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 Online meeting: * <p> *For IBM employees,* use the following link:<br />[[https://lli.ibm.com/meeting/join/?schedid=4446009]] (IBM intranet authentication required)</p> * <p> *For people outside IBM,* use the following link:<br />[[https://apps.lotuslive.com/meetings/join?id=4446009]]</p> ---++ Agenda *Issue with the Use of dcterms:title and dcterms:description with oslc:ResponseInfo* * [[http://open-services.net/pipermail/oslc-core_open-services.net/2010-November/000638.html]] *Review actions taken since last meeting* * AI: Dave to propose schedule for next couple of months and seek topic owners * See also [[http://open-services.net/pipermail/oslc-core_open-services.net/2010-October/000597.html]] * Dec 1 - Discuss schedule * Dec 8 - Multi-typed resources (Jim Conallen?) * Dec 15 - Comments / Discussions (Jim Conallen?) * Jan 5 - Test Suite (Steve Speicher?) * Jan 12 - Reference Implementation (Dave Johnson) * Jan 19 - Attachments (Dave Johnson) * Jan 26 - Baselining (Nick Crossley?) * AI: Dave to apply version number changes and headers to all domain specs and seek help from Scott and Steve * Done in Core spec, still needs to be done in domain specs * [[http://open-services.net/bin/rdiff/Main/OslcCoreSpecification?rev1=39;rev2=38]] * AI: Clarify oslc:isMemberProperty * Done. New text is: "If set to true, this indicates that the property is a membership property, as described in the [[OSLCCoreSpecQuery#Member_List_Patterns][Query Syntax Specification: Member List Patterns]]. This is useful when the resource whose shape is being defined is viewed as a container of other resources. For example, look at the last example in Appendix B's [[OSLCCoreSpecRDFXMLExamples#Specifying_the_shape_of_a_query][RDF/XML Representation Examples: Specifying the shape of a query result]], where =blog:comment= is defined as a membership property and comment that matches the query is returned as value of that property" * Atom examples now validate with W3C Feed Validator. Fixed in Core appendix B and OSLC-CM. Also added link to validation check. * Done. For example: * [[http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fopen-services.net%2Fpub%2FMain%2FOSLCCoreSpecAtomExamples%2Fatom-core-example.xml]] * [[http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fopen-services.net%2Fpub%2FMain%2FCmSpecificationV2Samples%2Fatom-cm-example-1.xml]] * [[http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fopen-services.net%2Fpub%2FMain%2FCmSpecificationV2Samples%2Fatom-cm-example-2.xml]] * Small clarification in respond to recent reviews * Made OSLC terms in glossary normative * Marked Resource Creation and Resource Deletion section as informative * Small tweaks to unknown content language * Small tweaks to resource paging language * Diff: [[http://open-services.net/bin/rdiff/Main/OslcCoreSpecification?rev1=42;rev2=41]] *Other issues for discussion* Got issues? ---++ Minutes Attendees and notes from the meeting ---+++ Possible Attendees * DaveJohnson * NickCrossley * JimConallen * ScottBosworth * ArthurRyman ---+++ Topics discussed * Response info issue: we decided Arthur's option #1 is the best, but use property =oslc:thisPage= * AI Steve: check with implementations teams and any client usage, but impact should be minimal * AI Dave: update the specs and all impacted examples * Dragos issue: cannot rely on nesting * Topics for workgroup: * Arthur: we should have a primer topic, we really need a primer * Scott: we should have a set of "scoped" primers, not just one big primer * Jim: should explain how to work with existing implementations, how to work with at least one primer/consumer * Scott: need to be careful primer does not become Rational product documentation * Scott: should this be consumer or providers, or both * Arthur: primer should be end to end * Attachments: good topic, see AM examples * AI: Dave to write up schedule and sentence or two for each topic * Dec 1 - Discuss schedule * Dec 8 - Multi-typed resources (Jim Conallen) * Dec 15 - Primer (Dave) * Jan 26 - Baselining (Nick Crossley?) - common terminology, what belongs in OSLC what does not * Jan 5 - Comments / Discussions (Speicher and John Vasta?) state of union and options for going forward * Jan 12 - Test Suite (Steve Speicher?) * Jan 19 - Reference Implementation (Dave Johnson) * Jan 26 - Attachments (Dave Johnson) * Scott: need to advertise these meetings to the other community, in community mailing list, email to each workgroup lead * AI Dave: follow Scott's advice
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 - 24 Nov 2010 - 16:13:21 -
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