Clarification needed for Category and @Purpose|OPC UA Standard|Forum|OPC Foundation

I’m updating our own UA-stack from NodeSet2 V1.04 to the latest V1.05. We’re running the stack on a device with limited resources. Using V1.04 we were able to compile just the supported parts of the NodeSet.xml because they were split into different XML-files. According to the new V1.05 spec these separate files have been replaced by the the Category subnodes and @Purpose attribute on the nodes that shall be used to exclude nodes (see https://reference.opcfoundatio…..5/docs/F.3 and https://reference.opcfoundatio…../docs/F.11). Actually, I haven’t been able to implement the filtering process and generating correct and complete code using our xslt-based nodeset compiler.

Consider the UADataType-nodes: We don’t want to support Part 11 Historical Data Access. How do I exclude the DataType HistoryReadRequest (@NodeId=”i=662), for example? There’s no Category given for the DataType, thus no chance to exclude it. Are Category subnodes missing in the NodeSet2.Services.xml?

Please clarify how the filtering should be done in detail for the different node types. I’m aware of your comments on a similar topic focusing on a ready-to-use tool for filtering (see https://opcfoundation.org/foru…..eset2-xml/).