Ilya A. Volynets-Evenbakh wrote:
From that POV, Course could actually be derived from Topic. And in a way it is - after all, Course does cover some Topic/subject. Anatoly Volynets wrote:I still do not see a crucial reason to have one top level topic. If course is an administrative unit (which is actually true) then let it do its job: manage list of topics first of all. This is natural an casual way of course organizing. Yes, topic of any level can have list of subtopics like a course does, but this is not that heavy price in my view. If you need it badly from the programming point of view, make a parent class for course and topic, but do not confuse your customers with "one topic course" or "no in course topic" Ilya A. Volynets-Evenbakh wrote:Looking at data model, it seems that somewhat cleaner way to design things is to make a _single_ top-level topic for a course. Reasoning: 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 process. Objections?
-- Anatoly Volynets, Co-Founder total-knowledge.com culturedialogue.org
Authoright © Total Knowledge: 2001-2008