Re: 48-Hour Call for Consensus (CfC): Personalization TF Publication Requests

Janina wrote:

1.)     For permission to publish updated working drafts of the
[Personalization
draft documents]


+1 to this.


2.)     For standing permission to publish future working draft updates.


+1 again, with a request that in the future we split this type of CfC, as
the way it is currently worded, there are two requests, but seemingly only
one "response" possibility to the CfC.

JF

On Thu, Jun 27, 2019 at 12:12 PM Janina Sajka <janina@rednote.net> wrote:

> Colleagues:
>
> This is a Call for Consensus (CfC) to the Accessible Platform
> Architectures (APA) Working Group seeking consensus on two related
> requests from our Personalization Task Force:
>
> 1.)     For permission to publish updated working drafts of the
> following 4 documents:
>
> Personalization Semantics Explainer 1.0<
> https://w3c.github.io/personalization-semantics/>
>
> Adaptable Content<
> https://w3c.github.io/personalization-semantics/content/index.html>
>
> Adaptable Help and Support<
> https://w3c.github.io/personalization-semantics/help/index.html>
>
> Adaptable Tools<
> https://w3c.github.io/personalization-semantics/tools/index.html>
>
> 2.)     For standing permission to publish future working draft updates.
>
> ***Background Info***
>
> The head of thread for this request in the Personalization TF with
> additional details concerning these publications can be found here:
>
>
> https://lists.w3.org/Archives/Public/public-personalization-tf/2019Jun/0022.html
>
> Please also note the TF Facilitator's decision message which appears below.
>
> ***ACTION TO TAKE***
>
> This CfC is now open for objection, comment, as well as statements of
> support via email. Silence will be interpreted as support, though
> messages of support are certainly welcome.
>
> If you object to either of these two proposed actions, or have comments
> concerning this proposal, please respond by replying on list to this
> message no later than 23:59 (Midnight) Boston Time, Wednesday 3 July.
>
> NOTE: This Call for Consensus is being conducted in accordance with the
> APA Decision Policy published at:
>
> http://www.w3.org/WAI/APA/decision-policy
>
> Janina
>
> Charles LaPierre writes:
> > Hello everyone,
> >
> > We did not receive any objections to publish our next public working
> drafts with the main update of using data- as well as harmonizing with the
> autocomplete values within HTML and using hyphens instead of camelCase for
> our values.  Next step is to ask the APA for their approval and also ask
> the APA if we can publish future drafts without having the APA WG go
> through a CFC period.
> >
> > Janina, I am not sure how to formally ask the APA for our Task Force to
> publish our explainer and 3 modules as our next public working drafts and
> also at the same time ask for the option to publish future drafts without
> having to ask the APA each time.
> >
> > Can this email to our Personalization TF be our request?
> > Remember I am officially on holidays now until July 10th, I hope this
> can be published before I return.
> > Take care all as see you in a few weeks.
> >
> > Thanks
> > EOM
> > Charles LaPierre
> > Technical Lead, DIAGRAM and Born Accessible
> > Twitter: @CLaPierreA11Y
> > Skype: charles_lapierre
> >
> >
> > Begin forwarded message:
> > Charles LaPierre writes:
> > Colleagues:
> >
> > The previous CFC which was to be completed by midnight tonight is being
> replaced with this CFC which will be due by midnight Friday, due to the
> fact that their 3 modules did not have the updated table values with the
> addition of all the auto-complete values and change from camelCase to
> hyphens between long value names, those changes were in a separate branch,
> this has been merged now into the master branch (Thanks Roy)
> >
> > This is a Call for Consensus (CfC) to the Personalization Task Force
> which is under the Accessible Platform
> > Architectures (APA) Working Group seeking consensus on
> >
> > Publishing updated Public Working Drafts for the following Documents:
> >
> > Personalization Semantics Explainer 1.0<
> https://w3c.github.io/personalization-semantics/>
> >
> > Adaptable Content<
> https://w3c.github.io/personalization-semantics/content/index.html>
> >
> > Adaptable Help and Support<
> https://w3c.github.io/personalization-semantics/help/index.html>
> >
> > Adaptable Tools<
> https://w3c.github.io/personalization-semantics/tools/index.html>
> >
> > This was discussed in the minutes at
> >
> > https://www.w3.org/2019/06/17-personalization-minutes.html
> > Huge thanks to both Michael and Roy for getting these documents ready
> for our next publication.
> >
> > *       ACTION TO TAKE
> >
> > This CfC is now open for objection, comment, as well as statements of
> > support via email. Silence will be interpreted as support, though
> > messages of support are certainly welcome.
> >
> > If you object to this proposed action, or have comments concerning this
> > proposal, please respond by replying on list to this message no later
> > then 23:59 (Midnight) Boston Time, Friday June 21, 2019.
> >
> > NOTE: This Call for Consensus is being conducted in accordance with the
> > APA Decision Policy published at:
> >
> > http://www.w3.org/WAI/APA/decision-policy
> >
> > Thank you
> > Charles LaPierre
> > Lisa Seeman
> >
>
> --
>
> Janina Sajka
>
> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup:       http://a11y.org
>
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair, Accessible Platform Architectures        http://www.w3.org/wai/apa
>
>
>

-- 
*​John Foliot* | Principal Accessibility Strategist | W3C AC Representative
Deque Systems - Accessibility for Good
deque.com