W3C home > Mailing lists > Public > www-tag@w3.org > June 2002

[Minutes] 3 June TAG teleconference (errorHandling-20, w3cMediaType-1, RFC3023-charset-21, charmodReview-17, whenToUseGet-7)

From: Dan Connolly <connolly@w3.org>
Date: 03 Jun 2002 16:08:02 -0500
To: www-tag@w3.org
Message-Id: <1023138483.25653.450.camel@dirk>

On Thu, 2002-05-30 at 12:52, Ian B. Jacobs wrote:
>                     Agenda for 3 June 2002 TAG teleconference

see also: IRC log
  http://www.w3.org/2002/06/03-tagmem-irc
  http://www.w3.org/2002/06/03-tagmem-irc.html
  http://www.w3.org/2002/06/03-tagmem-irc.txt
  http://www.w3.org/2002/06/03-tagmem-irc.rdf

> 1. Administrative (15min)
http://www.w3.org/2002/06/03-tagmem-irc#T19-05-55

Attendance: present: TimBL (chair for part), Norm (chair for the rest),
  Roy, Tim.Bray, DanC (scribe), DOrchard, Chris
regrets: Ian, PaulC, Stuart

>      1. Accept [13]previous minutes

RESOLVED: to accept
  http://www.w3.org/2002/05/27-tag-summary
  Mon, 27 May 2002 22:17:45 GMT

  as a true record.

  (note: the [13] pointer in the agenda was wrong.)

RESOLVED: to meet again 10Jun, 3pET.

  potential regrets: DaveO
  timbl has a telcon just before

  NOTE WELL: Stu/Ian are expected to organize the agenda.


>      2. Accept this agenda

added: status whenToUseGet-7 and XMLP WG

>    1.1 New issues?
http://www.w3.org/2002/06/03-tagmem-irc#T19-10-30

RESOLVED: to accept errorHandling-20 as a new issue,
following discussion with RobLa et. al.


> 2. Technical (75min)
http://www.w3.org/2002/06/03-tagmem-irc#T19-12-55

>    2.1 Findings in progress, architecture document (25min)

continued: ACTION IJ 2002/03/18: Integrate/combine one-page summaries
(Revised)

continued: (in progress): ACTION TBL 2002/05/05: Negotiate more of IJ
time for arch doc

pending XMLP response:
ACTION DO/TB/CL 2002/05/05: Polish up DO's .1-level draft and find out what's going on with XForms
see also: agenda item 2.2.4. whenToUseGet-7, progress in XMLP WG below.

continued: ACTION NW 2002/05/20: Draft a finding for
formattingProperties-19; find out source of issue from CSS WG.

continued: ACTION IJ 2002/05/20: Revise and publish whenToUseGet-7
finding

continued: ACTION CL 2002/05/05: Add concern regarding non-western
characters to the POST scenario (issue whenToUseGet-7)


>     See [15]findings.
>      1. Confirm completed status of [16]Internet Media Type
>          registration, consistency of use.
http://www.w3.org/2002/06/03-tagmem-irc#T19-25-42

>         This resolves [17]issue w3cMediaType-1. Open pieces
>         remain for [18]customMediaType-2 use of "+xml" convention?
>         Do all "shoulds of [19]RFC 3023 section 7.1 apply? (~5min)

RESOLVED: to adopt
    Internet Media Type registration, consistency of use
    http://www.w3.org/2001/tag/2002/0129-mime
    $Date: 2002/05/21 19:36:40 $ $Revision: 1.25 $
  with dissent from Tantek noted.

[TimBL and everybody, I wasn't sure, at the time, whether
we were resolved or not. I now believe we were.

I'm not sure what the TAG does with decisions  that are
made without consensus; I presume we need to carry the
outstanding dissent forward. Ian, please acknowledge
the dissent specially in the issues list somehow.]

ACTION DanC: research the bug in the svg diagram.


RESOLVED: to accept a new issue, RFC3023-charset-21
ACTION Chris: to write up the issue in the next day or so.



>      2. [20]QNames as Identifiers ([21]issue qnamdAsId-18). (~5min)

POSTPONED in favor of charmodReview-17.

>    2.2 Priority issues (50min)
> 
>      1. Finalize TAG position on [22]charmodReview-17. (~20min)
http://www.w3.org/2002/06/03-tagmem-irc#T19-44-48

RESOLVED: agreed to mid:120200295000.20020527215051@w3.org
http://lists.w3.org/Archives/Public/www-tag/2002May/0164.html , subject
to ammendments by norm.

ACTION Norm: tell I18N WG.

RESOLVED: SHOULD NOT in specifications add rules for character encoding
beyond what is provide in XML. And you MUST NOT restrict character sets
beyond what XML allows (you MUST support UTF8 and UTF16) . e.g. for some
routing protocol that uses XML, MUST NOT use other than utf-8/16 is
acceptable, but not for something human-editable like MathML20:08:42
ACTION Norm: tell I18N WG while he's at it.


>      2. Status of [23]URIEquivalence-15. Relation to Character Model of
>         the Web (chapter 4)? (~20min)

POSTPONED.

>      3. If we get here: [24]httpRange-14, [25]namespaceDocument-8

POSTPONED.


4. whenToUseGet-7, progress in XMLP WG.
http://www.w3.org/2002/06/03-tagmem-irc#T20-10-46

ACTION: DaveO will report to the XMLP task force that for operations
where GET would be appropriate SOAP nodes should provide the ability to
use GET


-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
Received on Monday, 3 June 2002 17:08:31 GMT

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