- From: Dmitry Turin <html60@narod.ru>
- Date: Thu, 28 Jun 2007 11:23:29 +0300
- To: public-html@w3.org
>> JS> <code> should have a type attribute, which indicates the media type of the >> JS> inlined content(-fragment). >> JS> <code type="text/x-python-source"> >> Let's prolong this idea, and we will describe semantic of all tags ! >> Let's foresee future, and use 'role' for all tags at all. I used term "semantic" not in special informational sense, but in general human sense. JS> I'm not suggesting that @type refines those semantics. I'm suggesting that if you JS> include (a fragment of) content, it is useful to know the media type of that JS> content. Josh, in what are you see difference between "media type" and "semantics" ?? >> JS> Also, I note the analog with <object type=...>. >> There is no analogy, >> because |type| of OBJECT specify technical characteristic, >> but |type| of _all_ tags at all specify semantic characteristic. JS> In the same way that <object type> specifies a technical characteristic (the JS> media type) of the referenced object, <code type> would specify a technical JS> characteristic (the media type) of the in-lined code. I not argue, what is 'type' in OBJECT separately, and what is 'type' in CODE separately, but i'd like to note about comparison characteristic: OBJECT is executed element, but CODE is not, therefore sense of mentioned attribute are different in them, so both attributes can not be technical characteristic simultaneously. >> > <pre><code type="text/x-python-source"> >> > <pre><code type="application/json"> l> However, I don't really see what a type attribute adds that a class l> attribute could not be used to provide instead. No. Values "python", etc have other sense, than style. Attribute 'role' ('semantic') is actually necessary here _as keywords for search robots_. Dmitry Turin HTML6 (6.1.0) http://html60.chat.ru SQL4 (4.1.0) http://sql40.chat.ru Computer2 (2.0.3) http://computer20.chat.ru
Received on Friday, 6 July 2007 12:48:46 UTC