[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ** EDIINT COmments
Thanks for your comments Graham. My comments follow in the text.
>23 Comments: From Graham Helliar
>We still have no clear idea of how many EDI Interchanges go within a single MIME
>message. X.435 stipulates a single EDI Interchange, so if you want to map
>between MIME and X.435 you need to address this.
23 Comments: From Rik Drummond
Even though X.435 only allows one interchange per message, it seems a short sighted restriction because of the *Request for Quote* type messages which go to may addresses. To this end if we wish to have what ever we do be 1) translatable to/from X.435 (we have not agreed on this yet) and 2) we wish to support multiple MIME/RFC822 addresses per Interchange in our MIME message we must know the impact this have on the translation between X.435 and MIME/EDI? What transactions does it possibly impact? The big question: How will it affect the EDI translator? The problem may be with the translator sending out one interchange from its point of view and receiving multiple responses. (I assume we would not have the translator create many messages and then stick them in a single MIME message.) I don't know the impact. Does any body?
>04 Comments: From Graham Helliar
>>> From Rik Drummond
>>> step 3) the data is copied from the EDI transaction (Step 1 output) is
>>> appropriately places in the proper MIME or SMTP message
>I would be grateful for any pointers to where the 'appropriate places' are
04 Comments: From Rik Drummond
Graham, I was presenting the logic used in the X.435 envelope creation. The movement of some ISA data fields up to the X.435 envelope. I don't have the standards in front of me, so I can't quote which data items. In the case of MIME the only ones I can think of are the source/destination addresses after being translated to RFC822 addresses. Should there be others, if we encrypt the entire Interchange? Maybe we should move (copy) the entire ISA segment into a special field in the MIME envelope so that it may be read when the interchange is encrypted -- just a thought -- don't know if it has any use.