RE: Call For Consensus

Hi Jason


Note that  the cfc seas changes may happen that affect implementation if a strong need is identified. (Such as from implementation feedback)
I think that addresses your concern


We discussed this on the last call. We did the same thing with ARIA to get firefox to be an early adopter.
Getting adoption of these three values are important because we need it to become a standard, and for WCAG to require it. If we do not meet the needs of implementations we can not become a standard .


All the best

Lisa Seeman

LinkedIn, Twitter





---- On Wed, 03 Jan 2018 18:25:53 +0200  White<jjwhite@ets.org> wrote ---- 

    -1
 A decision to preclude changes affecting implementations would prevent this Task Force from properly considering and responding to comments received on working drafts of the specification. The only point in the process at which it is appropriate to signal that backward-incompatible changes are not expected is the transition to Candidate Recommendation. The experience gained from early implementations is no doubt valuable in guiding further development, but this experience may well lead to decisions that substantively change the formal vocabulary defined in the specification. The text of the CfC raises the bar too high for making changes.
  
 This CfC seeks improperly to restrain the Task Force from further developing the specification in response to comments received from participants, from external parties and from prospective implementers.
  
 I would support a CfC that simply sought agreement to publish a working draft or to include items that have been discussed at meetings in the next draft.
  
    From: Charles LaPierre [mailto:charlesl@benetech.org] 
 Sent: Wednesday, January 3, 2018 10:32 AM
 To: public-personalization-tf@w3.org
 Subject: Call For Consensus
 
 
  
   Hello Personalization TF members and Happy New Year!
   
 
  We have a Call For Consensus which ends Monday Jan 8th at 11 am Boston time. 
 
   
 
   This task force does not intend to make changes to the the action field and destination vocabularies in https://w3c.github.io/personalization-semantics/ that may affect implementation. Editorial changes may still occur. 
 
  Note that 
   Changes may happen that affect implementation if a strong need is identified. (Such as from implementation feedback)
 We may also add advanced terms at some stage and a mechanism for adding options. Terms that may need options have been identified in the specification. 
   
 
  The changes from the previous draft  are: adding ccType , transactionCurrency, transactionAmount and checkout
 
  The term organizationTitle has also been changed to position. 
  If you have concerns about this proposed consensus position that have not been discussed already and feel that those concerns result in you “not being able to live with” this decision, please let the group know before the CfC deadline. note we do have time to make a few changes and redo the CFC.
 
   You may vote by replying to this message with a +1 or if you have any concerns a -1 and what your concerns are.
 
  
  All the best
 Lisa and Charles
 
   
 
        Thanks
 
  EOM
 
 Charles LaPierre
 Technical Lead, DIAGRAM and Born Accessible
 E-mail: charlesl@benetech.org
 Twitter: @CLaPierreA11Y
 Skype: charles_lapierre
 Phone: 650-600-3301
 
   
 
 
 
 
 
 
 
  
 
 
  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.