Experience and further thinking on pathways require the removal of the domain and range of the PathwayComponent subclasses from the terms ceterms:precedes and ceterms:prerequisite. Appropriate domains/ranges for these properties are, at a minimum, ceterms:Course and ceterms:LearningProgram.
The rationale for removing the domain and range from PathwayComponent subclasses is that both properties define conditions directly on an instance of a PathwayComponent subclass when all such conditioning must be handled through that PathwayComponent's ceterms:ComponentCondition as the following diagram illustrates:
The notion of "precedes" is inherent in the structure of the pathway through the hasChild and, additionally, through any progression model used that identifies points in the progression and adds gloss. The notion of "prerequisite" in the pathway is illustrated in the diagram above by the ConditionComponent for the "HTML5 CSS 3" badge component.
Related to #804
Experience and further thinking on pathways require the removal of the domain and range of the PathwayComponent subclasses from the terms ceterms:precedes and ceterms:prerequisite. Appropriate domains/ranges for these properties are, at a minimum, ceterms:Course and ceterms:LearningProgram.
The rationale for removing the domain and range from PathwayComponent subclasses is that both properties define conditions directly on an instance of a PathwayComponent subclass when all such conditioning must be handled through that PathwayComponent's ceterms:ComponentCondition as the following diagram illustrates:
The notion of "precedes" is inherent in the structure of the pathway through the hasChild and, additionally, through any progression model used that identifies points in the progression and adds gloss. The notion of "prerequisite" in the pathway is illustrated in the diagram above by the ConditionComponent for the "HTML5 CSS 3" badge component.
Related to #804