syndication : Messages : 4611-4640 of 4640

thinking even more about it - when generating feed why not to generate
as much metadata in as many standards as possible? who knows what may
turn out to be useful ...

<atom:link rel="related" href="http://nytimes/2005/foo" title="Foo">
<atom:link rel="related" href="http://bbc/2005/bar" title="Bar">
<atom:link rel="via" href="http://other-blogger" title="other" />
<atom:link rel="related" href="http://myspace/SomeTopic"/>
<s:link rel="s:topic" xmlns:s="my-space" href="/SomeTopic"/>
<!-- now all kind of tagging -->
<dc:subject>SomeTopic</dc:subject>
<atom:category term="SomeTopic" />
<atom:category scheme="http://myspace/"
           term="SomeTopic">
    <a href="http://myspace/SomeTopic">SomeTopic</a>
</category>
    <!-- i do not think rel="tag" is allowed in ATOM? ow it is going otbe
handled in ATOM 1.x? -->
<atom:link rel="related" href="http://technorati.com/tag/SomeTopic"/>

i wonder if there are more metadata schemas ...

thanks,

alek

--
The best way to predict the future is to invent it - Alan Kay

#4612

From: Aleksander Slominski <aslom@...>
Date: Thu Jul 28, 2005 6:52 pm
Subject: Re: RSS Referencing

as10m

Offline

Aleksander Slominski wrote:

> <atom:link href="nytimes" title="Foo">
> <atom:link href="bbc" title="Bar">
> <atom:link rel="via" href="other-blogger" title="other" />
> <atom:link href="http://myspace/SomeTopic"/>
> <s:link rel="s:topic" xmlns:s="my-space" href="SomeTopic"/>

it seems default for rel is "alternate" so that should be chnaged to

<atom:link rel="related" href="nytimes" title="Foo">
<atom:link rel="related" href="bbc" title="Bar">
<atom:link rel="via" href="other-blogger" title="other" />
<atom:link href="http://myspace/SomeTopic"/>
<s:link rel="s:topic" xmlns:s="my-space" href="SomeTopic"/>

best,

alek

--
The best way to predict the future is to invent it - Alan Kay

#4613

From: Aleksander Slominski <aslom@...>
Date: Thu Jul 28, 2005 6:48 pm
Subject: Re: RSS Referencing

as10m

Offline

On 7/27/05, Stephen Downes <Stephen.Downes@...> wrote:

>But who cares, right? After all, if we have the link to the content
>document on Blogger, then we have all the information we need. The
>author can simply write about the NY Times as part of the post
>content, and embed a link into what will eventually become the
>description. Problem solved.
>
>
it seems you do nto care about the case when there can be multiple links
to content?

what about referencing other places "via" link?

i think that it is more natural to put those links in body content
(<description> in RSS) than to force in UI external elements

then let software extract links and put them into generated atom feed, ex:

<body><div xmlns="xhtml">I was ready <a href="nytimes">Foo</a> and <a
href="bbc">Bar</a> and baz (<a rel="via"
href="other-blogger">other</a>)</div></body>

generates links:

<atom:link href="nytimes" title="Foo">
<atom:link href="bbc" title="Bar">
<atom:link rel="via" href="other-blogger" title="other" />

if you have more complicated links relations i think it is beneficial to
define superset of atom:link and allow more powerful relations in
decentralized way - i did it internally in my engine by using QNames,
for example to point to internal topic (which is like "tag" or Wiki
topic): <a href="/SomeTopic" rel="s:topic">...</a> that is later
translated to <s:link rel="s:topic" xmlns:s="my-space"
href="SomeTopic"/> where s:link is superset of atom:link with redefined
rel/rev and other attributes possible.

and for interoperability i can still of course generate <atom:link> in
my atom feed (alas! i loose my custom relations as atom 1.0 has
centralized rel content and does not allow namespace so for my own
benefit i still include my own link el):

<atom:link href="nytimes" title="Foo">
<atom:link href="bbc" title="Bar">
<atom:link rel="via" href="other-blogger" title="other" />
<atom:link href="http://myspace/SomeTopic"/>
<s:link rel="s:topic" xmlns:s="my-space" href="SomeTopic"/>

best,

alek

--
The best way to predict the future is to invent it - Alan Kay

#4614

From: Phillip Pearson <phil@...>
Date: Sun Jul 31, 2005 12:07 pm
Subject: Re: RSS Referencing

phillip_pear...

Online Now

The most sensible way of doing things, IMHO, is to put the link to the
blog post inside the <guid> field, and to replicate it in the <link>
field if the post doesn't have anything better to link to.

(So in your case, when you're writing posts that reference the NYT
etc, your own post's link goes in <guid> and the NYT's link goes in
<link>.  If you write a post with no link, both <guid> and <link> will
then point to the post.)

This is how Radio Userland and a bunch of other tools do it.

On the 'consumer' side, it's easy to see what's going on.  The spec
says that text inside <guid> (with no isPermalink attribute, or with
isPermalink="true") is the post's permalink.  The text inside <link>
is defined more vaguely - it's just a link that has something to do
with the post.  Aggregators generally make the title of the post link
to what's inside the <link> tag, and put a smaller link somewhere that
points to what's inside <guid>.

Cheers,
Phil

On Wed, Jul 27, 2005 at 06:04:34PM -0000, Stephen Downes wrote:
>
> RSS Referencing
> Stephen Downes
> July 27, 2005

#4615

From: Steve Cayzer <steve.cayzer@...>
Date: Mon Aug 1, 2005 10:27 am
Subject: Re: Re: RSS Referencing

cayzers

Offline

So, reading this thread carefully, one possible resolution is that the
atom "rel" attribute is extended.

<link rel="parent" href="http://myblog/monthly_summary">
<link rel="replyto" href="http://yourblog/contentious_article">
<link rel="reference" href="http://communityblog/about_this_topic">

These 3 to be added to the exisiting: related, alternate, vias,
enclosure and self.

Aleksander Slominski wrote:

> if you have more complicated links relations i think it is beneficial
> to define superset of atom:link and allow more powerful relations in
> decentralized way - i did it internally in my engine by using QNames,
> for example to point to internal topic (which is like "tag" or Wiki
> topic): <a href="/SomeTopic" rel="s:topic">...</a> that is later
> translated to <s:link rel="s:topic" xmlns:s="my-space"
> href="SomeTopic"/> where s:link is superset of atom:link with
> redefined rel/rev and other attributes possible.
>
>
.. and Aleksander appears to agree. Is there any mechanism to tell the
aggregator about the superset relationship (RDF would say superclass)
between s:link and atom:link ?

> and for interoperability i can still of course generate <atom:link> in
> my atom feed (alas! i loose my custom relations as atom 1.0 has
> centralized rel content and does not allow namespace

So what's the best, to get Atom buy in (which may not happen), or to
roll your own namespace (which will doubtless get ignored by the
aggregators)?
I've more or less taken the latter route but using RDF properties from
known vocabularies (eg Annotea 'annotates'
http://www.w3.org/2000/10/annotation-ns).

Steve

#4616

From: Sam Ruby <rubys@...>
Date: Mon Aug 1, 2005 12:36 pm
Subject: Re: Re: RSS Referencing

sa3ruby

Offline

Aleksander Slominski wrote:
>
> if you have more complicated links relations i think it is beneficial to
> define superset of atom:link and allow more powerful relations in
> decentralized way - i did it internally in my engine by using QNames,
> for example to point to internal topic (which is like "tag" or Wiki
> topic): <a href="/SomeTopic" rel="s:topic">...</a> that is later
> translated to <s:link rel="s:topic" xmlns:s="my-space"
> href="SomeTopic"/> where s:link is superset of atom:link with redefined
> rel/rev and other attributes possible.
>
> and for interoperability i can still of course generate <atom:link> in
> my atom feed (alas! i loose my custom relations as atom 1.0 has
> centralized rel content and does not allow namespace so for my own
> benefit i still include my own link el):
>
> <atom:link href="nytimes" title="Foo">
> <atom:link href="bbc" title="Bar">
> <atom:link rel="via" href="other-blogger" title="other" />
> <atom:link href="http://myspace/SomeTopic"/>
> <s:link rel="s:topic" xmlns:s="my-space" href="SomeTopic"/>

Why is this superset necessary?  Atom supports decentralized definitions
of custom relations.

http://www.atomenabled.org/developers/syndication/#extensibility
http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.secti\
on.4.2.7.2

Here are a few examples of valid feeds:

http://feedvalidator.org/testcases/atom/4.1.1/link-rel-full.xml
http://feedvalidator.org/testcases/atom/4.2.7.2/absolute_rel.xml
http://feedvalidator.org/testcases/atom/6.4/link-extensions.xml

Note in the third example, there even are new attributes defined (in
their own namespace), and even elements placed inside the rel.

- Sam Ruby

#4617

From: Aleksander Slominski <aslom@...>
Date: Mon Aug 1, 2005 7:08 pm
Subject: Re: Re: RSS Referencing

as10m

Offline

Sam Ruby wrote:

Aleksander Slominski wrote:

<atom:link href="nytimes" title="Foo">
<atom:link href="bbc" title="Bar">
<atom:link rel="via" href="other-blogger" title="other" />
<atom:link href="http://myspace/SomeTopic"/>
<s:link rel="s:topic" xmlns:s="my-space" href="SomeTopic"/>

Why is this superset necessary? Atom supports decentralized definitions
of custom relations.
http://www.atomenabled.org/developers/syndication/#extensibility
http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.7.2
Here are a few examples of valid feeds:
http://feedvalidator.org/testcases/atom/4.1.1/link-rel-full.xml
http://feedvalidator.org/testcases/atom/4.2.7.2/absolute_rel.xml
http://feedvalidator.org/testcases/atom/6.4/link-extensions.xml
Note in the third example, there even are new attributes defined (in
their own namespace), and even elements placed inside the rel.

hi Sam,

thanks for the pointers - i think it is the best choice and i will use for ATOM 1.0 export even if it does not support a compact notation for multiple relations (such as in HTML4) which i think is used by some specs to express more in rel="..." such as XFN (none seems to support namespaces so some day "friend" rel is bind to collide with other "friend" ...) - example:

<a href="http://john" rel="friend met colleague">John</a>.

which i think in ATOM 1.0 would be best expressed as an equivalent (but longer) set of links:

<atom:link rel="http://gmpg.org/xfn/rel/freind" href="http://john" title="John"/>
<atom:link rel="http://gmpg.org/xfn/rel/met" href="http://john" title="John"/>
<atom:link rel="http://gmpg.org/xfn/rel/colleague" href="http://john" title="John"/>

this should work fine (especially that it can be autogenerated from XHTML content..)

the only thing i do not like is that i lost a separation between namespaces and term defined in that namespace (topic, tag, keyword, relation name etc.). in other words conversion of QName (pair of URI and name) into extended URI is not bidirectional in general (for example if i have URI: http://some/A#B - is term part "B", "A", or "A#B" even if '#' is illegal in NCName ...)

thanks,

alek

-- The best way to predict the future is to invent it - Alan Kay

#4618

From: Mark Nottingham <mnot@...>
Date: Mon Aug 15, 2005 8:33 pm
Subject: FYI: Feed History -03

mnotting

Online Now

Draft -03 of feed history is now available, at:
    http://www.ietf.org/internet-drafts/draft-nottingham-atompub-feed-
history-03.txt

Note that this is a mechanism that's equally usable in different
versions of RSS, as well as Atom.

Significant changes in this revision include:
    - add fh:archive element, to indicate that an entry is an archive
    - allow subscription feed to omit fh:stateful if fh:prev is present
    - clarified that fh doesn't add ordering semantics, just allows
you to reconstruct state
    - cleaned up text, fixed examples, general standards hygiene

There's going to be at least one more draft, as I neglected to
acknowledge people who have made suggestions and otherwise helped so
far. Sorry!


--
Mark Nottingham     http://www.mnot.net/

#4619

From: "Stephen Downes" <Stephen.Downes@...>
Date: Thu Aug 18, 2005 1:12 am
Subject: Re: FYI: Feed History -03

datamouse2001

Offline

syndication@yahoogroups.com wrote:

> Draft -03 of feed history is now available, at:
>   http://www.ietf.org/internet-drafts/draft-nottingham-atompub-
feed- history-03.txt
>
>
>

Looks good to me. Thumbs up.

-- Stephen

--

Stephen Downes  ~  Research Officer  ~  National Research Council  Canada
http://www.downes.ca  ~  stephen@...         __\|/__ Free  Learning

--

#4620

From: Mark Nottingham <mnot@...>
Date: Tue Sep 6, 2005 11:18 pm
Subject: Feed History -04

mnotting

Online Now

Feed History -04 is out, at:
    http://www.ietf.org/internet-drafts/draft-nottingham-atompub-feed-
history-04.txt

Changes:
    - fh:stateful -> fh:incremental, with appropriate changes in text
    - more explicit cardinality information
    - implications of fh:prev being an Absolute URI spelled out
    - more explicit white space handling
    - Acknowledgements section

--
Mark Nottingham     http://www.mnot.net/

#4621

From: Julian Bond <julian_bond@...>
Date: Thu Sep 15, 2005 8:08 am
Subject: I wish these services produced RSS/Atom

jbond23uk

Offline

- Amazon wishlist for a person
- Amazon Lists
- Amazon Recommendations for one person
- eBay listings from one person
- eBay search results
- Craigslist listings for one person
- Craigslist listings in a category/region
- My Yahoo subscriptions for one person
- Google Search results

I bet you can think of others in the same vein.

Can anyone help make them happen?

--
Julian Bond E&MSN: julian_bond at voidstar.com  M: +44 (0)77 5907 2173
Webmaster:             http://www.ecademy.com/  T: +44 (0)192 0412 433
Personal WebLog:      http://www.voidstar.com/  S: callto://julian.bond
                       *** Just Say No To DRM ***

#4622

From: "Content-wire Research" <editor@...>
Date: Tue Oct 4, 2005 3:38 am
Subject: content-wire feeds riddle help

editor@...

Hi good syndication peoples

you ll remember content wire, we started off about 5 years ago and several of you helped us pull our rss feeds together

this happened in a variety of fashions, from spiders scraping html and converting to rss, to various other types of feed burners and news aggregators that you guys have been working on

a couple of years later our software supplier created a built in feature to produce feeds, that we have been using ever since, in fact moreover, google, newsnow, factiva and various others use our feeds daily

it turns out that our rss does not validate now due to a coldfusion propretary tag at the top, and this is preventing

some of our users who are able to write ad hoc parsers to use our feeds

nobody ever told me that was a problem before, and considering our feeds code is embedded in the system, it is not likely that i ll be able to upate the code until next upgrade

first, I d like to ask all on this list who have worked with content-wire rss before to kindly look into the problem

and update their entires where relevant, we have changed our feeds structure

second, if someone can suggest a quick fix (I am thinking of options) other than changing the code

that would be appreciated, thanks

www.content-wire.com/feeds/feeds2.cfm

Paola

#4623

From: "Nick Lothian" <nlothian@...>
Date: Tue Oct 4, 2005 3:43 am
Subject: RE: content-wire feeds riddle help

nick_a_l

Offline

You mean the <META NAME="ColdFusionMXEdition" CONTENT="ColdFusion DevNet Edition - Not for Production Use."> tag?

I would guess that using a licenced version of ColdFusion might help with the "Not for Production Use" problem....

From: syndication@yahoogroups.com [mailto:syndication@yahoogroups.com] On Behalf Of Content-wire Research
Sent: Tuesday, 4 October 2005 1:09 PM
To: syndication@yahoogroups.com
Subject: [syndication] content-wire feeds riddle help

Hi good syndication peoples

you ll remember content wire, we started off about 5 years ago and several of you helped us pull our rss feeds together

this happened in a variety of fashions, from spiders scraping html and converting to rss, to various other types of feed burners and news aggregators that you guys have been working on

a couple of years later our software supplier created a built in feature to produce feeds, that we have been using ever since, in fact moreover, google, newsnow, factiva and various others use our feeds daily

it turns out that our rss does not validate now due to a coldfusion propretary tag at the top, and this is preventing

some of our users who are able to write ad hoc parsers to use our feeds

nobody ever told me that was a problem before, and considering our feeds code is embedded in the system, it is not likely that i ll be able to upate the code until next upgrade

first, I d like to ask all on this list who have worked with content-wire rss before to kindly look into the problem

and update their entires where relevant, we have changed our feeds structure

second, if someone can suggest a quick fix (I am thinking of options) other than changing the code

that would be appreciated, thanks

www.content-wire.com/feeds/feeds2.cfm

Paola

IMPORTANT: This e-mail, including any attachments, may contain private or confidential information. If you think you may not be the intended recipient, or if you have received this e-mail in error, please contact the sender immediately and delete all copies of this e-mail. If you are not the intended recipient, you must not reproduce any part of this e-mail or disclose its contents to any other party.
This email represents the views of the individual sender, which do not necessarily reflect those of education.au limited except where the sender expressly states otherwise.

It is your responsibility to scan this email and any files transmitted with it for viruses or any other defects.

education.au limited will not be liable for any loss, damage or consequence caused directly or indirectly by this email.

#4624

From: <editor@...>
Date: Tue Oct 4, 2005 5:01 am
Subject: RE: content-wire feeds riddle help

editor@...

> You mean the <META NAME="ColdFusionMXEdition" CONTENT="ColdFusion
DevNet
> Edition - Not for Production Use."> tag?
>
> I would guess that using a licenced version of ColdFusion might help
> with the "Not for Production Use" problem....

LOL
the software used is fully licensed as far as I know
not sure why that appears, but your right, doesnt look good, will investigat

however
that would not make a difference in terms of validity
try again with another answer pleaz
thanks
Pdm

>
>
> ________________________________
>
>  From: syndication@yahoogroups.com
> [mailto:syndication@yahoogroups.com] On Behalf Of Content-wire Research
>  Sent: Tuesday, 4 October 2005 1:09 PM
>  To: syndication@yahoogroups.com
>  Subject: [syndication] content-wire feeds riddle help
>
>
>
> 	  Hi good syndication peoples
>
>  you ll remember content wire, we started off about 5 years ago
> and several of you helped us pull our rss feeds together
>
>  this happened in a variety of fashions, from spiders scraping
> html and converting to rss, to various other types of feed burners and
> news aggregators that you guys have been working on
>
>
>
>  a couple of years later our software supplier created a built in
> feature to produce feeds, that we have been using ever since, in fact
> moreover, google, newsnow, factiva and various others use our feeds
> daily
>
>  it turns out that our rss does not validate now due to a
> coldfusion propretary tag at the top, and this is preventing
>  some of our users who are able to write ad hoc parsers to use
> our feeds
>
>  nobody ever told me that was a problem before, and considering
> our feeds code is embedded in the system, it is not likely that i ll be
> able to upate the code until next upgrade
>
>  first, I d like to ask all on this list who have worked with
> content-wire rss before to kindly look into the problem
>  and update their entires where relevant, we have changed our
> feeds structure
>
>  second, if someone can suggest a quick fix (I am thinking of
> options)  other than changing the code
>  that would be appreciated, thanks
>
>  www.content-wire.com/feeds/feeds2.cfm
>
>
>  Paola
>
>
> ________________________________
>
>  YAHOO! GROUPS LINKS
>
>
>
>  *  Visit your group "syndication
> <http://groups.yahoo.com/group/syndication> " on the web.
>
>  *  To unsubscribe from this group, send an email to:
> 		 syndication-unsubscribe@yahoogroups.com
> <mailto:syndication-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>
>  *  Your use of Yahoo! Groups is subject to the Yahoo!
> Terms of Service <http://docs.yahoo.com/info/terms/> .
>
>
> ________________________________
>
> IMPORTANT: This e-mail, including any attachments, may contain private or
confidential information.
> If you think you may not be the intended recipient, or if you have received
this
e-mail in error,
> please contact the sender immediately and delete all copies of this e-mail. If
you are not the intended
> recipient, you must not reproduce any part of this e-mail or disclose its
contents to any other party.
>
> This email represents the views of the individual sender, which do not
necessarily reflect those of
> education.au limited except where the sender expressly states otherwise.
>
> It is your responsibility to scan this email and any files transmitted with it
for
viruses or any other
> defects.
>
> education.au limited will not be liable for any loss, damage or consequence
caused directly or indirectly by this email.
>
>



--

#4625

From: "Clinton Gallagher" <csgallagher@...>
Date: Wed Dec 21, 2005 1:21 am
Subject: Formatting skipDays and skipHours...

pocketchange...

Offline

The RSS 2.0 specification is ambiguous. The specification [1] clearly states
how to represent the values but fails to indicate how to delineate a
collection of values. Commas? Spaces? Other?

The skipDays verbiage also mentions Sunday as the last day of the week. Does
the order of days in the collection matter to those parsing the channel and
again what is the preferred delineator if any?

Finally, as a point of discussion which ahs probably been argued in the past
the specification fails to indicate how the channel for a restaurant or deli
for example may or may not indicate skipped hours on such and such a day(s)
while skipping other hours on this day and that day instead while skipping
days entirely on this day and that day. Clear as mud ;-)

I'll be posting this inquiry to several lists hoping to attract the
attention and comments of those who may have insight regarding how
aggregators and readers are responding to these issues. Perhaps a general
consensus will emerge as I haven't found any FAQs or "Best Practice"
documents yet...

<%= Clinton Gallagher

[1] http://blogs.law.harvard.edu/tech/skipHoursDays#skiphours

#4626

From: Phil Ringnalda <philringnalda@...>
Date: Wed Dec 21, 2005 4:13 am
Subject: Re: Formatting skipDays and skipHours...

philringnalda

Offline

Clinton Gallagher wrote:
> The RSS 2.0 specification is ambiguous. The specification [1] clearly states
> how to represent the values but fails to indicate how to delineate a
> collection of values. Commas? Spaces? Other?

Other, repeated elements.
<skipHours><hour>8</hour><hour>9</hour></skipHours>

> Finally, as a point of discussion which ahs probably been argued in the past
> the specification fails to indicate how the channel for a restaurant or deli
> for example may or may not indicate skipped hours on such and such a day(s)
> while skipping other hours on this day and that day instead while skipping
> days entirely on this day and that day. Clear as mud ;-)

Yep, if you want that granularity, you'll want to design something new,
all the while remembering how very, very few aggregators support
skipHours/skipDays, and how your new thing will get even less support.
And it's even less granular than you may be thinking since "days" that
are skipped probably have to be assumed to be days in UTC, so depending
on how far away from Europe you are, the overlap between your day and
the skipped day may be pretty poor.

I'll leave it up to someone else to do the standard "mod_syndication is
so much better specified" (without mentioning that it is probably even
less widely supported).

Phil Ringnalda

#4627

From: "Clinton Gallagher" <csgallagher@...>
Date: Wed Dec 21, 2005 7:25 pm
Subject: Re: Formatting skipDays and skipHours...

pocketchange...

Offline

> Message: 1
>    Date: Tue, 20 Dec 2005 19:21:25 -0600
>    From: "Clinton Gallagher" <csgallagher@...>
>    Subject: Formatting skipDays and skipHours...
>
> The RSS 2.0 specification is ambiguous. The specification [1]
> clearly states how to represent the values but fails to
> indicate how to delineate a collection of values. Commas?
> Spaces? Other?
>
<snip />
>
> <%= Clinton Gallagher
> [1] http://blogs.law.harvard.edu/tech/skipHoursDays#skiphours
>
> Message: 2
>    Date: Tue, 20 Dec 2005 20:13:03 -0800
>    From: Phil Ringnalda <philringnalda@...>
>    Subject: Re: Formatting skipDays and skipHours...
>
<snip />
>
> <skipHours><hour>8</hour><hour>9</hour></skipHours>
>
> I'll leave it up to someone else to do the standard
> "mod_syndication is so much better specified" (without
> mentioning that it is probably even less widely supported).
>
> Phil Ringnalda

Thank you, I went to the web and found more comments and
implementation insights. Your comments regarding mod_syndication
is making too much sense.

Well Phil, do you know of any collections of "best practice"
documents for developers to gain insight rather than picking
a bit and a byte at a time?

<%= Clinton Gallagher

#4628

From: "zirgleratbag" <zoe.barnett@...>
Date: Tue Apr 25, 2006 10:48 am
Subject: RSS Questions from a novice

zirgleratbag

Online Now

Hi there,

I was hoping someone could help me with the latest
thinking/information about:
1. What RSS standards/versions are out there?
2. Which is the best?
3.How much time and effort would it take to implement?
4. What is the lastest stuff available for aggregating news from
sister sites onto one main site homepage?

Many thanks

#4629

From: "Vikas" <vikassah@...>
Date: Tue Jun 27, 2006 2:57 pm
Subject: Please provide feedback on www.infoabtdeals.com

vikas_is

Offline

I have developed a deals aggregator site using RSSLib and would like
your comments and feedback on it.

The site can be found at: http://www.infoabtdeals.com

Thanks.

#4630

From: "Steven Clift" <slc@...>
Date: Mon Feb 5, 2007 5:38 pm
Subject: Aggregation to RSS services, Mash-up tool recommendations

netclift

Offline

I am looking for recommendations on a web-based service that would
allow me to aggregate clusters of RSS feeds and turn them into a
combined RSS feed I can display on my my site.

I am currently using the Drupal aggregator to display about 100 feeds
related to "e-democracy" and I'd like to stream-line the presentation.
While I know that I can use blog search tools to display specific
keywords in a combined feed, I am really looking for something that
combines feeds (a keeps them freshly gathered).

Also, since I can't find a e-list on "mash-ups" I am looking for a
tool that combines YouTube, Flickr, Del.icio.us and others.  Something
we can use to replicate this "mnpolitics" tag aggregation page
http://e-democracy.org/voices for the U.S. Presidential election and the
"p2008" tag.

Cheers,
Steven Clift
Please reply to: clift@...

#4631

From: Sam Ruby <rubys@...>
Date: Mon Feb 5, 2007 6:06 pm
Subject: Re: Aggregation to RSS services, Mash-up tool recommendations

sa3ruby

Offline

Steven Clift wrote:
>
> I am looking for recommendations on a web-based service that would
> allow me to aggregate clusters of RSS feeds and turn them into a
> combined RSS feed I can display on my my site.
>
> I am currently using the Drupal aggregator to display about 100 feeds
> related to "e-democracy" and I'd like to stream-line the presentation.
> While I know that I can use blog search tools to display specific
> keywords in a combined feed, I am really looking for something that
> combines feeds (a keeps them freshly gathered).
>
> Also, since I can't find a e-list on "mash-ups" I am looking for a
> tool that combines YouTube, Flickr, Del.icio.us and others. Something
> we can use to replicate this "mnpolitics" tag aggregation page
> http://e-democracy.org/voices <http://e-democracy.org/voices> for the
> U.S. Presidential election and the
> "p2008" tag.

One such tool can be found here:

http://www.intertwingly.net/code/venus/

- Sam Ruby

#4632

From: "Akilesh Ayyar" <akilesh@...>
Date: Mon Feb 5, 2007 5:48 pm
Subject: RE: Aggregation to RSS services, Mash-up tool recommendations

shivohum

Offline

Hi,

I think Dapper, at http://www.dappit.com/index.php -- might do what you're
looking for. It allows you to slice and splice together RSS feeds. It has a
bit of a learning curve, but it looks to be pretty powerful.

Hope that helps,

Akilesh

-----Original Message-----
From: syndication@yahoogroups.com [mailto:syndication@yahoogroups.com] On
Behalf Of Steven Clift
Sent: Monday, February 05, 2007 12:38 PM
To: syndication@yahoogroups.com
Subject: [syndication] Aggregation to RSS services, Mash-up tool
recommendations


I am looking for recommendations on a web-based service that would
allow me to aggregate clusters of RSS feeds and turn them into a
combined RSS feed I can display on my my site.

I am currently using the Drupal aggregator to display about 100 feeds
related to "e-democracy" and I'd like to stream-line the presentation.
While I know that I can use blog search tools to display specific
keywords in a combined feed, I am really looking for something that
combines feeds (a keeps them freshly gathered).

Also, since I can't find a e-list on "mash-ups" I am looking for a
tool that combines YouTube, Flickr, Del.icio.us and others.  Something
we can use to replicate this "mnpolitics" tag aggregation page
http://e-democracy.org/voices for the U.S. Presidential election and the
"p2008" tag.

Cheers,
Steven Clift
Please reply to: clift@...




Yahoo! Groups Links

#4633

From: "Steven Clift" <slc@...>
Date: Mon Aug 20, 2007 7:46 pm
Subject: Authenticated web feed access standard?

netclift

Offline

Is there a standard that defines how news aggregators should request
access to web feeds behind a login/password?

Our few private groups - http://forums.e-democracy.org - generate web
feeds which may be read by default browser-based feed readers and
there is no problem to display them if someone stays logged in via the
browser.

However, I'd like to have the developer of the open source GroupServer
- http://groupserver.org - tool explore giving authenticated access to
Bloglines and other users of aggregators that supposedly support this
kind of access.

Steven Clift
E-Democracy.Org

#4634

From: "elijah wright" <elijah.wright@...>
Date: Tue Aug 21, 2007 10:46 pm
Subject: Re: Authenticated web feed access standard?

elw_wc

Offline

if they can rig things up to support standard web auth via a username/password box... then...

the format:

http://username:password@feedhost/feedurl/

should work just fine.

[I'm using this with rss2email to yank updates out of a copy of pmwiki; sadly, google reader doesn't seem to support that sort of feed format.]

--e

On 8/20/07, Steven Clift <slc@...> wrote:

Is there a standard that defines how news aggregators should request
access to web feeds behind a login/password?

Our few private groups - http://forums.e-democracy.org - generate web
feeds which may be read by default browser-based feed readers and
there is no problem to display them if someone stays logged in via the
browser.

However, I'd like to have the developer of the open source GroupServer
- http://groupserver.org - tool explore giving authenticated access to
Bloglines and other users of aggregators that supposedly support this
kind of access.

Steven Clift
E-Democracy.Org

#4635

From: "Mark Nottingham" <mnot@...>
Date: Sat Oct 11, 2008 10:59 pm
Subject: List Closing

mnotting

Online Now

Just a quick note -

I started this list <http://tech.groups.yahoo.com/group/syndication/message/2>
more than
nine years ago (!) to talk about "syndication". In the process, we had a nice
war about RSS,
and helped birth a new, open standard -- Atom.

There hasn't been any serious activity on this list since 2004, and even its
name isn't terribly
relevant any more, as the community's discussion has moved from syndication to
blogging,
open data APIs and further.

As a result, I'll be closing this list down soon. It was fun.

If you have syndication-related questions, there are a number of places to take
them; I'd
suggest the atom-syntax mailing list <http://www.imc.org/atom-syntax/> as a
starting
point.

May you enjoy having one less mailbox to monitor,

#4636

From: "Mark Nottingham" <mnot@...>
Date: Sat Oct 11, 2008 11:33 pm
Subject: Re: List Closing

mnotting

Online Now

P.S. Many thanks to Bill Kearney for moderating for a good chunk of that time.

Bye,

#4637

From: Anish Shrestha <shresthaanish@...>
Date: Sun Oct 12, 2008 4:23 am
Subject: Re: List Closing

shresthaanish

Offline

thanx for all your efforts.

Anish

--- On Sat, 10/11/08, Mark Nottingham <mnot@...> wrote:

From: Mark Nottingham <mnot@...>
Subject: [syndication] List Closing
To: syndication@yahoogroups.com
Date: Saturday, October 11, 2008, 3:59 PM

Just a quick note -

I started this list <http://tech. groups.yahoo. com/group/ syndication/ message/2> more than
nine years ago (!) to talk about "syndication" . In the process, we had a nice war about RSS,
and helped birth a new, open standard -- Atom.

There hasn't been any serious activity on this list since 2004, and even its name isn't terribly
relevant any more, as the community's discussion has moved from syndication to blogging,
open data APIs and further.

As a result, I'll be closing this list down soon. It was fun.

If you have syndication- related questions, there are a number of places to take them; I'd
suggest the atom-syntax mailing list <http://www.imc. org/atom- syntax/> as a starting
point.

May you enjoy having one less mailbox to monitor,

#4638

From: "Martin Hirsch" <peopleunit@...>
Date: Mon Oct 13, 2008 12:37 am
Subject: Leave the group active for reference purposes

peopleunit

Offline

I joined this group so that one day, when time permits, I might be
able to go through the messages and what not to learn more about
syndication. If you don't think there's any worthwhile information,
then by all means, pull the plug.

My recommendation would be to open up the message viewing to the
public without requiring membership, place a note on the home page
that the existing messages are being saved for reference purposes, for
a while longer at least.

#4639

From: "Bill Kearney" <wkearney@...>
Date: Fri Oct 17, 2008 6:12 pm
Subject: Re: Leave the group active for reference purposes

wkearney99

Offline

--- In syndication@yahoogroups.com, "Martin Hirsch" <peopleunit@...>
wrote:
>
> I joined this group so that one day, when time permits, I might be
> able to go through the messages and what not to learn more about
> syndication. If you don't think there's any worthwhile information,
> then by all means, pull the plug.
>
> My recommendation would be to open up the message viewing to the
> public without requiring membership, place a note on the home page
> that the existing messages are being saved for reference purposes, for
> a while longer at least.

There is a plan to pull the message archives off to another server.

#4640

From: "Mark Nottingham" <mnot@...>
Date: Sat Oct 18, 2008 6:39 am
Subject: Re: Leave the group active for reference purposes

mnotting

Online Now

As Bill mentioned, we're working on getting the archives up elsewhere. Until
then (and
perhaps afterwards), we'll leave the archives up here, but not allow new members
or
messages (except, perhaps, for Bill announcing the location of the archive copy
:)

Cheers,

--- In syndication@yahoogroups.com, "Martin Hirsch" <peopleunit@...> wrote:
>
> I joined this group so that one day, when time permits, I might be
> able to go through the messages and what not to learn more about
> syndication. If you don't think there's any worthwhile information,
> then by all means, pull the plug.
>
> My recommendation would be to open up the message viewing to the
> public without requiring membership, place a note on the home page
> that the existing messages are being saved for reference purposes, for
> a while longer at least.
>