IGF Virtual Community

English:
IGF Virtual Community

Français:
IGF Virtual Community

Español:
IGF Virtual Community

한국어:
IGF Virtual Community

English:
<p>This is a draft requirements document for building an online community for the IGF, at least equivalent to those of other Internet governance institutions such as the IETF etc. The focus here is not on remote participation, which although also important, is being dealt with <a href="http://www.igfremote.com/" class="external text" title="http://www.igfremote.com/" rel="nofollow">elsewhere</a>. Discussion can take place <a href="http://igf-online.net/wws/info/igf-ocdc" class="external text" title="http://igf-online.net/wws/info/igf-ocdc" rel="nofollow">here</a>.
</p>
<table id="toc" class="toc" summary="Contents"><tr><td><div id="toctitle"><h2>Contents</h2></div>
<ul>
<li class="toclevel-1"><a href="#Draft_timetable"><span class="tocnumber">1</span> <span class="toctext">Draft timetable</span></a></li>
<li class="toclevel-1"><a href="#Rationale"><span class="tocnumber">2</span> <span class="toctext">Rationale</span></a></li>
<li class="toclevel-1"><a href="#What_the_IGF_already_has"><span class="tocnumber">3</span> <span class="toctext">What the IGF already has</span></a>
<ul>
<li class="toclevel-2"><a href="#Official_Web_site"><span class="tocnumber">3.1</span> <span class="toctext">Official Web site</span></a></li>
<li class="toclevel-2"><a href="#IGF_Community_Site"><span class="tocnumber">3.2</span> <span class="toctext">IGF Community Site</span></a></li>
<li class="toclevel-2"><a href="#Host_country_sites"><span class="tocnumber">3.3</span> <span class="toctext">Host country sites</span></a></li>
<li class="toclevel-2"><a href="#Other"><span class="tocnumber">3.4</span> <span class="toctext">Other</span></a></li>
</ul>
</li>
<li class="toclevel-1"><a href="#What_changes_are_required"><span class="tocnumber">4</span> <span class="toctext">What changes are required</span></a>
<ul>
<li class="toclevel-2"><a href="#Institutional"><span class="tocnumber">4.1</span> <span class="toctext">Institutional</span></a></li>
<li class="toclevel-2"><a href="#Technical"><span class="tocnumber">4.2</span> <span class="toctext">Technical</span></a></li>
<li class="toclevel-2"><a href="#Social"><span class="tocnumber">4.3</span> <span class="toctext">Social</span></a></li>
</ul>
</li>
</ul>
</td></tr></table><script type="text/javascript"> if (window.showTocToggle) { var tocShowText = "show"; var tocHideText = "hide"; showTocToggle(); } </script>
<a name="Draft_timetable" id="Draft_timetable"></a><h2>Draft timetable</h2>
<table class="wikitable">

<tr>
<td> 30 June 2008
</td><td> Document open for editing on the wiki
</td></tr>
<tr>
<td> 1 July 2008
</td><td> Final document posted for a consensus call to <a href="http://igf-online.net/wws/info/igf-ocdc" class="external text" title="http://igf-online.net/wws/info/igf-ocdc" rel="nofollow">[email protected]</a>
</td></tr>
<tr>
<td> 7 July 2008
</td><td> Close of consensus call with Apache-style "lazy consensus" (a few positive votes with no abstentions)
</td></tr>
<tr>
<td> 8 July 2008
</td><td> Finalised requirements document sent to developers for quotes (note: free is also a quote)
</td></tr>
<tr>
<td> 8 August 2008
</td><td> Closure of deadline for quotes
</td></tr>
<tr>
<td> 10 August 2008
</td><td> OCDC selects a recommended quote and forwards all documents to the Secretariat for endorsement
</td></tr>
<tr>
<td> September 2008
</td><td> If necessary, documents presented at open consultation and call for donations to cover development cost
</td></tr></table>
<a name="Rationale" id="Rationale"></a><h2>Rationale</h2>
<p>The establishment of the IGF was an ambitious innovation in global governance for the Internet. Whereas earlier Internet governance institutions such as the IETF, the RIRs, and to some extent ICANN, emerged largely from the grassroots of the Internet technical community and utilised principally online working methods from the outset, the IGF is the first new Internet governance institution to be structured principally as a face-to-face annual meeting, and aside from the activities of its dynamic coalitions, it remains set in that form.
</p><p>Whilst this may have provided a more natural means of engagement for some stakeholders from outside the Internet technical community, it has distanced the IGF from ordinary Internet users and limited its potential to draw in the breadth of community engagement that the other Internet governance institutions mentioned above have enjoyed. Thus even when mechanisms such as Webcasting have been provided to bridge the annual meeting with online users, these have been underutilised because remote users have not felt part of the same community as those meeting in person.
</p><p>To improve the mechanisms of remote participation made available by the IGF therefore only addresses part of the problem. What is more important is that the IGF produce a virtual community to motivate a broad cross-section of users, including those who cannot afford to attend the annual meetings, to participate actively and enthusiastically in year-round policy dialogue. In short, the IGF must welcome online discourse as a principal means of engagement in its activities, not merely as an adjunct to its discrete annual meetings.
</p><p>To date, the IGF has fallen short in this. Where other Internet governance institutions host vibrant and effective virtual discussions that benefit from the unique discursive properties of the online environment, the IGF does not. The development of such a virtual community for the IGF has been limited by a number of factors, and it is the purpose of this requirements document to set those out, and to sketch the institutional, technical and social modifications that the IGF should commit to if it wishes to foster the development of a more engaging online environment for the IGF community.
</p>
<a name="What_the_IGF_already_has" id="What_the_IGF_already_has"></a><h2>What the IGF already has</h2>
<a name="Official_Web_site" id="Official_Web_site"></a><h3>Official Web site</h3>
<ul><li> Static pages, manually maintained navigation and ad-hoc archival
</li><li> Manually maintained ACL for event organisers to update event information
</li><li> Semi-automated management of event information
</li><li> No programmatic access to metadata such as calendar files
</li><li> Interactivity limited to a manually maintained RSS feed
</li><li> No site map, search or user-generated content
</li><li> Limited support for asynchronous discussion (the official Web forum)
</li><li> Limited support for synchronous discussion (the official Webcast and chat client)
</li><li> No support for collaborative editing, decision-making, social networking or multilingualisation
</li></ul>
<a name="IGF_Community_Site" id="IGF_Community_Site"></a><h3><a href="http://igf-online.net/" class="external text" title="http://igf-online.net/" eel="nofollow">IGF Community Site</a></h3>
<ul><li> Not supported by the Secretariat, developed by the Online Collaboration Dynamic Coalition
</li><li> Single sign-on with OpenID to centralised community Wiki and blog site
</li><li> Shared but manually-maintained links to official and community resources in header menu
</li><li> Flexible support for asynchronous discussion (hybrid mailing lists and Web forum)
</li><li> Limited support for synchronous discussion (IRC channel and Web gateway)
</li><li> Flexible support for collaborative editing (wiki)
</li><li> No support for decision-making or social networking
</li><li> <a href="http://igf-online.net/gregarius" class="external text" title="http://igf-online.net/gregarius" rel="nofollow">Limited content aggregation</a> (RSS, not enhanced by metadata)
</li><li> Limited multilingualisation support
</li></ul>
<a name="Host_country_sites" id="Host_country_sites"></a><h3>Host country sites</h3>
<ul><li> Static, manually maintained content
</li><li> Do not share data with official or community Web sites
</li><li> No support for any of the forms of online democratic engagement
</li></ul>
<a name="Other" id="Other"></a><h3>Other</h3>
<ul><li> Social networking through unofficial IGF Facebook group
</li><li> Does not share data with official or other community Web sites
</li></ul>
<a name="What_changes_are_required" id="What_changes_are_required"></a><h2>What changes are required</h2>
<a name="Institutional" id="Institutional"></a><h3>Institutional</h3>
<ul><li> It should be possible to register as an IGF stakeholder without attending a meeting in person
</li><li> Rather than the IGF’s plenary activity being limited to an annual meeting that meeting should cap a programme of online intersessional work
</li><li> The official Web site should be unified or closely integrated with community and host country resources
</li><li> Data from the official IGF Web site should be programmatically accessible and tagged for reuse:
<ul><li> User registration details
</li><li> Calendar of events
</li><li> Live transcripts
</li><li> Dynamic coalitions
</li><li> Stakeholder contributions
</li></ul>
</li><li> Funding should be sought for online resources just as it is allocated for the annual meeting
</li></ul>
<a name="Technical" id="Technical"></a><h3>Technical</h3>
<ul><li> Unified registration system for IGF annual meetings, sub-events and IGF online resources
</li><li> Rich ACL providing roles for Secretariat, Advisory Group, Dynamic Coalitions and others
</li><li> Registration details can be shared with community Web sites and events using OpenSocial API
</li><li> <a href="http://bestbits.net/wws/arc/igf-ocdc/2007-02/msg00022.html" class="external text" title="http://bestbits.net/wws/arc/igf-ocdc/2007-02/msg00022.html" rel="nofollow">RSS+Dublin Core metadata engine</a> to unify data from official and community sources
</li><li> Multi-modal online participation should be facilitated where possible (eg. email, Web, RSS)
</li><li> <a href="http://bestbits.net/wws/arc/igf-ocdc/2007-02/msg00045.html" class="external text" title="http://bestbits.net/wws/arc/igf-ocdc/2007-02/msg00045.html" rel="nofollow">Unified set of themes for IGF sites</a> (differentiating between official and community resources)
</li><li> Engine to gate live transcripts to IRC, Jabber, Second Life, etc
</li><li> Event information made available in iCalendar format
</li><li> All workshops and events to have access to integrated online fora
</li><li> Extension and unification of existing facilities for asynchronous and synchronous discussion
</li><li> Extension of existing facilities for collaborative editing (eg. add polling support)
</li></ul>
<a name="Social" id="Social"></a><h3>Social</h3>
<ul><li> Appointed volunteer rapporteurs to bridge online and offline fora
</li><li> Outreach programme to existing online communities of Internet users
</li><li> Capacity building for government stakeholders in the use of online resources
</li></ul>

Français:
<p>This is a draft requirements document for building an online community for the IGF, at least equivalent to those of other Internet governance institutions such as the IETF etc. The focus here is not on remote participation, which although also important, is being dealt with <a href="http://www.igfremote.com/" class="external text" title="http://www.igfremote.com/" rel="nofollow">elsewhere</a>. Discussion can take place <a href="http://igf-online.net/wws/info/igf-ocdc" class="external text" title="http://igf-online.net/wws/info/igf-ocdc" rel="nofollow">here</a>.
</p>
<table id="toc" class="toc" summary="Contents"><tr><td><div id="toctitle"><h2>Contents</h2></div>
<ul>
<li class="toclevel-1"><a href="#Draft_timetable"><span class="tocnumber">1</span> <span class="toctext">Draft timetable</span></a></li>
<li class="toclevel-1"><a href="#Rationale"><span class="tocnumber">2</span> <span class="toctext">Rationale</span></a></li>
<li class="toclevel-1"><a href="#What_the_IGF_already_has"><span class="tocnumber">3</span> <span class="toctext">What the IGF already has</span></a>
<ul>
<li class="toclevel-2"><a href="#Official_Web_site"><span class="tocnumber">3.1</span> <span class="toctext">Official Web site</span></a></li>
<li class="toclevel-2"><a href="#IGF_Community_Site"><span class="tocnumber">3.2</span> <span class="toctext">IGF Community Site</span></a></li>
<li class="toclevel-2"><a href="#Host_country_sites"><span class="tocnumber">3.3</span> <span class="toctext">Host country sites</span></a></li>
<li class="toclevel-2"><a href="#Other"><span class="tocnumber">3.4</span> <span class="toctext">Other</span></a></li>
</ul>
</li>
<li class="toclevel-1"><a href="#What_changes_are_required"><span class="tocnumber">4</span> <span class="toctext">What changes are required</span></a>
<ul>
<li class="toclevel-2"><a href="#Institutional"><span class="tocnumber">4.1</span> <span class="toctext">Institutional</span></a></li>
<li class="toclevel-2"><a href="#Technical"><span class="tocnumber">4.2</span> <span class="toctext">Technical</span></a></li>
<li class="toclevel-2"><a href="#Social"><span class="tocnumber">4.3</span> <span class="toctext">Social</span></a></li>
</ul>
</li>
</ul>
</td></tr></table><script type="text/javascript"> if (window.showTocToggle) { var tocShowText = "show"; var tocHideText = "hide"; showTocToggle(); } </script>
<a name="Draft_timetable" id="Draft_timetable"></a><h2>Draft timetable</h2>
<table class="wikitable">

<tr>
<td> 30 June 2008
</td><td> Document open for editing on the wiki
</td></tr>
<tr>
<td> 1 July 2008
</td><td> Final document posted for a consensus call to <a href="http://igf-online.net/wws/info/igf-ocdc" class="external text" title="http://igf-online.net/wws/info/igf-ocdc" rel="nofollow">[email protected]</a>
</td></tr>
<tr>
<td> 7 July 2008
</td><td> Close of consensus call with Apache-style "lazy consensus" (a few positive votes with no abstentions)
</td></tr>
<tr>
<td> 8 July 2008
</td><td> Finalised requirements document sent to developers for quotes (note: free is also a quote)
</td></tr>
<tr>
<td> 8 August 2008
</td><td> Closure of deadline for quotes
</td></tr>
<tr>
<td> 10 August 2008
</td><td> OCDC selects a recommended quote and forwards all documents to the Secretariat for endorsement
</td></tr>
<tr>
<td> September 2008
</td><td> If necessary, documents presented at open consultation and call for donations to cover development cost
</td></tr></table>
<a name="Rationale" id="Rationale"></a><h2>Rationale</h2>
<p>The establishment of the IGF was an ambitious innovation in global governance for the Internet. Whereas earlier Internet governance institutions such as the IETF, the RIRs, and to some extent ICANN, emerged largely from the grassroots of the Internet technical community and utilised principally online working methods from the outset, the IGF is the first new Internet governance institution to be structured principally as a face-to-face annual meeting, and aside from the activities of its dynamic coalitions, it remains set in that form.
</p><p>Whilst this may have provided a more natural means of engagement for some stakeholders from outside the Internet technical community, it has distanced the IGF from ordinary Internet users and limited its potential to draw in the breadth of community engagement that the other Internet governance institutions mentioned above have enjoyed. Thus even when mechanisms such as Webcasting have been provided to bridge the annual meeting with online users, these have been underutilised because remote users have not felt part of the same community as those meeting in person.
</p><p>To improve the mechanisms of remote participation made available by the IGF therefore only addresses part of the problem. What is more important is that the IGF produce a virtual community to motivate a broad cross-section of users, including those who cannot afford to attend the annual meetings, to participate actively and enthusiastically in year-round policy dialogue. In short, the IGF must welcome online discourse as a principal means of engagement in its activities, not merely as an adjunct to its discrete annual meetings.
</p><p>To date, the IGF has fallen short in this. Where other Internet governance institutions host vibrant and effective virtual discussions that benefit from the unique discursive properties of the online environment, the IGF does not. The development of such a virtual community for the IGF has been limited by a number of factors, and it is the purpose of this requirements document to set those out, and to sketch the institutional, technical and social modifications that the IGF should commit to if it wishes to foster the development of a more engaging online environment for the IGF community.
</p>
<a name="What_the_IGF_already_has" id="What_the_IGF_already_has"></a><h2>What the IGF already has</h2>
<a name="Official_Web_site" id="Official_Web_site"></a><h3>Official Web site</h3>
<ul><li> Static pages, manually maintained navigation and ad-hoc archival
</li><li> Manually maintained ACL for event organisers to update event information
</li><li> Semi-automated management of event information
</li><li> No programmatic access to metadata such as calendar files
</li><li> Interactivity limited to a manually maintained RSS feed
</li><li> No site map, search or user-generated content
</li><li> Limited support for asynchronous discussion (the official Web forum)
</li><li> Limited support for synchronous discussion (the official Webcast and chat client)
</li><li> No support for collaborative editing, decision-making, social networking or multilingualisation
</li></ul>
<a name="IGF_Community_Site" id="IGF_Community_Site"></a><h3><a href="http://igf-online.net/" class="external text" title="http://igf-online.net/" eel="nofollow">IGF Community Site</a></h3>
<ul><li> Not supported by the Secretariat, developed by the Online Collaboration Dynamic Coalition
</li><li> Single sign-on with OpenID to centralised community Wiki and blog site
</li><li> Shared but manually-maintained links to official and community resources in header menu
</li><li> Flexible support for asynchronous discussion (hybrid mailing lists and Web forum)
</li><li> Limited support for synchronous discussion (IRC channel and Web gateway)
</li><li> Flexible support for collaborative editing (wiki)
</li><li> No support for decision-making or social networking
</li><li> <a href="http://igf-online.net/gregarius" class="external text" title="http://igf-online.net/gregarius" rel="nofollow">Limited content aggregation</a> (RSS, not enhanced by metadata)
</li><li> Limited multilingualisation support
</li></ul>
<a name="Host_country_sites" id="Host_country_sites"></a><h3>Host country sites</h3>
<ul><li> Static, manually maintained content
</li><li> Do not share data with official or community Web sites
</li><li> No support for any of the forms of online democratic engagement
</li></ul>
<a name="Other" id="Other"></a><h3>Other</h3>
<ul><li> Social networking through unofficial IGF Facebook group
</li><li> Does not share data with official or other community Web sites
</li></ul>
<a name="What_changes_are_required" id="What_changes_are_required"></a><h2>What changes are required</h2>
<a name="Institutional" id="Institutional"></a><h3>Institutional</h3>
<ul><li> It should be possible to register as an IGF stakeholder without attending a meeting in person
</li><li> Rather than the IGF’s plenary activity being limited to an annual meeting that meeting should cap a programme of online intersessional work
</li><li> The official Web site should be unified or closely integrated with community and host country resources
</li><li> Data from the official IGF Web site should be programmatically accessible and tagged for reuse:
<ul><li> User registration details
</li><li> Calendar of events
</li><li> Live transcripts
</li><li> Dynamic coalitions
</li><li> Stakeholder contributions
</li></ul>
</li><li> Funding should be sought for online resources just as it is allocated for the annual meeting
</li></ul>
<a name="Technical" id="Technical"></a><h3>Technical</h3>
<ul><li> Unified registration system for IGF annual meetings, sub-events and IGF online resources
</li><li> Rich ACL providing roles for Secretariat, Advisory Group, Dynamic Coalitions and others
</li><li> Registration details can be shared with community Web sites and events using OpenSocial API
</li><li> <a href="http://bestbits.net/wws/arc/igf-ocdc/2007-02/msg00022.html" class="external text" title="http://bestbits.net/wws/arc/igf-ocdc/2007-02/msg00022.html" rel="nofollow">RSS+Dublin Core metadata engine</a> to unify data from official and community sources
</li><li> Multi-modal online participation should be facilitated where possible (eg. email, Web, RSS)
</li><li> <a href="http://bestbits.net/wws/arc/igf-ocdc/2007-02/msg00045.html" class="external text" title="http://bestbits.net/wws/arc/igf-ocdc/2007-02/msg00045.html" rel="nofollow">Unified set of themes for IGF sites</a> (differentiating between official and community resources)
</li><li> Engine to gate live transcripts to IRC, Jabber, Second Life, etc
</li><li> Event information made available in iCalendar format
</li><li> All workshops and events to have access to integrated online fora
</li><li> Extension and unification of existing facilities for asynchronous and synchronous discussion
</li><li> Extension of existing facilities for collaborative editing (eg. add polling support)
</li></ul>
<a name="Social" id="Social"></a><h3>Social</h3>
<ul><li> Appointed volunteer rapporteurs to bridge online and offline fora
</li><li> Outreach programme to existing online communities of Internet users
</li><li> Capacity building for government stakeholders in the use of online resources
</li></ul>

Español:
<p>This is a draft requirements document for building an online community for the IGF, at least equivalent to those of other Internet governance institutions such as the IETF etc. The focus here is not on remote participation, which although also important, is being dealt with <a href="http://www.igfremote.com/" class="external text" title="http://www.igfremote.com/" rel="nofollow">elsewhere</a>. Discussion can take place <a href="http://igf-online.net/wws/info/igf-ocdc" class="external text" title="http://igf-online.net/wws/info/igf-ocdc" rel="nofollow">here</a>.
</p>
<table id="toc" class="toc" summary="Contents"><tr><td><div id="toctitle"><h2>Contents</h2></div>
<ul>
<li class="toclevel-1"><a href="#Draft_timetable"><span class="tocnumber">1</span> <span class="toctext">Draft timetable</span></a></li>
<li class="toclevel-1"><a href="#Rationale"><span class="tocnumber">2</span> <span class="toctext">Rationale</span></a></li>
<li class="toclevel-1"><a href="#What_the_IGF_already_has"><span class="tocnumber">3</span> <span class="toctext">What the IGF already has</span></a>
<ul>
<li class="toclevel-2"><a href="#Official_Web_site"><span class="tocnumber">3.1</span> <span class="toctext">Official Web site</span></a></li>
<li class="toclevel-2"><a href="#IGF_Community_Site"><span class="tocnumber">3.2</span> <span class="toctext">IGF Community Site</span></a></li>
<li class="toclevel-2"><a href="#Host_country_sites"><span class="tocnumber">3.3</span> <span class="toctext">Host country sites</span></a></li>
<li class="toclevel-2"><a href="#Other"><span class="tocnumber">3.4</span> <span class="toctext">Other</span></a></li>
</ul>
</li>
<li class="toclevel-1"><a href="#What_changes_are_required"><span class="tocnumber">4</span> <span class="toctext">What changes are required</span></a>
<ul>
<li class="toclevel-2"><a href="#Institutional"><span class="tocnumber">4.1</span> <span class="toctext">Institutional</span></a></li>
<li class="toclevel-2"><a href="#Technical"><span class="tocnumber">4.2</span> <span class="toctext">Technical</span></a></li>
<li class="toclevel-2"><a href="#Social"><span class="tocnumber">4.3</span> <span class="toctext">Social</span></a></li>
</ul>
</li>
</ul>
</td></tr></table><script type="text/javascript"> if (window.showTocToggle) { var tocShowText = "show"; var tocHideText = "hide"; showTocToggle(); } </script>
<a name="Draft_timetable" id="Draft_timetable"></a><h2>Draft timetable</h2>
<table class="wikitable">

<tr>
<td> 30 June 2008
</td><td> Document open for editing on the wiki
</td></tr>
<tr>
<td> 1 July 2008
</td><td> Final document posted for a consensus call to <a href="http://igf-online.net/wws/info/igf-ocdc" class="external text" title="http://igf-online.net/wws/info/igf-ocdc" rel="nofollow">[email protected]</a>
</td></tr>
<tr>
<td> 7 July 2008
</td><td> Close of consensus call with Apache-style "lazy consensus" (a few positive votes with no abstentions)
</td></tr>
<tr>
<td> 8 July 2008
</td><td> Finalised requirements document sent to developers for quotes (note: free is also a quote)
</td></tr>
<tr>
<td> 8 August 2008
</td><td> Closure of deadline for quotes
</td></tr>
<tr>
<td> 10 August 2008
</td><td> OCDC selects a recommended quote and forwards all documents to the Secretariat for endorsement
</td></tr>
<tr>
<td> September 2008
</td><td> If necessary, documents presented at open consultation and call for donations to cover development cost
</td></tr></table>
<a name="Rationale" id="Rationale"></a><h2>Rationale</h2>
<p>The establishment of the IGF was an ambitious innovation in global governance for the Internet. Whereas earlier Internet governance institutions such as the IETF, the RIRs, and to some extent ICANN, emerged largely from the grassroots of the Internet technical community and utilised principally online working methods from the outset, the IGF is the first new Internet governance institution to be structured principally as a face-to-face annual meeting, and aside from the activities of its dynamic coalitions, it remains set in that form.
</p><p>Whilst this may have provided a more natural means of engagement for some stakeholders from outside the Internet technical community, it has distanced the IGF from ordinary Internet users and limited its potential to draw in the breadth of community engagement that the other Internet governance institutions mentioned above have enjoyed. Thus even when mechanisms such as Webcasting have been provided to bridge the annual meeting with online users, these have been underutilised because remote users have not felt part of the same community as those meeting in person.
</p><p>To improve the mechanisms of remote participation made available by the IGF therefore only addresses part of the problem. What is more important is that the IGF produce a virtual community to motivate a broad cross-section of users, including those who cannot afford to attend the annual meetings, to participate actively and enthusiastically in year-round policy dialogue. In short, the IGF must welcome online discourse as a principal means of engagement in its activities, not merely as an adjunct to its discrete annual meetings.
</p><p>To date, the IGF has fallen short in this. Where other Internet governance institutions host vibrant and effective virtual discussions that benefit from the unique discursive properties of the online environment, the IGF does not. The development of such a virtual community for the IGF has been limited by a number of factors, and it is the purpose of this requirements document to set those out, and to sketch the institutional, technical and social modifications that the IGF should commit to if it wishes to foster the development of a more engaging online environment for the IGF community.
</p>
<a name="What_the_IGF_already_has" id="What_the_IGF_already_has"></a><h2>What the IGF already has</h2>
<a name="Official_Web_site" id="Official_Web_site"></a><h3>Official Web site</h3>
<ul><li> Static pages, manually maintained navigation and ad-hoc archival
</li><li> Manually maintained ACL for event organisers to update event information
</li><li> Semi-automated management of event information
</li><li> No programmatic access to metadata such as calendar files
</li><li> Interactivity limited to a manually maintained RSS feed
</li><li> No site map, search or user-generated content
</li><li> Limited support for asynchronous discussion (the official Web forum)
</li><li> Limited support for synchronous discussion (the official Webcast and chat client)
</li><li> No support for collaborative editing, decision-making, social networking or multilingualisation
</li></ul>
<a name="IGF_Community_Site" id="IGF_Community_Site"></a><h3><a href="http://igf-online.net/" class="external text" title="http://igf-online.net/" eel="nofollow">IGF Community Site</a></h3>
<ul><li> Not supported by the Secretariat, developed by the Online Collaboration Dynamic Coalition
</li><li> Single sign-on with OpenID to centralised community Wiki and blog site
</li><li> Shared but manually-maintained links to official and community resources in header menu
</li><li> Flexible support for asynchronous discussion (hybrid mailing lists and Web forum)
</li><li> Limited support for synchronous discussion (IRC channel and Web gateway)
</li><li> Flexible support for collaborative editing (wiki)
</li><li> No support for decision-making or social networking
</li><li> <a href="http://igf-online.net/gregarius" class="external text" title="http://igf-online.net/gregarius" rel="nofollow">Limited content aggregation</a> (RSS, not enhanced by metadata)
</li><li> Limited multilingualisation support
</li></ul>
<a name="Host_country_sites" id="Host_country_sites"></a><h3>Host country sites</h3>
<ul><li> Static, manually maintained content
</li><li> Do not share data with official or community Web sites
</li><li> No support for any of the forms of online democratic engagement
</li></ul>
<a name="Other" id="Other"></a><h3>Other</h3>
<ul><li> Social networking through unofficial IGF Facebook group
</li><li> Does not share data with official or other community Web sites
</li></ul>
<a name="What_changes_are_required" id="What_changes_are_required"></a><h2>What changes are required</h2>
<a name="Institutional" id="Institutional"></a><h3>Institutional</h3>
<ul><li> It should be possible to register as an IGF stakeholder without attending a meeting in person
</li><li> Rather than the IGF’s plenary activity being limited to an annual meeting that meeting should cap a programme of online intersessional work
</li><li> The official Web site should be unified or closely integrated with community and host country resources
</li><li> Data from the official IGF Web site should be programmatically accessible and tagged for reuse:
<ul><li> User registration details
</li><li> Calendar of events
</li><li> Live transcripts
</li><li> Dynamic coalitions
</li><li> Stakeholder contributions
</li></ul>
</li><li> Funding should be sought for online resources just as it is allocated for the annual meeting
</li></ul>
<a name="Technical" id="Technical"></a><h3>Technical</h3>
<ul><li> Unified registration system for IGF annual meetings, sub-events and IGF online resources
</li><li> Rich ACL providing roles for Secretariat, Advisory Group, Dynamic Coalitions and others
</li><li> Registration details can be shared with community Web sites and events using OpenSocial API
</li><li> <a href="http://bestbits.net/wws/arc/igf-ocdc/2007-02/msg00022.html" class="external text" title="http://bestbits.net/wws/arc/igf-ocdc/2007-02/msg00022.html" rel="nofollow">RSS+Dublin Core metadata engine</a> to unify data from official and community sources
</li><li> Multi-modal online participation should be facilitated where possible (eg. email, Web, RSS)
</li><li> <a href="http://bestbits.net/wws/arc/igf-ocdc/2007-02/msg00045.html" class="external text" title="http://bestbits.net/wws/arc/igf-ocdc/2007-02/msg00045.html" rel="nofollow">Unified set of themes for IGF sites</a> (differentiating between official and community resources)
</li><li> Engine to gate live transcripts to IRC, Jabber, Second Life, etc
</li><li> Event information made available in iCalendar format
</li><li> All workshops and events to have access to integrated online fora
</li><li> Extension and unification of existing facilities for asynchronous and synchronous discussion
</li><li> Extension of existing facilities for collaborative editing (eg. add polling support)
</li></ul>
<a name="Social" id="Social"></a><h3>Social</h3>
<ul><li> Appointed volunteer rapporteurs to bridge online and offline fora
</li><li> Outreach programme to existing online communities of Internet users
</li><li> Capacity building for government stakeholders in the use of online resources
</li></ul>

한국어:
<p>This is a draft requirements document for building an online community for the IGF, at least equivalent to those of other Internet governance institutions such as the IETF etc. The focus here is not on remote participation, which although also important, is being dealt with <a href="http://www.igfremote.com/" class="external text" title="http://www.igfremote.com/" rel="nofollow">elsewhere</a>. Discussion can take place <a href="http://igf-online.net/wws/info/igf-ocdc" class="external text" title="http://igf-online.net/wws/info/igf-ocdc" rel="nofollow">here</a>.
</p>
<table id="toc" class="toc" summary="Contents"><tr><td><div id="toctitle"><h2>Contents</h2></div>
<ul>
<li class="toclevel-1"><a href="#Draft_timetable"><span class="tocnumber">1</span> <span class="toctext">Draft timetable</span></a></li>
<li class="toclevel-1"><a href="#Rationale"><span class="tocnumber">2</span> <span class="toctext">Rationale</span></a></li>
<li class="toclevel-1"><a href="#What_the_IGF_already_has"><span class="tocnumber">3</span> <span class="toctext">What the IGF already has</span></a>
<ul>
<li class="toclevel-2"><a href="#Official_Web_site"><span class="tocnumber">3.1</span> <span class="toctext">Official Web site</span></a></li>
<li class="toclevel-2"><a href="#IGF_Community_Site"><span class="tocnumber">3.2</span> <span class="toctext">IGF Community Site</span></a></li>
<li class="toclevel-2"><a href="#Host_country_sites"><span class="tocnumber">3.3</span> <span class="toctext">Host country sites</span></a></li>
<li class="toclevel-2"><a href="#Other"><span class="tocnumber">3.4</span> <span class="toctext">Other</span></a></li>
</ul>
</li>
<li class="toclevel-1"><a href="#What_changes_are_required"><span class="tocnumber">4</span> <span class="toctext">What changes are required</span></a>
<ul>
<li class="toclevel-2"><a href="#Institutional"><span class="tocnumber">4.1</span> <span class="toctext">Institutional</span></a></li>
<li class="toclevel-2"><a href="#Technical"><span class="tocnumber">4.2</span> <span class="toctext">Technical</span></a></li>
<li class="toclevel-2"><a href="#Social"><span class="tocnumber">4.3</span> <span class="toctext">Social</span></a></li>
</ul>
</li>
</ul>
</td></tr></table><script type="text/javascript"> if (window.showTocToggle) { var tocShowText = "show"; var tocHideText = "hide"; showTocToggle(); } </script>
<a name="Draft_timetable" id="Draft_timetable"></a><h2>Draft timetable</h2>
<table class="wikitable">

<tr>
<td> 30 June 2008
</td><td> Document open for editing on the wiki
</td></tr>
<tr>
<td> 1 July 2008
</td><td> Final document posted for a consensus call to <a href="http://igf-online.net/wws/info/igf-ocdc" class="external text" title="http://igf-online.net/wws/info/igf-ocdc" rel="nofollow">[email protected]</a>
</td></tr>
<tr>
<td> 7 July 2008
</td><td> Close of consensus call with Apache-style "lazy consensus" (a few positive votes with no abstentions)
</td></tr>
<tr>
<td> 8 July 2008
</td><td> Finalised requirements document sent to developers for quotes (note: free is also a quote)
</td></tr>
<tr>
<td> 8 August 2008
</td><td> Closure of deadline for quotes
</td></tr>
<tr>
<td> 10 August 2008
</td><td> OCDC selects a recommended quote and forwards all documents to the Secretariat for endorsement
</td></tr>
<tr>
<td> September 2008
</td><td> If necessary, documents presented at open consultation and call for donations to cover development cost
</td></tr></table>
<a name="Rationale" id="Rationale"></a><h2>Rationale</h2>
<p>The establishment of the IGF was an ambitious innovation in global governance for the Internet. Whereas earlier Internet governance institutions such as the IETF, the RIRs, and to some extent ICANN, emerged largely from the grassroots of the Internet technical community and utilised principally online working methods from the outset, the IGF is the first new Internet governance institution to be structured principally as a face-to-face annual meeting, and aside from the activities of its dynamic coalitions, it remains set in that form.
</p><p>Whilst this may have provided a more natural means of engagement for some stakeholders from outside the Internet technical community, it has distanced the IGF from ordinary Internet users and limited its potential to draw in the breadth of community engagement that the other Internet governance institutions mentioned above have enjoyed. Thus even when mechanisms such as Webcasting have been provided to bridge the annual meeting with online users, these have been underutilised because remote users have not felt part of the same community as those meeting in person.
</p><p>To improve the mechanisms of remote participation made available by the IGF therefore only addresses part of the problem. What is more important is that the IGF produce a virtual community to motivate a broad cross-section of users, including those who cannot afford to attend the annual meetings, to participate actively and enthusiastically in year-round policy dialogue. In short, the IGF must welcome online discourse as a principal means of engagement in its activities, not merely as an adjunct to its discrete annual meetings.
</p><p>To date, the IGF has fallen short in this. Where other Internet governance institutions host vibrant and effective virtual discussions that benefit from the unique discursive properties of the online environment, the IGF does not. The development of such a virtual community for the IGF has been limited by a number of factors, and it is the purpose of this requirements document to set those out, and to sketch the institutional, technical and social modifications that the IGF should commit to if it wishes to foster the development of a more engaging online environment for the IGF community.
</p>
<a name="What_the_IGF_already_has" id="What_the_IGF_already_has"></a><h2>What the IGF already has</h2>
<a name="Official_Web_site" id="Official_Web_site"></a><h3>Official Web site</h3>
<ul><li> Static pages, manually maintained navigation and ad-hoc archival
</li><li> Manually maintained ACL for event organisers to update event information
</li><li> Semi-automated management of event information
</li><li> No programmatic access to metadata such as calendar files
</li><li> Interactivity limited to a manually maintained RSS feed
</li><li> No site map, search or user-generated content
</li><li> Limited support for asynchronous discussion (the official Web forum)
</li><li> Limited support for synchronous discussion (the official Webcast and chat client)
</li><li> No support for collaborative editing, decision-making, social networking or multilingualisation
</li></ul>
<a name="IGF_Community_Site" id="IGF_Community_Site"></a><h3><a href="http://igf-online.net/" class="external text" title="http://igf-online.net/" eel="nofollow">IGF Community Site</a></h3>
<ul><li> Not supported by the Secretariat, developed by the Online Collaboration Dynamic Coalition
</li><li> Single sign-on with OpenID to centralised community Wiki and blog site
</li><li> Shared but manually-maintained links to official and community resources in header menu
</li><li> Flexible support for asynchronous discussion (hybrid mailing lists and Web forum)
</li><li> Limited support for synchronous discussion (IRC channel and Web gateway)
</li><li> Flexible support for collaborative editing (wiki)
</li><li> No support for decision-making or social networking
</li><li> <a href="http://igf-online.net/gregarius" class="external text" title="http://igf-online.net/gregarius" rel="nofollow">Limited content aggregation</a> (RSS, not enhanced by metadata)
</li><li> Limited multilingualisation support
</li></ul>
<a name="Host_country_sites" id="Host_country_sites"></a><h3>Host country sites</h3>
<ul><li> Static, manually maintained content
</li><li> Do not share data with official or community Web sites
</li><li> No support for any of the forms of online democratic engagement
</li></ul>
<a name="Other" id="Other"></a><h3>Other</h3>
<ul><li> Social networking through unofficial IGF Facebook group
</li><li> Does not share data with official or other community Web sites
</li></ul>
<a name="What_changes_are_required" id="What_changes_are_required"></a><h2>What changes are required</h2>
<a name="Institutional" id="Institutional"></a><h3>Institutional</h3>
<ul><li> It should be possible to register as an IGF stakeholder without attending a meeting in person
</li><li> Rather than the IGF’s plenary activity being limited to an annual meeting that meeting should cap a programme of online intersessional work
</li><li> The official Web site should be unified or closely integrated with community and host country resources
</li><li> Data from the official IGF Web site should be programmatically accessible and tagged for reuse:
<ul><li> User registration details
</li><li> Calendar of events
</li><li> Live transcripts
</li><li> Dynamic coalitions
</li><li> Stakeholder contributions
</li></ul>
</li><li> Funding should be sought for online resources just as it is allocated for the annual meeting
</li></ul>
<a name="Technical" id="Technical"></a><h3>Technical</h3>
<ul><li> Unified registration system for IGF annual meetings, sub-events and IGF online resources
</li><li> Rich ACL providing roles for Secretariat, Advisory Group, Dynamic Coalitions and others
</li><li> Registration details can be shared with community Web sites and events using OpenSocial API
</li><li> <a href="http://bestbits.net/wws/arc/igf-ocdc/2007-02/msg00022.html" class="external text" title="http://bestbits.net/wws/arc/igf-ocdc/2007-02/msg00022.html" rel="nofollow">RSS+Dublin Core metadata engine</a> to unify data from official and community sources
</li><li> Multi-modal online participation should be facilitated where possible (eg. email, Web, RSS)
</li><li> <a href="http://bestbits.net/wws/arc/igf-ocdc/2007-02/msg00045.html" class="external text" title="http://bestbits.net/wws/arc/igf-ocdc/2007-02/msg00045.html" rel="nofollow">Unified set of themes for IGF sites</a> (differentiating between official and community resources)
</li><li> Engine to gate live transcripts to IRC, Jabber, Second Life, etc
</li><li> Event information made available in iCalendar format
</li><li> All workshops and events to have access to integrated online fora
</li><li> Extension and unification of existing facilities for asynchronous and synchronous discussion
</li><li> Extension of existing facilities for collaborative editing (eg. add polling support)
</li></ul>
<a name="Social" id="Social"></a><h3>Social</h3>
<ul><li> Appointed volunteer rapporteurs to bridge online and offline fora
</li><li> Outreach programme to existing online communities of Internet users
</li><li> Capacity building for government stakeholders in the use of online resources
</li></ul>