Re: working on the definitions for support personliazion

The problem is that the HTML5 list are tokens for attributes, not human readable names.

That undermines the proposed solution in the SC, where the name can be a method of passing.

Unless we have token/name pairs that are equivalent?

Cheers,

-Alastair


From: "White, Jason J" <jjwhite@ets.org>
Date: Thursday, 27 July 2017 at 19:02
To: David MacDonald <david100@sympatico.ca>
Cc: "lisa.seeman" <lisa.seeman@zoho.com>, WCAG <w3c-wai-gl@w3.org>
Subject: RE: working on the definitions for support personliazion
Resent-From: WCAG <w3c-wai-gl@w3.org>
Resent-Date: Thursday, 27 July 2017 at 19:01

I would be comfortable with David’s suggested approach for now.

From: David MacDonald [mailto:david100@sympatico.ca]
Sent: Thursday, July 27, 2017 2:00 PM
To: White, Jason J <jjwhite@ets.org>
Cc: lisa.seeman <lisa.seeman@zoho.com>; W3c-Wai-Gl-Request@W3. Org <w3c-wai-gl@w3.org>
Subject: Re: working on the definitions for support personliazion

Makes sense Jason...

Personally, I'd rather we just go with the HTML 5 list for the acceptance of the SC, and our vote... seems non controversial and we may be able to get it in without much more discussion...then after August some COGA specific items to it and have those conversations which could be quite time consuming.


Cheers,
David MacDonald



CanAdapt Solutions Inc.

Tel:  613.235.4902

LinkedIn
<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Fdavidmacdonald100&data=02%7C01%7Cjjwhite%40ets.org%7C3ab2142f99ff4b2b471608d4d5194a5b%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636367751980975109&sdata=PmNREUx3iwhc2FBglIMa%2BaDrfxttioKu%2BLHxWipq9Xg%3D&reserved=0>

twitter.com/davidmacd<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fdavidmacd&data=02%7C01%7Cjjwhite%40ets.org%7C3ab2142f99ff4b2b471608d4d5194a5b%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636367751980975109&sdata=luDkwEwQz%2BYte%2BxA0KZsEGN1nnPPDbzQbaZDTcf2%2FK0%3D&reserved=0>

GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDavidMacDonald&data=02%7C01%7Cjjwhite%40ets.org%7C3ab2142f99ff4b2b471608d4d5194a5b%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636367751980975109&sdata=n%2FvCwoL350PLiMd0EjijuDJuOMXo2I2qKyGCq7Od6Cg%3D&reserved=0>

www.Can-Adapt.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.can-adapt.com%2F&data=02%7C01%7Cjjwhite%40ets.org%7C3ab2142f99ff4b2b471608d4d5194a5b%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636367751980975109&sdata=bY0Mkw6zBu%2Fmtm1h5kWx016R7qc%2FE59qIiZdifYxRWk%3D&reserved=0>



  Adapting the web to all users
            Including those with disabilities

If you are not the intended recipient, please review our privacy policy<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.davidmacd.com%2Fdisclaimer.html&data=02%7C01%7Cjjwhite%40ets.org%7C3ab2142f99ff4b2b471608d4d5194a5b%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636367751980975109&sdata=79xPcesxGTACDiIRHNo%2BOkknWr%2FkWXkHDzrb5nMwXb4%3D&reserved=0>

On Thu, Jul 27, 2017 at 1:09 PM, White, Jason J <jjwhite@ets.org<mailto:jjwhite@ets.org>> wrote:
I would include everything in the table from the HTML specification, then add further items to it. I would not omit anything which is in the HTML specification, as these items are all important (in various contexts) and we have tokens in HTML that can satisfy the programmatic determination requirement with respect to all of them.

I don’t expect to have significant time available to work on this for a while due to other pressing demands, but I’ll monitor how it develops.

Regards,

Jason.

From: lisa.seeman [mailto:lisa.seeman@zoho.com<mailto:lisa.seeman@zoho.com>]
Sent: Thursday, July 27, 2017 11:22 AM
To: W3c-Wai-Gl-Request@W3. Org <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Subject: working on the definitions for support personliazion

For the discussion on issue 6 -Taking to be compatible with auto complete - Here are some of the common form fields with deffintions


Are we happy with this brevity /  format?
Also I suggest we remove some of the (see my comments)


Token

Description

Lisa's comment

Names



name

full name



honorific-prefix

prefix or title (Mr., Mrs. Dr., etc.)



given-name

given or first name



additional-name

additional or middle name



additional-name-initial

additional or middle name initial

Suggest we omit

family-name

family name, surname, or last name



honorific-suffix

suffix (Jr., II, etc.)

Suggest we omit

nickname

nickname

Suggest we omit




Addresses



street-address

full street address condensed into one line



address-line1

first line of street address



address-line2

second line of street address



address-line3

third line of street address

Suggest we omit

locality

locality or city

Suggest we omit

city

same as locality

We can change to locality or city

administrative-area

administrative area, state, province, or region

Suggest we omit

state

same as administrative-area

Suggest we omit

province

same as administrative-area

Suggest we omit

region

same as administrative-area

Keep

postal-code

postal or ZIP code



country-name

country name






Contact Information



email

email address



tel

full phone number, including country code



tel-country-code

international country code



tel-national

national phone number: full number minus country code

Suggest we omit

tel-area-code

area code



tel-local

local phone number: full number minus country and area codes




tel-extension

phone extension number



fax

full fax number, including country code



fax-country-code

international country code

Suggest we omit

fax-national

national fax number: full number minus country code

Suggest we omit

fax-area-code

area code

Suggest we omit

fax-local

local fax number: full number minus country and area codes

Suggest we omit





fax-extension

fax extension number

Suggest we omit




Credit Cards



cc-name

full name, as it appears on credit card







cc-number

credit card number



cc-exp-month

month of expiration of credit card



cc-exp-year

year of expiration of credit card (see note 3 below about formatting)



cc-exp

date of expiration of credit card (see note 4 below about formatting)



cc-csc

credit card security code






Other



language

preferred language



bday

birthday (see note 4 below about formatting)



bday-year

year of birthday (see note 3 below about formatting)



bday-month

month of birthday



bday-day

day of birthday



org

company or organization



organization-title

user's position or title within company or organization



sex

sex or gender



gender-identity

gender identity

Suggest we omit

url

Website URL



photo

photo or avatar

Suggest we omit

section-*****

used to group forms together (see note 5 below)

Suggest we omit




All the best

Lisa Seeman

LinkedIn<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fil.linkedin.com%2Fin%2Flisaseeman%2F&data=02%7C01%7Cjjwhite%40ets.org%7C5c8f7489cbaa44435e1008d4d5035cfc%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636367657802652024&sdata=60k6RFjjH5IhMflEJtVMqEUsZC5vuCSupb14zElZI4w%3D&reserved=0>, Twitter<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2FSeemanLisa&data=02%7C01%7Cjjwhite%40ets.org%7C5c8f7489cbaa44435e1008d4d5035cfc%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636367657802662033&sdata=boLtCmS8uj0t4hqw2vw%2BJadPSnaN19VaX8R2vsDbY68%3D&reserved=0>

________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________


________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________