Home Projects Jobs Clientele Contact


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: DB structure: Dialog of Texts (DoT)

I need to look it over.

Ilya A. Volynets-Evenbakh wrote:
Alexey Parshin wrote:
Any object that is potentially changeble should have an ACL entry.
Correct. It's just I think DoT is single object, including texts it
contains, and Texts
that are part of it are not separately shareable. However, I'm not 100%
sure about it.
Apparently we talked about what DoT really is, but never wrote it down.
Someone may want to edit a text.. Adding, deleting texts with DoT may
be assumed as 'edit' permission on DoT.

Cross-reference would be added. I just need to understand, is it like
'Also take a look at the following texts: {list of texts here}' ..
OK. I updated
with bit more info. Now, we need to review it and figure out if it's
really something we
want to do, and that we want it in UUv1time frame.

2006/10/18, Ilya A. Volynets-Evenbakh <ilya@total-knowledge.com

    What I mean is that single text within DoT may not actually be
    I.E. one cannot reference separate text, and thus there is no need
    to have
    separate ACL. Access to whole dialog object applies to separate
    of it as well.

    Also, important part of DoT functionality is cross-referencing between
    How is this reflected in our database schema? (Take a look at
    to see sketch of what is intended).

    Alexey Parshin wrote:
    > IMHO, dialog of text logically should be connected to a topic. We do
    > need an ACL for the texts, controlling editing, deleting, and MB
    > referencing (for the commercial server).
    > 2006/10/18, Ilya A. Volynets-Evenbakh < ilya@total-knowledge.com
    > <mailto:ilya@total-knowledge.com
    >     - Is dialog_of_texts really course-level thing?
    >     Actually this is more of a question to Anatoly. Spec says
    >     it's course-level object, but I suspect what is meant is that
    >     DoT is at the same level as course ( i.e. completely
    >     I guess it could be referenced from courses/topics/etc. in same
    >     way as any other media object.... I think this needs more
    >     in specification.
    >     - I'm not sure we really need separate ACL for texts_in_dialog
    >     Again - needs clarification in spec - i.e. can texts be included
    >     in different dialogs without being modified. Is
    >     between texts in a dialog actually separate from texts
    >     (logically it can be, but does our data structure reflect
    that at
    >     all?)
    >     --
    >     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

Alexey Parshin,


Anatoly Volynets, Co-Founder

Authoright © Total Knowledge: 2001-2008