W3C | TAG | Previous: 8 Jul | Next: 22 July

Agenda for 15 July 2002 TAG teleconference

Nearby: Teleconference details issues list www-tag archive

Note: The Chair does not expect the agenda to change after close of business (Boston time) Thursday of this week.

1. Administrative (15min)

  1. Confirm scribe
  2. Roll call. Regrets: CL
  3. Accept this agenda
  4. Next meeting? Proposed 22 July.
  5. Accept 8 July minutes
  6. Confirm status of completed actions
  7. Confirm status of withdrawn actions [None]

1.2 Completed actions?

  1. IJ: Find out whether the W3C Comm Team expects to have a publishing moratorium in August. (Awaiting reply).

2. Technical (75min)

2.1 Findings in progress, architecture document (45min)

See also: findings.

  1. Architecture document
    1. ACTION TBL 2002/05/05: Negotiate more of IJ time for arch doc
    2. ACTION RF 2002/06/24: Write a paragraph on technical and political aspects of URIs and URI References.
    3. Action TB, DC 2002/07/08: Propose text for section 1.1 (URI Schemes)
    4. Action CL 2002/07/08: Propose text for section 2 (Formats). Deadline 30 July.
    5. Action DC 2002/07/08: Ask Michael Mealing when IETF decided not to use HTTP URis to name protocols.
    6. Action IJ 2002/07/08: Produce WD of Arch Doc. Deadline 30 August.
  2. Internet Media Type registration, consistency of use.
  3. Qnames as identifiers
    1. Action NW 2002/06/24: Follow up on Rick Jelliffe comments/proposal.
  4. Consistency of Formatting Property Names, Values, and Semantics

2.2 Priority issues (30min)

  1. httpRange-14: Need to make progress here to advance in Arch Document.
  2. uriMediaType-9: Status of negotiation with IETF? See message from DanC.
  3. RFC3023Charset-21:
  4. Status of URIEquivalence-15. Relation to Character Model of the Web (chapter 4)? See text from TimBL on URI canonicalization and email from Martin in particular.
  5. Status of discussions with WSA WG about SOAP/WSDL/GET/Query strings?
  6. RFC3023Charset-21
  7. augmentedInfoset-22:

2.3 New issues?

  1. Bad practice: Overriding HTTP content-type with a URI reference.See email from TBL.
  2. "Deep linking illegal" bad practice? See email from Tim Bray.

Ian Jacobs, for TimBL
Last modified: $Date: 2002/07/15 19:06:36 $