Paul Thorpe wrote: > > On Fri, 24 May 2002, Egon Andersen, Talura wrote: > > > Paul Thorpe wrote: > > > > > > Hi Egon, > > > > > > You have the latest version (pre-published). The only > > > changes that will be made before publication are that the > > > cross-references will be updated to point to clauses in the ASN.1 > > > 2002 edition. > > > > > Thanks, but that is actually in contradiction to the message I got when > > I sent a defect report on the document related to clause 9.4, where > > "xmlhstring" will give a non-unique encoding. > > So I'm a little confused. > > There was an editorial omission in 9.3.1 and in 9.4 which will be in the > published version. Add "with all white-space removed" to the end of > 9.3.1, and add "with all white-space removed, and all letters in > upper-case" to the end of 9.4. > I would prefere 'over-decadic hexadecimal digits' instead of 'letters'. (BEEF will mean different things, either re-cycled bits or something eatable.) Furthermore I think we still have a problem, if the number of hexadecimal digits is an odd number. 1FF and 1FF0 shall be interpreted the same, according to X.680 (2002) 22.8. I think we have to restrict the number of hexadecimal digits to be: "not an odd number of hexadecimal digits". (And now when I read 22.8 again, the wording '... is not an even number ...' may be better if it was written: '... is an odd number ...', because the number 0 (zero) is sometimes debated whether it is an even number or not! As I remember it, 0 (zero) is not an even number in the strict mathematical sence.)
Best regards Egon Andersen -- * Talura ApS * Phone: +45 43 52 50 00 * * Baldersh�j 24 B * mailto:[EMAIL PROTECTED] * * DK-2635 Ish�j * http://www.talura.dk *
