The SCM Tools Requirements statement

I am ready to begin creating my N3/triples table for my CM tools requirements spec so doing some research on where to begin. I have a spreadsheet with many columns to detail responses to each requirement which are laid out in each row. The columns will serve to display the following:

Impact Area - the task area or part of the tool does the requirement affect (such as admin, build and deploy, defect tracking, source control, etc.)
Role - the functional area is affected (admin, build, engineering, QA, BA, support, etc.)
Item - the requirement description
Detail - a detailed description of the requirement that needs to be met, or specific data requirements
Benefit Value - a statement of justification to why this requirement is important or needed
Value to Us - a ranking scale of 1-5 where 1 is Ok and 5 is Mandatory
Vendor response and rankings - comments from the vendor if needed (i.e. if a requirement is not met why, and can it be expected in the next release), and how they are rated against the requirement.

So, as an abstract on my Project Page in our wiki group I have stated: "Semantic web technologies provide a way to add meaning to data and to use software tools to help navigate that data in new and interesting ways. This paper explores the use of semantic web technologies in the area of Software Configuration Management (SCM) tools and how to select the correct one for your project or organization. Specifically, this paper reports on the how variables in selecting a tool have been used to help solve the problem of what requirements are met by analyzing the functionality of each tool and determining how each requirement has or has not been met. The results of this effort will show that we were able to select the best SCM tool for the job."