<Hixie> is there a page that describes the various public-html-* lists?
<Hixie> the equivalent of http://whatwg.org/mailing-list but for the HTML WG?
<MikeSmithX> Hixie: nope
<MikeSmithX> I suppose I should make one
<Hixie> would be nice to link to it from the acknowledgements (see the foot of the spec)
<MikeSmith> Hixie: http://www.w3.org/html/wg/lists/
<Hixie> MikeSmith: thanks
<MikeSmith> Hixie: is that what you had in mind?
<rubys> trackbot, start meeting
<trackbot> Date: 04 February 2010
<cardona507> good morning everyone
<Mark> Mark Foladare is present
<rubys> scribenick: mjs
<MikeSmith> scribe: mjs
First item is action items due February 4th
<trackbot> ACTION-127 -- Maciej Stachowiak to establish process for "official WG response" to other WG's RFC on LC drafts -- due 2010-02-04 -- OPEN
rubys: action-127 - maciej?
mjs: I just sent a rough draft of a proposed policy to the list
masinter: make sure that it is linked from the action
<masinter> not linked from the action, if you say "ACTION-127" in the message, it will get auto-linked
<masinter> otherwise please edit action directly to put in link! Thanks
<masinter> suggest marking it pending review
rubys: should the action still be open?
mjs: remaining steps are to respond to feedback and call to consensus
<trackbot> ACTION-163 -- Michael(tm) Smith to mediaWiki successor for current MoinMoin based wiki -- due 2010-02-04 -- OPEN
rubys: next action on MikeSmith - MediaWiki successor
<rubys> mjs: action is now pending-review
<masinter> please link wiki into action item?
<rubys> action-163 due 10 Feb
<trackbot> ACTION-163 MediaWiki successor for current MoinMoin based wiki due date now 10 Feb
<masinter> links in http://www.w3.org/html/wg/
rubys: next item is proposed publications
rubys: we have links on the
homepage to the proposed drafts
... I realize some may be controversial, we will likely handle this as a Call for Consensus
<MikeSmith> action-163: if systems team has not migrated content from the ESW wiki by Feb 10, I propose we just tell people to move any content they want over manually -- copy/paste -- and then we shut down editing of the old ESW wiki and do all new work at the MediaWiki one
<trackbot> ACTION-163 MediaWiki successor for current MoinMoin based wiki notes added
rubys: I notice that we haven't
talked about html4-diffs
... we should ask Anne to update it so we can publish it as we usually do with the HTML5 draft
masinter: I wonder if anyone has reviewed this...
<masinter> link from http://www.w3.org/html/wg/
<paulc> http://dev.w3.org/html5/html4-differences/ is dated Sep 2009
<masinter> points to http://dev.w3.org/html5/html4-differences/
<MikeSmith> anne, you plan to update the html-diffs doc for the next round of publication?
masinter: the diffs document is old
rubys: we need to ask Anne to update it
paulc: the diffs document is not a useful source of information on changes
rubys: the diffs document has traditionally been updated the week before we publish
<MikeSmith> anne has always gotten the diffs doc updated very quickly and well prior to every new WD publication of the spec
<masinter> I think RDFa and microdata are both out of scope for the committee; if the status of the documents had been updated to make the status clear, that might have been a compromise, but it doesn't look like that isn't happening.
paulc: Larry is dissatisfied with the way the status sections of HTML+RDFa and Microdata got changed
<masinter> HTML+RDFa might be OK, haven't looked again, but Microdata definitely doesn't look right
rubys: next item on the agenda,
calls for proposals that close this week
... there are none
<trackbot> ISSUE-83 -- Use of the dt and dd elements in figure and details content models -- OPEN
rubys: next item on the agenda is
new calls for proposals / calls for consensus this week
... there is one: ISSUE-83
... last I saw, Shelley had removed her remaining objection
... next item on the agenda: issues to move forward on
<trackbot> ISSUE-27 -- @rel value ownership, registry consideration -- OPEN
rubys: ISSUE-27 rel-ownership - looks like we are near consensus, next step might be a Call for Consensus
<Julian> +1 to CfC on this
rubys: can I ask for an opportunity to ask a question?
paulc: in this case we are
effectively taking a dependency on another document
... I want to make sure that when we get consensus we are clear on whether this document would block or help our progress
rubys: certainy as we add more dependencies, the dependencies themselves could impede our progress in the future
masinter: sounds like something that should be visible
<masinter> the URL dependency for example, should have some actions to track
rubys: ISSUE-66 image-analysis seems like we are not quite at consensus, may need counter-proposals
<trackbot> ISSUE-66 -- image analysis heuristics -- OPEN
<trackbot> ISSUE-88 -- Should meta/@content allow a list of languages instead of just a single language? -- OPEN
rubys: next issue is issue-88 content-language-multiple, seems like we may be close to consensus on that
aphillip: hi, this is Addison,
chair of I18N Working Group
... want to ask what it is that we're close to consensus on
aphillip: ah, that's our proposal
rubys: any other questions or comments?
<paulc> summary: new CfC on 27 and 88
rubys: next agenda item: new
issues this week
... no new issues this week
<paulc> summary: Call for counter proposals on 66
rubys: next item on the agenda is
... f2f meeting we have been discussing - at the moment it's on hold
... exploring focus on cross-group coordination
masinter: some ideas on agenda items that might encourage progress
<masinter> if you proposed a sample agenda, it might focus the discussion of "whether to have a meeting in general" to "whether to have a meeting with those agenda items"
paulc: Larry's point is well taken which is that people want to know the return on investment, so having a concrete agenda may help
<masinter> well, if not "concrete" at least "fleshed out" or "proposed"
rubys: next item on the agenda is
... we have some feedback and we need to track that better - proposal is to have a bugzilla component
masinter: I asked for the process document to be expanded and clarified
rubys: my opinion is that a
number of questions will require changes to the document - we
need a way to track that
... Mike: can you set up a bugzilla component for decision policy?
MikeSmith: sure, yeah
rubys: make the component "decision policy"
<paulc> Are the Chairs agreeing to take the existing comments into Bugzilla?
<masinter> it's both a process and policies that affect how the process is being followed
paulc, I can put Larry's comments in bugzilla
<paulc> Thanks, Maciej
rubys: the last discussion is on
licensing - I don't have a quick link but there is a
... of the AC
<masinter> should cross-working group review policy be added? It seems to be related? WHy not merge the two?
rubys: whether Member companies would be willing to accept a more liberal license
<paulc> FAQ on licensing: http://www.w3.org/2010/01/licfaq (possibley Member only)
rubys: next item is scribe for the next meeting...
<MikeSmith> I added a new component called "working group Decision Policy"
masinter: the IRI working group
has been approved
... it's meeting in Anaheim in March
... went to meeting of Unicode core Working Group, got them to agree to participate and help
paulc: Larry, could you send the info on the IETF meeting in March?
rubys: anything else before we
... meeting adjourned
<paulc> We need to generate the minutes
MikeSmith: how do I get the bot to generate the minutes?
<paulc> trackbot, generate minutes
<trackbot> Sorry, paulc, I don't understand 'trackbot, generate minutes'. Please refer to http://www.w3.org/2005/06/tracker/irc for help
<MikeSmith> mjs, "RRSAgent, make minutes"
RSSAgent, make minutes
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/rubys/paulc/ Succeeded: s/issue-81/issue-88/ Succeeded: s/process/process document/ Succeeded: s/process/decision policy/ Found ScribeNick: mjs Found Scribe: mjs Inferring ScribeNick: mjs WARNING: No "Topic:" lines found. WARNING: No "Present: ... " found! Possibly Present: Cooper Cynthia_Shelly Eliot_Graff Hixie J_Voracek Julian Lachy Laura Mark MichaelC Michelangelo Microsoft Mike MikeSmith MikeSmithX ROBOd Radhika_Roy Rich Richard Sam aaaa aabb action-163 anne aphillip aroben aroben_ arronei cardona507 drunknbass_work frankoliiver html-wg joined jstewart2 karl kliehm masinter miketaylr mjs myakura oedipus paul_irish paulc plh plh_ r12a richardschwerdtfe rubys sbublava scribenick summary tlr trackbot wonsuk You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy Regrets: Gregory_Rosmaita Agenda: http://lists.w3.org/Archives/Public/public-html-wg-announce/2010JanMar/0009.html WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 04 Feb 2010 Guessing minutes URL: http://www.w3.org/2010/02/04-html-wg-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]