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