infer relation between a Storey and adjacentElement of a Space #23
Comments
|
?Hi,
That is true, but I don't think we really need that "relatedElement" property in BOT. Many things are 'related'. I would opt to keep BOT concise and not include that property to be honest.
Pieter
…________________________________
Van: mathib <notifications@github.com>
Verzonden: dinsdag 15 mei 2018 16:46
Aan: w3c-lbd-cg/bot
CC: Subscribed
Onderwerp: [w3c-lbd-cg/bot] infer relation between a Storey and adjacentElement of a Space (#23)
If bot:containsElement is used from a bot:Space to a bot:Element, e.g.
inst:storey1 bot:hasSpace inst:spaceA .
inst:spaceA bot:containsElement inst:deskA .
one can infer correctly:
inst:storey1 bot:containsElement inst:deskA .
However, if bot:adjacentElement is used from a bot:Space to a bot:Element, e.g.
inst:storey1 bot:hasSpace inst:spaceA .
inst:spaceA bot:adjacentElement inst:wallA .
one cannot infer the following using BOT (which is correct):
inst:storeyA bot:containsElement inst:wallA .
This comes because this adjacent wall element can be adjacent to OR contained in the storey that contains the space, depending if the wall is resp. external or internal. If BOT would define a superproperty for bot:adjacentElement and bot:containsElement (e.g. bot:relatedElement), then one could infer from the above example with a propertyChainAxiom on bot:relatedElement (bot:containsZone bot:adjacentElement) that:
inst:storey1 bot:relatedElement inst:wallA .
The data modeler would have to define more precisely what the relation is between the storey and the wall: bot:containsElement or bot:adjacentElement.
-
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#23>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABjr0umQ1ciQWIonDruU8N7V-Mcojv3kks5tyupdgaJpZM4T_sam>.
|
|
It would be useful to find the storeys and all elements that are related with an easier query. The naming could be changed to something as |
|
Also there could be a need for querying all elements that are somehow related to a building. I think we should consider this. Currently a Facility Manager cannot make a query for all windows of a certain building. Only if it is explicitly defined that they are adjacent to that building. We cannot infer that something which is adjacent to a space in the building is also adjacent to the building itself as it could be an internal window. I have thought about this before. |
|
=> add hasElement property in BOT that is a superProperty of bot:containsElement and bot:adjacentElement. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If bot:containsElement is used from a bot:Space to a bot:Element, e.g.
one can infer correctly:
inst:storey1 bot:containsElement inst:deskA .However, if bot:adjacentElement is used from a bot:Space to a bot:Element, e.g.
one cannot infer the following using BOT (which is correct):
inst:storeyA bot:containsElement inst:wallA .This comes because this adjacent wall element can be adjacent to OR contained in the storey that contains the space, depending if the wall is resp. external or internal. If BOT would define a superproperty for bot:adjacentElement and bot:containsElement (e.g. bot:relatedElement), then one could infer from the above example with a propertyChainAxiom on bot:relatedElement (bot:containsZone bot:adjacentElement) that:
inst:storey1 bot:relatedElement inst:wallA .The data modeler would have to define more precisely what the relation is between the storey and the wall: bot:containsElement or bot:adjacentElement.
The text was updated successfully, but these errors were encountered: