HistoryViewLinks to this page 2013 August 29 | 11:15 am

Date: 29 August 2013
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 Jim Conallen


  1. Update from core workgroup
  2. Discuss ongoing work at OMG related to OSLC integration
  3. Continue discussions of structure lists of resources as used in DM viewpoints and DOORS requirements modules

Active topics


Regrets: Clyde D. Icuspit, John Crouchley, Nir Mashkif

Attendees: Steve Speicher, Uri Shani, David Hirsch (for Sasha Rekhter), Jim Conallen


We started off with the discussion of structured views. Jim tried to argue for the case, and Steve kindly poked holes here and there, trying to see if any existing mechanisms would be sufficient. Requiring the client to have even the most basic semantic knowledge of the resources in a container just seems a little impractical. Even if it could get some from the published shapes of the resources in a container, that doesn’t necessarily mean the client would be able to construct appropriate queries for building a ‘view’ of the resources in that container.

Some examples of views that a container might offer (that would be useful) might be; all use cases that don’t have a link to a test case. Only UML packages and components. Only UML packages and diagrams.

Jim explained the basic flow of a client UI requesting from an OSLC container a list of views that are available for the container. Each view has a label and a description, suitable for the user to identify which view would be appropriate for the task at hand.

For example suppose the task at hand was ensuring all use cases have a test case. The UI would provide a tree control of UML packages and Use Cases (that don’t have a link to a test case - something that is difficult to express in OSLC simple query syntax). The UI then would ask the qm container for a list of existing test cases (perhaps a view of test cases currently not linked to a use case). The UI then could facilitate an easy matching of use cases and test cases. When the user is complete the UI would iterate through all the newly requested links and update the resources appropriately.

After the discussion of views, Steve updated the group on just some highlights of OSLC core activities; move to OASIS, release of 3.0 spec, and mentioned that we are in the phase of finishing up things and if there are any outstanding items left they will be getting dealt with soon.