RE: [Agenda] 17 Mar 2003 TAG teleconf (mtg planning, next arch doc?, tech plenary feedback, issues...)

>* [31]rdfmsQnameUriMapping-6
>          + Action DC 2003/02/06: Propose TAG response to XML Schema
>            desideratum ([32]RQ-23). See input from Jonathan Marsh
>            ([33]forwarded by Paul Cotton).

I would actually prefer that [33] was dealt with separately since it is
effectively a separate request for input from the WS Description WG.  

To give it the visibility it disserves I think it should be discussed
under New Issues.

/paulc

Paul Cotton, Microsoft Canada 
17 Eleanor Drive, Nepean, Ontario K2E 6A3 
Tel: (613) 225-5445 Fax: (425) 936-7329 
mailto:pcotton@microsoft.com

  

> -----Original Message-----
> From: Ian B. Jacobs [mailto:ij@w3.org]
> Sent: March 13, 2003 11:44 AM
> To: www-tag@w3.org
> Subject: [Agenda] 17 Mar 2003 TAG teleconf (mtg planning, next arch
doc?,
> tech plenary feedback, issues...)
> 
> 
> Hello,
> 
> The agenda of the 17 Mar 2003 TAG teleconf is available
> as HTML [1] and as text below.
> 
>  - Ian
> 
> [1] http://www.w3.org/2003/03/17-tag
> 
> ========================================================
> 
>                    Agenda for 17 Mar 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, Scribe
>     2. Accept [7]24 Feb telecon minutes?
>     3. Accept this [8]agenda?
>     4. Next meeting: 24 March?
> 
>       [7] http://www.w3.org/2003/02/24-tag-summary.html
>       [8] http://www.w3.org/2003/03/10-tag.html
> 
>   1.1 Meeting planning
> 
>      * May schedule?
>           + FTF meeting? See [9]thread from SW. Or a two-day
distributed
>             meeting?
>           + Presentation at AC meeting?
>           + 21 May W3C Track session?
>      * Proposed 14-15 Nov Japan
>      * If confirmed, IJ to ask Member calendar to be updated.
> 
>       [9] http://lists.w3.org/Archives/Member/tag/2003Mar/0003.html
> 
>   1.2 Mailing list management
> 
>      * Completed action SW: Send draft mailing list policy to
tag@w3.org.
>        (See [10]preliminary announcement and [11]proposed text).
>      * [12]Proposal from Paul Cotton for announcement list.
> 
>      [10]
http://lists.w3.org/Archives/Public/www-tag/2003Feb/0196.html
>      [11] http://lists.w3.org/Archives/Member/tag/2003Mar/0053.html
>      [12] http://lists.w3.org/Archives/Member/tag/2003Mar/0038.html
> 
>   1.3 Review of input from technical plenary
> 
>      * Feedback about TAG process?
>      * Feedback on specific issues?
>           + xlinkScope-23 and summary of BOF from Tech Plenary; see
>             [13]BOF report from Henry Thompson
> 
>      [13] http://www.w3.org/XML/Group/2003/03/xlink_bof_report.html
> 
>   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: [14]findings.
>     1. [15]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". [16]Proposal from
TB
>             to withdraw the proposal.
>          7. See [17]PC's email on feedback from Tech Plenary
> 
>      [14] http://www.w3.org/2001/tag/findings
>      [15] http://www.w3.org/2001/tag/2002/webarch-20030221
>      [16] http://lists.w3.org/Archives/Public/www-tag/2003Feb/0005
>      [17] http://lists.w3.org/Archives/Member/tag/2003Mar/0050.html
> 
>   2.2 Issues
> 
>    Note: IETF meets this week; is there anything we would like
addressed
>    that could be addressed in that forum?
> 
>    Prioritization pass?
>      * [18]xlinkScope-23
>           + Status report?
>      * [19]siteData-36
>           + Completed action TB: Post a [20]strawman proposal for
>             siteData-36.
>           + Action TBL 2003/02/24 : Summarize siteData-36
>      * [21]namespaceDocument-8
>           + Next steps on [22]RDDL Proposal from Tim Bray/Paul Cotton
>      * [23]xmlFunctions-34
>           + Action TBL 2003/02/06: State the issue with a reference to
>             XML Core work. Deadline 17 Feb.
>      * [24]binaryXML-30
>           + Action TB 2003/02/17: Write to www-tag with his thoughts
on
>             adding to survey.
>           + Next steps to finding? See [25]summary from Chris.
>      * [26]contentPresentation-26
>           + Action CL 2003/02/06: Create a draft finding in this
space.
>             Deadline 3 March.
> 
>      [18] http://www.w3.org/2001/tag/ilist.html#xlinkScope-23
>      [19] http://www.w3.org/2001/tag/ilist.html#siteData-36
>      [20]
http://lists.w3.org/Archives/Public/www-tag/2003Feb/0297.html
>      [21]
http://www.w3.org/2001/tag/open-summary.html#namespaceDocument-8
>      [22] http://lists.w3.org/Archives/Public/www-tag/2003Feb/0213
>      [23] http://www.w3.org/2001/tag/ilist#xmlFunctions-34
>      [24] http://www.w3.org/2001/tag/open-summary.html#binaryXML-30
>      [25]
http://lists.w3.org/Archives/Public/www-tag/2003Feb/0224.html
>      [26] http://www.w3.org/2001/tag/open-
> summary.html#contentPresentation-26
> 
>      * [27]URIEquivalence-15
>           + See [28]draft 4. See also [29]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. ([30]Done))
>      * [31]rdfmsQnameUriMapping-6
>           + Action DC 2003/02/06: Propose TAG response to XML Schema
>             desideratum ([32]RQ-23). See input from Jonathan Marsh
>             ([33]forwarded by Paul Cotton).
>      * [34]uriMediaType-9
>           + Action DC 2003/02/06: Start discussion on
>             discuss@apps.ietf.org, but not urgent
>      * [35]RDFinXHTML-35
>           + Completed action DC 2003/02/06: Write up a crisp
articulation
>             of issue RDFINHTML-35. [36]Done
>      * [37]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 [38]message from Larry Masinter w.r.t. Web services.
>      * [39]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.
>      * [40]IRIEverywhere-27
>           + Action CL 2003/01/27: Send piece that CL/MD/IJ wrote to
>             www-tag.
>      * [41]metadataInURI-31
>           + Action SW 2003/02/06: Draft finding for this one.
>      * [42]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.
>      * [43]contentTypeOverride-24
>           + See [44]email from DC to Voice Browser WG. Does this
resolve
>             this issue?
> 
>      [27]
http://www.w3.org/2001/tag/open-summary.html#URIEquivalence-15
>      [28] http://www.textuality.com/tag/uri-comp-4.html
>      [29] http://lists.w3.org/Archives/Public/www-tag/2003Feb/0090.htm
>      [30] http://lists.w3.org/Archives/Public/uri/2003Mar/0014.html
>      [31] http://www.w3.org/2001/tag/open-
> summary.html#rdfmsQnameUriMapping-6
>      [32]
http://www.w3.org/TR/2003/WD-xmlschema-11-req-20030121/#N400183
>      [33]
http://lists.w3.org/Archives/Public/www-tag/2003Feb/0207.html
>      [34] http://www.w3.org/2001/tag/open-summary.html#uriMediaType-9
>      [35] http://www.w3.org/2001/tag/ilist#RDFinXHTML-35
>      [36]
http://lists.w3.org/Archives/Public/www-tag/2003Mar/0019.html
>      [37]
http://www.w3.org/2001/tag/open-summary.html#HTTPSubstrate-16
>      [38]
http://lists.w3.org/Archives/Public/www-tag/2003Feb/0208.html
>      [39]
http://www.w3.org/2001/tag/open-summary.html#errorHandling-20
>      [40]
http://www.w3.org/2001/tag/open-summary.html#IRIEverywhere-27
>      [41]
http://www.w3.org/2001/tag/open-summary.html#metadataInURI-31
>      [42] http://www.w3.org/2001/tag/ilist#fragmentInXML-28
>      [43] http://www.w3.org/2001/tag/open-
> summary.html#contentTypeOverride-24
>      [44]
http://lists.w3.org/Archives/Public/www-tag/2003Feb/0085.html
> 
>   2.3 New Issues?
> 
>      * [45]message passing, a dual of shared state from Dan Connolly
> 
>      [45]
http://lists.w3.org/Archives/Public/www-tag/2003Mar/0018.html
> 
>      _________________________________________________________________
> 
> 
>     Ian Jacobs for Stuart Williams and TimBL
>     Last modified: $Date: 2003/03/13 15:41:37 $
> 
> --
> Ian Jacobs (ij@w3.org)   http://www.w3.org/People/Jacobs
> Tel:                     +1 718 260-9447

Received on Thursday, 13 March 2003 14:13:30 UTC