Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

[STDS-802-11-EDITORS] Fwd: [STDS-802-11-EDITORS] Fwd: [STDS-802-11-TGM] Fwd: RA conventions for binary and hexadecimal numbers



--- This message came from the IEEE 802.11 Editors' Reflector ---
Forwarded Mike's reply to EDITORS@LISTERV.

---------- Forwarded message ---------
From: M Montemurro <montemurro.michael@xxxxxxxxx>
Date: Mon, Jan 10, 2022 at 7:08 PM
Subject: Re: [STDS-802-11-EDITORS] Fwd: [STDS-802-11-TGM] Fwd: RA conventions for binary and hexadecimal numbers
To: <mark.hamilton2152@xxxxxxxxx>
Cc: Edward Au <edward.ks.au@xxxxxxxxx>, <STDS-802-11-EDITORS@xxxxxxxxxxxxxxxxx>


Hey Mark,

It might make sense to get a contribution with changes for REVme and discuss it there. We can bring it back to the Editors group once we have a conclusion. Also, I'll touchbase with Bob and the RAC to see if there has been any progress with updating the IEEE SA style guide.

Cheers,

Mike

On Mon, Jan 10, 2022 at 6:56 PM <mark.hamilton2152@xxxxxxxxx> wrote:

Hi, Edward,

 

Since REVme is undergoing its first WG LB now, this seems like a good time to remind us of this concern, and take the opportunity to consider 802.11’s usage of numbers.

 

A few comments on Bob’s points on slide 9 of the attached:

  • We do say “0x…” most of the time, but not always, when we are using hexadecimal.  (except in MAC Addresses, or in MIB DEFVALs – and not doing so is correct in those contexts)
  • Most of our long strings of hexadecimal numbers (at least) are separated with spaces for readability.  But, a few are not.
  • We have examples of MAC Addresses using colons, but only in examples/code/test vectors.  For example (D1.0): P2879.12, and P5944.21.  I guess we could debate about these uses, since they do appear to contradict IEEE Std 802’s defined style.
  • We do use both upper and lower case A-Z.  I don’t have an opinion if that is good or bad.
  • We are pretty bad about identifying binary numbers as such, with the assumption that it is clear from context (which I think it generally is).

 

So, in general, I think we are doing pretty well, but perhaps a quick scrub is worthwhile, and a couple points could be discussed.

 

Mark

 

From: *** IEEE stds-802-11-editors List *** <STDS-802-11-EDITORS@xxxxxxxxxxxxxxxxx> On Behalf Of Edward Au
Sent: Friday, May 21, 2021 12:01 PM
To: STDS-802-11-EDITORS@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-EDITORS] Fwd: [STDS-802-11-TGM] Fwd: RA conventions for binary and hexadecimal numbers

 

--- This message came from the IEEE 802.11 Editors' Reflector ---

Forwarded to Editors for awareness and discussion, if needed.

 

Regards,
Edward

 

---------- Forwarded message ---------
From: M Montemurro <montemurro.michael@xxxxxxxxx>
Date: Thu, May 20, 2021 at 4:35 PM
Subject: [STDS-802-11-TGM] Fwd: RA conventions for binary and hexadecimal numbers
To: <STDS-802-11-TGM@xxxxxxxxxxxxxxxxx>



--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---

Hello everyone,

 

Bob Grow suggested that I bring this up to REVme for consideration. In a couple of issues recently addressed by the RAC, there were cases where there is no consistency in the respresentation of hex and binary numbers as well as hex identifiers. Bob created the two documents I have attached. You will notice that 802.11 is called out in the PPT. Bob has also met with IEEE editorial staff and is suggesting some updates to the IEEE style guide. 

 

If there is interest, we could schedule some time to discuss this in context of REVme.

 

Cheers,

 

Mike 

 


To unsubscribe from the STDS-802-11-TGM list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM&A=1


To unsubscribe from the STDS-802-11-EDITORS list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-EDITORS&A=1


To unsubscribe from the STDS-802-11-EDITORS list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-EDITORS&A=1