Minutes, 22 Feb 2007 Web Services Description WG telcon

"Jonathan Marsh" <[email protected]>
Newsgroups gmane.comp.web.services.description
Message-ID <016601c756bc$69825ce0$1501010a@DELLICIOUS>
Enclosed.

 

Jonathan Marsh -  <http://www.wso2.com> http://www.wso2.com -
<http://auburnmarshes.spaces.live.com> http://auburnmarshes.spaces.live.com
20070222-ws-desc-minutes.html (text/html, 22.9 KB)
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html lang='en' xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
  <meta name="generator" content=
  "HTML Tidy for Linux/x86 (vers 12 April 2005), see www.w3.org" />

  <title>Web Services Description WG telcon -- 22 Feb 2007</title>
  <link type="text/css" rel="STYLESHEET" href=
  "http://www.w3.org/StyleSheets/base.css" />
  <link type="text/css" rel="STYLESHEET" href=
  "http://www.w3.org/StyleSheets/public.css" />
  <link type="text/css" rel="STYLESHEET" href=
  "http://www.w3.org/2004/02/minutes-style.css" />
  <meta content="SV_MEETING_TITLE" name="Title" />
  <meta content="text/html; charset=us-ascii" http-equiv=
  "Content-Type" />
</head>

<body>
  <p><a href="http://www.w3.org/"><img src=
  "http://www.w3.org/Icons/w3c_home" alt="W3C" border="0" height=
  "48" width="72" /></a></p>

  <h1>Web Services Description Working Group telcon</h1>

  <h2>22 Feb 2007</h2>

  <p>See also: <a href=
  "http://www.w3.org/2007/02/22-ws-desc-irc">IRC log</a> (partial)</p>

  <h2><a name="attendees" id="attendees">Attendees</a></h2>

  <div class="intro">
    <dl>
<dt>Present</dt>
<dd>Roberto Chinnici, Sun Microsystems</dd>
<dd>Paul Downey, British Telecommunications</dd>
<dd>Youenn Fablet, Canon</dd>
<dd>Jacek Kopecky, DERI Innsbruck at the Leopold-Franzens-Universität Innsbruck, Austria</dd>
<dd>Amelia Lewis, TIBCO</dd>
<dd>Philippe Le Hegaret, W3C</dd>
<dd>Jonathan Marsh, Co-chair/WSO2</dd>
<dd>Monica Martin, Sun Microsystems</dd>
<dd>Jean-Jacques Moreau, Canon</dd>
<dd>Gilbert Pilz, BEA Systems</dd>
<dd>Tony Rogers, Co-chair/Computer Associates</dd>
<dd>Asir Vedamuthu, Microsoft</dd>

      <dt>Regrets</dt>
<dd>Arthur Ryman, IBM</dd>
      <dt>Chair</dt>

      <dd>Jonathan</dd>

      <dt>Scribe</dt>

      <dd>JacekK</dd>
    </dl>
  </div>

  <h2>Contents</h2>

  <ul>
    <li>
      <a href="#agenda">Topics</a>

      <ol>
        <li><a href="#item01">approval of minutes</a></li>
        <li><a href="#item02">action item review</a></li>
        <li><a href="#item03">administrivia</a></li>
        <li><a href="#item04">issue CR147</a></li>
        <li><a href="#item05">CR153</a></li>
        <li><a href="#item06">CR issue 21</a></li>
        <li><a href="#item07">CR154</a></li>
        <li><a href="#item08">adjuncts 6.8.1.1</a></li>
        <li><a href="#item09">implementation status summary</a></li>
        <li><a href="#item10">publication status and plan</a></li>
      </ol>
    </li>

    <li><a href="#ActionSummary">Summary of Action Items</a></li>
  </ul>
  <hr />

  <div class="meeting">

	<p class='irc'>&lt;<cite>scribe</cite>&gt;: JacekK</p>

	<h3 id="item01">approval of minutes</h3>
	
	<p class='phone'><strong class='resolution'>RESOLVED: minutes of last week approved</strong></p>

	<h3 id="item02">action item review</h3>
	<pre>Review of Action items [.1].

?         2006-09-21: Jonathan to check periodically that SPARQL has 
                      added schemaLocation.
?         2007-01-04: Paul to report back on which test cases in the 
                      WSDL test suite fail the basic patterns, with
                      suggestions on how to address the issues.
?         2007-01-11: Jean-Jacques to provide more analysis on how 
                      difficult it would be deal with a Policy that 
                      only contains an MTOM policy assertion
DONE [.3] 2007-02-15: Jonathan to forward his WSDL1.1 identifiers 
                      Comments
DONE      2007-02-15: Jonathan to drum up a WS-A reviewer off-list
DONE [.4] 2007-02-15: Jonathan to check whether the test suite needs 
                      to be fixed with regards to SOAP Response and 
                      action

Current Editorial Action Items

Note: Editorial AIs associated with LC issues recorded at [.2].

[.1] http://www.w3.org/2002/ws/desc/#actions
[.2] http://www.w3.org/2002/ws/desc/5/cr-issues/actions_owner.html
[.3] http://lists.w3.org/Archives/Public/www-ws-desc/2007Feb/0118.html
[.4] http://lists.w3.org/Archives/Public/www-ws-desc/2007Feb/0158.html</pre>

<p class='phone'><cite>Jonathan:</cite> we may not need to review the WS-A spec formally in this WG, due to the overlap with WS-A<br/>
	... I fixed the test suite wrt: soap action on GET</p>
	<p class='phone'><cite>youenn:</cite> you broke put and didn't fix delete</p>
	<p class='phone'><cite>jjm:</cite> XMLP asked us to review the one-way MEP...</p>
	<p class='phone'><cite>Jonathan:</cite> I believe we did that<br/>
	... Jonathan: I may want to check the delivery of one-way MEP comments to XMLP</p>
	<p class='irc'>&lt;<cite>Jonathan</cite>> <a href="http://lists.w3.org/Archives/Public/xmlp-comments/2007Feb/0000.html">http://lists.w3.org/Archives/Public/xmlp-comments/2007Feb/0000.html</a></p>
	<p class='phone'><cite>Jonathan:</cite> done<br/>
	... will fix the PUT and DELETE</p>

	<h3 id="item03">administrivia</h3>

	<h3 id="item04">issue CR147</h3>
	<p class='phone'><cite>Jonathan:</cite> Jonathan: still waiting for the TAG to reply to our question</p>
	<p class='phone'><cite>Jacek:</cite> they will discuss it on Monday, probably</p>
	<p class='phone'><cite>Jonathan:</cite> Jonathan: we'll revisit it next week, then</p>

	<h3 id="item05">CR153</h3>
	<p class='phone'><cite>Jonathan:</cite> Jonathan: anybody against changing to http://www.w3.org/ns/wsdl or wsdl2?</p>
	<p class='phone'><cite>Jacek:</cite> I like wsdl2</p>
	<p class='phone'><cite>jjm:</cite> I like the change</p>
	<p class='phone'><cite>Jacek:</cite> would we also change the documents to version 2, not 2.0?</p>
	<p class='phone'><cite>Jonathan:</cite> why?</p>
	<p class='phone'><cite>Roberto:</cite> why even 2?</p>
	<p class='phone'><cite>gpilz:</cite> the 2 helps people distinguish from wsdl1.1</p>
	<p class='phone'><cite>Jonathan:</cite> without '2', we make a political statement that WSDL 2.0 is the one true version</p>
	<p class='phone'><cite>Jacek:</cite> if we adopt /wsdl and there's wsdl3, would we have /wsdl and then /wsdl3?</p>
	<p class='phone'><cite>Jonathan:</cite> that's a very unlikely scenario<br/>
	...most new things can be extensions</p>
	<p class='phone'><cite>Roberto:</cite> policy has /ns/policy with no version</p>
	<p class='phone'><cite>monica:</cite> we could ask the W3C about how they plan to handle future versions</p>
	<p class='phone'><cite>Jonathan:</cite> some namespaces have RDDL sets of links<br/>
	... Jonathan: next version would give us the question again, there's a central authority on this /ns/</p>
	<p class='phone'>chad, question: namespace<br/>
	... option 0: /2006/01/wsdl<br/>
	... option 1: /ns/wsdl<br/>
	... option 2: /ns/wsdl2<br/>
	... option 3: /ns/wsdl20<br/>
	... option 4: /ns/wsdl2.0</p>
	<p class='irc'>&lt;<cite>Roberto</cite>> are there precedents for /ns/wsdl2.0 ?</p>
	<p class='phone'><cite>TonyR:</cite> wsdl20 is like the number twenty</p>
	<p class='phone'><cite>Jonathan:</cite> but it's similar to the shortname in /TR/</p>
	<p class='irc'>&lt;<cite>jjm</cite>> vote: 1</p>
	<p class='irc'>&lt;<cite>JacekK</cite>> vote: 2, 3, 0</p>
	<p class='irc'>&lt;<cite>TonyR</cite>> vote: 2,1,0,4,3</p>
	<p class='irc'>&lt;<cite>plh</cite>> vote: 2, 1, 3</p>
	<p class='irc'>&lt;<cite>gpilz</cite>> vote: 2, 3, 4, 1, 0</p>
	<p class='irc'>&lt;<cite>Roberto</cite>> vote: 1, 4, 0, 3</p>
	<p class='irc'>&lt;<cite>youenn</cite>> vote: 1,2</p>
	<p class='irc'>&lt;<cite>Jonathan</cite>> vote: 1, 2</p>
	<p class='irc'>&lt;<cite>jkaputin</cite>> vote: 1, 2, 3</p>
	<p class='phone'>chad, count</p>
	<p class='irc'>&lt;<cite>chad:</cite>> Question: namespace<br/>
	... Option 0: /2006/01/wsdl (0)<br/>
	... Option 1: /ns/wsdl (5)<br/>
	... Option 2: /ns/wsdl2 (4)<br/>
	... Option 3: /ns/wsdl20 (0)<br/>
	... Option 4: /ns/wsdl2.0 (0)<br/>
	... 10 voters: alewis abstained,gpilz (2,3,4,1,0),JacekK (2,3,0),jjm (1),jkaputin (1,2,3),Jonathan (1,2),plh (2,1,3),Roberto (1,4,0,3),TonyR (2,1,0,4,3),youenn (1,2)<br/>
	... Round  1: Count of first place rankings.<br/>
	... Candidate 1 is elected.</br>
	... Winner is option 1 - /ns/wsdl</p>
	
	<p class='irc'>&lt;<cite>monica</cite>>  vote: 1, 4, 0, 3</p>
	<p class='phone'>a straw-poll indicates that /ns/wsdl is preferred by the WG</p>
	<p class='irc'>&lt;<cite>pauld</cite>> chad, option 5: /2007/01/wsdl</p>
	<p class='irc'>&lt;<cite>pauld</cite>> thinks /ns/* sucks</p>
	<p class='irc'>&lt;<cite>Jonathan</cite>> chad, options</p>
	<p class='irc'>&lt;<cite>chad</cite>> Question: namespace<br/>
	... Option 0: /2006/01/wsdl (0)<br/>
	... Option 1: /ns/wsdl (6)<br/>
	... Option 2: /ns/wsdl2 (4)<br/>
	... Option 3: /ns/wsdl20 (0)<br/>
	... Option 4: /ns/wsdl2.0 (0)<br/>
	... Option 5: /2007/01/wsdl (0)</p>
	
	<p class='phone'><cite>Jonathan:</cite> it seems people are interested in moving away from dated form</p>
	<p class='phone'><cite>TonyR:</cite> a bit of history is good for you</p>
	<p class='phone'><cite>plh:</cite> the tools will remember the dates easily</p>
	<p class='phone'><cite>pauld:</cite> I like the dated thing in face of multiple versions<br/>
	... typing it, I'm happy to use the date</p>
	<p class='phone'><cite>Jonathan:</cite> I prefer without date because it's not just a namespace, but other identifiers are based on it and I tend to type those so it's easier</p>
	<p class='phone'><cite>gpilz:</cite> those URIs might not even change between versions</p>
	<p class='irc'>&lt;<cite>pauld</cite>> it's "what colour are the bicycle sheds"</p>
	<p class='irc'>&lt;<cite>JacekK</cite>> vote: 0, 3, 2
	<p class='irc'>&lt;<cite>asir</cite>> vote: 1, 2</p>
	<p class='irc'>&lt;<cite>asir</cite>> chad, options<br/>
	<p class='irc'>&lt;<cite>chad</cite>> Question: namespace<br/>
	... Option 0: /2006/01/wsdl (1)<br/>
	... Option 1: /ns/wsdl (7)<br/>
	... Option 2: /ns/wsdl2 (3)<br/>
	... Option 3: /ns/wsdl20 (0)<br/>
	... Option 4: /ns/wsdl2.0 (0)<br/>
	... Option 5: /2007/01/wsdl (0)</p>

	<p class='irc'>&lt;<cite>pauld</cite>> <a href="http://en.wikipedia.org/wiki/Wikipedia:Avoid_Parkinson's_Bicycle_Shed_Effect">http://en.wikipedia.org/wiki/Wikipedia:Avoid_Parkinson's_Bicycle_Shed_Effect</a></p>
	<p class='phone'><cite>pauld:</cite> without versioning, we just pick, but expecting more versions, we might have a hard time with /ns/wsdl</p>
	<p class='irc'>&lt;<cite>JacekK</cite>> vote: 2, 3, 0
	<p class='irc'>&lt;<cite>jjm</cite>> vote: 1</p>
	<p class='irc'>&lt;<cite>jjm</cite>> votes: 1
	<p class='irc'>&lt;<cite>asir</cite>> vote: 1</p>
	<p class='irc'>&lt;<cite>asir</cite>> chad, options</p>
	<p class='irc'>&lt;<cite>chad</cite>> Question: namespace<br/>
	... Option 0: /2006/01/wsdl (0)<br/>
	... Option 1: /ns/wsdl (7)<br/>
	... Option 2: /ns/wsdl2 (4)<br/>
	... Option 3: /ns/wsdl20 (0)<br/>
	... Option 4: /ns/wsdl2.0 (0)<br/>
	... Option 5: /2007/01/wsdl (0)</p>
	
	<p class='irc'>&lt;<cite>pauld</cite>> vote: 5</p>
	<p class='irc'>&lt;<cite>plh</cite>> vote: 1</p>
	<p class='irc'>&lt;<cite>pauld</cite>> vote: 5, 0</p>
	<p class='phone'><cite>Jonathan:</cite> any objections to changing our namespace(s) to http://www.w3.org/ns/wsdl</p>
	<p class='irc'>&lt;<cite>gpilz</cite>> vote: 5</p>

	<p class='irc'>&lt;<cite>asir</cite>> chad, options</p>
	<p class='irc'>&lt;<cite>chad</cite>> Question: namespace<br/>
	... Option 0: /2006/01/wsdl (0)<br/>
	... Option 1: /ns/wsdl (8)<br/>
	... Option 2: /ns/wsdl2 (2)<br/>
	... Option 3: /ns/wsdl20 (0)<br/>
	... Option 4: /ns/wsdl2.0 (0)<br/>
	... Option 5: /2007/01/wsdl (2)</p>
	
	<p class='phone'><strong class='resolution'>RESOLVED: namespace changed to http://www.w3.org/ns/wsdl</strong></p>
	<p class='phone'><cite>Jonathan:</cite> issue CR153 closed</p>

	<h3 id="item06">CR issue 21</h3>
	<p class='phone'><cite>Jonathan:</cite> this will be bundled with 147</p>
	<p class='irc'>&lt;<cite>pauld</cite>> it's a configuration over convention</p>

	<h3 id="item07">CR154</h3>

	<p class='irc'>&lt;<cite>Jonathan</cite>> <a href="http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?content-type=text/html;%20charset=utf-8#InterfaceMessageReference-1205002">http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?content-type=text/html;%20charset=utf-8#InterfaceMessageReference-1205002</a></p>
	<p class='phone'><cite>Jonathan:</cite> seems that the assertion can be coded in the schema</p>
	<p class='phone'><cite>pauld:</cite> but this duplication is harmless</p>
	<p class='phone'><cite>Jonathan:</cite> this assertion would not surface from the validator because schema validation would reject it earlier</p>
	<p class='phone'><cite>Jonathan:</cite> and it'd be an easy fix</p>
	<p class='phone'><cite>Roberto:</cite> +1</p>
	<p class='phone'><cite>jkaputin:</cite> +1</p>
	<p class='phone'><strong class='resolution'>RESOLUTION: assertion markup around this assertion to be removed, and similarly the new corresponding assertion around interface faults, just added</strong></p>

	<h3 id="item08">adjuncts 6.8.1.1</h3>
	<p class='irc'>&lt;<cite>Jonathan</cite>> <a href="http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20-adjuncts.html?content-type=text/html;%20charset=utf-8#_http_operation_location_cited_ser">http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20-adjuncts.html?content-type=text/html;%20charset=utf-8#_http_operation_location_cited_ser</a></p>
	<p class='phone'><cite>Jonathan:</cite> should offensive characters in the template get encoded together with the filled-in values?<br/>
	... Jonathan: some more confusion in the text found (double negatives)<br/>
	... Jonathan: first part of the fix - move the bullets with assertions in 6.8.1.1 up front<br/>
	... Jonathan: and removing NOT from second bullet of current second bullet</p>
	<p class='phone'><cite>Jacek:</cite> NOT is not a RFC2119 keyword, right?</p>
	<p class='phone'><cite>Jonathan:</cite> and then the IRI is transcoded into URI<br/>
	... the RFC says that some characters SHOULD be encoded - this impacts us<br/>
	... Jonathan: canon and wso2 are planning to honor that SHOULD</p>
	<p class='phone'><cite>youenn:</cite> RFC2396, sec 3.3 says & is allowed in path<br/>
	... ... and ; = ? / are reserved</p>
	<p class='phone'><cite>Jonathan:</cite> maybe we should move this to email, we need a number of double-checks<br/>
	... about semicolon, equals, ampersand...<br/>
	... Jonathan: and {query parameter separator}</p>
	<p class='phone'><cite>Jacek:</cite> the query parameter separator is harmful in query</p>
	<p class='phone'><cite>Jonathan:</cite> I feel we just need to drop the first subbulet of the second bullet</p>

	<p class='phone'><cite>Jonathan:</cite> recapitulation:<br/>
	... move the 4th and 5th bullets up, remove the NOT from the second subbulet of second bullet<br/>
	... Jonathan: remove first subbulet of second bullet<br/>
	... Jonathan: remove ; and = from the remaining subbullet<br/>
	... add &amp; there</p>

	<a name="action00" id="action00"></a>
    <p class='irc'><strong>ACTION:</strong> Jonathan to put the proposal on the list for us to double-check.</p>

    <p class='phone'><cite>Jonathan:</cite> we'll take this to the list<br />
    ... other issues? Youenn may have had one</p>

    <p class='phone'><cite>youenn:</cite> it's about the query
    parameter separator value, which may be anything</p>

    <p class='phone'><cite>Jonathan:</cite> yes, but what if it's
    something that interacts with the encoding algorithm?<br />
    ... so should we restrict the values to something more
    manageable, like {';', '&amp;'}</p>

    <p class='phone'><cite>youenn:</cite> maybe a SHOULD
    restriction to the two could be sufficient</p>

    <p class='phone'><cite>Jonathan:</cite> e.g. # would not be a
    good query param separator<br />
    ... how much do we want to keep people from hanging
    themselves?<br />
    ... we can come up with a list of harmless characters, and even
    put it in schema</p><a name="action01" id="action01"></a>

    <p class='irc'>&lt;<cite>scribe</cite>&gt;
    <strong>ACTION:</strong> Jonathan to figure out what characters
    can be used as query separators without causing harm [recorded
    in <a href=
    "http://www.w3.org/2007/02/22-ws-desc-minutes.html#action01">http://www.w3.org/2007/02/22-ws-desc-minutes.html#action01</a>]</p>

    <p class='phone'>people happy with the direction</p>

    <p class='phone'><cite>Jonathan:</cite> any other issues?</p>

    <p class='phone'><cite>jkaputin:</cite> I had one<br />
    ... on the schema, about #any, #other, and it still has
    features and properties?</p>

    <p class='irc'>&lt;<cite>monica</cite>&gt; there is an
    issue</p>

    <p class='irc'>&lt;<cite>Jonathan</cite>&gt; <a href=
    "http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.xsd">
    http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.xsd</a></p>

    <p class='phone'><cite>Jonathan:</cite> the editor's copy
    doesn't have f&amp;p</p>

    <p class='irc'>&lt;<cite>youenn</cite>&gt; <a href=
    "http://lists.w3.org/Archives/Public/uri/2007Feb/0006.html">http://lists.w3.org/Archives/Public/uri/2007Feb/0006.html</a></p>

    <p class='phone'><cite>youenn:</cite> still on the URI
    encoding, people are talking about it in the W3C URI list</p>

    <p class='phone'><cite>Jonathan:</cite> do you think they say
    something that we could use?</p>

    <p class='phone'><cite>youenn:</cite> it'd be good to have
    consensus with them</p>

    <p class='phone'><cite>Jonathan:</cite> we can send a summary
    of our proposal to them</p><a name="action02" id=
    "action02"></a>

    <p class='irc'>&lt;<cite>scribe</cite>&gt;
    <strong>ACTION:</strong> Jonathan to send a summary of our URI
    templating text to the URI list [recorded in <a href=
    "http://www.w3.org/2007/02/22-ws-desc-minutes.html#action02">http://www.w3.org/2007/02/22-ws-desc-minutes.html#action02</a>]</p>

    <h3 id="item09">implementation status summary</h3>

    <p class='phone'><cite>Jonathan:</cite> we're getting closer to
    completion<br />
    ... all green on interchange results<br />
    ... no results for LocationTemplate-2G</p>

    <p class='phone'><cite>youenn:</cite> working on that</p>

    <p class='phone'><cite>Jonathan:</cite> ... few reds expected
    to remain<br />
    ... all-green would assure us that no new issues should be
    coming<br />
    ... results for validation should probably be refreshed before
    director's call</p>

    <p class='phone'><cite>youenn:</cite> some of the results may
    stay red in PR</p>

    <p class='phone'><cite>Jonathan:</cite> director's call should
    come within 10 days after our vote to move to PR</p>

    <p class='phone'><cite>jkaputin:</cite> we may have better
    results</p>

    <p class='phone'><cite>Jonathan:</cite> msg-level tests are the
    main thing to focus on now</p>

    <h3 id="item10">publication status and plan</h3>

    <p class='phone'><cite>jjm:</cite> editorial items
    implemented</p>

    <p class='phone'><cite>Roberto:</cite> have problems with
    CVS</p>

    <p class='phone'><cite>Jonathan:</cite> we should have
    everything done before we vote for PR next week<br />
    ... renumbering assertions?</p>

    <p class='phone'><cite>JacekK:</cite> where do the assertion
    IDs show up?</p>

    <p class='phone'><cite>Jonathan:</cite> in the summary,
    fragment-id's, and test suite in validation<br />
    ... two numbering schemes - token, then number or a coded
    number</p>

    <p class='phone'><cite>gpilz:</cite> do we have a proposal for
    renumbering?</p>

    <p class='phone'><cite>Jonathan:</cite> arthur came up with a
    new system</p>

    <p class='phone'><cite>jkaputin:</cite> consistency would be
    good</p>

    <p class='phone'><cite>Jonathan:</cite> the question is about
    who does it</p>

    <p class='phone'><cite>JacekK:</cite> don't think they're
    prominent enough that they need to be changed</p>

    <p class='phone'><cite>Jonathan:</cite> the question is whether
    we have somebody to do it<br />
    ... if we don't care, let's drop this</p>

    <p class='phone'><cite>jkaputin:</cite> it'd be good to have
    the IDs identify a section in the spec</p>

    <p class='phone'><cite>Jonathan:</cite> the assertion ID is a
    fragment ID, direct link<br />
    ... I'll send a mail to Arthur that we don't really care about
    the renumbering</p>

    <p class='phone'><cite>jkaputin:</cite> if I send you a patch,
    would it be considered?</p>

    <p class='phone'><cite>Jonathan:</cite> it would be
    accepted<br />
    ... let's talk with Arthur</p><a name="action03" id=
    "action03"></a>

    <p class='irc'>&lt;<cite>Jonathan</cite>&gt;
    <strong>ACTION:</strong> Jonathan to start renumbering
    discussion [recorded in <a href=
    "http://www.w3.org/2007/02/22-ws-desc-minutes.html#action03">http://www.w3.org/2007/02/22-ws-desc-minutes.html#action03</a>]</p>

    <p class='phone'><cite>Jonathan:</cite> any necessary changes
    to the SOAP 1.1 binding?<br />
    ... RDF mapping?</p>

    <p class='phone'><cite>JacekK:</cite> it will be updated for
    the PR publication round</p>

    <p class='phone'><cite>Jonathan:</cite> next week we'll ask
    about new WDs of SOAP 1.1 binding, additional MEPs, and RDF
    mapping</p>

    <p class='irc'>&lt;<cite>alewis</cite>&gt; noted, jonathan.</p>

    <p class='phone'><cite>Jonathan:</cite> the additional MEPs
    title should look more official<br />
    ... similar to the specs</p>

    <p class='phone'><cite>jjm:</cite> CR136 implementing needs the
    regeneration of the component table</p>

    <p class='phone'><cite>plh:</cite> I can do it</p>

    <p class='phone'><cite>Jonathan:</cite> there's a - component
    which is weird<br />
    ... see you next week</p>

    <p class='phone'><cite>asir:</cite> not aware of any changes
    for SOAP 1.1 binding doc</p>
  </div>

  <h2><a name="ActionSummary" id="ActionSummary">Summary of Action
  Items</a></h2><!-- Action Items -->

  <strong>[NEW]</strong> <strong>ACTION:</strong> Jonathan to put the proposal on the list for us to double-check. [recorded in <a href="#action00">#action00</a>]<br />

  <strong>[NEW]</strong> <strong>ACTION:</strong> Jonathan to
  figure out what characters can be used as query separators
  without causing harm [recorded in <a href=
  "http://www.w3.org/2007/02/22-ws-desc-minutes.html#action01">http://www.w3.org/2007/02/22-ws-desc-minutes.html#action01</a>]<br />

  <strong>[NEW]</strong> <strong>ACTION:</strong> Jonathan to send
  a summary of our URI templating text to the URI list [recorded in
  <a href=
  "http://www.w3.org/2007/02/22-ws-desc-minutes.html#action02">http://www.w3.org/2007/02/22-ws-desc-minutes.html#action02</a>]<br />

  <strong>[NEW]</strong> <strong>ACTION:</strong> Jonathan to start
  renumbering discussion [recorded in <a href=
  "http://www.w3.org/2007/02/22-ws-desc-minutes.html#action03">http://www.w3.org/2007/02/22-ws-desc-minutes.html#action03</a>]<br />

  &nbsp;<br />
  [End of minutes]<br />
  <hr />

  <address>
    Minutes formatted by David Booth's <a href=
    "http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm">
    scribe.perl</a> version 1.127 (<a href=
    "http://dev.w3.org/cvsweb/2002/scribe/">CVS log</a>)<br />
    $Date: 2007/02/22 18:32:01 $
  </address>

</body>
</html>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.