|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
Re: ANSI ASC X12: BIN and BDS segments
From: "Mike Rawlins" <
> There's been a bit of traffic on this, but I don't think any of the
> messages have quite answered your essential questions. You ask:
>
> >But how can this be, given that a communications protocol may be a 7-bit
> >protocol? If you use a 7-bit protocol, either you'd lose
> >bit 7 of each octet or it would be misinterpreted as a control character.
> >Or, does the use of BDS/BIN presuppose the use of an 8-bit
> >protocol? Or preempt the use of high-order characters?
> >
> >Or does the standard just assume that "you have the data, communications
> >is a totally separate consideration?" (Which really seems
> >strange given the origin and original design of ANSI ASC X12 data format).
> Actually, the answer is sort of the last case, but with
>qualification This is the reason for the "Filter ID Code" in BDS01 and EFI16
(used with BIN).
Aha! Partners may (or may have to!) agree on an encoding standard for BIN03
data consistent with their communications agreement!
Now *that* makes sense!! (If not to the little guys I work with, it does to
me).
Thank you much.
Michael Mattias
Tal Systems, Inc.
Racine WI
http://www.talsystems.com
|
|
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
