[provision] Technical Reporters Next Steps

[Darran Rolls <Darran.Rolls@waveset.com>]

Folks

I understand that on Monday's con-call we came to some level of
agreement on the Technical Reporter issue.  So far we have the following
TR's identified: 

TR-1	ASN.1 MIB->XML				GavenrajS
TR-2	CIM/XML initiative			WinstonB
TR-3	OASIS CIQ					DarranR
TR-4	OASIS SAML & XACML			HalL
TR-5	OASIS ebXML					DarranR
TR-6	W3C Web Services Architecture WG	KarlG
TR-7	SOAP security				CliffS

Unless anyone wishes to change or modify the proposed TR charter, it
stands as follows:

"There are many adjacent technologies that do/could effect the
requirements of SPML. A TR would be responsible for investigating,
reporting and recommending to the committee specific adjacent
technologies that affect/over-lap with the charter of the PSTC.
Technical Reporters collate, summarize and recommend to the committee
details of their assigned "subject" in the form of an informal report.
The TR role may develop into a more permanent liaison role if needed."

No doubt, TR activities will vary in depth and activity timing depending
on the subject at hand.  IMO we do need to get some initial data on some
of the subjects.  I therefore propose that we set a date of 3/25/2002
for an outline of each and submit the following template for a TR
submission document:

1) Introduction to "subject"
2) Discussion of "subject" relevance to SPML
	2.1) How "subject" effects SPML
	2.2) How SPML could effect "subject"
3) Initial recommendation for action items
4) Recommended reading 

I also propose a regular "2 minute update" on each TR subject be added
to the agenda for each bi-weekly con-call.

Thoughts/comments?

--------------------------------------------------------
Darran Rolls                      http://www.waveset.com
Waveset Technologies Inc          drolls@waveset.com 
(512) 657 8360                    PGP  0x8AC67C6F   
--------------------------------------------------------