RE: [Maturity] Referencing the Excel Spread Sheet

And of course this thought came in after I hit send: it might make sense to ask people to either flag in the spreadsheet their suggested changes, or submit a text summary of the suggested changes since change tracking in Excel is difficult at best.

Sheri

From: Sheri Byrne Haber <sbyrnehaber@vmware.com>
Sent: Wednesday, August 24, 2022 8:06 AM
To: Jeff Kline <jeffrey.l.kline@gmail.com>; Mary Jo Mueller <maryjom@us.ibm.com>
Cc: Janina Sajka <janina@rednote.net>; public-rqtf@w3.org; APA Chairs <group-apa-chairs@w3.org>
Subject: RE: [Maturity] Referencing the Excel Spread Sheet

I don’t think we want to lock it, we want people to fiddle with it to send comments back.  Any way that we can implement (because it’s Excel) to prevent people from changing it and then pretending it’s what came from W3C is a) fairly easily worked around through screen shots, and b) will discourage comments, which we don’t want.

Thanks,

Sheri

-----
Sheri Byrne-Haber (She/Her)
Senior Staff, Accessibility Architect
Mobile: 650 703 2376 (please text first if you have not called me before, otherwise it may go to VM)

Upcoming OOO
VMware Explore – August 29-Sept 1
PTO: Sept 5-9, Oct 3-5
Expect a delay in my replies

Phonetic pronunciation:   shei riə bUHRn heɪ buhr
Audio:   https://vimeo.com/665808784<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fvimeo.com%2F665808784&data=05%7C01%7Csbyrnehaber%40vmware.com%7C3611075082c040518ba108da85e24144%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637969504066371515%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=IS%2BZAGQcgQNGPkbSE1D%2B0p4vsw%2BMuISYrbxCuZZmEGU%3D&reserved=0>
ASL Name Sign:  https://vimeo.com/665809840<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fvimeo.com%2F665809840&data=05%7C01%7Csbyrnehaber%40vmware.com%7C3611075082c040518ba108da85e24144%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637969504066371515%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=LgE%2FPaGZ203AMX16etYMSjIyCie0V85mH6Ofpt%2BFee4%3D&reserved=0>

From: Jeff Kline <jeffrey.l.kline@gmail.com<mailto:jeffrey.l.kline@gmail.com>>
Sent: Wednesday, August 24, 2022 7:40 AM
To: Mary Jo Mueller <maryjom@us.ibm.com<mailto:maryjom@us.ibm.com>>
Cc: Janina Sajka <janina@rednote.net<mailto:janina@rednote.net>>; public-rqtf@w3.org<mailto:public-rqtf@w3.org>; APA Chairs <group-apa-chairs@w3.org<mailto:group-apa-chairs@w3.org>>
Subject: Re: [Maturity] Referencing the Excel Spread Sheet


⚠ External Email
I like this approach, but it could generate a lot of user edited copies being out there.

Wondering if we should:

1. Put a “W3C draft” or other watermark in the spreadsheet or

2. Lock the cells in the spreadsheet that are not designated for user input.

Thoughts?

Jeff



On Aug 24, 2022, at 8:41 AM, Mary Jo Mueller <maryjom@us.ibm.com<mailto:maryjom@us.ibm.com>> wrote:

I think it would be OK to put it in RQTF’s space. Any references to the spreadsheet and in the spreadsheet itself should have an editor’s explaining that it is experimental and subject to change until the final publication. We recommend that folks make a copy of it, so their version will continue to work. We can ask for feedback on the approach used in the spreadsheet if that is desired.

Best Regards,

Mary Jo
IBM Accessibility Standards Program Manager

From: Janina Sajka <janina@rednote.net<mailto:janina@rednote.net>>
Date: Tuesday, August 23, 2022 at 3:57 PM
To: public-rqtf@w3.org<mailto:public-rqtf@w3.org> <public-rqtf@w3.org<mailto:public-rqtf@w3.org>>
Cc: APA Chairs <group-apa-chairs@w3.org<mailto:group-apa-chairs@w3.org>>
Subject: [EXTERNAL] [Maturity] Referencing the Excel Spread Sheet
Dear All:

The current thinking is to place the .xlsx in RQTF's w3.org space and
reference the file from within our html document.

The advantage is that it will continue to point to the latest
spread sheet as we revise and update our document (and, of course, the
spread sheet itself).

But, is there a disadvantage? That someone might get broken data if we
upversion the spread sheet so that it no longer functions like the old
one? Should we be concerned over that?

Now's a good time to work out the approach we want to use upt to the
time we actually build a forms based interface.

Thoughts?

Best,

Janina


--

Janina Sajka (she/her/hers)
Accessibility Consultant https://linkedin.com/in/jsajka<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinkedin.com%2Fin%2Fjsajka&data=05%7C01%7Csbyrnehaber%40vmware.com%7C3611075082c040518ba108da85e24144%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637969504066371515%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9LI2yP5YWZvuuPQUvWNAzx%2F%2F9ogtRrwtXYzdapgr9fw%3D&reserved=0>

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures     http://www.w3.org/wai/apa<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2Fwai%2Fapa&data=05%7C01%7Csbyrnehaber%40vmware.com%7C3611075082c040518ba108da85e24144%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637969504066527760%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gMTpfpqHEbpRgjTKp3oPY5TqZbqg%2BhGfA%2BRa376ze7Y%3D&reserved=0>

Linux Foundation Fellow
https://www.linuxfoundation.org/board-of-directors-2/<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linuxfoundation.org%2Fboard-of-directors-2%2F&data=05%7C01%7Csbyrnehaber%40vmware.com%7C3611075082c040518ba108da85e24144%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637969504066527760%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bQJqp27tPIM17ee9He28NxXEFgRGuxhTckB1blbQZQk%3D&reserved=0>


________________________________

⚠ External Email: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender.

Received on Wednesday, 24 August 2022 15:08:29 UTC