{"id":540,"date":"2005-06-17T19:08:00","date_gmt":"2005-06-17T19:08:00","guid":{"rendered":"http:\/\/sdi.thoughtstorms.info\/?p=540"},"modified":"2005-06-17T19:08:00","modified_gmt":"2005-06-17T19:08:00","slug":"540","status":"publish","type":"post","link":"https:\/\/blog.thoughtstorms.info\/?p=540","title":{"rendered":""},"content":{"rendered":"<p>Bill Seitz : <em>I think treating every page as an outline is a better direction to go<\/em><\/p>\n<p><a href=\"http:\/\/webseitz.fluxent.com\/wiki\/z2005-06-17-PhilJonesWikiOutlining\">http:\/\/webseitz.fluxent.com\/wiki\/z2005-06-17-PhilJonesWikiOutlining<\/a><\/p>\n<p>I&#8217;m wondering what this means in the SdiDesk context. That every page should really be a tree, rather like an HTML or XML document?<\/p>\n<p>That the basic, underlying representation of pages is plain-text is a non-negotiable virtue for me. I don&#8217;t want to get involved in XML as the base representation.<\/p>\n<p>On the other hand, at present SdiDesk treats pages with a bunch of heuristic substitutions (much as traditional wiki does). You can go a long way with this approach, but my rewriting bullet-lists is actually an admission that a more structured way of thinking works for this part of a page.<\/p>\n<p>The same is true of tables too. These are parsed into a special Table class.<\/p>\n<p>And if I allow table objects and list objects to be embedded sub-parts of pages, why shouldn&#8217;t we treat the page as a list of &#8220;nodes&#8221; which can be either table, bullet-list or paragraph?<\/p>\n<p>Could also be used to generate &#8220;table of contents&#8221; as with wikipedia . And allow finer (purple) addressing.<\/p>\n<p>Aaargh! Too many ideas to implement. Not enough time. Worth mulling over though. Comments welcome, as usual.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Bill Seitz : I think treating every page as an outline is a better direction to go http:\/\/webseitz.fluxent.com\/wiki\/z2005-06-17-PhilJonesWikiOutlining I&#8217;m wondering what this means in the SdiDesk context. That every page should really be a tree, rather like an HTML or XML document? That the basic, underlying representation of pages is plain-text is a non-negotiable virtue [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[473],"class_list":["post-540","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-uncategorized"],"_links":{"self":[{"href":"https:\/\/blog.thoughtstorms.info\/index.php?rest_route=\/wp\/v2\/posts\/540","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.thoughtstorms.info\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.thoughtstorms.info\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.thoughtstorms.info\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.thoughtstorms.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=540"}],"version-history":[{"count":0,"href":"https:\/\/blog.thoughtstorms.info\/index.php?rest_route=\/wp\/v2\/posts\/540\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.thoughtstorms.info\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=540"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.thoughtstorms.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=540"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.thoughtstorms.info\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=540"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}