W3C | TAG | Previous teleconference: 19 Feb 2009. | Next teleconference: 12th March 2009 (tentative).
Dave Orchard (outgoing TAG member), Noah Mendelsohn, Larry Masinter, John Kemp, T.V. Raman, Hubbell, Tim Berners-Lee, Henry Thompson, Jonathan Rees, Dan Connolly, Ashok Malhotra
Nearby: issues list - findings - www-tag archive - tag archive - Actions: (open, pending review)
Regrets: none (former TAG member David Orchard will join us Wed. evening and Thursday)
Tues 3rd March | ||
Agenda | Minutes | |
09:00-9:30 | Convene
Welcome new members Review: F2F Goals and Agenda |
|
9:30-10:30 | HTTP Content negotiation | |
10:30-10:45 | Break (15 mins) | |
10:45-12:00 | HTML and "Tag Soup" Integration |
|
12:00-13:15 | Lunch (75 mins) | |
13:15-14:00 | URNsAndRegistries-50: URIs, URNs, "location independent" naming systems and associated registries for naming on the Web (review - Henry) | |
14:00-15:00 | Review of ongoing TAG projects | |
15:00-15:30 | Break (30 mins) | |
15:30-16:00 | Issue Prioritization | |
16:00-16:30 | Administration:
|
|
16:30-17:00 | ...available... | |
Weds 4th March | ||
Agenda | Minutes | |
09:00-10:30 | TAG Priorities for Coming Year - initial discussion | |
10:30-11:00 | Break (30 mins) | |
11:00-12:00 | webApplicationState-60: Web Application State Management (Raman?) | |
12:00-13:15 | Lunch (75 mins) | |
13:15-14:45 | httpRedirections-57: Resource description discovery and access | |
14:45-15:15 | xmlFunctions-34: XML Transformation and composability (review - Henry) | |
15:15-15:45 | Break (30 mins) | |
15:45-17:00 | This was supposed to be errorHandling-20: Error handling, but we decided to use it for more of xmlFunctions-34. | |
Thurs 5th March | ||
Agenda | Minutes | |
09:00-10:30 | TAG Priorities for Coming Year - conclusion | |
10:30-11:00 | Break (30 mins) | |
11:00-12:00 | errorHandling-20: Error handling | |
12:00-13:15 | Lunch (75 mins) | |
13:15-15:00 | ...available... | |
15:00 | Meeting adjourns | |
15:00-17:00 | ...those who are not traveling until Friday may wish to stay for informal discussion... | |
Unscheduled topics
There are some other topics we may decide to discuss in the free time slots. Suggested discussion goals and preparation materials are available in the section linked below. |
||
Unscheduled topics |
Note that preparation is also encouraged for some items for which fixed time slots have not been allocated. We may or may not decide to discuss some or all of these, presumably in the sessions not yet scheduled.
(also separate Logistics page)
Several recent email threads have raised questions about the proper use of content negotiation on the Web. In particular, these questions have included:
The TAG goes into this meeting with 28 open issues. The overall goal of this session to identify a few key issues from our previous work that we will designate as possible major focus items for the coming year, to identify other issues that should remain active with lesser emphasis, and as appropriate to close (or open) others. In other F2F sessions, we will consider suggestions for new focus areas and priorities, so the final TAG agenda for the coming year will likely be a combination of ongoing work continued or refocused, along with new undertakings. This particular F2F session is aimed at ensuring that we understand and are properly tracking the status of work already underway. When we are done, the issues list should reflect in the description field the goals, deliverables, checkpoints, and success criteria for issues that remain active.
Specific goals for this F2F session are:
We will discuss this topic at least twice. The first session will focus on briefly reviewing proposals for new directions for TAG work, as well as proposals for which ongoing activites should be emphasized. We will also discuss which aspects of the TAG's work have been most effective, and which have not been effective. Note that we will in a separate session do a detailed review of all ongoing TAG activity (I.e. open issues), closing and reprioritizing as appropriate. The results of that analysis will be used as input to the second round discussion, which will attempt to set our overall priorities for the coming year.
No specific discussion time is allocated to the following, but we may choose to discuss these in some of the free time slots.
The following list was extracted from Tracker's list of open issues. The "F2F" column indicates issues that appear as explicit agenda items for this F2F. We will discuss the "Proposed Priority" column at the meeting.
ISSUE # | F2F | Old Issue Name | Proposed
Priority |
Description | Raised on |
Number of
Open Actions |
---|---|---|---|---|---|---|
7 | whenToUseGet-7 | Close | (1) GET should be encouraged, not deprecated, in XForms(2) How to handle safe queries | 23-Jan-02 | 0 | |
16 | HTTPSubstrate-16 | Close | Should HTTP be used as a substrate protocol? Does W3Cagree with RFC 3205? | 24-Mar-02 | 0 | |
20 | X | errorHandling-20 | High | What should specifications say about error handling? | 22-May-02 | 0 |
24 | contentTypeOverride-24 | Background | Can a specification include rules for overriding HTTPcontent type parameters? | 14-Jun-02 | 0 | |
27 | IRIEverywhere-27 | Background | Should W3C specifications start promoting IRIs? | 9-Oct-02 | 2 | |
28 | fragmentInXML-28 | Background | Use of fragment identifiers in XML | 31-Oct-02 | 0 | |
30 | binaryXML-30 | Background | Standardize a "binary XML" format? | 9-Oct-02 | 1 | |
33 | mixedUIXMLNamespace-33 | ?? | Composability for user interface-oriented XML namespaces | 6-Feb-03 | 0 | |
34 | X | xmlFunctions-34 | Medium | XML Transformation and composability (e.g., XSLT,XInclude, Encryption) | 6-Feb-03 | 1 |
36 | siteData-36 | Medium | Web site metadata improving on robots.txt, w3c/p3p and favicon etc. | 10-Feb-03 | 0 | |
37 | abstractComponentRefs-37 | ?? | Definition of abstract components with namespace names and frag ids | 3-Feb-03 | 0 | |
39 | rdfURIMeaning-39 | ?? | Meaning of URIs in RDF documents | 13-Jul-03 | 0 | |
40 | URIGoodPractice-40 | Background | What are good practices for URI construction? | 16-Oct-03 | 0 | |
41 | XMLVersioning-41 | Background | What are good practices for designing extensible XMLlanguages and for handling versioni | 27-Jun-03 | 3 | |
42 | ultimateQuestion-42 | What is the answer to life, the universe, and everything. | 15-Nov-03 | 3 | ||
43 | DerivedResources-43 | ?? | How are secondary resources derived? | 15-Nov-03 | 0 | |
45 | mediaTypeManagement-45 | Background | What is the appropriate level of granularity of the media type mechanism? | 14-May-04 | 0 | |
46 | xml11Names-46 | Close | Impact of changes to XML 1.1 on other XML Specifications | 19-May-04 | 0 | |
47 | endPointRefs-47 | Close | WS-Addressing SOAP binding & app protocols | 3-Jan-05 | 0 | |
49 | schemeProtocols-49 | Background | Relationship of URI schemes to protocols and operations | 7-Feb-05 | 0 | |
50 | X | URNsAndRegistries-50 | High | URIs, URNs, "location independent" naming systems and associated registries for namin | 15-Mar-05 | 2 |
54 | X | TagSoupIntegration-54 | High | Tag soup integration | 17-Oct-06 | 1 |
55 | utf7Encoding-55 | Background | Security issues with incorrect metadata | 14-Dec-06 | 0 | |
56 | abbreviatedURIs-56 | Background | Abbreviating URIs in Web Languages | 30-Mar-07 | 0 | |
57 | X | HttpRedirections-57 | High | The use of HTTP Redirection | 22-Aug-07 | 3 |
58 | scalabilityOfURIAccess-58 | ?? | Scalability of URI Access to Resources | 22-Aug-07 | 1 | |
60 | X | webApplicationState-60 | High | Web Application State Management | 14-Dec-07 | 3 |
61 | uriBasedPackageAccess-61 | High or Background? | URI Based Access to Packaged Items | 8-Jul-08 | 0 |