Funny, I thought ConOps was a euphimism for a remake
of "The Sting"
;-)
"HUGHES,JIM (HP-Cupertino,ex1)" wrote:
>
> Prasad,
>
> Ralph was thinking of IEE 1362-1998, "Concept of Operations (ConOps)
> Document". Look at
> http://standards.ieee.org/reading/ieee/std_public/description/se/1362-1998_d
> esc.html (I think this is correct, but I can't seem to connect to the IEEE
> website this evening...).
>
> Jim
>
> > -----Original Message-----
> > From: Prasad Yendluri [mailto:]
> > Sent: Friday, July 20, 2001 5:07 PM
> > To: HUGHES,JIM (HP-Cupertino,ex1)
> > Cc: ebXML Msg
> > Subject: Re: Comments directed to Teams
> >
> >
> > Thanks Jim. That helps a lot. I guess we need to clarify what
> > the ConOps stands
> > for before people read too much into it (I mean with Ralph as
> > the lead:)
> >
> > Regards, Prasad
> >
> > -------- Original Message --------
> > Subject: RE: Comments directed to Teams
> > Date: Fri, 20 Jul 2001 16:22:17 -0700
> > From: "HUGHES,JIM (HP-Cupertino,ex1)" <>
> > To: ebXML Msg <>
> >
> > Minor comments on the Team missions:
> >
> > - T1 isn't defining an initial Service Interface (which is
> > missing from the
> > current spec); this team is looking at the overall
> > architecture issues, how
> > this messaging spec relates to other standards bodies, how it
> > fits into the
> > work of the overall OASIS/CEFACT ebXML Architecture Work
> > Group (not yet
> > organized), etc. Thus, the Service Interface topic is really about
> > confirming the need for it and resolving that this TC needs
> > to do the work.
> >
> > - For those not at the meeting, the wording in T2's
> > description (create a
> > "TC Spec") is deliberate. Another option is to create a full "OASIS
> > Standard" that gets voted on by the whole OASIS membership.
> > We're not going
> > to do the latter, reserving that action for the V2 document.
> >
> > - T3 is starting with the old ebXML Requirements Matrix,
> > upgrading it for
> > use in building V2...
> >
> > Regards,
> >
> > Jim
> >
> >
> > > -----Original Message-----
> > > From: David Fischer [mailto:]
> > > Sent: Friday, July 20, 2001 1:16 PM
> > > To: ebXML Msg
> > > Subject: Comments directed to Teams
> > >
> > >
> > >
> > > The ebXML Teams have requested that messages posed directly
> > > to the teams have a
> > > subject line prefaced with the Team Designation to ensure
> > > timely receipt and
> > > processing. The Teams are as follows:
> > >
> > > Team Team
> > > Designation Description
> > > -------------- --------------
> > > T1 Con Ops Team (Team 1) Lead Ralph Berwanger
> > > Definition on how things work and why (Architecture)
> > > V1.0 sections 5 & 6 (make a usage section)
> > > Define initial Service Interface
> > >
> > > T2 v1.0 Errata Team (Team 2) Lead David Burdett
> > > Clarifications, Easy bug fixes, NO NEW FUNCTIONALITY,
> > > Document will be v1.1 and will be a TC Specification
> > > Comments Cut-off will be 17 August at midnight Pacific
> > >
> > > T3 Requirements Team (Team 3) Lead Brian Gibb
> > > New Functionality
> > > Recommendations for v2.0 Document
> > >
> > > Example Subject: T2 Request for Clarification Section 8.2.2
> > >
> > > Regards,
> > >
> > > David Fischer
> > > Secretary, ebXML-Msg TC
> > >
> >
> >
>
> ------------------------------------------------------------------
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to:
