- From: Arthur Ryman <ryman@ca.ibm.com>
- Date: Mon, 26 Feb 2007 00:21:33 -0500
- To: "Jonathan Marsh" <jonathan@wso2.com>, woden-dev@ws.apache.org
- Cc: "'John Kaputin \(gmail\)'" <jakaputin@gmail.com>, "'www-ws-desc'" <www-ws-desc@w3.org>
- Message-ID: <OFD0BC1555.33E1B5B2-ON8525728E.001CC7D8-8525728E.001D7064@ca.ibm.com>
Jonathan, I updated the spec Part 1 and 2, and the test suite, documents. I preserved the old assertion ids using a new attribute: @cr-id. I generated 2 files that give the mappings of the old to new numbers: renumber-assertions-1.properties [1], renumber-assertions-2.properties [2]. These can be used in the Ant <replace> task to do bulk updates. Here is the task from the test suite build.xml [3] <target name="renumber-assertions" description="Renumbers assertions using PR ids."> <replace dir="documents" includes="**/*.xml, **/*.wsdl" replacefilterfile="../wsdl20/renumber-assertions-1.properties" /> <replace dir="documents" includes="**/*.xml, **/*.wsdl" replacefilterfile="../wsdl20/renumber-assertions-2.properties" /> </target> John - I haven't updated the Woden code yet. Can you handle this? [1] http://dev.w3.org/cvsweb/2002/ws/desc/wsdl20/renumber-assertions-1.properties [2] http://dev.w3.org/cvsweb/2002/ws/desc/wsdl20/renumber-assertions-2.properties [3] http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/build.xml Arthur Ryman, IBM Software Group, Rational Division blog: http://ryman.eclipsedevelopersjournal.com/ phone: +1-905-413-3077, TL 969-3077 assistant: +1-905-413-2411, TL 969-2411 fax: +1-905-413-4920, TL 969-4920 mobile: +1-416-939-5063, text: 4169395063@fido.ca "Jonathan Marsh" <jonathan@wso2.com> 02/23/2007 11:16 AM To Arthur Ryman/Toronto/IBM@IBMCA cc "'John Kaputin \(gmail\)'" <jakaputin@gmail.com>, "'www-ws-desc'" <www-ws-desc@w3.org> Subject RE: Renumbering assertions The schedule is, if we can complete the small amount of editorial work remaining (renumbering assertions would be the biggest part of it), get LocationTemplate-2G working and regenerate WSO2ß à Canon message testing results, and close the last few issues, we?ll be ready to go the PR. I?d like that vote to occur next Thursday, but active discussion about what to encode still continues? Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com From: Arthur Ryman [mailto:ryman@ca.ibm.com] Sent: Friday, February 23, 2007 4:21 AM To: Jonathan Marsh Cc: 'John Kaputin (gmail)'; 'www-ws-desc' Subject: Re: Renumbering assertions Jonathan, I'll do the renumbering. I want to preserve the old numbers too so we can provide mapping help for implementors and the test suite. I'll do this on the weekend. The 7-digit numbering scheme was introduced to minimize conflicts when we had the team currently working on many sections of the spec. I'll cut it back down to 4 digits which should be plenty. I'll reserve the first digit to indicate the spec Part (1 or 2). That leaves 999 slots in each spec. I'll also clean up any outstanding ed actions this weekend, My new projects are preventing me from attending calls lately but I am highly motivated to finish the ed work on the spec and move it to PR. What is our schedule? Arthur Ryman, IBM Software Group, Rational Division blog: http://ryman.eclipsedevelopersjournal.com/ phone: +1-905-413-3077, TL 969-3077 assistant: +1-905-413-2411, TL 969-2411 fax: +1-905-413-4920, TL 969-4920 mobile: +1-416-939-5063, text: 4169395063@fido.ca "Jonathan Marsh" <jonathan@wso2.com> 02/22/2007 07:50 PM To Arthur Ryman/Toronto/IBM@IBMCA, "'John Kaputin \(gmail\)'" <jakaputin@gmail.com> cc "'www-ws-desc'" <www-ws-desc@w3.org> Subject Renumbering assertions Arthur, Today in the WG call we discussed whether we should renumber the assertions as we had planned to do. Some assertions use a 4-digit number and others use a 7-digit number which includes a locator code. Presumably they should all move toward the 7 digit code (though beyond indicating which part of the spec the assertion is found in the extra digits don?t prove that useful ? one can take the assertion number and use it as a fragment identifier against the spec to locate the corresponding text.) We however weren?t able to solicit a volunteer to do this work, which is fairly substantial when one considers that any assertion number change needs to simultaneously be changed throughout the test suite metadata. I even reluctantly volunteered if the WG expressed a strong desire to normalize these identifiers. It didn?t. John did offer to try to fit in some work along this line, but first perhaps it would be good to see how motivated you are to have consistent assertion identifiers. Are you motivated enough to do some significant editorial work? Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com
Received on Monday, 26 February 2007 05:21:56 UTC