W3C home > Mailing lists > Public > public-html@w3.org > June 2007

Re: <code type="...">

From: Josh Sled <jsled@asynchronous.org>
Date: Thu, 21 Jun 2007 11:20:48 -0400
To: Dmitry Turin <html60@narod.ru>
Cc: public-html@w3.org
Message-ID: <87sl8lxrjj.fsf@phoenix.asynchronous.org>
Dmitry Turin <html60@narod.ru> writes:
> 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 don't understand what you're saying.

The semantics of the code element are defined by
<http://www.whatwg.org/specs/web-apps/current-work/#the-code>.  I'm not
suggesting that @type refines those semantics.  I'm suggesting that if you
include (a fragment of) content, it is useful to know the media type of that
content.  If the content was fetched (via HTTP, at least), the headers of
that response can indicate the type; but here, as the content is included
inline, there is no other way to determine the media type.


> 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.

In the same way that <object type> specifies a technical characteristic (the
media type) of the referenced object, <code type> would specify a technical
characteristic (the media type) of the in-lined code.

-- 
...jsled
http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo ${a}@${b}

Received on Thursday, 21 June 2007 15:21:48 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:45 UTC