See also: IRC log
<trackbot> Date: 10 April 2013
<janina> Meeting: IndieUI Task Force Teleconference
<janina> Thanks, Ted!
James: still planning to separate clearly those items in User Contexts that correspond to operating system settings. Other minor changes have been made.
Andy raises the question of how to draw the distinction, given differences between settings available on different systems.
James: suggests prefixing each item with "setting" or "preference"; "setting" would mean that the item is on at the moment, e.g., that colour inversion is active already. The application need not respond to this. The related preference would be light on dark or the inverse, to which the application would respond with style sheet changes.
This is a response to the objection that having such parallel keys (inverse and light/dark) is confusing.
In response to discussion: the preference is needed for captions, for example, where the native caption format is not supported by the Web application.
<richardschwerdtfeger> q
<richardschwerdtfeger> q
<richardschwerdtfeger> q
<richardschwerdtfeger> q_
After discussion: it is noted that there are difficulties that arise when there are both settings and preferences (e.g., for captions) and each may be true in different circumstances.
Example: HTML 5 video player that doesn't use one of the available timed text formats. Janina and James discuss this and related cases that may arise in an HTML 5 environment to delineate the use case clearly.
Janina notes that regulatory requirements may impose uniformity upon the implementation of captions/descriptions/video requirements, shifting away from proprietary implementations of such features.
James: in that case let's specify captions as a setting only, not a secondary preference.
Michael has no further remarks to make, other than to note that inference derivation need not be closely connected to the lexical form of the preferences.
He suggests taking this discussion to the detailed level.
Andy raises the issue of how well this scheme corresponds to the properties defined by other existing and emerging specifications.
Michael clarifies that the use of key-value pairs (or not) doesn't affect the vocabulary and therefore shouldn't influence the viability of mapping our properties to those defined elsewhere.
Andy proposes to consider the consequences of this change further.
Michael clarifies that the proposal changes syntax, not the technical content - in particular, not the question of which properties are included in 1.0.
Janina raises the question of scheduling the next meeting.
There is a widespread preference for 1 May.
<MichaelC> ACTION: Andy to review user preferences for implications of key-value pair proposal [recorded in http://www.w3.org/2013/04/10-indie-ui-minutes.html#action01]
<trackbot> Created ACTION-49 - Review user preferences for implications of key-value pair proposal [on Andy Heath - due 2013-04-17].
Janina notes the recent engagement of the e-publishing industry in the development of HTML 5 and recent meetings identifying their requirements.
This led to suggestions (reflecting prior proposals from the accessibility community) for CSS to reflect users' colour contrast preferences, e.g., for night-time reading of an e-published book.
An inverted colours setting would need to be different according to context (e.g., image vs. surrounding text).
Janina will cite the minutes of the relevant meeting when they become available.
James recalls additional media queries' being proposed by PF.
Janina notes that further steps need to be taken with respect to this proposal.
James notes a new draft of CSS Media Queries and acknowledges overlap with the User Preferences; items supported by Media Queries (contrast settings for example) need not be duplicated in the User Preferences spec.
He suggests that the privacy issues would be different in the case of media queries and there might be greater uptake.
He clarifies that it's possible to change CSS properties based on the queries and it might (but this needs to be checked) allow a notification to be given to the application when a boundary is reached.
Rich notes the use case of changes in lighting conditions that require the device to modify contrast settings; this should be supported either in media queries or a notification to the Web application.
James notes that if the result of the media query changes, the CSS properties are updated.
James clarifies in response to a question from Andy that changes in environmental conditions, detected by the device, could result in property changes by virtue of a CSS media query.
James suggests preparing a proposed list of items that should be taken up in media queries. These would be matters that can be well handled in CSS and would not then be duplicated in User Contexts.
Michael suggests inquiring with the CSS WG as to which items should be covered by media queries and which in User Contexts; active dialogue is reuired.
He notes that there are needs/preferences that can obviously be treated as media queries and others which are less clear; these need to be discussed.
<MichaelC> ACTION: james to prepare a list of user context properties that might be able to be covered by media queries [recorded in http://www.w3.org/2013/04/10-indie-ui-minutes.html#action02]
<trackbot> Created ACTION-50 - Prepare a list of user context properties that might be able to be covered by media queries [on James Craig - due 2013-04-17].
James proposes to draw up a preliminary list for media queries.
James notes font size and contrast as the obvious candidates for media queries.
<jcraig> http://w3c-test.org/csswg/mediaqueries3/
Michael notes that a call for agenda will be issued by 26 April; participants should propose items for discussion at the meeting.
This is scribe.perl Revision: 1.137 of Date: 2012/09/20 20:19:01 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/we could specify captions as a setting, not a preference./let's specify captions as a setting only, not a secondary preference./ No ScribeNick specified. Guessing ScribeNick: jasonjgw Inferring Scribes: jasonjgw Default Present: Rich_Simpson, Janina_Sajka, jcraig, Jason_White, Andy_Heath, Rich, Michael_Cooper, Cooper Present: Rich_Simpson Janina_Sajka jcraig Jason_White Andy_Heath Rich Michael_Cooper Cooper Found Date: 10 Apr 2013 Guessing minutes URL: http://www.w3.org/2013/04/10-indie-ui-minutes.html People with action items: andy james WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]