[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ebxml-iic] Groups - ebMS 2.0 Deployment Profile Template (ebMS2-Deployment-Profile-Template-1.1-b.doc) uploaded
Jacques, Here is some feedback on the document; hope this is useful .. 2.1.4 A community could also impose restrictions at the MIME envelope level. E.g. restricting the MIME types allowed for attachments, and the relative order of attachments of various types. The total size of the message may be an issue, e.g. when SMTP gateways are used in the community, so average and maximum message size is useful information in a profile. 3.1.6 Some ebXML profiles have requirements for the format and source of MessageId. E.g. in the HL7 DSTU it is derived from the HL7 interaction id. Similarly for RefToMessageId. There may be length and format restrictions if the ID is generated by an EAI messaging protocol that the ebMS processor bridges to. 3.1.4 An example of a different use of ConversationId: In HL7 there is a concept of interactive queries, where there would be a message for query initialization, and then messages for "give me the next batch" continuation queries. The ConversationId could be used to encode such interations within a single query to allow a backend data source to set and maintain a cursor corresponding to a query. This it is not in the current DSTU, but was proposed for a revision. 3.19 Manifest. The profile could specify if the order of Manifest elements has to match the order of the referenced MIME attachments. Some profiles may restrict the range of value for xlink:reference (e.g. nothing other than content id references). General: It may be useful to separate functionality of the ebXML message processor from the application adapter invoking the message processor. E.g. it is important to know which optional parts of ebMS are needed to interact in a particular community when you are in a software supplier selection process. This is independent of payload format. Functionality such as setting ebXML header fields (e.g. MessageId) based on XML payload data would be part of the invocation of the processor, rather than its ebXML capabilities. The "alignment" field is very useful for applications where ebXML header fields are filled from corresponding fields in the XML payloads, in addition to the alignment with CPA and BPSS. For example, the HL7 ebXML DSTU provides such a mapping for HL7. The responsibility of preserving this mapping is of the application invoking the message processor, rather than the ebXML processor. Pim van der Eijk -----Original Message----- From: jdurand@us.fujitsu.com [mailto:jdurand@us.fujitsu.com] Sent: 13 June 2005 23:32 To: ebxml-iic@lists.oasis-open.org Subject: [ebxml-iic] Groups - ebMS 2.0 Deployment Profile Template (ebMS2-Deployment-Profile-Template-1.1-b.doc) uploaded Please review new revision (file name ending "-b") - we'll put it to vote as soon as it is stable. We may set a call next week, Monday 20th. -- Mr Jacques Durand The document revision named ebMS 2.0 Deployment Profile Template (ebMS2-Deployment-Profile-Template-1.1-b.doc) has been submitted by Mr Jacques Durand to the OASIS ebXML Implementation, Interoperability and Conformance (IIC) TC document repository. This document is revision #5 of ebMS2-Deployment-Profile-Template.doc. Document Description: (June 13th) Fixing issues noted by Pete and Sacha today. This is a complete, ready-to-use new version (1.1) of the template for ebMS2 Deployment Profiles. Editorial corrections, especially on the status of doc statement. View Document Details: http://www.oasis-open.org/apps/org/workgroup/ebxml-iic/document.php?document _id=13075 Download Document: http://www.oasis-open.org/apps/org/workgroup/ebxml-iic/download.php/13075/eb MS2-Deployment-Profile-Template-1.1-b.doc Revision: This document is revision #5 of ebMS2-Deployment-Profile-Template.doc. The document details page referenced above will show the complete revision history. PLEASE NOTE: If the above links do not work for you, your email application may be breaking the link into two pieces. You may be able to copy and paste the entire link address into the address field of your web browser. -OASIS Open Administration
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]