W3C home > Mailing lists > Public > www-tag@w3.org > May 2003

[Agenda] 2 June extended TAG teleconf (Arch Doc, Findings, Issues)

From: Ian B. Jacobs <ij@w3.org>
Date: 29 May 2003 15:09:10 -0400
To: www-tag@w3.org
Message-Id: <1054138740.797.484.camel@seabright>

Hello,

The TAG will be holding a four-hour extended teleconference
on 2 June. The agenda is available as HTML [1] or as text
below. The agenda primarily involves:

 * A walk-through of the Arch Doc (led by Norm Walsh)
 * Next steps for three draft findings
 * A walk through of issues to identify those we might
   be able to close quickly, and those we would like
   to commit to closing before a last call of the
   Arch Doc.

Thank you,

 - Ian

[1] http://www.w3.org/2003/06/02-tag

==========================================================

                   Agenda for 2 June 2003 TAG teleconference

   Nearby: [4]Teleconference details  [5]issues list  [6]www-tag
   archive

      [4] http://www.w3.org/2001/tag/group/#remote
      [5] http://www.w3.org/2001/tag/ilist
      [6] http://lists.w3.org/Archives/Public/www-tag/

   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 (SW), Scribe (IJ, at least for some of the meeting).
       Regrets: PC. Possible regrets: DO
    2. Accept [7]27 May teleconference minutes?
    3. Accept this [8]agenda?
    4. Next meeting: 9 June? [No meeting 16 June since meeting 19 June]
    5. 19 June: Regrets DC and RF. Confirm or reschedule meeting
    6. Feedback from Budapest? In particular, AC responses to
       [9]questions from the TAG?

      [7] http://www.w3.org/2003/05/27-tag-summary.html
      [8] http://www.w3.org/2003/06/02-tag.html
      [9] http://www.w3.org/2003/Talks/AC-0520-TAG/12.svg

2. Technical (3.5 hours)

   We plan for breaks!

  2.1 Architecture document (1.5 hours)

   Norm Walsh will walk the TAG through the Arch Doc. Norm may send
   further detail about the structure of this session.

   See also: [10]findings.
    1. [11]26 Mar 2003 Working Draft of Arch Doc:
         1. Action DC 2003/01/27: write two pages on correct and
            incorrect application of REST to an actual web page design
         2. Action DO 2003/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.
         3. Action DC 2003/03/17: : Write some text for interactions
            chapter of arch doc related to [12]message passing, a dual of
            shared state.

     [10] http://www.w3.org/2001/tag/findings
     [11] http://www.w3.org/TR/2003/WD-webarch-20030326/
     [12] http://lists.w3.org/Archives/Public/www-tag/2003Mar/0018.html

  2.2 Findings status (30 mins)

   Next steps for draft findings:
     * [13]Client handling of MIME headers
     * [14]URIs, Addressability, and the use of HTTP GET and POST
     * [15]How should the problem of identifying ID semantics in XML
       languages be addressed in the absence of a DTD?

     [13] http://www.w3.org/2001/tag/doc/mime-respect.html
     [14] http://www.w3.org/2001/tag/doc/whenToUseGet-20030509.html
     [15] http://www.w3.org/2001/tag/doc/xmlIDSemantics-32.html

  2.3 Issues the TAG intends to discuss (1 hour)

   The TAG expects to do a walk-through of the open and pending
   [16]issues in order to determine:
     * Which ones we are near closing
     * Which ones we can commit to close w.r.t. last call of the arch doc

     [16] http://www.w3.org/2001/tag/open-summary.html

   Then, we expect to work on issues we think we are near closing.

  2.4 New issues?

  2.5 Issues that have associated action items

     * [17]contentTypeOverride-24
          + Next step on finding "[18]Client handling of MIME headers"
          + [19]Speech Recognition Grammar Specification Version 1.0,
            section [20]2.2.2 External Reference by URI
     * [21]whenToUseGet-7
          + Next step for [22]revised draft finding?
     * [23]metadataInURI-31
          + Action SW 2003/02/06: Draft finding for this one. See [24]SW
            proposal
          + See also [25]TB email on Apple Music Store and use of URI
            schemes instead of headers
     * [26]uriMediaType-9
          + IANA appears to have responded to the spirit of this draft
            (see [27]email from Chris Lilley).What's required to close
            this issue?
          + Action CL 2003/05/05: Propose CL's three changes to
            registration process to Ned Freed. [What forum?]
     * [28]abstractComponentRefs-37
          + See [29]issue description from David Orchard. Next steps?
     * [30]namespaceDocument-8
          + Action TB 2003/04/07: Prepare RDDL Note. Include in status
            section that there is TAG consensus that RDDL is a suitable
            format for representations of an XML namespace. Clean up
            messy section 4 of RDDL draft and investigate and publish a
            canonical mapping to RDF.
          + Action PC 2003/04/07: Prepare finding to answer this issue,
            pointing to the RDDL Note. See [31]comments from Paul
            regarding TB theses.
          + Action TB 2003/04/28: Draft a TAG opinion on the use of URNs
            for namespace names, for review by the TAG
               o RF: Folks assume that because the specs say so, URNs
                 will be persisitent. But persistence is a function of
                 institutional commitment and frequency of use.
     * [32]xlinkScope-23
          + Status report?
          + See [33]draft, and [34]SW message to CG chairs.
     * [35]IRIEverywhere-27
          + Action CL 2003/04/07: Revised position statement on use of
            IRIs. CL says to expect this by 21 April.
          + Action TBL 2003/04/28: Explain how existing specifications
            that handle IRIs are inconsistent. [36]TBL draft not yet
            available on www-tag.
          + See TB's[37]Proposed step forward on IRI 27.
     * [38]URIEquivalence-15
          + SW proposal: Track RFC2396bis where [39]Tim Bray text has
            been integrated. Comment within the IETF process. Move this
            issue to pending state.
     * [40]xmlIDSemantics-32
          + See [41]Chris Lilley draft finding.
            Action NW 2003/05/05: Point Core WG to CL finding once made
            public.
     * [42]siteData-36
          + Action TBL 2003/02/24 : Summarize siteData-36
     * [43]xmlFunctions-34
          + Action TBL 2003/02/06: State the issue with a reference to
            XML Core work. See [44]email from TimBL capturing some of the
            issues.
     * [45]binaryXML-30
          + Action TB 2003/02/17: Write to www-tag with his thoughts on
            adding to survey.
          + Next steps to finding? See [46]summary from Chris.
     * [47]contentPresentation-26
          + Action CL 2003/02/06: Create a draft finding in this space.
            Due 3 March.
     * [48]rdfmsQnameUriMapping-6
          + Action DC 2003/02/06: Propose TAG response to XML Schema
            desideratum ([49]RQ-23).
     * [50]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 [51]message from Larry Masinter w.r.t. Web services.
     * [52]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. Due first week of March.
     * [53]fragmentInXML-28 : Use of fragment identifiers in XML.
         1. Connection to content negotiation?
         2. Connection to opacity of URIs?
         3. No actions associated / no owner.

     [17] http://www.w3.org/2001/tag/open-summary.html#contentTypeOverride-24
     [18] http://www.w3.org/2001/tag/doc/mime-respect.html
     [19] http://www.w3.org/TR/speech-grammar/
     [20] http://www.w3.org/TR/speech-grammar/#S2.2.2
     [21] http://www.w3.org/2001/tag/ilist.html#whenToUseGet-7
     [22] http://www.w3.org/2001/tag/doc/get7-20020610.html
     [23] http://www.w3.org/2001/tag/open-summary.html#metadataInURI-31
     [24] http://lists.w3.org/Archives/Member/tag/2003May/0050.html
     [25] http://lists.w3.org/Archives/Public/www-tag/2003Apr/0151.html
     [26] http://www.w3.org/2001/tag/open-summary.html#uriMediaType-9
     [27] http://lists.w3.org/Archives/Public/www-tag/2003Feb/0302.html
     [28] http://www.w3.org/2003/06/24-tag-summary.html#abstractComponentRefs-37
     [29] http://lists.w3.org/Archives/Public/www-tag/2003Apr/0089.html
     [30] http://www.w3.org/2001/tag/open-summary.html#namespaceDocument-8
     [31] http://lists.w3.org/Archives/Member/tag/2003Apr/0046.html
     [32] http://www.w3.org/2001/tag/ilist.html#xlinkScope-23
     [33] http://lists.w3.org/Archives/Member/tag/2003Mar/0094.html
     [34] http://lists.w3.org/Archives/Member/tag/2003Mar/0104
     [35] http://www.w3.org/2001/tag/open-summary.html#IRIEverywhere-27
     [36] http://lists.w3.org/Archives/Member/tag/2003Apr/0074.html
     [37] http://lists.w3.org/Archives/Public/www-tag/2003Apr/0090.html
     [38] http://www.w3.org/2001/tag/open-summary.html#URIEquivalence-15
     [39] http://www.textuality.com/tag/uri-comp-4
     [40] http://www.w3.org/2001/tag/ilist#xmlIDSemantics-32
     [41] http://www.w3.org/2001/tag/doc/xmlIDSemantics-32.html
     [42] http://www.w3.org/2001/tag/ilist.html#siteData-36
     [43] http://www.w3.org/2001/tag/ilist#xmlFunctions-34
     [44] http://lists.w3.org/Archives/Public/www-tag/2003Feb/0309.html
     [45] http://www.w3.org/2001/tag/open-summary.html#binaryXML-30
     [46] http://lists.w3.org/Archives/Public/www-tag/2003Feb/0224.html
     [47] http://www.w3.org/2001/tag/open-summary.html#contentPresentation-26
     [48] http://www.w3.org/2001/tag/open-summary.html#rdfmsQnameUriMapping-6
     [49] http://www.w3.org/TR/2003/WD-xmlschema-11-req-20030121/#N400183
     [50] http://www.w3.org/2001/tag/open-summary.html#HTTPSubstrate-16
     [51] http://lists.w3.org/Archives/Public/www-tag/2003Feb/0208.html
     [52] http://www.w3.org/2001/tag/open-summary.html#errorHandling-20
     [53] http://www.w3.org/2001/tag/ilist#fragmentInXML-28

3. Other actions

     * Action IJ 2003/02/06: Modify issues list to show that
       actions/pending are orthogonal to decisions. IJ and PLH making
       substantial progress on this; hope to have something to show in
       May.

     _________________________________________________________________


    Ian Jacobs for Stuart Williams and TimBL
    Last modified: $Date: 2003/05/28 16:11:23 $


-- 
Ian Jacobs (ij@w3.org)   http://www.w3.org/People/Jacobs
Tel:                     +1 718 260-9447
Received on Thursday, 29 May 2003 15:09:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:17 GMT