OpenCamInterop: offline executable fixtures for ONVIF notification edge cases #835
Unanswered
elkampu
asked this question in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We have released OpenCamInterop v0.1.0-alpha.1, an Apache-2.0 .NET library and CLI for turning sanitized camera-event quirks into deterministic offline tests.
The current ONVIF slice accepts bounded, caller-supplied WS-Notification
Notifyand EventPullMessagesResponseXML, normalizes each notification to a deterministic CloudEvent, and can replay fixture cases as NDJSON. It contains no camera discovery, subscription, credential, or network client. It is not an ONVIF conformance or certification tool.The baseline is deliberately small: two synthetic ONVIF payloads, zero externally derived behavior cases, and zero independent consumers. We are looking for implementer feedback about notification behavior that is difficult to test consistently—namespace variation,
PropertyOperation, batching or ordering, reconnect duplicates, or bounded vendor extensions are examples.Please do not post a raw device export or private payload. A short behavior description is enough to start; a contribution should ultimately reduce it to a minimal synthetic XML fixture plus an executable expected result. The safety and evidence rules are in the fixture guide, and the focused request is issue #3.
All reactions