OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-brsp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: DRAFT MINUTES - 22 August 2013 - WS-BRSP TC Meeting


----------------------------------------
DRAFT MINUTES
OASIS WS-BRSP TC Meeting
22 August 2013, 12:00pm to 01:00pm PDT
----------------------------------------

Scribe: Gershon Janssen

0. Call to Order and roll call
Jacques Durand calls the meeting to order and welcomes everyone.

* Roll call:
Jacques Durand 
Gershon Janssen 
Doug Davis
Tom Rutt
Micah Hainline

This meeting quorates.

Agenda adopted.


1. Administrative
Approval of July 18, 2013 meeting minutes:
URL: https://lists.oasis-open.org/archives/ws-brsp/201308/msg00000.html
Minutes approved by unanimous consent.


2. Fixing the CSDs
PR request was posted a little later due to summer time. PR didn't actually happen -- TC Admin noticed our documents were not completely correct.

A couple of things, pionted out by TC admin, have changed:

- The front page got cleaned-up by Chet. Jacques added the abstracts that were missing.

- The Acknowledgement sections are added or cleaned up (were either missing or inadequate)

This has been updated in a new CSD.

We now need to approve these new CSDs of the 4 profiles.

* Basic Profile Version 1.2

Motion (1):
that the TC approve Basic Profile Version 1.2, (Working Draft 05) and all associated artifacts 
packaged together in: 
https://www.oasis-open.org/apps/org/workgroup/ws-brsp/download.php/50377/BP12-WD04b.zip
as a Committee Specification Draft as a replacement for the previously 
approved  https://www.oasis-open.org/apps/org/workgroup/ws-brsp/download.php/49762/BP12-WD04.zip  
and designate the DOC version of the specification as authoritative. 
We further direct the Chairs to submit  this draft for a 30 day public review and to 
perform any actions required by the TC Administrator to accomplish that issuance as soon as practicable.

Gershon moves, Tom Rutt seconds. No discussion.
Roll call vote: Jacques - Y, Gershon - Y, Micah - Y, Tom Rutt - Y, Doug - Y.
Result: 5 out of 5 YES.
Motion carried.

* Basic Profile Version 2.0

Motion (2):
that the TC approve Basic Profile Version 2.0, (Working Draft 05) and all associated artifacts 
packaged together in:
https://www.oasis-open.org/apps/org/workgroup/ws-brsp/download.php/50376/BP20-WD04b.zip
as a Committee Specification Draft as a replacement for the previously 
approved  https://www.oasis-open.org/apps/org/workgroup/ws-brsp/download.php/49763/BP20-WD04.zip
and designate the DOC version of the specification as authoritative. 
We further direct the Chairs to submit  this draft for a 30 day public review and to 
perform any actions required by the TC Administrator to accomplish that issuance as soon as practicable.

Tom Rutt moves, Gershon seconds. No discussion.
Roll call vote: Jacques - Y, Gershon - Y, Micah - Y, Tom Rutt - Y, Doug - Y.
Result: 5 out of 5 YES.
Motion carried.

* Reliable Secure Profile Version 1.0

Motion (3):
that the TC approve Basic Security Profile 1.1, (Working Draft 05) and all associated artifacts 
packaged together in: 
https://www.oasis-open.org/apps/org/workgroup/ws-brsp/download.php/50375/BSP11-WD04b.zip
as a Committee Specification Draft as a replacement for the previously 
approved   https://www.oasis-open.org/apps/org/workgroup/ws-brsp/download.php/49764/BSP11-WD04.zip 
and designate the DOC version of the specification as authoritative. 
We further direct the Chairs to submit  this draft for a 30 day public review and to 
perform any actions required by the TC Administrator to accomplish that issuance as soon as practicable.

Tom Rutt moves, Gershon seconds. No discussion.
Roll call vote: Jacques - Y, Gershon - Y, Micah - Y, Tom Rutt - Y, Doug - Y.
Result: 5 out of 5 YES.
Motion carried.

* Basic Security Profile Version 1.1

Motion (4):
that the TC approve Reliable Secure Profile Version 1.0, (Working Draft 05) and all associated artifacts packaged together in: 
https://www.oasis-open.org/apps/org/workgroup/ws-brsp/download.php/50378/RSP10-WD04b.zip
as a Committee Specification Draft as a replacement for the previously 
approved  https://www.oasis-open.org/apps/org/workgroup/ws-brsp/download.php/49761/RSP10-WD04.zip
and designate the DOC version of the specification as authoritative. 
We further direct the Chairs to submit  this draft for a 30 day public review and to 
perform any actions required by the TC Administrator to accomplish that issuance as soon as practicable.

Tom Rutt moves, Gershon seconds. No discussion.
Roll call vote: Jacques - Y, Gershon - Y, Micah - Y, Tom Rutt - Y, Doug - Y.
Result: 5 out of 5 YES.
Motion carried.


3. Test Tools follow-up 

Off load handling of the test tools availability / distribution by another platform / group. OASIS is not a suitable organization for this.  We like to donate / upload them to open-source projects.

Main concern is making the test tools available, so people can download them. Let's now decide to just put them out there. This doesn't have to be a formal part of the TC.

The connection between the TC and open source versions of the tools is that the TC can make (approve) statements that a particular version of the referred tools and suites is appropriate for verifying conformance to a particular version of a particular profile. Such statements would include precise references to these tools and suite.

Micah notes that this is not something we have done so far.

Tom Rutt notes that tool testing was performed in the past and was a very daunting task in terms of execution. New tools should handle the XPath statements; are somewhat more friendly. The TC is more worried about the older tools.

Jacques like the OASIS TC to have some sort of authority towards the test tools; this needs to be discussed.

Tom Rutt notes that we do have the test assertions; if someone made a tool that changed the test assertions, we would not even be able to find out without going through code. We need to maintain the test assertions. We cannot certify if they have done a good job implementing the test assertions.

Micah mentions that Microsoft is willing to donate all of its work on the test tools to open source.

Tom Rutt will post a new version of the analyzer tool.

We do need to think on how to setup e.g. an open source project such as on GitHub; who would be able to access it? e.g. create a TC account? or add all members of the TC to it?

Various questions need to be answers in following meetings.


4.  Adjourn
Next meeting around mid September (4 weeks from now).

Meeting adjourned.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]