Cover Pages: TMAPI 1.0 Alpha Release: Common Topic Map Application Programming Interface.: "The goal of TMAPI is "to allow developers to learn and use just one programming API for work with any topic map processing engine."
Gmail accessibility [dive into mark]: "The only way to use Gmail is the way that the Gmail designers use Gmail. The only way Gmail could be less accessible is if the entire site were built in Flash."
InterWikiMarkupLanguage (IWML): finally: ""InterWikiMarkupLanguage, intended to capture an interoperable subset of common wiki functionality. It is not meant to support everything that any wiki syntax is capable of representing, it is for reliable interchange between wiki systems."
We need this, I'm glad someone is tackling it.
Yahoo! Groups - Groups Abuse: I can't seem to access Yahoo's feedback forms. Everytime I click a link to contact them I get an error page. Anyone?
Doing subtitles in Vegas: Export the audio of your movie, get this free subtitling tool, subtitle, save subtitle file, install a plugin and import the subtitle file like this. (I haven't tried this out yet.)
Another First-Time Filmmaker (11/99).
Sound is by far the most technically complex aspect of the documentary, at least for me. We used an excellent shotgun mike. I plugged it in the wrong hole a few times, and for some tracks, for some strange reason I haven't been able to figure out, the sound was recorded mono (not stereo) and too loud. It doesn't sound good. I'll try to figure out a way to reduce it's volume while making it sound better.
$14 Steadycam: build your own steadycam.
On a related note, I've started editing the Colombian documentary using Vegas 4.0 on my $800 Windows XP computer (+ $160 external 160 Gig harddrive).
I've already uploaded 3 hours of video in my project and Vegas hasn't flinched. I was worried about being able to edit 20 hours of video on my cheap machine, but now I feel confident. I love Vegas.
I skimmed through the manual today on the train (for about 1 hour), and I think I know everything I need to now. The interface is remarkably easy to learn, because everything maps to easy to visualize real-life metaphors.
One thing I'm trying to figure out that the manual didn't talk about much is how to organize all that video while editing. I created a "temp" track where I park stuff temporarily, a "final" track that should contain the final edit, and a track for each of my 23 tapes (so I can easily refer to my printed log that shows all the scenes on each tape with notes).
Vegas lets you add notes and stuff, but even after only having 2 tapes (2 hours) of video on their tracks and taking out cuts and moving them into the final track, I'm getting confused on how to manage this.
I am cutting out cuts of their track and moving them into the "final" track so I know which cuts I already used. I can then look at the tape 7 track for example and see if there's anything else in there (not yet cut out) that should make it into the final track. I think this will work.
I also created a "filler" track: images of mountains and roads and nature and such that can be used as filler pretty much anywhere in the documentary - as opposed to cuts of action or interviews that need a specific place.
Any ideas on organizing this stuff in while editing are very welcome!
Big Fractal Tangle: the deal with don: "Ten years ago today, I signed away 51% of my second software company, Gravity Systems Inc, to a businessman with an incredibly deep gravely voice named Don Van Natta.
[...]
Aside from my plasma trips, I made cash developing a custom estimation package for Don's mechanical contracting company. My plan was to make and market "Vienna Estimator" to plumbers, electricians, and HVAC shops, then use those profits to fund my Gravity & Colony dreams. That was mistake #1, resulting in me spending three years writing plumbing software instead of riding the wave like the Netscapes of the world."
Grammar [dive into mark]: "Also, a snide note from a grammar nazi who took umbrage with the sentence 'There is a zen to it which I am not one with.'"
Grammar nazi's are sad. They, like, really miss the point of language altogether, all while professing they love language. Ay! Study linguistics, not grammar, dudes!
Note: The Anti-Worm Guys Don't Like "Financial Sustainability" in a Development Context: Archive Entry From Brad DeLong's Webjournal: "While sustainability is certainly a desirable goal, it may be difficult to achieve. Teaching people to fish rather than providing fish is great if it works, but this method works only if the donor knows more about fishing in the local area than the people who live there, and only if the donor can transfer this knowledge."
The Shifted Librarian: "My parents just got back from two weeks in Belgium and environs. When we talked on the phone tonight, the very first thing they both described was not the beauty of the land, how expensive things were (Euro against the dollar), or even the chocolate. No, the one thing they wanted to talk about first - and which obviously had a quite an impact on them - was the ubiquity of cell phones in that area."
I had a cut in my head sown a month ago, and it healed very nicely, but there's a little thread sticking out of my head. Aren't those supposed to just fall out?
Some thoughts on Drupal, an excellent open source community system. I've played with it for over 6 months now, and am using it on a live site. It's not perfect though (is anything ever perfect?)
1. Good code. Drupal, as opposed to, say, PHPNuke, contains good code. The developers continually attempt to keep the codebase clean and modular. The Drupal culture is a coders' culture.
A very nice advantage of this approach is that there are many modules available that extend Drupal's functionality. It is hard to figure out which module is up to date and being maintained, and it's hard to figure out exactly what a module does until you install it, but those are small problems that I'm sure the Drupal team will fix soon.
A disadvantage of Drupal's coders culture, is that features are sometimes coders toys instead of what users really need. For example, the "remember me" feature still doesn't work well, and was removed from the latest version. Big mistake for a community site! On the other hand, you can request features, and offer to pay for them (which is great).
Still, all in all, the approach works. The problems mentioned above are fixable.
2. Limited templating. The templating system of Drupal is built with the purpose of letting an admin user customize their site through their browser interface. By clicking some checkboxes, you can customize navigation, and add "blocks" to your site. However, this means less support for easy template coding.
Drupal uses 1 file for your template (as opposed to a separate file for each section of your site, like Moveabletype does). This means that, if your entire site has the same structure to it, you're fine. If you want different parts of your site to look differently, you end up coding a lot of PHP.
A second problem with the template file is that it is full of php code. There is no clean separation using tags, like most template engines use. The template file uses functions. This means that, to customize the template beyond small html changes, css changes and what you can do in the admin section, you will be coding PHP. Bad. In my opinion, this part of Drupal needs an overhaul.
There is a Smarty wrapper available, but until that becomes the standard (and until you can use multiple templates for different sections of your site), my complaint stands.
If you're a Drupal coder: I know you can do anything with Drupal. That's not what matters. It's about how easy it is to do things out of the box, and how easy things are to customize with limited understanding of PHP and Drupal's architecture.
Multiple languages.
It is possible to provide multiple languages for the templates of Drupal (the text that lets you sign up and such), but the "nodes" (the basic content container of Drupal) do not provide the ability to have multiple language versions of an article (for example).
There are some modules that try to address this problem, but until Drupal provides a standard, out of the box facility to have multiple language versions of an article (including translation facilities), Drupal only partially supports multiple languages out of the box.
Scaling of the UI.
Like many open source CMS's, Drupal needs to think about how it approaches growing websites. Out of the box, the system is optimized for medium size websites. There are too many options, too many pages, and many things take too many steps. Drupal should be optimized for small websites, and allow scaling the UI and functionality to medium and large scale websites. But start with small - that's how most of your users will start.
Overall, I think the Drupal team needs to focus on the basics. Drupal is at a level of maturity now where it is more important to improve basic usability and functionality (like the install process, which they are improving) than to come up with more new and exciting functionality.
If they improve their focus on improving basic functionality and usability, Drupal can become a real standard CMS. If they don't, it risks to become a feature bloated open source CMS as there are already dozens if not hundreds on the market.
IBM Usability: Role by phase matrix
AlterNet: Globalization vs. Americanization: "I grew up a patriotic South Vietnamese living in Vietnam during the war. I remember singing the national anthem, swearing my allegiance to the flag, and promising my soul and body to protect the land and its sacred rice fields and rivers. Wide-eyed child that I was, I believed every word.
But then the war ended and I, along with my family (and eventually a couple of million other Vietnamese), betrayed our agrarian ethos and land-bound sentiments by fleeing overseas to lead a very different life.
Almost three decades later, I make a living traveling between East Asia and the United States of America as an American journalist and writer. My relatives, once all concentrated in Saigon, are scattered across three continents, speaking three and four other languages, becoming citizens of several different countries. Once sedentary and communal and bound by a singular sense of geography, we are now bona fide cosmopolitans who, when we get online or meet in person, still marvel at the difference between our past and our highly mobile if intricately complex present."
Fast Company | Fresh Start 2002: Weird Ideas That Work: "Personally, I think failure stinks. But the fact is, every bit of evidence demonstrates that it is impossible to generate a few good ideas without generating a lot of bad ideas."
A clever way of categorizing! New Scientist: "A new system that can caption your digital photos by listening to you and your friends chat about them is being developed by Hewlett-Packard in California.
Digital photography is booming, and people are storing ever greater volumes of photos on the hard drives of their PCs. The trouble is that people rarely label their photos.
"This is the weak link for digital photo collections," says Margaret Fleck at HP's lab in Palo Alto. "In 10 years' time, finding something amongst them will be very difficult."
Fleck's answer is to tap into the wealth of information in the conversations we have when we talk about our photos with friends. She says the stories we tell do not merely describe the photo, but also talk about the events that happened before and after the picture was taken.
[...]
To harness this information, Fleck has developed software that records these conversations to hard disc, converts the speech to text using a speech-recognition program, and then extracts keywords with which the photos are captioned and indexed."
Sounds like a mistake though: the problem with our digital pictures is not finding them, it's sharing them and the stories around them. (This is a new interest of mine.) Recording those stories to then throw them away just to extract some keywords is a waste.
This is the kind of fresh thinking that puts a smile on my face.
Situated software - megnut.com: "This gets to something I've been thinking about for sometime now, the possibility of using personas to represent groups rather than individuals. In fact, I even proposed it as a talk for the last O'Reilly Emerging Technology Conference but it wasn't accepted.
I'm still tickled by this idea of modeling the groups, because as Clay writes, there's a power in groups that you don't find when the same individuals operate in isolation. By creating group personas (groupas? grouponas?), perhaps we could better design and hone our software to utilize the group's power."
InfoWorld: Toshiba, Sandisk develop 4Gb flash memory: "The new chip can store 4Gb (512KB) of data and the companies said they are also working on a second new chip that contains two of the 4Gb chips inside a single case for what is effectively an 8Gb (1GB) flash memory chip."
Is that "4Gb (512 KB)" just an editing mistake, or does it mean something?
WorldChanging: Another World Is Here: How to Build a Coral Reef: "This group has come up with a process for building new coral reefs. It involves wire-mesh frameworks, low-voltage currents creating mineral accretion, and the transplant of broken pieces of coral."
OK, instead of me posting every single story Worldchanging runs, why don't you add them to your newsreader. I don't really post every story, so if you like this stuff check them out.
BBC NEWS | Technology | Radio mail links Pacific islands: "A internet connection speed of 2Kbps may not sound like much, but it is providing a lifeline for the people of the Solomon Islands.
[...]
But for the past four years, the People's First Network has tried to mend fences by using high frequency radio to send and receive e-mail.
[...]
The two main ways of getting in touch with people are short-wave radios or satellite telephones. But radio offers no privacy, whereas satellite phones are too expensive for most to use regularly."
Not to speak of the other advantage of email over radio/phone: asynchronicity (sender and receiver don't need to be there at the same time).
"At the moment that are 14 e-mail stations in schools or clinics in rural areas. The stations are owned by the community, with decisions taken by a committee of village chiefs and religious leaders.
The stations are a pretty basic affair, consisting of an ageing laptop, radio and modem. The kit is powered by a car battery, which itself runs off a solar panel as in most areas there is no electricity. The total cost of the equipment runs to around $8,000."
You'd think that can be done cheaper. Then again, cheap supplies aren't as plentiful everywhere in the world as they are in the USA.
The project uses WaveMail: "WaveMail is optimized for use over relatively slow links like radio-links (Pactor / Packet radio), Inmarsat and telephone lines. In order to use the slow links in an efficient manner, all messages are compressed and a very efficient protocol is used for message transfer (compression and decompression is done automatically without user intervention)."
Next they'll try to provide internet access. See World's poor to get own search engine: "Researchers at the Massachusetts Institute of Technology (MIT) are developing a search engine designed for people with a slow net connection. Someone using the software would e-mail a query to a central server in Boston. The program would search the net, choose the most suitable webpages, compress them and e-mail the results a day later.
[...]
The thinking behind the TEK search engine is that people in poor countries are short of money but have time on their hands, whereas people in the West are cash-rich but time-poor."
Seems like solid thinking.
Percepnet: "Thus, while we would sense lights, sounds, tastes, smells and touches, we would perceive them as, say, a chocolate ice-cream or a glass of lightly chilled Burgundy.
[...]
The research that is being conducted in developmental neurobiology, neurophysiology and cognitive neuropsychology is suggesting that the processes involved in perception are so intermingled that there is little value in trying to divide them up neatly into sensation and perception."
Learn Dutch. Nice site.
(via Phil Bradley) Inside the Searcher's Mind: It's a Jungle in Here!: "There's No Such Thing as an Average Searcher." A study by a marketing agency, and therefore suspect, but still worth a read.
"For instance, women tended to scan all organic [he means non-sponsored] results and read titles and descriptions more carefully than men."
Mmm...
Other conclusions are about banner blindness ("It seems that people have already mentally divided the results page from their favorite engine into sections"), search behaviour ("A person searches, chooses a result, visits a site, and hopefully converts. In reality, we see the typical search pattern is quite different.").
Nothing you don't know and haven't seen analyzed better.
They do have an interesting section about what Jared Spool calls "the seducible moment". In short (and this is my interpretation of their results): don't pitch products during search, instead help users refine their search towards your product. Again, this is my interpretation - the article talks about the "Anonymity threshold". ("If given the choice between getting information and remaining anonymous and getting the information through registering, people will always choose the former.")
Nagging seems to work: Alex has started writing a Topic maps tutorial entitled "How to sort your CD collection with Topic Maps", following up on my post Why is it so hard to learn topicmaps.
NewsForge | Builder.com outsourcing content production to India: "Builder.com, CNET Networks' site aimed at application developers, plans to begin offshoring authoring of many of its articles to India shortly."
urlgreyhot : $10 to whomever figures out my anonymous user page not found problems.
So it's not just me.
Drupal is a great CMS product, and has a wonderful developer community, but something bothers me. The "remember me" login feature was broken in version 4.3, and now it's been removed from 4.4.
A question on the mailing list got me this answer:
"The reason "remember me" was removed is not because the remembering is broken per se, the problem is that it is not possible to choose the
behaviour anymore due to PHP overriding Drupal's cookie. Whether or not you are remembered depends on the session persistence and lifetime settings in php.ini / htaccess. Check PHP's documentation if you are not getting the behaviour you want."
Developer hogwash! A community CMS should not be released with such a central feature broken.
Escapable Logic: "You can get a lot done by filling out government forms, but it's a lot like writing code.
One of my projects involved 120 acres on the Denver-Boulder turnpike, but without access. All it took to increase the value of our land 20-fold was to get four layers of bureaucracy, including the Federal Highway commission, to authorize us to build the interchange by adding an assessment to our land and other interested parcels." (Via Doc Searls)
Wires - A girl, a toolkit, Iraq: "Tonight as I write this, a group of nervous wiremen are sitting at Heathrow airport, waiting to board the flight which will eventually lead them to Baghdad, to install the cameras in the studio there."
(Via Simon) Topix.net Weblog: The Secret Source of Google's Power. That's why I like this blogging thing. Thoughts like this were surely going through the (sub)conscious of thousands of people after the GoogleMail announcement. Then someone articulates it well, and we all get to read it. It gells. We all learn. Nice.
GoogleMail no Joke: "It's not like Internet search service Google can't laugh at itself, but when an April Fool's joke got out of hand on Thursday, a real business plan was rumored to be a Web hoax -- and that was no laughing matter."
"This is Mohammed Bah Abba's Pot-in-pot invention. In northern Nigeria, where Mohammed is from, over 90% of the villages have no electricity. His invention, which he won a Rolex Award for (and $100,000), is a refrigerator than runs without electricity.
Here's how it works. You take a smaller pot and put it inside a larger pot. Fill the space in between them with wet sand, and cover the top with a wet cloth. When the water evaporates, it pulls the heat out with it, making the inside cold. It's a natural, cheap, easy-to-make refrigerator.
So, instead of perishable foods rotting after only three days, they can last up to three weeks. Obviously, this has the potential to change their lives. And it already has -- there are more girls attending school, for example, as their families no longer need them to sell food in the market."
Alex writes a rebuttal to my article on Why is it so hard to learn topicmaps?
Alex: "We are hard-working people who write specialised and clever applications, and so we don't really have the time to write "how to sort your CD collection with Topic Maps.
[...]
So, in Peter we trust, and even though I've seen most of the responses (I added some myself) he still says there are no hackable applications that you could use for easily learning about Topic maps. How does he come to that conclusion? I surely don't agree, but it is hard to fight this one back as I don't have the readership he's got."
Um, Alex, you may be overestimating my readership there :) And hopefully this link will help the people who read my blog also find your post (and your excellent blog).
The point of the post, and I stand strongly behind that, is that we need better tutorials, for the reasons I outlined.
I am a big believer in topicmaps, but as it stands, it's almost impossible to learn topicmaps without a large amount of developer background. I believe it doesn't have to be so hard. I believe you don't need to know your data model from your reification in order to get going with topicmaps. A basic understanding of XML should be all that's required. And I believe that providing tutorials like the ones I was attempting to describe is the best way to get topicmaps understood and adopted.
There are clear advantages to using topicmaps technology (for example, you can change the relationships in your data without changing your data model) that we should be able to illustrate with a basic tutorial. Developers generally learn by coding - we should work with that.
A text adenture game based on RDF. Cool. (via RDFPlanet)
SWAD-Europe Weblog: FAQ: How do I parse RDF? A list of RDF parser libraries for most programming languages.
Why is it so hard to lean topicmaps?
Some ideas on why many people hit a wall when trying to learn topicmaps.
Topicmaps are a powerful standard for managing ontology-like metadata. It's kinda hard to get your head around topicmaps, but this is not because they are especially complex or hard to grasp (Not harder than object orientation, relational databases or XML for example). They're really not that bad. It's because of the lack of easy to understand real world applications that you could hack together in order to learn topicmaps data structures and concepts.
When you learn about databases, you'll start by programming a simple script to organize your CD's or something.
Manage your contacts, organize your income - there are thousands of beginners tutorials like this for almost any programming language available. After you've wrapped your head around the basic concepts (relations and ID's), you can then learn about more advanced ideas like normalization or joins.
If you had to read about the conceptual underpinnings of databases in order to get your head around them, they would never have taken off the way they did.
There are no hackable applications that I know of you can use to learn topicmaps. This means that there are no beginners tutorials that let you hack a useful application together based on topicmaps. All the tutorials I've seen teach you topicmap concepts and how to create a topicmap. They don't help you create an application to organize your CD's.
In a recent post to the topicmaps list, I asked to come up with something that was easily hackable, useful and would help people understand topicmaps. There were some ideas, but we couldn't come up with an acceptable example. (This is not to say that it can't be done. We should think about what exactly is missing here.)
So when you're interested in topicmaps, you read the specs or one of these tutorials, and unless you're familiar with data models and a bunch of advanced metadata concepts (reification anyone?), it's gonna blow your head. Many people give up right there.
The distance between the topicmap model and a real life application seems larger than the distance between the relational database model and a real life application.
Similarly:
Topicmap tools are at the topicmap level, not at the real-life usefulness level. In other words, topicmap tools let you manage, create, and merge topicmaps. But they don't let you do anything specifically useful outside of the topicmap realm (like create a simple application for managing your CD's, like Access lets you do).
The level of abstraction of topicmaps is higher (which provides great Power and Flexibility) than that of databases. But that means that, to get from a topicmap to a useful application, you need more stuff in between. RDF seems to be resolving this problem: the stuff in between are useful standards like FOAF. Topicmaps need standards like that, that let you do something useful with topicmaps, and thus make the tools useful and topicmaps understandable.
Shirky at his best describes patterns that seem to fly against common sense. Situated Software: "The curious thing to me about Teachers on the Run was that it worked where the Web School version failed. RateMyProfessors.com has been available for years, with a feature set that put the simplistic write/read/vote capabilities of Teachers on the Run to shame. Yet no one at ITP had ever bothered to use RateMyProfessors.com, though the weekend's orgy of rating and voting demonstrated untapped demand."
Jon Udell on Macromedia Flex: a developers environment for developing applications in Flash. Competing with XUL (open source) and XAML (microsoft).
So Apple is patenting a hierarchical menu on the iPod? United States Patent Application: 0040055446: In a portable multimedia device, a method, apparatus, and system for providing user supplied configuration data are described."
Someone seems to have messed up, the link to the American express Seinfeld/Superman ad shown on TV doesn't work: HTTP 404 Not Found. (It's fixed now)
An answer in reply to my recent XML question. More examples would be good, I'm trying to understand this...
Mena's Corner: "Nine days ago was the one year anniversary of our incorporation of Six Apart (prior to that we were a LLC). In this last year, we went from two people working out of our apartment to a company of twenty-four including a Japanese subsidiary (announcement) and a team in Europe working as our exclusive agent.
[...]
When we knew that Movable Type Pro had to be postponed because the direction of the product hadn't been clearly outlined in terms of development resources, we should have told our users."
Six Apart, eating their own dogfood, started blogging from within their own corporation.
Andrew points to A new kind of comments spam?.
Looking at this a bit more, it is clearly spam. Someone is creating a circle of fake "personal" websites using cookie cutter text (the 'about me' is the same for all the sites), various free hosts and varying images. Warning: the sites pop up ads of the most annoying kind.
It really wouldn't take a hacker much work to create thousands of fake "personal" websites that are a lot better and varied than this one, and then comment spam the hell out of the weblog world to build pagerank. I don't want to give anyone ideas but I'm pretty sure this is inevitable.
XML, trees and laticces.
I've been wondering about XML and highlighting text. If I have some text, and I highlight a piece and tag it with some subject, I can easily express that in XML.
But what if then I highlight another, partly overlapping part of the sentence and want to tag that with another tag? How am I supposed to identify that with XML? I don't want to do what HTML does with overlapping Italics Bold tags, because I want to remember what I highlighted as 1 section, not cut it up in different sections that are tagged the same way. (Is this making sense).
So what is the solution to this? Is there any? I think the fundamental problem is that, at a data modeling level, XML lets you build trees very easily, but not laticces (overlapping structures).
Help.
Annotated Aggregator client HTTP tests: UI standards to complement Aggregator HTTP standards.