Both seem reasonable. I’d call the extra filter something like “semantic” and by default it will search for the given tag(s) and below. That should capture any custom tags a user may create.
I’m not sure that we should exclude Property tags though. I could definitely see wanting to do stuff like limit the list to Setpoint/Temperature but exclude Measurement/Temperature. Without the Property tag I’d get all the setpoints, not just Temperature. This may not be the best example as the tag also matches a dimension, but there isn’t a one-to-one mapping between dimensions and semantic Property tags. One cannot always use the type for filtering like this.
Note that I’m seeing use cases wider than just eliminating the Semantically tagged Groups. Using the semantic model to help filter I think could be quite useful, particularly for stuff like semanticHomeMenu Part 3 - Security [4.0.0.0;5.0.0.0].
I was wondering about that. How do I use the pick from model from a property like this? I could only figure out how to get the list of Items, so I focused on that. But being able to pick from the model would be a really nice option. I’m not sure if there is a need to filter with the model picker. Everything is presented hierarchically so the need to narrow the list down isn’t as important.
I think this is related to the question I had for @ysc above. I think there are contexts that I don’t know about built into MainUI. I don’t know where to look to find them.