Comments on: XoxoOutliner and further outline addressing adventures http://decafbad.com/blog/2006/11/15/xoxooutliner-and-further-outline-addressing-adventures It's all spinning wheels and self-doubt until the first pot of coffee. Fri, 19 Mar 2010 00:06:39 +0000 hourly 1 http://wordpress.org/?v=3.0-alpha By: Michael Poremba http://decafbad.com/blog/2006/11/15/xoxooutliner-and-further-outline-addressing-adventures/comment-page-1#comment-370648 Michael Poremba Thu, 18 Sep 2008 23:45:56 +0000 http://decafbad.com/blog/2006/11/15/xoxooutliner-and-further-outline-addressing-adventures#comment-370648 <p>Wondering if you ever completed your online outliner? Check out dynamiclist.com, a functioning but incomlete project I launched back in 2001. The editor is rich and works well. Been thinking of reviving now that all major browsers support the contentEditable tag.</p> Wondering if you ever completed your online outliner? Check out dynamiclist.com, a functioning but incomlete project I launched back in 2001. The editor is rich and works well. Been thinking of reviving now that all major browsers support the contentEditable tag.

]]> By: l.m.orchard http://decafbad.com/blog/2006/11/15/xoxooutliner-and-further-outline-addressing-adventures/comment-page-1#comment-51301 l.m.orchard Sat, 18 Nov 2006 21:40:41 +0000 http://decafbad.com/blog/2006/11/15/xoxooutliner-and-further-outline-addressing-adventures#comment-51301 <p>One reason I didn't use the #identifier URI syntax for suboutlines is because some gymnastics need to be done to get the hash through to the server from a browser. Otherwise, it gets treated as an in-page anchor. The semicolon syntax seems to work well for a set of path-segment parameters, and follows the standard (if I've read it correctly). </p> <p>In either case, it works for me, and should be just fine in a REST context - the suboutline syntax here should always identify a single parent outline node as a resource, and will eventually work for GET / PUT / POST / DELETE.</p> <p>Now I just need to implement a solution for the <a href="http://www.w3.org/1999/04/Editing/01" rel="nofollow">Lost Update Problem</a>.</p> One reason I didn’t use the #identifier URI syntax for suboutlines is because some gymnastics need to be done to get the hash through to the server from a browser. Otherwise, it gets treated as an in-page anchor. The semicolon syntax seems to work well for a set of path-segment parameters, and follows the standard (if I’ve read it correctly).

In either case, it works for me, and should be just fine in a REST context – the suboutline syntax here should always identify a single parent outline node as a resource, and will eventually work for GET / PUT / POST / DELETE.

Now I just need to implement a solution for the Lost Update Problem.

]]> By: Vincent D Murphy http://decafbad.com/blog/2006/11/15/xoxooutliner-and-further-outline-addressing-adventures/comment-page-1#comment-51294 Vincent D Murphy Sat, 18 Nov 2006 20:52:07 +0000 http://decafbad.com/blog/2006/11/15/xoxooutliner-and-further-outline-addressing-adventures#comment-51294 <p>I think (and said as much on Tom Morris' site) that a fragment identifier would be a better solution, in which case Opath would be a fragment identifier syntax for OPML and XOXO. At least it would be the best solution from a REST/web architecture point of view..</p> I think (and said as much on Tom Morris’ site) that a fragment identifier would be a better solution, in which case Opath would be a fragment identifier syntax for OPML and XOXO. At least it would be the best solution from a REST/web architecture point of view..

]]>