[semantics] Add ActionService to support using Semantics features in Rules #2088
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cweitkamp
changed the title
Signed-off-by: Christoph Weitkamp <[email protected]>
cweitkamp
force-pushed
the
feature-semantics-in-rules
branch
from
c05ae47 to
92ca7ac
Compare
kaikreuzer
approved these changes
Feb 27, 2021
kaikreuzer
changed the title
|
This pull request has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/openhab-3-1-milestone-discussion/116025/25 |
|
This pull request has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/access-oh3-semantic-metadata-by-dsl-rules/118903/4 |
|
This pull request has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/how-to-use-new-actionservice-for-semantics-in-rules/125844/1 |
|
This pull request has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/extending-blockly-with-new-openhab-commands/127169/409 |
splatch
pushed a commit
to ConnectorIO/copybara-hab-core
that referenced
this pull request
Jul 11, 2023
Signed-off-by: Christoph Weitkamp <[email protected]> GitOrigin-RevId: 191a629
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I like to use Semantic features in Rules. E.g. determine the location of an item. Regardless if it is a Point, an Equipment or a Location itself. Therefore I propose to add a bunch methods to be used in Rules. I submitted this as a draft because I am not sure if this is the preferred way to add such features.
boolean isLocation(Item)- checks if the given Item is is a Locationboolean isEquipment(Item)- checks if the given Item is is an Equipmentboolean isPoint(Item)- checks if the given Item is is a PointItem getLocation(Item)- gets the Location Item of the ItemClass<? extends Location> getLocationType(Item)- gets the Location type of the ItemItem getEquipment(Item)- gets the Equipment Item an Item belongs toClass<? extends Equipment> getEquipmentType(Item)- gets the Equipment type an Item belongs toClass<? extends Point> getPointType(Item)- gets the Point type of an ItemClass<? extends Property> getPropertyType(Item)- gets the Property type an Item relates toClass<? extends Tag> getSemanticType(Item)- gets the semantic type of an Item (i.e. a sub-type of Location, Equipment or Point)Signed-off-by: Christoph Weitkamp [email protected]