Please increase Mantis priority.
Just now (today) i already adjusted my CCS configuration tool and further tools corresponding to the description of Matthias: I eliminated the OPC UA namespace from the CCS UABinaryFileDataType.Namespaces list as it was/is specified and mandated by the /Part 81 1.00.02 Release/, F.2. Writing the OPC UA namespace to the UABinaryFileDataType.Namespaces list is a real bug in the /Part 81 1.00.02/ as already described. I will not roll back my latest code changes.
 Hence I expect that the priority of this Mantis is increased
 and corrected asap by the /Part 81 1.00.03/
 because this specification error is IOP relevant by using the standard CCS as specified in /Part 81/, Annex F: CM components must not expect the OPC UA namespace in the CCS UABinaryFileDataType.Namespaces list as required by /Part 81 1.00.02/. And vice versa Connection Editors must not write this OPC UA namespace to the UABinaryFileDataType.Namespaces list to ensure that those standard CCS can be loaded by CM components without failures.

This file format is for CCS information - and the http://opcfoundation.org/UA/FX/AC/ does not exist in a CCS - so I am confused by the requirement for this namespace in the configuration?

Removing the http://opcfoundation.org/UA/ namespace is just a textual update and can easily be accomplished (no nodeset changes required)

Paul you are right - I was refering to ConnectionEndpointTypeId NodeId in the Endpoint structure that contains typically a NodeId from the AC namespace.

But this is the NodeId related to the server where the endpoint is created and therefore the namespace table of the server entry is relevant.
I checked our namespace mapping code and it is using the related server namespace.

But we need Data and CM namespaces

updated text as described

reviewed in call closed issue