search

building-envelope-data / api

API specification to exchange data about building envelopes
MIT License
3 stars 1 forks source link

Ideas for future development #16

Open simon-wacker opened 4 years ago

simon-wacker commented 4 years ago

In GitLab by @christoph-maurer on Mar 24, 2020, 09:50

@simon-wacker I tried to list and prioritize possible next steps in planning.md 086f4112be52a1d2dc20b5150552c4bab75da608 . What do you think about it? When we agree, I would discuss it with Tilmann.

simon-wacker commented 4 years ago

In GitLab by @simon-wacker on Mar 24, 2020, 11:18

Sounds reasonable. I only have a vague idea though about what the domain specific additions to the schema mean and how big those additions are going to be. At some point we need to stop making ever more additions or at least slow the process down for the schema not to get out of hands; it still needs to be maintained and thoroughly validated with (real) example data and the amount of example data needed to validate the schema thoroughly grows exponentially in the size of the schema (if there are the properties x and y with two possible values each there are 2*2=4 possible states and if you add the property z again with two possible values then there are 2*2*2=8 possible states; of course in example data we don't need to validate all states but the amount of proper example data still grows rather fast).

simon-wacker commented 4 years ago

In GitLab by @simon-wacker on Mar 24, 2020, 11:22

Sidenote: You can not just link the commit with the changes to planning.md but also an HTML representation of the document generated by GitLab Changes you make to the file planning.md in subsequent commits will be reflected in this file (but not in the link to the commit you put in the description).

simon-wacker commented 4 years ago

In GitLab by @christoph-maurer on Mar 24, 2020, 16:00

Thank you, Simon! For building envelopes and especially 'optical', 'calorimetric' und 'photovoltaic', we were in need to create a data schema because there were no suitable ones. For all other topics, we cannot handle large amount of properties. Therefore, I try to stick with existing formats such as IFC and Revit.