Protocol scope and method
The inspector extracts common XML tags with a conservative text parser. It does not validate against a schema or preserve namespaces.
Find Item blocks, then extract DeviceID, Name and Status tags.
Diagnostic scenario
Paste a small redacted Catalog response body and inspect XML well-formedness, command type, sequence number, device list count and item identifiers. Compare declared SumNum and DeviceList Num with the actual item population before importing it.
How to interpret the result
Well-formed XML can still violate the GB/T profile, omit required elements or use a namespace and encoding the receiver does not expect. Catalog responses may be paged, so one message is not necessarily the complete inventory.
Input reference
- Catalog XML
- Example default: Sample input included
Common mistakes
- Using an unredacted production capture with vehicle, credential or network identifiers.
- Treating one paged Catalog response as the full device inventory.
- Treating a successfully parsed sample as standards compliance or interoperability proof.
Before using the result
- Confirm the protocol edition, transport framing and vendor profile before interpreting fields.
- Reconcile declared counts, actual Item elements and sequence numbers.
- Keep a redacted known-good and known-bad sample as a regression pair.
Questions to check during diagnosis
Does the GB/T 28181 Catalog XML Inspector leave my browser?
No application upload is used. Avoid putting sensitive production data in shareable URLs.
Is this a standards compliance test?
No. Confirm the edition and vendor profile with licensed documents and your target platform.
Offline diagnostic aid. Verify fields, version and vendor extensions before production use.