<alewis> silly creature apparently isn't aware of ntp ....

Look at that!

Eric as scribe.

<Roland> Scribe: eric

Need volunteers for editors.

Roland: Wants to see a draft out from the W3C quickly - two or three items.
... Need to change the namespace.
... 3rd item - one namespace or two? People wanting to use the properties in WSDL for other purposes than just SOAP - thus want to separate properties from SOAP.
... continuing the IRI/URI effort - on the third draft. Some small changes required in the SOAP/JMS specification to match the latest draft.
... (that is, matching the latest URI scheme draft at the IETF)

glen: with so few implementations of the preceding specification, changing the namespace should be a no-brainer.

<alewis> +1 to changes as soon as possible.

phil: we should change the namespace sooner, and people are probably expecting the namespace to change with the W3C.

<gdaniels> +1

<bhakti> +1

<PhilAdams> +1

+1

<Derek> +1

eric: Two namespace - understand the idea, but the implementation might be spurious.

roland: tend to agree with Eric. Looks odd when people using it for other purposes - but there are already too many namespaces in the world.
... are there significant changes in the URI spec that will affect SOAP/JMS binding?

eric: Not many that I'm aware of.

glen: pulling together interoperability plans, test plans.

roland: yes - talked about it last week. Test cases, interoperability. Talk about editors - also need editor for writing test plans, test reports, development of test cases.

bhakti: also willing to help with editing.

Roland: Specification has been moved to the W3C CVS repository.

alewis: IETF submission still on the Subversion server.

<scribe> ACTION: Roland to send information to bhakti about using CVS [recorded in http://www.w3.org/2008/05/13-soap-jms-minutes.html#action01]

<trackbot-ng> Created ACTION-4 - Send information to bhakti about using CVS [on Roland Merrick - due 2008-05-20].

(got pointers from Amy)

Roland: Need to get started on test plans and interoperability. What can we do about test cases.

eric: Go through and enumerate the RFC 2119 criteria, identify whether items are testable, and for those that aren't, look at the spec, for those that are, identify the test.

roland: identify what makes sense as conformance statements.
... look for these items as you're refamiliarizing yourself with the spec.
... anyone else with issues?
... reconvene next week.

This is scribe.perl Revision: 1.133  of Date: 2008/01/18 18:48:51  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: eric
Inferring ScribeNick: eric

WARNING: No "Topic:" lines found.

Default Present: +0138687aaaa, +1.919.742.aabb, alewis, Roland, peaston, +1.708.246.aacc, +1.408.431.aadd, derek?, +1.781.999.aaee, bhakti, PhilAdams
Present: +0138687aaaa +1.919.742.aabb alewis Roland peaston +1.708.246.aacc +1.408.431.aadd derek? +1.781.999.aaee bhakti PhilAdams
Regrets: Mark Yves Peter_(Partial)
Agenda: http://lists.w3.org/Archives/Public/public-soap-jms/2008May/0003.html
Got date from IRC log name: 13 May 2008
Guessing minutes URL: http://www.w3.org/2008/05/13-soap-jms-minutes.html
People with action items: roland

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