tpac-2007-uri-extensibility.html
12.8 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
<?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='conference, tpac, tpac2007, w3c, w3c_tpac07' />
<meta name="description" content="The Technical plenary day is continuing. Someone in a comment earlier asked what TPAC was. TPAC means Technical Plenary and Advisory Committee meeting. All W3C Working groups and representatives of W3C are meeting. This year we open a bit more..." />
<meta name="revision" content="$Id: tpac-2007-uri-extensibility.html,v 1.50 2011/12/16 02:58:39 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>TPAC 2007 - URI-Based Extensibility: Benefits, Deviations, Lessons-Learned - W3C Blog</title>
<link rel="start" href="http://www.w3.org/QA/" title="Home" />
<link rel="prev" href="http://www.w3.org/QA/2007/11/tpac-2007-openness.html" title="TPAC 2007 - Openness of W3C Working Groups" />
<link rel="next" href="http://www.w3.org/QA/2007/11/tpac-2007-video.html" title="TPAC 2007 - Making Video a First-Class Citizen of the Web" />
<!--
<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/11/tpac-2007-uri-extensibility.html"
trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/93"
dc:title="TPAC 2007 - URI-Based Extensibility: Benefits, Deviations, Lessons-Learned"
dc:identifier="http://www.w3.org/QA/2007/11/tpac-2007-uri-extensibility.html"
dc:subject="HTML"
dc:description="The Technical plenary day is continuing. Someone in a comment earlier asked what TPAC was. TPAC means Technical Plenary and Advisory Committee meeting. All W3C Working groups and representatives of W3C are meeting. This year we open a bit more..."
dc:creator="Karl Dubost"
dc:date="2007-11-07T15:26:58+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/11/tpac-2007-openness.html">« TPAC 2007 - Openness of W3C Working Groups</a> |
<a href="http://www.w3.org/QA/">Main</a>
| <a href="http://www.w3.org/QA/2007/11/tpac-2007-video.html">TPAC 2007 - Making Video a First-Class Citizen of the Web »</a>
</p>
<h2 class="entry-header">TPAC 2007 - URI-Based Extensibility: Benefits, Deviations, Lessons-Learned</h2>
<div class="entry-body">
<p>The Technical plenary day is continuing. Someone in a comment earlier asked what TPAC was. TPAC means Technical Plenary and Advisory Committee meeting. All W3C Working groups and representatives of W3C are meeting. This year we open a bit more the technical plenary day to bloggers, journalists, and Web designers community.</p>
<p>The <a href="http://www.w3.org/2007/11/07-TechPlenAgenda.html#uri">session</a> which just started is a bit more technical addressing URI-based extensibility in the <a href="http://www.w3.org/TR/webarch/">Web architecture</a>. URI are identifiers, exactly like a barcode in the physical world. The principle of URI-based extensibility relies on associating a vocabulary (markup language) with an URI. Imagine there is a Smith family in Boston and a Smith family in New-York, you will talk about the Smith of Boston or the Smith of New-York. You qualified the smith to disambiguate which ones you were talking about and to avoid misunderstandings. URI-extensibility is working in the same way but using URIs for the unique identifier.</p>
<p>Dave Orchard introduces the topics citing work in Web Architecture. Sam Ruby proposed a <a href="http://www.intertwingly.net/blog/2007/08/02/HTML5-and-Distributed-Extensibility">mechanism for HTML 5 and distributed extensibility</a>. Ian Hickson challenged the benefits of URI extensibility by studying the small number of Web pages actually using the profile attribute in HTML pages. Dan Connolly says that even if his backyard is insignificant with regards to the rest of the planet, he might need disambiguation mechanism. Tim-Berners Lee remind that there is not only one community. HTML is a big community, but there are others communities. Smaller communities are more in need of uri-extensibility than bigger ones. </p>
<p>Dan Connolly is asking for support of the profile attribute in Dreamweaver. I tend to agree with Dan here. Some features are not used in the community because tools do not integrate them. Tools will not save us but they can help us a lot in many circumstances. Dan says that "it's a bug when you have a merger; it's a feature when people don't play nice."</p>
<p>Tim Berners-Lee: "The thing I like about web architecture is that I can follow my nose.... giving pointers, give context to things."</p>
<p>Ian Hickson stresses out that there is little value to give URI for microformats for example, and that you still need knowledge of the vocabulary to implement it.</p>
<p>Dan Connolly replies that it is not fair that a community removes the possibility of using some vocabulary from other communities, just because they decided it.</p>
<p>Chris Wilson finds interesting that the community decide to formalize well-known semantics used largely by the community. I would reply to that the English community is imposing a lot of patterns on others communities.</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 November 7, 2007 3:26 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/meetings/">Meetings</a>, <a href="http://www.w3.org/QA/archive/web_spotting/opinions_editorial/">Opinions &amp; Editorial</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/w3c_life/">W3C Life</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/">W3C・QA News</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2007/11/tpac-2007-uri-extensibility.html">Permalink</a>
| <a href="http://www.w3.org/QA/2007/11/tpac-2007-uri-extensibility.html#comments">Comments (1)</a>
| <a href="http://www.w3.org/QA/2007/11/tpac-2007-uri-extensibility.html#trackback">TrackBacks (0)</a>
</p>
<h3 class="comments-header" id="comments">Comments</h3>
<div class="comment" id="comment-81673">
<p class="comment-meta" id="c081673">
<span class="comment-meta-author"><strong>Slim Amamou </strong></span>
<span class="comment-meta-date"><a href="#c081673">#</a> 2007-11-08</span>
</p>
<div class="comment-bulk">
<blockquote>URI are identifiers, exactly like a barcode in the physical world.</blockquote>
<p>barcodes syntax have been obfuscated by the fact they were merely considered as identifiers. while barcodes are structured (as most computer codes and identifiers), rare are humans that can decode them.</p>
<p>by considering URIs as mere identifiers, we omit the structure, syntax and semantics aspect in them. thus making the web less human friendly.</p>
<p><a href="http://idn.icann.org/Talk:IDNwiki#RTL_scripts_URL_directionality_problem_.28arabic_for_instance.29" rel="nofollow">see how IRI structure (slashes order), raises some issues in right to left scripts (Arabic and Hebrew).</a></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="101" />
<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:39 $</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>