-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[XML] Align chip-types.xml with the spec while making a nod towards the data model number allocation #28976
Labels
Spec XML align
SDK XML does not match the spec (including naming, etc)
Comments
robszewczyk
added
the
Spec XML align
SDK XML does not match the spec (including naming, etc)
label
Aug 31, 2023
robszewczyk
added a commit
to robszewczyk/connectedhomeip
that referenced
this issue
Aug 31, 2023
* reordered the XML to use the same order as the spec; this should make maintenance a bit more sane * renumbered types to avoid duplication and conflicts and to align with the spec Fixes project-chip#28976
github-project-automation
bot
moved this from Todo
to Done
in [Enhancements] Spec/XML Alignment
Sep 5, 2023
mergify bot
pushed a commit
that referenced
this issue
Sep 5, 2023
* Aligned chip-types.xml with the latest Matter spec * reordered the XML to use the same order as the spec; this should make maintenance a bit more sane * renumbered types to avoid duplication and conflicts and to align with the spec Fixes #28976 * Regen ZAP * Reflect the type changes in the Python codegen per code review comment * Add XSD validation for unique IDs * Add a unique constraint on the `id` element in `<type/>` sequence * Add chip-types.xml to the validator script
abpoth
pushed a commit
to abpoth/connectedhomeip
that referenced
this issue
Sep 12, 2023
* Aligned chip-types.xml with the latest Matter spec * reordered the XML to use the same order as the spec; this should make maintenance a bit more sane * renumbered types to avoid duplication and conflicts and to align with the spec Fixes project-chip#28976 * Regen ZAP * Reflect the type changes in the Python codegen per code review comment * Add XSD validation for unique IDs * Add a unique constraint on the `id` element in `<type/>` sequence * Add chip-types.xml to the validator script
HunsupJung
pushed a commit
to HunsupJung/connectedhomeip
that referenced
this issue
Oct 23, 2023
* Aligned chip-types.xml with the latest Matter spec * reordered the XML to use the same order as the spec; this should make maintenance a bit more sane * renumbered types to avoid duplication and conflicts and to align with the spec Fixes project-chip#28976 * Regen ZAP * Reflect the type changes in the Python codegen per code review comment * Add XSD validation for unique IDs * Add a unique constraint on the `id` element in `<type/>` sequence * Add chip-types.xml to the validator script
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
IDs for data types are not used in Matter over the wire, so there is no impact to interop, and the SDK can readily be changed. Align the https://github.com/project-chip/connectedhomeip/blob/master/src/app/zap-templates/zcl/data-model/chip/chip-types.xml with the Matter spec in line with changes in https://github.com/CHIP-Specifications/connectedhomeip-spec/pull/7054
The text was updated successfully, but these errors were encountered: