Thorsten Scherler schrieb:
El mié, 08-02-2006 a las 12:37 +0100, J. Wolfgang Kaltz escribió:
[...]
Ok, for me the above site is awesome and I agree as well on content item
because item = nugget. Nugget is just shorter as "ContentItem", why not
"Item". ;-)
Because I think we should explicitly distinguish the items pertaining to
content from the other things used in the CMS (dare I say "resources" ;)
): the CSS, XSLTs, maybe other things too (sitemaps ? plugins ?)
> The only thing still hurting me is the document. You say "a
Document is a collection of such pieces" so why not call it
"ContentCollection" or "collection"?
That's conceivable too, at least for our internal terminology, but we
need something for external terminology in any case. "Document" IMO is
more user-oriented, it is the information presented to the consumer. The
consumer doesn't care that the document may actually be structured in
several pieces. But the authoring user may need to be aware of that:
which piece do I want to edit now ? With which tool (according to the
type of the piece, different tools may be available) ? Am I authorized
to edit this piece of information, or is this one reserved for the
senior author (for example a start page, containing news which one
person may edit, but also a company vision or something, which only the
senior author may edit) ?
So, my opinion: use "Document" to refer to that which is presented to
the consumer of the site. Since we need a term for that internally too,
might as well use the same one (though ContentCollection could be used
here, too). Use "ContentItem" for the individual pieces used in a
"Document". An end-user will never see that terminology, but an author
may (if the document consists of several pieces)
--
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
