RE: [ekmi] Re: unable to speak at tomorrow's EKMI meeting after all

["Mary McRae" <mary.mcrae@oasis-open.org>]

Hi Arshad,

  They are not allowed to participate in a TC meeting. Any and all
information from a non-TC-member must come through the TC comment list, per
the OASIS TC Policy.

Mary

> -----Original Message-----
> From: Arshad Noor [mailto:arshad.noor@strongauth.com]
> Sent: Monday, February 16, 2009 4:49 PM
> To: mary.mcrae@oasis-open.org
> Cc: 'Dee Schur'; drsecure@us.ibm.com; 'James Bryce Clark';
> laurent.liscia@oasis-open.org; mark.schiller@hp.com;
> robert.griffin@rsa.com; 'ekmi'
> Subject: Re: [ekmi] Re: unable to speak at tomorrow's EKMI meeting
> after all
> 
> And, in the case when their presentation refers to publicly
> available information - which may already be designated as
> royalty-free - what other assurances are they supposed to
> agree to before presenting to the TC?
> 
> Arshad
> 
> Mary McRae wrote:
> > Especially so, since they are not a member of the TC and have not
> agreed to
> > the feedback license for whatever their specific contribution might
> be. All
> > input from non-TC members must come through the TC Comment list.
> >
> > Mary
> >
> >> -----Original Message-----
> >> From: Arshad Noor [mailto:arshad.noor@strongauth.com]
> >> Sent: Monday, February 16, 2009 4:37 PM
> >> To: mary.mcrae@oasis-open.org
> >> Cc: 'Dee Schur'; drsecure@us.ibm.com; 'James Bryce Clark';
> >> laurent.liscia@oasis-open.org; mark.schiller@hp.com;
> >> robert.griffin@rsa.com; 'ekmi'
> >> Subject: Re: [ekmi] Re: unable to speak at tomorrow's EKMI meeting
> >> after all
> >>
> >> Even when invited to present on a topic that is germane to the TC
> >> and its work?
> >>
> >> Mary McRae wrote:
> >>> In this particular case, the person in question is a contractor to
> >> OASIS and
> >>> performing work for the TC. I see no reason why he wouldn't be
> >> allowed to a
> >>> portion of the TC call discussing the contracted work.
> >>>
> >>> On the other hand, non-members should not be participating in TC
> >> calls -
> >>> that is a violation of OASIS Policy.
> >>>
> >