[w3c sml][agenda] 2008-10-16 SML

Kirk/Kumar, it appears you may be scribing this week.



Chair: when sending out an agenda, use following format

  [w3c sml][agenda] yyyy-mm-dd SML          in subject of email ([agenda]

agreed to, rest chair's convention)

Chair: when sending out an updated agenda, use following format, "n" =

update number, 1st update == 2, etc.

  [w3c sml][agenda][ver n] yyyy-mm-dd SML   in subject of email ([agenda]

[ver n] agreed to, rest chair's convention)

Scribe: read entire agenda, I restructured it so your "to do"s around the

scribe list are time-sequenced

  i.e. less to remember



The phone number to use for the SML WG teleconference is documented on the

WG's administrative home page:

http://www.w3.org/XML/Group/SML#phone



Participants are invited to join IRC channel, as documented on the WG's

administrative home page:

http://www.w3.org/XML/Group/SML#irc



Teleconference Time and Length (two hours)

Pacific   11 AM -  1 PM

Mountain  12 PM -  2 PM

Central    1 PM -  3 PM

Eastern    2 PM -  4 PM

UK         7 PM -  9 PM

Paris      8 PM - 10 PM

Beijing    2 AM -  4 AM (sorry)



Publication moratorium for the rest of this year:

 13 October, 12pm ET: Deadline for publication requests

                      before moratorium

 16 October:      Last publications before moratorium

 17 - 26 October: No publications

 27 October:      Publications resume



18 December, 12pm ET: Deadline for publication requests

                      before moratorium

22 December: Last publications before moratorium

23 December - 1 January: No publications

 2 January 2009: Publications resume



Proposed Agenda:



1. Roll call (present/regrets/absent)



2. Selection of Scribe based on list below

   New scribes see:

   - Scribe Quick Start Guide

http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/scribe/scribedoc.htm

   - Scribe FAQ

http://lists.w3.org/Archives/Member/member-ws-policy/2006Oct/0001.html

   - Instructions (steps "n-...") at the end of this agenda for reviewing

and sending out minutes



   - PLEASE make any new Actions fully self-describing so they do not

require the minutes as context.

     We found it awkward in the past to require going back to the minutes

for context.



Last Scribe Date        Member Name         Regrets pending

2008-05-22              Lynn, James         Until further notice

2008-07-10              McCarthy, Julia     Until further notice

2008-09-11              Wilson, Kirk

2008-09-18              Smith, Virginia     10/16

2008-09-25              Kumar, Pandit

2008-10-02              Gao, Sandy

Exempt                  Arwe, John

Exempt                  Dublish, Pratul

Exempt                  MSM                 10/9 10/16



3. Approval of minutes from previous meeting(s):

   - http://www.w3.org/XML/SML/#records

   - 10/02 http://lists.w3.org/Archives/Public/public-sml/2008Oct/att-0006/20081002-sml-minutes.html



4. Review Schema WG's resolution for the following bugs that were opened by our WG



        http://www.w3.org/Bugs/Public/show_bug.cgi?id=5153

       http://www.w3.org/Bugs/Public/show_bug.cgi?id=5155



5. Action items: goes faster if you update yours before the meeting...

   http://www.w3.org/2005/06/tracker/sml/



6. Test case discussion.

   Review updated test plan draft. http://lists.w3.org/Archives/Public/public-sml/2008Oct/att-0007/sml-interop-test-plan.pdf



   SML and SML-IF interop test suite using the COSMOS suite as the starting point - discuss add/cuts to COSMOS suite



n-5. Review bugs with no keywords or target (none as of this writing!)



n-4. Review and attempt to reach consensus on other non-editorial bugs

targeted for the next draft.



     Within each cluster, typically we look at them in this order

           "decided" (after the 2-week grace period for responses ends)

           "needsReview" (either we have consensus, it's no longer

needsReview, or the editors need to re-spin the proposed text)

           "hasProposal"

           "externalComments + reviewerNotSatisfied" - even if closed,

e.g. 5543, 5562

           "externalComments + neither( reviewerNotSatisfied ,

reviewerSatisfied )" aka "reach out again?"

           others



n-3. Scribe: update scribe list below in this meeting's minutes, for use

in the next meeting's agenda:

   Update the list below and sort it (LRU), leaving people who will be out

for an extended period near the bottom

   to keep the names of draftees for the current meeting near the top, so

when the next agenda goes out people

   will know if their name is at or near the top of the list to scribe

next.



Last Scribe Date        Member Name         Regrets pending

2008-05-22              Lynn, James         Until further notice

2008-07-10              McCarthy, Julia     Until further notice

2008-09-11              Wilson, Kirk

2008-09-18              Smith, Virginia     10/9

2008-09-25              Kumar, Pandit

2008-10-02              Gao, Sandy

Exempt                  Arwe, John          10/9

Exempt                  Dublish, Pratul

Exempt                  MSM                 10/9 10/16



n-2. Scribe: follow the steps in the Scribe Quick Start Guide through

"Generate minutes"

   http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/scribe/scribedoc.htm

   Also issue the command "rrsagent, make log public" since we are a

public workgroup.



   DO NOT use tools that significantly change the source html, like Word,

to do your editing.

   Those tools make compare tools to sanity check the scribe's edits

unusable even though it

   renders fine visually (even here, some like Word remove W3C style

sheets so it renders

   with subtle differences).



n-1. Scribe: (optional, but most often followed)

   Send the original and updated minutes to the meeting chair as an

editorial check before

   sending to the full list.  Assume the chair will use a compare tool.



n. Scribe: send the minutes to the public mailing list

   After the meeting, follow the conventions we have agreed on within the

wg to help

  people search the email archives more effectively, namely:

    [w3c sml][minutes] yyyy-mm-dd SML     in subject of email ([minutes]

agreed to, rest chair's convention)

  As with agendas, if minutes are updated include a [ver n] "tag" as well.



----

n+1. Chair

     After meeting, update good standing list

Received on Wednesday, 15 October 2008 19:41:13 UTC