[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Protocol/Requirements for BP PT Documents for QRT
the documents should follow the same standards as the technical specifications (ie ebXML template and line identification in PDF format). at QR we treat these the same as technical specs its just that they only have one round of review. the latest ebXML document tmeplate is available at http://www.ebxml.org/project_teams/technical_coord/One-Pagers.htm -but the only change to the one you already have is the revised copyright statement. good luck! "Marcia L. McLure Ph.D." wrote: > Tim, > I will be assisting the Business Process Analysis sub team in pulling the > various documents together in order to send you a compiled grouping of these > documents. Do you have any suggestions regarding this matter and how best to > present these docs to you on the 19th? In terms of presentation format, the > documents will follow the document template that was provided by QRT. Is > there an updated version of the template that I need to be aware of?Does QRT > also require 'line by line recognition' in these docs? I know that is the > case for the specifications but wondered if you wanted them for the white > papers? Are there any other guidelines that I should be aware of? I will > continue working on these documents this weekend. > Tim, if you have any additional suggestions on the process or format > requirements,please let me know. > Thank you Tim. > Best regards, > Marcia > BP PT Co-Lead > > Marcia L. McLure Ph.D. > MMI > 28720 Canwood Street Suite 208 > Agoura Hills CA 91301 > 818-706-3882 > Fax 818-706-1213 > ----- Original Message ----- > From: "Tim McGrath" <tmcgrath@tedis.com.au> > To: "christopher ferris" <chris.ferris@east.sun.com> > Cc: <ebxml-stc@lists.ebxml.org>; "'ebXML Coordination'" > <ebxml-coord@lists.ebxml.org> > Sent: Wednesday, March 14, 2001 4:48 PM > Subject: Re: ebXML Message Service Spec V 98b > > > <eb:MessageHeader SOAP-ENV:mustUnderstand="1" eb:version="98.0"> > > <eb:From> > > <eb:PartyId>QR Team</eb:PartyId> > > </eb:From> > > <eb:To> > > <eb:PartyId>TRP Team</eb:PartyId> > > </eb:To> > > <eb:CPAId>1800-ANYTIME</eb:CPAId> > > <eb:ConversationId>20001209-133003-28572</eb:ConversationId> > > <eb:Service>QualityReviewSubmission</eb:Service> > > <eb:Action>Acknowledgement</eb:Action> > > <eb:MessageData> > > <eb:MessageId>nice.comm.20001209-133003-28572</eb:MessageId> > > <eb:Timestamp>200103150043Z</Timestamp> > > </eb:MessageData> > > <eb:QualityOfServiceInfo deliverySemantics="OnceAndOnlyOnce"/> > > </eb:MessageHeader> > > </SOAP-ENV:Header> > > <messagetext> > > The QR team acknowledge receipt of this specification. We shall try and > turn it around on or before Tuesday > > 20th March. > > > > PS. I am not sure if this message is compliant :-) > > </messagetext> > > > > christopher ferris wrote: > > > > > Tim, > > > > > > Attached you will find the final working draft of the > > > ebXML Message Service specification, version 0.98b > > > that we hereby formally submit to QRT for formal review. > > > > > > Thanks, > > > > > > Chris > > > > > > ------------------------------------------------------------------------ > > > Name: ebXML > Message Service Specification v0.98b.pdf > > > ebXML Message Service Specification v0.98b.pdf Type: Portable > Document Format (application/pdf) > > > Encoding: BASE64 > > > Description: ebXML > Message Service Specification v0.98b.pdf > > > > -- > > regards > > tim mcgrath > > TEDIS fremantle western australia 6160 > > phone: +618 93352228 fax: +618 93352142 > > > > > > > > ------------------------------------------------------------------ > > To unsubscribe from this elist send a message with the single word > > "unsubscribe" in the body to: ebxml-stc-request@lists.ebxml.org > > -- regards tim mcgrath TEDIS fremantle western australia 6160 phone: +618 93352228 fax: +618 93352142
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC