OSLC Core Meeting January 19, 2010
Last week's meeting
Link to OSLC Core spec:
OslcCoreSpecification
Meeting logistics
How to dial-in to our telecon and login to our screen-sharing session (when we need it).
Telecon Info
- USA Toll-Free: 888-426-6840
- USA Caller Paid: 215-861-6239
- Participant Code: 6867265
Online meeting
(when we need it)
- For IBM employees, use the following link:
- For people outside IBM, use the following link:
Agenda
- Comments / Discussions, Steve Speicher The OSLC Core spec includes Comments and Discussion resources but they have not been widely adopted. Steve will cover the state of union in regard to comments/discussions and lead a discussion of options for moving forward.
Minutes
Attendees and notes from the meeting
Attendees
Topics discussed
Agenda
- Comments / Discussion
- Resizing
- Upcoming
Topic: comments/discussions
Steve reviews the Core spec appendix A Comment and Discussions resources
Jim C: this looks good but what about multi-media comments
Rob E: for example, a defect with a screenshot
Jim C: could we treat this as attachments?
Rob E: how does discussion work, resource references comment? resource references discussion?
Steve S: you can post new comments to the discussion property
Jim C: if you have a comment URI, can you figure out what resource the comment is about?
Steve S: you would have to navigate to the Discussion, then to the resource
Scott B: after the discussion is established, are all comments in-reply-to something?
Rob E: top level comments could be in-reply-to comments
Scott B: we are using discussion in two different ways
Jim C: do we need a discussion resource?
Scott B: we need discussion URI to create comments, it is the comment factory
Steve S: discussion also provides a collection of comments
Dave J: we really need a spec that explains how spec works
Dave J: when do we do what? do we do this stuff before being FINAL?
Scott B: need to deal with renaming issues, clarifications, etc.
Steve: change Comment resource oslc:discussion to oslc:partOfDiscussion
Scott B: perhaps we should get procedural and only allow comments to be in Appendix A when it really is common
Steve S: we could run into problem of having CM comments then needing Core level comments too
Scott B: do we really need an identifier?
Steve S: one use case is that users use ID number to refer to other comments, i.e. "See Fred's comment #13"
AI: Steve S to write up clarifying paragraph for comments/discussions
Topic: Resize for delegated UI
Steve: we should allow this for delegated UI in addition to UI preview
Scott B: there is also an initial height in UI preview, that indicates need for dynamic sizing. We'd need that too
Topic: next topics
Dave J: reviewed the upcoming topics
Dave J: mentioned that OSLC RI source may be available next week, may need to post-pone discussion if not
Nick C: suggested baselines, but perhaps later in February as internal discussions still in progress
Nick C: also mentioned reading ACLs and security handling, but that is not written up yet