buildingSMART / buildingSMART/IFC4.x-development

Is the IfcWorkSchedule project declaration mutually exclusive to aggregation within a relating IfcWorkPlan?

Open
#321 2 comments 0 reactions 0 assignees View on GitHub
allocated-sequence ifc-update-out proposal
Dominant language
Python
Stars
234
Forks
123
Avg merge
15h 4m
Merged PRs (30d)
5

Description

Originally posted https://forums.buildingsmart.org/t/is-the-ifcworkschedule-project-declaration-mutually-exclusive-to-aggregation-within-a-relating-ifcworkplan/3510

The IFC documentation describes two possible relationships on how an IfcWorkSchedule is related back to the IfcProject / IfcContext.

One scenario is that the IfcWorkSchedule is directly declared to the project.

![image|392x500](upload://52wh9P02s0qodZaIs5cmawFsgjq.png)

Another scenario is that the IfcWorkSchedule is aggregated to an IfcWorkPlan, and the IfcWorkPlan is then declared to the project.

![image|433x499](upload://t7zuNdoZKCBXssngtD8AVUdMCU4.png)

There are two potential interpretations:

1. An IfcWorkSchedule is **always** declared to the IfcContext, and may be additionally included as an aggregate to an IfcWorkPlan.
2. An IfcWorkSchedule is declared to the IfcContext, **unless** it is included as an aggregate to an IfcWorkPlan

Can someone clarify?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.