MASTER INDEX

Spec Registries & Catalogs

Where specs live before you pick an individual RFC or file format. SDOs publish normative documents; registries allocate code points; meta-indexes catalog the organizations themselves.

Sources indexed
95
Meta-indexes
9
Code-point registries
10
In Rundown bodies
44

SDO vs Registry vs Meta-index

Standards body (SDO)

Standards body — publishes normative protocol and format specs (RFC Editor, W3C, ISO).

Code-point registry

Code-point registry — allocates numbers and enums (IANA ports, MIME types, RTP PTs).

Meta-index

Catalog of catalogs — find which org owns a spec (ConsortiumInfo, ISO ICS, ANSI SDOs).

Type
Domain
Rundown
Showing 95 of 95 registry sources
ConsortiumInfoMeta-index

ConsortiumInfo Standards Setting Organizations List

When you don't know which body owns a spec, start here. It's the phone book of standards organizations.

Taxonomy: Searchable flat list with categorized overviews per organization
De jure SDOsConsortiaOpen source foundationsIndustry alliances
meta
ISO MembersMeta-index

ISO National Standards Bodies

ISO specs are often mirrored or sold through your national body. This is how you find the US, UK, or EU entry point.

Taxonomy: By country/territory · Membership tier (full, correspondent, subscriber)
Full membersCorrespondent membersSubscriber members
metadata-formatssystems
ISO ICSMeta-index

ISO International Classification for Standards (ICS)

Browse ISO's catalog by subject when you know the domain (file formats, healthcare, vehicles) but not the standard number.

Taxonomy: 3-level ICS: Field (2-digit) → Group → Sub-group
01 Generalities & documentation35 Information technology37 Image technology43 Road vehicles49 Aircraft & space
metadata-formatssystems
ANSI SDOsMeta-index

ANSI Accredited Standards Developers

Many 'international' specs are developed by US SDOs (INCITS, IEEE, ASTM) and transposed to ISO. ANSI is the US hub.

Taxonomy: Accredited SDO directory with scope and contact
Accredited SDOsUS TAGs to ISO/IECTechnical advisory groups
metainternetsystems
RFC EditorStandards body (SDO)In Rundown

RFC Editor

Every internet protocol spec (HTTP, TLS, DNS, SMTP, OAuth) eventually lands here as an RFC.

Taxonomy: By RFC number · Full-text search · By stream (IETF, IAB, IRTF, ISE, Legacy)
Standards-track RFCsBest Current Practice (BCP)InformationalExperimentalHistoric
internetwebsecuritytelecom
IETFStandards body (SDO)In Rundown

IETF Datatracker

See what's being standardized now — WG charters, draft revisions, and adoption status before it becomes an RFC.

Taxonomy: By Area → Working Group → Document · Streams · IESG state
Applications & Real-TimeGeneralInternetOps & ManagementRouting+2 more
internetwebsecuritynetworking
IANACode-point registryIn Rundown

IANA Protocol Registries

Specs define behavior; IANA registries define the allowed code points. Wrong port or MIME type? Check here.

Taxonomy: Alphabetical A–Z index grouped by protocol name
HTTP & URIDNSTLS & DTLSMedia Types (MIME)RTP & SRTP+2 more
internetwebsecuritytelecomdata-formats
ICANNPolicy bodyIn Rundown

Internet Corporation for Assigned Names and Numbers

Domain registration policy, WHOIS/RDAP deployment context, and new TLD programs live here — distinct from IETF DNS protocol specs.

Taxonomy: By policy area: domains, DNS security, contractual compliance
gTLD programccTLDRegistrar accreditationDNSSEC deploymentPolicy development
internet
WHATWGStandards body (SDO)In Rundown

WHATWG Living Standards

Browsers implement WHATWG — not versioned W3C snapshots. HTML, Fetch, and URL all live here.

Taxonomy: Flat list of living standards (no version numbers)
HTMLDOMFetchURLStreams+4 more
web
W3CStandards body (SDO)In Rundown

W3C Technical Reports

CSS, CSP, WebAuthn (with FIDO), SVG, and accessibility specs are W3C Recommendations even when WHATWG owns HTML.

Taxonomy: By status (Rec, CR, WD, Note, Registry) · By tag (CSS, Security, Media, Accessibility…)
Standards (Recommendations)Draft StandardsSupporting NotesSupporting RegistriesAccessibility (WAI)+2 more
websecuritymedia
EcmaStandards body (SDO)In Rundown

Ecma International Standards

JavaScript language semantics and JSON syntax have Ecma normative specs — implemented by all engines.

Taxonomy: By ECMA number · By category · By last change
ECMA-262 JavaScriptECMA-404 JSONECMA-376 OOXMLNFC/security (ECMA-4xx)
webdata-formats
UnicodeStandards body (SDO)In Rundown

Unicode Consortium

Every string, domain name (IDNA), and emoji behavior traces back to Unicode specs and the character database.

Taxonomy: By report type: UAX (annexes) · UTS (standards) · UTR (reports) · Stabilized/Withdrawn
UAX (Standard Annexes)UTS (Technical Standards)UTR (Technical Reports)Character Database (UCD)CLDR
webdata-formatsinternet
NIST CSRCStandards body (SDO)

NIST Computer Security Resource Center

FIPS 140 (crypto modules), AES/SHA standards, and NIST post-quantum algorithms — the US government's normative crypto baseline.

Taxonomy: By series: FIPS · SP 800 · SP 1800 · NISTIR · CSWP · By topic (crypto, identity, privacy)
FIPS (standards)SP 800 (guidance)SP 1800 (practice guides)NISTIRCybersecurity White Papers
security
CA/B ForumPolicy bodyIn Rundown

CA/Browser Forum

Every Let's Encrypt, DigiCert, or ACM certificate must comply with CA/B Baseline Requirements — not just PKIX RFCs.

Taxonomy: By working group: Server TLS · S/MIME · Code Signing · NetSec · By document type
TLS Baseline RequirementsEV GuidelinesS/MIME BaselineNetwork Security Guidelines
securityinternet
OpenIDIndustry consortiumIn Rundown

OpenID Foundation Specifications

OIDC Core, Discovery, and Session Management are published here — separate from IETF OAuth RFCs.

Taxonomy: By specification family: OIDC · OAuth profiles · SSF · Verifiable Credentials
OpenID Connect CoreOIDC DiscoveryFAPIShared SignalsIdentity Assurance
securityweb
FIDOIndustry consortiumIn Rundown

FIDO Alliance Specifications

Passkeys = WebAuthn (W3C) + CTAP (FIDO). Both spec sets are required for implementation.

Taxonomy: By spec: FIDO2 · CTAP · UAF/U2F (legacy) · Certification levels
FIDO2CTAP2WebAuthn (with W3C)PasskeysCertification
securityweb
OWASPIndustry consortium

OWASP Foundation

When someone says 'follow OWASP' they mean ASVS or Top 10 — the canonical security baseline for web apps, separate from NIST and IETF crypto specs.

Taxonomy: By project type: Top 10 · ASVS/MASVS · SAMM · Cheat Sheets · Testing Guide · Flagship vs Lab vs Production
OWASP Top 10ASVS (Application Security Verification Standard)SAMM (Software Assurance Maturity Model)MASVS (Mobile Application Security Verification)Cheat Sheet Series+1 more
securityweb
MITRECode-point registry

MITRE ATT&CK, CWE & CVE Program

Security teams map threats to ATT&CK, classify bugs with CWE, and track vulns by CVE — three vocabularies that interlink across the industry.

Taxonomy: ATT&CK: Tactics → Techniques → Sub-techniques · CWE: hierarchical weakness tree · CVE: ID list by year/vendor
ATT&CK Enterprise/Mobile/ICSCWE weakness catalogCAPEC attack patternsCVE Program (ID coordination)Engenuity (open security tools)
security
CISA KEVCode-point registry

CISA Known Exploited Vulnerabilities Catalog

If a CVE appears in KEV, patch priority jumps — widely used as a de-facto industry triage list beyond raw CVSS scores.

Taxonomy: Flat catalog by CVE ID · Filter by vendor/product · Required action dates
Known Exploited VulnerabilitiesBinding Operational DirectivesAdvisories
security
PCI SSCPolicy body

PCI Security Standards Council

Any system touching cardholder data must map controls to PCI DSS — a policy spec parallel to (and stricter than) generic app security baselines.

Taxonomy: By standard: PCI DSS · PTS · P2PE · PA-DSS (legacy) · By version and document type
PCI DSSPTS (PIN devices)P2PESecure Software StandardASV program
securitycloud
CSAIndustry consortium

Cloud Security Alliance

CSA CCM is the cross-cloud control framework — maps to ISO 27001, NIST, and PCI for cloud service assessments.

Taxonomy: By research domain: CCM · STAR · AI safety · Zero Trust · Working group outputs
CCM (Cloud Controls Matrix)STAR registry & CAIQConsensus AssessmentsAI safety initiative
securitycloud
ENISAPolicy body

ENISA Publications & Threat Landscape

EU regulatory context (NIS2, CRA, eIDAS2) and ENISA threat intel feed European compliance and product security programs.

Taxonomy: By publication type: Threat landscape · Guidelines · Certification · Policy briefs
EU Cybersecurity ActThreat LandscapeNIS2 guidanceCertification schemesAI cybersecurity
security
CISPolicy body

CIS Critical Security Controls

CIS Benchmarks are the practical hardening checklists (AWS, K8s, Windows) that complement OWASP app guidance and NIST frameworks.

Taxonomy: Controls v8: 18 control groups · Benchmarks by platform · IG1/IG2/IG3 implementation tiers
CIS Controls v8CIS BenchmarksCIS-CAT assessmentCommunity Defense Model
securitycloud
TCGIndustry consortiumIn Rundown

Trusted Computing Group

Secure Boot, TPM attestation, and BitLocker-style key sealing trace to TCG specs — the hardware root of trust below UEFI.

Taxonomy: By work group: TPM · PC Client · Storage · Network · Identity · By spec family
TPM 2.0 LibraryPC Client Specific ImplementationStorage (Opal)Network equipmentAttestation
securitysystems
Common CriteriaPolicy body

Common Criteria Portal

Government procurement and high-assurance products reference CC EAL levels and Protection Profiles — the global product security certification framework.

Taxonomy: By document: CC v3.1 · Protection Profiles · Certified products · National schemes
ISO/IEC 15408 (CC)Protection ProfilesCollaborative Protection ProfilesCertified Products
security
KantaraIndustry consortium

Kantara Initiative

Enterprise federation trust frameworks and eIDAS-adjacent identity assurance certification live here — complementary to OpenID and SAML.

Taxonomy: By program: Assurance · Consent · Interoperability · Working group deliverables
Identity Assurance FrameworkAssurance CertificationConsent & NoticeFAPI-adjacent trust
securityweb
ITU-TStandards body (SDO)In Rundown

ITU-T Recommendations

E.164 phone numbers, G.711/G.722 audio codecs, and H.323 all live in ITU-T series — foundational for telephony.

Taxonomy: Letter series A–Z · Study Groups · Recommendation number
E — Network operation & telephoneG — Transmission systemsH — Audiovisual/multimediaQ — Switching & signalingX — Data networks+1 more
telecommedia
3GPPStandards body (SDO)In Rundown

3GPP Specification Series

VoLTE, 5G NR, SMS PDU format, and SIM/USIM specs all come from 3GPP TS/TR documents indexed by series and release.

Taxonomy: Two-digit series × Release (Rel-15…Rel-19) · TS (normative) vs TR (report)
21 — Requirements22 — Stage 1 (services)23 — Stage 2 (architecture)24/29 — Stage 3 (signaling)26 — CODECs+3 more
telecommedia
ETSIStandards body (SDO)In Rundown

ETSI Standards

European mobile standards transposition, NFV/MEC for telco cloud, and many 3GPP specs publish through ETSI.

Taxonomy: By ETSI committee · Work programme · Standard number (GS, ES, TS, EN)
3GPP transpositionNFV (ETSI NFV)MECCybersecurity (ETSI CYBER)TETRA
telecomnetworking
GSMAIndustry consortiumIn Rundown

GSMA Specifications & Resources

RCS Universal Profile and eSIM remote provisioning specs are GSMA — not 3GPP — and drive consumer messaging and SIM policy.

Taxonomy: By solution area: eSIM · RCS · IoT · Identity · Fraud
eSIM/eUICC (SGP)RCS Universal ProfileDevice checkOperator guidelines
telecomiot
ISOStandards body (SDO)In RundownPaid access

ISO Standards Catalogue

Most binary file formats on the web (JPEG, PDF, MP4) are ISO/IEC standards — browse by ICS or search by number.

Taxonomy: ICS 3-level hierarchy · TC/SC committees · ISO number
JTC 1 — Information technologySC 29 — Coding of audio/videoSC 34 — Document descriptionICS 35 — ITICS 37 — Image technology
data-formatsmediasystems
IECStandards body (SDO)Paid access

International Electrotechnical Commission

ISO/IEC joint specs (14496 MPEG, 10918 JPEG) publish through both ISO and IEC — IEC webstore for electrical/embedded.

Taxonomy: By TC/SC · IEC 60000 series · ISO/IEC JTC 1 joint work
TC 100 — Audio/videoISO/IEC JTC 1/SC 29 — MPEGElectrical safety (60000 series)
data-formatsmediasystems
AOMediaIndustry consortiumIn Rundown

Alliance for Open Media

AV1/AVIF are the open web media codecs — normative specs live here, not at ISO (though HEIF container is ISO).

Taxonomy: By specification: AV1 · AVIF · IAMF
AV1 video codecAVIF image formatIAMF audio
mediaweb
KhronosIndustry consortiumIn Rundown

Khronos Registry

WebGL and Vulkan specs plus extension enums are maintained in the Khronos registry — structured like a formal spec tree per API.

Taxonomy: Per-API spec trees · Extension registries · API enum assignments
WebGL / OpenGL ESVulkanSPIR-VOpenCLglTF+1 more
webmediasystems
FileFormat.infoCode-point registry

FileFormat.info

Upload validation and forensic identification start with magic bytes. This is the best practical lookup when you don't have the full spec.

Taxonomy: By file extension · By magic bytes · By MIME type
Magic byte searchExtension lookupMIME correlation
data-formatswebsecurity
IEEE SAStandards body (SDO)In RundownPaid access

IEEE Standards Association

Every Ethernet frame and Wi-Fi packet conforms to IEEE 802 specs — the physical/link layer foundation.

Taxonomy: By IEEE number · By technology area · 802 working groups
IEEE 802.3 EthernetIEEE 802.11 Wi-FiIEEE 802.1 Bridging/VLANIEEE 802.1X NAC
networking
OASISStandards body (SDO)In Rundown

OASIS Open Standards

MQTT (IoT), SAML (enterprise SSO), and OpenDocument (ODF) are all OASIS standards with formal catalog entries.

Taxonomy: By Technical Committee · By standard name · Approved vs in-progress
MQTTAMQPSAMLPKCSOpenDocument (ODF)+1 more
iotsecuritydata-formatsweb
OpenConfigIndustry consortiumIn Rundown

OpenConfig YANG Models

Modern network automation (Google, Meta, Apple operators) standardizes on OpenConfig models over vendor SNMP/MIBs.

Taxonomy: By model domain: BGP · Interfaces · Platform · Routing · Telemetry
OpenConfig YANG modelsgNMI protocolModel releases
networking
UEFI ForumIndustry consortiumIn Rundown

UEFI Forum Specifications

Secure Boot, ACPI power management, and firmware-to-OS handoff are all UEFI Forum specs.

Taxonomy: By spec document: UEFI · ACPI · PI · Shell
UEFI SpecificationACPIPlatform Initialization (PI)UEFI Shell
systems
DMTFIndustry consortiumIn Rundown

DMTF Standards

Redfish replaces IPMI for out-of-band server management — the API schema and protocol are DMTF standards.

Taxonomy: By standard: Redfish · CIM · SMBIOS · OVF · DSP documents
RedfishCIMSMBIOSOVFCloud Infrastructure Management
systemscloud
PCI-SIGIndustry consortiumIn RundownPaid access

PCI-SIG Specifications

Every GPU and NVMe SSD connects via PCIe — the spec tree and ECN index live at PCI-SIG (membership for latest revs).

Taxonomy: By spec: PCIe base · CXL · Form factors · ECNs
PCI ExpressCXLM.2Card Electromechanical (CEM)
systems
USB-IFIndustry consortiumIn Rundown

USB-IF Specifications

USB HID (keyboards/mice), mass storage, and Type-C PD all have USB-IF class specs — separate from the base transport spec.

Taxonomy: By spec type: Base · Type-C/PD · Device class · Compliance
USB4USB 3.2USB Type-CUSB Power DeliveryDevice classes (HID, MSC, CDC)
systems
EIPsCode-point registryIn Rundown

Ethereum Improvement Proposals

ERC-20, ERC-721, EIP-1559, EIP-4337 (account abstraction) — all indexed by type and number at eips.ethereum.org.

Taxonomy: By type: Core · Networking · Interface · ERC · Meta · Informational · By status
Core (protocol)ERC (application)InterfaceMetaInformational
blockchain
BIPsCode-point registryIn Rundown

Bitcoin Improvement Proposals

HD wallets, mnemonic seeds, and Bitcoin URI schemes are BIPs — the index is the authoritative catalog.

Taxonomy: By BIP number · README index · Status (Draft/Proposed/Final/Rejected)
Standards TrackInformationalProcess
blockchain
IPFSIndustry consortiumIn Rundown

IPFS Specifications

Content-addressed web infrastructure — each primitive (CID, gateway, IPNS) has its own spec page in a structured index.

Taxonomy: By spec area: Content addressing · Naming · HTTP gateways · Data models
CID / Multihash / MultibaseIPLDIPNSDNSLinkHTTP Gateways (Path, Subdomain, Trustless)
blockchaininternet
Linux FoundationMeta-indexIn Rundown

Linux Foundation Projects

When a protocol is 'under the Linux Foundation' (OpenAPI, GraphQL, OCI, Node.js) this is the parent org catalog — broader than CNCF alone.

Taxonomy: By foundation sub-group: CNCF · OpenJS · LF Networking · LF Edge · Project lifecycle
CNCF (cloud native)OpenJS (JavaScript)LF NetworkingOpenSSF (security)Zephyr RTOS
cloudmetasecurity
OCIIndustry consortium

Open Container Initiative

Every container image and runtime (containerd, CRI-O, Podman) implements OCI specs — not Docker proprietary format.

Taxonomy: By spec: Image · Runtime · Distribution · Artifacts · Reference types
OCI Image FormatOCI Runtime SpecOCI Distribution SpecImage artifacts
cloudsystems
SPIFFEIndustry consortium

SPIFFE / SPIRE

mTLS between microservices at scale uses SPIFFE IDs instead of per-service certificates — CNCF graduated identity standard.

Taxonomy: By spec: SPIFFE ID · JWT-SVID · X.509-SVID · SPIRE architecture · Federation
SPIFFE specificationSPIRETrust federationJWT-SVIDX.509-SVID
securitycloud
YAML.orgStandards body (SDO)In Rundown

YAML Specification

YAML 1.2 is the normative spec for config syntax — distinct from JSON Schema validation layered on top.

Taxonomy: By version: 1.2.2 (current) · 1.1 (legacy) · Working drafts
YAML 1.2.2YAML 1.1 (legacy)Language design notes
data-formatscloudweb
Schema.orgIndustry consortium

Schema.org Vocabulary

Rich snippets, SEO structured data, and knowledge graph markup use Schema.org types — the de-facto web semantics catalog.

Taxonomy: By type hierarchy: Thing → subtypes · By property · Extension hosts
Full type hierarchyCore types (Thing, Organization…)Action typesMedical/Auto extensions
webdata-formats
XSFIndustry consortium

XMPP Standards Foundation

Federated chat (Movim, Snikket, commercial XMPP) implements XEPs — the IETF core RFC plus hundreds of XEP extensions indexed here.

Taxonomy: XEP number · Status (Draft/Experimental/Stable/Final) · Category (Core/Server/Client)
Core XEPsInstant messagingPubSubJingle (VoIP/video)Federation & DNS
telecominternet
AT ProtocolIndustry consortium

Authenticated Transfer Protocol (AT Protocol)

ActivityPub isn't the only federated social model — AT Protocol's lexicon catalog and repo sync spec are indexed at atproto.com.

Taxonomy: By spec area: Repository · Lexicons · Sync · Identity · HTTP APIs (XRPC)
AT Protocol coreLexicon schema catalogRepository commit syncDID methodsLabeling
internetweb
RIPECode-point registry

RIPE NCC Technical Documents

BGP routing policy, ASN allocation, and RIPE DB inetnum/inet6num objects are governed by RIPE community policies and docs.

Taxonomy: By document type: Policies · RIPE Docs · RIPE Labs · Database object types
IPv4/IPv6 allocation policiesASN assignmentRIPE DatabaseRouting registry (RPSL)
internetnetworking
ARINCode-point registry

ARIN Policy & Resource Management

North American IP and ASN resources are allocated under ARIN policy — distinct from RIPE/APNIC regional rules.

Taxonomy: By resource: IPv4 · IPv6 · ASN · Policy documents · RDAP/WHOIS
Number resource policiesRDAP/WHOISTransfer policiesCommunity policy development
internetnetworking
APNICCode-point registry

APNIC Policies & Resources

APAC IP allocation and routing registry (whois.apnic.net) follows APNIC-specific policies — third leg of the RIR system.

Taxonomy: By policy manual sections · Resource guides · Routing security (RPKI, MANRS)
Policy manualIPv4/IPv6 delegationASN registrationRPKI & routing security
internetnetworking
NVMeIndustry consortiumIn Rundown

NVM Express

Every NVMe SSD and cloud block volume speaks NVMe — spec revisions and command set registry at nvmexpress.org.

Taxonomy: By spec: Base · Command sets · Fabrics · Management · ZNS · RPMB
NVMe BaseNVMe-oFNVMe-MIZNS (Zoned Namespaces)Command set registry
systems
JEDECStandards body (SDO)Paid access

JEDEC Solid State Technology Standards

RAM timing, flash endurance ratings, and memory module specs are JEDEC — the hardware layer below NVMe and PCIe.

Taxonomy: By committee: JC-42 (DRAM) · JC-64 (Flash) · JC-11 (Mechanical) · Free vs member specs
DDR/LPDDReMMC/UFSSSD endurance (JESD218)Module standardsSerial presence detect
systems
VESAIndustry consortium

VESA Standards & DisplayPort

Monitor connectors, HDR certification, and desk mount hole patterns are VESA specs — ubiquitous but rarely cited by name.

Taxonomy: By standard family: DisplayPort · DisplayHDR · Adaptive-Sync · Mount · EDID/DPID
DisplayPortDisplayHDRAdaptive-SyncFlat Display Mounting InterfaceEDID
systemsmedia
HDMIIndustry consortiumPaid access

HDMI Forum Specifications

HDMI 2.1 features (4K120, VRR, eARC) are HDMI Forum specs — parallel to VESA DisplayPort for display transport.

Taxonomy: By HDMI version · Feature modules · Compliance test specs
HDMI 2.1eARCVRR/ALLMUltra High Speed CableCompliance testing
systemsmedia
RISC-VStandards body (SDO)In Rundown

RISC-V International Specifications

Every RISC-V CPU implements ratified ISA modules from riscv.org/specifications — the open alternative to ARM/x86 ISAs.

Taxonomy: By status: Ratified · Frozen · Draft · By extension letter · Profiles (RVA20, RVA22…)
Unprivileged ISAPrivileged architectureVector extension (V)Bit-manip (B)Profiles
systems
DWARFStandards body (SDO)In Rundown

DWARF Debugging Information Format

gdb, lldb, and perf rely on DWARF — the spec is maintained independently from ELF (gABI) and LLVM debug info.

Taxonomy: By DWARF version: 2 · 3 · 4 · 5 · 6 (draft) · Section-based reference
DWARF 5DWARF 4 (legacy)Call frame informationLocation descriptionsType units
systemsdata-formats
LLVMVendor / de-facto

LLVM Documentation & LangRef

Rust, Swift, Clang, and Julia target LLVM IR — LangRef is the practical spec for compiler and toolchain interoperability.

Taxonomy: By doc: LangRef · Bitcode · Extensions · Project-specific (Clang, MLIR, Flang)
LLVM Language ReferenceBitcode file formatClang C/C++ extensionsMLIRDebug info (DIBuilder)
systemsdata-formats
SMPTEStandards body (SDO)Paid access

SMPTE Standards

Broadcast IP video (ST 2110) and professional timecode (ST 12) are SMPTE — the production pipeline layer above consumer codecs.

Taxonomy: By ST number · Technology committee · Registered disclosure documents
ST 2110 (IP studio)ST 2084 (PQ HDR)Timecode (ST 12)MXFIMF
mediatelecom
DVBIndustry consortium

DVB Specifications

European and global broadcast receivers implement DVB spec families — parallel ecosystem to ATSC (US) and ISDB (Japan).

Taxonomy: By delivery: Terrestrial · Satellite · Cable · IPTV · By spec blueprint
DVB-T2DVB-S2/S2XDVB-C2DVB-I (IP)CI+ conditional access
mediatelecom
TM ForumIndustry consortium

TM Forum Open APIs & Frameworx

Telco BSS/OSS digital transformation standardizes on TM Forum Open APIs — the REST catalog for operator IT integration.

Taxonomy: By API component (TMF###) · Frameworx (eTOM, SID, TAM) · Open Digital Architecture
Open API catalog (TMF6xx/9xx)eTOMSID information modelOpen Digital Architecture (ODA)
telecomcloud
MEFIndustry consortium

MEF Standards

Enterprise WAN and carrier Ethernet SLAs reference MEF service definitions — parallel to IETF protocol specs for operator services.

Taxonomy: By service type: Ethernet · SD-WAN · SASE · LSO APIs · Certification
Carrier Ethernet (CE 2.0)SD-WANSASELSO Sonata/Legato APIsMEF 3.0
telecomnetworking
SIP ForumIndustry consortium

SIP Forum Technical Recommendations

Enterprise SIP trunking (SIPconnect) and robocall mitigation (STIR/SHAKEN) deployment guides are SIP Forum — atop IETF SIP RFCs.

Taxonomy: By recommendation: SIPconnect · STIR/SHAKEN · IPv6 · Testing · Security advisories
SIPconnectSTIR/SHAKENSIP over IPv6Interop testingSecurity advisories
telecom
OPC UAIndustry consortium

OPC Foundation Specifications

Factory floor, SCADA, and Industry 4.0 integrations standardize on OPC UA — the industrial protocol catalog beyond MQTT.

Taxonomy: By part number (Part 1–14+) · Companion specs · Profiles · Online reference
OPC UA core (Parts 1–7)PubSubInformation modelsCompanion specsCertification profiles
iotsystems
OMGStandards body (SDO)

Object Management Group

UML/BPMN diagrams and DDS real-time pub/sub middleware trace to OMG — common in aerospace, defense, and enterprise architecture.

Taxonomy: By specification category: Modeling · Middleware · Domain · By formal/ beta status
UML 2.xBPMN 2.0DDSSysMLCORBA (legacy)
systemscloudiot
FIXIndustry consortium

FIX Trading Community

Equity and FX trading integrations speak FIX — the tag/value message dictionary is versioned and indexed by the FIX Trading Community.

Taxonomy: By FIX version: 4.0–5.0SP2 · Extension packs · EPICS (standards proposals) · Orchestra (machine-readable rules)
FIX 4.4FIX 5.0 SP2FIX OrchestraFIX LatestExtension packs
clouddata-formats
GS1Standards body (SDO)

GS1 Standards

Every UPC/EAN barcode and warehouse scan event maps to GS1 identifiers — the physical-world naming layer for logistics and retail.

Taxonomy: By standard: Identification · Barcodes · EPC/RFID · EPCIS · Digital Link · GDSN
GTIN / barcodesEPCIS 2.0GS1 Digital LinkGDSNApplication Identifiers
iotdata-formats
DICOMStandards body (SDO)

DICOM Standard (NEMA)

Hospital PACS, CT/MRI exports, and radiology workflows use DICOM — a massive tagged data dictionary indexed by PS number.

Taxonomy: By PS number (Part 1–20+) · IOD index · SOP classes · Transfer syntaxes
File format & media storageNetwork communicationIOD dictionarySOP classesStructured reporting
healthcaredata-formats
HL7Standards body (SDO)

HL7 International Standards

Legacy hospital HL7v2 ADT/ORU feeds and CDA clinical documents remain ubiquitous — FHIR is one branch of the HL7 catalog.

Taxonomy: By product line: FHIR · V2 · V3/CDA · CDA · SMART · Implementation Guides
FHIR R4/R5HL7 v2.x messagingCDA R2SMART on FHIRImplementation Guides
healthcarecloud
Apache ASFMeta-indexIn Rundown

Apache Software Foundation Projects

Data infrastructure specs (Parquet, Avro, Arrow) live under Apache — broader than the Parquet/Arrow entry alone.

Taxonomy: By category: Big Data · Web · Libraries · Incubator · Attic
Big Data (Kafka, Spark, Hadoop)Web servers (httpd, Tomcat)Formats (Parquet, Avro, Arrow)Lucene/Solr
clouddata-formatsmeta
EclipseMeta-index

Eclipse Foundation Specifications

Sparkplug B industrial MQTT and Jakarta REST/JMS specs are Eclipse — major specs outside Apache and CNCF.

Taxonomy: By working group: IoT · Jakarta EE · IDE · Research · Specification projects
Jakarta EESparkplug (IoT)Eclipse IoTOpen VSXAdvisory council specs
iotcloudmeta
PEPsCode-point registry

Python Enhancement Proposals

Python packaging (pyproject.toml), type hints, and stdlib behavior are specified as PEPs — the language's RFC equivalent.

Taxonomy: By PEP number · Status (Accepted/Final/Deferred) · Type (Standards Track/Informational/Process)
Standards TrackInformationalProcessTyping & packaging PEPs
data-formatscloud
SPDXIndustry consortium

SPDX Specification

SBOM mandates (US EO 14028, EU CRA) reference SPDX — the license ID list and SBOM tag-value/JSON format spec.

Taxonomy: By SPDX version: 2.3 · 3.0 · License list · SBOM profiles · Use cases
SPDX 2.3 SBOMSPDX 3.0 modelLicense ListISO/IEC 5962Conformance profiles
securitycloud
CycloneDXIndustry consortium

CycloneDX Specification

Many SCA tools default to CycloneDX JSON/XML alongside SPDX — ECMA-424 normative spec with VEX and attestations.

Taxonomy: By version: 1.5 · 1.6 · By use case: SBOM · VEX · Attestations · ML-BOM
CycloneDX SBOMVEX (Vulnerability Exploitability)AttestationsECMA-424Tool center
securitycloud
OpenSSFIndustry consortium

OpenSSF Best Practices & Scorecards

SLSA provenance levels and OpenSSF Scorecards are the practical OSS security maturity frameworks — under Linux Foundation.

Taxonomy: By project: Scorecards · SLSA · Sigstore · Best Practices Badge · Working groups
OpenSSF ScorecardsSLSASigstoreBest Practices BadgeAlpha-Omega
securitycloud
WikipediaMeta-index

Wikipedia List of File Formats

Not normative, but the fastest way to discover what a format is called and find the real spec link — referenced throughout Rundown file format entries.

Taxonomy: Alphabetical · By category (audio, video, archive, document…) · Cross-linked articles
Alphabetical listCategory: file formatsComparison tablesSee-also chains
metadata-formats
OpenAPIIndustry consortium

OpenAPI Initiative

OpenAPI 3.1 is the de-facto REST API contract format — spec versions published at spec.openapis.org.

Taxonomy: By OAS version: 3.0 · 3.1 · 2.0 (Swagger)
OpenAPI 3.1OpenAPI 3.0Swagger 2.0 (legacy)
cloudweb
JSON SchemaIndustry consortium

JSON Schema

API request/response validation and OpenAPI schemas trace to JSON Schema drafts — indexed by version at json-schema.org.

Taxonomy: By draft version: 2020-12 · 2019-09 · draft-07 · draft-04
Draft 2020-12Draft 2019-09Understanding JSON Schema (guide)
cloudwebdata-formats
AsyncAPIIndustry consortiumIn Rundown

AsyncAPI Specification

AsyncAPI is the OpenAPI equivalent for pub/sub and streaming APIs — versioned spec at asyncapi.com.

Taxonomy: By AsyncAPI version: 3.0 · 2.x
AsyncAPI 3.0AsyncAPI 2.6Bindings (MQTT, Kafka, HTTP…)
cloudiot
GraphQLIndustry consortiumIn Rundown

GraphQL Foundation

GraphQL spec versions are published at spec.graphql.org with a clear edition index (June 2018, October 2021…).

Taxonomy: By edition date: October 2021 · June 2018 · Working draft
Language specificationType systemIntrospectionExecution
cloudweb
ProtobufVendor / de-factoIn Rundown

Protocol Buffers

Proto3 syntax, wire encoding, and language guides are indexed at protobuf.dev — separate from gRPC transport specs.

Taxonomy: By topic: Language guide · Wire format · Style guide · Well-known types
Proto3 language guideWire formatLanguage implementationsWell-known types
clouddata-formats
ApacheIndustry consortiumIn Rundown

Apache Parquet & Arrow

Data lake and analytics pipelines standardize on Parquet file layout and Arrow IPC — specs at apache.org project sites.

Taxonomy: Per-project documentation: Parquet format · Arrow columnar · ORC (separate project)
Parquet file formatArrow IPC / FeatherArrow C Data interface
data-formatscloud
CSAIndustry consortiumIn Rundown

Connectivity Standards Alliance

Matter device spec and certification requirements are CSA — the index spans Matter core, clusters, and device types.

Taxonomy: By solution: Matter · Zigbee · Z-Wave · Thread · Certification
Matter specificationZigbee PROZ-Wave Long RangeThread (with Thread Group)
iot
LoRa AllianceIndustry consortiumIn Rundown

LoRa Alliance Specifications

LoRaWAN spec versions and regional frequency parameters are published and versioned by the LoRa Alliance.

Taxonomy: By spec version · Regional parameters · Certification program
LoRaWAN L2/L3 specRegional parameters (RP)CertificationBackend interfaces
iottelecom
MatrixIndustry consortiumIn Rundown

Matrix Specification

Matrix spec versions are published at spec.matrix.org with a structured API index — the federated messaging alternative to XMPP.

Taxonomy: By API: Client-Server · Server-Server · Application Service · Push · Identity · Room versions
Client-Server APIServer-Server federationApplication Service APIPush GatewayRoom version specs
iottelecom
OMAIndustry consortiumIn Rundown

OMA SpecWorks

LwM2M (IoT device management) and MMS message formats are OMA specs — indexed by release at openmobilealliance.org.

Taxonomy: By release · By enabler (LwM2M, MMS, DM) · Approved vs candidate
LwM2MMMSOMA DMPushDigital Rights
iottelecom
HL7 FHIRStandards body (SDO)

HL7 FHIR

Healthcare API integrations (EHR, payers, apps) use FHIR resource catalog and REST spec at hl7.org/fhir.

Taxonomy: By FHIR version (R4, R5) · Resource index · Search parameters · Profiles
Resources (Patient, Observation…)RESTful APISearchBundlesImplementation Guides
healthcarecloud
INCITSStandards body (SDO)

INCITS Technical Committees

US participation in ISO/IEC IT standards flows through INCITS committees — find the US entry point for POSIX, C, SQL, etc.

Taxonomy: By INCITS committee · By standard number · ISO/IEC adoptions
JTC 1 TAGProgramming languagesCharacter setsStorage interfaces
systemsdata-formats
Open GroupStandards body (SDO)In Rundown

The Open Group Standards

POSIX.1 is the portable Unix API — published and indexed by The Open Group, co-maintained with IEEE.

Taxonomy: By standard family: POSIX · UNIX · TOGAF · ArchiMate · Open Footprint
POSIX.1Single UNIX SpecificationTOGAFArchiMateUNIX certification
systems
Bluetooth SIGIndustry consortium

Bluetooth SIG Specifications

Web Bluetooth, BLE devices, and audio accessories all implement Bluetooth SIG specs — indexed by core version and profile.

Taxonomy: By spec type: Core · Mesh · Profiles · GATT · Assigned Numbers
Core SpecificationMeshLE AudioGATT profilesAssigned Numbers
iotsystems
CNCFMeta-index

CNCF Cloud Native Landscape

Cloud-native infrastructure projects live here — useful for finding which foundation owns a protocol vs a product.

Taxonomy: By maturity: Graduated · Incubating · Sandbox · By category (Orchestration, Observability, Runtime…)
Graduated projectsIncubatingSandboxTrail map categories
cloudmeta