W3C home > Mailing lists > Public > public-diselect-editors@w3.org > July to September 2006

Re: HTML WG comments on DI Select

From: Rhys Lewis <Rhys.Lewis@volantis.com>
Date: Mon, 4 Sep 2006 10:34:38 +0100
To: "public-diselect-editors@w3.org" <public-diselect-editors@w3.org> , "steven.pemberton@cwi.nl" <steven.pemberton@cwi.nl>
Message-ID: <20060904103438956.00000002524@v-rhys3>
Generator Microsoft Word 11 (filtered medium) Dear Steven, 

Thanks for the comments from the HTML working group concerning our DISelect specification last call in http://lists.w3.org/Archives/Public/public-diselect-editors/2005AprJun/0021.html.

DIWG agrees with the HTML group that mixing styling and content is generally undesirable, and it is not our intent to promote such practices. Just because something is possible does not make it desirable. XHTML, through the style attribute, makes mixing of style and content possible. That doesn' t automatically mean that such usage should be encouraged.

It is certainly not DIWG' s intent to promote DISelect as an alternative to existing styling methods. Indeed, we would anticipate it being used, for example, to allow fine control over which of a number of CSS stylesheets might be used for different devices. Selection itself might take place completely external to the document containing the content.

These more realistic uses of DISelect are difficult to use when trying to describe and illustrate the basic syntax. DIWG believes that the best way to encourage good practice in the use of DISelect is to publish a primer alongside the formal specification. Work on this document has begun and publication will occur sometime after that of the formal specification.

DIWG expects to issue a second last call for the DISelect specification shortly. There have been a significant number of modifications.

By the way, the DIWG' s experience of developing sites that can be used by a multitude of different kinds of device shows categorically that while it is possible to use XSLT and CSS to create different versions, it is impractical to do so. Modern mobile systems, for example, avoid direct use of XSLT for adaptation, though they do use it in other roles. Such systems must cope with thousands of different kinds of device.

In summary, we will not make any specific modifications to the DISelect specification in response to this comment, but we will introduce a primer to assist readers in understanding how DISelect can be used in practice. 

Best wishes
Received on Monday, 4 September 2006 09:35:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:41:55 UTC