Editorial Policy

The rules governing how technical data is sourced, verified, and presented on this site. We prioritize traceability over simplicity.

The Source Hierarchy (E-E-A-T)

When researching a specification, we prioritize sources in the following order. A lower-tier source can never override a higher-tier source.

Hierarchy of evidence used for technical claims.
TierSource TypeExamples
Tier 1Official StandardsIEEE 802.3, ANSI/TIA-568, ISO/IEC 11801.
Tier 2Testing & CertificationFluke Networks, UL, ETL.
Tier 3Manufacturer White PapersCisco, CommScope, Panduit, Belden.
Tier 4General ExplanatoryIndustry publications, educational resources.

Conflict Resolution

The networking industry is not perfectly unified. TIA (North America) and ISO/IEC (International) sometimes classify cables differently (e.g., Cat6A vs. Class EA), and manufacturer datasheets sometimes exceed standard minimums.

Our Rule: We never silently pick one number. If TIA and ISO differ on a maximum distance, we state both. If a manufacturer claims a 10% performance increase over the standard, we note it as a manufacturer-specific attribute, not a universal fact.

Example: Cat6 10GBASE-T reach. The standard gives a conservative 37m to 55m range based on alien crosstalk. We do not print "55m" as a guaranteed fact; we print the range and explain the variables.

Verification Statuses

Every record in our structured dataset carries a status badge so you know exactly how strong the evidence is.

Status labels used across the site's data tables.
StatusMeaning
VerifiedChecked directly against an IEEE, TIA, or ISO standard, or a certified testing lab.
ConditionalCorrect only under specific conditions (e.g., alien crosstalk, temperature, installation quality).
Not SupportedThe standard explicitly states this configuration does not meet requirements.
Insufficient DataNo reliable standard or datasheet covers this specific combination.

Corrections & Updates

Standards evolve (e.g., the release of TIA-568.2-E in 2024). If a specification changes, we update the data. If a reader finds an error and provides a verifiable source, we correct it immediately and note the change.

To submit a correction, please visit our Contact pageand include the URL and the source that proves the error.

Published · Last reviewed