See also: IRC log
<trackbot-ng> Date: 09 October 2007
<trackbot-ng> Tracking ISSUEs and ACTIONs from http://www.w3.org/2007/xmlsec/Group/track/
<scribe> Scribe: Konrad Lanz
Frederick Hirsch: cancel thanks giving meeting?
<Thomas Roessler> 20 November cancelled
Frederick Hirsch: 20th of November Meeting cancelled
Frederick Hirsch: ... try to have joint session with EXI arrange time to meet
<Thomas Roessler> Juan Carlos Cruellas, you're muted currently, since your line caused significant noise
Frederick Hirsch: meeting thursday and friday, not on saturday
Frederick Hirsch:To whom in xml core do we have to talk to?
Konrad Lanz: Richard Tobin, the guy from IBM and myself ...
<Thomas Roessler> glen marcy
Konrad Lanz: Yes, Glen that's his name.
<Thomas Roessler> question is whether these folks are actually going to attend
<Juan Carlos Cruellas> q
<Zakim> Thomas Roessler, you wanted to ask about speakerphone requirements for TPAC
Konrad Lanz: attend rather by phone than in person ...
<FrederickHirsch> who planning to attend by phone - Konrad, who else?
Ed Simon:couldn't we use skype or similar?
<Thomas Roessler> my earlier attempts to use skype for that went pretty badly
Frederick Hirsch:Ed are you planing to be in boston or to call in?
Ed Simon: planing to be there ...
Thomas Roessler: some people might have conflicts with AC meetings ...
Frederick Hirsch: everyone please indicate time constraints
Juan Carlos Cruellas: ESI meeting, difficult to be there on Wednesday
Juan Carlos Cruellas; might not be in boston, maybe arrive thursday and friday
Juan Carlos Cruellas: might not be in boston, maybe arrive thursday and friday
Thomas Roessler: reservations ASAP
... hotel rooms unpleasently expensive at that time
<Thomas Roessler> http://www.w3.org/2007/09/18-xmlsec-minutes
<Thomas Roessler> http://www.w3.org/2007/09/11-xmlsec-minutes
RESOLUTION: Minutes approved.
<Thomas Roessler> the report and minutes are publicly visible, but we're playing a bit of security by obscurity right now. ;-)
Frederick Hirsch: do we want comments on the public or the member list?
Frederick Hirsch: let's use member list
<Thomas Roessler> anyway, don't block on me till you close one ;)
ACTION 74 open
ACTION 81 open
Frederick Hirsch: need to figure out if sections match
<Thomas Roessler> that's yet another issue
ACTION 82 closed
ACTION 83 closed
ACTION 90 closed
ACTION 91 closed
ACTION 92 closed
ACTION 93 open relates to xml:base clarification at the interop
ACTION 94 closed
ACTION 95 open, check back with sean
ACTION 96 closed
two actions are needed one conecrning square brackets "[ ]" in xpointers, the other one concerning xml:base
<Thomas Roessler> I think the concrete step is an agenda+ for the next call...
<Thomas Roessler> PROPOSED ACTION: konrad to raise [] issue on public list
<Thomas Roessler> ACTION: konrad to raise [] issue on public list [recorded in http://www.w3.org/2007/10/09-xmlsec-minutes.html#action01]
<trackbot-ng> Created ACTION-97 - Raise [] issue on public list [on Konrad Lanz - due 2007-10-16].
Frederick Hirsch: generate test cases for dname
issue?
... we need to be able to generate our interop report
<FrederickHirsch> Resolve imiplementation issues for DNAME testing
<FrederickHirsch> PROPOSED ACTION: Record open issues and actions resulting from interop testing
Konrad Lanz: escaping of = vs \=
<Thomas Roessler> PROPOSED ACTION: konrad to send e-mail to summarize dname related interop issue to public list
<scribe> ACTION: Konrad Lanz to send e-mail to summarize dname related interop issue to public list [recorded in http://www.w3.org/2007/10/09-xmlsec-minutes.html#action02]
<trackbot-ng> Created ACTION-98 - Send e-mail to summarize dname related interop issue to public list [on Konrad Lanz - due 2007-10-16].
<FrederickHirsch> PROPOSED ACTION: Record open issues and actions resulting from interop testing
<Thomas Roessler> ACTION: cruellas to review interop report to record open issues and actions resulting from interop testing [recorded in http://www.w3.org/2007/10/09-xmlsec-minutes.html#action03]
<trackbot-ng> Created ACTION-99 - Review interop report to record open issues and actions resulting from interop testing [on Juan Carlos Cruellas - due 2007-10-16].
<Thomas Roessler> http://lists.w3.org/Archives/Public/public-xmlsec-maintwg/2007Oct/0000.html
Frederick Hirsch: no change
<FrederickHirsch> http://lists.w3.org/Archives/Member/member-xmlsec-maintwg/2007Oct/0004.html
Frederick Hirsch: drafted report, fairly brief,
comments on member list
... try to get something more publicly readable
... report http://lists.w3.org/Archives/Public/public-xmlsec-maintwg/2007Oct/0000.html
Juan Carlos Cruellas: access to conclusions instead of interop report
Frederick Hirsch: once we are ready this will be published
Thomas Roessler: waiting for comments ...
... are publicly visible but not prominent
Juan Carlos Cruellas: will point to those places
<Thomas Roessler> I'd see the report as the first step toward getting to a charter draft.
Konrad Lanz: maybe we should start some discussion on the general direction could be updating vs. refactoring
Frederick Hirsch: need to produce a red line for xml-core
<Thomas Roessler> they're meeting tomorrow
<Zakim> Thomas Roessler, you wanted to note that workshop report is intended to be published and to
Thomas Roessler: need two answers ...
... 1 . are we right on what we assume
<FrederickHirsch> does xml core agree with analysis - timing for when to update document
Thomas Roessler: 2. what is the timescale for
updating c14n1.1
... discussion on c14n 1.1
Konrad Lanz: will try to pull c14n 1.1 to front of core agenda
Frederick Hirsch: maybe private contact to
chair of core
Frederick Hirsch: Best Practices write up
... don't know how well the wiki is working
ed: likes the wiki
Frederick Hirsch: shall we switch to a doc?
Konrad Lanz: use wiki to write in sections and chapter style
Thomas Roessler: could you provide a script for conversion
Konrad Lanz: thought more about plain text editiiong in wiki and to to the markup later
<Thomas Roessler> +1 to keeping stuff in the wiki for the moment, reviewing it, and then having somebody (not me) edit it. ;-)
Frederick Hirsch: cvs and do documents there?
<Bruce Rich:> can someone provide link for wiki?
Frederick Hirsch: we should have a best practices section there
http://www.w3.org/2007/xmlsec/Group/Overview.html#wiki
<Konrad Lanz:lost call, dialing in again
Frederick Hirsch: we need to get it on the list
Juan Carlos Cruellas: agree there are no volunteers now, defer volunteer issue ...
Frederick Hirsch: report not in that detail
Konrad Lanz: use position papers as best practices input
Frederick Hirsch: use the mailing list to point
the to the relavant information for best practices
... decryption transform no interest
Frederick Hirsch: what are we going to do with this?
Thomas Roessler: we are supposed to fix the
inheritance and xpointers as in xmldsig
... if we have time and energy and go to last call
... decryption transform is dealing as exceptions specified as xpointers
... how much of this remains useful looking at the state of xpointers
... spec in bad shape due to it's heavy use of xpointers
... maybe, fixing needs refactoring and is to be chartered in another
group
Frederick Hirsch: is there another path that deprecates it
Thomas Roessler: it's possible to rescind a specification
Konrad Lanz: maybe just add a note that
warns
... that xpointer is a WD
... just do the quick and dirty fixes
Thomas Roessler: two aspects, doing minimal fixes ...
second it's wired that it needs xpointer and hence redesign ...
can someone identify what needs to be done ...
we have done part of it but not all of it ...
one or two edits have to be finished ...
Frederick Hirsch: 1. figure out what has to be done
2. what are the issues and add a warning
hal: what about doing best practices stuff in
the next working group ...
... maybe not part of this working group
<Zakim> Thomas Roessler, you wanted to note that our charter does list best practices
Thomas Roessler: we are chartered to do best
practices
... maybe a good idea to start as long as it is fresh
<FrederickHirsch> +1 to Thomas Roessler
Frederick Hirsch: how would chartering for new group work
Thomas Roessler: posibility to recharter
<Thomas Roessler:> ... new group can use work of this group
Thomas Roessler: split up between maintenance
work
... and new work
... documents should be able to transition
... from one group to another
... no best practices REC material in this group
... other groups can use the work we can use here
<FrederickHirsch> note this group does produce REC for signature revision.
<FrederickHirsch> (PER)
<Thomas Roessler> ok, to be totally clear:
<Thomas Roessler> - no rec-track best practices in this charter
<Thomas Roessler> - PER for dsig-core
<Thomas Roessler> - rec-track work for decryption transform
<Thomas Roessler> (just to set the record straight)
<Thomas Roessler> adjourned