[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: We passed: FW: trp version 0.21d Message Handling Services SpecforQR review
Martha and all, Here as promised my comments on the MSS revised example and schema: - Suggested changes to example: 1. Proposal : ?xml element in header and payload header : change in text or in example to common attribute name for « encoding » (preferred) or charset. Reason: suspected error: inconsistency with spec text. 2. Proposal: RefToMessageId: remove Not Applicable or put a reference to a document. Reason: suspected error: inconsistency with spec text. 3. Typo: ReliableMessagingInfo: </ReliableMessagingInfo> is missing. 4. Proposal: ErrorURI: contains the application( mailto: in front). At least for consistency reasons, the other UIDs seem also to need such an application in front. 5. Proposal: Content-Length in payload envelope: should come after Content-ID. Reason: suspected error (vs. MIME spec). - Suggested changes to Schema: 1. Proposal: Routing Header in ebXMLHeader description: add minOccurs = 0. 2. Correction: ebXMLHeader: add xmlns as first attribute. 3. Proposal: Manifest: Change minOccurs value from 0 to 1. Reason: must not be mentioned if empty. 4. Proposal: TPAId: change type from uri to string. Reason: currently inconsistent with MessageId and RefToMessageId. 5. Proposal: General: Review the sequencing of the definitions to ensure consistency of resolution of elements. E.g. TPAId definition seems to be moved from in front to after TPAInfo. Reason: Suspected violation of schema rules (anyway, it should be so for processing reasons). Thanks, John Rik Drummond wrote: > martha, please send the v0.21d to the list with the comment spreadsheet... > thanks, rik > > -----Original Message----- > From: Tim McGrath [mailto:firstname.lastname@example.org] > Sent: Thursday, October 19, 2000 10:59 PM > To: Rik Drummond > Cc: email@example.com > Subject: Re: trp version 0.21d Message Handling Services Spec for QR > review > > sorry Rik we may have got caught in procedural delays. i know klaus is > travelling which may cause some problems. > > here is our response to the executive > > > The QR team have reviewed the latest document submitted by the Transport, > > Routing and > > Packaging Team - Messaging Service Specification Version 0.21d dated 16 > > October 2000 > > (ebXML_TA_v0.9.doc). > > > > Our findings are that it: > > * aligns with the vision of ebXML, > > * satisifes the ebXML's approved requirements document > > * does not overlap or conflict with any other specification, and > > * provides complete and correct information about the purpose of the > document > > > > We therefore recommend this document for its second round of public > review. > > > this does not mean that the Executive has given approval - that must come > from > Klaus. (but i don't imagine there will be a problem). > > i am not sure what else we can do. > > > > > > Rik Drummond wrote: > > > tim, how do we look? > > > > -----Original Message----- > > From: Tim McGrath [mailto:firstname.lastname@example.org] > > Sent: Monday, October 16, 2000 8:54 PM > > To: Rik Drummond > > Cc: Ebxml-Stc > > Subject: Re: trp version 0.21d Message Handling Services Spec for QR > > review > > > > the QR Team accept this document and as agreed will report to the > executive > > by 18:00 PST on Thursday 19th. > > > > Rik Drummond wrote: > > > > > 016-m > > > > > > ------------------------------------------------------------------------ > > > Name: > > ebxml Message Service Specification v-021d 001016-maw.doc > > > ebxml Message Service Specification v-021d 001016-maw.doc Type: > > Microsoft Word Document (application/msword) > > > Encoding: > > BASE64 > > > > > > Name: > > ebXML Message Service Specification v-021d 001016-maw.pdf > > > ebXML Message Service Specification v-021d 001016-maw.pdf Type: > > Portable Document Format (application/pdf) > > > Encoding: > > BASE64 > > > > > > Name: Comments on ver 0.21c.xls > > > Comments on ver 0.21c.xls Type: Microsoft Excel Worksheet > > (application/x-msexcel) > > > Encoding: BASE64 > > > > -- > > regards > > tim mcgrath > > TEDIS fremantle western australia 6160 > > phone: +618 93352228 fax: +618 93352142 > > -- > regards > tim mcgrath > TEDIS fremantle western australia 6160 > phone: +618 93352228 fax: +618 93352142 -- This e-mail and any attachments thereto may contain information that is confidential and/or proprietary and is intended for the sole use of the recipient(s) named above. It is not intended to create or affect any contractual arrangements between the parties. If you have received this e-mail by mistake, please notify the sender and delete it immediately. Thank you for your co-operation.
begin:vcard n:Neve;John N. tel;fax:+32 2 655 30 05 tel;work:+32 2 655 30 87 x-mozilla-html:TRUE url:www.swift.com org:S.W.I.F.T. s.c.;Marketing- Standards adr:;;avenue Adele 1;La Hulpe;;B1310;Belgium version:2.1 email;internet:email@example.com title:Systems architect fn:John N. Neve end:vcard
Powered by eList eXpress LLC