buildingSMART / buildingSMART/IFC5-development
EXPRESS functions and rules, and their successors
- Dominant language
- HTML
- Stars
- 220
- Forks
- 80
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 2
Description
EXPRESS functions and rules may find an equivalent in OCL (Object Constraint Language, a part of current UML specifications) if the future IFC modeling language is UML. Similarly, if the future modeling language were OWL, SHACL shapes could at least partly take over those aspects of the current EXPRESS model.
The transition from EXPRESS to other formal languages (UML was, at least initially, considered the successor of choice) should also be considered in this light. At the time of writing, it seems however that the focus is on serialization (JSON vs. STEP) rather that model level. What would be the next steps?
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the issue's discussion of EXPRESS, OCL, UML, OWL, SHACL, and the current focus on JSON versus STEP serialization. A useful outcome would be a decided set of next steps for addressing a model-level transition, rather than leaving the alternatives and scope open.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100