Thanks, Jason. That's great to hear. <br><br>I like the feedburner approach. We already are exposing all of our existing blogs to feedburner via a combination of the Wordpress RSS/feedburner support and out having registered the appropriate <a href="http://openwetware.org">openwetware.org</a> DNS support with Feedburner. Using a similar route, we can configure any RSS feed as 'feedburner-aware'. <br>
<br>We can also publish the same (or pretty similar) information as either hcalendar or ical calendar formats. This allows for publishing the information to other calendar and scheduling tools. <br><br>This isn't an either-or choice. The support can be parameterized using a parameter in the calendar tag. Since the calendar is dynamic (to some degree), the specific options can change over time. <br>
<br>For something like the Event:... calendar, it makes a lot of sense to publish wide, thus via Feedburner. But for other cases, such as a personal notebook, making it a little less public may be desirable. I'm not sure if this will always be the case. By making it easy to change and modify, it can change over time.<br>
<br>Let me look into Feedburner to see how much we would need to do to publish through them as an option. <br><br>I really appreciate your comments. <br><br>B.<br><br><div class="gmail_quote">On Fri, Apr 18, 2008 at 12:32 PM, Jason Morrison <<a href="mailto:jason.p.morrison@gmail.com">jason.p.morrison@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote"><div>First off, great stuff on RSSing the calendars!<br></div><div class="Ih2E3d">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">In the spirit of reciprocity, it might be useful to think about how a person hosting such a list would know how much activity was present on their RSS feed. This is clearly not an original idea: blogs have been doing it for a long time. But it would be nice to think about how this could be tracked. We could do it via Feedburner: publish all RSS feeds that way. The advantage of this would be that the data would be disseminated via Google to a lot of people. </blockquote>
</div><div><br>This would be great, too! It'd be *really* great if this could be integrated (so a lab doesn't have to go sign up for FeedBurner themselves, etc.), and I notice that FeedBurner's "Total Stat PRO" service is now free (<a href="http://code.google.com/apis/feedburner/101_flares.html" target="_blank">http://code.google.com/apis/feedburner/101_flares.html</a>).<br>
<br>Hmm.... looks like you can definitely get the statistics via their API... see idea #52 on <a href="http://code.google.com/apis/feedburner/101_flares.html" target="_blank">http://code.google.com/apis/feedburner/101_flares.html</a>.<br>
<br></div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">OK. Sorry to be so verbose today. </blockquote></div><div><br>
Maybe I'm the only one... but I think it's great to hear about OWW development ideas! :)<br>
<br>Jason<br><br> </div></div><br clear="all"><br>-- <br>Jason Morrison<br><a href="mailto:jason.p.morrison@gmail.com" target="_blank">jason.p.morrison@gmail.com</a><br><a href="http://jayunit.net" target="_blank">http://jayunit.net</a><br>
(585) 216-5657
</blockquote></div><br>