Personal Software Integration


Wahoo! Major breakthrough!

I’ve been able find a way to get my Radio weblog uploaded to my Linux box, despite the headaches with trying to get the filesystem upstream driver to work. Now I know that I’m not the only one. Bah!

I’m realllly frustrated with Radio right now. But I can’t just abandon it yet. My annual license billing is probably about to come due, and that’s a pity, but I’ll keep up with it at least another year.

Radio’s underpinnings are bittersweet. Radio is a great example of how a well-designed system (i.e., Frontier) can evolve to meet ongoing needs. And there’s power in it too. The News aggregator, the web services, the upstreaming. Cool stuff. But there’s a big cost.

What Radio offers in power and robustness it takes away in usability and learning curve. I’m upset that I need to know so much about the internals of the product (UserTalk script, Radio’s complex database layout) to customize it the way I would like (Yeah, I really bet they were thinking of me in particular when the built it).

And it takes a good deal of digging to find out how to do quite a few not-so-unreasonable things. It was weeks before I figured out that pages that talked about “installing a tool file” were not referring to the web interface. I mean–come on–how hard would it be to PLACE A SHORTCUT TO THE Radio GUI IN THE STINKING PROGRAM MENU. I stumbled across it by accident when I was exploring the right-click menu on the taskbar icon. Later, I found that I was not the only one. That’s lame.

So far, I’ve only been able to get my Radio weblog files to my Linux box by copying the “rendering” folder’s contents to my Linux Samba share.

At the same time, it’s not totally fair to bash it. I think Radio has the “cool, I can publish a post in 5 minutes out of the box” bit down pretty well. But then users start to want more.

Try uploading pictures. It’s clunky. Who are they helping by having a dedicated folder that you copy pictures into and they magically get spirited off to (maybe) the right location? Oh, and forget trying to control filename and location of the picture in the actual web content.

Or the whole local vs. cloud links when rendering. Aargh! Ya know, I actually *do* have an ongoing, comprehensive list somewhere about my pet peeves with Radio. I think I will honor the irony (both the fact that I’m using Radio to post my peeves about it, *and* the fact THAT I STILL CONTINUE TO USE IT!) by posting a story on the topic.

The thing that really gets me though, is how many others like Michael Boyink and Dale Lature at Theoblogical (I’ll post more names and links later) have grown weary of the Radio hassles and abandoned it altogether for Movable Type or a custom solution. Maybe I have more of a tolerance for mental pain (and that’s not bragging, it’s actually sad).

I have to say, I’m personally leaning toward Keith Devens‘ approach of creating his own CMS complete with bells and whistles. The problem right now is that with trying to have a life and cope with my ADD and all that stuff at once, I’m having trouble keeping up with a blog that requires little to no programming (at least just for posting alone).

Ultimately, my work on objects and metadata is beginning to merge with my work on Content Mangagement topics. I believe that I will follow the example that Radio has so aptly demonstrated (hey, it’s a great pioneer of the conceptual)–run a local web server type app that offers a local interface and allows things to be rendered and pushed (I can’t say “upstreamed” right?) wherever you like.

Right now it looks like my efforts will be a mix of ASP.NET website widgets and local publishing applications (rich and thin client).

Nuf said. The cool thing is that xagronaut.com actually has content now. Sweet.

Update: I’m still on the trail about the fileSystem upstream driver problem. It looks like Roland might have found something.

Lately I’ve been thinking about all of the data pieces that I would like to track if I had a good system. But then, my data is scattered throughout a bunch of segregated systems and stored in diverse formats.

What if I had one central system to pool all of that data and manipulate it? I think an object-based data environment that allows me to add metadata to objects would be ideal. Now the persistence question is there–how will this be stored on disk? But I’m still working on that.

My thought right now is that I can mirror objects in other systems (e.g., my Outlook contacts) while still attaching other metadata not supported by systems (or at least not easily).

The metadata and object structure would have to be very extensible, with a core flexible object model. XML provides a good framework for this, but I’m looking for something a little more virtual–expressible in XML of course, but not tied to it.

The topic of the Semantic Web entered my thoughts during this time. The easiest way to create the Semantic Web (especially with today’s hodge-podge Web) is not to require your average web page producer to learn special markup. Someone else can have that job!

No! The way to create the Semantic Web is to create vertical semantic applications that draws a stable community of users to a common schema by virtue of using the same client software. At say, 10, 100, 500, or 15000 users, you have a meaningful data schema for that application space.

Capitalism is great; competition is great. But the Semantic Web pines for standardization in the midst of choice. So a standard for trust in schema mappings must be devised. Trusted mappers sign their trusted maps and other parties (robots or real) trust the schema mappings in their own applications.

This allows applications and robots to “intuit” equivalence between schemas based on a system of trust. Tomorrow, anyone can create a brand new schema. And within their circle of trust, the semantics can be honored. Establish credibility with a major schema authority, and virtually everyone can trust your schema.

So here’s the sequence:

Vertical application leads to
A community of users that agree to
A common data schema (probably XML) which becomes
A trusted schema by a schema mapping authority who publishes
A public schema mapping which is
Trusted by the “mapping downstream”

So an exchange might go like this:
Client: Hey, Semantic Web source! Do you have any data that adheres to the Simpson Geneology schema?
SW: Well, not exactly, but I do see that one of my trusted schema mapping authorities believes that the National Science Foundation’s Geneology Lexicon contains some mappable elements in this location. Would you like to try there?
Client: Why yes, that would be fine. Oh, and since you trust the National Science Foundation’s Geneology Lexicon as mappable to the Simpson Geneology schema, I will add that to my list of trusted mappings because I trust you. And in the future, I will also include the NSFGL in my list of acceptable result formats for my next request. Thanks again.

Granted, this “conversation” is protocol talk over the wire and sever and cyberspace.

And another thing. In the world of schema trust, we won’t have a mega market giant like Verisign as the main schema mapping trust authority. Well, maybe we will, just de facto, but this will be very grass roots. I myself could choose to be a schema trust authority. Anyone who trusts me and authenticates my schemas (using PKI of course) can choose to also trust the mappings that I produce/author and/or trust.

So, my vision of the Semantic Web is not one gigantic standardized pool of data that follows good markup because everyone is speaking exactly the official vertical dialect for an application space. Rather, new application spaces pop up all the time. A software developer chooses to play nice by adhering to some standards that make the data created by the application usable by the Semantic Web. Vertical application communities evolve. Circles of trust form. Somebody releases an “open source” schema equivalence mapping. Everyone else trusts the mapping. The Semantic Web bots just skip along from stone to stone across to the other side of the river and back.

OK, I’m definitely tired right now, and I know I’m rambling, but you’ll have to forgive me. At least I’m posting again, right?

I have given some thought on how to prevent SW spam. Think about it. If all it takes is a special set of tags for a certain knowledge space, anyone can plug them in. You remember the META keyword tags right? So, now smutmongers can specifically target you when you’re looking for rare bird species.

So the whole “Google magic” might be needed in the SW space as well. Well, Tim (Berners-Lee), that’s my two cents for today.

NPR Content Via RSS Enclosures and Audible.

NPR and Audible Team Up To Provide Customized Audio To You Through Their New Weblog-enabled Affliate Service

[The Shifted Librarian]

My Thoughts:

The two items above ring true with hopes of mine in recent times.  But I must say, in the past two weeks, I started listening by chance, and I haven’t been able to change the station.

Yes, NPR has earned a preset on my radio, albeit the last FM preset I had open.  I find the news content, music coverage, and cultural insight incredibly stimulating.  I can definitely see the value in having that content available at will.  Cool!

The above two items also fit nicely into a growing trend in my own life and in the culture of aggregating a myriad of heterogenous content into one place for synthesis and presentation in the format.  It follows my definition of nerdvana: “If nirvana is the state of achieving ultimate knowledge (or something like that), then nerdvana is the state of organizing all of that knowledge in a seemless, integrated way on all of your electronic devices.”

I have just upgraded to , and installed Brad Choate’s . This is a test

of the Textile formatting.

  • I love bulleted lists. I hate entering HTML by hand.
  • WYSIWYG would be even better, but Textile is better than raw HTML.
  • I wonder if tools like could support it.

[]

Textile sounds more and more compelling.  Maybe later…Must work now.

Yes. Mostly.  Here’s the scoop from the Movable Type FAQ.

MT version 2.0 and higher is free for personal or non-profit use. We’re following a donate-ware model in which we ask that you send us a paypal payment for the amount which you feel the product is worth to you. In return, for every $20 that you donate, you will receive a Recently Updated Key. For donations of $45 or more, you are entitled to additional support. See here for more details.

Here are two good finds about Movable Type:

Radio vs. Movable Type
http://blogs.salon.com/0001111/2002/08/14.html#a194

Making the Move to Movable Type
http://www.meryl.net/articles/archives/000947.php

OK, I’m in heaven! I just discovered that has the ability to serve up feeds on any project in their system. Project-level RSS feeds seem to center around news releases for the project, and you can choose among a few formats (like with or without full news release text). In fact, they have a on all the RSS feeds available and explanations/FAQs.

I was also impressed with the way their documents were laid out, being able to jump into any section of the document, like the or a specific topic like “” I think this is a great idea, and I will try to include this feature in any content management system .

The Curse of Outlook.

In reference to Ximian Evolution, The FuzzyBlog! wonders, “Why is it that things that try and look and act like Outlook end up being the same type of slothful, buggy pigs like Outlook itself?”

He wonders if Chandler will also have the same fate, even “Is this just the natural end point for products that try and emulate Microsoft Apps?”

I wonder, is it worth the risk and time to create an application that behaves much differently?  There are an awful lot of users out there that would find and Outlook-ish style application approachable.

I think that in the end, competition in the software space both hurts and helps innovation.  It helps because competitors must both keep pace with each other *AND* find a new feature that beats the other guy.  But, it can also hurt because no feature can be counted on to be totally compatible or integratable (easily) with other systems.  Proprietary systems often lack just enough ease of integration to either require their consulting services or ensure entrenchment once the infiltration has been made into the IT infrastructure.

Still, it seems that complete refactorings come along every several years that summarize, in one place, all or a representation of all, of the advancements that had been made in the preceeding technological generation.

It’s the pain of the early adopters all over again.  The late adopters may not gain competitive advantage, but they are more likely to have offerings available that are easier to integrate, either by design of the software system or by the sheer availability of service organizations (VARs, consultants) competing in that space.

I’m aggravated! Microsoft’s updated support page/Knowledge Base article
format will not save in Web Archive format. This is a recent change, and
I have responded at lease once using their feedback form. I have heard
nothing.

I suspect it is related to the cross-domain stylesheet reference, but I
can’t be sure without researching it (Update: I don’t think that’s the
problem now–all stylesheets have relative paths). But I’m miffed! I
save MSDN/KB articles as archives all the time. MSDN still works, but now
the new layout at support.microsoft.com prevents saving in any format
except “HTML only”, or (*gasp*) plain text. Believe me the “HTML only”
format looks pretty crappy upon reloading.

Dismay

Maybe the world at large has not discovered the joys of the MHT format.
Or maybe they have no concern when they are thwarted. Maybe the
workaround is sufficient for them. My most recent Google search seems to
consistently point to the same (mostly worthless) Microsoft KB article
(#235589).

Are my interests that obscure? Somehow, I doubt it.

Hope?

A few point to an that affects sites in the Restricted Sites group. I
doubt that Microsoft.com is in the Restricted sites group by default. I
did however, find some possibly-related security settings in the IE
options that affect frame navigation, scripting, etc. Interesting…

Background

I use the Web Archive format (*.MHT) extensively with Internet Explorer to
save a snapshot of a web page with all parts in a single file. All of the
images, stylesheets, and scripts are embedded as message parts in a
multipart MIME message. The format is actually not proprietary–it
complies with . The page is reconstructed by Internet Explorer as it
existed when it was saved.

In many cases, this is better than link rot. I don’t have to print out
the web page unnecessarily, and I can guarantee that the contents of the
page will not change the next time I “visit.” Granted, the file size is a
bit chunky, and you don’t benefit from things like image caching since
every web archive file has every element embedded. But hey, gigs are
cheap, right?

An older alternative format with Internet Explorer was the “Web Page
Complete” format. It saves a .htm page file and creates a child folder
with the same name as the page file. All supporting objects (images,
etc.) are saved as distinct files in the child folder. Some people like
that for scavenging web page parts. I personally hate it because it
becomes a file management nightmare. Every time I want to move the web
page, I have to also deal with an accompanying folder. Most of the time,
Windows Explorer groups folders separately from files, so the two items
are seldom close together in a file list. Forget it!

So I use MHT files a lot. Occasionally, however, Internet Explorer gives
an error message and refuses to save a web page as a Web Archive. This
can happen for a number reasons, very few of which I understand. But in
general, there seems to be a problem on some pages with Flash items. That
happens to be a lot of pages–ouch! Microsoft acknowledges the error and
lists a long line of browser products that exhibit the error–pretty much
all of the versions of Internet Explorer since the Web Archive format was
introduced. A recent search of Google groups also suggested that there
were some security considerations involving spreadsheets from a domain
other than where the page was located.

Microsoft addresses a couple of reasons (sorry, you
can’t save that article as a Web Archive!). Excel 2000 HTML spreadsheets
with multiple worksheets (which Excel creates by default–Sheet1, Sheet2,
& Sheet3) don’t save.

The article above provides this help: “To work around this problem, save
the Web page in Internet Explorer using a different Save as format.” Um,
what if my problem is that I CAN’T SAVE IN THE WEB ARCHIVE FORMAT??

Possible issues to consider

1.) The site with the desired page might know how to block this type of
operation.
Don’t know how yet, but I haven’t ruled it out. MSN.com
is one site Microsoft mentions specifically, and I haven’t found any good
reason why. Heck, the fact that they document MSN.com in particular in a
support article seems to be evidence that they intend that phenomenon to
persist. Sure, I imagine that the MSN.com folks and the support article
folks probably can’t get together and address this specific problem, so
it’s easier to write about it than to make a change.

2.) The page might not be reproduceable without DHTML or the
appropriate cookie or some other element that only exists in the rendered
version you are viewing.
It appears that IE trys to reacquire the page
in a separate “duplicate” request, rather than just saving the page you
are viewing. Wouldn’t that be convenient? Well, maybe not–the MSHTML
component in Windows does some HTML correction to reconcile poorly formed
HTML. It standardizes case and inserts closing tags. In other words, you
wouldn’t be saving the true source of the page; you would be saving IE’s
processed view of the source. Depending on your needs, this may not be
desirable. If you’re interested in what the processed version of the page
looks like, save a page as “Web Page, complete”, and look at the
difference in capitalization between the saved .htm file and the source
displayed by clicking View Source in IE.

Alternatives

A.) Create the file yourself: painful, but I’m beginning to think about
it. The format is documented well enough, that one should be able to
assemble an IE-compatible MHT file without IE’s help in saving it. It
requires arcane MIME knowledge though–message headers, sifting through
dense RFCs–not for the faint-of-heart or crunched-for-time.
B.) Find products that will save MHT files and don’t rely on the Internet
Explorer API to do it. Don’t know of any yet.
C.) Test the Chilkat MHT library and hope it doesn’t require the IE API
either. The Chilkat library is a bit pricey for the individual, but you
can buy a license for their entire suite that covers redistribution. The
price isn’t too bad (you’ll have to check their site) if you’re writing
and selling software that can defray the cost.

Related links

Gordon Weakliem had some problems that included the culprit message, but I
doubt that
will help me.

Data islands are seldom tropical.

I tried saving a web archive version (*.MHT) of a Microsoft support/KB site. It did not work before, probably because they reworked their site design. I was not able to pin down what changed to fix it, but about the site being “broken” does not seem to still apply. However, when I saved the web page and viewed it from disk, some of the styles were not preserved. The fonts that are normally small (or should I say “x-small”) were obnoxiously “normal” size.

Here’s I left on my earlier post.

Well, as of 12/1, I can save Microsoft KB/support articles in MHT format again. I don’t know what changed or when, but the problem seems to have been fixed. I submitted feedback via their content links, but received no reply. I can only suppose that they either “got around to it” or that enough people complained.

« Previous PageNext Page »