SIG Implementation Checks¶
Maintainers use two repository scripts to cross-check GATT implementations against Bluetooth SIG sources. These are optional, local checks—not part of the contributor quality gates in Contributing.
Scope and backlog¶
What is implemented, planned, and out of scope is documented in Registry Coverage. Use that reference when deciding whether a gap belongs in this repository.
Spec table validation¶
scripts/validate_service_characteristics_from_specs.py compares characteristics tables from extracted spec text to classes under src/bluetooth_sig/gatt/services/.
Fetch spec HTML using Fetching SIG Specs in .github/copilot-instructions.md. Prepare text extracts and run the script; see its module docstring and python scripts/validate_service_characteristics_from_specs.py --help for file layout, --spec-dir, --pattern, and exit codes.
YAML coverage report¶
scripts/gatt_coverage_report.py reports YAML-defined UUIDs versus Python implementations for characteristics, services, and descriptors. See python scripts/gatt_coverage_report.py --help for usage.
Runtime validation (applications)¶
For checking a concrete device service at runtime, use validate_service() on service classes—see Service Validation. That API is separate from the maintainer spec-table script above.
See Also¶
Adding Characteristics — Implement new characteristics and services
Registry Coverage — Implementation status and roadmap
Contributing — Pull requests and quality gates