BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20241002T122454Z
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-MICROSOFT-CDO-TZID:13
BEGIN:STANDARD
DTSTART:20231105T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:STANDARD
DTSTART:20241103T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20240310T100000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:17d0482c-06fa-4fab-8085-387a02dcce35
DTSTAMP:20241002T122454Z
SUMMARY:Simplifying the Updatable REC Process
DTSTART;TZID=America/Los_Angeles:20240925T111500
DTEND;TZID=America/Los_Angeles:20240925T121500
DESCRIPTION:https://www.w3.org/events/meetings/17d0482c-06fa-4fab-8085-387a
 02dcce35/\n\nJoin us at the W3C TPAC 2024 Tech Plenary to address the chal
 lenges and potential solutions for the updatable REC process. We'll focus 
 on the issues outlined in [issue #866](https://github.com/w3c/process/issu
 es/866) and collaborate on making the process more efficient.\n\n**Core Ch
 allenges:**\n1. **Complex Manual Markup:** The requirement for detailed ma
 nual markup (e.g.\, `<ins>`\, `<del>`\, specific classes) is time-consumin
 g and prone to errors\, frustrating many editors.\n2. **Detailed Change Tr
 acking:** Extensive documentation and linking for each change add unnecess
 ary overhead\, often leading to mistakes and confusion.\n3. **Inflexible C
 lass System:** The rigid classification system complicates the editing pro
 cess and increases the potential for errors.\n\n**Proposed Alternatives:**
 \n- **Enhanced Automated Tooling:** Develop tools that automatically gener
 ate the necessary markup from simpler inputs\, reducing the manual burden 
 on editors.\n- **Streamline the Existing Process:** Simplify the current m
 arkup requirements to lower the entry barrier and reduce the time spent on
  updates.\n- **Educational Support:** Increase training and support for ed
 itors to improve efficiency and understanding of the process.\n\n**Additio
 nal Strategic Alternatives:**\n- **Discontinue the Updatable REC Process:*
 * Consider phasing out the current process in favor of something that alig
 ns better with the working realities of editors while maintaining necessar
 y IPR protections.\n- **Discourage Use of the Current Process:** Officiall
 y recommend that the current updatable REC process be used only when absol
 utely necessary due to its complexity and high overhead.\n- **Introduce a 
 'Living Recommendation' Model:** Adopt a model similar to the WHATWG livin
 g standards\, allowing for continuous updates without detailed version tra
 cking and complex markup. But we do it in manner that meets W3C assurances
  and requirements.\n\nAgenda\n\n**Chairs:**\nMarcos Caceres\n\n**Descripti
 on:**\nJoin us at the W3C TPAC 2024 Tech Plenary to address the challenges
  and potential solutions for the updatable REC process. We'll focus on the
  issues outlined in [issue #866](https://github.com/w3c/process/issues/866
 ) and collaborate on making the process more efficient.\n\n**Core Challeng
 es:**\n1. **Complex Manual Markup:** The requirement for detailed manual m
 arkup (e.g.\, `<ins>`\, `<del>`\, specific classes) is time-consuming and 
 prone to errors\, frustrating many editors.\n2. **Detailed Change Tracking
 :** Extensive documentation and linking for each change add unnecessary ov
 erhead\, often leading to mistakes and confusion.\n3. **Inflexible Class S
 ystem:** The rigid classification system complicates the editing process a
 nd increases the potential for errors.\n\n**Proposed Alternatives:**\n- **
 Enhanced Automated Tooling:** Develop tools that automatically generate th
 e necessary markup from simpler inputs\, reducing the manual burden on edi
 tors.\n- **Streamline the Existing Process:** Simplify the current markup 
 requirements to lower the entry barrier and reduce the time spent on updat
 es.\n- **Educational Support:** Increase training and support for editors 
 to improve efficiency and understanding of the process.\n\n**Additional St
 rategic Alternatives:**\n- **Discontinue the Updatable REC Process:** Cons
 ider phasing out the current process in favor of something that aligns bet
 ter with the working realities of editors while maintaining necessary IPR 
 protections.\n- **Discourage Use of the Current Process:** Officially reco
 mmend that the current updatable REC process be used only when absolutely 
 necessary due to its complexity and high overhead.\n- **Introduce a 'Livin
 g Recommendation' Model:** Adopt a model similar to the WHATWG living stan
 dards\, allowing for continuous updates without detailed version tracking 
 and complex markup. But we do it in manner that meets W3C assurances and r
 equirements.\n\n**Goal(s):**\nImprove process and tooling\n\n\n\n**Materia
 ls:**\n- [minutes](https://www.w3.org/2024/09/25-updatable-rec-minutes.htm
 l)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2024-breakou
 ts/issues/11)\n\n**Track(s):**\n- Standards
STATUS:CONFIRMED
CREATED:20240916T214800Z
LAST-MODIFIED:20241002T122454Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:-1 Lower Level - Catalina 7
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
END:VCALENDAR