| 1 | @sequence meta | 
| 2 | @title joko's sample notes - 2003-03 - ResourceIntegration | 
| 3 | @subtitle ResourceIntegration II | 
| 4 | @topic joko's Tasks | 
| 5 | @author joko@netfrag.org | 
| 6 | @document-mime-type text/plain | 
| 7 | @document-mime-type text/english text/german | 
| 8 | @document-mime-type text/vnd.twingle | 
| 9 |  | 
| 10 | @sequence meta | 
| 11 | @document-history | 
| 12 | @cvs-info | 
| 13 | $Id$ | 
| 14 | $Log$ | 
| 15 |  | 
| 16 | @sequence meta | 
| 17 | @x-transport | 
| 18 | @x-transport-from grasshopper.netfrag.org | 
| 19 | @x-transport-to quepasa.netfrag.org | 
| 20 | @x-transporter Microsoft Windows | 
| 21 | @x-transporter WinCVS [WinCVS 1.3.8.1 Beta 8 (Build 1)] | 
| 22 | @x-transporter-protocol cvs client-server protocol | 
| 23 | @x-transporter OpenSSH client on grasshopper [OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090607f] | 
| 24 | @x-transporter-protocol ssh [OpenSSH Version 2] | 
| 25 | @x-transporter OpenSSH daemon on quepasa [OpenSSH_3.4p1 Debian 1:3.4p1-1, SSH protocols 1.5/2.0, OpenSSL 0x0090603f] | 
| 26 | @x-transporter cvs [Concurrent Versions System (CVS) 1.11.1p1 (client/server)] | 
| 27 | @x-transporter-protocol cvs client-server protocol | 
| 28 | @x-transporter Linux running on quepasa.netfrag.org [Linux version 2.4.18-29um (root@linux) (gcc version 2.95.3 20010315 (SuSE)) #1 Sun May 26 17:01:48 CEST 2002] | 
| 29 | @x-transporter-protocol ext3 | 
| 30 | @x-transporter Linux running on h1.service.netfrag.org [Linux version 2.4.10-4GB (root@Pentium.suse.de) (gcc version 2.95.3 20010315 (SuSE)) #1 Tue Sep 25 12:33:54 GMT 2001] | 
| 31 | @x-transporter-protocol ext3 | 
| 32 | #@x-converter twingle [Twingle 0.01 - http://search.netfrag.org/twingle] | 
| 33 |  | 
| 34 | @sequence script | 
| 35 | @set o=@todo | 
| 36 |  | 
| 37 |  | 
| 38 |  | 
| 39 | @sequence block | 
| 40 | @injected | 
| 41 | @date 2003-03-06 20:29 | 
| 42 | @file [unknown] | 
| 43 | @x-editor Notepad [Microsoft Editor Version 5.0 (Build 2195: Service Pack 3) | 
| 44 | @x-transporter Microsoft COM | 
| 45 | @x-transporter-protocol copy & paste negotiation | 
| 46 | @x-editor UltraEdit [UltraEdit(r)-32 Professional Text/HEX Editor Version 8.10b] | 
| 47 |  | 
| 48 |  | 
| 49 | o use arial|verdana for netscape|mozilla rendering on netfrag.org | 
| 50 |  | 
| 51 | - We get spam! | 
| 52 | After feeling relatively safe through amavis based email filtering, it happened again. | 
| 53 | jonen recieved some spam again. | 
| 54 |  | 
| 55 | Why? | 
| 56 | I believe the addresses get collected by foreign agents crawling | 
| 57 | the growing content on netfrag.org. | 
| 58 |  | 
| 59 | What todo now? | 
| 60 | Mungle email addresses published on netfrag.org through some lisp- | 
| 61 | or scheme-based address-mungler found recently. | 
| 62 | They stay rfc-compliant, but are (hopefully) unreachable for common | 
| 63 | regex parsers. | 
| 64 | Send info to ->jonen. | 
| 65 | @tbd Automate this task! Do you wanna rewrite each address by hand...??? | 
| 66 |  | 
| 67 | o personal requirement: | 
| 68 | o daily: review contributions made by other users | 
| 69 | o requirement to solve this: have everything as rss/rdf and filter the xml by author | 
| 70 |  | 
| 71 | o rss.netfrag.org (register) | 
| 72 | o establish some web-based rss-browser embedding content from | 
| 73 | o RssGenerators for local content ... | 
| 74 | o news//rss (for news.netfrag.org) | 
| 75 | o cvs//rss (for cvs.netfrag.org) | 
| 76 | o ... and RssGateways to other ones, possibly at remote locations | 
| 77 | o phpWiki//rss (for www.netfrag.org) | 
| 78 | o TWiki//rss (for future www.netfrag.org) | 
| 79 |  | 
| 80 | o post to perl-development (nfo.dev.perl): | 
| 81 | o how to abstract the view/editing of xml-files via an api? | 
| 82 | o fetch: all|single-node | 
| 83 | o edit: single-node flattened into an object | 
| 84 | o browser layer: locator registry (pointing to a) an orm-db and b) to a file-set of xml-files (our control-db)) | 
| 85 | o item layer: view/edit nodes of an xml-file a) in a tree-editor (look at HTML_Tree_XYZ itself!!!) and | 
| 86 | b) split into our "flat-components" Item and List (object-like) | 
| 87 |  | 
| 88 | how b)? solve in backend! | 
| 89 | o backend | 
| 90 | o change values containing references to their interpolated placeholders to convert a node to an item | 
| 91 | ->getNode(...) | 
| 92 | example: getNode('root') | 
| 93 | o place querying api via XPath parallel to that -> also returns a single node or multiples (a node-set) | 
| 94 | ->getNodeSet(...) | 
| 95 | example: getNodeSet('xpath-query|named-filter') | 
| 96 | o establish backend querying api for xml-documents on top of that! | 
| 97 | ->sendQuery(...) should dispatch to one of ->getNode or ->getNodeSet | 
| 98 | o frontend | 
| 99 | o browse relations (parent-, child-node) using the ValueInterpolator and the ItemComponent | 
| 100 | o edit Attributes and Content of Nodes with the ItemComponent showing *two* areas (this is the "FlatteningOfNodes"): | 
| 101 | o -> attributes | 
| 102 | o -> content | 
| 103 | That's the way various XML-EasyTree-Xyz implementations use to work. | 
| 104 | @link http://www.cpan.org/ | 
| 105 | o frontend issues these generic rpc-commands to the backend (encapsulated somewhere) | 
| 106 | o ->sendQuery(array(remote=1, rpc=1, blah=1,   $query      )) - | 
| 107 | which gets dispatched by switching some stuff from "$query" to these methods under the hood (in fact, *implemented at backend side*) | 
| 108 | o ->getNodeSet('xpath-query|named-filter') | 
| 109 | example: | 
| 110 | $xml_filter_query = array( 'return' => 'object|object-set', [filter => 'xpath-query|named-filter'] ); | 
| 111 | (speak: Item or List) | 
| 112 | sendQuery(array(remote=1, rpc=1, blah=1,  $xml_filter_query , xml=1???   )) - | 
| 113 |  | 
| 114 | --> what is 'remote' and/or 'rpc' about??? | 
| 115 | if i remember that right - 'remote' means 'orm' (the datasource-type) and 'rpc' means 'rpc' (the transport-type) | 
| 116 |  | 
| 117 | o new twingle-symbol-topology using ... | 
| 118 | <code> | 
| 119 | o ... @-tags (stolen from JavaDoc via phpDocumentor) | 
| 120 | o @-tags only refer to scopes they live in | 
| 121 | o make the basic work: @todo, @link, @see, etc.  (but enhanced - of course - since perl doesn't limit you in any way....!!!) | 
| 122 | o add some more: @sequence, @is-a, @title | 
| 123 | o @see | 
| 124 | o @embed this-and-that from these .twingle files: | 
| 125 | o @link DummyNamespaces in PHP - final proposal.twingle | 
| 126 | o @link Re - Namespaces in PHP.twingle | 
| 127 | </code> | 
| 128 |  | 
| 129 | o project-metadata: / nfo topics | 
| 130 | <code> | 
| 131 | @is-a rfc | 
| 132 | @todo tbd | 
| 133 | x @topic source(cvs) | 
| 134 | x @topic doc(api) | 
| 135 | o @topic source(raw)  (via symlinks: expand directories first, symlink files afterwards!) | 
| 136 | o @topic doc(tutorial) | 
| 137 | o @topic doc(examples) | 
| 138 | o @topic doc(howto) | 
| 139 | o introduce: @subtopic: | 
| 140 | @topic source | 
| 141 | @subtopic raw|cvs | 
| 142 | @topic doc | 
| 143 | @subtopic api|tutorial|examples|howto | 
| 144 | </code> | 
| 145 |  | 
| 146 | o register: api.netfrag.org | 
| 147 |  | 
| 148 | o arcor!!! | 
| 149 |  | 
| 150 | o working alpha version of "Ts" on new server niu!!! | 
| 151 |  | 
| 152 | o .phpdocrc: split main code to module, integrate index-generation of predefined (registered) modules | 
| 153 |  | 
| 154 | o RssNewsletter: | 
| 155 | o schedule | 
| 156 | o hourly, daily, weekly, monthly, on-incoming | 
| 157 | o choose topic | 
| 158 | o all topics (cvs, news, api, docs, www) | 
| 159 | o choose destination | 
| 160 | o filtered-rss made available at specified url as xml or xhtml | 
| 161 | o via email | 
| 162 | o archived in archive-type (zip|tar) with format (html|) | 
| 163 | made available at specified url | 
| 164 |  | 
| 165 | o look at FreeBSD's "doscmd"!!! | 
| 166 |  | 
| 167 | o mechanism to refactor old smtp-mail-messages into new nntp-news-posts | 
| 168 | all our tools fail! *forwarding* the message seems to break mime (for e.g. the mozilla-viewer and probably others) | 
| 169 | o possible solution: strip "--- forwarded by ---" - header before actually posting | 
| 170 | maybe identifiable by subject: [Fwd: ] | 
| 171 |  | 
| 172 | o enhance Twingle: | 
| 173 | o twingle2message: | 
| 174 | o twingle2mail: twingle2rfc822, twingle2mime | 
| 175 | o twingle2news: twingle2rfc | 
| 176 |  | 
| 177 | o gather version info from installed components: | 
| 178 | o CPAN | 
| 179 | o PEAR | 
| 180 | x GNU: <program> --version   (e.g.: cvs --version) | 
| 181 | x OpenSSH: ssh -V | 
| 182 | x Linux: cat /proc/version | 
| 183 | o our Perl-/PHP- component system | 
| 184 |  | 
| 185 | o what are the MIME-types of XML-payloads sent between (e.g.) RPCXML-hosts??? | 
| 186 | text/xml??? | 
| 187 |  | 
| 188 | look at /etc/mime.types!!! | 
| 189 | e.g.: (stripped from there) - looking interesting: | 
| 190 |  | 
| 191 | text/* | 
| 192 | text/x-java | 
| 193 | text/uri-list | 
| 194 | text/rfc822-headers | 
| 195 | text/directory | 
| 196 | text/vnd.IPTC.NewsML | 
| 197 | text/vnd.IPTC.NITF | 
| 198 | text/vnd.motorola.reflex | 
| 199 | text/vnd.DMClientScript | 
| 200 | text/richtext | 
| 201 | text/rtf | 
| 202 | text/plain | 
| 203 | text/comma-seperated-values | 
| 204 | text/css | 
| 205 | text/enriched | 
| 206 |  | 
| 207 | --> vnd=vendor??? | 
| 208 |  | 
| 209 | @sequence references | 
| 210 | @title The text/enriched MIME Content-type | 
| 211 | @link http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1896.html | 
| 212 | @title Mechanisms for Specifying and Describing the Format of Internet Message Bodies | 
| 213 | @link http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1521.html | 
| 214 | @title The text/enriched MIME Content-type | 
| 215 | @link http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1523.html | 
| 216 | @title Mechanisms for Specifying and Describing the Format of Internet Message Bodies | 
| 217 | @link http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1341.html | 
| 218 | @title The text/enriched MIME Content-type | 
| 219 | @link http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1563.html | 
| 220 |  | 
| 221 | message/delivery-status | 
| 222 | message/disposition-notification | 
| 223 | message/external-body | 
| 224 | message/http | 
| 225 | message/s-http | 
| 226 | message/news | 
| 227 | message/partial | 
| 228 | message/rfc822 | 
| 229 |  | 
| 230 | inode/chardevice | 
| 231 | inode/blockdevice | 
| 232 | inode/directory-locked | 
| 233 | inode/directory | 
| 234 | inode/fifo | 
| 235 | inode/socket | 
| 236 |  | 
| 237 | multipart/* | 
| 238 |  | 
| 239 | o refactor some twingle tags using ETF: | 
| 240 | @link http://citeseer.nj.nec.com/borenstein94textenriched.html | 
| 241 | --- snip --- | 
| 242 | @misc{ borenstein-textenriched, | 
| 243 | author = "N. Borenstein", | 
| 244 | title = "The text/enriched MIME Content-type", | 
| 245 | url = "citeseer.nj.nec.com/borenstein94textenriched.html" } | 
| 246 | --- snip --- | 
| 247 |  | 
| 248 | o re-enable yakka! | 
| 249 | @link http://netfrag.org/~bareface/yakka/ | 
| 250 |  | 
| 251 | o search.netfrag.org | 
| 252 | o enable mnoGoSearch to index http://www.netfrag.org/docs/code/api/ | 
| 253 |  |