The TagCommons effort is operating something like a software project. The process is very lightweight, but has an important step that is often forgotten in discussions about ontologies and formats: for what purposes are we designing this? These days, a good way to look at functional requirements for software is to identify use cases and then derive engineering requirements. This was the first outcome of the working group, and the results are summarized here. We will describe the use cases first and then the requirements.
Tuesday, December 20, 2011
TagCommons has the Functional Requirements for Sharing Tag Data.