IRC log of tagmem on 2012-02-09

Timestamps are in UTC.

17:53:10 [RRSAgent]
RRSAgent has joined #tagmem
17:53:10 [RRSAgent]
logging to http://www.w3.org/2012/02/09-tagmem-irc
17:56:57 [Ashok]
Ashok has joined #tagmem
17:59:36 [JeniT]
JeniT has joined #tagmem
18:00:01 [ht]
ht has joined #tagmem
18:00:29 [DKA]
DKA has joined #tagmem
18:01:30 [JeniT]
trackbot, start telcon
18:01:32 [trackbot]
RRSAgent, make logs public
18:01:34 [trackbot]
Zakim, this will be TAG
18:01:34 [Zakim]
ok, trackbot, I see TAG_Weekly()1:00PM already started
18:01:35 [trackbot]
Meeting: Technical Architecture Group Teleconference
18:01:35 [trackbot]
Date: 09 February 2012
18:01:38 [plinss]
zakim, [IPcaller] is me
18:01:38 [Zakim]
+plinss; got it
18:01:46 [JeniT]
Zakim, who's on the call?
18:01:47 [Zakim]
On the phone I see ??P0, plinss, [IPcaller.a]
18:02:18 [Ashok]
zakim, IPcaller.a is me
18:02:18 [Zakim]
+Ashok; got it
18:02:22 [Zakim]
+Jonathan_Rees
18:02:36 [Zakim]
-Jonathan_Rees
18:03:01 [jar]
jar has joined #tagmem
18:03:01 [plinss]
JeniT: http://www.w3.org/2006/tools/wiki/Zakim_Tips
18:03:02 [Zakim]
+Masinter
18:03:08 [ht]
ht has joined #tagmem
18:03:12 [Zakim]
+DKA
18:03:39 [Zakim]
+Jonathan_Rees
18:03:46 [DKA]
(BTW Noah invited me to attend today - I haven't gone senile - yet.)
18:03:53 [Zakim]
+??P10
18:04:11 [JeniT]
DKA, he probably wants you to provide the minutes from however many weeks ago you scribed ;)
18:04:24 [DKA]
I thought I did that.
18:04:42 [Larry]
Larry has joined #tagmem
18:04:45 [noah]
noah has joined #tagmem
18:04:49 [Zakim]
+noah
18:04:57 [Larry]
scribenic: Larry
18:05:03 [Larry]
scribe: Larry
18:05:08 [noah]
zakim, who is here?
18:05:08 [Zakim]
On the phone I see JeniT, plinss, Ashok, Masinter, DKA, Jonathan_Rees, ht, noah
18:05:10 [Zakim]
On IRC I see noah, Larry, ht, jar, DKA, JeniT, Ashok, RRSAgent, Zakim, plinss, trackbot, Yves
18:06:09 [Larry]
agenda: http://www.w3.org/2001/tag/2012/02/09-agenda
18:06:17 [JeniT]
I might not be able to make next week
18:07:05 [Larry]
Yves regrets today, Jonathan 2/23
18:07:29 [Larry]
topic: agenda review
18:07:55 [DKA]
Minutes from the 19th now sent - sorry about that.
18:08:42 [ht]
http://www.w3.org/2001/tag/group/track/actions/23
18:09:43 [Larry]
topic: approval of minutes
18:09:57 [noah]
Minutes of the 19th of January: Concentration of KIO3 (M)
18:09:59 [DKA]
http://www.w3.org/2001/tag/2012/01/19-minutes.html
18:10:05 [Larry]
http://www.w3.org/2001/tag/2012/01/19-minutes
18:10:08 [noah]
Minutes of the 19th of January: http://www.w3.org/2001/tag/2012/01/19-minutes
18:11:02 [Larry]
resolution: minutes of 19 Jan approved
18:11:13 [noah]
Minutes from Feb. 2: http://www.w3.org/2001/tag/2012/02/02-minutes
18:11:33 [Larry]
RESOLUTION: minutes of 19 Jan approved
18:11:52 [Larry]
RESOLUTION: http://www.w3.org/2001/tag/2012/02/02-minutes Minutes of 2/2 approved
18:12:23 [Larry]
topic: administrative items
18:12:25 [Zakim]
-JeniT
18:12:34 [Larry]
no news on these
18:12:50 [Zakim]
+??P0
18:12:51 [Larry]
topic: Action-563, note to Jeff
18:13:01 [noah]
ACTION-563?
18:13:01 [trackbot]
ACTION-563 -- Noah Mendelsohn to arrange for periodic TAG key issues reports to Jeff per June 2011 F2F Due 2011-10-15 -- due 2012-01-31 -- OPEN
18:13:01 [trackbot]
http://www.w3.org/2001/tag/group/track/actions/563
18:13:12 [plinss]
zakim, ?P0 is me
18:13:12 [Zakim]
sorry, plinss, I do not recognize a party named '?P0'
18:13:23 [noah]
Proposed text: https://lists.w3.org/Archives/Member/tag/2012Feb/0012.html
18:13:31 [plinss]
zakim, P0 is me
18:13:31 [Zakim]
sorry, plinss, I do not recognize a party named 'P0'
18:13:51 [Larry]
https://lists.w3.org/Archives/Member/tag/2012Feb/0012.html
18:15:16 [DKA]
I largely agree with Robin's comments.
18:15:36 [DKA]
I suggest removing the reference to Flash as it's a red herring.
18:15:43 [DKA]
(IMO)
18:15:59 [noah]
Robin offers revised text: https://lists.w3.org/Archives/Member/tag/2012Feb/0023.html
18:17:22 [timbl]
timbl has joined #tagmem
18:17:28 [DKA]
I would suggest an intro paragraph.
18:17:58 [Larry]
shorter is better than longer
18:20:14 [Larry]
Larry: i think Robin's is shorter, and removing an irrelevant sentence from it would make it shorter still, which is good.
18:20:46 [Larry]
Larry: I also think we should delete the sentence about SSL and privacy and SPDY because it's controversial and not helpful.
18:21:16 [DKA]
"The Web has become an application deployment platform for 'desktop' devices. It has been held back from this role by the rise of proprietary app formats and closed app stores. As a result, much content and many user experiences are being locked into proprietary formats and applications and are not part of the Web. This is clearly a threat to the open Web. What can be done to make the Web the preferred development and deployment environment for these types of
18:21:16 [DKA]
applications?"
18:21:36 [noah]
Remove the whole sentence, or just the phrase about Flash?
18:22:02 [Larry]
The whole sentence, the discussion about proprietary vs. "open" is interesting but complex
18:22:16 [noah]
This is primarily due to the fact that, as it was with Flash for over a decade, it is faster to ship a proprietary feature than the same one through a specification with multiple interoperable implementations.
18:23:26 [Larry]
Larry: we can raise the issue without taking a stand on a complex issue
18:23:35 [noah]
I actually think the interesting point is that many proprietary features are introduced in conjunction with hardware changes and/or proprietary back-end (cloud) infrastructure (e.g. Siri)
18:24:23 [Larry]
It's an interesting discussion that i'd love to have but we haven't had
18:24:47 [Larry]
There's an interesting question about development of featurees in an "open" way
18:24:54 [Larry]
"Standards follow innovation"
18:26:57 [Larry]
"This is primarily due to " => "This may well be due to "
18:27:13 [Larry]
noah: we could put weasel words
18:28:12 [Zakim]
-??P0
18:28:17 [Larry]
noah: I think what's happening in the mobile space is much deeper. People are building hardware/software/server stack and developing it, and then brining it to the standard.
18:28:37 [Zakim]
+??P0
18:28:58 [Larry]
noah: part of what made Siri interesting was the proprietary noise cleanup. And that what happens in the open space is going to be a generation behind.
18:29:43 [noah]
s/noise cleanup/noise cleanup that's implemented in proprietary hardware in the CPU chip/
18:29:59 [Larry]
dka: in fact, what's happening in mobile is different. ON the desktop innovation was moving to the web, but in mobile the innovation in mobile (and tablets) is moving....
18:30:12 [jar]
noah: Anything we do on the web is going to be a generation behind. DKA: But on mobile all the innovation is happening in web. (?)
18:30:29 [Larry]
dka: device APIs and touch events working group... this is part of a good story, mitigation of the threat is happening already
18:30:37 [noah]
Therefore, it's hard to standardize audio cleanup unless the underlying capability becomes widespread.
18:30:58 [Larry]
Larry: change of opinion, i'm ok with shipping Robin's text as is.
18:32:00 [noah]
We agree without objection to remove the pharse: "as it was with Flash for over a decade,"
18:32:02 [Larry]
"This is primarily due to the fact that, as it was with Flash for over a decade, it is faster to ship a proprietary feature than the same one through a specification with multiple interoperable implementations.
18:32:36 [noah]
Discussing proposed new intro text:
18:32:37 [noah]
"The Web has become an application deployment platform for 'desktop' devices. It has been held back from this role by the rise of proprietary app formats and closed app stores. As a result, much content and many user experiences are being locked into proprietary formats and applications and are not part of the Web. This is clearly a threat to the open Web. What can be done to make the Web the preferred development and deployment environment for these types
18:32:37 [noah]
<DKA> applications?"
18:33:17 [noah]
"The Web has become an application deployment platform for 'desktop' devices. It has been held back from this role on mobile and tablet devices by the rise of proprietary app formats and closed app stores. As a result, much content and many user experiences are being locked into proprietary formats and applications and are not part of the Web. This is clearly a threat to the open Web. What can be done to make the Web the preferred development and deploymen
18:34:00 [Larry]
-1
18:34:13 [noah]
-0.5
18:34:20 [Larry]
s/-1/Larry: -1
18:35:13 [noah]
Noah: I hear agreement to include Robin's text in place of mine, minus the phrase on Flash
18:35:23 [noah]
https://lists.w3.org/Archives/Member/tag/2012Feb/0012.html
18:35:32 [plinss]
I have an additional item for the list. Sending in email to the member list due to bad audio on this call.
18:36:25 [Larry]
Larry: I propose removing Also, the use of SSL for all
18:36:25 [Larry]
SPDY interactions offers the promise of improved privacy on the Web,
18:36:25 [Larry]
but also raises architectural questions relating to caching,
18:36:25 [Larry]
certificate management, etc.
18:36:38 [jar]
+1
18:36:49 [noah]
Jonathan, is that +1 to removing?
18:36:55 [jar]
t
18:37:11 [DKA]
+1
18:39:00 [noah]
I thought we heard that, while SSL will not be >required<, it will usually be needed in practice to get through existing proxies.
18:39:30 [jar]
whether true or false, the privacy comment is controversial, and doesn't add anything significant to the note to Jeff. just flush it
18:41:00 [jar_]
jar_ has joined #tagmem
18:41:50 [noah]
Existing deployments of SPDY depend on SSL for tunneling through existing proxies, and therefore raise also raises architectural questions relating to caching,
18:41:50 [noah]
certificate management, etc
18:42:03 [noah]
Existing deployments of SPDY depend on SSL for tunneling through existing proxies, and therefore raises architectural questions relating to caching,
18:42:12 [noah]
certificate management, etc
18:42:23 [noah]
Existing deployments of SPDY depend on SSL for tunneling through existing proxies, which raises architectural questions relating to caching,
18:42:25 [noah]
Existing deployments of SPDY depend on SSL for tunneling through existing proxies, which raises architectural questions relating to caching,
18:42:26 [noah]
certificate management, etc
18:42:38 [DKA]
could be "e.g. related to caching"
18:43:09 [Larry]
i'm not sure "depend on" is accurate
18:43:32 [noah]
Existing deployments of SPDY use SSL for tunneling through existing proxies, which raises architectural questions relating to caching,
18:43:33 [noah]
certificate management, etc
18:43:39 [DKA]
+1
18:43:41 [JeniT]
+1
18:43:42 [noah]
+1
18:43:48 [jar]
+1
18:43:49 [noah]
Any objections?
18:43:51 [noah]
None
18:43:56 [noah]
We'll make that change.
18:44:03 [Zakim]
-??P0
18:44:23 [Zakim]
+??P0
18:45:16 [noah]
Additional item from Peter: https://lists.w3.org/Archives/Member/tag/2012Feb/0025.html
18:46:44 [Larry]
larry: I like the topic, but i don't think it's narrowly applied to CSS as much as it is that the battle for distributed extensibility continues
18:47:46 [noah]
Proposed topic: Proliferation of proprietary properties
18:48:24 [Larry]
Proposed topic: "Distributed extensibility and CSS vendor prefixes at issue"
18:48:26 [noah]
Mozilla and Opera are currently making plans to implement support for -webkit- prefixed CSS properties in their respective browsers. They feel they are being driven to this due to the large amount of mobile web content that only provides -webkit- prefixed properties despite the availability of equivalent prefixed properties on Gecko and Presto.
18:48:32 [noah]
if browser vendors begin implementing other browser's proprietary properties, the entire standards process is in danger of getting usurped. This also puts the plan to apply vendor prefixes in another areas (such as JavaScript) at risk as the primary purpose for having vendor specific prefixes is being bypassed.
18:51:31 [noah]
There is some hope that the CSS working group can make progress in limiting long-term deployment of proprietary extensions that would be better standardized, but prospects for success aren't entriely clear.
18:51:44 [Larry]
Larry: We're still trying to manage 'distributed extensibility', and the method CSS was using is now (also) under threat.
18:51:49 [noah]
s/enreily/entirely/
18:51:50 [ht]
"We're still trying to manage distributed extensibility, but the mechanism the CSS WG was using is now under threat"
18:52:01 [ht]
I really like that sentence of Larry's
18:52:48 [noah]
From the top:
18:52:55 [noah]
We're still trying to manage distributed extensibility, but the mechanism the CSS WG was using is now under threat"
18:53:05 [noah]
Mozilla and Opera are currently making plans to implement support for -webkit- prefixed CSS properties in their respective browsers. They feel they are being driven to this due to the large amount of mobile web content that only provides -webkit- prefixed properties despite the availability of equivalent prefixed properties on Gecko and Presto.
18:53:10 [noah]
if browser vendors begin implementing other browser's proprietary properties, the entire standards process is in danger of getting usurped. This also puts the plan to apply vendor prefixes in another areas (such as JavaScript) at risk as the primary purpose for having vendor specific prefixes is being bypassed.
18:53:18 [noah]
There is some hope that the CSS working group can make progress in limiting long-term deployment of proprietary extensions that would be better standardized, but prospects for success aren't entriely clear.
18:53:40 [noah]
The CSS working group may make progress in limiting long-term deployment of proprietary extensions that would be better standardized, but prospects for success aren't entriely clear.
18:53:57 [noah]
Proposed topic: "Distributed extensibility and CSS vendor prefixes at issue"
18:54:07 [noah]
at issue?
18:54:19 [noah]
Proposed topic: "Distributed extensibility and CSS vendor prefixes"
18:54:36 [Larry]
Larry: +1 ship it
18:54:42 [noah]
Should we adopt this as an additional section?
18:54:48 [JeniT]
+1
18:54:52 [noah]
Agreed without objection.
18:55:28 [Larry]
noah: send this note, on behalf of the TAG to Jeff?
18:55:32 [DKA]
Rock it.
18:55:43 [noah]
. RESOLUTION: The TAG agrees that Noah should send the note to Jeff on behalf of the TAG
18:55:45 [JeniT]
+1
18:55:49 [noah]
RESOLUTION: The TAG agrees that Noah should send the note to Jeff on behalf of the TAG
18:55:50 [Larry]
+1
18:59:00 [noah]
Agreed that Noah will ask Jeff, for this one and in general, what level of distribution he'd prefer.
18:59:01 [Larry]
larry: in general these should all be public since the discussion is public
18:59:36 [Larry]
larry: i think this is a good precedent
18:59:49 [Zakim]
-??P0
19:00:03 [Zakim]
+??P0
19:00:25 [noah]
topic: XML Schema namespace document in the XML Schema WG
19:00:29 [noah]
ACTION-23?
19:00:29 [trackbot]
ACTION-23 -- Henry Thompson to track progress of #int bug 1974 in the XML Schema namespace document in the XML Schema WG -- due 2012-01-24 -- PENDINGREVIEW
19:00:29 [trackbot]
http://www.w3.org/2001/tag/group/track/actions/23
19:00:50 [jar]
zakim, ??P0 is plinss, we think
19:00:50 [Zakim]
I don't understand '??P0 is plinss, we think', jar
19:01:40 [noah]
HT: Since day 1, the Schema Rec has said "if you want to identify datatype X", use a URI of the form URI-for-schema-namespace#X. RDF has been doing this.
19:02:02 [noah]
HT: It was observed (probably by Noah), that doing this is suspect if there aren't anchors for those URIs
19:02:09 [noah]
HT: So far, 'taint there.
19:02:32 [jar]
we should do it as RDFa, with rdfs:comment properties
19:02:42 [noah]
HT: I thought 6 or 7 years ago I knew what to do to fix it. I had a proposed alternative namespace document, in the form of an HTML document, with an anchor for each name.
19:02:59 [noah]
HT: Didn't happen for unintersting reasons.
19:03:44 [noah]
HT: I recently tried to get focus from the Schema WG. The editor did some work. It was pointed out to me two weeks ago on the TAG call that adding the anchors makes things worse, not better, because it suggests that the URIs refer to elements, not datatypes. A bad thing.
19:04:29 [noah]
HT: Didn't get to do all my homework, but would like to ask Jonathan. The TAG has long standing advice that says: you should publish a document at the namespace URI.
19:04:39 [noah]
I think we encourged RDDL, no?
19:04:46 [noah]
scribenick: noah
19:04:52 [noah]
HT: Two part question:
19:05:08 [noah]
HT: 1) Does the TAG believe that namespace documents should be served with a 200 or a 303
19:05:26 [jar]
ht: if the URI identifies a namespace, should its namespace doc be served at that URI with a 200?
19:05:39 [noah]
HT: 2) If with a 200, should we include directly or indirectly RDFa, to establish triples for the bindings.
19:05:43 [jar]
q?
19:06:29 [noah]
JAR: Namespaces seem very similar to RDF graphs. I wouldn't worry about the 200. Probably should use RDFa.
19:06:32 [Larry]
jar: I think namespaces are very similar to RDF graphs. We might not need to invent any vocabulary for it, they should just used RDFa.
19:06:54 [Larry]
ht: i know how to say 'is defined by'. jar: rdf:type ?
19:06:58 [noah]
scribenick: Larry
19:07:10 [Larry]
jar: I'm looking at the model document
19:07:18 [Larry]
jeni: I think it is rdf:datatype
19:07:26 [noah]
q+ to ask Jar a clarificaiton, once this discussion dies down
19:07:44 [JeniT]
http://www.w3.org/TR/rdf-schema/#ch_datatype
19:07:46 [Larry]
larry: why is this a TAG topic
19:07:49 [JeniT]
rdfs:Datatype
19:08:00 [jar]
larry, there were 2 questions. The comparison to rdf graphs was in answer to #1. RDFa was in answer to #2.
19:08:08 [Larry]
noah: the TAG has had opinions for a long time on how to put namespaces on the web
19:08:10 [noah]
ack next
19:08:11 [Zakim]
noah, you wanted to ask Jar a clarificaiton, once this discussion dies down
19:08:45 [Larry]
noah: JAR, you started "Namespaces are a lot like RDF graphs". You then said "I wouldn't ... about 200"
19:09:00 [ht]
s/i know/I expect we need two triples for each URI, one saying "is defined by" [some anchor in the schema spec, and one saying "is a datatype". I know how to say "is defined by", and how to say "is a", but how do I say "datatype"? JAR replies: rdf:type/
19:09:02 [Larry]
noah: you might need rdf+xml or turtle
19:10:06 [Larry]
noah: in this case, we're saying return an HTML document with a 200, that the semantics were "this URI refers to a document, the fragments in it within anchors within the document, and by the way, the document may return RDF triples"
19:10:19 [Larry]
jar: your conclusions go way further than the specs warrant
19:11:02 [Larry]
ht: the proposal is not to include anchors in the HTML
19:11:10 [Larry]
jar: I'm saying use RDFa
19:11:16 [jar]
not anchors
19:11:26 [Larry]
larry: can they use microdata?
19:12:00 [Larry]
noah: if no one else feels this is broken
19:12:28 [Larry]
ht: please put this back in the 'Due' pile, but the last call on Rec is soon
19:12:35 [noah]
ACTION-23?
19:12:35 [trackbot]
ACTION-23 -- Henry Thompson to track progress of #int bug 1974 in the XML Schema namespace document in the XML Schema WG -- due 2012-02-14 -- OPEN
19:12:35 [trackbot]
http://www.w3.org/2001/tag/group/track/actions/23
19:12:37 [jar]
define it using RDFa only for now, not as anchor. later we can figure out whether we agree with Manu Sporny about about= + id=
19:12:47 [Zakim]
-ht
19:12:49 [noah]
Reopening and setting date at Henry's request. Need to intercept XSD going to Rec.
19:13:19 [ht]
s/need to intercept/need to be aware of/
19:13:27 [Larry]
ht: that was useful, will go back and work on this for next week
19:13:37 [Larry]
topic: web application storage
19:13:58 [noah]
Two weeks ago we said: http://www.w3.org/2001/tag/2012/01/26-minutes#item04
19:14:02 [noah]
ex: if you are creating something locally and it will be exported, what is the linking story there?
19:14:02 [noah]
let's continue in two weeks, when Ashok and Robin will be there
19:15:29 [Zakim]
-??P0
19:15:29 [Larry]
noah: With this topic, we don't seem to start off where we left off, this one has been near conclusion for a while
19:15:54 [jar]
jenit, you are right, rdf-mt has rdfs:Datatype as a subclass of rdfs:Class (which is a subtype of rdf:type ??…), so that's the one to use
19:15:55 [Larry]
noah: next topic, Web APplication, should awit for Robin
19:16:03 [Larry]
topic: pending review items
19:16:10 [noah]
s/near conclusion/struggling to get started/
19:16:11 [Zakim]
+??P0
19:16:20 [noah]
ACTION-568?
19:16:20 [trackbot]
ACTION-568 -- Noah Mendelsohn to draft note for Jeff Jaffe listing 5 top TAG priorities as trackable items. -- due 2012-01-03 -- PENDINGREVIEW
19:16:20 [trackbot]
http://www.w3.org/2001/tag/group/track/actions/568
19:17:03 [noah]
http://lists.w3.org/Archives/Public/www-tag/2011Aug/0030.html
19:17:38 [noah]
close ACTION-568
19:17:38 [trackbot]
ACTION-568 Draft note for Jeff Jaffe listing 5 top TAG priorities as trackable items. closed
19:17:39 [Larry]
+1 close it
19:17:58 [Larry]
no objection to closing 568
19:18:06 [noah]
ACTION-599?
19:18:06 [trackbot]
ACTION-599 -- Noah Mendelsohn to close out HTML5 review product -- due 2011-12-20 -- PENDINGREVIEW
19:18:06 [trackbot]
http://www.w3.org/2001/tag/group/track/actions/599
19:19:50 [noah]
http://lists.w3.org/Archives/Public/public-tag-announce/2011Dec/0001.html
19:20:07 [noah]
close ACTION-599
19:20:07 [trackbot]
ACTION-599 Close out HTML5 review product closed
19:20:28 [Larry]
action-651?
19:20:28 [trackbot]
ACTION-651 -- Noah Mendelsohn to announce closing of Web App State Product Due: 2012-01-17 -- due 2012-01-12 -- PENDINGREVIEW
19:20:28 [trackbot]
http://www.w3.org/2001/tag/group/track/actions/651
19:20:31 [noah]
ACTION-651?
19:20:31 [trackbot]
ACTION-651 -- Noah Mendelsohn to announce closing of Web App State Product Due: 2012-01-17 -- due 2012-01-12 -- PENDINGREVIEW
19:20:31 [trackbot]
http://www.w3.org/2001/tag/group/track/actions/651
19:20:48 [noah]
Closing announced in email to www-tag and public-tag-announce on 15 January 2012
19:20:52 [noah]
close ACTION-651
19:20:52 [trackbot]
ACTION-651 Announce closing of Web App State Product Due: 2012-01-17 closed
19:21:05 [noah]
ACTION-663?
19:21:05 [trackbot]
ACTION-663 -- Noah Mendelsohn to verify with Harry Halpin the TAG's plan to "keep an eye" on CA issues, and solicit his and TLR's help in keeping us informed Due: 2012-01-31 -- due 2012-01-31 -- PENDINGREVIEW
19:21:05 [trackbot]
http://www.w3.org/2001/tag/group/track/actions/663
19:21:21 [noah]
Sent this: http://lists.w3.org/Archives/Public/www-tag/2012Jan/0106.html
19:21:27 [jar]
q?
19:21:32 [noah]
close ACTION-663
19:21:32 [trackbot]
ACTION-663 Verify with Harry Halpin the TAG's plan to "keep an eye" on CA issues, and solicit his and TLR's help in keeping us informed Due: 2012-01-31 closed
19:22:02 [Larry]
jar: I plan to put out a draft on UDDP over the weekend
19:22:14 [Larry]
ashok: fine
19:22:52 [Larry]
noah: if you want something you want discussed and on the agenda, please let noah
19:23:00 [Larry]
s/let noah know/
19:23:12 [noah]
topic: Overdue actions
19:23:39 [noah]
ACTION-632?
19:23:39 [trackbot]
ACTION-632 -- Ashok Malhotra to frame issues around client-side storage work -- due 2012-02-07 -- OPEN
19:23:39 [trackbot]
http://www.w3.org/2001/tag/group/track/actions/632
19:23:54 [noah]
ACTION-632 Due 2012-02-14
19:23:54 [trackbot]
ACTION-632 Frame issues around client-side storage work due date now 2012-02-14
19:24:05 [noah]
ACTION-647?
19:24:05 [trackbot]
ACTION-647 -- Ashok Malhotra to draft product page on client-side storage focusing on specific goals and success criteria Due: 2012-01-17 -- due 2012-02-07 -- OPEN
19:24:05 [trackbot]
http://www.w3.org/2001/tag/group/track/actions/647
19:24:22 [noah]
close ACTION-632
19:24:23 [trackbot]
ACTION-632 Frame issues around client-side storage work closed
19:24:40 [noah]
ACTION-647 Due 2012-02-14
19:24:40 [trackbot]
ACTION-647 Draft product page on client-side storage focusing on specific goals and success criteria Due: 2012-01-17 due date now 2012-02-14
19:24:55 [noah]
ACTION-611?
19:24:55 [trackbot]
ACTION-611 -- Larry Masinter to draft initial cut at http://www.w3.org/standards/webarch/protocols -- due 2011-12-29 -- OPEN
19:24:55 [trackbot]
http://www.w3.org/2001/tag/group/track/actions/611
19:28:36 [Zakim]
-Masinter
19:30:00 [noah]
NM: Propose we adjourn. We can discuss in e-mail either reinvesting in helping W3C with architecture pages and/or improving the presence of the TAG on the Web
19:30:09 [jar]
+1
19:30:14 [noah]
NM: We are adjourned. Thank you.
19:30:18 [Larry]
my phone battery died
19:30:21 [Larry]
thanks
19:30:26 [Larry]
i'll get minutes out soon
19:30:29 [Zakim]
-Ashok
19:31:10 [Zakim]
-DKA
19:31:11 [Zakim]
-noah
19:31:12 [Zakim]
-JeniT
19:31:19 [Zakim]
-Jonathan_Rees
19:31:22 [Zakim]
-??P0
19:31:23 [Zakim]
TAG_Weekly()1:00PM has ended
19:31:23 [Zakim]
Attendees were Ashok, Jonathan_Rees, JeniT, Masinter, DKA, ht, noah
19:40:24 [jar]
rrsagent, make logs public
19:40:32 [jar]
rrsagent, pointer
19:40:32 [RRSAgent]
See http://www.w3.org/2012/02/09-tagmem-irc#T19-40-32
21:34:08 [Zakim]
Zakim has left #tagmem
23:17:46 [timbl]
timbl has joined #tagmem