[Zope-PTK] feature request: news categories
Paul Everitt
paul@digicool.com
Wed, 16 Feb 2000 11:10:33 -0500
Jochen Haeberle wrote:
> I think this depends... for content like that on Zope.org, that's
> perfect. But if you think of some sort of news system, than providing
> an article is more of "submitting" it to the editor of the paper. I
> think this is important that the user does not have every control of
> the article as publishing rights get handed over to the paper... and
> if the content "moves" out of the users folder when it is sent to
> review, that's a sign of that legal event.
Who said that reviewing policies were tied to location? Who said the
user would suddenly get every control of the article?
> >I don't buy the argument that putting stuff close to people breaks
> >URLs. Take a look on the web at all the ~username URLs you see out
> >there. Moreover, deleting a member doesn't delete their content, just
> >like deleting someone on a Linux system doesn't delete all their files.
>
> I guess it would be possible to find means to secure this... ID's
> need not be editable after all...
>
> On the other hand, when using search engines or link lists, you know
> how much content on the Internet changes. The people on this list
> might be aware of those problems, but most users we will deal with in
> the Portals defenitely are not!
You seem to argue, "Don't let users author anything, because they might
change it, and thus break search engines." You can certainly have a
portal where members aren't allowed to author anything.
There is no reason to think that putting content in a central place will
magically solve all problems regarding change.
At the end of the day, though, please remember: it's just like HTML
files on websites. You can put them in your home directory, or if the
local policies require that you put them in a central area, you can do
that as well.
I'm still confused as to what is the problem here. What does the PTK
not do that it should? It lets you put the same kind of content in
central folders, with the same policies, as in member folders. Should
it do something different when content goes in a central folder?
--Paul