This is one of the details we need to sort out in the beginning of a new specification life cycle…
The goal is always to not change released specs in areas where it breaks compatibility with older versions. The profile URIs are critical parts of the spec, changing them will break compatibility. The mentioned areas in the spec that need updates are more clarifications about expected behaviour that is not defined detailed enough. These missing details are typically found during product implementations, interoperability testing and during the development and use of the compliance test tool.
The good news is that the compliance test tool development makes good progress.
I fully agree with your statement:
This is why the OPC-UA interop and test lab need to happen![/quote]
At the moment it is important to test products with demo servers / clients based on the different SDKs and stack versions. I assume you are already testing with the .NET SDK from the OPC Foundation.
You should also test with the C++ based UA Demo Server and UaExpert (client) provided by Unified Automation. You can find free downloads at
A lot of commercial C++ based OPC UA servers are based on the same C++ SDK that was used to build this demo server.
I assume you are also providing demo downloads of your product. I will recommend to Unified Automation that they test releases of their SDK with your server and client. Is there a special version or component they should use for testing?