W3C | TAG

W3C TAG meeting 12-14 June 2012 in Cambridge, MA USA

Back: Jonathan Rees, Ashok Malhotra, Jeni Tennison, Henry Thompson
Front: Larry Masinter, Tim Berners-Lee, Noah Mendelsohn, Peter Linss

Agenda Summary

Logistics

Required Reading

• Best Practices for Fragment Identifiers and Media Type Definitions
• Product page: Fragment Identifiers and Mime Types (28 May 2012 version)
• New draft Patterns for Privacy by Design in Javascript APIs: W3C Draft TAG Finding 06 June 2012 (late addition)
• 2 April 2012 F2F discussion of Privacy by Design in APIs (since there's been little discussion since then, the chair wants to be sure TAG members are up on what was previously agreed)
• In preparation for discussion of TAG effectiveness:
  • Technical Architecture Group (TAG) Charter
  • TAG Status Report (December, 2011 - April, 2012)
  • TAG Status Report (May, 2011 - October, 2011)
  • TAG Status Report (January, 2011 - April, 2011)
  • Tim Bray's 2002 proposal that the TAG publish "Findings"
• HTML/XML Task Force Report (9 February 2012)
• Record of meeting with Norm Walsh on 5 January 2012 (HTML/XML Unification)
• Relating to storage and synchroniztion
  • E-mail Patterns and pitfalls in storage synchronisation from Robin Berjon (late addition)
  • E-mail on proposed TAG goals for work on Client-side storage from Robin Berjon (late addition)

Agenda Details

1. Convene, review agenda
   • Scribes: TAG members are encouraged to sign up for scribing by using CVS to edit scribing assignments table, or by emailing the chair
   • Roll call
     • Regrets: Robin Berjon, Yves Lafon, Larry Masinter (not attending on Thursday)
   • Approve minutes of teleconferences:
     • 24 May 2012
   • F2F Goals:
     • Main goals:
       1. Get more TAG members involved in preparing deliverables for coming 6 months
       2. Agree to publish a First Public Working Draft of a W3C TAG Recommendation on Best Practices for Fragment Identifiers and Meda Type Definitions
       3. Find an effective path forward on ISSUE-57 (HttpRedirections-57) including ISSUE-14 (HttpRange-14)
       4. Make bounded plan for getting to a finding on Privacy by Design in APIs for Web Applications
       5. Determine next steps on HTML/XML unification
       6. Decide whether there are changes to our direction or procedures that would improve the TAG's effectiveness
2. Review TAG Priorities for 2012
   • Goals:
     • Remind ourselves of priorities and commitments from TAG product pages
     • The Tuesday session is primarily a quick level-set at the start of the F2F — updates and debates about the priorities will happen as we go along and in a session on Thursday.
3. Administration:
   • Future TAG F2F meetings
     • 7-10 October 2012, UK (3 days to be selected)
     • Start thinking about location/dates for winter meeting
   • Group photo
4. ISSUE-66 (mimeAndWeb-66): Fragment Identifiers and Mime Types
   • Goal:
     • Review Best Practices for Fragment Identifiers and Media Type Definitions
     • Agree to publish a First Public Working Draft of a W3C TAG Recommendation on Best Practices for Fragment Identifiers and Meda Type Definitions (as promised in the product page for this activity)
     • Open new actions as needed to track activity in this area (right now, all actions are closed)
   • Background
     • New draft from Jeni Tennison: Best Practices for Fragment Identifiers and Media Type Definitions (required reading)
     • product page — 28 May 2012 version (required reading)
     • ACTION-690: on - Jeni Tennison - sort next steps on Fragment Identifiers and Mime Types - Due: 2012-05-05 - CLOSED
5. Web Applications: Privacy by Design in APIs for Web Applications
   • Goals:
     • Review new draft Patterns for Privacy by Design in Javascript APIs: W3C Draft TAG Finding 06 June 2012 (required reading)
     • Update Draft Product Page to reflect goals, deliverables, and schedules (note that those listed are all in the past)
     • Decide whether Privacy by Design in APIs should be moved up to a top priority TAG deliverable
   • Background:
     • ACTION-684: on - Robin Berjon - Update Privacy by Design in APIs - Due: 2012-05-08 - OPEN
     • Draft Product Page
     • Discussion on 2 April 2012 (F2F)
     • ACTION-650: on - Jonathan Rees - Review what provenance WG is doing with an eye to application to privacy issues - Due: 2012-08-01 - OPEN
     • Earlier background:
       • ACTION-514: on - Robin Berjon - Draft a finding on API minimization - Due: 2012-05-01 - CLOSED
       • Discussion on 2 February 2012
       • Earlier draft: Privacy by Design in APIs: Draft TAG Finding 27 March 2012
       • Proposal from Robin Berjon to expand the scope of beyond minimization to include other API issues relating to privacy, notably fingerprinting. Robin offers a proposed revised product page
       • Data Minimization in Web APIs: Draft TAG Finding 05 June 2011
       • Brief discussion on 12 May 2011
       • Discussion at Feb 2011 TAG F2F
       • From previous F2F: Dan Appelquist writeup on API Design - (announcement email)
       • ACTION-461: on - Daniel Appelquist - Draft "finding" on Web Apps API design - Due: 2010-12-31 - CLOSED
6. ISSUE-57 (HttpRedirections-57), ISSUE-63 (metadataArchitecture-63) and ISSUE-14 (HttpRange-14): httpRange-14 — URI Documentation Discovery
   • Goals:
     • Decide best course for moving forward on httpRange-14
   • Logistics:
     Sessions will be scheduled as follows:
     • Tuesday: a long lunch will be scheduled, during which Jonathan, Henry and Jeni will work on this as a breakout
     • Tenatively, group discussion will be on Thursday — if as a result of the Tuesday meetings it appears better to start earlier, then we will reschedule as appropriate.
   • Background:
     • Draft product page: URI Documentation Discovery (revised 6 June)
     • HTTP URI use case matrix
     • ACTION-704: on - Jonathan Rees - with help from Jeni and Henry to try to identify next steps for moving forward on httpRange-14 - Due: 2012-05-29 - OPEN
     • Telcon discussion on 3 May 2012
     • F2F discusion on 2 April 2012, 4 April 2012 and again later on 4 April 2012
     • Earlier background:
       • ACTION-691: on - Jonathan Rees - Prepare table as described in 2012-04-04 minutes, for TAG review - Due: 2012-04-24 - CLOSED
       • E-mail from Jonathan Rees with pointer to matrix summarizing state of play and asking for discussion
       • The TAG Member's Guide to ISSUE-57 Discussion JAR 2012-03-27
       • How to move ISSUE-57 off the TAG's plate - email from JAR 2012-03-25
       • either strengthen or retract httpRange-14(a) - email from JAR 2012-03-02
       • Responses to the call for change proposals to address ISSUE-57 (wiki page snapshot 30 March 2012)
       • Jonathan Rees announces a Call for proposals to amend the "httpRange-14 resolution"
       • Understanding URI Hosting Practice as Support for URI Documentation Discovery (baseline document for change proposals)
       • Product page: URI Documentation Discovery
       • Yet earlier background:
         • ACTION-673: on - Jonathan Rees - Prepare for F2F discussion of httpRange-14 change proposals Due 2012-03-13 - Due: 2012-03-20 - OPEN
         • Jonathan Rees's earlier announcement of a plan for re-resolving httpRange-14
         • ACTION-624: on - Jonathan Rees - Draft for TAG consideration a call for httpRange-14 change proposals - Due: 2011-12-31 - CLOSED
         • ACTION-625: on - Noah Mendelsohn - Schedule followup discussion of http://www.w3.org/wiki/HttpRange14Options (per agreement in Santa Clara) - Due: 2011-12-21 - CLOSED
         • ACTION-589: on - Noah Mendelsohn - Work with Jonathan to update URI definition discovery product page Due: 2011-08-18 - Due: 2011-12-23 - CLOSED
         • Interoperability of referential uses of hashless URIs by Jonathan Rees (announcement email)
         • Providing and discovering definitions of URIs: Editor's Draft 25 June 2011 by Jonathan Rees (announcement email) — required reading
         • Information Resources and Web Metadata: Editor's Draft 25 June 2011 by Jonathan Rees (announcement email) — required reading
         • Wiki page on httpRange-14 history
         • A diagram explaining "metadata", from Jonathan Rees
         • ACTION-201: on - Jonathan Rees - Report on status of AWWSW discussions - Due: 2012-05-15 - OPEN
         • ACTION-282: on - Jonathan Rees - Draft a finding on metadata architecture. - Due: 2013-04-01 - OPEN
         • ACTION-413: on - Dan Connolly - Suggest a path thru some logic terminology that might speed up httpSemantics discussions - Due: 2010-05-07 - CLOSED
         • ACTION-587: on - Jonathan Rees - Prepare issue-57 and issue-63 documents for TAG members to discuss at Sept F2F - Due: 2011-10-11 - CLOSED
7. Client-side storage including synchronization
   • Goals:
     • Establish goals for TAG work on client-side storage
     • Consider possible TAG effort on opportunities and pitfalls relating to synchronization
   • Background on Client-side storage:
     • ACTION-647: on - Robin Berjon - Draft product page on client-side storage focusing on specific goals and success criteria - Due: 2012-06-29 - OPEN
     • E-mail from Robin Berjon proposing Goals for possible TAG work on client-side storage (required reading — late addition)
   • Background on synchroniztion:
     • ACTION-693: on - Robin Berjon - Draft scope and goals for the Patterns/Pitfalls work in local/remote storage synch - Due: 2012-04-19 - PENDING REVIEW
     • E-mail from Robin Berjon proposing direction for TAG work on"Paterns and Pitfalls in storage synchronization". (required reading — late addition) Note that Robin recommends:
       • [The TAG SHOULD NOT] attempt to provide a solution for synchronisation problems. It is a complex research area, and if a standardised solution were to be established (which may not be necessary, and certainly not yet) it ought to be created by a dedicated working group with the requisite expertise.
       • there could be room for the TAG to release a short advisory note that would document 1) the known pitfalls in dealing with data synchronisation, 2) the primary patterns and solutions, and 3) an overview of the terms of the trade. The goal of such a document would be to ensure that someone who may be an adept Web application developer but has no knowledge of this specific problem space to save precious time by being bootstrapped with the basics one needs to start working on a solution (no matter how partial).
8. ACTION-563: Periodic TAG key issues reports to Jeff Jaffe
   • Goal:
     • Start collecting lists of issues to be reported to Jeff Jaffe in the fall
   • Background
     • ACTION-563: on - Noah Mendelsohn - Arrange for periodic TAG key issues reports to Jeff per June 2011 F2F - Due: 2012-09-25 - OPEN
     • Feb. 2012 report to Jeff Jaffe on Issues of Concern to the TAG; Jeff's response and followup discussion
9. ISSUE-67 (HTML-XML-Divergence-67): HTML / XML Unification
   • The chair is trying to arrange for Norm Walsh to join us by phone — Norm is also hoping to provide us with a brief summary of progress since our January 2012 meeting with him.
   • Goals:
     • Help Norm Walsh to decide next steps following publication of the HTML/XML Task Force Report
     • Review and update TAG product page HTML / XML Unification (26 December 2011 version)
   • Background:
     • Record of meeting with Norm Walsh on 5 January 2012:
       • At the start of the meeting Norm said: "My goal is to publish report, which the TAG needs to do so that we can get public review"
       • There was discussion of various proposed changes, e.g. to provide more references
       • At the end of the meeting, the TAG passed a formal RESOLUTION: The TAG thanks Norm Walsh and the task force, and expects that Norm will shortly provide the TAG for review a draft on XML/HTML Unification to be published as a W3C note for comunity review and comment. TAG chair will check with TAG before giving final clearance for publication.
     • The HTML/XML Task Force Report (required reading) was announced on 22 February 2012.
     • TAG product page HTML / XML Unification (22 December 2011 version)
     • ACTION-655: on - Noah Mendelsohn - Check Norm Walsh draft of W3C Note with the TAG, draft cover letter to include with Note, and review that with the TAG - Due: 2012-01-31 - CLOSED
     • ACTION-656: on - Noah Mendelsohn - Schedule discussion of possibly getting W3C to invest in technologies for liberal XML processing (e.g. XML5) - Due: 2012-04-24 - CLOSED
     • ACTION-657: on - Noah Mendelsohn - Schedule telcon discussion of possible XML/HTML Unification next steps - Due: 2012-04-10 - CLOSED
     • Earlier background:
       • Norm Walsh announces availability of a draft HTML/XML Task Force Report (22 December 2011 version) (required reading) for TAG review
       • ACTION-437: on - Tim Berners-Lee - Create a task force on XML / HTML convergence - Due: 2011-06-01 - CLOSED
       • ACTION-522: on - Noah Mendelsohn - Build Tracker product page for HTML/XML Unification - Due: 2011-05-17 - CLOSED
       • ACTION-578: on - Noah Mendelsohn - Make sure HTML/XML work gets TAG review when ready Due: 2011-08-01 - Due: 2011-12-27 - CLOSED
       • ACTION-591: on - Noah Mendelsohn - Ping Norm end of Sept. on revised HTML/XML report per discussion on 1 Sept 2011 - Due: 2011-12-27 - CLOSED
       • Norm Walsh is chairing a group under the TAG's auspices (mailing list)
       • Polyglot Markup: HTML-Compatible XHTML Documents (part of HTML5 Last Call)
       • Note from T.V. Raman (3 May 2010)
       • ACTION-433: on - Tim Berners-Lee - Help Tim get in touch with staff etc. re XML/HTML unification - Due: 2010-05-28 - CLOSED
       • ACTION-427: on - John Kemp - Read 4 distributed extensibility proposals and summarize them w.r.t. proposals TAG has discussed to date - Due: 2010-11-01 - CLOSED
       • Discussion on 7 June 2010 F2F: "TAG recommends the formation of a task force to drive the reunification of XML and HTML"
       • September/October 2010 HMTL WG poll on distributed extensibility
       • TAG endorses "like SVG" extension mechanism for HTML5
10. Improving the TAG's Effectiveness
    • Goal:
      • Consider whether the TAG should adopt changes that would increase our effectiveness in meeting the goals set forth in our charter
    • Background:
      • ACTION-709: on - Noah Mendelsohn - Talk to Jeff & W3M about TAG futures - Due: 2012-06-06 - PENDING REVIEW (NOTE: Jeff is not available this week
      • Reading: (all of the following are required preparation):
        • Technical Architecture Group (TAG) Charter
        • TAG Status Report (December, 2011 - April, 2012)
        • TAG Status Report (May, 2011 - October, 2011)
        • TAG Status Report (January, 2011 - April, 2011)
        • Tim Bray's 2002 proposal that the TAG publish "Findings"
11. Positioning of Web and Native applications
    • Goals:
      • Consider the likely effectiveness of Web applications in coexisting with or displacing native applications
      • Decide whether this is an area in which the TAG should be active (note that Hannes Tschofenig has indicated that the IETF IAB has some interest in the TAG's views on these questions)
    • Background:
      • E-mail from Larry Masinter: Question from IETF's Interenet Architecture Board (IAB) web apps, native apps, web-based apps
12. Action item review:
    • Pending review actions in Tracker
    • Overdue actions in Tracker
    • Open actions in Tracker
13. Open issue review:
    • This is an optional agenda item: we'll do it if there's time
    • Goal: review our list of open issues — look especially for issues that are open but dormant decide to assign resource/close/leave as background activity.