W3C | TAG | Previous: 14 June | Next: 21 June
Agenda of 28 June 2004 TAG teleconference
Nearby: Teleconference
details · issues
list (handling new
issues)· www-tag
archive
0. In Memoriam
Some tributes to Mario
available. Many thanks to Paul Cotton for organizing a floral tribute on
behalf of the TAG.
1. Administrative
- Roll call. Regrets: TBL
- Accept the minutes of the 14 June
teleconf?
- Accept this agenda?
- Next meeting: 12 July. Likely regrets: TBL. Possible regrets from
IJ.
- Action TBL 2004/05/12: Talk to TB and DO about editor role. (Proposal
from SW that this is done).
SW: Ack of continuing involvement/editing in some forum?
- IJ to be acting W3C Head of Communications 1 July. IJ expects to help
NW with editing, but otherwise setting low expectations for TAG
participation during the summer and early fall.
1.1 Meeting schedule
Action TAG 2004/06/07: Send summer regrets to TAG list.
- AC meeting rescheduled
for 2-3 December. Does this affect whether to hold TAG ftf meeting in
November?
- Ottawa meeting update?
- Action NW/PC 2004/06/14: Prepare ftf meeting agenda. See email
from Paul.
- Should we ask DO to attend the meeting if extensioning and
versioning is on the agenda?
1.3 TAG Charter
Action IJ 2004/06/07: Report back on next AB meeting to discuss TAG
charter and relation to patent policy. See AB
meeting summary, which essentially states that they think the policy
applies, but no consensus yet on how.
2. Technical
See also open
actions by owner and open
issues.
2.1 xml11Names-46
Was Norm
email forwarded to the XML CG?
2.2 httpRange-14 status
Action TBL/RF 2004/05/13: Write up a summary position to close
httpRange-14, text for document.
2.3 IRI draft status in IETF
Action CL 2004/06/14: Draft text basd on 14 June discussion and send to
TAG for review.
2.4 Web Architecture Document Last Call
2.4.1 Heartbeat Requirement
Should we request that 8 June draft be published on the TR page?
2.4.2 Reviews
See the 8 June
2004 Editor's Draft.
- Action NW 2004/05/14: Propose text on tradeoffs for section 4.2.2.
- Action CL 2004/05/14: Rewrite story at beginning of 3.3.1. Consider
deleting para that follows last sentence third para after story in 3.3.1.
"Note also that since dereferencing a URI (e.g., using HTTP) does not
involve sending a fragment identifier to a server or other agent, certain
access methods (e.g., HTTP PUT, POST, and DELETE) cannot be used to
interact with secondary resources."
- Action TBL 2004/06/08: For issue hawke7, ask Sandro for clarification
on whether second URI should have "#". Done: Sandro said that the hashes
were not the point, but that the point was that in the context of
dereferencing, it does matter which URI you use. Note:
IJ has removed the paragraph in the 8 June draft.
Actions from 2004/06/14:
- DC to review section 2 of 8 June draft.
- PC to review sections 1, 5, and 6 of 8 June draft.
- CL to review section 4 of 8 June draft.
- SW, NW to review entire 8 June draft.
Resources:
- Last Call
issues list (sorted by
section)
- Annotated
version of WebArch
- Archive of public-webarch-comments
- List of
actions by TAG participant
The TAG does not expect to discuss issues below this line.
3. Status report on these findings
See also TAG findings
4. Other action items
- Action DC 2003/11/15: Follow up on KeepPOSTRecords with Janet Daly on
how to raise awareness of this point (which is in CUAP).
- Action CL 2003/10/27: Draft XML mime type thingy with Murata-san
Ian Jacobs for Stuart Williams and TimBL
Last modified: $Date: 2004/06/28 15:21:58 $