- From: Joshue O Connor <joconnor@w3.org>
- Date: Mon, 2 Mar 2020 19:17:48 +0000
- To: "White, Jason J" <jjwhite@ets.org>
- Cc: Janina Sajka <janina@rednote.net>, RQTF <public-rqtf@w3.org>
White, Jason J wrote on 02/03/2020 19:15: > It should also be noted that many of the issues which I raised with the draft remain open. This is as it should be, since we decided to postpone changes addressing the more substantive issues until the first public working draft was published. Thats also what I recall we agreed, thanks Jason. Josh > > -----Original Message----- > From: Joshue O Connor <joconnor@w3.org> > Sent: Monday, March 2, 2020 2:12 PM > To: Janina Sajka <janina@rednote.net> > Cc: White, Jason J <jjwhite@ets.org>; RQTF <public-rqtf@w3.org> > Subject: Re: Updated RTC Accessibility User Requirements doc ready > > Janina Sajka wrote on 02/03/2020 16:22: >> Just FYI that the links are coming through via the Outlook "safe links" >> proxy. >> >> For CfC we'll need the true time-stamped URI and the TR Editor's Draft >> URL, not the proxy. > Yup. At this stage I'm just sharing the latest changes for comments. > This will then be merged into master etc and we will mint our time stamped URI from there and update the editors draft. > > Thanks > > Josh >> Just noting. >> >> Janina >> >> White, Jason J writes: >>> Thank you, Josh. I have reviewed this branch, and it reads well. >>> >>> -----Original Message----- >>> From: Joshue O Connor <joconnor@w3.org> >>> Sent: Monday, March 2, 2020 9:38 AM >>> To: RQTF <public-rqtf@w3.org> >>> Subject: Updated RTC Accessibility User Requirements doc ready >>> >>> Hi all, >>> >>> I've spent today doing an editorial pass on the document. While doing so also I noticed the need to tighten the language and clarify some of our user needs and related requirements. So I did so. I don't feel these changes go beyond editorial work, as they certainly clarify the meaning and intent. In the previous version, there were qualifying clauses, at the end of sentences for example. Or there may have been an illustrative example in the middle of an important clause. >>> >>> You can see these changes in this branch: >>> >>> https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fraw. >>> githack.com%2Fw3c%2Fapa%2FAccessibleRTC%2Frtc%2Findex.html&data=0 >>> 2%7C01%7Cjjwhite%40ets.org%7C3dd1f1e9daa94d407c3308d7bedd9bdf%7C0ba6e >>> 9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637187731332557724&sdata=Sh >>> eveGZ%2B0x52MTvIdKwSf7GSN81FborC4IRKXQdVq8Y%3D&reserved=0 >>> >>> Please do review for any errors or omissions but I hope you will feel they improve readability and clarity of the document. >>> >>> Thanks >>> >>> Josh >>> >>> -- >>> Emerging Web Technology Specialist/Accessibility (WAI/W3C) >>> >>> >>> ________________________________ >>> >>> 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. >>> >>> ________________________________ > > -- > Emerging Web Technology Specialist/Accessibility (WAI/W3C) > > > ________________________________ > > 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. > > ________________________________ -- Emerging Web Technology Specialist/Accessibility (WAI/W3C)
Received on Monday, 2 March 2020 19:17:56 UTC