<rdf:RDF
    xmlns:s='http://snipsnap.org/rdf/snip-schema#'
    xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'
    xml:base='http://snipsnap.org/rdf'>
    <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-77'
         s:oUser=''>
        <s:name>comment-feature requests-77</s:name>
        <s:content>I have been using SnipSnap for some time now and think it is great, however, there are a few things I would like to be able to do which I can&apos;t currently see a way of doing:&#xD;&#xA;&#xD;&#xA;1. Whenever someone registers with the wiki the first thing I do is give them editor priveleges which involves us having to alter the configuration settings every time. Is there a way of setting the default priveleges for a new user?&#xD;&#xA;&#xD;&#xA;2. I would like to be able to send an instant message to the people currently active on the wiki (perhaps using Jabber).&#xD;&#xA;&#xD;&#xA;3. I would like to be able to view the users on my system by the countries they come from. This could be done by filtering them according to their email address which is off a specific format (name@country.company.com)&#xD;&#xA;&#xD;&#xA;4. I would like to be able to have 2 snip names refer to the same snip (e.g. ABC and Another Boring Company should both link to the same snip). Most wikis I have seen tend to have the acronymn page containing a link to the expanded name page which seems pretty redundant to me.&#xD;&#xA;&#xD;&#xA;Can anyone suggest any answers to these problems?</s:content>
        <s:cUser>Chris Tomkins</s:cUser>
        <s:mUser>Chris Tomkins</s:mUser>
        <s:mTime>2004-06-16 09:54:34.358</s:mTime>
        <s:cTime>2004-06-16 09:54:33.559</s:cTime>
        <s:commentedSnip>
            <s:Snip rdf:about='http://snipsnap.org/rdf#feature+requests'
                 s:cUser='olli'
                 s:oUser=''
                 s:mUser='ramses'>
                <s:name>feature requests</s:name>
                <s:content>First see [snipsnap-roadmap]&#xD;&#xA;&#xD;&#xA;&#xD;&#xA;__DONE__ means: works at least in developer version or in released version.\\&#xD;&#xA;__NEW__ means: should be reviewed by the authors.&#xD;&#xA;&#xD;&#xA;Please use the bug tracker at http://sourceforge.net/projects/snipsnap for entering bugs.&#xD;&#xA;- __NEW__ Upgrade to jetty6 [ramses] 2006.06.02&#xD;&#xA;- __NEW__ The ability to export a snapshot of snip snap site as static html.&#xD;&#xA;- __NEW__ The ability to subscribe to notification (XMPP or otherwise) without modifying source code. - [trejkaz] 2005.02.14&#xD;&#xA;- __NEW__ The ability to tie extra attributes to user accounts (e.g. Jabber ID) so that they become as tightly bound to an account as an email address.  Also the ability to verify these extra attributes, to cut down on abuse. - [trejkaz] 2005.02.14&#xD;&#xA;- __NEW__ The ability to label new snips before first saving, also for blog entries. Then you can edit and label (Idea, Remember, Wish) new blog-snips before post. - [rbtst] 2005.01.22&#xD;&#xA;- __NEW__ Separate indexes for blog entries and wiki pages (the @ section in the index here is out of control) - [goofrider] 2004.05.25&#xD;&#xA;- __NEW__ Text titles for blog entries in index, page view, search results, etc., instead of (or in additional to) the current numeric titles - [goofrider] 2004.05.25&#xD;&#xA;- __NEW__ Conext-sensitive sidebar macros. e.g. a ~~sniplinks~~ macro on the sidebar will render links of the current page rather than those of [Snipsnap-portlet-1] itself - [goofrider] 2004.05.25&#xD;&#xA;- __NEW__ Publishing functionality - Why? A team can work on an offline system and, if editorial persons means the snips are OK, publish the snips to an online-system. This could be done a.) With an online-system realized as a namespace (\online\[\&lt;snips&gt;\]\[\&lt;subsnips&gt;\]) and/or, in an enhanced XL version, another snipsnap-instance (with the planned [p2p-functionality|SnipSpace Collaboration]) or b.) With version based labels, like software-version-systems. The publishing of snips should be snip-, namespace-, label- or system-granular. - [rbtst]&#xD;&#xA;- __NEW__ a way to draw process-diagramms like {link:Prozessdarstellung DIN 66001|http://62.2.89.141/dippweb/index/produktunterlagen/prozessdarstellung.htm} from a process-description. With these and with permission and versioning, it should be possible to use snipsnap as an collaboration QM-System. Everyone can from everywhere maintain QM-Processdiagramms (per Processdescripton) and -documentations (as a Snip and Attachements), link to- (Link Macro) or embedd external ressources (HTML include Macro) but only someone can approve and release changes whose someone made (?missing feature?). With an search macro or a more sophisticated query engine, a list of the actual QM-Documentation and there versions can printed. - [rbtst].&#xD;&#xA;- __NEW__ a &apos;bullet&apos; parameter to thje \{search\} macro, to display results as a list and not as an ureadable block. This one seems to be quite necessary and is requested in a few other feature-requests on this page. I maybe made a starter which is explained on [Lucene]. [JanPrill]&#xD;&#xA;- __NEW__ some way to suppress the suggestion to create a snip with the search term as name.&#xD;&#xA;- __NEW__ exclude the search macro call itself from search hits&#xD;&#xA;- __NEW__ web-based gui for snip edit in the way as http://www.pintexx.com is for web based html edit. large pages such as the feature request snip here or the wikipedia startpage are for normal users very hard to read and edit - [rbtst].&#xD;&#xA;- __NEW__ &quot;snips by this author&quot; list should be sorted. Either alphabetically or by the edit date would be better than what it is now, that is none, but even better sorting criterion could be passed to the macro as an argument. - [Davor]&#xD;&#xA;- __NEW__ support other URL types besides http. Example: file:/Users/geoff/Documents/Papers/ would create a link interpreted by my browser (Safari) to open up a folder in the Finder.&#xD;&#xA;- __NEW__ The zap button should have a confirmation dialog. We&apos;ve had more than one page accidentally zapped. - [benbenben]&#xD;&#xA;- __NEW__ Constrain weblog to [dated snips]. -[phobia]&#xD;&#xA;- __NEW__ Multiple recognized hostnames so self-referrals from e.g. www.snipsnap.org don&apos;t appear as external [BackLinks]. -[phobia]&#xD;&#xA;- __NEW__ More pervasive presentation of [snip types]. -[phobia]&#xD;&#xA;- __NEW__ could the search functionality be made so that if a snip title matches the search criteria exactly that the snip is displayed with other matches below?  this would often save me a click as i use search to navigate. [yeroc]&#xD;&#xA;- __NEW__ a more effecient .exists() method that just tests if a snip exists without loading it. [masukomi]&#xD;&#xA;- Dynamic search size in macro \{search\}&#xD;&#xA;- A line context with the highlighted search word, would make it easier to decide which snips (especially which comments) are relevant.  Recently, I was searching for XP, too see if they were any issues around running snipsnap in on Windows XP.  However many of the search results were about eXtreme Programming. [mlevison] ~~Lucene didn&apos;t support this the last time I checked. I will rework the search part in the future [stephan]~~&#xD;&#xA;- __NEW__ HTML rnd II - Several of my users have complained that they don&apos;t want to learn yet another markup language.  While I appreciate the security concerns, I&apos;m trying to lower the barriers to entry, so that there is no excuse not use our snipsnap as a good discussion server.  Could we have a &apos;preserve-html&apos; macro?  It would allow people who are additicted to &lt;b&gt;&lt;/b&gt; to be happy.  The management console could even be used to turn this feature on/off (avoiding the security risk). [mlevison] \\I have to second this. we&apos;re doing stuff which requires a specialized font in places and can&apos;t without html control. I think supporting html really ought to be an admin level decision not app level [masukomi]&#xD;&#xA;- __NEW__ A spelling checker [mlevison] ~~We already looked for spell checkers for some time and found only one usable. MacOSX supports spell checking in input forms ;-) [stephan]~~&#xD;&#xA;- __NEW__ For export of the snips, default name for the file: export-yyyy-mm-dd.xml or WEB-INF/Appname-yyy-mm-dd.snip, to avoid overwriting a previous backup - [soucpower]&#xD;&#xA;- __NEW__ A simple Manager-only option to edit snips/users at XML level. I think of something like editing single snip/user XML into an editable field, which can be reimported. This would allow &apos;cleaning&apos; the database for small mistakes made by the users. -- [pdinoto]&#xD;&#xA;- __NEW__ To avoid local names showing as referrers, a configuration parameter to hold all alternative names for the server. -- [pdinoto]&#xD;&#xA;- __NEW__ A manager option to purge referrer entries. -- [pdinoto]&#xD;&#xA;- __NEW__ Since users and snips share the same namespace, user creation should fail if a user tries to register with a name that already is being used as snip. For example, I can register myself as &quot;feature requests&quot;. -- [pdinoto]&#xD;&#xA;- __NEW__ I want to use SnipSnap as the document and discussion system for multiple development projects, each with different clients. This means I cant have clients see each others snips. Can a user be created or extended to have groups? Could each snip then be created with the their groups flagged for that user, with control via checkboxes on the edit form. Then all content served back to the user could be filtered by their groups? I looked at Interceptors and this may be any easy mechanism to implement this? I dont mind helping to code it if you can advise on how. ~~This sounds more like a CMS system I think and might take some time before implemented in SnipSnap (view permissions) as we probably do view permissions with encryption. Why not run several SnipSnaps in one instance? (klick on manager) -  [funzel]~~   I tried multiple instances just now, yes it will do for now. I didnt recognise that they all run in the same VM :-)  Only wishlist thing is a macro that takes you across to the other wiki along with your login/passwd?? - [robert42] ~~Well, we think about [Single Sign On] for SnipSnap and other Tools, this would include switching to another instance - [funzel]~~ In some case a fine granular permissions User/Roles/Groups and Read/Edit/Publish were very helpfull. Therefore i also request such feature. - [rbtst]&#xD;&#xA;&#xD;&#xA;- __NEW__ Can I make weblog-like pages manually with any date I want and have them appear in the calendar? I started using SnipSnap as a personal logbook, and would like to enter some entries from my paper notebook under their real dates, which may be several weeks in the past. Or in the future, too. That way I can use it to keep track of important dates, too. I tried creating a page with the title in the form &quot;yyyy-mm-dd&quot; so that its address looked the same as those of my weblog entries, but it still wouldn&apos;t show in the start page or be linked in the calendar. (I don&apos;t mind trying to implement this myself, but wanted to check whether the functionality is already there and I just don&apos;t know how to use it.) ~~ The functionality is not there yet, but we plan to add [Label] support for dates. [funzel]~~&#xD;&#xA;- Apple Rendezvous support [snipsnap-rendezvous]? ~~I think we prefer JXTA for our P2P binding, as long as there is no native java rendezvous --[funzel]~~&#xD;&#xA;- A way to include local and/or remote HTML pages inside a snip. Is this possible?  This is not possible right now and I think will not be done in the future because of security problems (we prohibit HTML in snips) -- [funzel] ... one soloution may be to provide a [HTML 2 SnipSnap] converter for importing remote/local HTML, and to allow authors to create snips in HTML and have them automatically converted (keeping only the wanted markup) :- [Cameron Braid] -- nice idea, we need this for XML-RPC GUI frontends too, which post links etc. with HTML - [funzel] &#xD;&#xA;- not too many features. I&apos;d request an architecture which focuses on the basics and lets everything else be handled by other &quot;things&quot;. Maybe some kind of pluggable architecture with SnipSnap as framework featuring a clean API and loads of useful Plugins. Want Email Support? Take this Plugin. Want a forum? Take that plugin. Want project management? Take this plugin, but beware it costs money :-). And so on. Probably not really a feature request, but an idea to think about. __PARTIALLY DONE__ Macros etc. are now plugins&#xD;&#xA;- __NEW__ Problem: uploading is for images only. I have written a FlashMacro to allow the embedding of SWF content in a snip (using \{swf:foo.swf|width=W|height=H\}) but after having uploaded the swf, file the &quot;Show/Hide Image upload&quot; thingy displays the file with the \{image:foo.swf\} hint. There should be some kind of a way to detect that a particular file will be linked using a particular macro, or something like that. --[lucsky]&#xD;&#xA;- __NEW__ the \{image\} macro has problems with the automatic naming, if the snipname where I include the picture (somename.png) is test, snipsnap looks for a picture names &apos;image-test-somename.png&apos;. If I include this snip via \{!test\} in a snip called hallo snipsnap looks for &apos;image-hallo-somename.png&apos; which does not exist. See the problem? Furthermore If I include &apos;hallo&apos; into &apos;schnipp&apos; it shows \{image:somename.png\} on the webpage. Is kind of a bug report, but sourceforge gives me &apos;Unkknown User&apos; while I&apos;m logged in  ~~[olli]~~&#xD;&#xA;- __NEW__ A way to create multi-levels list. \-- [lucsky] ~~I just hacked this in 0.3.3a. The syntax is to just concatenate list symbols (e.g., &quot;**&quot;, or &quot;*-&quot;) and the code opens and closes nested lists as necessary. What do I do to pass it back to the developers? \-- [Davor] ~~&#xD;&#xA;- __NEW__ Alright, how about this: graphical smileys as part of a theme :) -- [lucsky]&#xD;&#xA;- __NEW__ There must be an easy to use solution to detach a file as there is to attach a file to a snip. This should be done soon. It&apos;s is not intiutive to delete the files by hand on the server. -- [PHohn]&#xD;&#xA;- __NEW__ Plugins using BSF: Plugin development can be greatly simplified if it can be done in other scripting languages like Jython or Rhino (both of which supported by BSF). Users can write marcos and deploy them at runtime, without having to compile anything.  - [goofrider] 2003.04.06&#xD;&#xA;- __NEW__ More info in See Also and Search results:  Like times viewed, authors, etc. Not neccessarily displayed right next to the SnipLinks, in can be placed in alt text or something. Additional info can be really helpful when trying to look for relevant snips in a huge list  - [goofrider] 2003.04.06&#xD;&#xA;- __NEW__ Breadcrumbs:  A personalized list of recently viewed snips.  - [goofrider] 2003.04.06&#xD;&#xA;- __NEW__ Automatic Archiving: How are previous blogs archived ? The start page only goes back to 20March. Is there an automatic archive facility ? [PARubini] 2003.04.17&#xD;&#xA;- __NEW__ Snipname aliases: It would be nice if I could tell my snip \[Newsgroups\] to also act as \[Newsgroup\] and other things. This could perhaps be configured setting a [label] as in: aliases=&quot;Newsgroup, News, otherName&quot;. The headline of a snip would then display the names separated by comma so that the aliases are well known to be taken and active. [Atrus] 2003-06-26&#xD;&#xA;&#xD;&#xA;&#xD;&#xA;&#xD;&#xA;&#xD;&#xA;__DONE__&#xD;&#xA;- Named internal links, so that \[Hans|phobia\] is rendered as {link:Hans|/space/phobia} without the external link icon. [phobia]&#xD;&#xA;- Enchanced search facilities.  Return more than 10 hits.  A search for Feature currently finds 108 hits, but I can only see the first 10.  If there are more than 20/50/100 (whatever number), give us more hits link. [mlevison] ~~This has been there from the beginning, just change the search page to use \{search:\$query|100\}. [funzel]~~ __DONE__ &#xD;&#xA;- want to upload photos! __DONE__ (20021231)&#xD;&#xA;- Full UTF-8 support __DONE__ (20021231).&#xD;&#xA;- &quot;what&apos;s new since last page load in this weblog?&quot; would also be a great feature __DONE__ see \{since-last-visit\} macro&#xD;&#xA;- it would be nice, if the recent changes contains icons for comments and users. if we extend snipsnap in this way, the leading &quot;comment-&quot; of a snip need not to be displayed in the recent changes. __DONE__ (2002-11-28)&#xD;&#xA;- auto-login of a once authenticated user (after reading a lot about cookies) __DONE__ (2002-09-21)&#xD;&#xA;- longer list of recently changed snips __DONE__&#xD;&#xA;- need list of most-read snipets __DONE__&#xD;&#xA;- need a place for the weblog name for own applications (or should i replace the snip-snap logo at the top?) __DONE__&#xD;&#xA;- list of active users in the moment __DONE__&#xD;&#xA;- easier navigation from comments to the original wiki entry. __DONE__&#xD;&#xA;- would be nice if I could include images from other websites, someting like (picture: test|www.xyz.com/test.jpg) __DONE__&#xD;&#xA;- rightmanagement, I don&apos;t want others to edit my blog/wikis, maybe they can just comment, or disable edit/comment at all and registration needs to be verifyed by admin, or the creator can decide whether the snippet should be open to be edited by anybody or closed (comment only), comments and edits only from registered users (should not get too restrictive imho). __PARTIALLY DONE__&#xD;&#xA;- multidomain with a single server __DONE__&#xD;&#xA;- default page for not found wikis, not just a blank page (with a search of course) __DONE__&#xD;&#xA;- way to shutdown the server from commandline (for /etc/init.d/) Can be done with ./run.sh stop __DONE__&#xD;&#xA;- A way make Jetty serve local pages, either per app (a /static directory under each app directory) or per server (like a special &quot;dumb&quot; app). Tried to configure Jetty from XML config file without success. ~~There is a applications/&lt;app-name&gt;/static directory~~ -[funzel] __DONE__&#xD;&#xA;&#xD;&#xA;__DISPUTED__&#xD;&#xA;- [Why login for comments] for the feature: Anonymous posting of comments.&#xD;&#xA;- Automatic wikification. For example, if I create a snip named &quot;John Doe&quot;, then every time the words &quot;John Doe&quot; appear in another snip, they should be linked to the &quot;John Doe&quot; snip. This way my content becomes more hyperlinked with less effort. ~~How to tell Snip to link to &quot;John Doe&quot; and not &quot;John&quot; and &quot;Doe&quot;? This would involve testing every word combination in every snip, hard to do :-) But when storing a snip, SnipSnap will suggest possible snip links like &quot;John&quot; and &quot;Doe&quot;.~~ Well, the automatic linking could apply only to Wiki-style words (LikeThis). Suggesting possible links when storing a snip would be nice, but the great thing about Wikis is that I may write about MobBlogs 100 times before I actually create a MobLogs snip--but when I do all the old content will be linked to it automatically. ~~Well but you have to decide first to write (unreadable) MobLogs instead of Moblogs or MoBlogs or Mo Blogs. Then you could also decide to write \[MoBlogs\] and then the same arguments apply here - old content will be linked to it automatically. Even if you write \[Moblogs\] or \[MobLogs\] (which both could not be found with WikiLinking MoBlogs. Bottom line: we will not add WikiLinking anytime soon because we think it&apos;s unreadable and ugly (and doesn&apos;t give much advantage) for most people. People who think WikiLinking is automatic, just have adapted to ThinkingInWikiMarkup. Start thinking in brackets, it&apos;s the same. If you need it, go ahead, there should be only one regex to change.~~ - funzel</s:content>
                <s:mTime>2006-06-03 00:26:09.175</s:mTime>
                <s:cTime>2002-07-13 12:59:11.936</s:cTime>
                <s:comments>
                    <rdf:Bag>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-1'
                                 s:cUser='pmode'
                                 s:oUser=''
                                 s:mUser='pmode'>
                                <s:name>comment-feature requests-1</s:name>
                                <s:content>olli, can you propably give me some rights to add the feature requests?</s:content>
                                <s:mTime>2002-07-13 13:28:52.136</s:mTime>
                                <s:cTime>2002-07-13 13:28:49.528</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-2'
                                 s:cUser='leo'
                                 s:oUser=''
                                 s:mUser='leo'>
                                <s:name>comment-feature requests-2</s:name>
                                <s:content>Apache: see [install] and just take the logo on the bottom of this page.</s:content>
                                <s:mTime>2002-07-13 15:04:32.224</s:mTime>
                                <s:cTime>2002-07-13 15:04:25.184</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-3'
                                 s:cUser='leo'
                                 s:oUser=''
                                 s:mUser='leo'>
                                <s:name>comment-feature requests-3</s:name>
                                <s:content>As to the plugin architecture ... this is just about what we are aiming for :-)</s:content>
                                <s:mTime>2002-07-16 08:37:16.76</s:mTime>
                                <s:cTime>2002-07-16 08:37:19.4</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-4'
                                 s:cUser='fastjack'
                                 s:oUser=''
                                 s:mUser='fastjack'>
                                <s:name>comment-feature requests-4</s:name>
                                <s:content>Great :-)</s:content>
                                <s:mTime>2002-07-16 12:35:16.704</s:mTime>
                                <s:cTime>2002-07-16 12:35:12.344</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-5'
                                 s:cUser='pmode'
                                 s:oUser=''
                                 s:mUser='pmode'>
                                <s:name>comment-feature requests-5</s:name>
                                <s:content>I&apos;ve created such a script in /etc/init.d/snipsnap. It is only a test version but works fine for a first version.</s:content>
                                <s:mTime>2002-08-21 12:49:32.6</s:mTime>
                                <s:cTime>2002-08-21 12:49:34.952</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-6'
                                 s:cUser='Kriegel'
                                 s:oUser=''
                                 s:mUser='Kriegel'>
                                <s:name>comment-feature requests-6</s:name>
                                <s:content>how about disabling the register functionality?&#xA;- remove it from mainbuttons.jsp&#xA;- alter register.jsp&#xA;&#xA;is this enough? or do i have to change other places too?&#xA;&#xA;and what does the ${ page } in main.jsp?&#xA;&#xA;is it possible to split it up into&#xA;- ${ weblog }&#xA;- ${ see }&#xA;- ${ people-from }&#xA;&#xA;or something like that?</s:content>
                                <s:mTime>2002-10-04 19:22:06.16</s:mTime>
                                <s:cTime>2002-10-04 19:21:29.2</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-7'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-7</s:name>
                                <s:content>@kriegel: &#xA;$\{page\} renders the actual page, for example the Snip, or the register form. main.jsp is the frame around every page. So there is no need to split anything up, it&apos;s already splitted.&#xA;&#xA;\{weblog\} is a [Macro] that is part of the snip content (usually of start). It takes all [SubSnips] and renders them as a weblog.&#xA;&#xA;~~see~~ and ~~people-from~~ are part of the Snip renderer which is defined in snip.jsp. ~~see~~ is the JSTL tag &lt;s:snipLinks&gt; and ~~people-from~~ is the JSTL tag &lt;s:backLinks&gt;.</s:content>
                                <s:mTime>2002-10-07 09:23:44.544</s:mTime>
                                <s:cTime>2002-10-07 09:01:42.528</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-8'
                                 s:cUser='goofrider'
                                 s:oUser=''
                                 s:mUser='goofrider'>
                                <s:name>comment-feature requests-8</s:name>
                                <s:content>- [goofrider] suggests [FavoriteSnips], [BacklinksAsBacklinks], [RelatedLinks] and [Googlish-Search]</s:content>
                                <s:mTime>2002-10-23 05:42:41.6</s:mTime>
                                <s:cTime>2002-10-21 07:13:20.944</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-9'
                                 s:cUser='goofrider'
                                 s:oUser=''
                                 s:mUser='goofrider'>
                                <s:name>comment-feature requests-9</s:name>
                                <s:content>How about [Processing Directives] like #REDIRECT and #DEPRECATED?&#xA;</s:content>
                                <s:mTime>2002-10-30 21:29:09.208</s:mTime>
                                <s:cTime>2002-10-30 21:25:12.592</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-10'
                                 s:cUser='ruslan'
                                 s:oUser=''
                                 s:mUser='ruslan'>
                                <s:name>comment-feature requests-10</s:name>
                                <s:content>i hope __Full UTF-8 support__ means complete i18n, right?&#xA;&#xA;McKOI support international characters but SnipSnap needs to be flexible in defining content=&quot;text/html; charset=iso-8859-1&quot; parameter</s:content>
                                <s:mTime>2002-12-03 10:26:29.976</s:mTime>
                                <s:cTime>2002-12-03 10:24:35.28</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-11'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-11</s:name>
                                <s:content>We start refactoring SnipSnap for i18n when we reach beta. This means UTF-8 and language packs and application charsets.</s:content>
                                <s:mTime>2002-12-03 11:07:09.512</s:mTime>
                                <s:cTime>2002-12-03 11:07:12.224</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-12'
                                 s:cUser='dan'
                                 s:oUser=''
                                 s:mUser='dan'>
                                <s:name>comment-feature requests-12</s:name>
                                <s:content>Things I would like to see:&#xA;* Title for blogs.  Otherwise the RSS title looks wierd.&#xA;* Different RSS streams, one for blogs, one for site-wide changes&#xA;* An easy way to change the templates (How do I change the templates?)&#xA;</s:content>
                                <s:mTime>2002-12-05 18:47:07.872</s:mTime>
                                <s:cTime>2002-12-05 18:47:06.816</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-13'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-13</s:name>
                                <s:content>- There is an title in the RSS stream. This is taken from the application configuration title which can be change &lt;title&gt;SnipSnap&lt;/title&gt; &#xA;- Yes different RSS streams would be nice and easy to do. Perhaps you can take a look at the source, otherwise it may take some time&#xA;- The templates are easy to change. The layout and look is defined in CSS files. Just change the CSS files.</s:content>
                                <s:mTime>2002-12-06 09:19:45.064</s:mTime>
                                <s:cTime>2002-12-06 09:19:48.928</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-14'
                                 s:cUser='winkler'
                                 s:oUser=''
                                 s:mUser='winkler'>
                                <s:name>comment-feature requests-14</s:name>
                                <s:content>I&apos;d really like to see Categories..probably built on labels, as I understand the design.. this combined with granularity would allow subscribing to different facets..for example, javablogs.com readers have specific interests, and should only get the &quot;java&quot; category.&#xA;&#xA;Another one: a more recent referers list (&quot;people came here from&quot;).. this rewards links in the short-term. See diveintomark as an example..it reinforces the links and drives traffic back. Having a cumulative count is useful, but doesn&apos;t provide short-term visibility/reinforcement, because the hit count is too low to show up on the list.</s:content>
                                <s:mTime>2002-12-06 20:32:09.208</s:mTime>
                                <s:cTime>2002-12-06 20:32:09.88</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-15'
                                 s:cUser='omoikane'
                                 s:oUser=''
                                 s:mUser='omoikane'>
                                <s:name>comment-feature requests-15</s:name>
                                <s:content>PS: I didn&apos;t know where to post this.&#xA;How reliable is snipsnap? and how secure is it?&#xA;I guess the answer could be added to the to-do list.&#xA;Would the default setup survive a crash without loss of data?</s:content>
                                <s:mTime>2002-12-08 23:05:57.8</s:mTime>
                                <s:cTime>2002-12-08 23:06:00.808</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-16'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-16</s:name>
                                <s:content>@winkler: Yes, we too think that categories are one of the essential features.&#xA;&#xA;Referer: Yes, we thought about showing the referers at the bottom of each daily post, instead at the bottom of start. Clearing the referer list from time to time at specific posts (or downgrading the count) could be done (although I don&apos;t know how to do this in a senseful way).&#xA;&#xA;@omoikane: We run SnipSnap with aprox. 3500 Snips right now without problems (and with no crash). The cache policy is write through, but there might be problems with the default database (McKoi) because I can&apos;t predict the write-through policy of the database (You can use another one). Security might be a problem. We have not done a security audit yet, we will do one when we have reached beta because right now several things might change.</s:content>
                                <s:mTime>2002-12-09 09:21:15.408</s:mTime>
                                <s:cTime>2002-12-09 09:21:09.472</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-17'
                                 s:cUser='omoikane'
                                 s:oUser=''
                                 s:mUser='omoikane'>
                                <s:name>comment-feature requests-17</s:name>
                                <s:content>How are snips merged? I mean when you import a snip that already exist and you specify not to overwrite, what happens?&#xA;Does snipsnap support versioning? </s:content>
                                <s:mTime>2002-12-09 10:19:55.84</s:mTime>
                                <s:cTime>2002-12-09 10:19:51.128</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-18'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-18</s:name>
                                <s:content>@omoikane: The contend is appended right now. [Apinkin] works on versioning that we will use, see [RevisionHistory] but we do not support versioning right now.</s:content>
                                <s:mTime>2002-12-09 15:21:38.76</s:mTime>
                                <s:cTime>2002-12-09 15:21:36.528</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-19'
                                 s:cUser='manolo'
                                 s:oUser=''
                                 s:mUser='manolo'>
                                <s:name>comment-feature requests-19</s:name>
                                <s:content>Hi all.&#xA;&#xA;I&apos;m trying to change the default permissions of registered users, so that every registered user had &quot;Editor&quot; permissions at register time. Is that possible?&#xA;&#xA;Thanks.</s:content>
                                <s:mTime>2002-12-15 11:30:05.0</s:mTime>
                                <s:cTime>2002-12-15 11:30:16.824</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-20'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-20</s:name>
                                <s:content>No, actually not. But this is definetly a feature we&apos;ll implement soon. For now the only solution would be to edit the user creation source. Ask on the developer mailinglist when you&apos;re interested. Should be as easy as adding one line.</s:content>
                                <s:mTime>2002-12-16 09:17:22.08</s:mTime>
                                <s:cTime>2002-12-16 09:17:19.944</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-21'
                                 s:oUser=''>
                                <s:name>comment-feature requests-21</s:name>
                                <s:content>__Another feature request__&#xA;A macro that can be used as a RSS aggregator. &#xA;&#xA;\\{rss-link:url=http://slashdot.org/slashdot.rdf limit=10}&#xA;will display upto 10 headlines from the RSS feed as hyperlinks.&#xA;&#xA;I apologize for the duplicate posts ... I got a 500 error when I submitted the comment and I assumed the comment did not make it ... and I cannot seem to find a way to delete the comments.</s:content>
                                <s:cUser>Rish M</s:cUser>
                                <s:mUser>Rish M</s:mUser>
                                <s:mTime>2003-01-15 05:53:26.808</s:mTime>
                                <s:cTime>2003-01-15 05:49:52.504</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-25'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-25</s:name>
                                <s:content>Actually there is no way to delete the comment for you. Deleting can only be done by editors.&#xA;&#xA;Yes we had a RSS aggregator in the SnipSnap predecessor bur most people seem to use GUI RSS readers nowadays. But a RSS macro could be useful for &quot;portal&quot; style websites. I add this to our internal roadmap. Probably with mixin several feeds into one like Radio does it.&#xA;</s:content>
                                <s:mTime>2003-01-15 09:53:39.248</s:mTime>
                                <s:cTime>2003-01-15 09:53:35.128</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-26'
                                 s:cUser='frederic'
                                 s:oUser=''
                                 s:mUser='frederic'>
                                <s:name>comment-feature requests-26</s:name>
                                <s:content>There should be a way to delete its own comments. I got into the same problem than Rish (posting using Apple&apos;s Safari)</s:content>
                                <s:mTime>2003-01-17 19:30:34.904</s:mTime>
                                <s:cTime>2003-01-17 19:30:29.688</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-27'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-27</s:name>
                                <s:content>Well, deleting comments would violate the integrity of the comments thread. So we usually do not think of deletion of snips as a good thing. With beta and a better security layer, SnipSnap hosters could enable owners to delete their posts. On SnipSnap.org most probably this will not be enabled. Double posts? Who cares, not us. Just ignore them. If they are such a pain to you, I can delete them.</s:content>
                                <s:mTime>2003-01-18 11:21:18.28</s:mTime>
                                <s:cTime>2003-01-18 11:20:21.672</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-28'
                                 s:cUser='schwabe'
                                 s:oUser=''
                                 s:mUser='schwabe'>
                                <s:name>comment-feature requests-28</s:name>
                                <s:content>A few requests (some may be reinforcing other people´s requests...)&#xA;&#xA;* Documentation of macro parameters, not just names&#xA;&#xA;* Macro since-last-visit should be able to be called w/o parameters. In this case, this would mean &quot;since-last-visit&quot; of the currently logged user.\\Actually, this convention could be applied to several others, and analogously for dates (current date if parameter is empty).&#xA;* Provide a way for users to change their passwords onsite. As I have been able to determine, it is only possible to reset the password and have a key emailed to you. This is akward in the case the administrator has created user accounts with temporary initial passwords that users should change when first logging in.&#xA;&#xA;* A configurable template for new user snips.&#xA;&#xA;* Configure which snip the user is directed to after login&#xA;</s:content>
                                <s:mTime>2003-02-01 19:13:11.512</s:mTime>
                                <s:cTime>2003-02-01 14:46:31.2</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-29'
                                 s:cUser='petef'
                                 s:oUser=''
                                 s:mUser='petef'>
                                <s:name>comment-feature requests-29</s:name>
                                <s:content>I&apos;d like to see some kind of &apos;view source&apos; functionality whih would let me click on a view source link on a snip to see the snip as it appears in the edit screen with macros etc.&#xA;&#xA;This will make it much easier for people to learn new features - when they see something they like they can immediately find out how it&apos;s done.</s:content>
                                <s:mTime>2003-02-03 14:58:01.168</s:mTime>
                                <s:cTime>2003-02-03 14:58:00.792</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-30'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-30</s:name>
                                <s:content>__@petef:__ It&apos;s pratically there, just replace ../space/.. with ../raw/.. but there are allready to many buttons.&#xA;</s:content>
                                <s:mTime>2003-02-03 16:36:14.216</s:mTime>
                                <s:cTime>2003-02-03 16:36:20.704</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-31'
                                 s:cUser='soucpower'
                                 s:oUser=''
                                 s:mUser='soucpower'>
                                <s:name>comment-feature requests-31</s:name>
                                <s:content>__Another Feature Request From an end-user perspective__&#xA;&#xA;1. To encourage Knowledge sharing, by addition of snip, snip should be ratable/measurable (kind of did you like this document: 1-5), which would credit the snip owner&#xA;&#xA;1. Be able to record and view a diff between updated snip (to track update)</s:content>
                                <s:mTime>2003-02-14 09:42:59.912</s:mTime>
                                <s:cTime>2003-02-14 09:43:07.056</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-32'
                                 s:cUser='jolly'
                                 s:oUser=''
                                 s:mUser='jolly'>
                                <s:name>comment-feature requests-32</s:name>
                                <s:content>1 A couple things I might like to see implemented...&#xA;&#xA;* __A templating system for the Wiki Modules__\\- User (admin only maybe) selectable tags for bold and italics... make it act more like your favorite wiki =)&#xA;* __Flowchart creation__\\- Yeah, I know this one&apos;s stretching it a little, but hey -- you&apos;ve already got that nifty &apos;table&apos; macro...  It shouldn&apos;t be a ~~lot~~ of difference from that...</s:content>
                                <s:mTime>2003-02-26 17:03:47.784</s:mTime>
                                <s:cTime>2003-02-26 17:03:44.816</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-33'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-33</s:name>
                                <s:content>Well, flowcharts are currently not on our agenda, so it may take some time. But via the lazy web, perhaps someone writes a plugin. We plan organigram and UML sequence support though.</s:content>
                                <s:mTime>2003-02-26 17:37:46.504</s:mTime>
                                <s:cTime>2003-02-26 17:37:53.272</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-34'
                                 s:cUser='Davor'
                                 s:oUser=''
                                 s:mUser='Davor'>
                                <s:name>comment-feature requests-34</s:name>
                                <s:content>I recently hacked multi-level list support in 0.3.3a. The syntax is to just concatenate list symbols (e.g., &quot;**&quot;, &quot;*-&quot;, also numbered lists: &quot;1*.&quot; or &quot;*1.&quot;) and the code opens and closes nested lists as necessary. What do I do to pass it back to the developers, assuming they&apos;re interested to include it into the codebase? </s:content>
                                <s:mTime>2003-03-03 10:41:49.176</s:mTime>
                                <s:cTime>2003-03-03 10:41:44.32</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-35'
                                 s:cUser='petef'
                                 s:oUser=''
                                 s:mUser='petef'>
                                <s:name>comment-feature requests-35</s:name>
                                <s:content>@funzel: &gt; just replace .../space/... with .../raw/...&#xA;&#xA;Great, thanks. FYI this seems to break with Japanese characters, e.g. http://snipsnap.org/raw/leo</s:content>
                                <s:mTime>2003-03-26 16:46:35.6</s:mTime>
                                <s:cTime>2003-03-26 16:46:38.424</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-36'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-36</s:name>
                                <s:content>@petef: this might be a principal problem because of no html, but I take a look and see if I can fix it.</s:content>
                                <s:mTime>2003-03-26 17:46:47.584</s:mTime>
                                <s:cTime>2003-03-26 17:46:47.416</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-37'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-37</s:name>
                                <s:content>I think I fixed the buggy line. So the next bugfix release will include this. Or try CVS tomorrow.</s:content>
                                <s:mTime>2003-03-26 18:09:02.496</s:mTime>
                                <s:cTime>2003-03-26 18:09:03.176</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-38'
                                 s:cUser='nfrank'
                                 s:oUser=''
                                 s:mUser='nfrank'>
                                <s:name>comment-feature requests-38</s:name>
                                <s:content>Currently someone can edit the a snip even if someone is already editing it. This lead that the second who save his snip override all changes of the first one changes.&#xA;&#xA;It would be great if the snip could be locked and not editable as long as someone has not release it (and is still logged in).\\&#xA;At least, the second user should be notify someone is already editing the file.</s:content>
                                <s:mTime>2003-03-27 19:21:07.056</s:mTime>
                                <s:cTime>2003-03-27 19:21:02.456</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-39'
                                 s:cUser='apb'
                                 s:oUser=''
                                 s:mUser='apb'>
                                <s:name>comment-feature requests-39</s:name>
                                <s:content>A suggestion for enhancing the image macro. How about an additional optional argument called style. If supplied it would be used as a css style attribute on the html tag generated by \{image}. The main use would be specify a size eg style:=width:100%;height:10em.The motivation for this is mainly for [svg] support where the current code is hardcoded to a size of 400 by 400, but I think it would be usefull for any image. </s:content>
                                <s:mTime>2003-03-28 13:34:16.64</s:mTime>
                                <s:cTime>2003-03-28 13:34:16.208</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-40'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-40</s:name>
                                <s:content>@nfrank: Yes your&apos;re right. Currently we think locking a file and forgetting to unlock it (or some mechanism for unlocking it after some time (do all the others have to wait for some hours?)) is more troublesome than edit collisions (we did not have any yet in 6 months).&#xA;&#xA;@apb: Yes. We add that one. And a class attribute to add e.g. borders to all your images.</s:content>
                                <s:mTime>2003-03-28 13:53:46.384</s:mTime>
                                <s:cTime>2003-03-28 13:53:44.576</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-41'
                                 s:cUser='pascal'
                                 s:oUser=''
                                 s:mUser='pascal'>
                                <s:name>comment-feature requests-41</s:name>
                                <s:content>Would it be possible to allow for marking blog comments to be &quot;pinned&quot; to the top of the list on the ~~[start]~~ page?&#xA;&#xA;This would allow forcing blog entries to be placed at the top of the list as &quot;must read&quot; items for visitors to see first.&#xA;&#xA;</s:content>
                                <s:mTime>2003-04-01 00:00:27.4</s:mTime>
                                <s:cTime>2003-04-01 00:00:26.24</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-42'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-42</s:name>
                                <s:content>Who would decide which comments to &apos;pin&apos;? It&apos;s possible easier to just edit the portlet to the right. Or edit the &apos;start&apos; snip to include content before the weblog.</s:content>
                                <s:mTime>2003-04-01 12:19:59.608</s:mTime>
                                <s:cTime>2003-04-01 12:20:04.376</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-43'
                                 s:cUser='nexos'
                                 s:oUser=''
                                 s:mUser='nexos'>
                                <s:name>comment-feature requests-43</s:name>
                                <s:content>~~Apple Rendezvous support [snipsnap-rendezvous]?~~&#xA;&#xA;~~I think we prefer [JXTA] for our P2P binding, as long as there is no native java rendezvous --[funzel]~~&#xA;&#xA;Look at ftp://ftp.strangeberry.com/pub&#xA;&#xA;...and what about [SLP]?</s:content>
                                <s:mTime>2003-04-01 13:12:25.144</s:mTime>
                                <s:cTime>2003-04-01 13:12:28.24</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-44'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-44</s:name>
                                <s:content>1. I do not understand Rendezvous (the terms they use)&#xA;1. I can&apos;t get JRendezvous working, even with the help of the author. I tried the command line version to map a snipsnap url to a service, the service is found in Safari but the URL does not work</s:content>
                                <s:mTime>2003-04-01 13:25:07.448</s:mTime>
                                <s:cTime>2003-04-01 13:25:08.08</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-45'
                                 s:cUser='pascal'
                                 s:oUser=''
                                 s:mUser='pascal'>
                                <s:name>comment-feature requests-45</s:name>
                                <s:content>@[funzel]:  Editors or admins would be able to toggle the pin-up.  It depends on how you interpret your site/application roles.&#xA;&#xA;Items like a welcome message on the start page would be better handled as a snip that is placed before the blog content.&#xA;&#xA;Although, I can see a use for sticky blog entries that would float at the top. &#xA;&#xA;BTW - do jsp pages that are part of snipsnap-jsp.jar file __always__ override jsp pages placed in the application directory?  I have tried copying the page from the src directory to the application directory and make the changes - no go.  </s:content>
                                <s:mTime>2003-04-06 19:13:06.496</s:mTime>
                                <s:cTime>2003-04-01 17:21:55.04</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-46'
                                 s:cUser='hoffie'
                                 s:oUser=''
                                 s:mUser='hoffie'>
                                <s:name>comment-feature requests-46</s:name>
                                <s:content>What is the best way to allow for multiple blogs within a SnipSnap instance, say 5 blogs which have only one editor each?</s:content>
                                <s:mTime>2003-04-04 19:11:18.008</s:mTime>
                                <s:cTime>2003-04-04 19:11:20.352</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-47'
                                 s:cUser='leo'
                                 s:oUser=''
                                 s:mUser='leo'>
                                <s:name>comment-feature requests-47</s:name>
                                <s:content>@[pascal]: The jsp pages are handled like Servlets. Thus the precompiled pages override the .jsp files.&#xA;&#xA;@[hoffie]: This is a theoretical feature of [SnipSnap]. It requires that the &quot;~~post blog~~&quot; command handles users to post to their home snip. A weblog is currently just a snip with children and post blog adds a new snip as a child of ~~start~~. The \{weblog\} macro then extracts the children and displays them in the weblog manner.</s:content>
                                <s:mTime>2003-04-04 20:33:45.0</s:mTime>
                                <s:cTime>2003-04-04 20:33:54.504</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-48'
                                 s:cUser='soucpower'
                                 s:oUser=''
                                 s:mUser='soucpower'>
                                <s:name>comment-feature requests-48</s:name>
                                <s:content>@[leo]: The Weblog currently create a snip for everyday. Would it be better if the &quot;~~Weblog~~&quot; create a separate snip for each entry of the day ? The main weblog would then aggregate all the child snips.&#xA;&#xA;Talking about &quot;~~post blog~~&quot;, the first user who post, will be the owner of the snip for this day. Others will be able to post, but only him will be able to edit it. If each entry is a separate snip, then user wold be able to edit their own entry, but maybe not the main weblog ... - [soucpower]</s:content>
                                <s:mTime>2003-04-04 21:59:47.464</s:mTime>
                                <s:cTime>2003-04-04 21:59:46.488</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-49'
                                 s:cUser='hoffie'
                                 s:oUser=''
                                 s:mUser='hoffie'>
                                <s:name>comment-feature requests-49</s:name>
                                <s:content>@leo: I think you are saying I need to change the code for /exec/post.jsp so that it creates a new snip as a child of ~~user~~ and then each /space/~~user~~ page needs to contain the \{weblog\} macro.  But is the \{weblog\} macro able to take an argument of ~~user~~ so that it only shows children of ~~user~~ ?</s:content>
                                <s:mTime>2003-04-05 00:12:05.84</s:mTime>
                                <s:cTime>2003-04-05 00:12:07.408</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-50'
                                 s:cUser='leo'
                                 s:oUser=''
                                 s:mUser='leo'>
                                <s:name>comment-feature requests-50</s:name>
                                <s:content>@[soucpower] The question of whether a snip-per-day or per-entry is a question of [granularity].&#xA;&#xA;@[hoffie]: The \{weblog\} macro always works relative to the snip it is in. If you put \{weblog\} into a snip named &quot;foobar&quot; it will take all children of &quot;foobar&quot; and display them. Take a look at [leo] where the calendar at the bottom is a child snip. There is another ~~problem~~ right now with the postings. They are created with the date as name which is not unique in the [snipspace]. The parent-child relation is actually a legacy feature. [Stephan] is working on a solution.&#xA;&#xA;Having \{weblog\} work on any snip allows per-Topic weblogs instead of user-centered logs. &#xA;&#xA;P.S. The calendar entry on my page is created using [WebDAV]. A rudimentary implementation allows storing a file/iCalendar as a snip.</s:content>
                                <s:mTime>2003-04-05 10:31:28.752</s:mTime>
                                <s:cTime>2003-04-05 10:31:26.456</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-51'
                                 s:cUser='jolly'
                                 s:oUser=''
                                 s:mUser='jolly'>
                                <s:name>comment-feature requests-51</s:name>
                                <s:content>I&apos;m confused...  On the [snipsnap-DOWNLOAD] page, you give credit to [Davor] for nested lists, but I sill don&apos;t see how to use them.&#xA;&#xA;The only posts I&apos;ve seen regarding this ~~(which coincidentally were by [Davor])~~ note that you should just concatenate listing symbols.&#xA;&#xA;This, however, doesn&apos;t work on 0.4.2a.&#xA;&#xA;~~Hmm....~~</s:content>
                                <s:mTime>2003-04-06 06:10:45.656</s:mTime>
                                <s:cTime>2003-04-06 06:10:39.072</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-52'
                                 s:cUser='pascal'
                                 s:oUser=''
                                 s:mUser='pascal'>
                                <s:name>comment-feature requests-52</s:name>
                                <s:content>@[leo]:  To allow me to work on the jsp files directly, would I remove the snipsnap-jps.jar&#xA;from the application WEB-INFO/lib directory and unpack it at the top level of the application tree?&#xA;&#xA;{code:none}&#xA;cd ~~snipsnap-home~~/application/~~application-name~~/&#xA;unzip WEB-INF/lib/snipsnap-jsp.jar&#xA;rm WEB-INF/lib/snipsnap-jsp.jar&#xA;{code}&#xA;&#xA;I would expect I would need to restart snipsnap after doing this.&#xA;</s:content>
                                <s:mTime>2003-04-06 19:12:39.44</s:mTime>
                                <s:cTime>2003-04-06 19:12:39.552</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-53'
                                 s:cUser='pascal'
                                 s:oUser=''
                                 s:mUser='pascal'>
                                <s:name>comment-feature requests-53</s:name>
                                <s:content>Would it be possible to have &quot;not found&quot; message emitted when a \{!~~snip~~} is not found do the same thing as when a \[~~snip~~] is not found and allow for creating the missing snip?&#xA;</s:content>
                                <s:mTime>2003-04-06 19:48:30.016</s:mTime>
                                <s:cTime>2003-04-06 19:48:31.656</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-54'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-54</s:name>
                                <s:content>@Jolly: We did not add nested lists. They are in the process of integration into SnipSnap. I&apos;ll add them today.&#xA;&#xA;@Pascal: The not found is a snip. You can edit an change it. I&apos;ll add a name=&lt;non-existing-snip&gt; as a parameter so you can use this in the not-found-snip. __DONE__ in [CVS]. Just add&#xA;{code}&#xA;\[\{$name}\]&#xA;{code} &#xA;somewhere on the notfound snip. This will add a \[create name\] link.</s:content>
                                <s:mTime>2003-04-07 10:33:22.064</s:mTime>
                                <s:cTime>2003-04-07 09:56:18.44</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-55'
                                 s:cUser='schwabe'
                                 s:oUser=''
                                 s:mUser='schwabe'>
                                <s:name>comment-feature requests-55</s:name>
                                <s:content>Could it be possible to define the page buttons that appear at the top of the page as a snip with some special name (e.g., page-buttons-snip, possibly configurable in the application.conf file), instead of having to edit directly in the .jsp file (which has become more inconvenient to do now)?\\&#xA;The current functionality of each button would be accessible via macros or via direct links.&#xA;This seems to be almost already the case, with the exception of &quot;login&quot;...</s:content>
                                <s:mTime>2003-04-09 18:08:04.672</s:mTime>
                                <s:cTime>2003-04-09 18:08:05.832</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-56'
                                 s:cUser='hoffie'
                                 s:oUser=''
                                 s:mUser='hoffie'>
                                <s:name>comment-feature requests-56</s:name>
                                <s:content>@funzel Can you give an update on when you anticipate the multiple blog  feature being ready?  Is this related to the Labels implementation mentioned in another thread? BTW we are nearing completion of getting SnipSnap to work with Oracle.  Will keep you posted.</s:content>
                                <s:mTime>2003-04-10 01:24:01.544</s:mTime>
                                <s:cTime>2003-04-10 01:23:57.6</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-57'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-57</s:name>
                                <s:content>@hoffie: No multiple logs depend on namespaces start/2003-03-26 or funzel/2003-03-26 e.g. not on Labels. great.</s:content>
                                <s:mTime>2003-04-11 13:01:45.296</s:mTime>
                                <s:cTime>2003-04-11 13:01:51.272</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-58'
                                 s:cUser='robocoder'
                                 s:oUser=''
                                 s:mUser='robocoder'>
                                <s:name>comment-feature requests-58</s:name>
                                <s:content>Snipsnap equivalents for --&lt;blockquote&gt;...&lt;/blockquote&gt;,-- &lt;sub&gt;...&lt;/sub&gt;, and &lt;sup&gt;...&lt;/sup&gt;&#xA;&#xA;--Shortcut to renaming a snip.  (For managers, ala zap!)-- __WONTFIX__&#xA;&#xA;--Rendering more compact looking tables.-- __USE CSS__&#xA;&#xA;Delete attachments.  (I see checkboxes on the Attach page that presumably could be used to mark files to be deleted.)&#xA;&#xA;--Redirects.  (Keep an old snip after refactoring, and simply send users to the new snip.)-- __DUPLICATE__</s:content>
                                <s:mTime>2003-05-26 22:41:17.936</s:mTime>
                                <s:cTime>2003-05-24 22:30:00.432</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-59'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-59</s:name>
                                <s:content>@robocoder:&#xA;- &lt;blockquote&gt; you might try \{quote\}, yes sub and sup would be needed, what characters should we use?&#xA;- we won&apos;t support renaming of snips.&#xA;- tables use style sheets so you can change the look and feel&#xA;- delete attachments is in the pipeline&#xA;- redirects, see [Processing Instructions]</s:content>
                                <s:mTime>2003-05-26 12:47:31.32</s:mTime>
                                <s:cTime>2003-05-26 12:47:33.952</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-60'
                                 s:cUser='robocoder'
                                 s:oUser=''
                                 s:mUser='robocoder'>
                                <s:name>comment-feature requests-60</s:name>
                                <s:content>How about nestable \{quote\} blocks?&#xA;</s:content>
                                <s:mTime>2003-05-26 22:39:34.568</s:mTime>
                                <s:cTime>2003-05-26 22:39:33.272</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-61'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-61</s:name>
                                <s:content>Macros are currently not nestable because they are handled with a regex engine which knows nothing about context and not a parser.</s:content>
                                <s:mTime>2003-05-27 11:19:43.68</s:mTime>
                                <s:cTime>2003-05-27 11:19:41.816</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-62'
                                 s:cUser='tmjiang'
                                 s:oUser=''
                                 s:mUser='tmjiang'>
                                <s:name>comment-feature requests-62</s:name>
                                <s:content>Good day, funzel,\\&#xA;　I&apos;m a newbie for blog and snipsnap. There&apos;s two questions in my mind for a while.\\&#xA;　The first one, for HTML entity &quot;quotation mark&quot;. I&apos;ve used quotation marks in the title of a blog, and then I found they are not that safe as RSS feed using. When I use escape character &quot;backslash&quot; as prefix of quotation mark, they turn into themselves directly, but for HTML&apos;s convenience, I think they should be converted to entity format; how about just write in entity syntax? unfortunately, they will be plain text in their syntax.\\&#xA;　The second and also the last one, I&apos;m wondering if the start page could be separated into pages, because it seems getting slower day by day, since I post &quot;too many&quot; words to xml parser?\\&#xA;　Hope I explained them in the clear way on the above.\\&#xA;　And thank you for your patience to read this comment.\\</s:content>
                                <s:mTime>2003-06-02 00:51:50.752</s:mTime>
                                <s:cTime>2003-06-02 00:51:05.808</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-63'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-63</s:name>
                                <s:content>- I just don&apos;t get it what you wanted to tell me :-)&#xA;- Well the start page contains several pages (the day snips) which are aggregated to a weblog. There is a bug in the current version, the next version will fix this and limit the number of posts to e.g. 10 again</s:content>
                                <s:mTime>2003-06-02 13:48:58.176</s:mTime>
                                <s:cTime>2003-06-02 13:48:51.896</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-64'
                                 s:cUser='tmjiang'
                                 s:oUser=''
                                 s:mUser='tmjiang'>
                                <s:name>comment-feature requests-64</s:name>
                                <s:content>Dear funzel,\\&#xA;　Like these:&#xA;1. \&quot;&#xA;1. \&amp;quot;&#xA;&#xA;　The first one is ok for display but not ok for RSS feed. The second one is ok for RSS feed but not ok for display.\\&#xA;&#xA;　And thank you for your explaination about pages aggregation.</s:content>
                                <s:mTime>2003-06-02 14:15:57.92</s:mTime>
                                <s:cTime>2003-06-02 14:15:07.232</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-65'
                                 s:content=''
                                 s:cUser='tmjiang'
                                 s:oUser=''
                                 s:mUser='tmjiang'>
                                <s:name>comment-feature requests-65</s:name>
                                <s:mTime>2003-06-02 14:15:16.28</s:mTime>
                                <s:cTime>2003-06-02 14:15:17.176</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-66'
                                 s:content=''
                                 s:cUser='tmjiang'
                                 s:oUser=''
                                 s:mUser='tmjiang'>
                                <s:name>comment-feature requests-66</s:name>
                                <s:mTime>2003-06-02 14:15:24.344</s:mTime>
                                <s:cTime>2003-06-02 14:15:22.896</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-67'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-67</s:name>
                                <s:content>You could [contact us] via email.</s:content>
                                <s:mTime>2003-06-02 14:29:58.568</s:mTime>
                                <s:cTime>2003-06-02 14:29:52.728</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-68'
                                 s:cUser='sdowell'
                                 s:oUser=''
                                 s:mUser='sdowell'>
                                <s:name>comment-feature requests-68</s:name>
                                <s:content>Funzel said:&#xA;&quot;A way make Jetty serve local pages, either per app (a /static directory under each app directory) or per server (like a special &quot;dumb&quot; app). Tried to configure Jetty from XML config file without success. There is a applications/&lt;app-name&gt;/static directory --funzel DONE&quot;&#xA;&#xA;&#xA;Sorry for my ignorance..  Does this mean that there is a way to run Snipsnap so that Jetty is not serving any external requests? This would be nice. I&apos;d like to be able to run Snipsnap on my PC at work without my PC being a server on the network (which would be frowned upon). Can I do this? And what exactly do I have to do to implement Snipsnap like this?&#xA;&#xA;Thanks much,&#xA;Steve&#xA;&#xA;&#xA;</s:content>
                                <s:mTime>2003-06-15 21:22:55.12</s:mTime>
                                <s:cTime>2003-06-15 21:22:54.624</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-69'
                                 s:cUser='apyh'
                                 s:oUser=''
                                 s:mUser='apyh'>
                                <s:name>comment-feature requests-69</s:name>
                                <s:content>@til, I&apos;m confused by your comment.  Is there a way to enable SnipSnap&apos;s Jetty to use .htaccess style authentication for a particular snip?  If so, how do you do it?&#xA;&#xA;</s:content>
                                <s:mTime>2003-07-24 18:25:04.12</s:mTime>
                                <s:cTime>2003-07-24 18:25:05.504</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-70'
                                 s:cUser='maulik'
                                 s:oUser=''
                                 s:mUser='maulik'>
                                <s:name>comment-feature requests-70</s:name>
                                <s:content>@aphy, any word from til about using htaccess ?&#xA;i tried putting in stuff in the jetty.conf but then it wouldn&apos;t load my app...</s:content>
                                <s:mTime>2003-08-09 01:10:43.504</s:mTime>
                                <s:cTime>2003-08-09 01:10:41.752</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-71'
                                 s:cUser='liz'
                                 s:oUser=''
                                 s:mUser='liz'>
                                <s:name>comment-feature requests-71</s:name>
                                <s:content>Whatever happened to {link:this|./comment-feature+requests-19} feature request? </s:content>
                                <s:mTime>2003-10-09 00:07:25.784</s:mTime>
                                <s:cTime>2003-10-09 00:03:23.52</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-72'
                                 s:cUser='maulik'
                                 s:oUser=''
                                 s:mUser='maulik'>
                                <s:name>comment-feature requests-72</s:name>
                                <s:content>@aphy @til&#xA;&#xA;this should help:&#xA;[restricted access 2]</s:content>
                                <s:mTime>2003-10-21 23:10:53.272</s:mTime>
                                <s:cTime>2003-10-21 23:10:52.704</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-73'
                                 s:cUser='heikohaller'
                                 s:oUser=''
                                 s:mUser='heikohaller'>
                                <s:name>comment-feature requests-73</s:name>
                                <s:content>hmm, I got to this page by searching for &quot;reverse linking&quot;, but the Mozilla in-page searche tells me &quot;reverse&quot; does not occur in this page.&#xA;Is this a bug, is the search not up-to-date or am I doing something wrong?</s:content>
                                <s:mTime>2003-12-12 11:39:34.896</s:mTime>
                                <s:cTime>2003-12-12 11:39:34.52</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-74'
                                 s:oUser=''>
                                <s:name>comment-feature requests-74</s:name>
                                <s:content>I would love to add something like {link:Kung Tunes|http://www.kung-foo.tv/itti.php} or {link:Blogrolling|http://blogrolling.com/} to my Site. I just can´t figure out a way to add these kind of items without HTML Support. Is it possible? And if not, what happened to the idea of an {html} macro as an admin decission? &#xA;&#xA;Again, thanks for your patience!</s:content>
                                <s:cUser>der Dennis</s:cUser>
                                <s:mUser>der Dennis</s:mUser>
                                <s:mTime>2004-01-19 23:27:55.064</s:mTime>
                                <s:cTime>2004-01-19 23:27:56.984</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-75'
                                 s:cUser='funzel'
                                 s:oUser=''
                                 s:mUser='funzel'>
                                <s:name>comment-feature requests-75</s:name>
                                <s:content>\{html\} is not on the near-time roadmap.&#xA;&#xA;Best way is to write a small macro in Java or Groovy. Or add this to the roadmap, such small features would be easily added.</s:content>
                                <s:mTime>2004-01-20 10:16:40.056</s:mTime>
                                <s:cTime>2004-01-20 10:16:39.864</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-76'
                                 s:cUser='phobia'
                                 s:oUser=''
                                 s:mUser='phobia'>
                                <s:name>comment-feature requests-76</s:name>
                                <s:content>A macro that includes HTML fragments from attachments might be a good general solution for tools like these that upload to a web server.  Of course, there&apos;d need to be a mechanism for uploading to attachments (without depending on filesystem Storage.</s:content>
                                <s:mTime>2004-01-20 16:54:15.704</s:mTime>
                                <s:cTime>2004-01-20 16:54:15.304</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#comment-feature+requests-77'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#comment-feature+requests-77'/>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-78'
                                 s:cUser='germuska'
                                 s:oUser=''
                                 s:mUser='germuska'>
                                <s:name>comment-feature requests-78</s:name>
                                <s:content>__Feature request: Lock While Editing__&#xD;&#xA;&#xD;&#xA;Quite a ways back in the comments is a request for &quot;lock-for-edit&quot; functionality. I&apos;d like to suggest that this is more valuable than might be obvious based on the use profile of SnipSnap.org. My point being that at any time, the wiki in my company has as many logged in users as SnipSnap.org, but with a higher percentage of overlapping knowledge among those logged in users. One sees a new snip, reviews it, goes to add something, and clobbers changes that the original author was in the midst of adding immediately after submitting. (Of course, we never get it perfect the first time!) I think in this case, the risk of simultaneous edits is high.&#xD;&#xA;&#xD;&#xA;I&apos;d also suggest that Moin Moin seems to have come up with a pretty workable solution that could be nicked for SnipSnap. Plus, since SnipSnap doesn&apos;t have anonymous authoring, the locks would be even nicer because they would report the user who holds the current lock.</s:content>
                                <s:mTime>2004-06-22 21:37:43.242</s:mTime>
                                <s:cTime>2004-06-21 23:22:54.735</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#comment-feature+requests-78'/>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-79'
                                 s:cUser='jld'
                                 s:oUser=''
                                 s:mUser='jld'>
                                <s:name>comment-feature requests-79</s:name>
                                <s:content>I just noticed that the {link: SnipSnap.org Index page|http://www.snipsnap.org/space/snipsnap-index} lists everything cleanly alphabetically (while our own SnipSnap index does not).  The difference appears to be that in the SnipSnap.org index everything is connected to the root snipsnap.org/space/ directory, while we have many layers such as space/product/enhancements/idea.  When our &quot;Idea&quot; snip is listed in our index, it falls under &quot;P&quot; for product rather than &quot;I&quot; for Idea.  This makes the index somewhat cumbersome, as there are many items that are found in places that would not seem correct.  Would we need to have everything connected to the root space/ directory to fix it?  Or might we be able to add a feature allowing a different kind of sorting either by snip (regardless of hierarchy) or by including all of the roots above that snip?  Either of these would allow for a better index for those folks who have many layers of related pages.  thanks.&#xD;&#xA;</s:content>
                                <s:mTime>2004-07-22 20:33:49.472</s:mTime>
                                <s:cTime>2004-07-22 20:33:47.859</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#comment-feature+requests-79'/>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-80'
                                 s:cUser='rajorshi'
                                 s:oUser=''
                                 s:mUser='rajorshi'>
                                <s:name>comment-feature requests-80</s:name>
                                <s:content>Don&apos;t know if this is already available or not. But how about a macro for expandable lists? i.e. click a plus sign next to an item and a list of sub-topics appears, click a minus sign and the sub-topics go away.</s:content>
                                <s:mTime>2005-01-26 23:05:15.301</s:mTime>
                                <s:cTime>2005-01-26 23:05:14.067</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-81'
                                 s:oUser=''>
                                <s:name>comment-feature requests-81</s:name>
                                <s:content>I&apos;d like to see a printable output - quality printable output that is.  Not just &quot;suitable&quot; or &quot;sufficient&quot; but &quot;professional&quot; quality print.&#xD;&#xA;&#xD;&#xA;This likely means TimesRoman output, multilevel headers, footnotes, and no extraneous output (such as display headers and quicklinks).&#xD;&#xA;</s:content>
                                <s:cUser>David Douthitt</s:cUser>
                                <s:mUser>David Douthitt</s:mUser>
                                <s:mTime>2005-05-29 21:26:50.696</s:mTime>
                                <s:cTime>2005-05-29 21:26:46.13</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-82'
                                 s:cUser='phobia'
                                 s:oUser=''
                                 s:mUser='phobia'>
                                <s:name>comment-feature requests-82</s:name>
                                <s:content>This should be possible with a CSS theme alone.  Or do you mean PDF?</s:content>
                                <s:mTime>2005-05-30 05:07:17.032</s:mTime>
                                <s:cTime>2005-05-30 05:07:11.829</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                        <rdf:li>
                            <s:Comment rdf:about='http://snipsnap.org/rdf#comment-feature+requests-83'
                                 s:oUser=''>
                                <s:name>comment-feature requests-83</s:name>
                                <s:content>Actually, both.  A PDF would be useful for saving a portable, printable document; a CSS would be useful for printing directly.&#xD;&#xA;&#xD;&#xA;However, I noticed that only __one__ theme has a __print.css__ - and it&apos;s the optional thinkberg theme - and it&apos;s not even in the thinkberg/css/* directory tree.</s:content>
                                <s:cUser>David Douthitt</s:cUser>
                                <s:mUser>David Douthitt</s:mUser>
                                <s:mTime>2005-07-14 01:37:31.595</s:mTime>
                                <s:cTime>2005-07-14 01:37:20.831</s:cTime>
                                <s:commentedSnip rdf:resource='http://snipsnap.org/rdf#feature+requests'/>
                            </s:Comment>
                        </rdf:li>
                    </rdf:Bag>
                </s:comments>
                <s:snipLinks>
                    <rdf:Bag>
                        <rdf:li rdf:resource='#snipsnap-search'/>
                        <rdf:li rdf:resource='#FAQ'/>
                        <rdf:li rdf:resource='#snipsnap-roadmap'/>
                        <rdf:li rdf:resource='#snipsnap-index'/>
                        <rdf:li rdf:resource='#snipsnap-changed'/>
                        <rdf:li rdf:resource='#install'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#SnipSnap Theme'/>
                        <rdf:li rdf:resource='#goofrider'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#HTML 2 SnipSnap'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#deleting comments'/>
                        <rdf:li rdf:resource='#phobia'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#dated snips'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#text formatting'/>
                        <rdf:li rdf:resource='#MathML'/>
                        <rdf:li rdf:resource='#funzel'/>
                        <rdf:li rdf:resource='#label'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#spell checker'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#Why login for comments'/>
                        <rdf:li rdf:resource='#Testimonials'/>
                        <rdf:li rdf:resource='#start'/>
                        <rdf:li rdf:resource='#jolly'/>
                        <rdf:li rdf:resource='#chicao'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#snip types'/>
                        <rdf:li rdf:resource='#snipsnap-help'/>
                        <rdf:li rdf:resource='#Developer'/>
                        <rdf:li rdf:resource='#Install'/>
                        <rdf:li rdf:resource='#snipsnap-documentation'/>
                        <rdf:li rdf:resource='#winkler'/>
                        <rdf:li rdf:resource='#comment-snipsnap-roadmap-2'/>
                        <rdf:li rdf:resource='#olli'/>
                        <rdf:li rdf:resource='#snipsnap-QuickTour'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#SnipSnap Macro Tutorial'/>
                        <rdf:li rdf:resource='#snipsnap-download'/>
                        <rdf:li rdf:resource='#Kriegel'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#2003-02-26'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#Feature Matrix'/>
                        <rdf:li rdf:resource='#comment-zohar-4'/>
                        <rdf:li rdf:resource='#slarti'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#SnipSnap as CMS'/>
                        <rdf:li rdf:resource='#portlet'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#SnipSnap Eclipse SpikeGecko'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#UML Sketching'/>
                        <rdf:li rdf:resource='#snipsnap-portlet-1'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#4marcus'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#Semantic Web'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#Snipsnap as CMS'/>
                        <rdf:li rdf:resource='#subversion'/>
                        <rdf:li rdf:resource='#lucsky'/>
                        <rdf:li rdf:resource='#lsiljama'/>
                        <rdf:li rdf:resource='#calendar-leo-iCalExample.ics'/>
                        <rdf:li rdf:resource='#Contributed'/>
                        <rdf:li rdf:resource='#linux_tip'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#comment-SnipSnap Bugs-1'/>
                        <rdf:li rdf:resource='#Label'/>
                        <rdf:li rdf:resource='#snipsnap-DOWNLOAD'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#Use Cases'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#SnipSpace Collaboration'/>
                        <rdf:li rdf:resource='#LinkToExternalImages'/>
                        <rdf:li rdf:resource='#rybesh'/>
                        <rdf:li rdf:resource='#DV'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#Java Wiki'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#Language packs'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#List Formatter Tutorial 2'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#Release Checklist'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#Processing Directives'/>
                        <rdf:li rdf:resource='#boggle'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#Developer Version'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#SnipSnap CVS Access'/>
                        <rdf:li rdf:resource='#graph'/>
                        <rdf:li rdf:resource='#OKJSP'/>
                        <rdf:li rdf:resource='#Davor'/>
                        <rdf:li rdf:resource='#sidebar'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#chris swift'/>
                        <rdf:li rdf:resource='#Weblog'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#comment-Why login for comments-2'/>
                        <rdf:li rdf:resource='#Markdown'/>
                        <rdf:li rdf:resource='#comment-version-0.3.2a-2'/>
                        <rdf:li rdf:resource='#agamen'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#Macro Tutorial'/>
                        <rdf:li rdf:resource='#faq'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#2002-09-18'/>
                        <rdf:li rdf:resource='#Interceptor'/>
                        <rdf:li rdf:resource='#Backlinks'/>
                        <rdf:li rdf:resource='#comment-snipsnap-help-16'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#feature requests'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#2003-05-27'/>
                        <rdf:li rdf:resource='#Subversion'/>
                        <rdf:li rdf:resource='#MartinBurger'/>
                        <rdf:li rdf:resource='#comment-Architecture-1'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#Instant Messaging'/>
                        <rdf:li rdf:resource='#plionne'/>
                        <rdf:li rdf:resource='#BlogTalk'/>
                        <rdf:li rdf:resource='#eeverman'/>
                        <rdf:li rdf:resource='#ronal'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#Beta Features'/>
                        <rdf:li rdf:resource='#GeoURL'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#start/2004-04-05/1'/>
                        <rdf:li rdf:resource='#Themes'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#restricted access 2'/>
                        <rdf:li rdf:resource='#ivar'/>
                        <rdf:li rdf:resource='#comment-ASCII-1'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#RDF, DAML, OIL'/>
                        <rdf:li rdf:resource='#snipsnap-installed'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#2003-04-16'/>
                        <rdf:li rdf:resource='#ThoMo'/>
                        <rdf:li rdf:resource='#developer'/>
                        <rdf:li rdf:resource='#daTom'/>
                        <rdf:li rdf:resource='#version-0.3.2a'/>
                        <rdf:li rdf:resource='#comment-install-22'/>
                        <rdf:li rdf:resource='#dan'/>
                        <rdf:li rdf:resource='#tompra'/>
                        <rdf:li rdf:resource='#ecogeo'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#Dublin Core'/>
                        <rdf:li rdf:resource='#kaa'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#2003-01-07'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#SnipSnap XL'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#2002-11-27'/>
                        <rdf:li rdf:resource='#comment-Contributed-1'/>
                        <rdf:li rdf:resource='#Chris_Samuels'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#C++'/>
                        <rdf:li rdf:resource='#apache_1.3-snipsnap_0.5.1a_war-jboss-mysql'/>
                        <rdf:li rdf:resource='#LazyWeb'/>
                        <rdf:li rdf:resource='#MetaData'/>
                        <rdf:li rdf:resource='#radeox'/>
                        <rdf:li rdf:resource='#SubSnips'/>
                        <rdf:li rdf:resource='#comment-junji-2'/>
                        <rdf:li rdf:resource='#Moblogging'/>
                        <rdf:li rdf:resource='#NameSpace'/>
                        <rdf:li rdf:resource='#comment-Calendaring-1'/>
                        <rdf:li rdf:resource='#nihon'/>
                        <rdf:li rdf:resource='#comment-install-44'/>
                        <rdf:li rdf:resource='#sniplinks'/>
                        <rdf:li rdf:resource='#rbtst'/>
                        <rdf:li rdf:resource='#ysidoro'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#Advanced Wiki features'/>
                        <rdf:li rdf:resource='#chris'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#help by pva'/>
                        <rdf:li rdf:resource='#guest'/>
                        <rdf:li rdf:resource='#Calendaring'/>
                        <rdf:li rdf:resource='#dhamilto'/>
                        <rdf:li rdf:resource='#gandhi'/>
                        <rdf:li rdf:resource='#hibernate'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#2003-11-17'/>
                        <rdf:li rdf:resource='#soucpower'/>
                        <rdf:li rdf:resource='#stevemac'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#2002-12-19'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#List Formatter Tutorial 1'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#why is this project successful'/>
                        <rdf:li rdf:resource='#Wiki'/>
                        <rdf:li rdf:resource='#BackLinks'/>
                        <rdf:li rdf:resource='#comment-2002-09-20-2'/>
                        <rdf:li rdf:resource='#comment-Interceptor-2'/>
                        <rdf:li rdf:resource='#k-logs'/>
                        <rdf:li rdf:resource='#Statistics'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#2002-10-01'/>
                        <rdf:li rdf:resource='#tester12'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#User management'/>
                        <rdf:li rdf:resource='#ruslan'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#catalog macro'/>
                        <rdf:li rdf:resource='#mackdav'/>
                        <rdf:li rdf:resource='#Eclipse'/>
                        <rdf:li rdf:resource='#comment-install-42'/>
                        <rdf:li rdf:resource='#subsnips'/>
                        <rdf:li rdf:resource='#Nanning'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#comment-Bug Reports-1'/>
                        <rdf:li rdf:resource='#csg'/>
                        <rdf:li rdf:resource='#jcbabb'/>
                        <rdf:li rdf:resource='#Sandbox'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#2003-01-24'/>
                        <rdf:li rdf:resource='#comment-2003-02-26-7'/>
                        <rdf:li rdf:resource='#noista001'/>
                        <rdf:li rdf:resource='#Xanadu'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#Cameron Braid'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#gth/Application Strategy/Personal Productivity'/>
                        <rdf:li rdf:resource='http://snipsnap.org/rdf#'/>
                    </rdf:Bag>
                </s:snipLinks>
                <s:attachments
                     rdf:type='http://www.w3.org/1999/02/22-rdf-syntax-ns#Bag'/>
            </s:Snip>
        </s:commentedSnip>
    </s:Comment>
</rdf:RDF>
