<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
[==shifted to pmwiki-devel==]]<br>
<br>
FWIW, at the design level, I've thought about this quite a bit. I think
there are a number of "feeds" from a page that would be helpful in a
variety of circumstances (I've named them collectively "summary
feeds"): <br>
<br>
1. Web feeds (ie RSS or Atom, could also appear as summaries on
overview pages)<br>
2. Microfeeds (mini-summaries that can appear on teaser pages)<br>
3. Segment feeds (based on current #start#end approach, though could be
multiple sections pasted together, ie sets of marker pairs)<br>
4. Change feeds (more or less the current change page format, but
excluding minor changes if marked)<br>
<br>
My current thinking is that at least the first two need to be written
in separate text boxes, and this should happen on the edit page while
the user has the context to do it. Most of the time the user should be
able to accomplish this with a bit of cut and paste. Probably requires
use of tabs on the edit page. All types of feeds could have options
available to control timing and content of output.<br>
<br>
All feeds would be available for both publishing (RSS etc., by
inclusion on specified wiki rss pages? special application of
pagelist?), and internal website inclusion (regular markup).<br>
<br>
For inclusion, I would have (:includepage:), (:includemicrofeed:),
(:includewebfeed:), (:includesegmentfeed:), (:includechangefeed:),
though natively it could be something like (:include
selector=page|micro|web|segment|change pagename:). <br>
<br>
I think these options would be useful for internal website use, for
federating websites, as well for straight-on publishing.<br>
<br>
This might be much more functionality than is appropriate for PmWiki
(which I am looking at as more of an engine than a completed
application). In other words all of this might be far more appropriate
as an add-on (recipe).<br>
<br>
Also there are all kinds of issues around this that I haven't begun to
address, or probably even discover,. eg. the use of markup, the
interface on edit pages, ease of use in publishing or inclusion,
inclusion logic (eg. activation and expire dates) etc. etc.<br>
<br>
- Henrik<br>
<br>
Patrick R. Michaud wrote:
<blockquote cite="mid:20080527150943.GA13596@host.pmichaud.com"
type="cite">
<pre wrap="">On Tue, May 27, 2008 at 03:32:57PM +0200, Thomas Tempelmann wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Whenever I create a new page on my pmwiki, I like to offer a RSS link to
that readers can quickly learn of updates to the particular page.
</pre>
</blockquote>
<pre wrap=""><!---->
We've generally blocked on this particular feature because there's
not a clear statement of what such a feed should look like.
In particular, what should the description of each update contain?
If it's to be a summary of changes in the versions -- how can we
display that concisely in text?
Pm
_______________________________________________
pmwiki-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pmwiki-users@pmichaud.com">pmwiki-users@pmichaud.com</a>
<a class="moz-txt-link-freetext" href="http://www.pmichaud.com/mailman/listinfo/pmwiki-users">http://www.pmichaud.com/mailman/listinfo/pmwiki-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Henrik Bechmann
bechmann.ca
Webmaster, celos.ca webhosting services</pre>
</body>
</html>