Inherits from the Base Provider(s) and can call any data store
provider known in the system.
Each page in the CSK will be made up of one or more channels. Yes, we
are designing to support having links, books and articles all on a single page,
for instance. The master page will handle the layout and the Content
Providers will supply the data.
A RSS feed is made up of 2 main parts:
A Channel is made up of:
- Required
- title - computes to section title like "Archived Books"
- link - computes to a section page like "www.abc.com/books/archives"
- description - pulled from the page or section description
- Optional
- language - the locality language (Italian, Spanish, English, etc)
- copyright - if the site is a business, an optional copyright can be
generated
- managingEditor - email address of the CMS editor(s) for this page
- webMaster - email address of the admin(s) for this site
- pubDate - CMS publication date
- lastBuildDate - last time this content was updated
(add/edit/update/delete)
- category - pulls from the CSK categories list
- generator - would be "CSK 2.0"
- docs - A URL that points to the documentation for the format used in the
RSS file. It's for people who might stumble across an RSS file on a Web
server 25 years from now and wonder what it is.
- cloud - Allows processes to register with a cloud to be notified of
updates to the channel, implementing a lightweight publish-subscribe
protocol for RSS feeds.
- ttl - the CMS time to live
- image - Specifies a GIF, JPEG or PNG image that can be displayed with
the channel.
- rating - the PICS rating
- textInput - Specifies a text input box that can be displayed with the
channel.
- skipHours - A hint for aggregators telling them which hours they can
skip.
- skipDays - A hint for aggregators telling them which days they can
skip.
An Item is made up of:
- Required and/or Optional - A channel may contain any number of
<item>s. All elements of an item are optional, however at least one
of title or description must be present.
- title -
- link -
- description -
- author -
- category -
- comments -
- enclosure -
- guid -
- pubDate -
- source -
Looking through the RSS spec it is clear that we track 90% of this already in
the original CSK. If we take the paradigm shift that the CSK is nothing
more than a large RSS (and extended) RSS generator/consumer, storing the data in
a RSS compliant manner only makes sense.
Next. I'll visit the table structure for Pages, Channels and
Items...