CAPTCHA draft - updates and discussion.

Janina: there remain small issues with the draft, including structural changes that need to take place before a CfC is issued.

Janina will meet with Michael to discuss the changes (e.g., nesting of section elements).

Janina: example: no specific section on ReCAPTCHA in the multi-party material.

Dave suggests making the examples more distinct in the presentation - making them stand out for those who are skim reading.

Janina approves of the idea and proposes we could similarly use "Suggestion:" for where we make suggestions/recommendations.

Janina notes it would be difficult to be consistent with the suggestion part, since some of the "suggestions" comprise entire sections/subsections.

Judy and Janina discuss the extent of the rewriting that would be required.

Scott: suggests this is worth looking at more closely, and he would like to see circulation of the public draft soon.

Janina: proposes to work on markup/structure with Michael; then to use the js-captcha branch to play with organizational fine tuning.
... fixing the section nesting first is necessary, then we can tune the emphasis of suggestions.
... think sections 4.1 and 4.2 merit further development.

Last sentence of section 4.1: we should clarify the discussion of single sign-on, some of which is carried over from the 2004/2005 published Note.

Janina suggests perhaps we shouldn't state single sign-in is the solution to the CAPTCHA problem.

Judy: notes that the data collection and privacy issues raise concerns, as does the problem that large areas of a user's activities ultimately become protected by a single set of credentials, raising a security issue.

Janina thinks the latter concern has been addressed to some extent by large providers, through detection of suspect activity.

Judy: suggests the risks involved and the measures that need to be taken should be noted in the discussion.

Janina: offers to add a sentence or two on the point, as well as the data collection/aggregation problem.
... where we discuss multi-device use (section 4.2). The text should be updated to reflect the fact that multi-device approaches are now current practice. These work, but also have the same risks and should be rewritten accordingly.

Janina (clarifying): logging into a system using multiple devices can be used as a means of overcoming the CAPTCHA problem.

Janina: section 4.2 should be rephrased so that it isn't in the future tense.

Sometimes the need is to validate that a person is human but not to identify the individual. This need isn't met by the approaches discussed in 4.2.

Janina reads the relevant text from section 4.2 of the current draft.

Scott: suggests changing "could" to "can where appropriate.

Scott queries what the issues are.

Janina: we need to clarify the discussion of these authentication methods in relation to the over-all objective served by CAPTCHA - to identify that the user is human, and not necessarily to identify the user.

Scott suggests clarifying that these technologies can be used in a CAPTCHA context.

Judy: in the introduction or in a suitable section we can clarify that some techniques go further than meeting the goal which CAPTCHA serves - and they do so by authenticating the identity of the user.

Janina: in the authentication discussions, the use cases served by CAPTCHA (of determining that the user is human without establishing identity) should be raised.

Agreement: to work on this aspect of the text over several days. If it evolves into a larger discussion, consider working on it in parallel with processing the next phase of public review comments on the upcoming workign draft.

Accessibility of domain-specific content and notations - navigation and interaction.

Janina suggests the SVG-based navigation technique should be listed.

Janina queries whether the JavaScript locks the user into a particular navigation strategy.

We'll resume this discussion at the next meeting.

Jason will add references to the wiki or post to the list if there isn't a suitable place in the wiki page.

We'll schedule the next RQTF meeting for two weeks hence.

Everyone agrees on the excellence of Janina's CAPTCHA Note work.

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: janina, scott_h, jasonjgw, sloandr
Present: janina scott_h jasonjgw sloandr
No ScribeNick specified.  Guessing ScribeNick: jasonjgw
Inferring Scribes: jasonjgw

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 23 Jan 2019
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)