Date: 24 May 2012
Time: 7:00 AM Pacific, 10:00 AM Eastern, 3:00 PM UK, 4:00 PM Frankfurt, 5:00 PM Haifa, 8:30 PM Bangalore
Call In Number: (emailed)
Participation request: contact JimConallen

Agenda

1. Updates on Core Activities
   1. Value Type
   2. PATCH support
   3. Requests for unknown or unsupported properties
2. Discuss migration of vocabularies from propriertery to OSLC.
3. Diagram resource type. Should we define one?
4. Continue discussion on impact analysis scenarios

Attendance

Regrets: Eldad Palachi, Eran Gery, John Crouchley, Jean-Louis Marechaux

Atendees: Steve Speicher, Jim Conallen

Minutes

We discussed the general issue of migrating vocabularies. The basic situation happens when implementers of resources define terms themselves that they need in order for their apps to work. But sometime later some of these terms get defined by a more authoratitive body (like the OSLC). Most of the properties remain the same, but a different namespace or authority is used. Everyone wants to start using these newer, and presumably better defined and more reusable terms. What guidance can we provide to clients and providers alike to deal with this situation.

1. We can have service providers provide both forms of properties (old namespace and new). Clients only look at what they expect to see. But doing PUTs might get confusing, if there is a contradiciton.

2. Have clients specify exactly what version to look for (i.e. OSLC-Core-Version: 2.0).

3. Have servers be responsible for transforming old style resources to new styled ones.

4. ...

We also discussed the need to identify dependency directions in property definitions.

Since the meeting was so lightly attended, we decided that Jim would detail these discussions and send it out to the AM and Core workgroups list.