Joachim Wolfgang Kaltz wrote:
Andreas Hartmann schrieb:
[...]
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 ?
Yes ...
[...]
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" ?
It would have to be "CS100_fall_2006", but I understand that this is
indeed hardly acceptable. The other option (CS100/Lectures/Fall2006)
would imply a path-based document organization structure (independent
from the URL space), only the leaf nodes would be documents:
URL -> [ path <-> UUID ]
Note that not all paths would point to UUIDs, since some paths
are only used as folders.
Michi, does this resemble your ideas?
If we don't require human-readable UNIDs or paths:
Maybe the identification problem (e.g. restoring after archiving)
could be solved by meta data queries etc. Or maybe you have another
idea how to solve it? Or do we have to design the system in a way that
this should never be necessary?
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
