See also: IRC log
<dorchard> scribe: dorchard
<Norm> Scribe: Dave Orchard
<Norm> ScribeNick: dorchard
<Norm> Date: 18 July 2006
<EdR> http://www.w3.org/2002/ws/addr/minutes.html
<noah> More hints on taking minutes:
Henry to scribe once VQ convinces him
RESOLUTION: Minutes of 27-Jun approved
<noah> The minutes we just approved for 27-June-2006 are at:
EdR: can't do passwords in the clear
<EdR> I'll publish Passwords a week prior to the 8th meeting for public/tag
<EdR> please put it on the agenda for the 8th.
TV: still need more to do
tvr: also addressing public comments
... seems to be benignly interesting
vq: need new/more reviewers
... volunteers?
norm: I can review but won't be present on the 8th
do: no time
nm: date is important so reviewers know when doc is stable
tvr: pls review after Aug 8th
<scribe> ACTION: TVR to publish new version of Generic Resources by Aug 8th [recorded in http://www.w3.org/2006/07/18-tagmem-minutes.html#action01]
vq: after checking into cvs please send to public list
... any more comments
dbo: I think tvr is still working on my comments
tvr: I thought I got them, can you look again?
vq: AB asked about using media types that aren't yet registered but used
dbo: think we shouldn't say anything against using unregistered media types
tvr: I was on voice browser wg, and the group was worried about getting LC
... can also relate to TAG position
nm: is there a written policy they should know about?
nobody knows of anything
nm: some worry about using unregistered media types
tvr: the widely deployed ones that aren't registered got widely deployed
nm: balance between saying there is a reason for registration
... reasons to reuse types
vq: ken laskey suggested something like this.
... then AB could use this and examine wrt w3c process
nm: not sure about how formal to be and even list in w3c process
vq: AB seems to ask for something informal, short email even
<Norm> Mostly I agree with Noah. I was going to point out that there's a distinction
<noah> Right, what I was trying to say was that it seems heavyweight to me to
<scribe> ACTION: Noah to draft of something rough on this [recorded in http://www.w3.org/2006/07/18-tagmem-minutes.html#action02]
<noah> ACTION 2=Noah to draft a very short email suggesting that in general its good
vq: there was also some discussion from AB on changes to ecmascript and
nw: on updated rfcs, specs need to do addendum to get new references
<scribe> ACTION: EdR to publish updated passwords in the clear by Aug 8th [recorded in http://www.w3.org/2006/07/18-tagmem-minutes.html#action03]
<Norm> ScribeNick: EdR
Vincent: Dave has updated the versioning document yesterday.
Dave: I prefer to walk through and give an overview and then take detailed
DO: In general what I've done has expunged much of the xml
... the sections on compatability, section 2 evolution is the same.
... then I did some more work on principles.
... I updated the bullet diagram based on our 'on the board' discussion at the
... I've tried to move towards the model of defining compatability based on
... In section 1.6 I talk about components instead of elements because we need
... I've added in the notion to avoid the 'big bang' by offering multiple
... this cant work in all cases (where new data fieldws are required) however.
Noah: I think is largely improved, however I'm only 5 pages into it.
... In the sections I've read I think the foundations are much stronger.
... I feel something needs tuning up.. it seems your looking for a very
... I think there are times where 99% of the instances have compatability
... I'm trying to seperate the notion that nobody should be able to every
... one important point is whether software will make mistake in
... We want to talk about the case where we plan for evolution, and in some
DO: I point out that if you want to enforce it, you need to point out a way to
Vincent: any other comments?
Norm: I have not had a chance to read it, but would like to for next week.
Ed: I havent yet either, but would like to.
Vincent: We can review in more detail next week.
... I've put it on the top of the agenda for next week.
... any other topics?
... meeting is adjourned.
<noah> More hints on taking minutes: