Re: Course<->topic relationship

["Ilya A. Volynets-Evenbakh" <ilya@total-knowledge.com>]

I don't think anyone is talking about getting rid of topic...
I suggested not having topic _list_ in course. Sergey suggested
not having course at all..

Alexey Parshin wrote:
> What is the advantage of getting rid of topic?
>
> 2006/9/7, Ilya A. Volynets-Evenbakh <ilya@total-knowledge.com
> <mailto:ilya@total-knowledge.com>>:
>
>     Can you elaborate?
>     I.E. what would topic be doing in such case?
>     What functions/properties would it have?
>     How do people sign up?
>
>     sergey@total-knowledge.com <mailto:sergey@total-knowledge.com> wrote:
>     > 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.
>     >> 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?
>     >>
>     >> --
>     >> Ilya A. Volynets-Evenbakh
>     >> Total Knowledge. CTO
>     >> http://www.total-knowledge.com <http://www.total-knowledge.com>
>     >>
>     >>
>     >>
>     >
>     >
>
>     --
>     Ilya A. Volynets-Evenbakh
>     Total Knowledge. CTO
>     http://www.total-knowledge.com
>
>
>
>
> -- 
> Alexey Parshin,
> http://www.sptk.net 

-- 
Ilya A. Volynets-Evenbakh
Total Knowledge. CTO
http://www.total-knowledge.com