Replies: 2 comments
-
That is an advanced feature that would make IDS more complicated, let's first make sure there is enough demand for it. Please add your vote if you find this feature worth considering by the group for future versions of the IDS standard. Examples of what you plan to use it for are also welcome. I can think of sanity checks like "GrossVolume" > "NetVolume". |
Beta Was this translation helpful? Give feedback.
-
At some point we'll likely get to this, some form of function evaluation or relational predicates instead of a direct unary value to compare to. But I think the increase in complexity is large and the utility gained from this is fairly low. You can also see this in the IFC Express schema. In the end we didn't actually write a lot of rules (but some of them are very powerful and valuable), but the increase in complexity of being able to evaluate them is huge. You can also think of rules like: is my date actually valid: "29th of Feb only allowed on leap years", etc. People will likely ask for this at some point, but the amount of intellectual effort required to encode this in the standard is most likely not worth it unless we have researched and grouped a wider set of use cases that can be addressed preferably by using a pre-existing vocabulary. |
Beta Was this translation helpful? Give feedback.
-
From Mohit Mangal (SBI International): Current IDS do not support checking using the comparison of two values (E.g., “Warranty End Date” to be later than the “Warranty Start Date”) Good to allow such comparisons.
Beta Was this translation helpful? Give feedback.
All reactions