Skip to content

Add DeviceManagementService V2.4 schema candidate - #31

Draft
MarcLeinenDE wants to merge 1 commit into
VDVde:masterfrom
MarcLeinenDE:candidate/dms-v2.4-xsd
Draft

Add DeviceManagementService V2.4 schema candidate#31
MarcLeinenDE wants to merge 1 commit into
VDVde:masterfrom
MarcLeinenDE:candidate/dms-v2.4-xsd

Conversation

@MarcLeinenDE

Copy link
Copy Markdown

Summary

This pull request adds a DeviceManagementService V2.4 XSD candidate and includes the required V2.4 schema dependencies so the candidate can be reviewed and used as a self-contained reference state.

Scope

Added:

  • IBIS-IP_DeviceManagementService_V2.4.xsd
  • IBIS-IP_common_V2.4.xsd
  • IBIS-IP_Enumerations_V2.4.xsd

Adjusted:

  • IBIS-IP_TicketValidationService_V2.4.xsd now includes IBIS-IP_Enumerations_V2.4.xsd for V2.4 schema-family consistency.

DeviceManagementService V2.4 derivation

The DMS V2.4 schema candidate is derived conservatively from the existing official IBIS-IP_DeviceManagementService_V2.2.xsd and the documented technical corrections in VDV-Schrift 301-2-0 DeviceManagementService V2.4.

Reflected DMS V2.4 changes:

  • GetDeviceErrorMessagesResponseData/ErrorMessage: changed from mandatory minimum 10 entries to optional 0..*.
  • SubdeviceErrorMessages/ErrorMessage: changed from mandatory minimum 10 entries to optional 0..*.
  • DeviceStatusImpact: optional.
  • DeviceStatusPriority: optional.
  • InstallUpdateRequest: UpdateID, UpdateTimestamp, and UpdateURL optional.
  • Existing optional fields UpdateFileChecksum and UpdateFileSize remain optional.

Unchanged intentionally:

  • UpdateStateData.UpdateTimestamp remains mandatory.
  • UpdateHistoryEntry.UpdateTimestamp remains mandatory.
  • UpdateHistoryEntry.UpdateURL remains mandatory.
  • DeviceStatusName and DeviceStatusFlag remain mandatory.

Why common/enumerations V2.4 are included

The current upstream TicketValidationService V2.4 already references IBIS-IP_common_V2.4.xsd, but the file is not present in the repository. Other existing/open V2.4 candidate work also follows the V2.4 schema-family direction. Including common V2.4 and Enumerations V2.4 here makes this DMS V2.4 candidate reviewable and usable without requiring consumers to assemble the dependency files manually from forks or open pull requests.

Notes

This is opened as a draft to make the candidate and its scope visible for review and discussion before marking it ready.

Add a conservative DeviceManagementService V2.4 schema candidate derived from the existing official DeviceManagementService V2.2 schema and the documented V2.4 changes.

Also include the V2.4 common/enumeration schema dependencies and align TicketValidationService V2.4 to use the V2.4 enumerations include.
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.

1 participant