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: minutes Nov 15


For review,

-jacques

----------------------------------------
DRAFT MINUTES
OASIS WS-BRSP TC Meeting
15 November 2012, 12:00pm
----------------------------------------

Agenda:
=======

 1. Administrative
    - Minutes previous meeting
(https://www.oasis-open.org/apps/org/workgroup/ws-brsp/email/archives/201210/msg00008.html)
    - WS-I MS affiliation update.
    - Next meeting(s) schedule.

    
2. Specification maintenance and progression

    - Moving current Profiles toward OASIS CS or further: which source format? (AI: Tom / Ram)

   - Test assertions as a separate doc?
    - editor(s)?

    
3. Distribution and management of source code (long term)

    - Follow-up on OASIS repository,
    - 1st generation test tools: distribution and maintenance.
    - 2nd generation test tools: distribution and maintenance.


Attendees:
==========

Jacques Durand
Doug Davis
Micah Hainline
Ram Jeyaraman
Tom Rutt

Regrets from:

Gershon Janssen
Alessio Soldano

Action Items:
=============

-AI1: Jacques: set a doodle poll for straw poll to check for a possible better time. 
-AI2: Tom/Jacques: to convert BP1.2/2.0 and RSP to WSWord.
-AI3: Jacques: to gather some sample logs generated from previous tests, 
and create a repository with approval from generating companies.
-AI4: Jacques to check what the proper test tool contribution (to BRSP TC) procedure should be,
then follow-up. 



Minutes:
========
Now: 9 voting members in TC.

1. Administrative:

    - Minutes previous meeting: October 18th, approved.
(https://www.oasis-open.org/apps/org/workgroup/ws-brsp/email/archives/201210/msg00008.html)
    - WS-I MS affiliation update: 
The Steering Committee approved the TC becoming part of the Member Section (Mike DeNicola)
    - Next meeting(s) schedule: Dec 13th same time (noonPT) for now.
Jacques to set a doodle poll for straw poll to check for a possible better time. 



2. Specification maintenance and progression

    - Moving current Profiles toward OASIS CS or further: which source format? (AI: Tom / Ram)
Ram: ISO is flexible in using source formats. ISO started to support Word2010. A commonly used
source format has benefit that ISO editors can help us on these docs. 
Tom: If we do a PAS submission, we want to be the editor. XML has often proved quite inconvenient as a source.
Tom: suggests to convert the HTML into MSWord and extract the Test Assertions from the original previous XML source
as a separate (XML) file, for tool processing mostly. We could optionally in addition render the TAs in HTML and
convert this rendition in Word as an appendix to the profile specification.
Jacques: suggest we worry about Word rendition of TAs later, go with the core spec(s) just identifying
the TAs using their ID.
Dug: I used word to mark-up the html docs in w3c wsra - it worked just fine.

MOTION: (Tom, 2ND:Ram) Motion: Tom/Ram  the TC will convert the HTML version of the profiles to word format 
as a basis for further editing and progression in OASIS. 
And will separte the Test assertions into a separate XML file. 
UNAN approved.

Tom/Jacques: to convert BP1.2/2.0 and RSP to WSWord.

Jacques: About test assertions: another option would be to reuse a more generic tool
(http://code.google.com/p/tamelizer/) derived from WS-I Analyzer tool, with a more generic
TA format. But that would require serious regression testing, in addition to the conversion
(~5% TAs would need manual conversion). So unless there is quite some demande to evolve the tests,
prefer to stick with current WS-I Analyzer tool.
Micah: may want to consider ability to test for the future fixes: we'd need to rerun the tests
and compare with existing logs.
Jacques: to gather some sample logs generated from previous tests, 
and create a repository with approval from generating companies.
Tom Rutt (Fujitsu): we may need to include the SaxonB library binary we used at that time for the 
test script to use in its execution
Tom Rutt: where are the tools? still WS-I old site? Jacques: both on old site ws-i.org , and also on OASIS.
   
    
3. Distribution and management of source code (long term)

    - Follow-up on OASIS repository,
    - 1st generation test tools: distribution and maintenance.
    - 2nd generation test tools: distribution and maintenance.

Jacques: current SVN rep is empty on our site.
after check with OASIS: first step is for member companies that developped WS-I tools,
to contribute these officially to teh BRSP TC.
Jacques to check what the proper procedure for this should be (just a statement from company rep on BRSP list?)
COntributors so far: Microsoft, IBM, Fujitsu.


Appendix:
=========

---------------------------
RAW CHAT TRANSCRIPT
---------------------------


Dug: the little squirrels on the oasis site are slow today

Dug: minutes from prev call: https://www.oasis-open.org/apps/org/workgroup/ws-brsp/email/archives/201210/msg00008.html

Dug: I used word to mark-up the html docs in w3c wsra - it worked just fine.

Tom Rutt (Fujitsu): Here are some links to relevant documents on PAS submisson document styles:

ISO/IEC directives part 2 : rules for structure and drafting of Internationsl Standards
http://isotc.iso.org/livelink/livelink?func=ll&objId=10562502&objAction=download

JTC1 Standing documents:

http://isotc.iso.org/livelink/livelink?func=ll&objId=12452876&objAction=Open&nexturl=%2Flivelink%2Flivelink%3Ffunc%3Dll%26objId%3D9384365%26objAction%3Dbrowse%26sort%3Dname

Zip file included SD 9 - guide to PAS transposition

subclause 6.1.2 Submissions has the following paragraph:

"
The format of the specification submitted is not regulated by JTC 1. However, PAS submitters are
encouraged to apply a documentation style close to ISO/IEC's style (as shown in the ISO/IEC Directives
Part 2), as this will ease later alignment at the time of the first review after five years. Advice on
ISO/IECs documentation style can be obtained from ITTF or the JTC 1 Secretariat who will refer them to
a PAS Mentor.
"

So we can use our existing format if we wish.

Tom Rutt (Fujitsu): Motion: Tom/Ram  the TC will convert the HTML version of the profiles to word format as a basis for further editing and progression in OASIS.

Ram (Microsoft): I second

Tom Rutt (Fujitsu): And to separte the Test assertions into a separate XML file

Ram (Microsoft): I second

Ram (Microsoft): No objections. Motion approved.

Dug: I need to drop in a minute

Tom Rutt (Fujitsu): we may need to include the SaxonB library binary we used at that time for the test script to use in its execution


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