I spent a few hours reading over the site and trying to get a feel for what kind of feedback to the workgroup would be beneficial. As far as OSLC RM is concerned, I judged that the following would be of interest:

• relevance to lifcycle collaboration and integration
• openness
• relevance to requirements management
• maturity and community interest, traction

tigris.org is a community site hosting a number of projects. There are several top-level groups of which on is "requirements" and this is the only one which declares it is to do with requirements. The other top-level groups address typical domains across software development - design, testing, defect tracking and so on. There is no mention of "systems" activities such as PLM, PDM.

The requirements section lives at http://requirements.tigris.org/. I spent my time exploring these pages.

Mongo

Is building a requirements management ontology based around IEEE Standard 830 (Recommended Practice for Software Requirements Specifications) and ISO/IEC 9126-1 (Product Quality). Additionally, it is defining a set of interfaces over that ontology, and is writing an implementation of those interfaces. This is fairly close to the remit of OSLC RM, so looks rather interesting.

In particular, their interface definition, Kraho, aims to support building CASE tools that can register and make use of software requirements.

Alas there hasn't been much interest on this project - not within several years. There are few (one or perhaps two) contributors.

RAVE

This looks like an interesting project but there is nothing to read about apart from the front matter.

Srtk

I'm including this only for completeness - too little to pass comment on, I'm afraid. This project offers set of UNIX command-line tools that offer awk-like capabilities through requirements which are written like email messages in text files.

Reqs

Offers a simple set of tools for manipualting requirements data. Of interest is a requirements representation language, RML, which bears some resemblance to the style of resources we're looking at in OSLC. Reqs "resources" are file based, and organised into projects & folders. The emphasis is on the dialects (ontologies) for different requirements processes, and on tools for sharing, processing and visualizing those requirements.

From what I can see the project looks to have stagnated - no activity and no community.

teamup4requirements

Aim is to make DOORS easier to use (!). I can't fathom what this project is about.