| 1 |
<?xml version="1.0" encoding="iso-2022-jp"?> |
| 2 |
<?xml-stylesheet type="text/xsl" href="htp-html-en.xsl" media="all"?> |
| 3 |
<?xml-stylesheet type="text/xsl" href="htp-html-ja.xsl" media="all" alternate="yes"?> |
| 4 |
<!DOCTYPE p:doc [ |
| 5 |
<!ATTLIST t:en xml:lang CDATA #FIXED "en"> |
| 6 |
<!ATTLIST t:ja xml:lang CDATA #FIXED "ja"> |
| 7 |
]> |
| 8 |
<p:doc xmlns:p="http://suika.fam.cx/~wakaba/archive/2005/2/htp#" |
| 9 |
xmlns:dc="http://purl.org/dc/elements/1.1/" |
| 10 |
xmlns:t="http://suika.fam.cx/~wakaba/archive/2005/2/m17n#" |
| 11 |
xmlns:h="http://www.w3.org/1999/xhtml" |
| 12 |
xml:lang="en" |
| 13 |
lastModified.RCS="$Date:$"> |
| 14 |
<p:entry xml:id="ADDRESS-CONTENT" s="syntax"> |
| 15 |
<dc:title>Structured <p:he>address</p:he></dc:title> |
| 16 |
<p:problem> |
| 17 |
<p:i><p:he>address</p:he> element type has inline content |
| 18 |
model in Strict DTDs.</p:i> |
| 19 |
<p:i>Some authors want to mark up structure of <p:he>address</p:he> content, |
| 20 |
such as author's name, mail address and copyright information, |
| 21 |
as block-level elements.</p:i> |
| 22 |
</p:problem> |
| 23 |
<p:situation> |
| 24 |
<p:i>Strict DTDs only allow inline content, while Transitional DTDs |
| 25 |
also allow <p:he>p</p:he> children.</p:i> |
| 26 |
</p:situation> |
| 27 |
<p:current> |
| 28 |
<p:i>Some authors select Transitional DTDs to enable block-level content.</p:i> |
| 29 |
<p:i>Others use inline element such as <p:he>span</p:he>.</p:i> |
| 30 |
<p:i>Others use <p:he>br</p:he> to separate contents.</p:i> |
| 31 |
<p:i>Others give up to use <p:he>address</p:he> and use |
| 32 |
<p:he>div</p:he> instead.</p:i> |
| 33 |
</p:current> |
| 34 |
<p:H4 section="struct/global.html#edef-ADDRESS"/> |
| 35 |
<p:H4 section="sgml/loosedtd.html"/> |
| 36 |
<p:SW page="address" anchor="6"/> |
| 37 |
<p:related ref="ADDRESS-SEMANTICS"/> |
| 38 |
</p:entry> |
| 39 |
|
| 40 |
<p:entry xml:id="ADDRESS-SEMANTICS" s="semantics"> |
| 41 |
<dc:title><p:he>address</p:he> Semantics</dc:title> |
| 42 |
<p:problem> |
| 43 |
<p:i><p:he>address</p:he> elements are used to mark up various |
| 44 |
contents, including author's names, author's contact addresses, |
| 45 |
copyright information, last-modified date of the document, |
| 46 |
Web site navigations, and so on.</p:i> |
| 47 |
</p:problem> |
| 48 |
<p:situation> |
| 49 |
<p:i>HTML 4 describes that this element type is |
| 50 |
<h:q cite="http://www.w3.org/TR/1999/REC-html401-19991224/struct/global.html#edef-ADDRESS">used by authors to supply contact information for a document or a major part of a document such as a form</h:q>.</p:i> |
| 51 |
<p:i>HTML 4 shows an example document fragment whose <p:he>address</p:he> |
| 52 |
contains modification date information.</p:i> |
| 53 |
</p:situation> |
| 54 |
<p:SW page="address" anchor="7"/> |
| 55 |
<p:related ref="ADDRESS-CONTENT"/> |
| 56 |
</p:entry> |
| 57 |
|
| 58 |
<p:entry xml:id="BLOCKQUOTE-HEADING-LEVEL" s="syntax"> |
| 59 |
<dc:title>Heading Level in <p:he>blockquote</p:he></dc:title> |
| 60 |
<p:problem> |
| 61 |
<p:i>What heading level (number) should headings in |
| 62 |
<p:he>blockquote</p:he> have?</p:i> |
| 63 |
<p:i>Possible solutions include (a) the next level in containing document, |
| 64 |
(b) <p:he>h1</p:he> and (c) the original level in the cited |
| 65 |
document.</p:i> |
| 66 |
</p:problem> |
| 67 |
<p:situation> |
| 68 |
<p:i>The content model allows any level of headings.</p:i> |
| 69 |
<p:i>Some people think quotation including headings are inappropriate |
| 70 |
from the view of <h:q>good document style</h:q>.</p:i> |
| 71 |
<p:i>XHTML 2.0 proposes unnumbered <h:xhe>h</h:xhe> element type.</p:i> |
| 72 |
</p:situation> |
| 73 |
<p:H4 section="struct/text.html#edef-BLOCKQUOTE"/> |
| 74 |
<p:XH2 section="mod-structural.html#edef_structural_heading"/> |
| 75 |
<p:ref uri="http://members.jcom.home.ne.jp/jintrick/Personal/elements.html#blockquote_and_heading" |
| 76 |
hrefLang="ja"> |
| 77 |
<dc:title xml:lang="ja">$B0zMQ$H8+=P$7(B</dc:title> |
| 78 |
<dc:author>Sophisme</dc:author> |
| 79 |
</p:ref> |
| 80 |
<p:SW page="blockquote" anchor="1"/> |
| 81 |
</p:entry> |
| 82 |
|
| 83 |
<p:entry xml:id="BLOCKQUOTE-CREDIT" s="syntax"> |
| 84 |
<dc:title>Credits or Captions for <p:he>blockquote</p:he></dc:title> |
| 85 |
<p:problem> |
| 86 |
<p:i>There's no standard way to describe credits and captions for |
| 87 |
<p:he>blockquote</p:he>.</p:i> |
| 88 |
</p:problem> |
| 89 |
<p:situation> |
| 90 |
<p:i>HTML 3.0 proposed <p:he>credit</p:he> element type for this purpose.</p:i> |
| 91 |
<p:i>A number of proposals has been submitted to public forum including |
| 92 |
www-html about this issue.</p:i> |
| 93 |
<p:i>There's already <p:he>caption</p:he> element type for tables.</p:i> |
| 94 |
</p:situation> |
| 95 |
<p:current> |
| 96 |
<p:i>Use outer <p:he>div</p:he> including <p:he>blockquote</p:he> |
| 97 |
and another <p:he>div</p:he> for credits.</p:i> |
| 98 |
<p:i>Use inner <p:he>div</p:he> for quoted text and |
| 99 |
another inner <p:he>div</p:he> for credits.</p:i> |
| 100 |
<p:i>Give up. Use <p:he>cite</p:he> in prose.</p:i> |
| 101 |
</p:current> |
| 102 |
<p:H3/> |
| 103 |
<p:ref uri="http://mst.vis.ne.jp/cd/extra/www/cite_blockquote.htm"> |
| 104 |
<dc:title xml:lang="ja">$B!X(Bblockquote$BMWAG$NCf$K=PE5$r<($9(Bcite$BMWAG$rJq4^$9$Y$-$+!Y$K4X$9$k5DO@%j%s%/=8(B</dc:title> |
| 105 |
</p:ref> |
| 106 |
<p:ref uri="http://www.mozilla.org/contribute/writing/markup#quotations"> |
| 107 |
<dc:title xml:lang="en">mozilla.org Markup Reference</dc:title> |
| 108 |
</p:ref> |
| 109 |
<p:SW page="credit" anchor="4"/> |
| 110 |
<p:ref uri="http://pc5.2ch.net/test/read.cgi/hp/1103795522/453-460"> |
| 111 |
<dc:title xml:lang="ja">Strict-HTML $B%9%l%C%I(B 26</dc:title> |
| 112 |
</p:ref> |
| 113 |
</p:entry> |
| 114 |
|
| 115 |
<p:entry xml:id="DIV-SPAN-COMMENT" s="edit"> |
| 116 |
<dc:title>DTD Comment for <p:he>div</p:he> and <p:he>span</p:he></dc:title> |
| 117 |
<p:problem> |
| 118 |
<p:i>HTML 4 DTDs only describe <p:he>div</p:he> and <p:he>span</p:he> |
| 119 |
as <h:q>generic language/style container</h:q>, but they are not |
| 120 |
the only purposes of these element types.</p:i> |
| 121 |
</p:problem> |
| 122 |
<p:H4 section="sgml/dtd.html"/> |
| 123 |
<p:H4 section="sgml/loosedtd.html"/> |
| 124 |
</p:entry> |
| 125 |
|
| 126 |
<p:entry xml:id="DIV-CONTENT" s="syntax"> |
| 127 |
<dc:title>Inline contents of <p:he>div</p:he></dc:title> |
| 128 |
<p:problem> |
| 129 |
<p:i>Some don't think <p:he>div</p:he> elements directly containing |
| 130 |
character data is good practice.</p:i> |
| 131 |
</p:problem> |
| 132 |
<p:situation> |
| 133 |
<p:i>HTML 4 DTDs declares <p:he>div</p:he> as having flow content.</p:i> |
| 134 |
</p:situation> |
| 135 |
<p:current> |
| 136 |
<p:i>Not so many pepole agree with that idea.</p:i> |
| 137 |
</p:current> |
| 138 |
<H4 section="struct/global.html#edef-DIV"/> |
| 139 |
</p:entry> |
| 140 |
|
| 141 |
<p:entry xml:id="DL-SEMANTICS" s="semantics"> |
| 142 |
<dc:title><p:he>dl</p:he> is Named Item List Rather Than |
| 143 |
Definition List</dc:title> |
| 144 |
<p:problem> |
| 145 |
<p:i>Although <p:he>dl</p:he> stands for <h:q>definition list</h:q>, |
| 146 |
it is actually named item list.</p:i> |
| 147 |
<p:i>Some authors think <p:he>dl</p:he> should only be used |
| 148 |
for definition list.</p:i> |
| 149 |
</p:problem> |
| 150 |
<p:situation> |
| 151 |
<p:i>HTML 4 explicitly allows non-definition list usage.</p:i> |
| 152 |
<p:i>TimBL thinks <p:he>dl</p:he> can have more applications than |
| 153 |
definition list.</p:i> |
| 154 |
</p:situation> |
| 155 |
<p:current> |
| 156 |
<p:i><p:he>dl</p:he> is widely used for generic named item lists.</p:i> |
| 157 |
</p:current> |
| 158 |
<p:H4 section="struct/lists.html#edef-DL"/> |
| 159 |
<p:ref uri="http://ksi.cpsc.ucalgary.ca/archives/WWW-TALK/www-talk-1993q1.messages/64.html" hrefLang="en"> |
| 160 |
<dc:title>Re: HTML todo list</dc:title> |
| 161 |
<dc:author>Tim Berners$B!>(BLee</dc:author> |
| 162 |
</p:ref> |
| 163 |
<p:SW page="dl" anchor="7"/> |
| 164 |
</p:entry> |
| 165 |
|
| 166 |
<p:entry xml:id="DL-CONTENT" s="syntax"> |
| 167 |
<dc:title><p:he>dl</p:he> Content Model</dc:title> |
| 168 |
<p:problem> |
| 169 |
<p:i>HTML 4 DTD definition of <p:he>dl</p:he> content model is |
| 170 |
less restrictive.</p:i> |
| 171 |
<p:i>There's no way to explicitly group <p:he>dt</p:he> |
| 172 |
and <p:he>dd</p:he> pairs.</p:i> |
| 173 |
<p:i>Style sheet authors and script developers often wish to group |
| 174 |
corresponding <p:he>dt</p:he> and <p:he>dd</p:he> pairs.</p:i> |
| 175 |
</p:problem> |
| 176 |
<p:situation> |
| 177 |
<p:i>XHTML 2.0 proposes <p:xhe>di</p:xhe> element type.</p:i> |
| 178 |
</p:situation> |
| 179 |
<p:current> |
| 180 |
<p:i>Many (but not all) <p:he>dl</p:he> consist of |
| 181 |
one <p:he>dt</p:he> and one <p:he>dd</p:he> pairs.</p:i> |
| 182 |
</p:current> |
| 183 |
<p:XH2 section="mod-list.html#edef_list_di"/> |
| 184 |
</p:entry> |
| 185 |
|
| 186 |
<p:entry xml:id="FIELDSET-CONTENT" s="edit"> |
| 187 |
<dc:title><p:he>fieldset</p:he> Content</dc:title> |
| 188 |
<p:problem> |
| 189 |
<p:i>HTML 4 forces any <p:he>legend</p:he> element to come before |
| 190 |
any other elements.</p:i> |
| 191 |
<p:i>HTML 4 DTD comment (informative) told any non-white space |
| 192 |
characters not to come before <p:he>legend</p:he> element.</p:i> |
| 193 |
<p:i>XHTML 1 DTDs relax this restriction because of XML DTD limitation.</p:i> |
| 194 |
<p:i>DTD comment on non-white space has retained in XHTML 1 DTDs.</p:i> |
| 195 |
</p:problem> |
| 196 |
<p:H4 section="interact/forms.html#edef-FIELDSET"/> |
| 197 |
<p:M12N section="xhtml-modularization.html#dtdelement_fieldset.qname"/> |
| 198 |
<p:SW page="fieldset" anchor="6"/> |
| 199 |
</p:entry> |
| 200 |
|
| 201 |
<p:entry xml:id="FORM-PARENT" s="syntax"> |
| 202 |
<dc:title><p:he>form</p:he> Context</dc:title> |
| 203 |
<p:problem> |
| 204 |
<p:i>Some Web-based application developers wish to |
| 205 |
use multiple <p:he>form</p:he>s in a table, |
| 206 |
e.g. one <p:he>form</p:he> for each table row.</p:i> |
| 207 |
<p:i>Some also wish to nest <p:he>form</p:he> inside another |
| 208 |
<p:he>form</p:he>.</p:i> |
| 209 |
</p:problem> |
| 210 |
</p:entry> |
| 211 |
|
| 212 |
<p:entry xml:id="FORM-MULTIPLE-SUBMIT" s="syntax"> |
| 213 |
<dc:title>Multiple <p:he>form</p:he> Submittions</dc:title> |
| 214 |
<p:problem> |
| 215 |
<p:i>Some Web-based application developers wish to |
| 216 |
submit <p:he>form</p:he> data to multiple form processing agents |
| 217 |
either at the one time or by selecting one agent upon the user's request. |
| 218 |
</p:i> |
| 219 |
<p:i>Such developers often wish to update more than one frames |
| 220 |
by a user's activation on <p:he>form</p:he> submittion buttons |
| 221 |
or <p:he>a</p:he> anchors.</p:i> |
| 222 |
</p:problem> |
| 223 |
<p:current> |
| 224 |
<p:i>Use scripting.</p:i> |
| 225 |
</p:current> |
| 226 |
</p:entry> |
| 227 |
|
| 228 |
<p:entry xml:id="FORM-SUBMITTIONS" s="semantics"> |
| 229 |
<dc:title>Non-Standardized Form Submittion Ways</dc:title> |
| 230 |
<p:problem> |
| 231 |
<p:i>There're non-standardized form submittion protocols in use, |
| 232 |
including <h:code>action="mailto:<h:var>foo@example.org</h:var>"</h:code> |
| 233 |
and <h:code>enctype="text/plain"</h:code>.</p:i> |
| 234 |
</p:problem> |
| 235 |
<p:SW page="$BDs=P(B"/> |
| 236 |
</p:entry> |
| 237 |
|
| 238 |
<p:entry xml:id="FORM-ACTION-QUERY" s="semantics"> |
| 239 |
<dc:title><p:he>form</p:he> <p:ha>action</p:ha> URI with query</dc:title> |
| 240 |
<p:problem> |
| 241 |
<p:i>If form submission URI already has a query part |
| 242 |
and the <p:ha>method</p:ha> to use submittion is |
| 243 |
<h:code>get</h:code>, the query part should be dropped.</p:i> |
| 244 |
</p:problem> |
| 245 |
<p:situation> |
| 246 |
<p:i>Web browsers includeing Mozilla, Opera and Lynx drops [Eric].</p:i> |
| 247 |
<p:i>XForms 1.0 and WSDL defines that the separator between |
| 248 |
action URI and form-data be <h:code>&</h:code> if there is |
| 249 |
query part defined.</p:i> |
| 250 |
</p:situation> |
| 251 |
<p:H4 section="interact/forms.html#h-17.13.3.4"/> |
| 252 |
<p:ref uri="mid:20050224033333.GB11887@w3.org"> |
| 253 |
<dc:title xml:lang="en">Compatibility between HTML, XForms, and WSDL</dc:title> |
| 254 |
<dc:author>Eric Prud'hommeaux</dc:author> |
| 255 |
</p:ref> |
| 256 |
<p:ref uri="http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20-bindings.html?content-type=text/html;%20charset=utf-8#_http_x-www-form-urlencoded"> |
| 257 |
<dc:title xml:lang="en">WSDL</dc:title> |
| 258 |
</p:ref> |
| 259 |
<p:ref uri="http://www.w3.org/TR/2003/REC-xforms-20031014/slice11.html#serialize-urlencode"> |
| 260 |
<dc:title xml:lang="en">XForms 1.0</dc:title> |
| 261 |
</p:ref> |
| 262 |
<p:ref uri="http://www.w3.org/TR/2005/WD-rdf-sparql-protocol-20050114/"> |
| 263 |
<dc:title xml:lang="en">SPARQL</dc:title> |
| 264 |
</p:ref> |
| 265 |
</p:entry> |
| 266 |
|
| 267 |
<p:entry xml:id="H1-MULTIPLE" |
| 268 |
s="semantics"> |
| 269 |
<dc:title><t:Alt> |
| 270 |
<t:en>Multiple <p:he>h1</p:he> elements</t:en> |
| 271 |
<t:ja>$BJ#?t$N(B <p:he>h1</p:he> $BMWAG(B</t:ja> |
| 272 |
</t:Alt></dc:title> |
| 273 |
<p:problem> |
| 274 |
<p:i>It is unclear whether a document should be allowed to have |
| 275 |
multiple <p:he>h1</p:he> elements.</p:i> |
| 276 |
</p:problem> |
| 277 |
<p:situation> |
| 278 |
<p:i>HTML 4 content model allows zero or more <p:he>h1</p:he> elements.</p:i> |
| 279 |
<p:i><p:he>pre-html</p:he> document type of Guide to ISO-HTML |
| 280 |
allows zero or more <p:he>h1</p:he> (and <p:he>div1</p:he>) elements. |
| 281 |
</p:i> |
| 282 |
</p:situation> |
| 283 |
<p:current> |
| 284 |
<p:i>Many author does not think putting multiple <p:he>h1</p:he>s |
| 285 |
is useful.</p:i> |
| 286 |
</p:current> |
| 287 |
<p:H4 section="struct/global.html#edef-H1"/> |
| 288 |
<p:UG fragment="DTD"/> |
| 289 |
</p:entry> |
| 290 |
|
| 291 |
<p:entry xml:id="HN-DEEP" s="syntax"> |
| 292 |
<dc:title>No <p:he>h7</p:he> element type</dc:title> |
| 293 |
<p:problem> |
| 294 |
<p:i>The HTML standards provide only six heading levels.</p:i> |
| 295 |
<p:i>Some large documents has more than six section levels, |
| 296 |
although such documents are rare and some people think |
| 297 |
that is a bad practice.</p:i> |
| 298 |
</p:problem> |
| 299 |
<p:situation> |
| 300 |
<p:i>There is non-standard extension element types such as |
| 301 |
<p:he>h7</p:he>, <p:he>h8</p:he> and so on.</p:i> |
| 302 |
<p:i>Using <p:ha>class</p:ha>ed <p:he>div</p:he> is common, |
| 303 |
but <p:ha>class</p:ha> names are vary.</p:i> |
| 304 |
<p:i>XHTML 2.0 proposes unnumbered <p:xhe>h</p:xhe> element type.</p:i> |
| 305 |
</p:situation> |
| 306 |
<p:XH2 section="mod-structural.html#edef_structural_heading"/> |
| 307 |
<p:SW page="hn" anchor="14"/> |
| 308 |
<p:SW page="hn//n"/> |
| 309 |
</p:entry> |
| 310 |
|
| 311 |
<p:entry xml:id="HN-IMPLIED-SECTION" s="semantics"> |
| 312 |
<dc:title>Section Implied by <p:he>h<h:var>n</h:var></p:he> Elements</dc:title> |
| 313 |
<p:ref uri="http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-March/003333.html" |
| 314 |
hrefLang="en"> |
| 315 |
<dc:title xml:lang="en">[whatwg] <h1> to <h6> in <body></dc:title> |
| 316 |
<dc:author xml:lang="en-GB-Hixie">Ian Hickson</dc:author> |
| 317 |
</p:ref> |
| 318 |
</p:entry> |
| 319 |
|
| 320 |
<p:entry xml:id="HR-SEMANTICS" s="semantics"> |
| 321 |
<dc:title><p:he>hr</p:he> Depracation</dc:title> |
| 322 |
<p:problem> |
| 323 |
<p:i>There's discussion that <p:he>hr</p:he> is presentation matter so |
| 324 |
that should not be used.</p:i> |
| 325 |
</p:problem> |
| 326 |
<p:situation> |
| 327 |
<p:i>XHTML 2.0 proposes <p:xhe>separator</p:xhe> element type.</p:i> |
| 328 |
</p:situation> |
| 329 |
<p:XH2 section="mod-structural.html#edef_structural_separator"/> |
| 330 |
</p:entry> |
| 331 |
|
| 332 |
<p:entry xml:id="ISINDEX-SEMANTICS" s="semantics"> |
| 333 |
<dc:title>No <p:he>isindex</p:he> Action Defined</dc:title> |
| 334 |
<p:problem> |
| 335 |
<p:i>HTML 4 fails to sepcify what <p:he>isindex</p:he> is. It only |
| 336 |
says <h:q>This element creates a single-line text input control</h:q> |
| 337 |
but it sounds as if it is equivalent to |
| 338 |
<p:he>input</p:he> <h:code>text</h:code> control.</p:i> |
| 339 |
</p:problem> |
| 340 |
<p:H2/> |
| 341 |
<p:H4 section="interact/forms.html#edef-ISINDEX"/> |
| 342 |
</p:entry> |
| 343 |
|
| 344 |
<p:entry xml:id="NOFRAMES-CONTEXT" s="edit"> |
| 345 |
<dc:title><p:he>noframes</p:he> before <p:he>frame</p:he></dc:title> |
| 346 |
<p:problem> |
| 347 |
<p:i>HTML 4 Specification defines <p:he>noframes</p:he> element should be |
| 348 |
placed <h:em>after</h:em> any <p:he>frame</p:he> or <p:he>frameset</p:he> |
| 349 |
siblings, while HTML 4 DTD allows <p:he>noframes</p:he> anywhere.</p:i> |
| 350 |
</p:problem> |
| 351 |
<p:current> |
| 352 |
<p:i><p:he>noframes</p:he> is placed after any siblings.</p:i> |
| 353 |
</p:current> |
| 354 |
<p:H4 section="present/frames.html#edef-NOFRAMES"/> |
| 355 |
<p:SW page="noframes" anchor="13"/> |
| 356 |
</p:entry> |
| 357 |
|
| 358 |
<p:entry xml:id="NOFRAMES-CONTEXT-M12N" s="edit"> |
| 359 |
<dc:title><p:he>noframes</p:he> in <p:he>body</p:he></dc:title> |
| 360 |
<p:problem> |
| 361 |
<p:i>XHTML m12n Abstract Module Definition |
| 362 |
does not allow <p:he>noframes</p:he> elements |
| 363 |
in <p:he>body</p:he>.</p:i> |
| 364 |
<p:i>In <p:fileName>xhtml-legacy-redecl-1.mod</p:fileName>, |
| 365 |
parameter entity <h:code>%BlkSpecial.class</h:code> |
| 366 |
contains <h:code>%noframes.qname;</h:code>.</p:i> |
| 367 |
</p:problem> |
| 368 |
<p:current> |
| 369 |
<p:i><p:he>noframes</p:he> in <p:he>body</p:he> is uncommon.</p:i> |
| 370 |
</p:current> |
| 371 |
<p:ref uri="http://web.archive.org/web/20020106151447/http://www1.odn.ne.jp/bungaku-shitsu/appendix/diary/d0112-3.html#day24-4" |
| 372 |
hrefLang="ja"> |
| 373 |
<dc:title xml:lang="en">bubble hour - 2001/12 #3</dc:title> |
| 374 |
</p:ref> |
| 375 |
<p:SW page="noframes" anchor="1"/> |
| 376 |
<p:M12N section="DTD/xhtml-legacy-redecl-1.mod"/> |
| 377 |
</p:entry> |
| 378 |
|
| 379 |
<p:entry xml:id="NOFRAMES-RENDERING" s="edit"> |
| 380 |
<dc:title>Rendering Both <p:he>frame</p:he> and <p:he>noframes</p:he></dc:title> |
| 381 |
<p:problem> |
| 382 |
<p:i>HTML 4 forces user agents to render either |
| 383 |
<p:he>frame</p:he> or <p:he>noframes</p:he>.</p:i> |
| 384 |
</p:problem> |
| 385 |
<p:current> |
| 386 |
<p:i>Frame$B!>(Bdisabled browsers often rendering both <p:he>noframes</p:he> |
| 387 |
and <p:he>frame</p:he> (as an anchor like <p:he>a</p:he>).</p:i> |
| 388 |
</p:current> |
| 389 |
<p:H4 section="present/frames.html#edef-NOFRAMES"/> |
| 390 |
<p:SW page="noframes" anchor="14"/> |
| 391 |
</p:entry> |
| 392 |
|
| 393 |
<p:entry xml:id="NOFRAMES-IN-FRAMESET-IN-FRAMESET" s="semantics"> |
| 394 |
<dc:title><p:he>noframes</p:he> in nesting <p:he>frameset</p:he></dc:title> |
| 395 |
<p:problem> |
| 396 |
<p:i>HTML 4 DTD allows <p:he>noframes</p:he> in <p:he>frameset</p:he> |
| 397 |
in <p:he>frameset</p:he>.</p:i> |
| 398 |
</p:problem> |
| 399 |
<p:current> |
| 400 |
<p:i><p:he>noframes</p:he> in <p:he>frameset</p:he> |
| 401 |
in <p:he>frameset</p:he> is uncommon.</p:i> |
| 402 |
</p:current> |
| 403 |
</p:entry> |
| 404 |
|
| 405 |
<p:entry xml:id="NOSCRIPT-RENDERING" s="semantics"> |
| 406 |
<dc:title>When should <p:he>noscript</p:he> should be rendered?</dc:title> |
| 407 |
<p:problem> |
| 408 |
<p:i>It is unclear what <p:he>noscript</p:he> element should |
| 409 |
be rendered and what should not.</p:i> |
| 410 |
</p:problem> |
| 411 |
<p:situation> |
| 412 |
<p:i>HTML 4 says that a user agent <h:q>doesn't support a scripting |
| 413 |
language invoked by a script element earlier in the document</h:q>, |
| 414 |
then it should be rendered. <h:q>Earlier</h:q> is insufficient |
| 415 |
when multiple script languages are in use.</p:i> |
| 416 |
<p:i>Some people thinks mixing multiple language is bad practice.</p:i> |
| 417 |
</p:situation> |
| 418 |
<p:H4 section="interact/scripts.html#edef-NOSCRIPT"/> |
| 419 |
<p:SW page="noscript" anchor="2"/> |
| 420 |
</p:entry> |
| 421 |
|
| 422 |
<p:entry xml:id="NOSCRIPT-CONTEXT-AND-CONTENT" s="syntax"> |
| 423 |
<dc:title>Context and Content for <p:he>script</p:he> and |
| 424 |
<p:he>noscript</p:he></dc:title> |
| 425 |
<p:problem> |
| 426 |
<p:i><p:he>noscript</p:he> is a block$B!>(Blevel element type while |
| 427 |
<p:he>script</p:he> is able to be used as an inline element.</p:i> |
| 428 |
</p:problem> |
| 429 |
<p:H4 section="interact/scripts.html#edef-NOSCRIPT"/> |
| 430 |
<p:SW page="noscript" anchor="7"/> |
| 431 |
</p:entry> |
| 432 |
|
| 433 |
<p:entry xml:id="P-CONTENT" s="syntax"> |
| 434 |
<dc:title>Block$B!>(BLevel Contents for <p:he>p</p:he></dc:title> |
| 435 |
<p:problem> |
| 436 |
<p:i>Block$B!>(Blevel contents, such as lists, are not allowed in |
| 437 |
<p:he>p</p:he>.</p:i> |
| 438 |
</p:problem> |
| 439 |
<p:situation> |
| 440 |
<p:i>This is TimBL's choice to keep compatibility with word processors.</p:i> |
| 441 |
<p:i>People don't think this is serious problem until style sheets |
| 442 |
becomes common and writing <h:code></p></h:code> end tag |
| 443 |
becomes common.</p:i> |
| 444 |
<p:i>It is more important for languages where breaking a sentence |
| 445 |
by blocks is common.</p:i> |
| 446 |
<p:i>XHTML 2.0 proposal allows block$B!>(Blevel contents in <p:xhe>p</p:xhe>.</p:i> |
| 447 |
</p:situation> |
| 448 |
<p:current> |
| 449 |
<p:i>Breaks a paragraph by three blocks (paragraph, block and |
| 450 |
paragraph).</p:i> |
| 451 |
<p:i>Puts blocks in <p:he>p</p:he> ignoring DTD restriction.</p:i> |
| 452 |
<p:i>Change wording not to break a paragraph.</p:i> |
| 453 |
</p:current> |
| 454 |
<p:XH2 section="mod-structural.html#edef_structural_p"/> |
| 455 |
<p:ref uri="http://www.mozilla.org/contribute/writing/markup#para"> |
| 456 |
<dc:title xml:lang="en">mozilla.org Markup Reference</dc:title> |
| 457 |
</p:ref> |
| 458 |
</p:entry> |
| 459 |
|
| 460 |
<p:entry xml:id="TABLE-ATTRIBUTES" s="syntax"> |
| 461 |
<dc:title>Table Presentational Attributes</dc:title> |
| 462 |
<p:problem> |
| 463 |
<p:i>HTML Table Model has a lot of presentational attributes.</p:i> |
| 464 |
</p:problem> |
| 465 |
<p:situation> |
| 466 |
<p:i>Now CSS supports table rendering controls.</p:i> |
| 467 |
</p:situation> |
| 468 |
</p:entry> |
| 469 |
|
| 470 |
|
| 471 |
<p:entry xml:id="TABLE-DATAPAGESIZE" s="edit"> |
| 472 |
<dc:title><p:he>table</p:he> <p:ha>datapagesize</p:ha> Is Not Reserved</dc:title> |
| 473 |
<p:problem> |
| 474 |
<p:i>HTML 4 DTDs (both Strict and Transitional) declare |
| 475 |
<p:ha>datapagesize</p:ha> attribute even if |
| 476 |
<h:code>%HTML.Reserved</h:code> is set to <h:code>IGNORE</h:code>.</p:i> |
| 477 |
</p:problem> |
| 478 |
<p:situation> |
| 479 |
<p:i>HTML 4 DTDs has the attribute definition, although |
| 480 |
its comment mentions it is a <h:q>reserved</h:q> feature.</p:i> |
| 481 |
<p:i>A DTD fragment in the section 11.2.1 of HTML 4 Specification |
| 482 |
does not include it.</p:i> |
| 483 |
</p:situation> |
| 484 |
<p:H4 section="struct/tables.html#edef-TABLE"/> |
| 485 |
<p:H4 section="sgml/dtd.html"/> |
| 486 |
<p:H4 section="sgml/loosedtd.html"/> |
| 487 |
</p:entry> |
| 488 |
|
| 489 |
<p:entry xml:id="EDIT-IN-FLOW" s="semantics"> |
| 490 |
<dc:title><p:he>ins</p:he> and <p:he>del</p:he> in Flow Content</dc:title> |
| 491 |
<p:problem> |
| 492 |
<p:i>Is an <p:he>ins</p:he> or <p:he>del</p:he> element |
| 493 |
block$B!>(Blevel or inline?</p:i> |
| 494 |
<p:i>For example: <h:code><li><ins><p><h:var>...</h:var></p></ins></lt></h:code>, |
| 495 |
<h:code><li><ins><ins><p><h:var>...</h:var></p></ins></ins></lt></h:code>, ...</p:i> |
| 496 |
</p:problem> |
| 497 |
</p:entry> |
| 498 |
|
| 499 |
<p:entry xml:id="ABBR-ACRONYM" s="semantics"> |
| 500 |
<dc:title><p:he>abbr</p:he> vs <p:he>acronym</p:he></dc:title> |
| 501 |
<p:problem> |
| 502 |
<p:i>Distinction between <p:he>abbr</p:he> and <p:he>acronym</p:he> |
| 503 |
is unclear.</p:i> |
| 504 |
</p:problem> |
| 505 |
<p:situation> |
| 506 |
<p:i>HTML 4 has two types for political reason.</p:i> |
| 507 |
<p:i>Distinction between <h:q>abbriviations</h:q> and <h:q>acronyms</h:q> |
| 508 |
is by nature unclear, in particular in some languages.</p:i> |
| 509 |
<p:i>WinIE only supports <p:he>acronym</p:he> while modern |
| 510 |
Web browsers all support both.</p:i> |
| 511 |
</p:situation> |
| 512 |
<p:current> |
| 513 |
<p:i>Those who love standards use only <p:he>abbr</p:he>.</p:i> |
| 514 |
<p:i>Those who think compatibility is very very important use |
| 515 |
only <p:he>acronym</p:he>.</p:i> |
| 516 |
<p:i>There are some people think these element types should be properly |
| 517 |
distincted.</p:i> |
| 518 |
</p:current> |
| 519 |
<p:H4 section="struct/text.html#edef-ABBR"/> |
| 520 |
<p:H4 section="struct/text.html#edef-ACRONYM"/> |
| 521 |
<p:ref uri="http://www.alib.jp/diary/diary_200111.html#diary20011129c" |
| 522 |
hrefLang="ja"> |
| 523 |
<dc:title xml:lang="ja">abbr $BMWAG$H(B acronym $BMWAG(B : W3C day $B$=$N8e(B</dc:title> |
| 524 |
<dc:author xml:lang="ja">KONDOU, Kazuhiro</dc:author> |
| 525 |
</p:ref> |
| 526 |
<p:ref uri="http://groups.google.com/groups?selm=685vol%24fb2%241%40news.sfc.keio.ac.jp" |
| 527 |
hrefLang="ja"> |
| 528 |
<dc:title xml:lang="en">Re: HTML 4.0 becomes W3C Recommendation</dc:title> |
| 529 |
<dc:author xml:lang="ja">Masayasu Ishikawa</dc:author> |
| 530 |
</p:ref> |
| 531 |
<p:ref uri="http://www.w3.org/2001/06/manual/#Misc" hrefLang="en"> |
| 532 |
<dc:title xml:lang="en">W3C Manual of Style</dc:title> |
| 533 |
</p:ref> |
| 534 |
<p:SW page="abbr$B$H(Bacronym"/> |
| 535 |
</p:entry> |
| 536 |
|
| 537 |
<p:entry xml:id="PHRASE-PRESENTATION" s="syntax"> |
| 538 |
<dc:title>Inline Presentational Element Types</dc:title> |
| 539 |
<p:problem> |
| 540 |
<p:i>Even Strict DTDs have presentational element types |
| 541 |
such as <p:he>b</p:he>, <p:he>i</p:he>, |
| 542 |
<p:he>big</p:he> and <p:he>small</p:he>.</p:i> |
| 543 |
</p:problem> |
| 544 |
<p:situation> |
| 545 |
<p:i>HTML 4 discourages their use.</p:i> |
| 546 |
<p:i>Many people think these element types should be deprecated.</p:i> |
| 547 |
<p:i>Some people think these element types are useful |
| 548 |
and less harnful.</p:i> |
| 549 |
</p:situation> |
| 550 |
<p:current> |
| 551 |
<p:i>A lot of people use style sheets for rendering control.</p:i> |
| 552 |
<p:i>A number of recently-issued W3C specifications use these element types |
| 553 |
for rendering control.</p:i> |
| 554 |
<p:i>A number of browsers, including text browsers, have poor |
| 555 |
support for these element types.</p:i> |
| 556 |
</p:current> |
| 557 |
<p:H4 section="present/graphics.html#h-15.2"/> |
| 558 |
</p:entry> |
| 559 |
|
| 560 |
<p:entry xml:id="ABBR-AA" s="semantics"> |
| 561 |
<dc:title><p:he>abbr</p:he> for ASCII Arts</dc:title> |
| 562 |
<p:problem> |
| 563 |
<p:i>WAI proposes to mark up inline ASCII arts by <p:he>abbr</p:he> |
| 564 |
while they are not abbreviations.</p:i> |
| 565 |
</p:problem> |
| 566 |
<p:situation> |
| 567 |
<p:i>Many people think it is inappropriate.</p:i> |
| 568 |
</p:situation> |
| 569 |
<p:ref uri="http://www.w3.org/TR/WCAG10-HTML-TECHS/#ascii-art"> |
| 570 |
<dc:title xml:lang="en">HTML Techniques for Web Content Accessibility |
| 571 |
Guidelines 1.0</dc:title> |
| 572 |
<dc:author xml:lang="en">W3C Web Content Accessibility Guidelines |
| 573 |
Working Group</dc:author> |
| 574 |
</p:ref> |
| 575 |
<p:SW page="abbr" anchor="24"/> |
| 576 |
</p:entry> |
| 577 |
|
| 578 |
<p:entry xml:id="EMPHASIS" s="semantics"> |
| 579 |
<dc:title>Emphasis Levels</dc:title> |
| 580 |
<p:ref uri="http://www.cs.tut.fi/~jkorpela/html/em.html" hrefLang="en"> |
| 581 |
<dc:title xml:lang="en">Emphasis in HTML: em, strong, and de-emphasis</dc:title> |
| 582 |
<dc:author xml:lang="en">Jukka "Yucca" Korpela</dc:author> |
| 583 |
</p:ref> |
| 584 |
<p:ref uri="http://www.mozilla.org/contribute/writing/markup#emphasis"> |
| 585 |
<dc:title xml:lang="en">mozilla.org Markup Reference</dc:title> |
| 586 |
</p:ref> |
| 587 |
</p:entry> |
| 588 |
|
| 589 |
<p:entry xml:id="BR-SEMANTICS" s="semantics"> |
| 590 |
<dc:title>Does <p:he>br</p:he> have any semantics?</dc:title> |
| 591 |
<p:ref uri="http://pc8.2ch.net/test/read.cgi/hp/1103795522/595-" |
| 592 |
hreflang="ja"> |
| 593 |
<dc:title xml:lang="ja">Strict-HTML $B%9%l%C%I(B 26</dc:title> |
| 594 |
</p:ref> |
| 595 |
</p:entry> |
| 596 |
|
| 597 |
<p:entry xml:id="LABEL-FOR" s="semantics"> |
| 598 |
<dc:title><p:he>label</p:he> Targets</dc:title> |
| 599 |
<p:problem> |
| 600 |
<p:i>It is unclear that what kind of elements can be |
| 601 |
<p:he>label</p:he>ed <p:ha>for</p:ha>.</p:i> |
| 602 |
</p:problem> |
| 603 |
<p:situation> |
| 604 |
<p:i>HTML 4 classfies form controls into those having implicit label |
| 605 |
and others, but their distinction is unclear.</p:i> |
| 606 |
<p:i>Common Web borwsers even allows non-form controls such as |
| 607 |
<p:he>a</p:he> anchor as <p:he>label</p:he> target.</p:i> |
| 608 |
</p:situation> |
| 609 |
<p:H4 section="interact/forms.html#form-labels"/> |
| 610 |
<p:SW page="label" anchor="21"/> |
| 611 |
</p:entry> |
| 612 |
|
| 613 |
<p:entry xml:id="OPTION-LABEL" s="edit"> |
| 614 |
<dc:title>What is <p:he>option</p:he> <p:ha>label</p:ha>?</dc:title> |
| 615 |
<p:problem> |
| 616 |
<p:i>Purposes for <p:he>option</p:he> <p:ha>label</p:ha> is undocumented; |
| 617 |
Why it is defined nevertheless there is <p:he>option</p:he> content?</p:i> |
| 618 |
</p:problem> |
| 619 |
<p:H4 section="interact/forms.html#adef-label-OPTION"/> |
| 620 |
<p:H4 section="interact/forms.html#idx-menu-3"/> |
| 621 |
<p:SW page="label" anchor="3"/> |
| 622 |
</p:entry> |
| 623 |
|
| 624 |
<p:entry xml:id="OPTGROUP-NESTING" s="syntax"> |
| 625 |
<dc:title>Nesting <p:he>optgroup</p:he></dc:title> |
| 626 |
<p:problem> |
| 627 |
<p:i>HTML 4 mentions possible future extensions of nesting |
| 628 |
<p:he>optgroup</p:he> elements.</p:i> |
| 629 |
</p:problem> |
| 630 |
<p:H4 section="interact/forms.html#edef-SELECT"/> |
| 631 |
</p:entry> |
| 632 |
|
| 633 |
<p:entry xml:id="RUBY-IN-CLASSIC-HTML" s="syntax"> |
| 634 |
<dc:title>No Non$B!>(BXHTML HTML DTD for <p:he>ruby</p:he></dc:title> |
| 635 |
<p:problem> |
| 636 |
<p:i>There is no W3C DTD for (non$B!>(BXML) HTML document type |
| 637 |
including <p:he>ruby</p:he> vocabulary.</p:i> |
| 638 |
</p:problem> |
| 639 |
<p:situation> |
| 640 |
<p:i>Ruby markup in (non$B!>(BXML) HTML document is popular |
| 641 |
in Japanese community.</p:i> |
| 642 |
<p:i>WinIE 5+ supports simple <p:he>ruby</p:he> markups.</p:i> |
| 643 |
<p:i>There's a popular extension for Gecko browsers to support |
| 644 |
<p:he>ruby</p:he> markups.</p:i> |
| 645 |
<p:i>Microsoft Office supports simple <p:he>ruby</p:he> markups.</p:i> |
| 646 |
<p:i>There're proxies to attach <p:he>ruby</p:he> for children.</p:i> |
| 647 |
</p:situation> |
| 648 |
<p:current> |
| 649 |
<p:i>Use XHTML 1.1 with <h:code>text/html</h:code>.</p:i> |
| 650 |
<p:i>Use XHTML 1.1 with <h:code>application/xhtml+xml</h:code>. |
| 651 |
(This solution have serious compatibility problem.)</p:i> |
| 652 |
<p:i>Use <p:he>ruby</p:he> markups in HTML 4 although it is invalid.</p:i> |
| 653 |
<p:i>Use <p:he>ruby</p:he> markups in <h:code>text/html</h:code> |
| 654 |
document without document type declaration.</p:i> |
| 655 |
<p:i>Note that tags for <p:he>rb</p:he> and end tags |
| 656 |
for <p:he>rp</p:he> and <p:he>rt</p:he> is often omitted.</p:i> |
| 657 |
<p:i>Give up to use <p:he>ruby</p:he> markups.</p:i> |
| 658 |
</p:current> |
| 659 |
<p:ref uri="http://www.akatsukinishisu.net/itazuragaki/2001_10.html#ruby_for_Mozilla_3" |
| 660 |
hrefLang="ja"> |
| 661 |
<dc:title xml:lang="ja">Mozilla$B$G%k%SI=<((B3</dc:title> |
| 662 |
<dc:author xml:lang="ja">$BKLB<Z|(B</dc:author> |
| 663 |
</p:ref> |
| 664 |
<p:ref uri="http://piro.sakura.ne.jp/xul/_rubysupport.html" hrefLang="ja"> |
| 665 |
<dc:title xml:lang="en">XHTML $B%k%S%5%]!<%H(B</dc:title> |
| 666 |
<dc:author>Piro</dc:author> |
| 667 |
</p:ref> |
| 668 |
<p:ref uri="http://piro.sakura.ne.jp/xul/_rubysupport.html.en" hrefLang="en"> |
| 669 |
<dc:title xml:lang="en">XHTML Ruby Support</dc:title> |
| 670 |
<dc:author>Piro</dc:author> |
| 671 |
</p:ref> |
| 672 |
<p:SW page="ruby"/> |
| 673 |
</p:entry> |
| 674 |
|
| 675 |
<p:entry xml:id="META-NAMING" s="syntax"> |
| 676 |
<dc:title>Naming Rules for <p:he>meta</p:he> <p:ha>name</p:ha>s</dc:title> |
| 677 |
<p:ref uri="http://www.altheim.com/specs/meta/NOTE-xhtml-augmeta.html" |
| 678 |
hrefLang="en"> |
| 679 |
<dc:title xml:lang="en">Augmented Metadata in XHTML</dc:title> |
| 680 |
<dc:author xml:lang="en">Murray Altheim</dc:author> |
| 681 |
</p:ref> |
| 682 |
<p:ref uri="http://www.nla.gov.au/metadata.html" hrefLang="en"> |
| 683 |
<dc:title xml:lang="en">Web Site Metadata Strategies and Guidelines</dc:title> |
| 684 |
<dc:author xml:lang="en">National Library of Australia</dc:author> |
| 685 |
</p:ref> |
| 686 |
</p:entry> |
| 687 |
|
| 688 |
<p:entry xml:id="META-HTTP-EQUIV" s="syntax"> |
| 689 |
<dc:title>Non$B!>(BASCII Characters In <p:he>meta</p:he> <p:ha>http-equiv</p:ha> |
| 690 |
<p:ha>content</p:ha></dc:title> |
| 691 |
<p:problem> |
| 692 |
<p:i>Non$B!>(BASCII characters should be restricted in |
| 693 |
<p:ha>content</p:ha> attribute values of |
| 694 |
<p:he>meta</p:he> elements which have <p:ha>http-equiv</p:ha> |
| 695 |
attribute, since HTTP defines header fields to be written in |
| 696 |
ASCII + any right$B!>(Bhand half (HTTP/1.0) or ISO/IEC 8859$B!>(B1 |
| 697 |
(HTTP/1.1).</p:i> |
| 698 |
</p:problem> |
| 699 |
<p:current> |
| 700 |
<p:i>Some HTML documents have <p:ha>content</p:ha> with |
| 701 |
non$B!>(BASCII characters, particularlly for |
| 702 |
<h:code>Default-Style</h:code> header field.</p:i> |
| 703 |
</p:current> |
| 704 |
</p:entry> |
| 705 |
|
| 706 |
<p:entry xml:id="EMBED-META" s="syntax"> |
| 707 |
<dc:title>Embedding Metadata in HTML Document</dc:title> |
| 708 |
<p:ref uri="http://www.altheim.com/specs/meta/NOTE-xhtml-augmeta.html" |
| 709 |
hrefLang="en"> |
| 710 |
<dc:title xml:lang="en">Augmented Metadata in XHTML</dc:title> |
| 711 |
<dc:author xml:lang="en">Murray Altheim</dc:author> |
| 712 |
</p:ref> |
| 713 |
</p:entry> |
| 714 |
|
| 715 |
<p:entry xml:id="TITLE-HIGHER-PROTOCOL" s="syntax"> |
| 716 |
<dc:title><p:he>title</p:he> Is Redundant If Higher$B!>(BLevel Protocol |
| 717 |
Has It</dc:title> |
| 718 |
<p:problem> |
| 719 |
<p:i><p:he>title</p:he> is redundant if higher$B!>(Blevel protocol has |
| 720 |
the same information, e.g. <h:code>Subject</h:code> header |
| 721 |
field in RFC 2822 messages.</p:i> |
| 722 |
</p:problem> |
| 723 |
<p:situation> |
| 724 |
<p:i><p:he>title</p:he> is required in HTML DTDs.</p:i> |
| 725 |
<p:i>It is common to present higher$B!>(Blevel title only in MUAs |
| 726 |
(and does not provide <p:he>title</p:he> until user |
| 727 |
requests to do so).</p:i> |
| 728 |
<p:i>There's no standardized DOM interface to access to |
| 729 |
higher$B!>(Blevel protocol providing information.</p:i> |
| 730 |
</p:situation> |
| 731 |
<p:current> |
| 732 |
<p:i>Puts the same <h:q>title</h:q> to both <p:he>title</p:he> |
| 733 |
and higher$B!>(Blevel protocol field.</p:i> |
| 734 |
<p:i>Puts the title to higher$B!>(Blevel field and provides no |
| 735 |
<p:he>title</p:he> although it is invalid against DTD.</p:i> |
| 736 |
<p:i>Puts the title to higher$B!>(Blevel field and lefts |
| 737 |
<p:he>title</p:he> blank. Although it is valid against |
| 738 |
DTD, it should be bad solution.</p:i> |
| 739 |
</p:current> |
| 740 |
</p:entry> |
| 741 |
|
| 742 |
<p:entry xml:id="HEAD-PROFILE-RELATIVE" s="syntax"> |
| 743 |
<dc:title>Relative <p:ha>profile</p:ha> URI References</dc:title> |
| 744 |
<p:problem> |
| 745 |
<p:i>Should relative references be allowed in <p:ha>profile</p:ha> |
| 746 |
attribute?</p:i> |
| 747 |
<p:i>If so, should <p:he>base</p:he> <p:ha>href</p:ha> be |
| 748 |
used to resolve it?</p:i> |
| 749 |
</p:problem> |
| 750 |
<p:situation> |
| 751 |
<p:i>HTML 4 defines the attribute as <h:code>%URI;</h:code> so |
| 752 |
that relative references are allowed.</p:i> |
| 753 |
<p:i>HTML 4 forces authors to place <p:he>base</p:he> element |
| 754 |
before any relative references, but it is inpossible |
| 755 |
in <p:ha>profile</p:ha> case.</p:i> |
| 756 |
<p:i>HTML 4 proposes an XML Namespaces$B!>(Blike usage of <p:ha>profile</p:ha> |
| 757 |
URI references. XML Names deprecates use of relative references.</p:i> |
| 758 |
</p:situation> |
| 759 |
<p:current> |
| 760 |
<p:i>Using relative references as <p:ha>profile</p:ha> is rare.</p:i> |
| 761 |
</p:current> |
| 762 |
</p:entry> |
| 763 |
|
| 764 |
<p:entry xml:id="XML-STYLESHEET-LINK" s="edit"> |
| 765 |
<dc:title>XHTML Documents With Both <h:code>xml-stylesheet</h:code> |
| 766 |
And <p:he>link</p:he> Linking Style Sheets</dc:title> |
| 767 |
<p:problem> |
| 768 |
<p:i>Relationship between <h:code>xml-stylesheet</h:code> and |
| 769 |
<p:he>link</p:he> linking style sheets in XHTML documents |
| 770 |
should be clarified.</p:i> |
| 771 |
</p:problem> |
| 772 |
<p:current> |
| 773 |
<p:i>Many XHTML documents do have both syntax of declarations |
| 774 |
for the same style sheets.</p:i> |
| 775 |
</p:current> |
| 776 |
</p:entry> |
| 777 |
|
| 778 |
<p:entry xml:id="TYPE-CONTENT-TYPE" s="syntax"> |
| 779 |
<dc:title>DataType <h:code>ContentType</h:code> With Parameters</dc:title> |
| 780 |
<p:problem> |
| 781 |
<p:i>In HTML 4, it is unclear whether <h:code>%ContentType</h:code> |
| 782 |
attribute values can contain Internet Media Type parameters.</p:i> |
| 783 |
</p:problem> |
| 784 |
<p:situation> |
| 785 |
<p:i>HTML 4 Specification does not mention to parameters.</p:i> |
| 786 |
<p:i>HTML 4 defines <h:code>%ContentType</h:code> attributes as |
| 787 |
case$B!>(Binsensitive.</p:i> |
| 788 |
<p:i>Some Internet Media Type requires its parameters to identify |
| 789 |
a particular sub$B!>(Bsub$B!>(Btype.</p:i> |
| 790 |
<p:i>While media types, subtypes and parameter names are case$B!>(Binsensitive, |
| 791 |
parameter values are not.</p:i> |
| 792 |
</p:situation> |
| 793 |
<p:current> |
| 794 |
<p:i>Media type with parameters are often used in <h:code>%ContentType</h:code> |
| 795 |
attributes, e.g. <h:code>type="text/javascript; |
| 796 |
version=1.2"</h:code>.</p:i> |
| 797 |
</p:current> |
| 798 |
</p:entry> |
| 799 |
|
| 800 |
<p:entry xml:id="ATTR-MEDIA-DEFAULT" s="syntax"> |
| 801 |
<dc:title><p:ha>media</p:ha> Default</dc:title> |
| 802 |
<p:problem> |
| 803 |
<p:i>Default value of <p:ha>media</p:ha> should be <h:code>all</h:code>.</p:i> |
| 804 |
</p:problem> |
| 805 |
<p:situation> |
| 806 |
<p:i>HTML 4 defines <h:code>screen</h:code> is default in prose.</p:i> |
| 807 |
<p:i>HTML 4 DTDs define it as <h:code>#IMPLIED</h:code>.</p:i> |
| 808 |
</p:situation> |
| 809 |
<p:current> |
| 810 |
<p:i>Most authors and browsers assume that default is |
| 811 |
<h:code>all</h:code>.</p:i> |
| 812 |
</p:current> |
| 813 |
</p:entry> |
| 814 |
|
| 815 |
<p:entry xml:id="ATTR-MEDIA-SEMANTICS" s="syntax"> |
| 816 |
<dc:title><p:ha>media</p:ha> For Non$B!>(BStyle Sheet Links</dc:title> |
| 817 |
<p:problem> |
| 818 |
<p:i>Can <p:ha>media</p:ha> be used for non$B!>(Bstyle sheet links?</p:i> |
| 819 |
</p:problem> |
| 820 |
<p:situation> |
| 821 |
<p:i>HTML 4 implies it is for style sheets.</p:i> |
| 822 |
<p:i>HTML 4 DTD comment (informative) describes it is also |
| 823 |
useful for links to printable version.</p:i> |
| 824 |
<p:i>In HTML 4, <p:he>link</p:he> and <p:he>style</p:he> have |
| 825 |
<p:ha>media</p:ha> but <p:he>a</p:he> and <p:he>area</p:he> |
| 826 |
does not.</p:i> |
| 827 |
</p:situation> |
| 828 |
</p:entry> |
| 829 |
|
| 830 |
<p:entry xml:id="ATTR-DIR-REQUIRED" s="edit"> |
| 831 |
<dc:title><p:ha>dir</p:ha> Attribute is Optional</dc:title> |
| 832 |
<p:problem> |
| 833 |
<p:i>XHTML m12n Specification marks <p:ha>dir</p:ha> attribute |
| 834 |
as required in the abstract module definition.</p:i> |
| 835 |
</p:problem> |
| 836 |
<p:situation> |
| 837 |
<p:i>Any other specifications and XHTML m12n DTD module |
| 838 |
defines it as optional.</p:i> |
| 839 |
</p:situation> |
| 840 |
<p:current> |
| 841 |
<p:i>No one believes it.</p:i> |
| 842 |
</p:current> |
| 843 |
</p:entry> |
| 844 |
|
| 845 |
<p:entry xml:id="ATTR-DIR-INHERIT" s="semantics"> |
| 846 |
<dc:title><p:ha>dir</p:ha> Inheritance</dc:title> |
| 847 |
<p:problem> |
| 848 |
<p:i><p:ha>dir</p:ha> inheritance is not well-defined for |
| 849 |
<p:he>title</p:he>, <p:he>li</p:he> and so on.</p:i> |
| 850 |
<p:i>Inherited <p:ha>dir</p:ha> values and style sheet specifications |
| 851 |
would make confusion.</p:i> |
| 852 |
</p:problem> |
| 853 |
<p:situation> |
| 854 |
<p:i>HTML 4 defines inheriting rules of <p:ha>dir</p:ha> |
| 855 |
for block$B!>(Blevel elements and inline elements.</p:i> |
| 856 |
<p:i>It is independent of style sheet properties.</p:i> |
| 857 |
</p:situation> |
| 858 |
<p:H4 section="struct/dirlang.html#blocklevel-bidi"/> |
| 859 |
</p:entry> |
| 860 |
|
| 861 |
<p:entry xml:id="XHTML-MEDIA-TYPE" s="syntax"> |
| 862 |
<dc:title>XHTML Documents Labeled as <h:code>text/html</h:code></dc:title> |
| 863 |
<p:ref uri="mid:f5by8dfh5cr.fsf@erasmus.inf.ed.ac.uk" hrefLang="en"> |
| 864 |
<dc:title xml:lang="en">Re: RDDL->RDF (was Re: Draft agenda of |
| 865 |
22 February 2005 TAG</dc:title> |
| 866 |
<dc:author xml:lang="en">Henry S. Thompson</dc:author> |
| 867 |
</p:ref> |
| 868 |
</p:entry> |
| 869 |
|
| 870 |
<p:entry xml:id="HTTP-LINK" s="syntax"> |
| 871 |
<dc:title>HTTP <h:code>Link</h:code> Header Field</dc:title> |
| 872 |
<p:problem> |
| 873 |
<p:i>HTML 4 describes <h:code>Link</h:code> header field |
| 874 |
differently as RFC 2068 (e.g. <h:code>anchor</h:code> parameter, |
| 875 |
<p:ha>media</p:ha> attribute).</p:i> |
| 876 |
<p:i><h:q>SGML entities</h:q> are allowed in that field |
| 877 |
but what it has intended is unclear.</p:i> |
| 878 |
</p:problem> |
| 879 |
<p:current> |
| 880 |
<p:i><h:code>anchor</h:code> is uncommon.</p:i> |
| 881 |
<p:i><h:q>Entities</h:q> in <h:code>Link</h:code> is uncommon.</p:i> |
| 882 |
</p:current> |
| 883 |
</p:entry> |
| 884 |
|
| 885 |
<p:entry xml:id="SCRIPT-EVENT-FOR" s="edit"> |
| 886 |
<dc:title><p:he>script</p:he> <p:ha>event</p:ha> and |
| 887 |
<p:ha>for</p:ha> Is Not Reserved</dc:title> |
| 888 |
<p:problem> |
| 889 |
<p:i>HTML 4 DTDs (both Strict and Transitional) declare |
| 890 |
<p:ha>event</p:ha> and <p:ha>for</p:ha> attributes even if |
| 891 |
<h:code>%HTML.Reserved</h:code> is set to <h:code>IGNORE</h:code>.</p:i> |
| 892 |
<p:i>In HTML marked-up version of HTML 4 DTDs (both Strict and Transitional), |
| 893 |
<p:ha>for</p:ha> attribute is linked to the definition |
| 894 |
of <p:ha>for</p:ha> attribute of <h:em><p:he>label</p:he> |
| 895 |
element</h:em>, which has different syntax and semantics.</p:i> |
| 896 |
</p:problem> |
| 897 |
<p:situation> |
| 898 |
<p:i>HTML 4 DTDs has the attribute definition, although |
| 899 |
their comment mention they are <h:q>reserved</h:q> features.</p:i> |
| 900 |
<p:i>A DTD fragment in the section 18.2.1 of HTML 4 Specification |
| 901 |
does not include it.</p:i> |
| 902 |
</p:situation> |
| 903 |
<p:H4 section="interact/scripts.html#edef-SCRIPT"/> |
| 904 |
<p:H4 section="sgml/dtd.html"/> |
| 905 |
<p:H4 section="sgml/loosedtd.html"/> |
| 906 |
</p:entry> |
| 907 |
</p:doc> |
Parent Directory
| 
Revision Log