zsmartsystems / com.zsmartsystems.zigbee.sniffer

ZigBee sniffer using Ember NCP and routing packets to Wireshark for display
Eclipse Public License 1.0
33 stars 18 forks source link

ZigBee to Zigbee and mention EFR32 #20

Closed Hedda closed 4 years ago

Hedda commented 4 years ago

"ZigBee" -> "Zigbee" as has the Zigbee Alliance has officially changed its trademarked name to stop using bicapitalization as its brand identity.

Please note that all com.zsmartsystems software looks to be using the old branding, as again, Zigbee should always a lowercase B, not a capital.

I'm unable to find a definitive reference for when the "rebranding" occurred, but it did.

zigbeealliance.org consistently uses the form with lowercase b, and contains numerous references like in https://zigbeealliance.org/solution_type/zigbee/ and https://zigbeealliance.org/developer_resources/zigbee-specification/

"Please note that this uses old branding, Zigbee is always a lowercase B, not a capital. This change occurred shortly after the official release of this document."

cdjackson commented 4 years ago

Clearly I am not planning on changing the class structure - that would be a major breaking change for something that really does not matter.

Hedda commented 4 years ago

@cdjackson But I did not suggest changing class structure, only the plain text parts in the readme file.

Even if you do not change any code you can still change plain text "Zigbee" references in the text files.

That is, code-wise it doesn't matter, but identity-wise it matters to the Zigbee Alliance branding.

cdjackson commented 4 years ago

Legally we are not allowed to use the Zigbee branding - I've already had this discussion with the Alliance! All of the ZSS documentation uses ZigBee so I would propose to keep everything the same rather than change. We can't change the class structure, so to me keeping a common naming that is inline with the naming and class naming used in the libraries is more consistent. Or do you not agree?

Hedda commented 4 years ago

ok