W3C | TAG | Previous: 17 Feb teleconference | Next: 10 Mar 2003
teleconf
Agenda for 24 Feb 2003 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 (20min)
- Confirm Chair (NW) and Scribe ??. Regrets: IJ
- Accept 17 Feb telecon minutes?
- Accept this agenda?
- Next meeting: 10 Feb. 3 Feb cancelled at 17 Feb teleconf.
1.1 Meeting planning
- Proposed 22, 23, 24 May (2003/02/17)
Completed action IJ: Start email thread to TAG to suggest alternate May
dates of 22 (All day), 23 (Morning), 24 (Morning). DO, TB, PC, NW, IJ can
meet those days. CL not sure yet.
- Proposed 14-15 Nov Japan
Completed Action IJ: Start separate thread on tag to try to get confirmation of
14-15 November in Japan. TB, PC, DO, NW, IJ, CL can meet those
days.
- If confirmed, IJ to ask Member calendar to be updated.
1.2 Technical Plenary presentations
- SW: TAG overview
- DC: Arch Doc overview
- CL: xmlIDSemantics-32
- NW: xmlProfiles-29
- PC: namespaceDocument-8
1.3 Mailing list management
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 (70min)
2.1 New issues?
2.2 Issues
- deepLinking-25
- Action TB 2003/02/06: Send URI equiv draft finding to
uri@w3.org.
- Completed action IJ: Announce to www-tag with updated status section to
highlight that this does not represent a W3C position. Ask for
comments within seven days. (Done)
- namespaceDocument-8
- 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.
2.3 Other issues
The TAG is likely to review action items associated with these issues.
- URIEquivalence-15
- Completed action TB: Revise draft finding on
URI equivalence bearing in mind DC presentation (slides) at ftf
meeting. Deadline: 1 March. Done, 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").
- rdfmsQnameUriMapping-6
- 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.
- Connection to content negotiation?
- Connection to opacity of URIs?
- No actions associated.
- contentTypeOverride-24
2.4 Architecture document
See also: findings.
- 21 Feb 2003 Editor's Draft of
Arch Doc:
- Resolve to request publication of this draft (with modifications?)
on TR page?
- Action DC 2003/02/06: Attempt a redrafting of 1st para under
2.2.4
- Action DC 2003/01/27: write two pages on correct and incorrect
application of REST to an actual web page design
- 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.
- 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.
- 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.
Ian Jacobs for Norm Walsh and TimBL
Last modified: $Date: 2003/02/22 00:27:46 $