[ZDP] On possible implementations of topic, subtopic, category and keyword inZDPZDP

[David Kankiewicz]

Maik Roeder wrote:
> 
> Hi !

Hi,

just a alterative implementation, another view of a hierarchy. (use my
terminology, if it makes more sense. Category/Subject?)

I've been modeling a large Web Catalog based on something similiar to
what I have below.

to copy your layout:

                  Usage |       specifity        | examples
------------------------+------------------------+-------------------
1. Category   top level | Whole Subject domains  | Zope, Python
2. Subject   everywhere | Defined subject        | Install, ZCat 
3. Topic    acquireable | Boardly defined Topics | acquisition, DTML
------------------------+------------------------+-------------------

The behavior of these are as follows:

Categories act as high level entry points (Probably not needed in the
case of Zope and Python, maybe if you needed developer, user). and a
place to put 'topic's...

Subjects are nothing special except when a they are given a matching
topic, defined as a 'string' containing the 'id' (has to be different,
waaahhh) of the topic, they would then list off all the matching
Categories/Subjects which contain entries under that topic:'some-topic'.

Topics are, as noted above, really weird! They act as if they are a type
of subtopic in every Subject or folder below where they are defined.
They would show up in any of the subjects below them, of course you can
allows just place them in the subject and have them only show up in only
that subject. They would only show themselves if something is in them...



So an example might be (again, using your example as a base):

> 
> Is the following ok ?
> 

 Subject:     -  Python
 Subject:     -  Zope
   Topic:         - syntax
   Topic:         - variables
   Topic:         - tags
   Topic:         - acquisition
   Subject:       - DTML
   Subject:       - Security
     Topic:         - roles
     Topic:         - permissions
     Topic:         - passwords
     Topic:         - authenticated_user
 Subject:      - external methods
 Subject:      - python methods
 Subject:      - python products
 Subject:      - zsqlmethods
 Topic:        - argument passing

 Topic or "Subject"? I have no idea:   - content manipulation
 

The idea is in any folder you would have a combined list of 'topic(s)'
from above.
e.g.:

1, In "Security" you would place a document under "acquisition", that
talks about, "how acquisition limits the range of the functions, like
so..."

From the one click view of "acquisition" at the top, you would see
"Security" as a sub - "subject". Click on it and your in
"Security/acquisition"

2. In "Security" you could place a document under "argument passing",...

3. etc. Hope you get the point...

Implementation:
Does not need a unique id, instead each document would get a 'link'
object that would point to the document you wanted, probably stored at
the top of the hierarchy.  (This differs completely from the way my own
model works, it stores the links inside documents... only works on
single server, more complex, etc.)

The 'link' would hold properties that contain the 'subject' and a 'list
of topics' you want want it to appear under.
One 'link' per "subject"... otherwise you lose the ability to limit to
area.




> 3. reviewed lists
>    new keywords are reviewed first by a maintainer
I vote for this type! No one person can think of everything.


Well, I hope that does the job of providing a different view,
regards,
David