Is2: Information Space Reloaded

Welcome to Day:

(...) Communiqué 4 is the first native JCR (JSR 170) standard compliant enterprise content management solution available on the market today. Communiqué 4 revolutionizes content management by decoupling the content management application from the underlying repository.

MicroModels - ESW Wiki:

Developments around blogging and syndication have led to the emergence of Web formats which are closely related to HTML but are designed to carry explicit data. The purpose of this page is to assemble a collection of interoperable data models corresponding to each of these, along with mappings from the formats to the models. Semantic Web languages (RDF and OWL) offer a standard approach.
To rephrase a line from [WWW] microformats.org :
Designed for machines first and humans second, micromodels are a set of simple, open data models built upon existing and widely adopted standards. Huh? why machines 1st? How about: objective: making it cost-effective to record and share knowledge formally, i.e. so that computers can manipulate it.

Wikiwyg - Home:

Wysiwyg Editing Welcome to the Wikiwyg home page. Wikiwyg is the simple way to add Wysiwyg editing to your existing social software project.

One of those little chnages from MySQL 4.x to 5.x that can cause lot of angst ... If you see that lovely exception than make sure to find in which table it happens (from stack trace and logs) and then review the column - good chance you had "silent" truncation in MySQL 4.x that is no longer silent!

com.mysql.jdbc.MysqlDataTruncation: Data truncation: 
Data truncated for column 'author' at row 1; 
nested exception is: Data truncation: 
Data truncated for column 'author' at row 1

Is2 as part of "Atomverse"? Atom Store and the Atomverse - Migs Paraz - Random Takes:

(...) If we have a cosmos of blogs and static text supporting these formats, we could have an "Atomverse" of content that can be indexed, searched, read, and written. (...)

In Knowledge Database section of Chryler's Agile Knowledge Management: how to "maintain" and "grow" your Knowledge (Base):

(...) Now, to make such a base work, there are two things you need to learn, which I am only beginning to learn: 1) you must write stuff into it and 2) you must read it. Both are equally hard. Regarding 1), I have taught myself to write small notes whenever I find myself in the following situation:
- I have just had a problem
- I have done some research or thinking in order to solve the problem
- I have validated the solution
Most often, such information comes from the web in which case I can usually copy/paste directly from the website, along with my own notes.

If there are different levels of protection it is no longer wiki (sounds more like a generic microcontent) but still looks interesting - Sharing Your Brain: Making Your Hard Drive into a Wiki:

(...) What could come of all of this might be some shared spaces, some collective intelligence that two or more people agreed was a synthesis of information, agreement or shared understanding, that they owned in common. So your wiki would then have three 'flavours' of content:
* stuff that you created (more or less) yourself
* stuff that others created that you have taken for your own, your 'accepted wisdom'
* stuff that is 'shared wisdom' that you and others have inseparably created in common
We are presumably close to the point where transcriptions of conversations could also be indexed and added to this repository.

Google made Blogs possible by following links and allowing ot find content?

Sharing Your Brain: Making Your Hard Drive into a Wiki (Dave Pollard):

(...) The simplicity and near-zero cost of blogging software has allowed millions of people to become instant publishers -- producing everything from private newspapers to influential journals to travelogues of their vacations for the folks back home. Why write anything by hand, and why put your journal entries in a place where no one can see them, when it's just as easy to blog them so you can get Google to index them for you, and so that you can share them with the world?
I think the next tipping point will be focused on wikis. We are close to the point where we will no longer have to pick an 'application' to create, open or change a document, any more than we have to pick a particular type of writing implement to do so in the physical world. What that will allow us to do is convert our entire hard drive -- every document -- and all the content we maintain on central servers -- every message and blog post, into a single 'virtual' wiki, a kind of giant tableau of all our stuff, everything we have created or contributed to, and everything created by others we have filed away or bookmarked or otherwise 'taken as our own'.
(...) One of the challenges would be one that those of us who spend much of our lives online are already grappling with: How to integrate e-mails and conversations into our organization of more 'formal' documents. I'd be interested in readers' thoughts on this subject. How do we integrate the results of conversations and e-mail 'discussions' into our own brains, our 'frames of thinking'? My sense is that these context-rich exchanges and searches for common understanding are very important to us, and get distilled tacitly by our brains, in ways different from how we internalize either analytical writing or stories. How might we represent this in a wiki-brain tableau?

Agile Knowledge Management (Chryler):

(...) Code Browser is a small, open source editor which works with both Windows and Linux. CB has search capabilities - but its real strength is with the structuring. Two features cause this: folding and linking. The concept is really simple - a folder is like a smaller file inside a file, and a link is, well, a link to another file or folder. With folders, you can make a hierarchical structures, but if that doesn't suit you current need, you can use links to complement the folders, resulting in a relational structure.

I do the same - nice name BTW for the practice - Idea Database mentioned in Chryler's Agile Knowledge Management :

(...) One particular kind of knowledge that I keep, is ideas. I didn't have a systematic way of storing ideas before, and I have lost a lot of them because of this. Ideas are bits of gold that you should store even if you aren't going to do anything about it right away. I now have a large number of ideas for all kinds of things written down and the funny thing that happens, when I "surf" around every now and then, is that some of them merge and reveal a pattern of some greater idea which might end up being worth implementing. You should write down everything - and link to everything that is even slightly related. Not only that; you should write problems down as well - problems to which you don't know or see a good solution. Let it simmer, and given some time, a problem will evolve into ideaspace, ending up being a challenge rather than a point of irritation.

I like text editor too but after 2MB+ of notes it became a bit unwieldy and Is2 has advantage of suggesting "related" links and super efficient full text search but most of all it supports true linking (for now to topics but more is possible ...)

Kristian Dupont on Weblogs Forum - Personal Knowledge Management Platform I'm Considering for Development (Posted: Nov 28, 2005 2:02 PM):

I wrote an article called Agile Knowledge Management (http://www.chrylers.com/weblog/kb.php) where I describe my experience with various such tools. TheBrain (http://www.thebrain.com) and FreeMind (http://freemind.sourceforge.net/) are quite appealing but what I found, basically, was that a basic text editor was the right thing for me. The editor Code Browser (http://code-browser.sf.net) supports a form of linking and folding which works excellently for knowledge management.To me, at least, the editor based approach is better because it doesn't involve the mouse.

I had the same "itch" and Is2 is is the result ...

Weblogs Forum - Personal Knowledge Management Platform I'm Considering for Development (Dale Asberry): Why?

(...) Looks like you call feature the way "how" you are going to make it not "why". I wonder which problems this tool solves?
Good questions...
For me, it scratches an itch. I have a lot of stuff floating around amorphously in my head with a lot of links, hard references, and quotes. This tool would help me find what I'm looking for (and possibly spur new ideas) while browsing my personal knowledge base. Also, an executive that I've been discussing this with has some tools that help him manage his personal knowledge base, but they suck at integration and context-related searching. Finally, I've seen lots of rumblings from various A- and B- list bloggers that are requesting some of these features.

The reason this will not work is the same that components did not work except for very specialized domains: consts of APIs and framework far outweights need to install and run simple blog, wiki, or just hack its code ...

The Atomization of Software (Dave Pollard):

(...) it is very conceivable that software offerings could atomize into a World of 'Microapplication' Ends --
many small networked software developers, each designing small pieces of code that add useful functionality that can be plugged into existing Open Source applications.
There is no reason why these microapplications couldn't also be Peer-Produced -- co-designed by the customers who need them.
So, for example, it would be nice to have a microapplication that would add wiki functionality, or maybe podcasting functionality, to blogs. The wiki 'plug-in' to a blog would produce what is called a bliki. It would allow any reader of the blog to add his two cents to an article right in the body of the post (instead of in the comments thread below it) -- to become in effect a co-author of the article. The miniapplication would have to allow the original author some simple control e.g. the ability to tag readers' additions and changes and 'inline' comments in another colour, or to display them only as pop-ups or scroll-overs, or to remove them if she thinks they detract rather than add to the article.

Weblogs Forum - Tip: Enabling personal knowledge management (Vinny Carpenter): Re: Tip: Enabling personal knowledge management (Posted: May 18, 2004)

(...) Very cool. I do something completely similar. I have a blog setup hosted by Blogger. Blogger accepts blog entries via. email and so I just send emails to my special mail-to-blog email address and blogger automatically publishes it to my server. Take a look at the url below: http://www.j2eegeek.com/blog/todo/

BTW: last link does not work - another not cool URI ...

Not Found
Sorry, but the page you requested cannot be found. I just upgraded my blog software from Blogger to WordPress and wasn't able to maintain the same permalinks. I apologize for the inconvenience - Please use the search engine to find the blog entry you are looking for.

Tip: Enabling personal knowledge management:

(...) My solution: I bought a Sandisk Cruzer USB memory drive, installed the Java 1.4.2 JRE, Apache Ant, Apache Tomcat 5.0.19, Snip-Snap Wiki-blog, Apache James, and Zoë email "googler". I've written an Ant script to start all of the services. Tomcat is used to host Snip-Snap and James is used as the base mail service. I email interesting links with a quick blurb to an email account managed by James. I use Zoë to browse and index those emails. As I consider ideas surrounding any particular topic, I then update/add/rearrange topics in the Snip-Snap wiki so that I can capture those ideas. The whole point is to try to make idea capturing as easy as possible, otherwise I'm disinclined to write anything.

It can be compiled with JDK 1.1 and should work OK with CDC (aleady running on Zaurus!). Contains SSL and throttling as well - impressive!

O'Reilly CodeZoo: Tiny Java Web Server:

Very small footprinted (~50K) Java based web server and servlet container. JSP and J2EE deployment (.war/web.xml) included in a separate 40K module. The server doesn't require installation and ready to work just out of the box. Servlet spec 2.4.

How to use?

/*4 lines of code and the webserver is running!*/
Serve server = new Serve(4591);
Servlet ss = new SupportServlet();
server.addServlet( "/apphook", ss );
server.serve();

MySQL 5.0 Reference Manual :: 15.10 MySQL Cluster FAQ: Is it possible to use FULLTEXT indexes with Cluster?

FULLTEXT indexing is not currently supported by the NDB storage engine, or by any storage engine other than MyISAM. We are working to add this capability in a future release.

Error: "Specified key was too long; max key length is 1024 bytes" .. Very, very bad - will need to think if is2_triples should use BLOB/MEDIUMTEXT for URLs? This is very annoying as I tried to use VARCHAR(65000) for URIs ...

MySQL Bugs: #6751: The maximum key size is still 1024 bytes on InnoDB (mysql 4.1.7):

Thank you for the bug report. I have now updated the manual. Unfortunately, the global MySQL limit is still 1024 bytes per key. A problem in raising it is that MySQL stores key values in the stack, and stack consumption must be kept very low that you can create 10 000 connections = 10 000 threads in a 32-bit computer. The InnoDB internal limit is 3500 bytes.

And thanks to using UTF8 limit is even lower ... MySQL Bugs: #12522: Primary Key of two varchar(255) cannot be created

(...) The problem is your default charset is set to UTF8 so 342 * 3 (3 bytes for utf8) > 1000 For example:

mysql> create table f (a varchar(340) not null primary key);
ERROR 1071 (42000): Specified key was too long; max key length is 1000 bytes

Looks nice - Eclipe RCP based - JBlogEditor:

JBlogEditor is a FREE blog client to help manage blogs from the desktop. JBlogEditor uses metaWeblog and atom API to communicate with the weblog server. JBlogEditor is written in Java using the Eclipse Rich Client Platform. Some of the main features of JBlogEditor are: * Easy-to-use intuitive interface. * Publish to JRoller, WordPress & Blogger services. * Save drafts locally for future publishing. * Edit multiple posts simultaneously. * Advanced HTML tag completion. * Rich Text Formatting. * Support for multiple accounts. * Support for multiple platforms. (windows, linux & macOS X [experimental] downloads are currently available)

MySQL 5.0 Reference Manual :: 5.3.3 Server System Variables: ft_min_word_len (default is 4)

(...) The minimum length of the word to be included in a FULLTEXT index. Note: FULLTEXT indexes must be rebuilt after changing this variable. Use REPAIR TABLE tbl_name QUICK.
(...) Posted by daniel gaddis on March 29 2004 7:53am
if you set

[mysqld]
ft_min_word_len=3

you should also set

[myisamchk]
ft_min_word_len=3

if you use myisamchk Add your own comment.