W3C home > Mailing lists > Public > public-personalization-tf@w3.org > September 2018

Informal Call for Consensus on bringing in COGA's terms and definitions into our Module #2

From: Charles LaPierre <charlesl@benetech.org>
Date: Mon, 10 Sep 2018 19:04:34 +0000
To: "public-personalization-tf@w3.org" <public-personalization-tf@w3.org>
Message-ID: <B2B73F35-47FF-40CD-8D9C-BF1C4A96BA3A@benetech.org>
Hello everyone,

During our call this morning we discussed bringing the COGA’s Semantic terms into our Module #2, and it was suggested that we should bring it to a vote for this group to take the terms as defined and bring them into our Module #2 into sections 3.1.2 and a newly proposed 3.1.3 section.

I first would like to thank the COGA TF for all the work they have done with defining these terms, and Thaddeus has done a great job in cleaning up the COGA’s Google Doc<https://docs.google.com/document/d/1kW2druI59AOuLQKjWHwcfq9RaYwAA0V0mapPCfIiLD8/edit#heading=h.57r2hwyynj6m> which defines a number of terms with their definitions for "3.1.2 Values for alternative content and content accessibility support<https://w3c.github.io/personalization-semantics/help/index.html#values-for-alternative-content-and-content-accessibility-support>” and a new "3.1.3 Values for types of help" (we have yet to define in our module.

If no one disagrees with this, I would like to ask Roy to move this over from the Google Doc<https://docs.google.com/document/d/1kW2druI59AOuLQKjWHwcfq9RaYwAA0V0mapPCfIiLD8/edit#heading=h.57r2hwyynj6m> into our Specification<https://w3c.github.io/personalization-semantics/help/index.html#values-for-alternative-content-and-content-accessibility-support> so that it can be a normative reference.  Once we do this we would also put an IMPORTANT Note Callout at the top of the Google Doc stating that the APA’s Personalization TF has taken this over and that any further development of this should continue in our module “Personalization Help and Support 1.0” (With a link going to our specification) - This hopefully will prevent two separate documents in the future being worked on and getting out of sync.

Pease email any concerns or objections to this proposal by EOD Wednesday September 12th.

Lisa, you may want to fwd this email as a curtesy to the COGA TF that we will be taking this work over in order to bring this to a W3C normative recommendation.


Thanks
EOM

Charles LaPierre
Technical Lead, DIAGRAM and Born Accessible
Twitter: @CLaPierreA11Y
Skype: charles_lapierre
Phone: 650-600-3301



Received on Monday, 10 September 2018 19:04:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:56 UTC