Categories
RDF Semantics Weblogging

Common interchange format

Recovered from the Wayback Machine.

After sleeping too late this morning and then waking with a headache–a response to long hours this weekend, culminating with finding out late yesterday the work was for naught and has to be re-done–I didn’t have enough time or energy to go for a hike somewhere, so I started playing around with technology.

I know this doesn’t make sense: why would a person spend all weekend with code and then spend time coding during off-hours? It’s really a variation of setting your alarm for Saturday morning just so you can turn it off when you don’t have to get up on your day off.

What? You don’t do this?

Anyway, I’ve been playing around in the WordPress code because my outgoing trackbacks and pingbacks have stopped working. I’ve also been playing around with some new PHP toys that I’ll cover in an upcoming new LAMP essay. However, most of the day has been spent thinking about interoperability.

The biggest challenge to industries in the past has been to establish a data model for the industry that all the participants could agree on. Once agreed on, then the groups could generate a data format that allows companies to electronically transmit data back and forth without having to go through a lot of transforms.

Some people think XML has eliminated the data transform problem, but XML is nothing more than a structured syntax – there is no ‘data’ within the XML model. It’s the same as having an alphabet, but no common agreed on language. I can scribble letters and you can scribble letters but if we don’t agree on what those letters mean, all we’re doing is creating pretty pictures.

Even RDF isn’t data. It’s a step up from XML in that it provides a structure for how objects relate to each other, but you still have to define the ‘objects’.

Anyway, I was thinking of data interoperability today because of the recent closing of weblogs.com, not to mention other recent movements between Movable Type and WordPress, Movable Type and Textpattern, and so on. I was reminded that one of the original purposes behind the Atom project was to define a common interchange format between tools, so that people could easily move from one to another. With this, people wouldn’t be facing some of the difficulties the weblogs.com folks are now facing, trying to get their Manila based exports into a format usable by other weblogging tools – something I’ve heard is not trivial.

However, the Atom folks went the syndication and API route and put an interchange format on the back burner. Too bad, really, because something like that would be rather handy now.

As coincidence would have it, one of the architects of Atom, Sam Ruby, volunteered to help write a data transform for those who are currently impacted by the weblogs.com shut-down. He wrote:

However, this is not a time for religious debate or partisanship. It is a time for compassion and an opportunity to learn and improve. Enough so that I am willing to step forward and offer to help with writing of conversion and migration tools. Assuming that the input looks anything like this format, I am willing to write conversion tools to either a comparable format or to a blosxom’s directory layout.

As Sam mentions, escape sequences and odd characters will now take on special interest, because these usually cause problems when either exporting or importing data. As he also mentions, getting one’s own domain is also a good think to think about now, too.

It’s great that individuals are stepping up to help out during this ‘crises’, but the better environment in the long run is to agree to a common interchange format and have all tools support it. Then people could export their weblogs weekly, or even daily if they’re paranoid enough (and no one could blame people for being paranoid now); if something like this were to happen again, the impact would be minor at best.

We have to stop putting those who aren’t technical into the position of being dependent on the technically proficient to come riding in to save the day every time a new ‘business decision’ is made. I like riding white horses as much as the next person, but it’s hard to walk about when people are kissing the tops of your boots.

However, technology is easy, business agreements are hard–in this environment, business agreements are damn near impossible. So until utopia hits, I also volunteer my help for those displaced from weblogs.com who want to move to WordPress or Textpattern. You’ll have to find your own server space, but I can help you get the tool installed and get your data ported to this environment.

Categories
RDF

A little light if you please

I think, I think, I think too much. I miss my hour, taken in last nights Daylight Savings Time raid. Time for a bit of lightness before I get serious again:

Ben Hammersley has decided to follow that old and obsolute BLX 1.0 standard rather than the shiny new BLX 2.0. As for his claim to have created an RDF version of BLX, that’s just impossible – it doesn’t support namespaces.

But then, what can we expect from a man daft enough to run across the Sahara Desert on foot?

(BTW – good luck Ben. Even we BLX 2.0 adherents are rooting for you.

Categories
RDF

Door opens and a single candle appears

Who says you can’t have fun with RDF? Not the creators of this online game that’s who.

The witches look at your naked body and titter. Then they see your bar of soap and take it away, muttering about scented baths and candles

(Thanks to Peter Van Dijick)

Categories
RDF Technology Weblogging

RSS Stuff

Recovered from the Wayback Machine.

Time to take a break from photos and philosophy, and feed the machine.

I have a file that maintains a list of 404 accesses, and the URL where the missing resource access originated. The file most accessed is the old Alter Ego weblog’s rss.xml feed. Since I closed the weblog over a year ago, not quite sure where these requests are originating, so I re-created the file with one entry that reads:

Title: This Weblog is dead, dead, dead

Description: This weblog, Burningbird’s Alter Ego, has been dead for over a year. Why are you still accessing this feed? If you can’t even tell which weblogs are active or not from the feed, perhaps you’re subscribed to too many sources. Try reading a few from time to time.

The point I think is good – some people proudly point to the multi-thousand aggregatiojn subscription count they maintain and my only response to that is, please remove me from your list.

Another old syndication feed chestnut is making its rounds again recently. Seems Joi Ito is providing a CSS stylesheet with his RSS feed. Deja vu all over again. I agree with several others who have pinged Joi in that it makes little sense to supply a stylesheet with a syndication feed. Not only does this override a person’s aggregator settings, it also makes the feed processing more complicated. Plus, I don’t see the point. The purpose of syndication is to provide a recent list of updates, with enough information so that if a person is interested, they’ll click through and read the rest of the writing at your web site.

Sigh. Over and over and over again.

However, there was an interesting point made on this by Liz that made me want to comment, again, on this concept. She wrote:

My gut response to this is discomfort with the idea of trying to use CSS with syndicated content-that it seems somehow contrary to the entire idea of syndicating simple content. But I know from long experience not to trust that kind of initial negativity too much, since it’s often connected with changes that turn out to be quite positive.

Curious – I wonder if Liz also questions her initial positive reactions to new technology with the same hesitancy that she applies to negation reactions? If not, is this because negative or should I say, critical writing is somehow valued less than positive writing?

I know that Joi Ito maintains a very positive outlook when it comes to geekery and tech, but then as a tech VC he has to: people don’t invest based on pessimism, or even realism. (Not to say that Joi wouldn’t be positive anyway – I really do think he loves this stuff.)

My job the last few years before the Great Bust was as a consultant finding the problems with existing or proposed architectures and software designs and decisions before the company spent millions of dollars on, frankly, overoptimistic but doomed technical innovations. In some cases I would then work with the folks to architect new solutions (or in case of a couple of contracting companies, find new companies). It was a job I was very good at, and I know that I saved one past customer several million dollars, and also helped a couple of others create systems that were simpler and much easier to scale. Seems to me the ‘criticism’ in these cases is a positive thing.

(Betcha you didn’t know that, did you? Betcha you just thought I was a negative person, didntcha? Yah sure, back in the good old days I used to charge a buncha money to do what you all get for free.)

Anyway, though I may eventually get around to an Atom feed, when I have the spare cycles, and I have a hidden comments feed (which you can find if you’re determined), I’m not going to fool around with stylesheets for my feeds.

Besides, I like Bloglines. I like the way the system looks, and I like the clean, easy to read aggregated excerpts. But I always click through when my small, select group of subscribed feeds update.

(Except if you provide full content and don’t take comments and host on Blogspot, like Halley).

Categories
Semantics Specs

RDF Specifications Recommended

Recovered from the Wayback Machine.

W3C is pleased to announce the advancement of the Resource Description Framework (RDF) to Proposed Recommendation.

Relieved more like it as these long awaited specifications finally reach the “proposed recommended” state, one short step before becoming formal recommendations.

These documents (RDF/XML Syntax Specification, RDF Vocabulary Description Language 1.0RDF SemanticsRDF PrimerRDF Test Cases, and RDF: Concepts and Abstract Syntax) represent a great deal of time and effort on the part of the RDF working group members, who are to be congratulated in finishing this important milestone.

In addition to the RDF documents, the OWL Web Ontology Language also made proposed recommendation status. Someone at the W3C must have said: let’s get this show on the road, children.

Semantic Web, or should I say, semantic web, here we come.

(Thanks to Dave Beckett and Danny Ayers for heads up.)