Further extensibility/granularity?

[bixfrankonis]

I’m wondering to what degree this is further extensible, if that would be desired. I’m thinking about he notion of different elements of a now page being their own items.

For instance, on my homepage which is just a glorified combo about/contact/now page, I have a hacky RSS feed where each emoji’d paragraph is it’s own individual item, rather than, say, the entire now page being considered a single item.

[colin-walker]

My proposal is of the simplest form but maybe it could be extended so that now:content (or an alternative) could act as a container for multiple elements. Something like:

<now:body>
    <now:item>...</now:item>
    <now:item>...</now:item>
</now:body>

How that then gets presented/consumed is another matter.

[colin-walker]

Thinking about it further, <now:content> doesn't have to be replaced – it can be used as the container. Clients would just need to check the nature of what it holds.

I'm open to suggestions here. The initial proposal is just a starting point.

[bixfrankonis]

In my head people could publish their /now page RSS with as much or as little granularity as they prefer, and feed readers could make use of as little or as much of that granularity as they prefer.

So, to use me, my /now page RSS might have individual items for "currently", "books", "movies", "food", and a feed reader could prefer either to consider each updated item its own thing or just consider the entire /now page as having been updated.

[colin-walker]

So, using <now:content> as both an elements or a container we could have either just a block of content or individual items with categories:

<now:item category="currently">...</now:item> <now:item category="movies">...</now:item>

A reader could then do what it wanted with that info based on the user's preferences.