Re: Fyi, Apache project proposal
I could certainly do with more of a critical mass of users / contributors / people-on-the-mailing-list James On 23/05/2006, at 8:59 AM, Sylvain Hellegouarch wrote: It seems to be good idea to do such promotion. However I wonder why you have not considerated using an existing project such as demokritos [1] which is quite well advanced. - Sylvain [1] http://www.jtauber.com/demokritos
Re: What Atom software are you working on?
Demokritos - APP server and Python library. http://jtauber.com/demokritos Currently implementing basic auth support for 0.4 release. Also recently started on a AJAX-based APP client to go with it. James -- James Tauber http://jtauber.com/ journeyman of some http://jtauber.com/blog/ On 05/05/2006, at 9:11 AM, Robert Sayre wrote: I've been working to add Atom support to Firefox 2. Some other Firefox devs are toying with exposing internal data like history and bookmarks as Atom feeds. What software are you writing? -- Robert Sayre I would have written a shorter letter, but I did not have the time.
Re: wiki mime type
Agreed that this would be very useful and also that it needs to be done on a per wiki format basis. I think, however, that this is something the format creators should be encouraged to register, or at least suggest a convention for. James On Mon, 06 Mar 2006 07:59:10 -0800, Walter Underwood [EMAIL PROTECTED] said: --On March 6, 2006 3:59:39 PM +0100 Henry Story [EMAIL PROTECTED] wrote: Silly question probably, but is there a wiki mime type? I was thinking of text/wiki or text/x-wiki or something. I want people to be able to edit their blogs in wiki format in BlogEd and be able to distinguish when they do that from when they enter plain text, html or xhtml. Perhaps this is also useful for the protocol. It would be really useful, especially for feeds that archive the content of a blog. It would be best to use the official names of the formats, like text/markdown or text/textile. The wikis and blogs that I use can be configured to accept different formats, so text/wiki doesn't work. wunder -- Walter Underwood Principal Software Architect, Autonomy -- James Tauber http://jtauber.com/ journeyman of somehttp://jtauber.com/blog/
Re: Google Sitemaps: Yet another RSS or site-metadata format and Atom competitor
I've been serving my site (not the change log but the actual site) as an Atom feed for as long as my blog has had an Atom feed. One nice (and unintentional) side effect of this is that I can subscribe to the site map in Bloglines and have Bloglines tell me when my non-blog pages are being referenced as well as my blog pages. James On 03/06/2005, at 8:02 PM, Graham wrote: I don't see how a highly specialized format for a particular task is a competitor to or even compatible with what Atom does. There's nothing in our charter that says we've failed if it isn't possible to do everything conceivably related to website updates with Atom. And I don't see how Atom would benefit from becoming a jack of all trades. Graham
Re: PaceContentAndSummaryDistinct
On Mon, 16 May 2005 01:16:21 +0200, A. Pagaltzis [EMAIL PROTECTED] said: An even half-way intelligent user agent would do something like display a read more link or button when it displays a summary, to alert the user that there is more to be read, either at the atom:[EMAIL PROTECTED]'alternate'] location or in a supplied atom:content. I think this is the key criterion albeit not a particularly formal one. Which got me thinking: say I provide both a summary-only feed and a full-content feed. I believe it is reasonable to: 1. include a summary element in my full-content feed in addition to the content element; and 2. have some (short) entries in my summary-only feed which contain a content element but no summary. In other words: 1. full-content feed doesn't preclude the existence of a summary element but there will never be a summary element without a content element. 2. summary-only feed really means that the included summary/content won't exceed some arbitrary length. If the content is short enough to fit this, I'll use a content element, even though this is a summary-only feed because the content is complete---there is no read more. James -- James Tauber http://jtauber.com/ journeyman of somehttp://jtauber.com/blog/
RE: Autodiscovery, real-world examples
On Thu, 5 May 2005 16:35:21 -0400, Bob Wyman [EMAIL PROTECTED] said: Being able to distinguish between alternates for the current page and just other feeds that are linked to from the page would be very useful. +1 Also, in the case where there are multiple real alternates to the page, it would be useful to be able to mark which feed is preferred. +0.5 James
Re: PaceOptionalSummary
On Wed, 27 Apr 2005 06:35:21 -0400, Sam Ruby [EMAIL PROTECTED] said: While I agree that the implications of a decision to omit a summary need to be understood and carefully weighed by the feed author, I don't believe that mandating the summary element actually achieves this So.. can we agree on SHOULD? Well, given how close what I've said I agree to is to the wording of RFC 2119, I'll look inconsistent if I don't say 'yes' :-) I could certainly live with SHOULD. James -- James Tauber http://jtauber.com/ journeyman of somehttp://jtauber.com/blog/
Re: PaceOptionalSummary
Does much of this debate come down simply to whether there is a distinction between an empty summary and an absence of a summary? I am in favour of an optional summary because if there is no summary, I would rather not see summary/ I can understand that people that don't have a problem with summary/ meaning no summary would not see any reason to make it optional. James -- James Tauber http://jtauber.com/ journeyman of somehttp://jtauber.com/blog/
Re: PaceCoConstraintsAreBad
On 10/4/05 12:52 AM, Eric Scheid [EMAIL PROTECTED] wrote: could it be reasonable that an empty element gets displayed as empty, but an absent element triggers a fall back mechanism (eg. use the summary element, and if that is missing display the link rel=alternate resource? The first RSS Reader I used (SharpReader) would retrieve the linked resource and display that in the absence of content (and presumably of summary too if that distinction had been made at the time). I enjoyed reading that way and so, as a result, the first feed I offered for my own blog was a titles-only feed. While I have long since added a full-content feed, I continue to get new subscribers to the titles-only feed. James -- James Tauber http://jtauber.com/ journeyman of some http://jtauber.com/blog/
