- From: Ian B. Jacobs <ij@w3.org>
- Date: 12 Feb 2003 13:44:41 -0500
- To: www-tag@w3.org
Hello,
The agenda for the 17 Feb 2003 TAG teleconf is
available as HTML [1] and as text below.
- Ian
[1] http://www.w3.org/2003/02/17-tag.html
=================================================================
Agenda for 17 Feb 2003 TAG teleconference
Nearby: [4]Teleconference details · [5]issues list · [6]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)
1. Confirm Chair (NW) and Scribe (IJ).
2. Accept [7]6-7 Feb face-to-face minutes?
3. Accept this [8]agenda?
4. Approve [9]revised Deep Linking finding? (TAG-only)
5. Next meeting: 24 Feb?
1.1 Meeting planning
* Action PC 2003/02/06: Talk to meeting planners about May 2003 TAG
schedule (noting that it overlaps with W3C track so there may be
absences).
* Completed Action IJ 2003/02/06: Talk to Nov AC meeting planners to
see if 14-15 ok for TAG meeting. We can meet any time according to
the Keio Team, and stay at the guest house.
* Completed Action PC 2003/02/06: Report TAG's tech plenary plan to
tech plenary planning committee ([10]Done).
1.2 Mailing list management
* Action SW: Send draft mailing list policy to tag@w3.org.
1.3 Other stuff
* Action IJ 2003/02/06: Fix issues list to show that actions/pending
are orthogonal to decisions.
* Action IJ 2003/02/06: Explain how TAG participants can edit the
source of the arch document.
2. Technical (70min)
2.1 New issues?
* Site metadata hook? See [11]email from TBL
2.2 Issues
* [12]deepLinking-25
+ Action TB 2003/02/06: Send URI equiv draft finding to
uri@w3.org.
+ Completd Action IJ 2003/02/06: Publish Deep Linking finding
as accepted finding. See [13]revised Deep Linking finding.
Approve this draft?
* [14]namespaceDocument-8
+ PC, TB 2003/01/13: Write up a Working Draft that recommends a
data format for namespace docs (not compulsory) and that such
a document should follow the Rec track process. The initial
content of the document should be taken from the RDDL
challenge proposals; they are isomorphic in technical
content. Please include drawbacks in the draft. See [15]NW
summary
* [16]xmlFunctions-34
+ Action DC 2003/02/06: State the issue with a reference to XML
Core work. Deadline 17 Feb.
* [17]mixedNamespaceMeaning-13
+ Action SW 2003/02/6: Report to www-tag on disposition of this
issue. Deadline 13 Feb.
2.3 Other issues
The TAG is likely to review action items associated with these issues.
* [18]uriMediaType-9
+ Action DC 2003/02/06: Start discussion on
discuss@apps.ietf.org, but not urgent
* [19]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]Proposed: Replace mixedNamespaceMeaning-13,
explaining that we identified three subissues (may be others)
and that initial issue was deemed to large.
* [20]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
* [21]errorHandling-20
+ Action CL 2003/02/06: Write a draft finding (deadline 1
month) 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.
* [22]contentTypeOverride-24
+ Action DC 2003/02/06: Send an email to the Voice WG that
third para of 2.2.2 CR of Speech Recognition Grammar Spec is
wrong regarding override of media type.
* [23]contentPresentation-26
+ Action CL 2003/02/06: Create a draft finding in this space.
Deadline 3 March.
* [24]IRIEverywhere-27
+ Action CL 2003/01/27: Send piece that CL/MD/IJ wrote to
www-tag.
* [25]binaryXML-30
+ Action CL 2003/01/27: Send [26]piece on binary XML to
www-tag.
* [27]metadataInURI-31
+ Action SW 2003/02/06: Draft finding for this one.
* [28]URIEquivalence-15
+ Completed Action DC 2003/02/06: Publish slides on URI
Equivalence. ([29]Done)
+ Action TBL 2003/02/06: Write up a proposal for a new issue
regarding generic metadata hooks (related to robots.txt).
* [30]fragmentInXML-28 : Use of fragment identifiers in XML.
1. Connection to content negotiation?
2. Connection to opacity of URIs?
2.4 Findings in progress, architecture document
See also: [31]findings.
1. [32]6 Dec 2002 Editor's Draft of Arch Doc:
1. Next TR page draft? IJ proposes after ftf meeting.
2. Action CL 2002/09/25: Redraft section 3 based on resolutions
of [33]18 Nov 2002 ftf meeting.
3. Action DC 2003/02/06: Attempt a redrafting of 1st para under
2.2.4
_________________________________________________________________
Ian Jacobs for Norm Walsh and TimBL
Last modified: $Date: 2003/02/12 18:43:42 $
--
Ian Jacobs (ij@w3.org) http://www.w3.org/People/Jacobs
Tel: +1 718 260-9447
Received on Wednesday, 12 February 2003 13:44:43 UTC