contribute-w3c-tutorials.html
15.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
<?xml version="1.0"?>
<!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" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<style type="text/css" media="all">
@import "/QA/2006/01/blogstyle.css";
</style>
<meta name="keywords" content='' />
<meta name="description" content=" We started a series about how you can contribute to W3C work. Last time, we have seen how to create and propose your own quick tips. This week, we will go a step further by looking at tutorials. Specifications..." />
<meta name="revision" content="$Id: contribute-w3c-tutorials.html,v 1.97 2011/12/16 02:58:28 gerald Exp $" />
<link rel="alternate" type="application/atom+xml" title="Atom" href="http://www.w3.org/QA/atom.xml" />
<link rel="alternate" type="application/rss+xml" title="RSS 1.0" href="http://www.w3.org/QA/news.rss" />
<title>How to to contribute to W3C work? Tutorials - W3C Blog</title>
<link rel="start" href="http://www.w3.org/QA/" title="Home" />
<link rel="prev" href="http://www.w3.org/QA/2007/06/html5-call-to-web-professionals.html" title="Authoring HTML 5 - A Call to Web Professionals" />
<link rel="next" href="http://www.w3.org/QA/2007/06/fixing_the_web_together.html" title="Fixing the Web… Together!" />
<!--
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
xmlns:dc="http://purl.org/dc/elements/1.1/">
<rdf:Description
rdf:about="http://www.w3.org/QA/2007/06/contribute-w3c-tutorials.html"
trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/60"
dc:title="How to to contribute to W3C work? Tutorials"
dc:identifier="http://www.w3.org/QA/2007/06/contribute-w3c-tutorials.html"
dc:subject="W3C Life"
dc:description=" We started a series about how you can contribute to W3C work. Last time, we have seen how to create and propose your own quick tips. This week, we will go a step further by looking at tutorials. Specifications..."
dc:creator="Karl Dubost"
dc:date="2007-06-13T07:30:51+00:00" />
</rdf:RDF>
-->
<!-- <script type="text/javascript" src="http://www.w3.org/QA/mt.js"></script>-->
</head>
<body class="layout-one-column">
<div id="banner">
<h1 id="title">
<a href="http://www.w3.org/"><img height="48" alt="W3C" id="logo" src="http://www.w3.org/Icons/WWW/w3c_home_nb" /></a>
W3C Blog
</h1>
</div>
<ul class="navbar" id="menu">
<li><strong><a href="/QA/" title="W3C Blog Home">[ W3C Blog ]</a></strong></li>
<li><a href="/QA/Library/" title="Documents and Publications on Web and Quality">Documents</a></li>
<li><a href="/QA/Tools/" accesskey="3" title="Validators and other Tools">Tools</a></li>
<li><a href="/2007/12/qa-blog-help/index#feedback">Feedback</a></li>
</ul>
<div id="searchbox">
<form method="get" action="http://www.google.com/custom" enctype="application/x-www-form-urlencoded">
<p id="formbox"><input type="text" size="15" class="textfield" name="q" accesskey="E" maxlength="255" /> <input type="submit" class="submitfield" value="Search" id="goButton" name="sa" accesskey="G" /> <input type="hidden" name="cof" value="T:black;LW:72;ALC:#ff3300;L:http://www.w3.org/Icons/w3c_home;LC:#000099;LH:48;BGC:white;AH:left;VLC:#660066;GL:0;AWFID:0b9847e42caf283e;" /><input type="hidden" id="searchW3C" name="sitesearch" checked="checked" value="www.w3.org/QA" /><input type="hidden" name="domains" value="www.w3.org/QA" /></p>
</form>
</div>
<div id="main"><!-- This DIV encapsulates everything in this page - necessary for the positioning -->
<p class="content-nav">
<a href="http://www.w3.org/QA/2007/06/html5-call-to-web-professionals.html">« Authoring HTML 5 - A Call to Web Professionals</a> |
<a href="http://www.w3.org/QA/">Main</a>
| <a href="http://www.w3.org/QA/2007/06/fixing_the_web_together.html">Fixing the Web… Together! »</a>
</p>
<h2 class="entry-header">How to to contribute to W3C work? Tutorials</h2>
<div class="entry-body">
<p>We started a series about how you can contribute to W3C work. Last time, we have seen how to create and propose your own <a href="http://www.w3.org/QA/2007/05/contribute-w3c-quick-tips.html" title="How to to contribute to W3C work? Quick Tips - W3C Q&A Weblog">quick tips</a>. This week, we will go a step further by looking at tutorials. </p>
<h4 id="specificiations">Specifications are for implementers</h4>
<p>W3C is somehow victim of its openness. We published all Working Drafts of a technology in a <a href="http://www.w3.org/TR/" title="W3C technical specifications">public space</a>. The specifications are freely downloadable by many different types of audiences. It creates friction and misunderstanding. The <strong>primary audience</strong> of W3C specifications is the developers community, people coding softwares.</p>
<p>There are expert users of the technology who do not develop a product implementing the technology but who are creating documents using the technology. This document will be viewed, parsed, processed by a product. These expert users need tutorials to understand and use the technology. Unfortunately, the W3C has not that much resources for developing materials in this category. Luckily enough, there are strong Web communities publishing materials online, writing books and giving examples. Sometimes a Working Group will publish a primer such as <a href="http://www.w3.org/TR/xhtml-rdfa-primer/" title="RDFa Primer 1.0">RDFa Primer</a> on how to use microformats the RDF way in your pages. Most of the time there isn't a primer.</p>
<h4 id="howto">How to create your own tutorials.</h4>
<p><strong>You can write a tutorial</strong>. W3C has a list of <a href="http://www.w3.org/2002/03/tutorials" title="Tutorials @ W3C">tutorials</a>. But too few. It would be cool if you could contribute more. If the topic is too big, split it and contribute by small pieces. When you have created a tutorial, please send it to <a href="mailto:public-evangelist@w3.org">public-evangelist@w3.org</a>. We will help you to contact the appropriate Working Group and its staff contact. And we will see if your content can be added to W3C Web site. (There is no guarantee, it will be.)</p>
<p>Tutorials usually offer a very good exposure of your competences. It is good for your karma. The community will have a broader access to the technology. It makes the technology easier to learn specifically when it is still quite new.</p>
</div>
<div id="more" class="entry-more">
</div>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/karl/">Karl Dubost</a> on June 13, 2007 7:30 AM in <a href="http://www.w3.org/QA/archive/web_spotting/tutorials/">Tutorials</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/w3c_life/">W3C Life</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2007/06/contribute-w3c-tutorials.html">Permalink</a>
| <a href="http://www.w3.org/QA/2007/06/contribute-w3c-tutorials.html#comments">Comments (7)</a>
| <a href="http://www.w3.org/QA/2007/06/contribute-w3c-tutorials.html#trackback">TrackBacks (0)</a>
</p>
<h3 class="comments-header" id="comments">Comments</h3>
<div class="comment" id="comment-45697">
<p class="comment-meta" id="c045697">
<span class="comment-meta-author"><strong>Nicolas Le Gall </strong></span>
<span class="comment-meta-date"><a href="#c045697">#</a> 2007-06-13</span>
</p>
<div class="comment-bulk">
<p>A good point will be to provide internationalized tutorials, or some links.</p>
<p>I think for non-expert users it is essential and will prevent misunderstanding.</p>
<p>About tutorials: I think proposing some examples based on real life is a very good thing. A non-expert has not the same logic than an expert and give them a point of reference is essential.</p>
</div>
</div>
<div class="comment" id="comment-45720">
<p class="comment-meta" id="c045720">
<span class="comment-meta-author"><strong>olivier </strong></span>
<span class="comment-meta-date"><a href="#c045720">#</a> 2007-06-13</span>
</p>
<div class="comment-bulk">
<p>Nicolas: when you say <em>internationalized tutorial</em>, do you mean translations? </p>
<p>There is already a <a href="http://www.w3.org/2005/11/Translations/Query?tut=any&sorting=byLanguage&output=FullHTML" rel="nofollow">list of tutorials and FAQ translations</a>, which may be what you're looking for. Of course, before having more translations, it needs more tutorials...</p>
</div>
</div>
<div class="comment" id="comment-45735">
<p class="comment-meta" id="c045735">
<span class="comment-meta-author"><strong>Nicolas Le Gall </strong></span>
<span class="comment-meta-date"><a href="#c045735">#</a> 2007-06-13</span>
</p>
<div class="comment-bulk">
<p>Yes, I was talking about translations (sorry for my approximate english).
Thank you for the link !</p>
</div>
</div>
<div class="comment" id="comment-45760">
<p class="comment-meta" id="c045760">
<span class="comment-meta-author"><strong>tom.opiumfield.com <a class="commenter-profile" href="http://tom.opiumfield.com/"><img alt="Author Profile Page" src="http://www.w3.org/QA/sununga/mt-static/images/comment/openid_logo.png" width="16" height="16" /></a></strong></span>
<span class="comment-meta-date"><a href="#c045760">#</a> 2007-06-13</span>
</p>
<div class="comment-bulk">
<p>Good point. That's one of the reasons that I have started getsemantic.com - a wiki where you can put up details of semantic web projects and tutorials.</p>
</div>
</div>
<div class="comment" id="comment-46314">
<p class="comment-meta" id="c046314">
<span class="comment-meta-author"><strong>Dirk Karl Maßat </strong></span>
<span class="comment-meta-date"><a href="#c046314">#</a> 2007-06-14</span>
</p>
<div class="comment-bulk">
<p>Thanks for very interesting article. btw. I really enjoyed reading all of your posts. It’s interesting to read ideas, and observations from someone else’s point of view… makes you think more. So please keep up the great work. Greetings.</p>
</div>
</div>
<div class="comment" id="comment-47134">
<p class="comment-meta" id="c047134">
<span class="comment-meta-author"><strong>Lynx Kraaikamp </strong></span>
<span class="comment-meta-date"><a href="#c047134">#</a> 2007-06-16</span>
</p>
<div class="comment-bulk">
<p>I think a tutorial for, say, (X)HTML should go so basic as to explain what "<" and ">" do (begin and end a tag, respectively). A tutorial should also explain why one should use a doctype, what an element actually does, and so on. I am working on such a tutorial.</p>
</div>
</div>
<div class="comment" id="comment-51315">
<p class="comment-meta" id="c051315">
<span class="comment-meta-author"><strong>Bloggeries </strong></span>
<span class="comment-meta-date"><a href="#c051315">#</a> 2007-06-26</span>
</p>
<div class="comment-bulk">
<p>I think it is brilliant that you are allowing us to implement our own tutorials. Despite the other attractions this site has the main reason I come here now and did in the beginning was the tutorials. I believe they always have and always will be a major force driving traffic to this amazing community. </p>
<p>Many thanks, I'll have to begin working on one.</p>
</div>
</div>
<div class="comments-open" id="comments-open">
<h3 class="comments-open-header">Leave a comment</h3>
<div class="comments-open-moderated">
<p>
Note: this blog is intended to foster <strong>polite
on-topic discussions</strong>. Comments failing these
requirements and spam will not get published. Please,
enter your real name and email address. Every
individual comment is reviewed by the W3C staff.
This may take some time, thank you for your patience.
</p>
<p>
You can use the following HTML markup (a href, b, i,
br/, p, strong, em, ul, ol, li, blockquote, pre)
and/or <a href="http://daringfireball.net/projects/markdown/syntax">Markdown syntax</a>.</p>
</div>
<div id="comments-open-data">
<form method="post" action="http://www.w3.org/QA/sununga/beach.pl" id="comments-form">
<h4>Your comment</h4>
<div id="comments-open-text">
<textarea id="comment-text" name="text" rows="20" cols="100"></textarea><br />
<label for="comment-text">Write your comment text here. Remember, keep the discussion on topic and courteous.</label>
</div>
<h4>About you</h4>
<div id="comment-form-name">
<input type="hidden" name="static" value="1" />
<input type="hidden" name="entry_id" value="63" />
<input type="hidden" name="__lang" value="en" />
<label for="comment-author">Your Name</label>
<input id="comment-author" name="author" size="30" value="" />
</div>
<div id="comment-form-email">
<label for="comment-email">Your Email Address</label>
<input id="comment-email" name="email" size="30" value="" />
</div>
<div id="comments-open-footer">
<input type="submit" accesskey="s" name="post" id="comment-submit" value="Submit" />
</div>
</form>
</div>
</div>
<p id="gentime">This page was last generated on $Date: 2011/12/16 02:58:28 $</p>
</div><!-- End of "main" DIV. -->
<address>
This blog is written by W3C staff and working group participants,<br />
and maintained by <a href="/People/CMercier/">Coralie Mercier</a>.<br />
Authorized parties may <a href="/QA/new">log in</a> to create a new entry.<br/>
<span id="poweredby">Powered by Movable Type, magpierss and a lot of Web Technology</span>
</address>
<p class="copyright">
<a rel="Copyright" href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 1994-2011
<a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a>®
(<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>,
<a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
<a href="http://www.keio.ac.jp/">Keio</a>),
All Rights Reserved.
W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>,
<a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
and <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-software">software licensing</a>
rules apply. Your interactions with this site are in accordance
with our <a href="http://www.w3.org/Consortium/Legal/privacy-statement#Public">public</a> and
<a href="http://www.w3.org/Consortium/Legal/privacy-statement#Members">Member</a> privacy
statements.
</p>
</body>
</html>