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

McCathieNevile-1

From: Rhys Lewis <rhys.lewis@volantis.com>
Date: Wed, 24 Aug 2005 10:17:02 +0100
Message-ID: <D18551A6C7EA6241B960D4909EB75DF5023092B4@squid.volantis-uk>
To: <chaals@opera.com>
Cc: <public-diselect-editors@w3.org>

Hello Charles,

Once again, thanks for your comments on the content selection last call in 
http://lists.w3.org/Archives/Public/public-diselect-editors/2005AprJun/0010.html

This mail documents DIWG's response to your comment numbered 1. DIWG has recorded this comment as McCathieNevile-1.

Comment McCathieNevile-1: Window Size
=====================================

1. The spec allows you to ask questions about the size of the window, and about the display size (resolution and colours) of the entire device. This seems of limited use except in allowing authors to determine a layout for the fullscreen and then if there is a difference just put in a message like "move to fullscreen to get the page". This seems to me a bad thing to encourage. I am wondering if there are things that make it more useful? (The only one I could think of was knowing that if the user is at fullscreen they don't see other windows, etc... I am not sure if this should be exposed to authors...)

DIWG Response
=============

The particular functions described in the document are equivalents of those proposed for CSS Media Queries. We have deliberately retained exactly the same functions as those used in that specification. This was stressed [1] in the document as follows: "They have been chosen to implement features similar to those associated with Media Queries. No attempt as been made to change the Media Queries function, except for two additions in the case of aspect ratio and the addition of a defaulting mechanism." This explanation is retained in the revised documents. Note also that these functions are only a minimum starting set and that the use of additional functions is permitted. This is explained [1] thus: "It is anticipated that, in future, additional sets of functions [will be] defined for more comprehensive access to the delivery context."

Furthermore, the execution of any function to access delivery context properties is only meaningful where such properties are present in the delivery context. The existence of a function to access a property does not imply that such a property actually exists in the delivery context.


[1]  <http://www.w3.org/TR/cselection/#sec-starter-set>


Changes to the DISelect document
===

DIWG does not propose to make any changes to the document as a direct result of this comment other than to correct the typo indicated by the "[will be]" in the response text. However, as a result of other comments, DIWG does plan to move the discussion of the functions to a separate document. DIWG will take the opportunity to emphasize the fact that this is a minimal starter set of delivery context functions.

Best wishes

Rhys
Received on Wednesday, 24 August 2005 09:13:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:11:10 GMT