Date:
2 Feburary 2012 Time: 7:00 AM Pacific, 10:00 AM Eastern, 3:00 PM UK, 4:00 PM Frankfurt, 5:00 PM Haifa, 7:30 PM Bangalore
Call In Number: (emailed)
Participation request: contact
JimConallen
Agenda
- Update on core activities
- Discuss priorities and themes for v 3.0
- Introduce agenda topics
- Discuss order of importance and schedule activities
- Open up oppertunity for new meeting time(s).
Attendance
Regrets:
Atendees: Parham Vasaiely, Vishwanath Ramaswamy, John Crouchley, Alan Yeung, Steve Speicher, Clyde D. Icuspit, Gary Johnston, Jim Conallen
Minutes
Steve got us up to date on Core activities. He talked about work being done with the
W3C? recently in a workshop, with some of the core link life cycle concepts of resources (i.e. ui preview). OSLC Query and shapes however were out of scope. He discussed some of the future topics for core (found on the wiki).
The Core is moving to a model where the individual domain specifications would evolve independently instead of trying to release with the core or other specs.
Jim asked if there were any topics that our workgroup should avoid and Steve indicated that for the most part our work in all topics is appreciated, especially use case scenarios. Even prototype specs could be fruitful and useful as a means of explaning our concerns to the other workgoups.
Parham, Clyde and John indicated that traceability and variablility are inmportant topics for us to discuss. John in particular pointed out the need to be able to get a the delta of changes (either as a first class resource or with links to the before and after change). This topic will feature prominantly in our future discussions. Jim took as an action item to reach out to those active in the discussion to document specific use case scenarios. They were forewarned
Gray correctly pointed out that the topic of long running transformations is a cross workgoup topic, however we can continue to work it in our workgoup, and then coorrdinate with the Automation and core workgroups.
Parham and Vishy expressed an interest in the importance of the common properties and common types topics. Since this is a potentially long topic, we should try to do a lot of the work offline and schedule a meeting discussion when sufficient work has been completed on it.