W3C home > Mailing lists > Public > public-apa-admin@w3.org > February 2022

RE: [EXTERNAL] Call for Consensus (CfC): Adopt Maturity Model Development

From: White, Jason J <jjwhite@ets.org>
Date: Mon, 28 Feb 2022 15:47:00 +0000
To: "Janina Sajka (janina@rednote.net)" <janina@rednote.net>, "public-apa-admin@w3.org" <public-apa-admin@w3.org>
Message-ID: <BL0PR07MB8019EF08CDFCE34165D49384AB019@BL0PR07MB8019.namprd07.prod.outlook.com>
I opened issues related to this document while it was under development by the Community Group:

I am concerned that some of the issues I created were closed without, in my view, satisfactorily addressing the substance of the matters raised, and without any dialogue with me as the issue submitter that could have clarified the perceived shortcomings in the document. While the technical merits of the issues are reasonably open to debate, I am here raising a process concern regarding the appropriate treatment of substantive issues and the need for a more rigorous approach to be adhered to in the event that this publication progresses further. It is my belief that the APA Working Group provides a suitable environment for maintaining a high-quality development process.
I am also concerned that there is considerable overlap between the scope of this work and the ISO/IEC 30071-1:2019 standard. A W3C Note in this area could create confusion as to the role and scope of the two respective publications, to the detriment of either.
I am comfortable with further progression of the Maturity Model within APA, under the condition that the APA Working Group Chairs take steps to address the aforementioned concerns. I do not object to the proposal stated in the CfC.

-----Original Message-----
From: Janina Sajka (janina@rednote.net) <janina@rednote.net>
Sent: Tuesday, 22 February 2022 15:34
To: public-apa-admin@w3.org
Subject: [EXTERNAL] Call for Consensus (CfC): Adopt Maturity Model Development


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.

Received on Monday, 28 February 2022 15:47:17 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:22:55 UTC