OSLC Core Meeting February 16, 2011
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.
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
Item: Community news
Item: Distributed Decision Making
- Next steps: add to Scott's Workgroup Best practices document
Item: Review and next steps
Item: Finalization and slowing down
I believe we are near the end of finalization and would like to propose that we slow-down the pace, move to bi-weekly meetings so we can focus on work on topics, educational materials (e.g. Primer) and the OSLC Tools projects.
We can meet again in two weeks to get an update on OSLC Tools and OSLC Primer status.
We can resume weekly meetings when we begin the push to OSLC v3, which is another topic for discussion.
Feedback on these thoughts?
Minutes
Attendees and notes from the meeting
Attendees
DaveJohnson
ArthurRyman
SteveSpiecher?
ScottBosworth
JimConallen
JimDesRivieres?
FrankBudinski?
Topics discussed
Community news
Steve:
we have a wiki just for OSLC Tools
created more examples for resource shapes
also checked in vocabulary documents to OSLC Tools project
Arthur:
Have you looked into vocabulary management tools?
Getting our docs into repository?
We could register with existing repositories or run our own
Arthur will follow-up on the mailing list
Steve:
We have needs for visualizing our repositories
Some folks use UML, but that is not ideal for RDF
Arthur:
Company "Sandpiper" has some UML RDF capabilities
Will send out links later for Sandpiper and Vocabulary registries
Scott:
What are "projects"
Vocabulary might be a good project, namespace documents
AI Dave: follow up on mailing list to determine what the list of OSLC Tools projects should be.
Distributed decision making
Dave:
Reviews new text, asks if it is OK
Scott:
We don't make decisions in the telecon, we make "recommended decisions" or "pending discussions" which are then discussed on mailing list
We should move this discussion to community mailing list, Core is not wide enough
Review and next steps
Multi-typed resources
- Jim C: not ready for guidance, not ready to propose solutions
- CAM has an answer, but not sure we have internal consensus
- Scott B: not a priority
- Dave J: backlog this until we hit this issue in a real use case
Baselining
- Dave J: backlog until Nick C comes back with proposal?
- Nick C: yes, need to come back very soon
- Scott B: several workgroups are interested in this, need to involve them
- Nick C: Need follow-up meeting soon, don't want to wait too long on this important topic
Comment & Discussions
- Steve S: few minor updates made to specs, then we are done
Change Log
- Frank B: will follow-up with mail list discussion, better use cases, etc.
- Nick C: there are still issues, such as what does it mean for resource to be changed?
- Frank B: would like to come back to this topic soon
Dave J: need to come back to topics of Baselining and Change Log in the near future
Nick C: also need to come back to Service Discovery
Dave J: could be part of OSLC v3 simplifications?
Nick C: yes
Scott B: please clarify
Nick C: service discovery service, service registry
Dave J: this would be a good discussion the the community mailing list
Moving to bi-weekly pace
Did not get to this topic, need to discuss on mailing list