Ilya A. Volynets-Evenbakh wrote:
And I would' like to remind that UMO and programming objects are not quite the same. Repository is for UMOs.Alexey Parshin wrote:From what you're saying, the course isn't necessary for the topic. In real life, the topic always belongs to some course.1. Don't forget about object repository. 2. When topic is subtopic of some other topic, it belongs to that topic, not the course.
I do understand the situation when topic belongs to more than one course - that totally makes sense. I don't see much difference so far between the top-level topic and thecourse.This is exactly what I'm trying to get across all this time.
And I am waiting for clarification how would it look? If this TLT is something separate from its course - this is not acceptable, but if they coincide totally and there is not such specific thing, like TLT, for end-user - this is fine with me.
The only difference I can see so far is the connection to the students.Yeap. Or, more precisely, administrative connection. It is through actions on the course object, that students get basic access to other course objects.In that case top-level topic is the course.TLT is _course content_. It's not same thing.
Again, how it looks for end-user? Does it bring in some not-so-usual formal relationship on UI? Would it ask to create TLT when user made up a course title already? I hope - not, it is fine with me then.
However, the topic may also have connection to the persons such as access level and status, for instance.Different kind of relationship.
That is administrative functionality for topic and course are different? Course has some extra, right? Let's make sure there is not any functionality on the topic level, which is not suitable for course. Or it doesn't matter?
-- Anatoly Volynets, Co-Founder total-knowledge.com culturedialogue.org
Authoright © Total Knowledge: 2001-2008