gesehen bei chiapas.ch:
Das Blog "Mexiko, Licht und Schatten"

Mit Hilfe des unten beschriebenen BlooGee entsteht die neue "Liliths Lounge" - Ja. Man hat mich überstimmt. Nicht Loge, sondern Lounge. Naaaa gut!

Das BlooGee ist frei verfügbar. Da es jedoch ein Sport geworden ist, unsere Kommunikationswege zu stören, bieten wir allen Interessierten an, sich zum Beispiel im gerade neu entstehenden "Dabringhausener Kultur-Kiosk" in der Nähe von Köln mit uns in Verbindung zu setzen. Die Adresse und Öffnungszeiten schreibe ich unter anderem hier ins Blog. Inwieweit im Sommer eine Präsens in Köln selbst geöffnet wird, zeigt sich in den nächsten Wochen.

Nette Leute sind im Kultur-Kiosk jederzeit herzlich willkommen. Alle anderen bleiben besser zu Hause. Über die Eingangsschwelle kommen sie eh' nicht hinaus ...


P.S. Und immer schön die Lauscherchen kleinen Ohren in Stellung lassen! Wir spielen nämlich jetzt Im-Kreis-Drehen.

Mir fällt da ganz spontan "Bulworth" ein: Soooozzziallissmuuuus ... Gelle? ...
War aber wirklich alles nur Spaß. *g

BlooGee - Nr. 4
BlooGee - Nr. 3
BlooGee - Nr. 2
BlooGee - Nr. 1


!!Example 4
Even the smallest blog provides categories... no need for this special property. Simply use keywords as URI to create category MCOs. Add to the array of relatives in Example 3:

{{{
< related > http://page/contains/linktothis.html http://thissite/index.php?fitem=100 http://anysite/permalink=122 < fitem> http://anway/image.jpg keyword category
}}}
Since 'http://myweblog/permalinksphp?myID=11' is the permalink to this entry, http://myweblog/rpc.php?myID=11' its API for this entry. At this time (1 think ?;-)) there seems no way to use a simple convention to build querfies an items 'keyword' and 'category'. By default, the controller has to deliver an object based an a translation from 'keyword, category' to appropiate entry IDs. These entries contain information about all known (at least local) entries related to 'keyword, category' an your server. So the object representing a collection of categorized MCOs for 'keyword' may be:
{({


keyword
< URI > http://myweblog/permalinks.php?myID=keyword http://myweblog/rpc.php?myID=keyword
< body >
[CDATA]

This Image describes best what this category 'category' is all about:

[/CDATA]

< related>
< fitem > http: //page/contains/linktothis.html http://anway/image.jpg
< fitem > http: //myweblog/permalinks php?myID=12 < fitem > http: //myweblog/permalinks.php?myID=17 < fitem > http: //myweblog/permalinks.php?myID=19 http://yourweblog/categorycontroller/category
< /rel ated >

}}}
By default, the controller application (i.e. [[Pseudocode Controller - Beispiel]]) should search for an entry with the title 'keyword' if given a non-numerical ID.



!! Active Blog Objects (ABO) as MCOM implemetation
let you collect and combine information from a variety of sources
* help you find and display related content

* work with any permalink capable CMS and Weblog System

* fully integrate into DOM and MVC

* let you create Portals and blogs from scratch, based an semantics (related content) from various sources

* Show you which other objects link to an ABO

* provide a full API and messaging format

* let you create drill down pages and document trees



By using ActiveBlogObjects, instead of putting pieces of text together an one page and loading another fulll page by clicking some link you Start combining pieces of microcontent by referring them by their permalink. If the user loads a page, he receives a collection of microcontent objects from various sources. Then he might drill down into the contenxt of each object without euer reloading the main page or leaving the page where he had started from.



ABO consists of two main Parts: a JavaScript for the client, and specialiced Controllers written in PHP for the Server. Additionally, ActiveBlogObjects provide a wrapper and text parser dass to transform sources which do not even make implicit use of MCOM.



ActiveBlogObjects is a proof-of-concept implementation of the MicroContentObjectModel. Since Weblogs are perfect sources of semantical !inked microcontent objects, full of links and based an a common model of blog entries. Most of them allready provide a Standard Port for messaging (trackback) Support permalinks and are capable of appropiate tagging Single entries.



!!How to use ActiveBlogObjects?
All you haue to do is sending the JavaScript and a set of Parameters (URLs of the MCOs you want to display initially) to your visitor, along with the header of your index.html. Second, haue the appropiate controller(s) for the CMS(s) installed an your site(s). Third, create stylesheets for your views, create your own interface, view document trees and find paths between documents. Simply display together what is related. And saue the information of being diplayed along with the information to be dispfayed. Ask objects about their relatives, and Start to build networks of sematically linked microcontent.



!!Programmers only?
Noop. While lt is quite usefull to understand the concepts of related microcontent and MCOM (which both are no rocket sciences nor require a degre in informatics), only little technical knowledge is needed to use fit: simply add URLs to your entries, using the field for trackbacks. Getting a little help an designing Interfaces is recommended. By default, you can simply insert the JavaScript part into an empty entry, add the permalinks you wart to haue an the st arting page, and the script will overlay the containing page with a switchable Interface to this MCO's context. ABO IS ENTIRELY ALPHA VERSIONED!



XIwwwIMCOMTXT-File date: 13.05-2006-File time 10'49'33
X1 wwwIMCOM TXT - File date: 13.05.2006 - File time: 10:49:33



Keywords:
AJAX, Web 2.0, WEB 2.0, BlooGee, Markus Koch, Markus C. Koch
(siehe Koch in der Literaturliste Weblogs/Wikipedia und PHP-Nuke/Wikipedia)

Tagesschau-Chat mit Renate Künast, Grünen-Bundestagsfraktionschefin

Zur Entscheidung des Bundeskabinetts zum Einsatz der Bundeswehr im Rahmen einer EU-Truppe im Kongo, erklärt der Europaabgeordnete der Linksfraktion (GUE(NGL), Tobias Pflüger, Mitglied des Auswärtigen Ausschuss und Koordinator der Linksfraktion im Unterausschuss Sicherheit und Verteidigung: weiter

Fehlerhafter Prototyp
SQL-Injections fehlen

BlooGee - Nr. 5
BlooGee - Nr. 3
BlooGee - Nr. 2
BlooGee - Nr. 1



Bloglands ...

In practical terms: This model cries for example usage with common weblog and content management systems. Microcontent as generated by those systems is perfect: fit IS fall of links to external ressources, fit consists of tagged structures expressable in MCOM, messaging between Systems is widely supported, permalinks are a common way of retrieving unique microcontent elements (the reasons why examples tend to be entries from weblogs). Remember, an entry may contain a fall-blown webplication, script generating a collection of MCO... move away from categories and comments, rather add a MCO to your weblog and link fit to the respective thread (and to any other interesting resource). And don't forget to message the remote MCO about that ;-)



Resume

Constructing an MCOM object will result in an object which contains MIME based data and collections of metadata, at least an the object's location and MIME type. Additionally, a special collection named "relatives" contains information (URLs) an related documents which are not directly linked from the MIME data. This collection may be updated from MCOM objects linking to fit, Bither from MIME data or relatives collection. This is done by using "update", one of three basic methods: "finit" initially loads a MCO into a document, "expand" expands a node in a MCO's contextual network. While the displaying MCO is rendered by the client'S browser, object data is delivered by a simple serverside controller. Appropiate properties of the MCO are rendered and displayed as nodes within the DOM to simplyfy the view. AJAX techniques help retrieve and display semantical vectors and their resulting trees. MCOM integrates with MVC and DOM, so all objects can be expressed in common scripting languages.



Details an MCOM

will be published soon; the notes an MCOM in TiddlyWiki BIogScript_html contain more basic information and code, but haue to be translated from german. It also discusses the MasterBlogObject (MBO). CAVE: All these are rough notes and scripts, no warranties, changes reserved, all rights reserved, use at own risk.



XML style description of MCO
This is the minimum required to build and transfer an MCO. This no DTD, but kind of template.
{{{


this.title this.URI
this.messageURL
this.content < related>
this.relations(0)
this.relations(1)
this.relations(2)
}}}
Regarding the document body, [CDATA] should be used: data is not to be parsed by the XML Interpreter, but
what we ask the clients browser to display as a certain object within DOM.


!!Example 1
A simple hyperlink like {{{
before... btw. I found this Image:
[/CDATA]


http://page/contains/linktothishtml
< fitem > http: //thissite/indexphp?fitem=100
http://anysite/permalink=122
http://anway/image.jpg

}}}
Please notfite: the array of items is added "automagically by the controller!
For this, he conveniently tries to parse the body... and, of course, von may Lisa a specialised controller (serverside or as patt of the view) to transform http requests of properly tagged blog entries to MCOs.




X1 wwwIMCOM TXT - File date: 13.05.2006 - File time: 1049:33
MCOM.TXT - Printed an 13.05.2006, 11:52:11 - Page 4

Schnuckelchen, merci für die Info, dass du wieder auf meinem Rechner sitzt ... Irgendwie muß ich da grad' allerdings auch noch an was anderes denken. *fg* Ich kopier die neue BlooGee-Version denn morgen mal. Es ist genug für alle da!

MCOM.TXT-Printed an 13.05.2006,11:52:11 - Page 1
- Micro Content Object Model - Abstract & Documentation, V.01a

BlooGee - Nr. 5
BlooGee - Nr. 4
BlooGee - Nr. 2
BlooGee - Nr. 1


Purpose

This document describes the first version of the Micro Content Object Model and is an abstract about the MicroContentObject (MCO). It is intended as a paper for thinking about, discussing and using an appropiate model to handle microcontent. This approach does not use keywords to find and glue related pieces of microcontent, fit merely focusses - beyond computing relevancy from matching strings an web pages - an the fact that content preferably is linked to "real word" related content and applications, driven by criteria and ideas which are as individual as the context a collection of microcontent represents. Implementing MCOM should benefit the programmer as well as the user by accessing content and appropiate context in one convenient model.



Describing the Problem

After handling microcontent in a variety of environments, one had two recurring experiences: people only want to change small things if their collection (i.e. a news magazine or a corporate website) once has been established. These websites regularly consist of a number of items, displayed in a context (this context is what we usually call the webpage). Sometimes collections of collections haue to be arranged and put into a new context, creating thematical pages. Keywords, categories, RSS, commenting - content management consists of a variety of techniques and systems, all describing HOW to display content, bot not trying to describe the content itself: While on one hand we haue sophisticated models to translate the procedures from the real word into applications to handle whatever content a computer can display, on the other hand we lack of models describing the qualities and semantics of the content itself. Don't panic - this is far from the point of making a program conscious of its tasks. But we are moving one step mto the semantics of micro content objects: the relations (here: links from and to) with other micro content objects is made part of the objects properties. In simple words: people always wish to combine and update as well content as application applying their own ideas and criteria. More than that, they are not willing to deal with a Programmets view an categorization etc., while they are interested in the main question: how do I get A,B,C and D together on one page? And how do I tell that C relates to F and G, while A and B both relate to F? The answer is quite simple: saue the URIS of F and G tgether with A, and tell F and G about that. There saue fit along with them. Easy, hm? Not quite. Simple purpose and main question: "These items belong together. How do I tell them?"



What changes?

By applying the MCOM, you get a model that does not require any new programming language, skills, frameworks or included classes. By applying MCOM you get documents which you may manipulate based an their contents relationships. You may view and "drall down" into content of any MIME type and display content by levels from various sources, all on one dynamic page ("to contain and to be contained"). You get a new descriptor for the network of micro content objects - you even may view informational trees, display all documents along a certain "path" to a certain depth and get a dynamic view an all objects based an their "depth". With MCOM, you can script documents based on their content rather than based on their technical structure. All this can be dorre using the traditional web programmer's toolbox and is widely based an AJAX style - may be fit makes life a little easier by having one page displaying bunchs of content and deep links in one convenient place without euer reloading any new page a whatsoever site.



About this document and version

As mentioned, this is the initial version of the MCOM and its basic Basses. The code published for now uses *Pseudocode* for PHP and JavaScript. AS IS, IT WILL NOT WORK IN ANY PROGRAMMING ENVIRONMENT EXCEPT YOUR BRAIN. But the code should give you a rough idea and taste of the structure, logic and usage of MCOM objects along with common AJAX techniques.



Facts, please!

If you are in a hurry, just haue a look on the basic class code. You will find a MicroContentObject with some properties and three basic methods. The MCO-Model closely corresponds to the DOM and MVC. Objects may be constructed in (at least) any web-orientated OOP-style programming language an dient and Server (this document uses "quasi" JavaScript/PHP).



If you read the code by now - smile. It is es easy as fit seems, really. Remember: fit is a change of point of view (hm, eventually a little change in the model data). From there, you simply treat an fitem (i.e. an entry of a Weblog, an article in your favorite online magazine, a picture or Sound file an your homepage, a video stream or a fitem in your favorite online shop) as an object of MicroContent. Several Parts of MicroContent together make up a site, an application - or simply a web page with at least one fitem of content. A starting page consists of a collection of assorted MicroContentObjects. Simple, hm? But take a closer look: each fitem of MicroContent - each MicroContentObject (MCO) - has a structure to describe itself, induding its relations to other MicroContentObjects. This is the does essential part of a MCO is its collection of related objects, er bettet: the URLs of MCOs which link to or from this MCO. It is no matter if these objects reside on a local or foreign site. A MCO may haue a number of relatives, bot at least n = 1: the parsmg page (of course, a parsing page mainly consists of one MCO referencing other MCOs in its relatives collection). In other words: One always knew what one is linking to, but no one know who is linking to my content!



Back to the MCO dass: the first four properties make up 50% of the objects identity: URI, description, content make up the "display version" of an MCO. The feedback URL links to an Interface to manipulate the Model (from MVC) of the MCO, i.e, the database which the blog entry is part of.



Another 1501/1. is made by the relatives collection which consists of an array of URLs. Each URL identifies another MCO with its collection of relatives.



Do you get a smell?

Bingo, with a few lines of code and an object model you can start to display documents made from elements of microcontent in their contentual context. Documents which no longer let you jump from site to site, but show related micro content elements from different sources in one convenient place. Don't worry, bach source is original, no copies or caching. You no longer haue to go there by yourself - MCOs will do the work for you, all in one browser window. With one dick, you can display and dick through trees which no longer consist of websites (one after the other) but of numbers of related documents (on one page). Drill down in the tree of a certain document, find out paths between documents which are not linked directly.



Paths?

Well, I'd rather talk about vectors. These vectors haue a starting point A and an end point Z, each one described by an URL. Now, how many and which objects' collections do one need to reach Z from A? May be D and X, since D relates to A and X, and X relates to Z. Additionally, D also relates to F,G and H; X also relates to U,V,F and h. For now, the path between A and Z goes straight along D and X, and if we request and display the documents A,D,X and Z, we already get a pretty page an a certain subject. The subject is described by its path, the vector.



There's more...

Take a look back at the example: we display the vector by showing the documents lying an it. But what about the relations of elements tackled by our vector? These are F, G, H, U and V. And, if we take a closer look, some of these elements are referenced more than once. But before computing, let's take a look back an the MicroContentObject.



Methods and linking back

Using the MCO's update method, you may send messages about establishing a relationship to the other MCO. If appropiate, the remote MCO will add the messaging ressource to its relatives collection. Concerning this, in our example a lot of relationships is explicitly missing, since we did not regard the "backlinks" ("I contain you" - "All right, I'll notice that!"). If you look back an the documents tackled by our vector, some documents are linked more often from other documents. Imagines V references A - beside the known vector A,D,X,Z there is another implicit vector A, V, X, Z (since A does not reference V, you will only retrieve this vector if started searching from Z or if iterating through all relatives collections along the given vector). After all, wo may take all tackled documents plus documents an vector A, D, X, Z: this makes up A, C, D, F, G, H, U, V, W, X, Z. Mixed an one page, sorted and arranged by number of repeated relations, we get a view an the contextual network of a subject described by the vector.



Linking deeper

If we start displaying a vector, we only "drill down" one level: relations besides the vector reside in the background, only elements residing an the vector itself will be dsplayed. If we drill down one more level, all references are displayed which belong to elements an the vector, bot do not belong to the vector itself. One level deeper again, we look for all relatives referenced by elements one level up ... of course, each click through starting with some document and ending somewhere else describes the path between A and Z, hopping from URL to URL.



In MCOM, you conveniently display fit all an one page, no clickthroughs an websites. Instead: database-style drilling into content, based an levels of "relation depth", documents describing individual context through combination of micro content elements.



Using Vectors

Vectors are paths leading through coritextual networks. These networks are made of nodes of information, described by the MCO. Each node may be opened and will display new nodes. It is not neccessary to think of a "real path" leading from information A to information Z; instead, within the MCOM, fit is possible to regard any collection of MIME based micro content as a vector. lost ask each element for its relatives, and drill down to the underlying context.

Es war ein Fehler, vermeintlich politisch Andersdenkende mit Spitzelmethoden versuchen zu schaden.

Es ist ein Fehler, durch Artikel zu diesem Thema von den eigenen Taten abzulenken.

Was ist ein Blogger? Wer veröffentlicht mit welchen Methoden? Wer versucht trotzig und uneinsichtig, den Kuchen der Aufmerksamkeitsökonomie alleine zu essen? Welche Rolle spielen Medien in einer Demokratie? Welche Rechte genießen wir in der Demokratie, undemokratischen Entwicklungen zu begegnen?

fehlerhafter Prototyp
SQL-Injections fehlen


BlooGee - Nr. 5
BlooGee - Nr. 4
BlooGee - Nr. 3
BlooGee - Nr. 1


DEVNOTES.txt - Printed 13.05.2006, 11:52:26 - Page 1
BIooGee Version O.OOf public



This is the first version of BlooGee. What is BlooGee?

First of all, BIooGee is not a fall blown content management or weblog system. BlooGee is rather a library for displaying and editing existing content from variety of sources. Upon this library and its model you can build highly customizable Interfaces to existing structured data produced by commonly used Systems as mentioned above. The basic BlooGee wrapper makes extensive use of the famous libraries "Prototype" and "Scriptaculous" which are included with this distribution. You may use BlooGee to search and edit your existing content in a comfortable way, or build an additional "display and edit port" to existing structured data.



What does BlooGee need?

BlooGee needs the follwing things: a living datasource (basically MySQL with tables from MovableType or Post/PHPNuke, or use your own format, See below), a properly Set up Apache, PHP are Server side prepositions, the dient side will need a common browser with activated JavaScript. (!!This version works properly only using Firefox!!). Just copy the fites and directories in the package to a directory of your choice (fit should be accessable via Apache...), you may rename index.php as needed. Set up the datasource (which is a high risk at this time, you may loose ALL your tables, or anyone may edit your content...!) , call index.php in your browser.



How does BIooGee work?

Initially, BIooGee works like a simple weblog - fit produces an array which alway has the Same structure: {id, title, text, [array $relatives], [array yconfig]}. If no quert' string is specified, fit takes a default action (selection) from its default plugin and Passes the result (the array, See above) to the appropiate wrapper. This wrapper produces the HTML and JavaScript output which is sent to the dient If the basic controller (index.php) receives a quert' string, fit will be examined if fit contains block commands. If so, only the first is executed, if not, BlooGee treats the quert' string as a search term and delivers a collection to the wrapper which will format and return fit to the dient. BlooGee works with any datasource which has a PHP-accessable API if the appropiate dbadaptor is used. As well BlooGee may produce not only HTML output, bat also XML or popular formats Ilke RSS (if the appropiate wrapper is used).



What does 61ooGee consist of?

BlooGee consists of a Set of clientside scripts and a Set of Server side PHP scripts. lt makes use of AJAX related stuff and is based an a simple object model for microcontent. To construct the wrapper interface, the common libraries Prototype and Scriptaculous are used.



Wrapper

A wrapper is the HTML Part that is initially loaded into the browser. lt contains references to JavaScript, CSS and basic HTML. A wrapper IS used to put all elements an screen, fit is the basic layout template for BlooGee. A wrapper is only loaded an initially calling a BlooGee Page and ties together all elements and behaviours, also the wrapper decides which format is used for initial output.



Commands

BlooGees datasource interface accepts a basic Set of shorthands to retrieve content items. These can easily be wrapped into specialised plugins or controller pages. Additionally, they can be passed via GET or POST data to BlooGee. If used with Controllers, partial updates are possible (See the example Controllers). BlooGee only accepts commands, fitem ids or keywords as querystring.



Plugins

Plugins smply control the default behaviour of a BIooGee and are included into index.php. They may be used fo building querfies an own specialised block commands. Plugins should pass their output back to index.php, so in most Gases a plugin produces a fall Page output.



Controller

Unlike plugins, Controllers update only Parts of the wrapper Page. They use block commands, bat provide their own formatter. Controller are called "stand alone" (not through index.php), fit is up to the wrapper to properly ask for and render a Controllers output. Controllers may be Small and simple appications (Ilke the search controller), or a fall blown application for user registration and management.



DB adaptor

The datasource adaptor provides the interface between command langvage and the data. By default, BlooGee uses a MySQL database with MovableType tables. Further versions will contain adaptors for PostNuke/PHPNuke, Serendipidity, Google, Amazon and ebay. By using different adaptors in specialised Controllers, several datasources may be combined into one BIooGee Page. If the datasource is not an your own Server, the
DEVNOTES.txt - Printed an 13.05.2006, 11:52:26 - Page 2
dbadator has to provide the ca-rect AJAX talk which will be handled through the dient sided wrapper.




Messaging

BIooGees block commands make fit highly communicative. If you haue the appropiate controller, a remote BIooGee may be queried and even updated. If you haue a lock at the classes, you will find a basic object which carries information an "per fitem" or "permalink" basis. For example, a BlooGee may query other sites and update if something corresponds with an fitem - for example, if a remote URL is added to the relatives section. The other side may decide whether to store this information to the relatives section of its element, or not.


Notfite: in this version O.Ol.a messaging is only "implicit", which means there is no special controller for that. Since messaging is one of the basic concepts (and features) of BlooGee, the next version will provide a RPC-like command for remote updating.



Installation
// if you decide to use this version: //
Copy all fites and directories to your Webserver. Edit the configwation values for your MySQL database (in this version, you will haue to edit the fieldnames in the SQL Statements by hand) which will work with nearly any basic CMS table with id, title, text structure. Edit the Stylesheets as you need and Ilke. // DO NOT provide BIooGee a database user WITH writing permissions!!!!!! // // if you cannot change the database user: DO NOT USE ON THE WEB NOW! // // this is only an alpha version, use at own fall risk.
// You may use this version to edit local content er use read only datasources.//
// This is for security reasons; anyone may alter and delete your MySQL database, regardless of edit.php.//



This versions limitations:
- no real messaging between BIooGees
- no saving or printing of results
- no control of user state


For further versions... ToDo



Viewports

Vieports are Small HTML/JavaScript templates which the wrapper er controller has to apply an a per fitem basis, so an fitem containing a simple link to an avi fite or stream may be automatically wrapped into a fallt' configured player, Image viewer er plugin.



Saving lists
is not possible yet, bat will bee soon. And printing as well ;-))



Comments
For weblog style comments a controller would be fine...



Licensing

BIooGee is licensed under GPL. Donations welcome. Use at own risk and own fun. BIooGee is not for governmental or miltary use.



Dedication

This work is dedicated to friends who helped me a tot in the past two years. So these are special thanks to rww, dl, mmv, js, ah, hs, hj. And, of course, this is dedicated to my beloved son and his patience with fit all.


Ke
X;1 www1DEVNOTES. txt- File date 13.05.2006- File time_ 11,3112
X1 wwwl DEVNOTES txt - File date: 13.05 2006 - File firne: 11:31:12


Keywords:
AJAX, Web 2.0, WEB 2.0, BlooGee, Markus Koch, Markus C. Koch
(siehe Koch in der Literaturliste Weblogs/Wikipedia und PHP-Nuke/Wikipedia)

fehlerhafter Prototyp
SQL-Injections fehlen


BlooGee - Nr. 2
BlooGee - Nr. 3
BlooGee - Nr. 4
BlooGee - Nr. 5


README.txt - 13.05.2006, 11:51:57 - Page 1


What is BIooGee?

Initially, Bloo Gee was developed as a proof-of-concept work for a simple object model concerning microcontent. Main target is to provide an instrument to establish semantic networks, based an communications between webservers. BlooGee is (for now) a kind of add-on for weblogs and content management systems. It works on any structured content which can be described by a simple model identifyer, short description (or headline) and extended description (the main content). In this sense, almost any table with text data may be used by BlooGee. It is not intended as a replacement for existing systems, but as add-on for common blog Systems to establish communcation based an semantics between different weblogs.



How does BlooGee work?

In this first version, BIooGee simply provides a kind of desktop Interface to exsiting blog content as well as a command Shell to access (not only) Server functionality. There are some nice features like in-place editing, a Jot of AJAX-stuff and some basic tools to test and establish communications between different BlooGees. It basically supports a "site to site" protocol, based an simple HTTP requests. Concerning the content, BlooGee adds a special property to Single items: relations between micro content objects. In this sense, BlooGee provides search capabilities which are no longer based an keywords, but an semantics. If a search is done, it still starts with a keyword (and only one single keyword), but then focuses an (user provided) relations between items - and different sites.



BlooGee core functions

Basically BlooGee adds an abstraction layer for existing content. This layer is strictly embedded into a security layer which controls access to its core command Set. BlooGee supports unlimited users, user rights and command rights are expressed as simple numbers: if the command "level" is less or egaul than the user "level", the command is executed. In this sense, the BlooGee security model may easily be extended or used for own development. And - of course - own commands may be implemented.



Communication between BlooGee Servers

The BlooGee prototoll is inspired by existing peer-to-peer networks. Each time a request is made, lists of known other Servers are exchanged between Servers. And - of course - search requests are exchanged too. If a site is unreachable (but still up), a semantic network of BlooGees may fetch the content.



What is BIooGee made of?

BlooGee consists of a Set of PHP pages, a System database and a (individual configurable) main content database. Since BlooGee integrates ADODB, it is quite flexible regarding its environment. The surface is based an Scriptaculous and Prototype libraries. For coming versions, PEAR classes will be integrated for generating HTML pages.



Extensibility

BlooGee provides some simple APIs so it may be easily extended to own needs. Basically it needs an appropiate adaptor for its main content database. Since it is written strictly in the MVC model, BlooGee may easyly be extended with own Controllers to set up special functions.



Command Shell - VT-100 ;-)

Originally written as a debugger, the Command Shell provides terminal like access to BlooGee. It is like "tefneting weblogs" and has some interesting features for accessing content and BlooGees System database as well. Using the command shell, a simple webserver may be used like a "HTTP machine" to construct headers, monitor BlooGee activities, fetch and inspect remote sites, filter links from remote sites ...



How to use BIooGee

BlooGee may live in any subdir an the webserver. If configured properly, it provides a nice "blog desktop" with drag 'n drop capabilities, in place editing, user Jogin and a Page menu. If the command Shell is opened, it provides access to Server functions es described. To take full advantage of BlooGee, a change in the model of the content is required: Single items haue to be "tagged" with keywords and/or the URLs (permalinks) of related items. The more relatives, the more effective the semantic network. And the less the need of "keyword matches" for successful searches...



About this version

This is the first Version of BlooGee - still below 0.1 ;-) - which has the following capabilities:
- a full security layer, supporting an

- abstract layer of basic datbase commands.
- a full featured command Shell to access the
- basic Set of Server-to-Server prototoll functions; and
- an AJAX based desktop for blog-style display.
- Integration of ADODB.
- A widely open architecture for extensions and third Party plugins.




README.txt - 13.05.2006, 11:51:57 - Page 2

Note: this first version will preferably work an MySQL and Apache. Although a basic different between System tabies and content table is made, both (in this initial version) will haue to reside in the same db. Server protocol is limited to basics since there is still a problem with "exploding" requests so the appropiate code paus are more or less "symbolic". This will be fixed in the next version, which also will provide some more database adaptors for common Weblog/CM Systems (in O.OOf (at this time, there are adaptors for MovableType, Postnuke and Serendipidity).



TODO (for upcoming versions)

- establish real messaging and search capabilities between BlooGees.
- handle requests in System db by scripts
- export selections and results to tiddlers (TiddlyWiki friends - smile!!)
- and fix a Jot of bugs ;-))



PLEASE:
Read MCOM.txt and DEVNOTES.txt before installing BlooGee. USE AT OWN RISK, NO WARRANTIES. And: BACKUP YOUR DATA BEFORE INSTALLION!
XlwwwlREADME.fxt-File date: 13.05.2006-File time 11:34:01
X I wwwIREADME. txt - File date: 13.05.2006 - File time: 11:34:01



Keywords:
AJAX, Web 2.0, WEB 2.0, BlooGee, Markus Koch, Markus C. Koch
(siehe Koch in der Literaturliste Weblogs/Wikipedia und PHP-Nuke/Wikipedia)

Es war ein Fehler der gut informierten Lady aus den Medien, die Messer-Sätze mit hohem Wiedererkennungswert fallen zu lassen.

Foto: Kim Rebecca Feldgen

Sie hat sich entschlossen, das Basketballspielen wieder aufzugeben und stattdessen ihre ganze Freizeit inklusive der Wochenenden im Stall zu verbringen.

"Es ist genug für alle da"

Deutsches Netzwerk Grundeinkommen

Grundeinkommen.at

Basis Income Earth Network (BIEN)

Das „Spiel des Lebens“ gestalten!
Was Grundeinkommen an der ökonomischen und politischen Situation von Frauen ändert. (PDF-Dokument)

Attac AG - Genug für Alle

Small Planet Institute

FÜR 4 PERSONEN


600 g entbeinte Lammschulter, in 2,5 cm
große Würfel geschnitten

4 TL geschälte und fein gehackte frische
Ingwerwurzel

7 Knoblauchzehen, zerdrückt

2 EL gemahlene Koriandersamen

5 EL Weizenkeim- oder Erdnussöl

150 g Zwiebeln, in sehr feine halbe Ringe
geschnitten

''1/2 TL Kurkumapulver (Gelbwurz)

¾ - 1 ½ TL Cayennepfeffer

1 TL Salz

4 EL Naturjoghurt

450 g frischer Spinat, gewaschen und in feine Streifen geschnitten




Masroor Ahmed gab mir dieses klassische Mogul-Rezept für Lammfleisch mit Spinat. Die einzig neue Zutat, die im Laufe der Jahrhunderte hinzugefügt wurde, ist wahrscheinlich der Cayennepfeffer. Das Gericht ist auch unter dem Namen Saag Gosht bekannt. Saag ist ein Sammelbegriff für grünes krautiges Gemüse, während es sich bei Paalag ganz konkret um Spinat handelt.
Der Spinat muss relativ fein zerkleinert werden. Dazu jeweils eine Hand voll Spinatblätter zusammendrücken und quer in feine Streifen schneiden.
Mit indischem Brot oder Reis und einer Joghurtsauce servieren.

Das Fleisch in eine Schüssel geben. Ingwer, Knoblauch und Koriander hinzufügen, gut vermischen und 30 Minuten marinieren lassen. Das Öl in einer breiten, antihaftbeschichteten Kasserolle bei mittlerer Temperatur erhitzen. Sobald es heiß ist, die Zwiebeln hineingeben und goldgelb und knusprig braten, dabei, falls nötig, die Temperatur reduzieren.

Die Zwiebeln mit einem Sieblöffel herausnehmen und auf Küchenpapier ausbreiten. So viel Öl wie möglich aufsaugen lassen.

Mittlere Temperatur einstellen, dann das Fleisch mit der Marinade hineingeben. Kurkuma, Cayennepfeffer und Salz zugeben, eine Minute lang unterrühren. Den Deckel auflegen und 10 Minuten köcheln lassen, dabei ab und zu umrühren.

Den Deckel abnehmen, 1 Esslöffel Joghurt zufügen und rühren, bis sich der Joghurt mit dem Inhalt der Kasserolle verbunden hat. Den restlichen Joghurt nach dieser Methode einarbeiten, jeweils nur 1 Esslöffel auf einmal.

Anschließend den Spinat hinzufügen. Die angebratenen Zwiebeln hacken und ebenfalls zugeben. Umrühren, bis der Spinat zusammengefallen ist.

Den Deckel auflegen und bei sehr niedriger Temperatur etwa
50 Minuten garen, bis das Fleisch weich und zart ist, dabei gelegentlich umrühren. Ist keine Flüssigkeit mehr vorhanden, einige Esslöffel Wasser hinzufügen und den Deckel wieder auflegen. Der Spinat sollte am Fleisch haften.



Aus:
Madhur Jaffrey, Currys indisch. Currys kreolisch, Currys asiatisch. Mit 225 Rezepten, Christian Verlag München 2006



Keywords:
Curry, Currys, Gewürz, Gewürze, Gelber Ingwer, Gelbwurz, Indien, Indischer Safran, Ingwer, Ingwerwurzel, Knoblauch, Kochen, Koriander, Koriandersamen, Kurkuma, Kurkumapulver, Lamm, Lammfleisch, Paalag, Paalag Gosht, Saag, Saag Gosht, Spinat, Turmerik

Gut informiert und trotzdem keine Ahnung?
Liliths Tageslosung:
"Reiche niemals einem Mann ein Schwert, der nicht tanzen kann".

EZLN ERKLÄRT ALARMSTUFE ROT


via labournet.de:
Solidarität mit Atenco


Seit dem 3. Mai probt die Polizei - unter dem öffentlichen Beifall der Fox-Regierung - den Bürgerkrieg gegen die Bevölkerung von San Salvador Atenco: Pruegelorgien, Massenfestnahmen, Tote. Die Stadt (in der Nähe der Hauptstadt) war als "Hochburg des Widerstands" bekannt geworden, seitdem vor einigen Jahren eines der weltweit verbreiteten Renommier-Flughafen Projekte am Widerstand gescheitert war. Die Organisationen aus Atenco hatten sich am 1. Mai am "anderen Mai" von Zapatisten und Gewerkschaftsoppositionellen beteiligt. Ein Muster-Protestbrief "SCHLUSS MIT DER REPRESSION IN SAN SALVADOR ATENCO!" der Gruppe BASTA vom 6. Mai 2006.



SCHLUSS MIT DER REPRESSION IN SAN SALVADOR ATENCO!



Als Einzelpersonen und Organisationen für Menschenrechte und Solidarität mit dem zapatistischen Kampf protestieren wir energisch gegen die repressiven Massnahmen, die die lokalen, bundesstaatlichen und föderalen Autoritäten gegen den gerechten Kampf der BlumenhändlerInnen des Marktes von Texcoco, Teil der Front der Gemeinden zur Verteidigung des Landes (FDPT), durchführen. Sie haben vor, sie von ihren Arbeitsplätzen zu vertreiben.



Wir weisen die gewalttätigen Aktionen der bundesstaatlichen und föderalen Regierung zurück, die sie seit dem 3. Mai 2006 gegen die Gemeinde von Atenco durchführen und die Zusammenstösse und verletzte, festgenommene und tote Personen verursacht haben. Was in diesen Tagen passiert, ist die Konsequenz von systematischen Aggressionen gegen den Widerstand der Gemeinde von San Salvador Atenco, seit dem Versuch der Zentralregierung von 2002, der Gemeinde einen internationalen Flughafen aufzuzwingen.



Der Kampf für ihr Überleben und ein würdiges Leben, den die BlumenhändlerInnen auf dem Markt von Texcoco durchführen, ist ein Kampf von einfachen und ehrlichen Leuten. Die ökonomischen und politischen Eliten belästigen und unterdrücken die ArbeiterInnen, die Bauern und Baäerinnen, die Leute, die unten sind.



Wir fordern:

1. Die sofortige Freilassung der Festgenommenen.

2. Dass die Aggressionen gegen die Gemeinde von San Salvador Atenco eingestellt werden.

3. Den kompletten Rückzug der Sicherheitskräfte die ihre Ländereien besetzen.

4. Körperliche Unversehrtheit der AktivistInnen der "Anderen Kampagne"!Wir rufen die internationale Zivilgesellschaft auf, dass sie ihre Solidarität mit der Gemeinde von Atenco und ihre Ablehnung der Repression mit pazifistischen Aktionen ausdrückt.



Wir sind und bleiben in Solidaritaet mit allen AnhängerInnen der "Anderen Kampagne"!



(Unterschrift &Datum)



Emailadressen:

foxcontigo@presidencia.gob.mx, servscom@pgr.gob.mx, ghuerta@segob.gob.mx, gob@gubernatura.gem.gob.mx, mail@embamexale.de