IS04 Subscription updates about is-04 HOT 2 OPEN

I agree, I don't think changes to resource properties like the label should need the resources to be DELETEd from and then rePOSTed to the Registration API, so long as resource identifiers are being preserved - see Identifier Mapping.

We may have been assuming this was obvious best practice, but we know what they say about assumptions... The lack of documentation around subsequent modifications has recently been noted - see #177 - even though the Registration API itself clearly describes 200 OK as the response for resource updates.

There is also a known lack of automated testing for these kind of updates in the NMOS API Testing Tool because such updates can only be triggered via proprietary APIs or user interaction. At JT-NM Tested events, implementers were made aware if their products were spamming the Registry, but this was a manual process. The infrastructure currently being added to the Testing Tool for (semi)automated Controller testing - see AMWA-TV/nmos-testing#616 - may allow this kind of test case to be automated in the future.

from is-04.

Architecture Review Group review: place on backlog

from is-04.