Menu
▾
▴
Re: [Slashcode-development] RSS 1.0
|
From: Rael D. <ra...@or...> - 2000-12-15 20:01:18
|
Howdy, On Fri, 15 Dec 2000, Chris Nandor wrote: > At 11:18 -0800 2000.12.15, Rael Dornfest wrote: > >> >> introtext rss:item->rss:description > >> >> bodytext (more content than metadata, but up to you) > >> > >> Technically, introtext is not necessarily metadata either. introtext is > >> what appears on the main page, which may be the entire text of the story. > > > >Then introtext would definitely be appropriate for description if there is > >bodytext beyond. > > Well, it depends on the site. For some sites, introtext may be the entire > story, for others it may be only part of it. What we will probably do is > make it an option to include introtext as description. However, yes, if > anything is description, this is it. It's just that some sites -- like > Slashdot, probably -- won't be including introtext in its RSS. If it does, > it will only be the first $n characters. That's just fine... including a taste is all that's needed. > >> I don't think any of them would be too useful or interesting -- or we just > >> would not want to give out that information -- with the _possible_ > >> exception of hitparade. > > > >I believe the way to go would be to create a Slash module with all of this, > >yet decide on what (like HitParade) you'd like to make public. The rest > >could be included only for internal/cross-site use. Up to you, though. > > Well, first there are the texts, introtext, bodytext, and relatedtext. > Setting aside those, writestatus doesn't matter, displaystatus is obvious > (if you can see it, it is displaying :), commentstatus doesn't work. So I > only see hits and hitparade as being interesting for putting in the module. Cool. > So introtext would be description, bodytext would be some other main body > text field (there's gotta be something like this in SOME module, it is > going to be needed by anyone who wants to put a full story in the RSS > file), and relatedtext is some other field. It's up to you (or the site at hand). I'd have... introtext as description unless no bodytext else first sentence or 100 or so chars of bodytext There is work well underway on a "content" module at: http://www.egroups.com/message/rss-dev/1307 > >> Yeah, since in the case of Slashdot we don't want to give this text away, > >> we would probably at most give the first $n words or something. But > >> probably, we won't put this in at all, and just rely on > >> section/topic/department. > > > >The number one complaint (not that I can do much about it aside from point > >it out) from readers is the lack of descriptions on certain feeds. The > >title often is not quite enough to determine whether or not I'd like to > >follow the link. I'd _strongly_ suggest using introtext when there's a > >bodytext and the first 80-100 characters (minimum) of introtext when > >bodytext does not exist. > > Yes, this will be under consideration. Ta. > >> > <dc:date>${story-date}</dc:date> > >> > <dc:format>text/html</dc:format> > >> > <slash:department>${story_department}</slash:department> > >> > <slash:comments>${story_number_of_comments}</slash:comments> > >> > <slash:hits>${story_hits}</slash:hits> > >> > >> Yeah, we won't put hits in, that's private data. > > > >I'm assuming you mean story_hits, not the others? > > Yes. > > > >date will, along with > >subject, be the number one use of the Dublin Core module. Format isn't > >all that necessary since most RSS items are assumed to be text/html. > >Number of comments is nice and will be very useful in a more generalised > >popularity element in a more generalised module. > > Yep. > > > >Again, this is still being worked out so as to be in accordance with DC and > >RDF in general, so don't worry about it for now. Meerkat, for instance, will > >map your categories to its own ontology and shuffle the stories about as > >appropriate. > > > >Please do let me know if there's any more info I can provide. > > OK, but what I still don't know is how to create this Slash RSS module. > What do we do there? Thanks, 0. Subscribe to RSS-DEV at eGroups (digest and Web-only modes are available) at: http://www.egroups.com/group/rss-dev/ 1. Write up a proposal using the mod_ template at: http://www.egroups.com/files/rss-dev/Modules/Proposed/mod_.html Use one of the others as guidance; a nice simple example (and more than a little apropos) is: http://www.egroups.com/files/rss-dev/Modules/Proposed/mod_annotation.html 2. Save it as mod_slash.html to: http://www.egroups.com/files/rss-dev/Modules/Proposed/ 3. Drop a note to RSS-DEV (rs...@eg...) proposing the module. Be sure to use a subject line like "(Slash) Slashcode Module Proposal" so discussion can be nicely threaded thereafter. That's it. I think we have already built out the basics for one here -- I'm glad to work on it with you. Rael ------------------------------------------------------------------ Rael Dornfest ra...@or... Maven, http://www.oreillynet.com/~rael The O'Reilly Network http://meerkat.oreillynet.com ------------------------------------------------------------------ |
