W3C

- DRAFT -

WebCGM teleconference
20 Nov 2008

Agenda

See also: IRC log

Attendees

Present
Dave C
Thierry
Dieter
Don
Regrets
Benoit
Chair
Lofton
Scribe
Stuart

Contents


roll call 11:00am ET,

<lofton> Absent: Don, Dieter (LH: both joined later.)

<lofton> Agenda: http://lists.w3.org/Archives/Public/public-webcgm-wg/2008Nov/0051.html

Al Gilman questions & remarks

Carry forward to next telecon. Everyone have a look.

LC Review completion and DoC

Lofton suggests that we move the completion date out two weeks from today.

resolutions of Issues 1, 2, and 3 (in the draft Disposition of Comments) can probably be endorsed today

there were no objections to approving resolution of Issue #1

there were no objections to approving resolution of Issue #2

Issue #3: DoC's clarifying sentence about Style Properties is okay. Benoit's criticism of 'locus' remains open.

Dieter pointed out that locus is not precise as used in the getObjExt text, because an APS can contain multiple drawn primitives, and various definitions of 'locus' seem more appropriate for single graphical primitives.

Lofton said its usage needs to include all of the graphical primitives within the APS

Dieter said it also doen't specify how to deal with rasters

davec - says that it should be the extents of the raster "patch"

Action item for someone who disagrees with the current wording to propose better wording

I18N comments

I18N submitted some comments that are located http://www.w3.org/International/reviews/0811-webcgm/

I18N comment 1 is editorial. Proposed response (agenda reference [8]) approved.

I18N comment 2 will be clarified to remove the ambiguity. Proposed response (agenda reference [8]) approved.

I18N comment 3 is a reply to question. Proposed response to comment number 3 was approved (agenda reference [9]).

I18N comment 4 is about how to strip out whitespace. All agree with Lofton's proposed wording (agenda reference [9]).

I18N comment item 6:

We think this means comparsions should be made in unicode

<thierry> http://en.wikipedia.org/wiki/Unicode_normalization#Normalization

I was looking at http://unicode.org/reports/tr15/

<scribe> ACTION: Stuart will look at unicode normalization and try to figure out what it means [recorded in http://www.w3.org/2008/11/20-webcgm-minutes.html#action01]

<trackbot> Created ACTION-58 - Will look at unicode normalization and try to figure out what it means [on Stuart Galt - due 2008-11-27].

I18N comment 5:

ISOLatin 1 is the default charater set

lofton: ISOlatin1 is the WebCGM default character set. The majority of WebCGM content for which the normalization rules were designed is ISOLatin1. Which is why it was specifically mentioned. It was not our intent to limit it to only ISOLatin1 but in character sets that are very different from ISOLatin1 the rules might give odd results.

Active new threads:

people need to comment on the open threads

Summary of Action Items

[NEW] ACTION: Stuart will look at unicode normalization and try to figure out what it means [recorded in http://www.w3.org/2008/11/20-webcgm-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.133 (CVS log)
$Date: 2008/11/21 00:52:48 $