18:00:22 <RRSAgent> RRSAgent has joined #tagmem
18:00:22 <RRSAgent> logging to http://www.w3.org/2010/01/21-tagmem-irc
18:00:47 <Zakim> +Raman
18:00:53 <noah> Ashok - if you're scribing, please be sure to delete the conference code echoed by zakim from the public record.  Thank you.
18:00:59 <Zakim> +DKA
18:01:02 <Zakim> +Ashok_Malhotra
18:01:19 <noah> zakim, who is here?
18:01:19 <Zakim> On the phone I see noah, Raman, DKA, Ashok_Malhotra
18:01:20 <Zakim> On IRC I see RRSAgent, Zakim, jar, DKA, Ashok, noah, trackbot
18:02:08 <raman> raman has joined #tagmem
18:02:12 <raman> on and muted.
18:02:13 <noah> s/0824/xxxx/
18:02:24 <DKA> sorry!
18:02:28 <Ashok> chair: Noah_Mendelsohn
18:02:39 <Ashok> scribe: Ashok
18:02:45 <Zakim> + +1.781.643.aaaa
18:02:47 <noah> zakim, who is here?
18:02:47 <Zakim> On the phone I see noah, Raman, DKA, Ashok_Malhotra, +1.781.643.aaaa
18:02:47 <Ashok> scribenick: Ashok
18:02:51 <Zakim> On IRC I see raman, RRSAgent, Zakim, jar, DKA, Ashok, noah, trackbot
18:02:53 <jar> zakim, aaaa is jar
18:02:57 <Zakim> +jar; got it
18:03:00 <Ashok> regrets+ TimBL
18:03:09 <DKA> FYI I will have to leave the call at 19:20 GMT today.
18:03:11 <Ashok> regrets+ John_Kemp
18:03:27 <Ashok> regrets+ Henry_Thompson
18:03:47 <raman> will need to bale in 25 mins
18:04:16 <noah> zakim, who is here?
18:04:16 <Zakim> On the phone I see noah, Raman, DKA, Ashok_Malhotra, jar
18:04:17 <Zakim> On IRC I see raman, RRSAgent, Zakim, jar, DKA, Ashok, noah, trackbot
18:04:19 <Ashok> Topic:  Opening
18:04:32 <Ashok> Noah:  5 of us present
18:04:55 <Ashok> Noah:  Regrets from TimBL for 5 weeks or so
18:05:06 <Ashok> Noah:  There will be a call last week
18:05:36 <noah> s/last/next/
18:05:42 <Ashok> Topic:  Approval of Minutes 14 January 2009
18:06:18 <Ashok> RESOLUTION:  Minutes of Jan 14 meeting are approved
18:07:33 <Ashok> Topic:  ACTION-278: Draft changes to 2.7 of Metadata in URIs to cover the "Google Calendar" case 
18:07:54 <Ashok> Noah explains action
18:08:39 <jar> The finding: http://www.w3.org/2001/tag/doc/metaDataInURI-31#hideforsecurity
18:08:52 <jar> ACTION-278?
18:08:52 <trackbot> ACTION-278 -- Jonathan Rees to draft changes to 2.7 of Metadata in URIs to cover the "Google Calendar" case -- due 2010-01-20 -- PENDINGREVIEW
18:08:52 <trackbot> http://www.w3.org/2001/tag/group/track/actions/278
18:08:57 <noah> Jonthan's email: http://lists.w3.org/Archives/Public/www-tag/2009Dec/0121.html
18:09:16 <noah> q?
18:09:45 <Ashok> Jar:  This is a drft not a proposal
18:09:55 <noah> s/drf/draft/
18:10:01 <Ashok> ... came out of our discussion of capabilities
18:10:23 <noah> Could you say a bit more about the Google Calender use case in particular?  What are they doing?
18:10:25 <Ashok> ... URIs to carry secrets is used all over the web.  Finding shd talk abt this
18:11:09 <Ashok> JAR:  Scope of finding is not limited to public URIs
18:11:20 <masinter> masinter has joined #tagmem
18:11:23 <masinter> sorry
18:11:40 <Ashok> ... There is a web interface and you can say "share this calendar"... it says send this URI to yr friend
18:11:49 <Zakim> +masinter
18:12:09 <Ashok> If you send URI to friend and he clicks on it the calendars are shared
18:12:15 <Zakim> -DKA
18:12:29 <Ashok> Noah:  Does it carry authority as well as allow sharing?
18:12:39 <noah> Crucial case is that the URI carries not just the identification, but also the authorization.
18:12:40 <Ashok> JAR:  Yes, carries authority
18:12:48 <Zakim> +DKA
18:12:48 <noah> Speaking for myself, I don't like that, and don't want to encourage it.
18:13:06 <masinter> "click here to unsubscribe" also
18:13:07 <noah> I think AWWW is right to make identity and authorization orthogonal
18:13:10 <Ashok> JAR:  Tyler Close says this is used and is good
18:13:23 <noah> q+ to question the appropriateness of the use case
18:13:31 <DKA> Is it a one-time use URI?
18:13:43 <Ashok> ... the person getting URI could publish it and then everyone has access
18:13:49 <noah> DKA, I don't think so.  Sounds like you can explicitly kill it.
18:13:50 <noah> q?
18:13:52 <masinter> q+ to propose drafting a document and getting review of it in the security community
18:13:55 <jar> q?
18:13:58 <Ashok> ... but capability can be retracted
18:14:30 <jar> google docs is another example
18:14:31 <Ashok> DKA:  Is this a one time ise?  It is a pattern they use.
18:14:34 <noah> One time use seems break GET/safe
18:14:54 <Ashok> JAR:  For calendar it is one time use
18:15:14 <Ashok> ... in Google docs you can send to many people
18:15:31 <Ashok> Raman:  URL works only if you are in the ACL for document
18:15:50 <Ashok> ... you can manage access control
18:16:07 <masinter> Adobe Buzzword (acrobat.com) has similar options: "open to anyone who has the URL" is an access control option
18:16:24 <Ashok> Noah:  Is this also true of Calendar?
18:16:34 <Ashok> Raman:  Calendar has different model.  Events have URLs
18:17:10 <Ashok> ... if private no one can see it
18:17:33 <Ashok> ... there is a single sign-in mechanism
18:17:48 <Ashok> ... access to URL does not give access
18:18:02 <noah> q?
18:18:06 <jar> code.google.com/apis
18:19:01 <Ashok> Noah:  Crucial question:  Does the URI give access control?
18:19:08 <masinter> "Allow anyone with a link to view this document" is a access control option that the user can set
18:19:12 <noah> ack next
18:19:13 <Zakim> noah, you wanted to question the appropriateness of the use case
18:19:14 <Ashok> ... or is just an identifier
18:19:21 <raman> Calendar API:http://code.google.com/apis/calendar/
18:19:27 <raman> All Google APIs: http://code.google.com/apis/
18:19:28 <noah> s/Does the URI/Should a URI ever/
18:19:48 <Ashok> Larry:  I can create a doc from Apple.com and I can create a doc and share it
18:19:54 <masinter> acrobat.com
18:20:06 <Ashok> ... describes sharing options
18:20:16 <Ashok> s/Apple/acrobat/
18:20:39 <noah> I think the question is:  how much do you bend what you would otherwise do with Web architecture to enable Larry's case, which he acknowledges as "weak"
18:20:45 <noah> q+ to say, I take Larry's point
18:20:50 <noah> ack masinter
18:20:50 <Zakim> masinter, you wanted to propose drafting a document and getting review of it in the security community
18:21:05 <noah> ack next
18:21:06 <Zakim> noah, you wanted to say, I take Larry's point
18:21:37 <Ashok> Noah:  Seems like passwords in clear discussion
18:22:00 <Ashok> ... its a weak security mechanism.  URIs are widely shared.  Not like private key.
18:22:14 <masinter> +1 that this is like password in the clear
18:22:30 <Ashok> ... but people use it because it's convenient
18:22:51 <Ashok> ... people use it and understand the risks
18:23:50 <Ashok> JAR:  Why do they give 64-bit URIs if it is not a protection scheme?
18:24:00 <masinter> obfucation is a useful technique. I don't think anything about "protected channels" doesn't really help much
18:24:12 <Zakim> -Raman
18:24:18 <Ashok> ... key word is trade-offs.  Finding shd describe trade-offs
18:24:31 <masinter> s/obfucation/obfuscation/
18:24:51 <Ashok> Noah:  Finding says access control shd be done orthogonally.  I think this is right.
18:25:06 <masinter> obfuscation isn't "access control"
18:25:07 <Ashok> ... we shd not be vague abt that.
18:25:10 <DKA> After just trying to share a google calendar I can confirm that seems to be how it works. The URI does not allow automatic access to the calendar. It seems to encode expected access credentials but still requires a credentials check (authentication).
18:25:41 <Ashok> JAR:  If finding says do not do the Google Calendar case we lose ccredibility
18:26:18 <masinter> https://acrobat.com/#d=Y5W06lRXkILNhbfV1yUjsw
18:26:27 <noah> q?
18:26:30 <masinter> q+
18:27:14 <Ashok> Larry:  I made a doc, and service creates a URL and anyone who has URL can read document
18:27:16 <Ashok> ... not so unreasonable
18:28:01 <Ashok> Noah:  I'm not conviced there is anything in the finding that's wrong.
18:28:35 <noah> Pertinent section of finding: http://www.w3.org/2001/tag/doc/metaDataInURI-31.html#hideforsecurity
18:28:35 <masinter> maybe expand the finding to cover the obfuscated URI being used as weak access control
18:28:51 <noah> """
18:28:51 <noah> A bank establishes a URI assignment policy in which account numbers
18:28:51 <noah> are encoded directly in the URI. For example, the URI
18:28:51 <noah> http://example.org/customeraccounts/456123 accesses information for
18:28:51 <noah> account number 456123. A malicious worker at an Internet Service
18:28:52 <noah> Provider notices these URIs in his traffic logs, and determines the
18:28:53 <noah> bank account numbers for his Internet customers. Furthermore, if
18:28:55 <noah> access controls are not properly in place, he might be able to guess
18:28:57 <noah> the URIs for other accounts, and to attempt to access them.
18:28:59 <noah> Good Practice: URI assignment authorities SHOULD NOT put into URIs
18:29:01 <noah> metadata that is to be kept confidential.
18:29:03 <noah> """
18:29:18 <masinter> yes, so the use case i gave above would be a violation of the finding
18:29:24 <Ashok> Noah:  Says only a little abt access control
18:30:36 <Ashok> Larry:  The finding is too strong
18:30:46 <noah> Unconvinced
18:30:48 <Ashok> JAR:  Finding rules out commen usecase
18:31:04 <Ashok> s/commen/common/
18:31:27 <masinter> q+ to say I would rather findings be couched in terms of making people aware of the consequences, rather than telling them what to do
18:31:43 <Ashok> Noah and JAR disagree on what finding says and shd say
18:31:54 <jar> https
18:31:57 <noah> ack next
18:31:58 <Zakim> masinter, you wanted to say I would rather findings be couched in terms of making people aware of the consequences, rather than telling them what to do
18:32:53 <Ashok> Larry:  Try and write findings based on consequences of doing things one way instead of another
18:33:13 <Ashok> ... so finding shd say use this mechanism if risks a acceptable
18:33:22 <Ashok> s/a/are/
18:34:02 <Ashok> Larry:  Some of these exposures are over the long run instead of short run
18:34:24 <Ashok> Noah:  A similar example is abt GET being safe
18:34:38 <masinter> q+ to suggest review on public-web-security
18:35:09 <Ashok> ... I'm happy we said GET is unsafe
18:35:17 <noah> ack next
18:35:18 <Zakim> masinter, you wanted to suggest review on public-web-security
18:35:35 <Ashok> ... just because it is wide spread we shd not condone the practice
18:36:22 <Ashok> Larry:  Need more discussion of public-web-security
18:36:46 <Ashok> Noah:  I wd feel better if we had better framing of the issue
18:36:47 <DKA> q+ to note that there seem to be a number of use cases here that look similar but are actually different - maybe the WSC group has already enumerated these?
18:36:47 <noah> q
18:36:53 <noah> ack next
18:36:54 <Zakim> DKA, you wanted to note that there seem to be a number of use cases here that look similar but are actually different - maybe the WSC group has already enumerated these?
18:37:44 <Ashok> DKA: We need a list of usecases and need to categorize them
18:38:39 <Ashok> Noah:  How is Web Securiry Context connected with public-web-security
18:39:00 <Ashok> Larry:  JAR could send note to public-web-security and see if we can get discussion started
18:39:22 <Ashok> Noah:  We shd try and get some shared terminology
18:39:39 <Ashok> Larry:  Next step?
18:40:07 <Ashok> JAR:  Spell out usecases more clearly?
18:40:53 <Ashok> Noah:  Some disagreement.  Some feel just becuase commen usecase it shd be condoned
18:41:12 <Ashok> JAR:  We shd say what the finding is about
18:41:49 <Ashok> Noah:  We have differeing assumptions about what people can put in URIs
18:42:17 <Ashok> JAR:  Notion of URI is much broader than these public URIs
18:42:44 <Ashok> ... URIs used in all sorts on situations.  Web is just one use.
18:43:46 <masinter> I think the point that putting the secret in the FragID rather than in the main URI itself is interesting.
18:44:07 <Ashok> Noah:  Wat private keys are manged is fundamental to their use
18:44:32 <Ashok> JAR:  You are saying URIs have a connotation to a public space on the web
18:44:46 <Ashok> ... I don't agree with this.
18:44:52 <masinter> maybe this is also a justification for Origin vs. Referer? because Origin doesn't include private keys
18:44:59 <Ashok> ... Noah, this is your opinion
18:45:32 <masinter> use cases & discussions of them would be really great
18:45:44 <Ashok> JAR:  I'll take an action to drill down on the usecases
18:46:11 <Ashok> Noah:  Shall we add that to Action-278 and change the due date
18:46:49 <noah> ACTION-278: Due 2010-02-04
18:46:49 <trackbot> ACTION-278 Draft changes to 2.7 of Metadata in URIs to cover the "Google Calendar" case notes added
18:46:51 <Ashok> Larry:  I'm not hesitant to ask the web Security Group to jump in
18:47:06 <Ashok> q+
18:47:21 <masinter> might add the acrobat.com one too while you're at it; let me know if you need more details
18:47:51 <noah> AM: I hear Noah and Jonathan disagreeing about how URIs are used?  Will doing use cases fix that?
18:48:04 <noah> NM: Not sure it will, but it may clarify the context for the discussion.
18:48:18 <noah> q?
18:48:22 <noah> ack next
18:48:36 <masinter> Ashok: I think the finding needs to be more nuanced, and that different kinds of security situations will need different advice. Having use cases will help us understanding of the situations and thus what kind of contextual advice to give.
18:49:59 <Ashok> Noah:  There is no harm in any of us coming up with new text.  This could spark useful discussion.
18:50:13 <masinter> agenda?
18:50:14 <Ashok> Topic: ACTION-372: Redrafting of HTTP for resource vs. representation 
18:50:29 <noah> s/HTTP/HTML/
18:50:34 <Ashok> s/HTTP?HTML/
18:50:34 <masinter> action-372?
18:50:35 <trackbot> ACTION-372 -- Larry Masinter to tell the HTML WG the TAG encourages the direction Roy's headed on resource/representation and endorse his request for more time. -- due 2010-01-20 -- PENDINGREVIEW
18:50:35 <trackbot> http://www.w3.org/2001/tag/group/track/actions/372
18:50:39 <noah> Note error in agenda, should have referred to HTML not HTTP
18:51:29 <noah> LM: I sent the email.  Got a response which might be viewed as to me as HTML WG or to the TAG.
18:51:37 <Ashok> Larry:  I sent the mail.  I got a response.  The staus of the issue is - Roy is unavailable to work on this issue
18:51:56 <noah> Larry: that's not quite right -- Roy says not available for 4 months, then available.
18:52:08 <Ashok> ... actually Roy said "not available for 4 months to work on issue"
18:52:34 <Ashok> ... not sure it was intereptred as a TAG request
18:53:00 <Ashok> Larry:  Noah, please, as chair clarify how we communicate.
18:53:31 <Ashok> ACTION:  Noah to frame discussion about how TAG communicated with WGs
18:53:31 <trackbot> Created ACTION-377 - Frame discussion about how TAG communicated with WGs [on Noah Mendelsohn - due 2010-01-28].
18:54:23 <Ashok> Larry:  I would like Noah to talk to HTML WG ...
18:55:35 <Ashok> Noah:  Some WG communicate with other WGs.   The WG vote on this and someone is asked to send the msg.
18:56:06 <Ashok> ... the TAG has as part of its charter to help WGs do their work
18:56:16 <Ashok> ... in some cases TAG will ask individuals to talk with WGs
18:57:07 <Ashok> Larry:  I got a response and I don't think the WGs response is not in line in what was requested
18:57:21 <Ashok> Noah:  The process is fine ... we need to decide what to do?
18:57:49 <Ashok> Noah:  Larry, what shd TAG do?
18:58:16 <DanC> DanC has joined #tagmem
18:58:22 <Zakim> +DanC
18:59:07 <Ashok> Larry:  If we are happy to give upon this that's ok with me
18:59:21 <masinter> i'm not sure they acknowledged hearing our opinion
18:59:23 <Ashok> s/upon/on/
18:59:48 <Ashok> Dan:  I don't understand why Roy cannot do the 2 edits?
19:00:02 <masinter> Roy said: "Honestly, unless you can prove to ME that there is a substantial
19:00:02 <masinter> burden being imposed upon *someone* by reordering the entirely random order that chairs have decided to call for consensus, then it should be obvious that *MY* constraints are more important than whatever you personally think the procedure should be. Otherwise, you are just railroading a particular conclusion.
19:00:02 <masinter>  
19:00:44 <Ashok> Dan:  I think it's ok if they close this.
19:00:46 <masinter> q+ to note issue in abarth-mime-sniffing
19:00:57 <noah> ack next
19:00:58 <Zakim> masinter, you wanted to note issue in abarth-mime-sniffing
19:01:31 <DanC> s/I think it's ok if they close this./I can understand if they close this; we might say we don't like it, but unless we have a proposal.../
19:01:39 <jar> http://www.ietf.org/mail-archive/web/apps-discuss/current/msg01250.html
19:01:54 <Ashok> Larry:  JAR on authoritative metadata finding cites abarth-mimesniffing.  I did a review of this
19:02:07 <Ashok> ... go down to "terminology"
19:02:13 <noah> Quoting:
19:02:14 <jar> ???
19:02:14 <noah> TERMINOLOGY "resource"
19:02:14 <noah> This document seems to have the same use of "resource"
19:02:14 <noah> to talk about what is fetched and not just the source
19:02:14 <noah> from which it is fetched, as discussed in HTML-WG
19:02:14 <noah> at length:
19:02:16 <noah> http://www.w3.org/html/wg/tracker/issues/81
19:02:17 <noah> For example
19:02:19 <noah>    For HTTP resources, only the last Content-Type HTTP header,
19:02:21 <noah>    if any, contributes any type information; the official type 
19:02:23 <noah>    of the resource is then the value of that header, 
19:02:25 <noah>    interpreted as described by the HTTP specifications.  
19:02:50 <jar> s/JAR on/John Kemp on/
19:02:50 <noah> Right, the phrase "type of the resource" is highly suspect
19:03:45 <Ashok> Noah:  The continuing non-resolution of issue 81 is haveing deleterious effect on the Web
19:04:05 <Ashok> Larry:  Roy is the best person on planet to do this
19:04:15 <noah> To be clear, I was asking Larry whether the "continuing non-resolution" was has position, and he said yes.
19:04:28 <masinter> s/is the best/is arguably the best/
19:04:41 <masinter> s/the best/the most qualified/
19:05:33 <Ashok> Noah:  We could send a note as the TAG saying that we feel it is very important that this gets resolved
19:06:18 <Ashok> Dan:  We shd call the chairs or call Mike Smith ...
19:06:41 <Ashok> Noah:  Just say "this remains impt"
19:06:52 <DanC> s/Dan:  We shd call the chairs or call Mike Smith ...//
19:07:33 <masinter> http://lists.w3.org/Archives/Public/public-html/2010Jan/0853.html
19:07:41 <masinter>  Write clear definitions of all affected terms, possibly in the form of suggested edits to the terminology section, and demonstrate correct usage of the terms by suggesting specific edits to one or two representative sections.
19:07:41 <masinter>  
19:08:33 <Ashok> Larry:  The above is something the TAG shd take on
19:08:43 <DanC> s/shd/could/
19:09:27 <masinter> the definitions of these terms don't belong in HTML, they belong in webarch
19:10:08 <masinter> defining the terms of the web architecture seems like a fine job for the TAG, and that there is no other group more authoritative
19:10:11 <Ashok> Noah:  This could take up a lot of resources/time
19:10:39 <Ashok> Larry:  I'm willing to work on it and I would like some help
19:12:02 <jar> 799 occurrences of "resource" in Overview.html
19:12:03 <DanC> Zakim, pick a victim
19:12:03 <Zakim> Not knowing who is chairing or who scribed recently, I propose DanC
19:13:16 <masinter> are the terms not already clearly defined in WebArch?
19:13:20 <jar> no
19:13:43 <Ashok> Noah:  You would a great volunteer, Dan!
19:14:00 <Ashok> Larry:  Deadline is Jan 23
19:14:09 <masinter> http://lists.w3.org/Archives/Public/public-html/2010Jan/0930.html
19:14:27 <masinter> "... let the Chairs know if they are interested in drafting a proposal to resolve Issue-81."
19:14:59 <Ashok> Noah:  We could not leave public tracks and you can just try and do the work.
19:16:15 <Ashok> Noah:  I would like the resources lined-up first
19:16:35 <DanC> ACTION: draft suggested text re resource/representation in HTML 5 for discussion with LMM and JAR
19:16:35 <trackbot> Sorry, couldn't find user - draft
19:16:51 <DanC> ACTION Dan: draft suggested text re resource/representation in HTML 5 for discussion with LMM and JAR
19:16:51 <trackbot> Sorry, amibiguous username (more than one match) - Dan
19:16:51 <trackbot> Try using a different identifier, such as family name or username (eg. connolly, dappelqu)
19:16:59 <DanC> ACTION Connolly: draft suggested text re resource/representation in HTML 5 for discussion with LMM and JAR
19:16:59 <trackbot> Created ACTION-378 - Draft suggested text re resource/representation in HTML 5 for discussion with LMM and JAR [on Dan Connolly - due 2010-01-28].
19:17:33 <masinter> http://www.w3.org/TR/webarch/#id-resources defines "resource"
19:17:42 <masinter> http://www.w3.org/TR/webarch/#def-representation defines "representation"
19:18:06 <Ashok> Topic:  Review Pending Actions
19:18:08 <noah> http://www.w3.org/2001/tag/group/track/actions/pendingreview
19:18:42 <DanC> ACTION-213 due next week
19:18:42 <trackbot> ACTION-213 Prepare 21 Jan weekly teleconference agenda due date now next week
19:19:21 <DanC> ACTION-213?
19:19:21 <trackbot> ACTION-213 -- Noah Mendelsohn to prepare 21 Jan weekly teleconference agenda -- due 2010-01-26 -- PENDINGREVIEW
19:19:21 <trackbot> http://www.w3.org/2001/tag/group/track/actions/213
19:20:02 <DKA> I must leave the call now - apologies - Noah please feel free to put me on the scribe rota for a future call except for Feb 18 where I will have to give my regrets.
19:20:24 <Zakim> -DKA
19:21:15 <DanC> action-278?
19:21:15 <trackbot> ACTION-278 -- Jonathan Rees to draft changes to 2.7 of Metadata in URIs to cover the "Google Calendar" case -- due 2010-02-04 -- OPEN
19:21:15 <trackbot> http://www.w3.org/2001/tag/group/track/actions/278
19:22:10 <masinter> http://www.ietf.org/mail-archive/web/apps-discuss/current/msg01250.html is linked from ACTION-308
19:25:07 <noah> On ACTION-337, Larry wants to punt.
19:25:23 <DanC> ACTION-337: Larry wants to punt.
19:25:23 <trackbot> ACTION-337 Prepare material for next phone conf metadata formats/representations notes added
19:25:34 <DanC> close action-337
19:25:34 <trackbot> ACTION-337 Prepare material for next phone conf metadata formats/representations closed
19:27:04 <DanC> order? is larry asking for futher discusison of ACTION-367?
19:27:17 <DanC> it's done to my satisfaction.
19:27:18 <noah> trying to find out
19:28:02 <DanC> if there are possible follow-ons, then it should be kept pending review. sigh.
19:29:03 <DanC> (no, I don't see a URL for the bug)
19:29:06 <masinter> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8220
19:30:49 <DanC> close ACTION-372
19:30:49 <trackbot> ACTION-372 Tell the HTML WG the TAG encourages the direction Roy's headed on resource/representation and endorse his request for more time. closed
19:32:03 <masinter> action-373?
19:32:03 <trackbot> ACTION-373 -- Noah Mendelsohn to convey, re language reference, to encourage the path they've indicated; we can't tell if we're satisifed; we'll stay tuned and comment when drafts become available -- due 2010-01-28 -- PENDINGREVIEW
19:32:03 <trackbot> http://www.w3.org/2001/tag/group/track/actions/373
19:32:05 <DanC> action-373?
19:32:05 <trackbot> ACTION-373 -- Noah Mendelsohn to convey, re language reference, to encourage the path they've indicated; we can't tell if we're satisifed; we'll stay tuned and comment when drafts become available -- due 2010-01-28 -- PENDINGREVIEW
19:32:08 <trackbot> http://www.w3.org/2001/tag/group/track/actions/373
19:32:31 <DanC> I'm happy with Maciej's reply.
19:32:36 <DanC> i.e. http://lists.w3.org/Archives/Public/www-tag/2010Jan/0031.html
19:33:59 <DanC> Zakim, pick a victim
19:33:59 <Zakim> Not knowing who is chairing or who scribed recently, I propose DanC
19:34:12 <DanC> Zakim, pick a victim
19:34:12 <Zakim> Not knowing who is chairing or who scribed recently, I propose Ashok_Malhotra
19:34:25 <noah> zakim, who is paying for dinner at the next F2F?
19:34:25 <Zakim> I don't understand your question, noah.
19:34:34 <DanC> ACTION Larry: check whether HTML language reference has been published
19:34:34 <trackbot> Created ACTION-379 - Check whether HTML language reference has been published [on Larry Masinter - due 2010-01-28].
19:34:44 <DanC> action-379 due in 4 months
19:34:44 <trackbot> ACTION-379 Check whether HTML language reference has been published due date now in 4 months
19:34:56 <noah> close ACTION-373
19:34:56 <trackbot> ACTION-373 Convey, re language reference, to encourage the path they've indicated; we can't tell if we're satisifed; we'll stay tuned and comment when drafts become available closed
19:35:01 <DanC> action-379 due 21 may
19:35:01 <trackbot> ACTION-379 Check whether HTML language reference has been published due date now 21 may
19:35:09 <Zakim> -masinter
19:35:11 <Zakim> -noah
19:35:17 <Zakim> -jar
19:35:19 <Zakim> -DanC
19:35:36 <Ashok> rrsagent, pointer?
19:35:36 <RRSAgent> See http://www.w3.org/2010/01/21-tagmem-irc#T19-35-36
19:35:58 <noah> Hmm,10 pending non-trivial actions == approx 5 weeks telcon time.
19:35:59 <DanC> I note there's a list of docs the HTML WG chairs are considering putting a publication question on, and the language reference isn't one of them. http://lists.w3.org/Archives/Public/public-html-wg-announce/2010JanMar/0005.html
19:36:15 <DanC> got a few minutes for a phone call, noah?
19:36:23 <noah> yes, a few.  I call you?
19:36:28 <noah> cell?
19:36:35 <noah> (I mean cell or home)
19:36:53 <DanC> RRSAgent, draft minutes
19:36:53 <RRSAgent> I have made the request to generate http://www.w3.org/2010/01/21-tagmem-minutes.html DanC
19:40:05 <Zakim> -Ashok_Malhotra
19:40:07 <Zakim> TAG_Weekly()1:00PM has ended
19:40:08 <Zakim> Attendees were DKA, noah, Raman, Ashok_Malhotra, +1.781.643.aaaa, jar, masinter, DanC
19:40:21 <noah> Phone dropped?
19:57:45 <DanC> DanC has joined #tagmem
20:04:44 <DanC> Meeting: TAG Weekly
20:04:55 <DanC> Zakim, list participants
20:04:55 <Zakim> sorry, DanC, I don't know what conference this is
20:05:10 <DanC> RRSAgent, draft minutes
20:05:10 <RRSAgent> I have made the request to generate http://www.w3.org/2010/01/21-tagmem-minutes.html DanC
20:05:37 <DanC> Agenda: http://lists.w3.org/Archives/Public/www-tag/2010Jan/0062.html
20:05:50 <DanC> RRSAgent, draft minutes
20:05:50 <RRSAgent> I have made the request to generate http://www.w3.org/2010/01/21-tagmem-minutes.html DanC
20:07:11 <DanC> s|s/0824/xxxx/||
20:08:59 <DanC> s/The continuing/I hear you saying: The continuing/
20:10:14 <DanC> s/got a few minutes for a phone call, noah?//
20:10:20 <DanC> s/yes, a few. I call you?//
20:10:28 <DanC> s/cell?//
20:10:34 <DanC> s/(I mean cell or home)//
20:10:40 <DanC> s/Phone dropped?//
20:10:45 <DanC> RRSAgent, draft minutes
20:10:45 <RRSAgent> I have made the request to generate http://www.w3.org/2010/01/21-tagmem-minutes.html DanC
20:11:19 <DanC> s|yes, a few. I call you?||
20:11:30 <DanC> RRSAgent, draft minutes
20:11:30 <RRSAgent> I have made the request to generate http://www.w3.org/2010/01/21-tagmem-minutes.html DanC
20:12:03 <DanC> s|yes, a few. I call you?||
20:12:23 <DanC> RRSAgent, draft minutes
20:12:23 <RRSAgent> I have made the request to generate http://www.w3.org/2010/01/21-tagmem-minutes.html DanC
20:13:03 <DanC> ScribeOptions: -noEmbedDiagnostics
20:13:05 <DanC> RRSAgent, draft minutes
20:13:05 <RRSAgent> I have made the request to generate http://www.w3.org/2010/01/21-tagmem-minutes.html DanC
20:13:34 <DanC> RRSAgent, make logs public
20:13:39 <DanC> RRSAgent, draft minutes
20:13:39 <RRSAgent> I have made the request to generate http://www.w3.org/2010/01/21-tagmem-minutes.html DanC
20:14:39 <DanC> ScribeOptions: -noEmbedDiagnostics -public
20:14:41 <DanC> RRSAgent, draft minutes
20:14:41 <RRSAgent> I have made the request to generate http://www.w3.org/2010/01/21-tagmem-minutes.html DanC
20:20:32 <DanC> RRSAgent, stop