Skip to content

wish list item placeholder: better scoping on what applies to what #2

@epaulson

Description

@epaulson

Setting aside the "where should wish list items go" for a moment, one thing I would like to do in Brick 2.0 is do a better job in limiting what points and relationships etc can target. Right now they're usually set to the very top level classes so it's hard to do anything with them. Like, we say its permitted to put chilled water flow sensors on equipment, which means that it's permitted to have them on an ethernet switch. Or if you look at all the properties /relationships that apply to an elevator - https://ontology.brickschema.org/brick/Elevator.html. it's got "tilt", which at least in any elevator I want to get in had better always be 0 degrees.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions