sweoig-charter.html 12 KB
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
  <meta http-equiv="content-type" content="text/html; charset=UTF-8" />
  <title>Semantic Web Education and Outreach Interest Group Charter</title>
  <link href="/StyleSheets/base.css" rel="stylesheet" type="text/css" />
  <link href="/2001/sw/swstyle" rel="stylesheet" type="text/css" />
</head>

<body>
<p class="banner"><a href="/" accesskey="W"><img src="/Icons/w3c_home"
width="72" height="48" alt="W3C" />
</a> <a href="/TandS/" accesskey="D"><img src="/Icons/tands" width="212"
height="48" alt="Technology and Society Domain" />
</a> <a href="/2001/sw/"><img src="/2001/sw/sw"
alt="The Semantic Web Home Page" />
</a></p>

<h1>Semantic Web Education and Outreach Interest Group</h1>

<p>The Semantic Web Education and Outreach (SWEO) Interest Group has been
established to develop strategies and materials to increase awareness among
the Web community of the need and benefit for the Semantic Web, and educate
the Web community regarding related solutions and technologies.</p>

<h2>Contents</h2>
<ol>
  <li><a href="#Scope">Scope</a></li>
  <li><a href="#deliverables">Deliverables</a></li>
  <li><a href="#schedule">Schedule</a></li>
  <li><a href="#x-rel">Relationship with Other Activities</a></li>
  <li><a href="#membership">Group Membership</a></li>
  <li><a href="#Meetings">Meetings and Communication</a></li>
  <li><a href="#pd">Patent Disclosures</a></li>
  <li><a href="#resources">Resources and W3C Team Involvement</a></li>
</ol>
<hr />

<div class="main">
<h2><a id="scope" name="scope">Scope</a></h2>

<p>The scope of SWEO group includes:</p>
<ul>
  <li>The development and maintenance of a variety of online and hard-copy
    education and outreach resources, such as tutorial, business cases,
    Semantic Web flyers, curricula, fact sheets, reference link pages,
    demonstration materials, introductory pages, etc.;</li>
  <li>To development and facilitate community outreach strategies, training
    and educational resources and expanded course offerings in Semantic Web
    technologies.</li>
  <li>The consultation with other Semantic Web groups to identify outreach
    needs; to develop strategies and resources to address those needs, and to
    advise on ease-of-use of other Semantic Web groups' deliverables,
    including presentation of information (structure, style, semantics)
    across all areas of the W3C's Semantic Web Activity</li>
</ul>
</div>

<div class="main">
<h2><a id="deliverables" name="deliverables">Deliverables</a></h2>

<p>SWEO group deliverables will include organization of symposiums, workshops
and summits that help educate the market, as well as documents reflecting the
Outreach needs identified by the Interest Group. One specific outreach
objective would be the organization of a CIO/CTO Symposium focused on
bringing together leaders in organizations using and / or interested in
applying Semantic Web technologies to the enterprise. The specific foci of
other events will be centered around the themes of the Interest Group task
forces. These task forces will typically operate in the following way:</p>
<ul>
  <li>The time frame of a task force is short-term, e.g. 4 (2-6) months</li>
  <li>The editors/coordinators of a task force are selected from the Interest
    Group participants</li>
  <li>A task force may recommend non-Member individuals with relevant skills
    to participate in the task force as invited experts. The <a
    href="http://www.w3.org/2004/08/invexp.html">normal invited expert
    process</a> will be followed. Final decision on any task force issue
    rests with member of the Interest Group.</li>
  <li>The task force will use the regular Interest Group communication
    channels.</li>
  <li>The result of this work is proposed to the full Interest Group for
    consideration and discussion on next steps.</li>
</ul>

<p>SWEO deliverables the task forces might address include but are not
limited to the following types of materials and events:</p>
<ul>
  <li><a name="Reaching" id="Reaching">Reaching out</a> to industry through
    documented proof-of-concept business cases, demonstration prototypes,
    etc, based on successful implementations of Semantic Web technologies</li>
  <li>A collection of Semantic Web presentations designed to communicate the
    features and benefits of the Semantic Web within their own
  organization.</li>
  <li>A resources page including comprehensive collections of Semantic Web
    tools, technologies, examples and projects.</li>
  <li>Presentation of business cases, materials and information targeted at
    various business levels regarding Semantic Web technologies</li>
  <li>Introductory references focused to help individuals and organizations
    start using Semantic Web technologies, making a Semantic Web Site and
    planning Semantic Web training</li>
  <li>Resource networks including outreach, training and education
  exchanges.</li>
</ul>

<p>SWEO document deliverables become W3C Notes. The focus of this work is
informational in nature, rather than technical specifications. SWEO
deliverables must be consensus-based, technically sound, and reflect the most
current W3C specifications.</p>

<h2><a id="schedule" name="schedule">Schedule</a></h2>

<p>The schedule for these deliverables represent an initial plan. As more
information becomes available, milestones may be renegotiated with the <a
href="/2001/sw/CG/">Semantic Web Coordination Group</a>. Schedule changes
that impact resource allocations are charter changes that require Advisory
Committee review.</p>
<ul>
  <li>July 2006 - Group Formation. W3C Members with relevant interest and
    expertise join the interest group. The chair may elect to invite non-W3C
    experts.</li>
  <li>August 2006 - Face to Face meeting to prioritize objectives and
    establish a strategy for delivering.</li>
  <li>Oct 2006 - First Interest Group deliverables expected to be
  published.</li>
  <li>Jan 2007 - Face to Face meeting to re-prioritize objectives and
    establish a strategy for delivering.</li>
  <li>March 2007 - CIO / CTO Symposium</li>
  <li>April 2007 - Face to Face meeting to re-prioritize objectives and
    establish a strategy for delivering.</li>
  <li>July 2007 - Interest Group deliverables expected to be published.</li>
  <li>Sept 2007 - Face to Face meeting to re-prioritize objectives and
    establish a strategy for delivering.</li>
  <li>Jan 2008 - Interest Group deliverables expected to be published.</li>
  <li>Febr 2008 - The SWEO Interest group ends.</li>
</ul>
</div>

<h2><a id="x-rel">Relationship with Other Activities</a></h2>

<p>In order to be most successful, the SWEO Interest Group will coordinate
with various W3C and non-W3C related groups working in similar areas. These
groups include:</p>
<ul>
  <li><a href="/2001/sw/interest/">W3C Semantic Web Interest Group</a> -
    which is a public forum to discuss the use and development of the
    Semantic Web.</li>
  <li><a href="/2001/sw/hcls/">W3C Semantic Web Health Care and Life Sciences
    Interest Group</a> - which is a member only interest group designed to
    use Semantic Web technologies to improve collaboration, research and
    development, and innovation adoption in the health care and life science
    industries.</li>
  <li><a href="http://colab.cim3.net/cgi-bin/wiki.pl?SICoP">The Federal CIO
    Council's Semantic Interoperability Community of Practice (SICoP)</a> -
    which is established by a group of individuals for the purpose of
    achieving "semantic interoperability" and "semantic data integration"
    focused on the US government sector.</li>
  <li><a href="http://www.w3.org/2001/di/Group/">Device Independence Working
    Group</a> that uses Semantic Web technologies in several of its work
    items (e.g., CC/PP, Semantic Enrichment for Device Independence)</li>
  <li><a href="http://www.w3.org/Mobile/">Mobile Web Initiative</a> in
    general, and the <a href="http://www.w3.org/2005/MWI/Steer/">Steering
    Council</a> (member only link) of MWI in particular, to ensure that the
    messaging of the Semantic Web and the Mobile Web are synchronized when
    necessary, and that the specific environments of the Mobile Web are also
    taken into consideration in the general messaging of the Semantic Web</li>
  <li><a href="http://www.w3.org/2005/MWI/DDWG/Group/">MWI Device
    Description</a> working group, that may provide a good use case example
    for Semantic Web applications</li>
</ul>

<p>Coordination with other groups will be managed through the <a
href="http://www.w3.org/2001/sw/CGcharter">Semantic Web Coordination
Group</a>.</p>

<h2><a id="membership">Interest Group Membership</a></h2>

<p>W3C has created the SWEO IG to be an an open, sustainable forum. To help
ensure that the deliverables identified in this charter are produced in a
timely fashion and represent the needs of a variety of communities, we
therefore seek dedicated participation. We anticipate that dedicated
individuals will enable the group to make timely progress, and that the
diverse communities interested in the goals outlined by this charter --
companies, universities, and organizations of various types -- will be
represented in the group.</p>

<p>The SWEO IG therefore welcomes participation from representatives of W3C
Member organizations. To enable a broad spectrum of input, the SWEO IG also
anticipates the active participation of individuals as <a
href="http://www.w3.org/2004/08/invexp">W3C Invited Experts</a> from
universities and organizations. Participation from W3C Members and
non-Members alike will help ensure the goals of this charter are effectively
addressed.</p>

<p>Participation is expected to consume at up to a day a week of each
participant's time.</p>

<h2><a id="Meetings">Meetings and Communication</a></h2>

<p>The SWEO Interest Group is expected to hold weekly conference calls, and
two or three face-to-face meetings. In addition, much of the work of this
Interest Group will be done in <a
href="http://www.w3.org/2004/02/Process-20040205/groups#task-force">task
forces</a>, which may hold additional conference calls or face-to-face
meetings.</p>

<p>Communications of the SWEOG will be public. This includes a public <a
href="/2001/sw/sweo/">home page</a> that records the history of the group and
provides access to <a
href="mailto:public-sweo-ig@w3.org">public-sweo-ig</a><a
href="mailto:public-sweo-ig@w3.org">@w3.org</a> mailing list, ( <a
href="http://lists.w3.org/Archives/Public/public-sweo-ig/latest">discussion
archives</a>, meeting minutes, updated schedule of deliverables, membership
list, and relevant documents and resources).</p>

<p>For <a href="http://www.w3.org/2004/08/invexp">W3C Invited Experts</a>,
access to W3C Member-only information will not be required for participation
in this Interest Group.</p>

<h2><a id="resources">Resources and W3C Team Involvement</a></h2>

<p>To be successful, we expect the Interest Group to have approximately 10 to
15 participating Member organizations and invited experts for its duration.
We also expect a large public review group that will participate in the
mailing list discussions.</p>

<p>The W3C Team expects to dedicate the services of one W3C team member at
20% for the duration of the Interest Group.</p>

<h2><a id="pd">Patent Disclosures</a></h2>

<p>W3C reminds Interest Group participants of their obligation to comply with
patent disclosure obligations as set out in <a
href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">Section
6</a> of the W3C Patent Policy. While the Interest Group does not produce
Recommendation-track documents, when Interest Group participants review
Recommendation-track specifications from Working Groups, the patent
disclosure obligations do apply.</p>
<hr />
<address class="contact">
  <a href="http://www.w3.org/People/Ivan/">Ivan Herman</a>
  &lt;ivan@w3.org&gt;, (W3C) Semantic Web Activity Lead<br />

</address>

<p><small><!-- keep -->
$Id: sweoig-charter.html,v 1.5 2007/09/11 20:21:45 ijacobs Exp $ <!-- /keep-->
</small></p>
</body>
</html>