Skip to content

Conversation

@appsdesh
Copy link
Contributor

Formatting, device compliance change

closes #311

Formatting, device compliance change
@appsdesh appsdesh requested a review from a team as a code owner December 16, 2025 17:20

## Device Compliance Change

In order to support notifying and responding to changes in device compliance status, implementations MUST support the event type `device-compliance-change`. This event is used to signal that a device's adherence to a set of security or organizational compliance policies has changed. implementations MUST support the following field values:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this line is too long... can you fix the formatting so the line breaks are correct.
The linter should also catch this.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

won't the kramdown / xml2rfc tools take care of the line length?

@thomasdarimont
Copy link
Contributor

Any update on this? We need this to be merged for the SSF Transmitter certification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CAEP Interop Profile - Add Device Compliance Change to the supported use-cases

5 participants