bSI-InfraRoom / bSI-InfraRoom/IFC-Specification
`IfcPropertTemplate` documentation for bounded value has to be updated
- Dominant language
- No language data
- Stars
- 27
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
an IfcPropertyBoundedValue has only one unit, and the measure type of all values (upper, lower, set point) shall be the same (enforced by where rules). So there is no secondary data type for bounded values - only IfcPropertyTableValue has two unit / measure type definitions.
NOTE: there seems to be an issue with the documentation of IfcPropertyTemplate.SecondaryMeasureType - P_BoundedValue should not be listed here, as it contradicts with the where rules at IfcPropertyBoundedValue. Should be added as a general issue on IFC4.3 (as it is not INFRA/RAIL specific).
_Originally posted by @TLiebich in https://github.com/bSI-InfraRoom/IFC-Specification/pull/191#discussion_r689334446_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the documentation for IfcPropertyTemplate.SecondaryMeasureType and the where rules for IfcPropertyBoundedValue. Check how P_BoundedValue is listed and compare it with the issue's distinction from IfcPropertyTableValue. Done means the bounded-value entry no longer lists a secondary measure type and the IFC4.3 documentation is consistent with its where rules.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100