As per spec, table 3-3, Core Abstract Types definitions:
Schedule:
EMIX products are delivered for a Duration, at a particular time. EMIX relies on the Interval and the Gluon as defined in [WS-Calendar] to communicate Schedules. The Schedule names a collection, but is not itself a type.
Component:
Components are the individual parts of a Schedule defined by [WS-Calendar]. EMIX relies primarily on the Interval and the Gluon.
Product Description:
The Product Description is placed in Components of the Schedule. Product Description is derived from an abstract [WS-Calendar] type that resides within [WS-Calendar] Components, and all Product Description-derived types
The definition of Schedule doesn't say what a Schedule is.
The definition for 'Components' says
'Components are the individual parts of a Schedule.'
If so, why is the word 'Component' not in the definition of Schedule?
Can we say a 'Schedule' is a set of 'Components'?
What are 'Components' (other than the individual parts of a Schedule')?
Line 372, table 3-6 has this definition for 'Component':
'In iCalendar, the primary information structure is a Component.'
This doesn't tell us what a 'Component' is (what data it conveys),
only it's place in the WS-Calendar information hierarchy.
Didn't find 'Component' defined in WS-Calendar.
The spec figure 6-1 seems to indicate a Schedule is a 'start time' and a 'duration' (see gluon 3).
How does this relate to 'Component'? Is a 'Component' a 'start time' and a 'duration'?
Requires further review / input / clarification.