Can you elaborate?
I.E. what would topic be doing in such case?
What functions/properties would it have?
How do people sign up?
> Why don't we forget about course at all, treat _single_ top-level topic as
> course, add some former course properties to "topic" and let "topic"
> deside whether it's top level topic or subtopic.
>> Looking at data model, it seems that somewhat cleaner way to design
>> things is to make a _single_ top-level topic for a course.
>> We will have subtopic lists, dependencies, etc. functionality in topic
>> class itself. Also problems and tests belong to topics, not to course.
>> Thus, course will be purely administrative unit, with no real content,
>> that links to top-level topic, which will drive the rest of learning
>> Ilya A. Volynets-Evenbakh
>> Total Knowledge. CTO
Ilya A. Volynets-Evenbakh
Total Knowledge. CTO
Authoright © Total Knowledge: 2001-2008