You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
431 lines
28 KiB
431 lines
28 KiB
<!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" xml:lang="en-US" lang="en-US">
|
|
<head>
|
|
<meta http-equiv="content-type" content="text/html; charset=UTF-8" /><title>RDFa Working Group Charter</title>
|
|
<link rel="stylesheet" href="http://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen" />
|
|
<link rel="stylesheet" type="text/css" href="http://www.w3.org/Guide/pubrules-style.css" />
|
|
<link rel="stylesheet" type="text/css" href="http://www.w3.org/2006/02/charter-style.css" />
|
|
<style type="text/css">
|
|
/*<![CDATA[*/
|
|
li.c2 {list-style: none}
|
|
ul.c1 {font-size: small}
|
|
.status { font-style: italic; font-variant: small-caps; font-size: 120% }
|
|
.atat {background: yellow}
|
|
.new { background: khaki; color: green }
|
|
.deleted { text-decoration: line-through; color: red }
|
|
/*]]>*/
|
|
</style>
|
|
<meta content="Manu Sporny, Ben Adida, Ivan Herman" name="author" />
|
|
</head>
|
|
<body>
|
|
<div id="template">
|
|
<ul id="navbar" class="c1">
|
|
<li><a href="#background">Background</a> </li>
|
|
<li><a href="#scope">Scope</a> </li>
|
|
<li><a href="#deliverables">Deliverables</a> </li>
|
|
<li><a href="#coordination">Dependencies</a> </li>
|
|
<li><a href="#participation">Participation</a> </li>
|
|
<li><a href="#communication">Communication</a> </li>
|
|
<li><a href="#decisions">Decision Policy</a> </li>
|
|
<li><a href="#patentpolicy">Patent Policy</a> </li>
|
|
<li><a href="#about">About this Charter</a> </li>
|
|
</ul>
|
|
<p><a href="http://www.w3.org/" shape="rect">
|
|
<img alt="W3C" src="http://www.w3.org/Icons/w3c_home" height="48" width="72" /></a>
|
|
<a class="domainlogo" href="/TandS/" shape="rect">
|
|
<img src="http://www.w3.org/Icons/tands" alt="Technology and Society Domain" /></a>
|
|
</p>
|
|
|
|
<h1 id="title">RDFa Working Group Charter </h1>
|
|
|
|
<p>The <strong>mission</strong> of the <a href="http://www.w3.org/2010/02/rdfa/">RDFa Working Group</a>
|
|
is to support the developing use of RDFa for embedding structured data
|
|
in Web documents in general. The Working Group will publish W3C Recommendations
|
|
to extend and enhance the currently published RDFa 1.0 documents, including an API. The Working Group
|
|
will also support the <a href="http://www.w3.org/html/wg/">HTML Working Group</a> in its work on
|
|
incorporating RDFa in HTML5 and XHTML5 (as a followup on the the currently
|
|
published <a href="http://www.w3.org/TR/rdfa-in-html/">Working Draft for RDFa 1.0 in HTML5)</a>.
|
|
</p>
|
|
<p>The main directions of RDFa’s enhancements are:</p>
|
|
<ol class="mission">
|
|
<li>specification of an API for RDFa, usable for browsers and XML applications</li>
|
|
<li>updates to the RDFa language that ease the practice of authoring RDFa</li>
|
|
<li>definition of the semantics of RDFa attributes for XML languages in general</li>
|
|
</ol>
|
|
<p class="mission">The goal is to maintain backward compatibility with RDFa 1.0 (although some
|
|
small non-compatible changes with regard to the defaults on XML Literals, may be introduced).
|
|
No radical redefinition of the RDFa language is envisaged.
|
|
</p>
|
|
|
|
<div class="noprint">
|
|
<p class="join"><a href="http://www.w3.org/2004/01/pp-impl/44350/join">Join the RDFa
|
|
Working Group</a>.</p>
|
|
</div>
|
|
<table class="summary-table">
|
|
<tbody>
|
|
<tr id="Duration">
|
|
<th rowspan="1" colspan="1">End date </th>
|
|
<td rowspan="1" colspan="1">31 July 2011 </td>
|
|
</tr>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">Confidentiality </th>
|
|
<td rowspan="1" colspan="1">Proceedings are
|
|
<a href="/2005/10/Process-20051014/comm.html#confidentiality-levels">public</a>
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">Initial Chairs </th>
|
|
<td rowspan="1" colspan="1">Ben Adida (Creative Commons)<br /> Manu Sporny (Digital Bazaar, Inc.)<br />
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">Initial Team Contacts</th>
|
|
<td rowspan="1" colspan="1">Ivan Herman (15%) <br />
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">Usual Meeting Schedule </th>
|
|
<td rowspan="1" colspan="1">Teleconferences: Weekly <br /> Face-to-face: None planned</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
|
|
<div >
|
|
<h2 id="background">Background</h2>
|
|
|
|
<p class="mission">The <a href="http://rdfa.info/about/">RDF in XHTML
|
|
Task Force</a>, jointly managed by the <a href="http://www.w3.org/2006/07/SWD/">Semantic Web Deployment</a>
|
|
and the <a href="http://www.w3.org/MarkUp/">XHTML2</a> Working Groups,
|
|
published <a href="http://www.w3.org/standards/techs/rdfa#w3c_all">two documents</a> in October 2009
|
|
that collectively describe RDFa 1.0. Since the release of these documents, RDFa has enjoyed many
|
|
successes, including a number of independent implementations and the public backing of
|
|
major search engine companies. Deployment by major public institutions, governmental sites, as well
|
|
as private companies, incorporation into CMS systems, etc, have also come to the fore. </p>
|
|
|
|
<p>Although formally defined as a module of XHTML1.1, there is a demand for the adaptation of RDFa to
|
|
newer generations of HTML. Also, the RDFa attribute set has already been adopted by other
|
|
XML applications, including the
|
|
<a href="http://www.w3.org/TR/2008/REC-SVGTiny12-20081222/">SVG 1.2</a> W3C
|
|
Recommendation, the <a href="http://developer.yahoo.com/searchmonkey/smguide/datarss.html">DataRSS</a> format
|
|
proposed by Yahoo, and
|
|
<a href="http://www.oasis-open.org/committees/document.php?document_id=31264">Version 1.2 of the OpenDocument
|
|
(ODF) format</a>. Consequently, there is a need for the consolidation of these developments in the form
|
|
of updated Recommendations.</p>
|
|
</div>
|
|
|
|
|
|
<div class="scope">
|
|
<h2 id="scope">Scope </h2>
|
|
<p>The goal of this Working Group is to make RDFa authoring easier, to ensure continued adoption of
|
|
the technology in HTML, XHTML, and XML, and to help developers to create applications based on RDFa data.
|
|
The main work items to be completed by this Working Group, are:</p>
|
|
<ul>
|
|
<li>Define an RDFa API</li>
|
|
<li>Simplify the RDFa markup where possible. This may include simplification on the usage
|
|
of CURIEs, or definition of predefined attributes for the @rel, @rev or @property attributes. The
|
|
goal is to make RDFa authoring easier for end users.</li>
|
|
<li>Unify and ensure orthogonality of RDFa markup among all languages (HTML, XHTML, and XML in general)</li>
|
|
<li>Maintain the RDFa-in-XHTML specification for bugs/errata</li>
|
|
<li>Maintain RDFa Test Cases across host languages</li>
|
|
<li>Create the necessary environments to maintain and help a growing RDFa community. The goal
|
|
is that this environment would stay active after the Working Group’s charter expiration. This involves:
|
|
<ul>
|
|
<li>creation and maintenance of wiki pages containing reference to implementations, tutorials,
|
|
and other documents</li>
|
|
<li>“cookbook” type documents on the usage of major vocabularies and ontologies for typical
|
|
RDFa applications</li>
|
|
<li>examples of scripting applications using the RDFa ECMAScript API and typical
|
|
ECMAScript libraries like jQuery, Dojo, etc</li>
|
|
</ul>
|
|
<p>Some of these documents may be published as Working Group Notes while others will be kept as Wiki pages
|
|
(to be kept up-to-date by the community).</p>
|
|
</li>
|
|
</ul>
|
|
|
|
<p>The primary target language for the API, as referred to above, is ECMAScript, although other
|
|
languages may also be considered. Wherever appropriate the group should use the
|
|
<a href="http://www.w3.org/TR/WebIDL/">WebIDL</a> formalism to specify its APIs. Also, the API is strictly
|
|
an <em>RDFa API</em>, ie, it does not
|
|
include a generic API for RDF data (“TripleStore API”). At the time of writing this charter, such
|
|
<em>standard</em> TripleStore API does not exist (although several different libraries are in use).
|
|
An RDFa API and a TripleStore API are clearly related. The Working Group will therefore take
|
|
existing APIs into account when working on the RDFa API, and may also document its findings on
|
|
generic TripleStore APIs in a separate Working Group Note. Such note may become a point
|
|
of departure for the standardization of a generic TripleStore API in a different Working Group.
|
|
It is, however, <em>not</em> in the charter of this Working Group to define a general TripleStore
|
|
API Recommendation.</p>
|
|
|
|
<p>Because the RDFa API is not based on any previous RDFa work at W3C, use cases for such API usage should
|
|
be gathered by the Working Group. Beyond influencing the final shape of the API, those use cases could also be
|
|
documented as part of the “RDFa usage cookbook”.</p>
|
|
|
|
<p>The group will also take into account the
|
|
<a href="http://www.w3.org/MarkUp/2008/REC-rdfa-syntax-20081014-errata/">errors on the
|
|
documents reported by the community</a> since the publication of of the RDFa
|
|
documents in October 2009, also archived in the
|
|
<a href="http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/">rdf-in-xhtml</a>
|
|
and <a href="http://lists.w3.org/Archives/Public/public-rdfa/">public-rdfa</a>
|
|
mailing lists.
|
|
</p>
|
|
|
|
<p>Backwards compatibility with RDFa 1.0 is of great importance. That means, in general, that
|
|
all triples that are produced via the
|
|
<a href="http://www.w3.org/TR/rdfa-syntax/">October 2008 version of RDFa</a>, should still be
|
|
generated in the new version. For each new feature, if there is doubt or a
|
|
perceived problem with respect to this, the guideline should be to not include the feature in the set
|
|
of modifications. The only minor feature the Working Group has identified and which may constitute a possible
|
|
exception to this rule, is the default XML Literal generation. (See the
|
|
<a href="http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2009Jul/0159.html">proposal</a> and
|
|
the corresponding thread for details.) </p>
|
|
|
|
<h3>Success Criteria</h3>
|
|
<ul>
|
|
<li>RDFa 1.1 improvements to authoring RDFa</li>
|
|
<li>RDFa API, implementable both by browsers and various ECMAScript libraries</li>
|
|
<li>Successful specification and usage of RDFa in other XML languages</li>
|
|
<li>Up-to-date testing environment for RDFa 1.1</li>
|
|
<li>Minimize and possibly eliminate all divergence between RDFa 1.1 in XHTML1.1, XML dialects and (X)HTML5</li>
|
|
</ul>
|
|
|
|
<h3>Out of Scope</h3>
|
|
<p>The working group does <em>not</em> assert any authority over the deliverables
|
|
of the <a href="http://www.w3.org/html/wg/">HTML Working Group</a>.
|
|
The group will have a strong cooperation with the <a href="http://www.w3.org/html/wg/">HTML Working Group</a>,
|
|
ensuring that the RDFa-in-HTML5 work remains compatible with the output of this group. </p>
|
|
|
|
</div>
|
|
<div>
|
|
<h2 id="deliverables">Deliverables </h2>
|
|
<p>(The titles of the documents are indicative only)</p>
|
|
<ul>
|
|
<li><strong>RDFa 1.1 API, <em>Recommendation</em></strong>:
|
|
This document will define a generic API for accessing RDFa
|
|
data contained in the current page.</li>
|
|
<li><strong>RDFa 1.1 Core, <em>Recommendation</em></strong>:
|
|
This document will specify the common RDFa attribute sets that may be included by other
|
|
languages such as XHTML, HTML, or general XML applications like SVG or ODF.</li>
|
|
<li><strong>RDFa 1.1 in XHTML1.1, <em>Recommendation</em></strong>:
|
|
This document will be based on the RDFa 1.1 Core document and specify RDFa usage in XHTML1.1
|
|
documents.</li>
|
|
<li><strong>RDFa 1.1 Primer, <em>Note</em></strong>: The RDFa Primer document will
|
|
be updated to include RDFa 1.1 modifications.</li>
|
|
<li><strong>RDF TripleStore APIs, <em>Note</em></strong>: Finding of the group
|
|
on generic TripleStore APIs. Publication of this note is optional.</li>
|
|
<li><strong>RDFa Usage Cookbook, <em>Note</em></strong>: Document on the usage of major
|
|
vocabularies and ontologies for typical RDFa applications. Publication of this note is optional.</li>
|
|
</ul>
|
|
|
|
<p>Although not formally part of the deliverables of this group, it is also the goal to strongly
|
|
cooperate with the <a href="http://www.w3.org/html/wg/">HTML Working Group</a> in publishing an
|
|
<strong>RDFa in HTML5</strong> document, in case the decision of the HTML WG is to finalize that
|
|
document as a Recommendation.
|
|
</p>
|
|
<h3 id="milestones">Milestones</h3>
|
|
<table class="roadmap" width="80%">
|
|
<tfoot>
|
|
<tr>
|
|
<td colspan="6" rowspan="1">Note: Dates are based on a charter starting in February 2010.
|
|
The group will document significant changes from this initial
|
|
schedule on the group home page. </td>
|
|
</tr>
|
|
</tfoot>
|
|
<tbody>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">Specification </th>
|
|
<th rowspan="1" colspan="1"><acronym title="First Working Draft">FPWD</acronym></th>
|
|
<th rowspan="1" colspan="1"><acronym title="Last Call Working Draft">LC</acronym> </th>
|
|
<th rowspan="1" colspan="1"><acronym title="Candidate Recommendation">CR</acronym> </th>
|
|
<th rowspan="1" colspan="1"><acronym title="Proposed Recommendation">PR</acronym> </th>
|
|
<th rowspan="1" colspan="1"><acronym title="Recommendation">Rec</acronym></th>
|
|
</tr>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">RDFa 1.1 API</th>
|
|
<td class="WD1" rowspan="1" colspan="1">April 2010 </td>
|
|
<td class="LC" rowspan="1" colspan="1">October 2010 </td>
|
|
<td class="CR" rowspan="1" colspan="1">January 2011</td>
|
|
<td class="PR" rowspan="1" colspan="1">March 2011</td>
|
|
<td class="REC" rowspan="1" colspan="1">April 2011</td>
|
|
</tr>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">RDFa 1.1 Core</th>
|
|
<td class="WD1" rowspan="1" colspan="1">April 2010 </td>
|
|
<td class="LC" rowspan="1" colspan="1">October 2010 </td>
|
|
<td class="CR" rowspan="1" colspan="1">January 2011</td>
|
|
<td class="PR" rowspan="1" colspan="1">March 2011</td>
|
|
<td class="REC" rowspan="1" colspan="1">April 2011</td>
|
|
</tr>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">RDFa 1.1 in XHTML1.1</th>
|
|
<td class="WD1" rowspan="1" colspan="1">April 2010</td>
|
|
<td class="LC" rowspan="1" colspan="1">October 2010</td>
|
|
<td class="CR" rowspan="1" colspan="1">January 2011</td>
|
|
<td class="PR" rowspan="1" colspan="1">March 2011</td>
|
|
<td class="REC" rowspan="1" colspan="1">April 2011</td>
|
|
</tr>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">RDFa 1.1 Primer</th>
|
|
<td class="WD1" rowspan="1" colspan="1">May 2010</td>
|
|
<td class="LC" rowspan="1" colspan="1">March 2011</td>
|
|
<td class="CR" rowspan="1" colspan="1">n/a</td>
|
|
<td class="PR" rowspan="1" colspan="1">n/a</td>
|
|
<td class="REC" rowspan="1" colspan="1">April 2011</td>
|
|
</tr>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">RDF TripleStore APIs (optional)</th>
|
|
<td class="WD1" rowspan="1" colspan="1">October 2010 </td>
|
|
<td class="LC" rowspan="1" colspan="1">April 2011 </td>
|
|
<td class="CR" rowspan="1" colspan="1">n/a</td>
|
|
<td class="PR" rowspan="1" colspan="1">n/a</td>
|
|
<td class="REC" rowspan="1" colspan="1">June 2011 </td>
|
|
</tr>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">RDFa Usage Cookbook (optional)</th>
|
|
<td class="WD1" rowspan="1" colspan="1">October 2010</td>
|
|
<td class="LC" rowspan="1" colspan="1">April 2011</td>
|
|
<td class="CR" rowspan="1" colspan="1">n/a</td>
|
|
<td class="PR" rowspan="1" colspan="1">n/a</td>
|
|
<td class="REC" rowspan="1" colspan="1">June 2011 </td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
<h3 id="timeline">Timeline View Summary</h3>
|
|
<ul>
|
|
<li>T: First teleconference</li>
|
|
<li>T+3: First Public Working Draft for the Recommendation track documents</li>
|
|
<li>T+4: First Public Working Draft for the Primer</li>
|
|
<li>T+9: Last Call Working Draft for the Recommendation track documents</li>
|
|
<li>T+9: First Public Working Draft for the TripleStore API and the Cookbook (both are optional)</li>
|
|
<li>T+11: Candidate Recommendation for the Recommendation track documents</li>
|
|
<li>T+13: Proposed Recommendation for the Recommendation track documents</li>
|
|
<li>T+13: Last Call Working Draft for the Primer</li>
|
|
<li>T+13: Publication of the API, RDFa 1.1 Core and RDFa 1.1 in XHTML1.1 Recommendations</li>
|
|
<li>T+13: Publication of the RDFa Primer</li>
|
|
<li>T+13: Last Call Working Draft for the TripleStore API and the Cookbook (both are optional)</li>
|
|
<li>T+15: Publication of the TripleStore API and the Cookbook (both are optional)</li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div class="dependencies">
|
|
<h2 id="coordination">Dependencies and Liaisons</h2>
|
|
<h3>Dependencies</h3>
|
|
<dl>
|
|
|
|
<dt><a href="http://www.w3.org/International/">Internationalization Activity</a></dt>
|
|
<dd>To ensure that all features introduced to RDFa 1.1 are in line with the requirements of Internationalization
|
|
on the Web.</dd>
|
|
<dt><a href="http://www.w3.org/WAI/PF/">Protocols and Formats Working Group</a></dt>
|
|
<dd>To ensure that all features introduced to RDFa 1.1 are in line with the requirements of Web Accessibility.</dd>
|
|
|
|
</dl>
|
|
|
|
<h3>Liaisons</h3>
|
|
|
|
<h4>W3C Groups</h4>
|
|
<dl>
|
|
<dt><a href="http://www.w3.org/html/wg/">HTML Working Group</a></dt>
|
|
<dd>To provide input for RDFa in HTML5 and XHTML5 specifications, and to use the feedbacks on those
|
|
specifications as input to the RDFa 1.1 development.</dd>
|
|
|
|
<dt><a href="http://www.w3.org/2008/webapps/">Web Applications Working Group</a></dt>
|
|
<dd>To ensure that the API work around RDFa stays in line with the general
|
|
Web Applications work.</dd>
|
|
|
|
<dt><a href="http://www.w3.org/2001/tag/">Technical Architecture Group (TAG)</a></dt>
|
|
<dd>To ensure that RDFa 1.1 is in line with general Web Architecture Principles</dd>
|
|
|
|
<dt><a href="http://www.w3.org/2001/sw/CG/">Semantic Web Coordination Group</a></dt>
|
|
<dd>To ensure that the development of RDFa and the APIs are coordinated with other
|
|
activities around the Semantic Web</dd>
|
|
|
|
<dt><a href="http://www.w3.org/Graphics/SVG/WG/">SVG Working Group</a></dt>
|
|
<dd>To ensure that the development of RDFa 1.1 and the APIs are in line with the development
|
|
of SVG</dd>
|
|
|
|
<dt><a href="http://www.w3.org/Graphics/SVG/IG/">SVG Interest Group</a></dt>
|
|
<dd>Provide feedback on the RDFa usage in SVG, as well as test cases that can also be used
|
|
by SVG 1.2 implementations. The cookbook examples should be coordinated with the SVG group,
|
|
thereby providing useful examples for the SVG community, too</dd>
|
|
|
|
<dt><a href="http://www.w3.org/WAI/PF/">Protocols and Formats Working Group</a></dt>
|
|
<dd>To explore whether and how RDFa 1.1 can contribute to the issues raised by future developments of
|
|
<a href="http://www.w3.org/standards/techs/aria">ARIA</a> and the usage of the @role attribute.</dd>
|
|
|
|
</dl>
|
|
|
|
<h4>External Groups</h4>
|
|
|
|
<dl>
|
|
<dt><a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">OASIS
|
|
Open Document Format for Office Applications (OpenDocument) TC</a></dt>
|
|
<dd>To synchronize on the RDFa usage in the ODF 1.2</dd>
|
|
</dl>
|
|
|
|
<div id="conformance">
|
|
<p>Furthermore, RDFa Working Group expects to follow these W3C Recommendations: </p>
|
|
<ul>
|
|
<li><a href="/TR/qaframe-spec/">QA Framework: Specification Guidelines</a>.</li>
|
|
<li><a href="/TR/charmod/">Character Model for the World Wide Web 1.0: Fundamentals</a> </li>
|
|
<li><a href="/TR/webarch/">Architecture of the World Wide Web, Volume I</a> </li>
|
|
</ul>
|
|
</div>
|
|
|
|
</div>
|
|
<div class="participation">
|
|
<h2 id="participation">Participation </h2>
|
|
<p>To be successful, the RDFa Working Group is expected to have 5 or
|
|
more active participants for its duration. Effective participation in the RDFa
|
|
Working Group is expected to consume one work day per week for each
|
|
participant; two days per week for editors. The RDFa Working Group will
|
|
allocate also the necessary resources for building proof-of-concept
|
|
Validators, Test Suites, and other implementations for
|
|
each specification. </p>
|
|
<p>Participants are reminded of the <a href="/2005/10/Process-20051014/groups.html#good-standing">Good
|
|
Standing requirements</a> of the W3C Process. </p>
|
|
</div>
|
|
<div class="communication">
|
|
<h2 id="communication">Communication </h2>
|
|
<p>This group primarily conducts its work on the public mailing list
|
|
public-rdfa@w3.org (with a publicly visible <a href="http://lists.w3.org/Archives/Public/public-rdfa/">archive</a>) .
|
|
</p>
|
|
<p>Information about the group (deliverables, participants, teleconferences, etc.) is available
|
|
from the <a href="http://www.w3.org/2010/02/rdfa">RDFa Working Group home page</a>. </p>
|
|
</div>
|
|
<div class="decisions">
|
|
<h2 id="decisions">Decision Policy </h2>
|
|
<p>As explained in the Process Document (<a href="/Consortium/Process/policies#Consensus" shape="rect">section 3.3</a>),
|
|
this group will seek to make decisions when there is consensus. When the Chair
|
|
puts a question and observes dissent, after due consideration of different
|
|
opinions, the Chair should record a decision (possibly after a formal vote) and any objections, and move on. </p>
|
|
|
|
<p>This charter is written in accordance with <a href="/Consortium/Process/policies#Votes">Section 3.4,
|
|
Votes</a> of the W3C Process Document and includes no voting procedures beyond what the Process Document
|
|
requires. </p>
|
|
</div>
|
|
<div class="patent">
|
|
<h2 id="patentpolicy">Patent Policy </h2>
|
|
<p>This Working Group operates under the <a href="/Consortium/Patent-Policy-20040205/" shape="rect">W3C Patent
|
|
Policy</a> (5 February 2004 Version). To promote the widest adoption of Web standards, W3C
|
|
seeks to issue Recommendations that can be implemented, according to
|
|
this policy, on a Royalty-Free basis. </p>
|
|
<p>For more information about disclosure obligations for this group,
|
|
please see the <a href="/2004/01/pp-impl/" shape="rect">W3C Patent Policy
|
|
Implementation</a>. </p>
|
|
</div>
|
|
<h2 id="about">About this Charter </h2>
|
|
<p>This charter for the RDFa Working Group has been created according
|
|
to <a href="/Consortium/Process/groups#GAGeneral" shape="rect">section 6.2</a> of the
|
|
<a href="/Consortium/Process" shape="rect">Process Document</a>. In the
|
|
event of a conflict between this document or the provisions of any charter
|
|
and the W3C Process, the W3C Process shall take precedence. </p>
|
|
<hr />
|
|
<address>Ivan Herman and Steven Pemberton, W3C staff, with input from Ben Adida, Manu Sporny, Mark Birbeck,
|
|
and Shane McCarron</address>
|
|
<p class="copyright"><a rel="Copyright" href="/Consortium/Legal/ipr-notice#Copyright" >Copyright</a>© 2010
|
|
<a href="/" shape="rect">W3C</a>® (<a href="http://www.csail.mit.edu/" shape="rect">MIT</a> ,
|
|
<a href="http://www.ercim.eu/" shape="rect">ERCIM</a>, <a href="http://www.keio.ac.jp/" shape="rect">Keio</a>),
|
|
All RightsReserved.</p>
|
|
<p>$Date: 2010/02/02 16:14:19 $</p>
|
|
</div>
|
|
</body>
|
|
</html>
|