validator-roadmap.html
12.9 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
<?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='dtd, html, html5, relaxng, schema, svg, validator, w3c' />
<meta name="description" content="With the latest release, today, of the markup validator, comes a time to give a look at its development roadmap. Among the contenders for development time: localization, support for schema languages, and a richer API. Interesting times ahead..." />
<meta name="revision" content="$Id: validator-roadmap.html,v 1.59 2011/12/16 02:58:36 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>Validator 0.8 getting stable - what next? - W3C Blog</title>
<link rel="start" href="http://www.w3.org/QA/" title="Home" />
<link rel="prev" href="http://www.w3.org/QA/2007/10/shorttags.html" title="Shorttags - the odd side of HTML 4.01" />
<link rel="next" href="http://www.w3.org/QA/2007/10/the_impact_of_javascript_and_x.html" title="The impact of Javascript and XMLHttpRequest on web architecture" />
<!--
<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/10/validator-roadmap.html"
trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/78"
dc:title="Validator 0.8 getting stable - what next?"
dc:identifier="http://www.w3.org/QA/2007/10/validator-roadmap.html"
dc:subject="Tools"
dc:description="With the <a href="http://lists.w3.org/Archives/Public/www-validator/2007Oct/0058.html">latest release</a>, today, of the markup validator, comes a time to give a look at its <a href="http://validator.w3.org/todo.html">development roadmap</a>. Among the contenders for development time: localization, support for schema languages, and a richer API. Interesting times ahead..."
dc:creator="olivier Théreaux"
dc:date="2007-10-11T03:45:13+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/10/shorttags.html">« Shorttags - the odd side of HTML 4.01</a> |
<a href="http://www.w3.org/QA/">Main</a>
| <a href="http://www.w3.org/QA/2007/10/the_impact_of_javascript_and_x.html">The impact of Javascript and XMLHttpRequest on web architecture »</a>
</p>
<h2 class="entry-header">Validator 0.8 getting stable - what next?</h2>
<div class="entry-body">
<p>I didn't get to announce properly the releases of the Markup Validator 0.8.0 and 0.8.1 here, so these will be bulked with today's special: the Validator version <a href="http://validator.w3.org/whatsnew.html#t2007-10-11">0.8.2</a> is out.</p>
<p>0.8.0 was a big step forward, bringing reliable XML support at last, and a faster parsing engine. Since then, the work has focused a lot on tons of little bug fixes, and usability. The latest release is no exception, and as the <a href="http://lists.w3.org/Archives/Public/www-validator/2007Oct/0058.html">release announcement</a> summarizes, 0.8.2 was mostly about <em>making it easier</em>...</p>
<p>The pleasant thing about releasing (relatively) often is that we get to look at the roadmap, with a critical eye, regularly. A few months ago, when the <a href="http://validator.w3.org/todo.html">development roadmap</a> was last revamped, it was obvious in my mind that the next big effort would be localization. Am I still absolutely certain that localization should have a high priority? Sure. As a tool that wants to help Web developers everywhere, being available in English only is a liability for the Markup Validator. But other work items are vying for attention too.</p>
<p>One of the most pressing of those is the question of "what we validate against". Up to the mid-<span title="it's about time we standardize the name of this decade, really. Or is ISO already on it?">noughties</span>, most languages standardized at W3C were formalized with SGML and XML DTD grammars. The Validator was (and still is) using a fantastic engine for parsing documents against DTDs: <a href="https://sourceforge.net/projects/openjade/" title="opensp/openjade project page at sourceforge.net">opensp</a>.</p>
<p>In the past few years, however, new schema languages came and were able to express much more than DTDs did. Namespace support (something unfortunately alien to DTDs) and extensibility, notably, made people look for other solutions. With a number of languages (e.g. SVG 1.2) based on such schema languages as RelaxNG or XML Schema getting mature, and other languages considering not having any kind of formal grammar at all, it is time for the validator to add new tricks to its bag - while keeping strong and reliable support for validation of older document types, which still make most of the web. It is a great time for experimentation: there will be much to learn, and adopt, from other projects such as <a href="http://relaxed.sourceforge.net/">relaxed</a> or <a href="http://code.google.com/p/html5lib/">html5lib</a>. Maybe some of this will be spun to other projects, tied together via the <a href="http://www.w3.org/QA/Tools/Unicorn/">Unicorn</a> framework. Experimental work should also be a good time for developers to join the project: it's always more fun to experiment and build new things than focus on fixing bugs in ten-years-old code.</p>
<p>Ultimately, where the validator goes will also be influenced greatly by its users. For example, after a relatively quiet start, the <a href="http://validator.w3.org/docs/api.html" title="Documentation of the Programmatic Interface (API) to The W3C Markup Validation Service">Validator's API</a> is getting more and more attention, and some developers are joining the <a href="http://lists.w3.org/Archives/Public/www-validator/" title="www-validator@w3.org Mail Archives">validator's mailing-list</a> with tons of ideas. Good, constructive ideas and working patches are generally the best way to influence an open source project, so expect some interesting evolution in this area...</p>
</div>
<div id="more" class="entry-more">
</div>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/olivier/">olivier Théreaux</a> on October 11, 2007 3:45 AM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/tools/">Tools</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2007/10/validator-roadmap.html">Permalink</a>
| <a href="http://www.w3.org/QA/2007/10/validator-roadmap.html#comments">Comments (1)</a>
| <a href="http://www.w3.org/QA/2007/10/validator-roadmap.html#trackback">TrackBacks (0)</a>
</p>
<h3 class="comments-header" id="comments">Comments</h3>
<div class="comment" id="comment-75052">
<p class="comment-meta" id="c075052">
<span class="comment-meta-author"><strong>Ronny Vårdal </strong></span>
<span class="comment-meta-date"><a href="#c075052">#</a> 2007-10-23</span>
</p>
<div class="comment-bulk">
<p>I'm looking forward to v0.9! I've already been in contact with you regarding the l10n of The Validator into nb-NO (Norwegian Bokmaal) and/or nn-NO (Norwegian Nynorsk).</p>
<p>I just hope I can contribute when that time arrives.</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="86" />
<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:36 $</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>