Re: Re: summary

RS[S] stands for really simple. I like the idea to have only a short
description. Why to complicate the problem with a short summary of 2 lines
and a longer content of 3-4 lines? A unique description I really think is
enough, not shorter description, longer description and very long
description + maybe a special description for those who want this option. :)
Let's keep it simple.

2RSS.com

> --- In [email protected], "Bill Kearney" <ml_yahoo@i...> wrote:
>
> No, RSS description is more like atom:content.
> The idea is that I want to have types of content in the Item:
>
> 1. short summary
> 2. longer content
>
> Sincerely,
> Vadim
>
>
>
> > In the context of an item it's the <description> element.  It's
> likewise the
> > same name in the channel.  Or is that sufficient for the sort of
> data you're
> > handling?
> >
> >
> > ----- Original Message -----
> > From: "Vadim Zaliva" <lord@c...>
> >
> >
> > > I am looking for a way to express in RSS1 something similar to ATOM
> > > "summary" field. Here is definition from ATOM spec:
> > >
> > >     The "atom:summary" element is a Content construct that
> > >     conveys a short summary, abstract or excerpt of the entry.
> > >
> > > Base spec does not have anything like that. I do not see anything in
> > > Dublin Core module. Any suggestions how can I express this using some
> > > exiting module? Of course I can always create new module, which is the
> > > path I am trying to avoid.
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
>



 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/rss-dev/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/