[Sigia-l] CMS and IA

[Margaret Hanley]

> Categorization structures. Most CMS's force you into a
> certain structure
> of categorization. Often a really simple one ("sections"
> or
> "categories"). In my mind, a CMS should separate the
> categorization from
> the content - and provide flexible categorization tools
> that can tie in
> with different front ends. I know that's kinda vague, I'd
> be happy to
> discuss this in a more practical way.

Following on from Peter's comments, three things that I
have noticed while working a CMS.
* Separating out where a piece of content (content object)
is placed or published to from the object itself, so it can
live in many places or platforms. Therefore not creating a
"an article for the Music web site", but an article that is
about music and can be published in many places like the
Music web site, a Going Out section of a site or to
interactive TV.

* Describing an object separate to where it lives in a
site. For example assigning descriptive metadata like
location, subject, audience and time period to each object.

* Identifying content objects at the correct level of
granularity. Is it worth putting headlines in as separate
objects or can the content be structured in XML to allow
parts of the object to be extracted?

Mags


__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com