W3C | TAG | Previous: 24 Feb teleconference | Next: 17 Mar 2003 teleconf

Agenda for 10 Mar 2003 TAG teleconference

Note: This meeting was cancelled.

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 (30min)

1. Confirm Chair, Scribe
2. Accept 24 Feb telecon minutes?
3. Accept this agenda?
4. Next meeting: 17 March?

1.1 Meeting planning

• May schedule? See thread from SW.
  
• Proposed 14-15 Nov Japan
  
• If confirmed, IJ to ask Member calendar to be updated.

1.2 Mailing list management

• Action SW: Send draft mailing list policy to tag@w3.org. (See preliminary announcement)

1.3 Review of input from technical plenary

• Feedback about TAG process?
• Feedback on specific issues?

1.4 Other stuff

• Action IJ 2003/02/06: Modify issues list to show that actions/pending are orthogonal to decisions. IJ is working with PLH on this.

2. Technical (60min)

2.1 Architecture document

See also: findings.

1. 21 Feb 2003 Editor's Draft of Arch Doc:
   1. Resolve to request publication of this draft (with modifications?) on TR page?
   2. Action DC 2003/02/06: Attempt a redrafting of 1st para under 2.2.4
   3. Action DC 2003/01/27: write two pages on correct and incorrect application of REST to an actual web page design
   4. Action DO2003/01/27: Please send writings regarding Web services to tag@w3.org. DO grants DC license to cut and paste and put into DC writing.
   5. Action CL 2003/0127: Draft language for arch doc that takes language from internet media type registration, propose for arch doc, include sentiment of TB's second sentence from CP10.
   6. Action TB 2003/01/27: Develop CP11 more: Avoid designing new protocols if you can accomplish what you want with HTTP. DC suggested describing GET/PUT/POST in a para each, then say "if your app looks like that, use HTTP". Proposal from TB to withdraw the proposal.

2.2 Issues

Prioritization pass?

• siteData-36
  • Completed action TB: Post a strawman proposal for siteData-36.
  • Action TBL 2003/02/24 : Summarize siteData-36
• namespaceDocument-8
  • Next steps on RDDL Proposal from Tim Bray/Paul Cotton
• xmlFunctions-34
  • Action TBL 2003/02/06: State the issue with a reference to XML Core work. Deadline 17 Feb.
• binaryXML-30
  • Action TB 2003/02/17: Write to www-tag with his thoughts on adding to survey.
  • Next steps to finding? See summary from Chris.
• contentPresentation-26
  • Action CL 2003/02/06: Create a draft finding in this space. Deadline 3 March.

• URIEquivalence-15
  • See draft 4. See also email from Larry Masinter on xml namespaces.
  • TBL 2003/01/20: Send email to uri@w3.org requesting terminology change (regarding definition of "URI").
  • Completed Action TB 2003/02/06: Send URI equiv draft finding to uri@w3.org. Done (URI?)
• rdfmsQnameUriMapping-6
  • Action DC 2003/02/06: Propose TAG response to XML Schema desideratum (RQ-23). See input from Jonathan Marsh (forwarded by Paul Cotton).
• uriMediaType-9
  • Action DC 2003/02/06: Start discussion on discuss@apps.ietf.org, but not urgent
• RDFinXHTML-35
  • Action DC 2003/02/06: Write up a crisp articulation of issue RDFINHTML-35. [DC says - don't expect results before May 2003 meeting]
• HTTPSubstrate-16
  • Action RF 2003/02/06: Write a response to IESG asking whether the Web services example in the SOAP 1.2 primer is intended to be excluded from RFC 3205
  • See message from Larry Masinter w.r.t. Web services.
• errorHandling-20
  • Action CL 2003/02/06: Write a draft finding on the topic of (1) early/late detection of errors (2) late/early binding (3) robustness (4) definition of errors (5) recovery once error has been signaled. Deadline first week of March.
• IRIEverywhere-27
  • Action CL 2003/01/27: Send piece that CL/MD/IJ wrote to www-tag.
• metadataInURI-31
  • Action SW 2003/02/06: Draft finding for this one.
• fragmentInXML-28 : Use of fragment identifiers in XML.
  1. Connection to content negotiation?
  2. Connection to opacity of URIs?
  3. No actions associated.
• contentTypeOverride-24
  • See email from DC to Voice Browser WG. Does this resolve this issue?