Back to SkosDev.
This is a proposed loose framework for working collaboratively on SKOS specifications.
SKOS Development Process
The firstname.lastname@example.org mailing list is the primary forum for all SKOS development. Anybody is free to post comments or suggestions on any of the SKOS specifications or documentation to this list at any time. A public archive of this mailing list is online.
Beyond informal comments and suggestions, there is a very simple structured development process which can be followed. The first stage is to identify a requirement. The second stage is to offer a proposal. The final stage is to take an action.
If you have a specific requirement which you do not feel can be satisfied by any of the current SKOS specifications, then write it up in an email and post it to the email@example.com mailing list, including '[Requirement]' as the first word in the subject line.
When discussing a requirement via the email list, please preserve the original subject line in all subsequent emails, prefixed with 're:'.
The URL for the original requirement email in the web archives may also be used to refer unambiguously to the requirement in future discussion and in proposals and actions relating to that requirement.
Example requirement email ...
To: firstname.lastname@example.org Subject: [Requirement] Need for semi-structured development process for SKOS specs I think SKOS could do with some sort of semi-structured development process. This will be essential as the team of contributors grows larger. It will help to make SKOS development more accessible if there is a way of registering new requirements with the SKOS development team. It will also help users to track changes to the specs, and for contributors to track developments. Al.
A proposal is a suggested action to change some part of the SKOS specifications.
If you have a specific proposal for improving the SKOS specifications, then write it up in an email and post it to the email@example.com mailing list, including '[Proposal]' as the first word in the subject line.
When discussing a proposal via the email list, please preserve the original subject line in all subsequent emails, prefixed with 're:'.
The URL for the original proposal email in the web archives may also be used to refer unambiguously to the proposal in future discussion and in actions relating to the proposal.
If your proposal is in response to a known requirement, then please include in the proposal email a reference to the URL of the requirement email in the web archive.
If you would like to make a proposal, then please first write up the specific requirement that has led you to invent the proposal. This will allow other SKOS contributors to evaluate the requirement you identify, and discuss alternative proposals in relation to this specific need, or indeed whether or not this need is within the scope of a particular SKOS specification.
Example proposal email ...
To: firstname.lastname@example.org Subject: [Proposal] define a SKOS development process This proposal is in response to the requirement identified in . I've written up a suggested SKOS development process on the SkosDev wiki - see . This wiki page is entirely the proposal. Al.  http://lists.w3.org/Archives/Public/public-esw-thes/2004Jun/0018.html  http://esw.w3.org/topic/SkosDev_2fChangeProcess
If after public discussion a consensus is reached that a specific proposal is in fact a good idea, then an action will be taken and the SKOS specification in question will be modified in line with the proposal. An email reporting the action will be posted to the email@example.com mailing list. The action will also be reported on the SKOS changelog.
Using the SkosDev Wiki
The SkosDev wiki provides an alternative way of publishing comments and suggestions on SKOS specifications.
If you would rather write up a requirement or a proposal on the wiki, that's fine, but please make sure to send an email to firstname.lastname@example.org in the style described above so it is registered as part of the development process. In the body of the mail include a reference to the URL of the wiki page and enough information to identify the bit you have added.