You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to suggest that we allow bot:adjacentElement to also be used as a relationship between two elements since it is probably quite confusing for most people that this is disallowed now and I think we should strive towards having an easily understandable representation of the building.
Current state: bot:adjacentElement is an rdfs:subClassOfbot:hasElement. bot:hasElement has the rdfs:domain constrained to bot:Zone.
Therefore using bot:adjacentElement between two elements would infer 1) the bot:hasElement relationship between the two and 2) that the subject element is a bot:Zone.
Suggestion:
Either the bot:adjacentElement should no longer be an rdfs:subClassOfbot:hasElement or the rdfs:domain constraint should be removed on the bot:hasElement. I am in favour of the latter since this makes the ontology less restrictive and easier to use.
The text was updated successfully, but these errors were encountered:
I would like to suggest that we allow
bot:adjacentElement
to also be used as a relationship between two elements since it is probably quite confusing for most people that this is disallowed now and I think we should strive towards having an easily understandable representation of the building.Current state:
bot:adjacentElement
is anrdfs:subClassOf
bot:hasElement
.bot:hasElement
has therdfs:domain
constrained tobot:Zone
.Therefore using
bot:adjacentElement
between two elements would infer 1) thebot:hasElement
relationship between the two and 2) that the subject element is abot:Zone
.Suggestion:
Either the
bot:adjacentElement
should no longer be anrdfs:subClassOf
bot:hasElement
or therdfs:domain
constraint should be removed on thebot:hasElement
. I am in favour of the latter since this makes the ontology less restrictive and easier to use.The text was updated successfully, but these errors were encountered: