Categories
Technology Weblogging

Tech stuff

Recovered from the Wayback Machine.

Back is still quite painful, and has now been joined by cable modem. A case of new technology on old wires — for the modem, that is, not the back. Until the repair person comes out a week from tomorrow, my online access is going to be sporadic.

Sam Ruby has provided a very abbreviated introduction to RSS. I appreciate Sam’s effort, though I think it’s important to note that the RSS 0.9x and the RSS 1.0 efforts are following two separate and not necessarily parallel paths. Small correction — I believe the original expansion for RSS was “Rich Site Summary”. (Thanks to Mark for link.)

There’s a new effort for defining weblogging data with the BlogMD initiative. I’m not sure whether the group would be interested in the RDF vocabulary I designed for ThreadNeedle. From current discussion in the associated forum, probably not.

Speaking of which: the active effort of embedding RDF (data) for ThreadNeedle in each weblog posting is out — doesn’t work with existing weblogging tools. I’m now working on a webbot and scanning for links and building discussions from same, which will then be stored in a respository. From this I will then generate RDF documents of a discussion.

Frankly, after the rather unenthusiastic response I’m seeing with TrackBack, I’m not sure weblogging really needs or wants some of the technology the techies keep wanting to provide.

Categories
Technology

A few points of clarification on RSS

Recovered from the Wayback Machine.

Dave has a long multi-part posting today about RSS as well as article that covers RSS and aggregators, which he blasts but won’t link to or provide a means for us to discover said article.

He writes:

A note to people writing articles about RSS-based news aggregators. UserLand wrote and deployed the first one, in the spring of 1999. It was called My.UserLand.Com and was quite popular.

The concept of news aggregators, as well as RSS, had roots that extended back beyond Dave and My.Userland.Com. The concept of using XML to provide news feeds had implementations as channels with both Netscape and Microsoft (and other specialized companies that didn’t survive the dot-com implosion).

Don’t believe me? Then read an article I wrote and managed to salvage through the Wayback Machine from the now defunct Netscape Enterprise Developer magazine, January, 1998. In it, I showed how XML provided for IE channels, known as CDF could actually be picked up and used in other “aggregators” — except they were called “applications”. Jon Udell also writes about this, and references the use of RDF for describing channels in this Webbuilder article.

To provide more background material, Dan Brickley did a very nice overview of the history of RSS at the Yahoo-based RSS Development discussion group.

So, technically, Dave not invent the concept of using XML for aggregation. Nor did he write the first implementation of a “news aggregator”. And the examples I just cited are what is known in legal circles as apriori art, which means that Dave should use caution when he throws around “patent” with the implication that he’s the inventor of RSS or aggregation.

What Dave did do was help provide an implementation that gained popularity for the idea, especially when Netscape dropped out of the picture. For this, the RSS folks do owe Dave a debt of gratitude. However, at this point in time, it’s time for the concepts to slip out of one person’s hands and into the public domain where it belongs.

The RSS 0.9x family of RSS has been and will always be under the dominion of Userland. Debt of gratitude or not, I would rather put my money on a specification that isn’t owned by any one person or any one company.

The RSS 1.0 specification has two advantages. First, it’s based on RDF, which means much of the existing work and APIs and technologies that can be used with other RDF applications can be used with RSS. Secondly, it’s an effort that’s based on a team effort, with no one person ‘owning’ the effort at any one time. In fact, the RSS development team just voted to allow several new members on the team due to their outstanding contributions to the specification.

Dave asked us last week about what the RSS in RSS 1.0 means. He then printed up a page of our efforts, and then…nothing. Why did he do this? The only reason I can see — the only one — was to look for something with which to discredit the RSS 1.0 effort. And since those few of us who took the bait didn’t give him a weapon he could use against us, he somehow latched on to an email sent to him from an RSS user with little markup experience who believes that somehow RSS 0.9x is simpler than RSS 1.0.

News for those who think RSS 1.0 is too ‘complicated’ to work with: The RSS functionality I built into this weblog page uses straight XML processing to parse the RSS 1.0 page, and incorporate the contents. It was built using PHP, and took me about, oh, 20 minutes to write.

Piece of cake.

I’m not going to repeat my reasons for supporting an RDF base with RSS 1.0. I am going to ask my own question, instead:

Dave, don’t you think it’s about time you stopped fostering the split between the two specifications and work with a team of folks — a team — in making sure that the RSS 1.0 specification maintains its simplicity, even with the use of RDF?

In addition, Dave, you might as well know right now that I wrote about aggregators in my RDF book and didn’t include Radio. Why? Radio’s only one application, it’s not the first, and aggregation is only one part of its functionality.

Regardless, don’t you think it’s a bit bald to write the statement “Sloppy habits that come from working in a corrupt industry” when referencing both a publication and a reporter who can’t then defend themselves because you won’t even privide a link or a name?

Second Update: I received an email from a friend that perhaps Dave didn’t link to the article because he was trying not to be directly confrontational, and was trying to be nice.

Any professional author and publication can take the heat — I know I have for my articles more than once. Dave withholding the link for these reasons just doesn’t wash, though I will acknowledge that his intentions could have been ‘good’.

However, by criticizing the article, saying it was ‘wrong’ for not including Radio, and then not providing a link to this article, Dave’s preventing us from reading it and judging for ourselves. Now all we’re left with is rumor and inuendo.

Update: In the comments associated with this posting, b!x pointed out a thread on RSS and the ethics of republication at Blogroots.com.

In my January 1998 article, mentioned above, I covered the problems associated with providing a data feed using XML on the web and how the material could be republished in ways not intended.

There’s also more of a story with this article — I proved this concept and associated problem out with Wired’s CDF file at the time, republishing their data at my web site as an example of the problems associated with published XML feeds. Wired discovered this — and the awful page I plastered their data into, leading them to start protecting their XML feed at that point.

Now, almost five years later, we’re starting to question the ethics of republishing RSS feeds.

My darling webloggers, what did you think people were doing with all that data — printing it out on pretty paper and using it to paper the baby’s room?

Categories
Diversity RDF Technology

Outside even among the outsiders

Recovered from the Wayback Machine.

Warning: Big time rant. Male/Female thing. Read at own risk.

Being a woman trying to find a place among the techie guys isn’t easy, particularly since the areas of technology of interest to me rarely have other women participants. Don’t have to believe me, take a look at the RSS-Dev group, the RDF interest groups, most of the W3C working groups and so on.

Sometimes the group participation has been good. I’m rather partial to the RDF working group because in the newsgroups, they always worked with me. However, in a lot of groups, particularly the RSS-Dev group, I am for the most part ignored. That’s not a lot of fun. It seems no matter what I do, I don’t have the respect of a lot of the players. Not all players — there’s good people here abouts that never ‘held’ me being a woman against me.

(Me not laying down a 100+ lines of code a day they might hold against me, but not being a woman. And I can live with this.)

The seemingly winless battle for respect over the last few years probably accounts for over 50% of my recent burnout. I’m not sure if any of you understand what its like not being sure if the reason you’re ignored in most of these groups is because you’re a woman, or an idiot. I guess I would prefer to think it was because I’m a woman. I seem to do okay on my jobs, and I’ve had some pretty tough technical jobs. But you just don’t know, and it eats at you. All the time. Takes your confidence and just tears it apart.

After I returned from my last trip, I felt renewed and ready to take on challenges again, especially after coming back to be met with the generosity of so many of you, helping me keep this weblog and my sites going. I started my work again with RDF, which I really do love. In particular, I started participating on Internet-related groups again — something I’m more than a bit wary of.

When things got bad at one email group I took the moderator up on his request to start another group, and started Bloggers Unlimited, and it grew. It’s now at 7698 members.

The conversations started out pretty good. There was a quiet time in the middle, but for most part, consistent discussion. It’s a bit too techy for the audience at times, but manageable.

However, I began to notice a distinctive behavior pattern with this group. There was a very strong dominant male presence, which I know left me feeling pushed out of most of the conversations. When the group fell silent for a few days, and then started up again, another member, a male member, was given credit for rejuvenating the group; and here is me, taking quiet pride in thinking I was the one that had sparked it back to life.

What was worse is that most of the comments I made were ignored. I began to feel invisible. The same old feeling of inadequacy. We had some crankiness among the male members a bit early on, but it smoothed out, and the group went back on track. Again, I hoped I helped on this and I suppose this is a nurturing female type of thing, but I didn’t want to be the nurturing female in this one act play.

I started questioning myelf: Is it just me? Am I asking dumb questions?

I decided to get another party’s opinion, and asked Liz today if she noticed this. Was I being paranoid? Did I have a valid concern? She responded with this posting after first giving me heads up and asking if I wanted to respond instead. I declined. Liz wrote:

 

Here’s how the story goes, so far as I can see:

a) Shelley posts an interesting query about the semantic web
b) A discussion begins, with posts from a number of people with interesting ideas
c) Shelley responds with questions and ideas, at the same time that predictable people begin posting predictable rants about predictable topics (RSS, for example. OPML. what constitutes an ad hominem attack. yada, yada, yada.)
d) Shelley’s points are essentially ignored in favor of the same-old-same-old peacocking and posturing among the boys.
e) Shelley gets mad.
f) Shelley gets noticed only because she got mad.
g) People like me unsubscribe because the signal-to-noise ratio is getting worse by the second, and they’d rather read blogs than wade through cross-posts and arguments.

 

I was somewhat relieved to feel vindicated in my read of the group responses, because Liz is not one to call out sexism, either lightly or easily.

On the other hand, though, I was more than a little discouraged to see her comment about me getting mad, because I’ve taken such care on the list not to be mad, to stay calm, even when baited. And I have been baited. Not just in the list but in emails.

Why won’t I take such and such down? Why won’t I hold such and such to task? Well, if I want to be walked on, that’s my problem.

When Liz talked in her posting about rather reading Jeneane and Halley’s comments, I know that she’s making a point about being among people that appreciate each other. And I understand this. However, the impact on me is that I feel left out among both the men and the women. That I have no place with either group.

So where does this leave me?

Most likely bowing out on the groups, though I’m continuing my RDF work here in my weblog, with just my readers who are interested. I most likely will not get involved in any of these groups in the future. I am disappointed at the guys in the list (not all, just some) who seem to have little regard for what I say (and I still have to live with that old worry, now, whether it’s because I’m a woman, or because I’m making stupid comments.)

But I’m also disappointed at the women in the group. Why didn’t they speak out? Why did I have to speak out, alone? Do they know how hard it is to be the only woman talking in these groups?

Where were they when I needed them?

I have some very bad stuff going on in my life now, which I’m not going to talk about here because its deeply personal and, respectfully, lovingly, none of your business. But I don’t have the energy to fight these battles now. I may not ever again in the future.

I’m not walking away from the tech again. I am enjoying my interaction with those who are interested in the RDF Poetry Finder. It may not be sexy lines of code, at least not yet; but this could be the first weblog-based group participation in a project that involves both technical and non-technical people, and it’s a really fun project. At least, I hope so.

When we’re finished, we’ll be able to offer it as a search engine implementation to sites such as Plagiarist and other literature, writing, and poetry related sites. Perhaps even the Guttenberg project. It’s a difference. A small difference, but a difference.

It’s not changing the face of the Web, or even of Google — but it’s a start. It may not be sexy, but it’s doable. I guess when it is up and running, and we can all look back and bask in the glow of our efforts, then that question I have about my worth in technology will be answered. Because it’s not going to get answered in email forums where the women stay silent, and the jerks dominate.

I will say this, though: social software is never going to fly if there isn’t some way to control the peacocks, as Liz called them, and the peahens don’t stop standing in the shadows.

Update:

I hope that the participants in the RDF Poetry Finder are not put off by this posting. Believe me when I say this wasn’t written lightly, and I’m aware it will make people uncomfortable. But it was something I had to say. And, note: I am also aware that I could be wrong in my interpretation — touchy I might be, but at least I try to be honest with myself.

Well, I think.

Categories
Technology Weblogging

Threadneedle just got competition

Ben and Mena at Movable Type just released a Trackback threading tool that will build an entire tree out of MT trackbacks. Here’s a page showing the Trackbacks from one of my earlier postings

Yes, this is what ThreadNeedle is supposed to do. Yes, ThreadNeedle is not finished.

When you enable TrackBack for a posting, Movable Type embeds a small piece of RDF in the page, such as the following:

 

<rdf:RDF xmlns:rdf=”http://www.w3.org/1999/02/22-rdf-syntax-ns#”
xmlns:dc=”http://purl.org/dc/elements/1.1/”>
<rdf:Description
about=”http://burningbird.net/cgi-bin/mt-tb.cgi?tb_id=17″
dc:title=”World Summit Weblog”
dc:identifier=”http://weblog.burningbird.net/archives/000476.php”
dc:subject=”Politics”
dc:description=”Many thanks go out to Farrago for pointing out that there’s an extremely well organized weblog covering the World Summit. Now, this is what a political weblog is all about. Take a look and tell me you’re not impressed with…”
dc:creator=”shelley”
dc:date=”2002-08-2514:00:27-06:00″ />
</rdf:RDF>

 

This simplified RDF can be embedded because all of the RDF data is treated as attributes — notice that there’s nothing outside of the Description element? Attributes don’t get printed out via the parsers in the browsers.

So, why can’t I do this with ThreadNeedle? Two reasons.

First, I can’t control the output of the weblogging tools, so if I give you a piece of RDF to embed in your posting, the weblogging tool will try to add break tags (< br/>) to the code to handle line breaks in the RDF. This screws up all RDF processors.

Secondly, anything more sophisticated then the example I showed you requires special handling to embed the RDF in HTML/XHTML. Surrounding the data with the Script tags will work — the parsers ignore anything contained in script tags. However, this still doesn’t solve the problem of weblogging tool munging.

I can generate RDF, and it’s very doable to create an application that finds the RDF, and follows the threaded entries to the new page and looks for embedded RDF and so on (as the Movable Type Trackback threading application does, except that it uses the Trackback data stored in our local data stores) but I can’t control the munging of the RDF by the weblogging tool.

Ben, Mena, this was cool. Really. And thanks! I hate to be greedy, but can you and Ev and Dave and the other weblogging tool builders give us a window in the weblog posting page to include content that is embedded directly in the posting, without manipulation by the weblogging tool? Then others, such as myself, can provide functionality — such as ThreadNeedle — that isn’t dependent on the weblogging tool and without having to go through extraordinary means of handling this markup munging problem.

I realize that webloggers can turn off line breaks (either for a weblog or a posting), but many webloggers don’t know how to include their own HTML line breaking tags. What I’m looking for is the best of all possible worlds — a separate window that takes text which is added to the bottom of a weblog posting without any processing by the weblogging tool, while still allowing tool processing of the weblog entry itself.

Pretty please?

In the meantime, I have the Movable Type Threading CGI application running (Access here, pass in the URL of the page with Trackbacks). Feel free to try this with pages that have TrackBack enabled. If it slows my server too much, I’ll have to pull it, but we can give it a try for now.

Categories
Technology

The geeks have it

Jonathon has become the latest recruit to the Geek Force. I’ll have to send him an autographed copy of Unix Power Tools 3rd edition as soon as it’s published. Just think, Jonathon– 1200 pages full of tips!

(Makes a good doorstop, too.)

And now Jonathon can join us in the most important debate of geekdom:

Which is better? vi/vim? Or emacs?

Blood has been spilled over this issue, so use caution when responding Jonathon. In fact, there are many items that generate an almost religious ferver within the Unix world as you’ll find out…soon.