MDPWS Profiling for Relevant Message Element Requirements

[ToddCooper]

Section Number

TF2A Appendix 2:A ISO/IEEE 11073 SDC / MDPWS Message Specifications (Normative)

Priority

• Medium: Significant issue or clarification. Requires discussion, but should not lead to long debate.

Issue

The 11073-20702 MDPWS standard references significantly more DPWS content than is required for use in SDC. As the community moves toward verification testing and conformity assessment, the lack of clarity as to what is required for SDPi connectivity and what is optional but not necessary, potentially results in unnecessary test cases for capabilities that are out-of-scope for SDC and SDPi.

Proposed Change

Craft additional MDPWS message profiling guidance and update to TF2A as appropriate.

[d-gregorczyk]

I need at least some examples of those non-used messaging content. I don't even know where to start here.

[ToddCooper]

Gemini CA & Tooling 2024.05.02 Discussion: Reviewed the intent of this issue, updated the issue wording. Confirmed the concept.

[ToddCooper]

SDPi Workshop 3 2024.06.04:

Clarified what was intended to be "scoped out" via profiling. For example,

1. Referenced profiles from the MDPWS specification that reference others etc. But not all are needed
2. Not just message content but all other content that doesn't need to be implemented.

Requires further investigation to identify what should be included in this list.
Update list to a new section in TF-2A MDPWS

APPROACH:

1. Create an initial list based on some obvious examples
2. Update in future revisions as additional items are identified
3. Include a DISCLAIMER that the list is not comprehensive

[ToddCooper]

SDPi Workshop #4 -

@d-gregorczyk - Status update? 2.0 or 2.1 or later?

[d-gregorczyk]

2.1 at least; there is currently no capacity to identify all non-used contents.