317 probematch behaviour potentially inconsistent (#339)

* Added note to DEV-47 to clarify behavior * Changelog update * Added note to DEV-47 to clarify behavior * Changelog update * Changelog update - 2nd attempt * Changelog update - 2nd attempt * Added note to DEV-47 to clarify behavior * Changelog update * Changelog update - 2nd attempt * Changelog update * debugging Changelog * Added note to DEV-47 to clarify behavior * Changelog update * Changelog update - 2nd attempt * Changelog update * Changelog update - 2nd attempt * Changelog update * debugging Changelog
IHE · Nov 20, 2024 · 5b03274 · 5b03274
1 parent 303935d
commit 5b03274
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 0 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -17,12 +17,16 @@ Each section shall contain a list of action items of the following format: `<bri
 
 ### Changes
 - Fixed action URN in waveform stream example ([#292](https://github.com/IHE/DEV.SDPi/issues/292))
+- Clarified intentionality of difference between ad-hoc and managed discovery ([#317](https://github.com/IHE/DEV.SDPi/issues/317))
 
 ### Editorial Fixes
 - Added deprecation notice for three requirements due to expected impact of BICEPS standard corrigendum ([#334](https://github.com/IHE/DEV.SDPi/issues/334))
 - Updated SDPi "Topic of Interest" issue management for clarity ([#274](https://github.com/IHE/DEV.SDPi/issues/274))
 - Addressed three JIRA tickets listed in issue ([#275](https://github.com/IHE/DEV.SDPi/issues/275))
 
+### Added
+
+-
 ## [1.4.1] - 2024-10-04
 
 ### Editorial Fixes

diff --git a/asciidoc/volume2/dev-47/tf2-dev-47.adoc b/asciidoc/volume2/dev-47/tf2-dev-47.adoc
@@ -133,6 +133,8 @@ The {var_label_dev_47_message_probe_match} message is sent as part of the BICEPS
 
 The {var_label_dev_47_message_probe_match} message is sent whenever a <<vol1_spec_sdpi_p_actor_discovery_proxy>> receives a <<vol2_clause_dev_47_message_probe, {var_label_dev_47_message_probe}>> message that contains a <<payload_dev_47_probe_discovery_scope>> that matches zero or more <<vol1_spec_sdpi_p_actor_somds_provider>>'s <<term_discovery_scope>>s.
 
+NOTE: The <<vol1_spec_sdpi_p_actor_discovery_proxy>> always responds to the <<vol2_clause_dev_47_message_probe, {var_label_dev_47_message_probe}>> message of the <<vol1_spec_sdpi_p_actor_somds_consumer>> with a <<vol2_clause_dev_47_message_probe_match, {var_label_dev_47_message_probe_match}>> message, even when there are zero <<payload_dev_47_probe_discovery_scope>> matches. Thus, the <<vol1_spec_sdpi_p_actor_somds_consumer>> can always recognize whether the <<vol1_spec_sdpi_p_actor_discovery_proxy>> has completed the transaction. This is possible in this transaction because of the non-multicast nature of its <<vol2_clause_dev_47_message_probe, {var_label_dev_47_message_probe}>> and <<vol2_clause_dev_47_message_probe_match, {var_label_dev_47_message_probe_match}>> messages. The behavior is different in the <<vol0_transaction_summary_dev_24>> transaction, which uses multicast messaging.
+
 [#vol2_clause_dev_47_message_probe_match_semantics]
 ====== Message Semantics