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