RE: [sca-assembly] Fw: Submission of SCA Assembly Test Suite package for Public Review

Mike,

 

Based on a discussion  we had on last week’s call, I
have been thinking that we should resolve the language issues before going to
public review.

I really don’t think it makes sense for Assembly to own
Java™, c/cpp and BPEL artifacts, even if they are for core Assembly tests.
Furthermore since the BPEL test are not ready it does seem bizarre to offer the
package up for PR at this point in time.

 

Therefore I suggest we withdraw the PR request from TC-Admin,
remove the language artifacts, then revote on submitting to PR. 

 

This of course does not affect the Test Assertions document.

 

Martin.

 

From: Mike Edwards
[mailto:] 

Sent: 08 July 2009 15:11

To: OASIS Assembly

Cc: Dave Ings; Michael Winters

Subject: [sca-assembly] Fw: Submission of SCA Assembly Test Suite
package for Public Review

 

Folks, 

OASIS has a
problem with the one of the namespaces used in the test suite. 

Unfortunately,
this namespace is what you get for the WSDL resulting from a standard JAX-WS

transformation
of the Java interfaces in the org.oasisopen.sca.test Java package. 

So we now have
an OASIS contradiction.  We are required to use a given Java package name
for 

our Java
classes, but OASIS can't live with the Java-standard namespace that inevitably
results from 

this package
name.  Something has to give. 

It is clear
that OASIS has very little experience of dealing with code packages.
 Getting the test suite 

published looks
like being very heavy going... 

Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.

Co Chair OASIS SCA Assembly TC.

IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.

Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  

Email:   

-----
Forwarded by Mike Edwards/UK/IBM on 08/07/2009 15:04 ----- 

 

  
  
From: 

  
  
  
Mary
  McRae <> 

  
 

 

  
  
To: 

  
  
  
Mike
  Edwards/UK/IBM@IBMGB 

  
 

 

  
  
Cc: 

  
  
  
Martin
  Chapman <> 

  
 

 

  
  
Date: 

  
  
  
08/07/2009
  03:32 

  
 

 

  
  
Subject: 

  
  
  
Re:
  Submission of SCA Assembly Test Suite package for Public Review

  
 

 

Hi Mike, 

  On the TestCases document there are 3 namespaces; I'll need a namespace
document for the first two; the third isn't allowed (http://test.sca.oasisopen.org). We
agreed that sca.oasisopen.org is being used as a java class/package (sorry I
don't know the proper terminology) name; but namespaces must live in the
predetermined docs.oasis-open.org domain. 

Also, the test cases themselves should either be referenced on the cover of the
spec or in the namespace document. 

thanks! 

Mary 

Mary P McRae 

Director, Standards Development 

Technical Committee Administrator 

OASIS: Advancing open standards for the
information society 

email:  

web: www.oasis-open.org 

twitter: fiberartisan  #oasisopen 

phone: 1.603.232.9090 

Standards are like parachutes: they work best
when they're open. 

On Jul 2, 2009, at 11:03 AM, Mike Edwards wrote: 

 

  
  
***********************

  Warning: Your file, sca-assembly-1.1-testsuite-cd01.zip, contains more than
  32 files after decompression and cannot be scanned.

  ***********************

  
 

Mary, 

Here is an updated copy of the ZIP containing the files, with the URLs corrected
as below. 

Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.

Co Chair OASIS SCA Assembly TC.

IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.

Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  

Email:  

 

  
  
From: 

  
  
  
Mary
  McRae <> 

  
 

 

  
  
To: 

  
  
  
Mike
  Edwards/UK/IBM@IBMGB 

  
 

 

  
  
Cc: 

  
  
  
Martin
  Chapman <> 

  
 

 

  
  
Date: 

  
  
  
01/07/2009
  15:13 

  
 

 

  
  
Subject: 

  
  
  
Re:
  Submission of SCA Assembly Test Suite package for Public Review

  
 

 

On Jul 1, 2009, at 9:59 AM, Mike Edwards wrote: 

Mary, 

I stand corrected regarding the URLs of the documents/artifacts, which are
clearly wrong on the current 

TestAssertions and TestCases documents, and should be changed to: 

http://docs.oasis-open.org/opencsa/sca-assembly/sca-assembly-1.1-testcases-cd01.pdf

and 

http://docs.oasis-open.org/opencsa/sca-assembly/sca-assembly-1.1-test-assertions-cd01.pdf

Do you need me to produce updated copies of the documents with the URLs changed
as above? 

I can change them if you want, or you can provide updated copies if you prefer.

OK regarding the root directory name for the unzipped package, as below:

http://docs.oasis-open.org/opencsa/sca-assembly/testsuite/cd01/

<personal opinion> 

I have no idea as to why OASIS thinks that an unzipped directory tree of
several hundred artifacts is useful to anyone, 

UNLESS it is inside some source repository such as Subversion.  The ZIP
represents an easily downloaded and 

managed file.  A directory tree full of stuff is simply a headache.

In my opinion, OASIS needs to change its procedures regarding code packages of
this kind. 

</personal opinion> 

There was some concern about hidden files and not being directly accessible. If
someone downloads it and unzips it they have the same results. But that gives
me an idea - does it make sense to put a readme in the zip file noting the SVN
URI and a URI to be used that would result in the same fileset (that is the
exact same versions of all components)? Of course the readme would then be
visible in the unzipped set on docs.oasis-open.org ... 

Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.

Co Chair OASIS SCA Assembly TC.

IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.

Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  

Email:  

 

  
  
From: 

  
  
  
Mary
  McRae <> 

  
 

 

  
  
To: 

  
  
  
Mike
  Edwards/UK/IBM@IBMGB 

  
 

 

  
  
Cc: 

  
  
  
Martin
  Chapman <> 

  
 

 

  
  
Date: 

  
  
  
01/07/2009
  14:28 

  
 

 

  
  
Subject: 

  
  
  
Re:
  Submission of SCA Assembly Test Suite package for Public Review

  
 

Hi Mike, 

The only thing is that we require that a zip file be unzipped - of course the
zip file is available and should be the thing referenced (which is what we do
for UBL which also has hundreds of tiny files associated with it) but I need to
unzip it as well. If I unzip it under 'testsuite' we'll end up with the problem
of needing to overwrite. Is it okay if the unzipped version lives in an
intermediate subdirectory? (cd01, or date, or ??) (i.e. http://docs.oasis-open.org/opencsa/sca-assembly/testsuite/cd01/{files
here}? You don't actually have to cite it anywhere; they just need to be
available. 

And don't forget the 'opensca' preceding sca-assembly. 

Mary 

On Jul 1, 2009, at 4:51 AM, Mike Edwards wrote: 

Mary, 

Both the TestCases document and the TestAssertions document have URIs that
follow the pattern of the SCA Assembly Model spec itself, 

so I hope that these are suitable as-is. 

The remaining thing is the testcase artifacts ZIP package. 

My view is that it will always be a ZIP package - there are hundreds of low
level artifacts and their names and their numbers will change 

over time so that it is never going to be practical to reference them directly
(that would require a permanent Subversion system with 

normative status, similar to what is done in many open source projects with
permanent branches capturing source + binary for each 

release). 

So, what URI can we give to the ZIP file?  How about treating it like
another document, along these lines: 

http://docs.oasis-open.org/sca-assembly/testsuite/sca-assembly-1.1-testcases-cd01.zip   (current
version) 

and 

http://docs.oasis-open.org/sca-assembly/testsuite/sca-assembly-1.1-testcases.zip   (latest
version) 

I envisage that the version number of the TestSuite ZIP will move in step with
the version number of the TestCases and TestAssertions documents. 

Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.

Co Chair OASIS SCA Assembly TC.

IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.

Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  

Email:  

 

  
  
From: 

  
  
  
Mary
  McRae <> 

  
 

 

  
  
To: 

  
  
  
Mike
  Edwards/UK/IBM@IBMGB, Martin Chapman <> 

  
 

 

  
  
Date: 

  
  
  
01/07/2009
  00:00 

  
 

 

  
  
Subject: 

  
  
  
Re:
  Submission of SCA Assembly Test Suite package for Public Review

  
 

Hi Mike, 

Yes, that makes sense. I would keep them separate, even if the vote happens
simultaneously. Otherwise you'll have difficulty updating them going forward
without impacting the specification itself. 

The CGM TC also maintains a test suite, but they don't include it as part of
the standard itself. It's just a series of XML files. ODF will likely do the
same at some point. 

Anyway, my suggestion is to establish a persistent URI - akin to a namespace or
the 'latest version' URI - that we will use to point to whatever the latest
version of the test suite is. That URI should then be noted on the main spec
cover (could be added beneath the Namespace section). Additionally, any
references to the test suite within the specification itself could use that URI
and not have to worry about it being out-of-date. Like a namespace, if/once the
spec changes so that the test suite is no longer applicable, a new test suite
URI would be created. 

Does that make sense? I'm certainly open to other suggestions. If you want to
re-think any of this before the public review is announced let me know and I'll
hold off. I'll go ahead and check the document anyway to see if there's
anything that needs to be tweaked in the meantime. 

Mary 

On Jun 30, 2009, at 5:05 PM, Mike Edwards wrote: 

Mary, 

I feel that we SCA TCs are being guinea pigs here...ideally, OASIS would have
established procedures for dealing 

with test suites. 

OK, so this is the Test Suite for the Assembly Model spec. 

We expect that eventually, when taking the Assembly Model spec forward as a
standard, the Assembly model spec will point to these 

documents and artifacts and say some thing like "In order to conform with
the Assembly Model spec, an SCA runtime must pass the 

Test Suite, as described in these documents and artifacts". 

It is however also likely that during the maintenance phase of the spec, that
the test suite may be updated on a schedule separate from 

that of the specification - effectively we envisage that the Test Suite will
itself have bugs which will need fixing, independently from any 

problems in the main spec itself.  So the documents and artifacts for the
test suite are going to get voted on separately in the long run, 

even if the initial vote has them done together. 

Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.

Co Chair OASIS SCA Assembly TC.

IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.

Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  

Email:  

 

  
  
From: 

  
  
  
Mary
  McRae <> 

  
 

 

  
  
To: 

  
  
  
Mike
  Edwards/UK/IBM@IBMGB 

  
 

 

  
  
Date: 

  
  
  
25/06/2009
  17:23 

  
 

 

  
  
Subject: 

  
  
  
Re:
  Submission of SCA Assembly Test Suite package for Public Review

  
 

Hi Mike, 

I haven't looked at the documents yet but wanted to ask how you envision this
document proceeding? That is, is it a separate specification that stands on its
own (and all ballots would happen separately) or is it intended to be part of
the main specification? 

Thanks, 

Mary 

Mary P McRae 

Director, Standards Development 

Technical Committee Administrator 

OASIS: Advancing open standards for the information society 

email:  

web: www.oasis-open.org

twitter: fiberartisan  #oasisopen 

phone: 1.603.232.9090 

Standards are like parachutes: they work best when they're open. 

On Jun 17, 2009, at 4:46 AM, Mike Edwards wrote: 

Mary, 

On the June 16th, 2009 conference call [1], the SCA Assembly TC resolved by
passing of unanimous motions to 

A) Submit the SCA Assembly Test Assertions document and the SCA Assembly
TestCases document with its associated 

set of test artifacts, as Committee Draft 1 package [2]  and to submit
these as a Public Review Draft 

B) Hold the Public Review for 60 days 

Please post the material in package [2] on the OASIS site. 

Please initiate the public review of the SCA Assembly Test Suite package.  

Please let me and Martin Chapman know if you have any questions. 

[1] http://www.oasis-open.org/apps/org/workgroup/sca-assembly/download.php/32959/SCA%20Assembly%20minutes%202009-06-09.html

[2] http://www.oasis-open.org/apps/org/workgroup/sca-assembly-testing/download.php/32966/sca-assembly-1.1-testsuite-cd01.zip

Explanation of the contents of the sca-assembly-1.1-testsuite-cd01.zip file:

a) Test Assertions document, in PDF, ODT and HTML formats 

b) TestCases document, in PDF, ODT, HTML formats 

c) TestCases artifacts file in ZIP format 

The artifacts file is the source form of the contents of the testcases
described in the TestCases document and consists of a very large 

number of SCA Composite files, WSDL files, Java files, C files, C++ files (and
so on), laid out in a directory structure.  We are unsure how 

you would like to present this material on the OASIS site, given the volume of
material.  We strongly suggest that the material is made 

available in the ZIP format to enable easy downloading by people wanting to
examine or run the testcase suite, even if the material is 

also laid out in directory tree form on the OASIS website.  The testcase
document currently does not contain a link to the artifacts in the 

ZIP file, simply because we do not know what location you intend to use for
these artifacts - I am happy to add such a link to the testcase 

document if you will let me know what URL to use. 

Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.

Co Chair OASIS SCA Assembly TC.

IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.

Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  

Email:  

Unless
stated otherwise above:

IBM United Kingdom Limited - Registered in England and Wales with number
741598. 

Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

 

Unless
stated otherwise above:

IBM United Kingdom Limited - Registered in England and Wales with number
741598. 

Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

 

 

Unless
stated otherwise above:

IBM United Kingdom Limited - Registered in England and Wales with number
741598. 

Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

 

 

 

Unless
stated otherwise above:

IBM United Kingdom Limited - Registered in England and Wales with number
741598. 

Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

 

Unless
stated otherwise above:

IBM United Kingdom Limited - Registered in England and Wales with number
741598. 

Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

<sca-assembly-1.1-testsuite-cd01.zip> 

 

Unless
stated otherwise above:

IBM United Kingdom Limited - Registered in England and Wales with number
741598. 

Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU