This pull request has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/openhab-5-semantic-model-proposal/162526/96

@mherwege can I kindly ask you to be a sparring partner for this PR? My goal is to allow developers to set a (proposed) semantic (equipment) tag in their thing type xml, and have this permeated through the thing type instances to the actual thing instances so that the UI can use that semantic (equipment) tag (as a hint) in creating a semantic model.

@mherwege can I kindly ask you to be a sparring partner for this PR? My goal is to allow developers to set a (proposed) semantic (equipment) tag in their thing type xml, and have this permeated through the thing type instances to the actual thing instances so that the UI can use that semantic (equipment) tag (as a hint) in creating a semantic model.

@andrewfg Sure. I like the idea as long as it does not then enforce anything on the item semantics. So I would think that it should be carried to the point of a having a tag on the thing, but then it should be up to the UI to pick this up as a suggested equipment semantic when creating the group item with its points (create model from thing).
As it should not be used on the thing directly, except when creating items, I am wondering what it should be called. Some day someone may think it carries meaning beyond a suggestion for an equipment group item, and may want to also show that in the UI...

Indeed. The tags in the ChannelType xml are hints for semantic “point” and semantic “property” tags which are intended for functional Item creation. And the single tag in the ThingType xml would be a hint for the semantic “equipment” tag intended for semantic GroupItem creation. The remaining “location” semantic tag is entirely user dependent and would not come from the xml.

PS we could even explicitly name it equipmentTag ..

Obviously it needs work now on the OH WebUI side in order to utilise this semanticEquipmentTag when creating the semantic model. => @mherwege :)

I don't think this is a very complex change in the UI. I can take care of it, but would prefer to finish the core code first. There are a lot of moving parts and dependencies here, and creating a core that has it all for testing a UI change against is a bit of a challenge. It will be easier to do when we get the core changes over the line first.

It will be easier to do when we get the core changes over the line first.

@mherwege understood. IMHO all the changes in OH Core are ready to merge (via this PR). So it would be helpful if you can review this and give LGTM so that we can indeed proceed to merge it.

Ping @ccutrer apropos our discussion on Equipment tags

@andrewfg May I ask you to rebase this PR?

May I ask you to rebase this PR?

@kaikreuzer done! Apparently the CI / JavaDoc test failed but I don't know why.

@andrewfg the log of the javadoc job needs improvement. Running it locally, I see the message causing it to fail:

[WARNING] Javadoc Warnings
[WARNING] openhab-core\bundles\org.openhab.core.thing\src\main\java\org\openhab\core\thing\Thing.java:246: warning: @param argument "tag" is not a parameter name.
[WARNING] * @param tag the semantic (equipment) tag or {@code null} if no tag has been configured.