Andreas Hartmann schrieb:
BTW, here's my own opinion:
(...)
Do you prefer
a) UUIDs (http://en.wikipedia.org/wiki/UUID)
b) Lenya-specific UNIDs which might be human-readable
+1
I'd like something human-readable (like in a Wiki) here.
Note that this identifier is not related to the URL space.
The human-readable UNID would have the advantage that documents
can be deleted, archived, restored etc. independent from
the URL space and can be identified later on.
Wouldn't this put the burden on the user to come up with a unique,
human-readable id, for a piece of content ?
IMO when you want a site to follow the Wiki principle, you should use
the "WikiPublication", which works like a Wiki, on the surface. That
means, for the user, there is no hierarchy, just a bunch of keywords
(which the users choose) and which must be unique.
In this publication, the wiki entry name is of course also stored by
Lenya, but only relevant for things like the navigation layer, not
defining the repository ids.
Example:
The
URL /home/news
is mapped to the document with the
UNID NewsOverview (language "en")
well, "news" sounds like an example picked for something that is indeed
unique ;) What about another example "CS100" (introductory computer
science lecture). Would the user have to say "CS100_fall_2006" as a
unique id, or would she be able to create a new entry "CS100" under
"Lectures" / "Fall 2006" ?
--
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
