Categories
Weblogging

Silent Voices

Recovered from the Wayback Machine.

I was, and was not, surprised to see Mike Sanders hang up on weblogging today. I could see glimpses of burn out in his recent posts. In addition, he’s involved in new conflicts that would leave a sour taste in anyone’s mouth who is witness to them.

My decision to do away with a traditional blogroll started, in part, with Mike. In March this year, he removed several people from his blogroll, and posted a note that he did so because the people were “terrorist sympathizers”. After the uproar attached to this action, he put the people back on his blogroll, and issued an apology, of sorts.

In my comments attached to the Roll Call post, Jonathon asked:

 

In terms of the delinking debate, will you include posts with which you vehemently disagree?

To answer Jonathon, the first post I was going to link to and excerpt in the new system was Mike Sanders’ post on removing people from his blogroll. I considered that one to be pivotal within the weblogging history I hope to capture.

There are few weblog postings that have had as much of an impact on me as Mike’s. Based on this posting, between one moment and the next, weblogging had changed for me. It was no longer me writing in a vacuum; it was about me being part of a community, one in which conflict exists in addition to comradery. As difficult as the events of the time were back then, the end result is that weblogging became a much richer experience for me. For many of us. And I would be less than remiss — less than honorable — if I weren’t to acknowledge this.

Mike brought much of the battle he retreates from on to himself. He used the term moral equivalency as a stone on which to stand and look down on others. He re-interpreted viewpoints in a manner almost guaranteed to frustrate the originators of the viewpoint. He used labels as weapons. He also sent emails to people that would exacerbate an already tense situation. Mike introduced conflict.

However, Mike also started conversations. He got people to think. He helped us to understand the power of this medium and he made us all realize how much impact simple words, and simple links, and simple actions, could have.

The (negative) concept of de-linking is partially responsible for me removing my blogroll. However, in its place will be something that, I hope, will be much better than passive links. Ultimately, I think we’ll benefit greately from this change. And I owe this, in part, to Mike.

The conflict he introduced, the discordant notes he played with many of us, added to the richness of this medium. He writes today:

 

So I would like to dedicate this post to any people I have angered. Consider my giving up blogging as your own personal victory. And get on to the important task of developing love towards your family, friends and community.

 

I feel no victory. His weblog will be missed. His silence will be heard.

Categories
RDF

Creative Commons and RSS Syndication

Recovered from the Wayback Machine.

I am applying some pushback in regards to RSS and the Creative Commons License over at the RSS Development Group discussion group.

My original statement:

I’ve already incorporated this into my weblog template and into my PostContent system for weblog resources. However, there is no defined semantics defining the understanding how licensing is applied to RSS feeds. For instance, is the license applied to the feed or the source? If the feed, how does the CCL attached the feed conflict with implied consent of the data considering that RSS feeds are assumed to be aggregated and potentially published? If the feed has excerpts only, wouldn’t this be overridden by fair use laws? If the feed has all the content, does the license apply to the content as feed or to the content separate from the feed?

How is a conflict resolved between a license in a feed and a license within the actual resource itself? Does the license in the resource take precedence?

Just because the CCL is RDF/XML, doesn’t mean we should run out an incorporate it into every existing RDF datastore: FOAF, RSS, and so on.

Good discussion. If you’re interested in CCL and syndication feeds, or impacts of licensing on aggregated material, or even a peek at the confusion that can result when tech and law are thrown together, you might be interested in checking out the discussion. Technical background not required.

Hopefully, some fo the Creative Commons folks will also check this out and get into the discussion.

Categories
RDF

RDF Browser

Recovered from the Wayback Machine.

Thanks to 0xDECAFBAD for pointing out another amazing RDF product from the HP Semantic Lab – Brownsauce.

Brownsauce is based on the Jena Java API and uses the lightweight Java web server, Jetty, to serve the application pages. Or, if you prefer, you can install it into your own Tomcat server. The only requirement is Java support, and there is no installation and configuration required to work with it. I’ve successfully used it without problems in Windows 2000, Mac OS 10.2, and Linux.

Brownsauce translates RDF into human-consumable content, including separating nested resources into separate pages, linked to the parent statement. Additionally, clicking on any of the predicates (properties) opens a page with information about the predicate, polled from the associated RDF Schema file.

One very slick application. A must for any RDF-er.

Categories
Technology Web

First, let’s fire the boy-racer HTML programmers

Recovered from the Wayback Machine.

Joe Clark, author of Building Accessible Webs in a Jonathon Delacour interview:

 

And of course we’ll also have to fire the boy racers’ clueless Dockers-wearing manager dweebs, who consider themselves old-timers because they got online in 1998 (!) and whose entire experience of the Internet is the commercial Web as rendered through Internet Explorer for Windows. These people cannot even *spell* “W3C” and still think banner ads have not been given a fair shake.

Boy racers and clueless Dockers-wearing managers, beware!

(And will Jonathon ask the question we’re dying to know: Does Joe use a Dishmatique?)

Categories
Technology

Office and XML

Recovered from the Wayback Machine.

Sam Ruby has an interesting thread going about Microsoft’s next version of Office and its support for XML:

 

On one side, the ability of MS tools to adapt to formats that users can describe will be an incredible step forward. On the other hand, this doesn’t explain an unwillingness to working with others to describe the semantics that PowerPoint 11 uses to capture a pie chart.

Interesting thread and comments. However, I’m also linking to this post in case Sam’s comments run out; the interested parties can then come over here and use the comments attached to this posting. I’m providing a Weblogger Comment Overflow Buffer.

Always a good neighbor.