OptionalcalendarChild task globalIds (from IfcRelNests where this task is RelatingObject).
WorkSchedule globalIds that control this task via IfcRelAssignsToControl.
OptionaldescriptionOptionalidentificationOptionallongOptionalobjectOptionaloutputexpressIds of products this task OUTPUTS via IfcRelAssignsToProduct (the
task in RelatedObjects): the buildingSMART "task builds this product"
convention (#6749). Separate from the inputs so a round trip writes each
back as the relationship it came from. Absent ≡ []. Read both lists
through taskProductExpressIds (schedule-task-products.ts).
OptionaloutputglobalIds of the same products (aligned with outputProductExpressIds by index).
OptionalparentParent task globalId (from IfcRelNests where this task is in RelatedObjects).
OptionalpredefinedOptionalpriorityexpressIds of products assigned via IfcRelAssignsToProcess: the task's INPUTS.
globalIds of the same products (aligned with productExpressIds by index).
OptionalstatusOptionaltaskOptionalwork
WorkCalendar globalIds assigned to this task via IfcRelAssignsToControl (RelatingControl an IfcWorkCalendar rather than an IfcWorkSchedule/ IfcWorkPlan). Array, not a single id, for the same reason as
controllingScheduleGlobalIdsabove — the schema places no cardinality limit on IfcRelAssignsToControl per object, so a source file can assign more than one calendar (e.g. a base calendar plus a site-specific exception calendar) via separate relations. Optional: absent and[]are equivalent everywhere this is read, matchingchildScheduleGlobalIds's convention below — the extractor always populates it, but SDK-side producers that never touch calendars aren't forced to.