RE: [ws-i-ms] charter proposal 09-01-2011

[Ram Jeyaraman <Ram.Jeyaraman@microsoft.com>]

> What looks to one person like a needed clarification of a requirement might be seen by another person as changing the actual requirements.

That's the reason why we need to make clear the scope of changes allowed. Unless we transcribe our intent clearly into charter scope, it makes it difficult to ascertain whether changes are in scope or not - particularly, when people move on over time and others end up carrying on the work.

Being able to transcribe our collective intent into clear charter wording that we all can agree upon is an essential exercise that will help ensure that we all are on the same page. Otherwise, we may assume that we have an agreement when in actuality there is none. If we can't agree on the charter wording, I question whether we all are on the same page?

I support the maintenance work on the WS-I profiles. I also understand that there is a desire to improve the test tools and test assertions; I support that as well. However, I want to ensure that any changes to the profile resulting from test enhancement activities don't result in breaking changes to the normative parts of the profile. Do we all agree on this point?

Thanks.

-----Original Message-----
From: ws-i-ms@lists.oasis-open.org [mailto:ws-i-ms@lists.oasis-open.org] On Behalf Of Micah Hainline
Sent: Monday, September 19, 2011 8:53 AM
To: ws-i-ms@lists.oasis-open.org Section
Cc: Gilbert Pilz; Ram Jeyaraman
Subject: Re: [ws-i-ms] charter proposal 09-01-2011

In my mind, the changes proposed by Ram seem a little too restrictive, specifically the phrases "(resulting from test enhancements)" and "Modifications resulting from test enhancements shall not change profile requirements or other normative parts of the profiles."  I think everyone agrees that we would prefer that all the changes made (if any!) be minor in nature.  I also recognize that everyone would like to "put this on the shelf", but that language may cause more problems than it solves.  What looks to one person like a needed clarification of a requirement might be seen by another person as changing the actual requirements.  I think that's something better handled in the TC, not in the charter.  I'm pretty confident that we're not going to get into a situation where a requirement change is approved that puts one of the implementations out of compliance with the profiles, and I don't think we really need quite so much defensive language in the charter protecting from this.  Unless I'm misunderstanding the intent of those changes?

One other issue that I'm curious about is the release of the testing tools.  I'm very much in favor, but I'm wondering if anyone knows what other OASIS standards have a software component, and how those are licensed.  I'd like to ensure that we don't have the same problem that WS-I had of overly restrictive licensing of test tools. 

-Micah

----- Original Message -----
From: "Ram Jeyaraman" <Ram.Jeyaraman@microsoft.com>
To: "Gilbert Pilz" <gilbert.pilz@oracle.com>, "ws-i-ms@lists.oasis-open.org Section" <ws-i-ms@lists.oasis-open.org>
Sent: Wednesday, September 7, 2011 4:30:03 PM
Subject: RE: [ws-i-ms] charter proposal 09-01-2011





We need to clearly describe the nature of anticipated minor modifications so that the scope of such modifications are well-defined. I have attached a modified version (all changes are marked). 





From: Gilbert Pilz [mailto:gilbert.pilz@oracle.com]
Sent: Friday, September 02, 2011 1:14 PM
To: ws-i-ms@lists.oasis-open.org Section
Subject: [ws-i-ms] charter proposal 09-01-2011 



Latest version of the charter: 

    • adds constraint that testing meet OASIS and JTC 1 requirements 
    • removes timeline 
    • adds caveat that 'The existing ISO/IEC profiles and BSP 1.1 both used a different testing methodology which may not be amenable to automation.' 
    • misc cleanups and word-smithing 


~ gp
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 

---------------------------------------------------------------------
To unsubscribe, e-mail: ws-i-ms-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: ws-i-ms-help@lists.oasis-open.org