Categories
Web

Who is your audience and what are you trying to accomplish?

Recovered from Wayback Machine.

Just posted the following over at RSS-Dev (edited to remove typos):

There seems to be three separate threads running along the lines of “Who are we and what are we trying to accomplish”, mixed in with proofs and justification of keeping RDF in the mix. How can the energy expended into these threads be coalesced into a determined course?

I asked the question, here and elsewhere, who is your audience? This isn’t marketing or make work. This is a genuine attempt to understand what this group hopes to accomplish other than working with cool technology for the sake of the technology. What is the business of this group?

If RSS, past and current, is based on providing syndication and aggregation feeds, and nothing more, than I agree with those that say RDF adds nothing to the mix, and not because RDF adds complexity — the reason is because the business of RSS isn’t necessarily compatible with the business of RDF.

In the last few weeks, Phil Ringnalda has been working on a application to process RSS 1.0 files and combine this with FOAF to provide a sophisticated interface allowing us to find who has posted or commented on what topic. Yesterday he hit what is probably the core difference between the business of RSS and the business of RDF — the fact that tools generate labels for blank nodes, and that these labels will vary each time the same file is parsed. (See
http://philringnalda.com/archives/002327.php). RDF/RSS (RSS 1.0) has blank nodes.

RDF is a meta-language for describing items that exist in such a way that this data can be processed with the same set of tools and combined with a great deal of confidence that this mergence results in a valid pool of rich data. It is literally a markup version of the relational data model, and as such, is extremely useful and necessary to help with the chaos that XML created. However, there is an implied persistence to the items described with RDF, the same as there is with relational databases. Data may change and be removed, but there is no temporal self-destruct attached to the items.

RSS, as the majority of those who view it (the users, not the tool developers) is a syndication feed — nothing more than recently updated items that can be polled and aggregated. There is no implied persistence. In fact, the business of RSS is based on impermanence.

This is a major difference in ‘business’ between the two concepts. From a database perspective, this is equivalent to using an RDBMS when a flat file of comma-delimited data is all you need.

If this group wants to continue providing a specification that defines syndication feeds, then it needs to consider that RDF not only doesn’t buy the group anything — it can harm the tool developers that use the spec. (Not to mention that trying to use RDF inappropriately can actually negatively impact the acceptance of the RDF specification.)

If, however, this group sees that what they’re working on transcends throwaway syndication feeds, then it needs to formally define exactly what the business is _before_ trying to create a spec that implements it. Hence my questions: who is your audience and what are you trying to accomplish?

Specific instances of technology aren’t an answer to these questions. This isn’t answered by, “Well, we’ll just continue as is and use XSLT to handle any problems in the future” or “We’ll use modules”. If you find yourself answering these questions by referencing technology, then either you’re missing the point, or (more likely) I’m doing a piss-poor job of explaining myself.

What is the problem this group is trying to resolve? What is the benefit this group is trying to provide that no other technology or specification provides? Who is your audience? Not the tool developers — people don’t write tools for no reason. Who are the consumers of the tools developed?

What are you trying to accomplish?

This understanding of the basic business goes beyond a name, though the name of ‘RSS’ is drastically adding to the problem by forcing a type of business on this group that this group really doesn’t want, as well as adding an element of competition that is both unnecessary and harmful.

Perhaps this group really isn’t interesting in throwaway syndication feeds. Perhaps this group is interested in finding ways of describing publication units that may or may not be smaller or bigger than an individual web page, and a side benefit of this is that the data can be used for aggregation purposes. Or not. I don’t know — the group hasn’t told me what the business is.

If you continually have to justify the use of something over and over again, either you’re wrong, or your audience is wrong. In either case, you need to re-focus your efforts, and either find a different audience, or stop beating a dead effort.

Categories
Web

The turbulent waters of RSS

Recovered from the Wayback Machine.

I was pleased and rather surprised to see so many comments attached to my posting on RDF. As to be expected with recent discussions, the thread soon turned to issues of RDF/RSS. That’s cool.

What isn’t cool is something such as this by Morbus Iff and Dave Winer’s absolutely atrocious response. Saying something such as:

Anyone who works with Hemenway or Kearney should be aware that these people are nothing less than monsters, who will stoop to any level to get their way. Their perversion may even be the reason they’re involved.

Over the line. What I especially can’t understand with the essay is why Dave brought Ben Hammersley into this particular discussion. The reason looks to be because Ben didn’t include Radio in the RSS aggregators discussed in an article he wrote for The Guardian. Dave called Ben’s article tainted just because Radio — which is a weblogging tool, not a pure news aggregator — wasn’t mentioned.

Calling Morbus on inappropriate joking is one thing. Publishing Morbus’ name, attacking Ben, and calling Bill and Morbus ‘monsters’, is another.

The RSS discussion continues I gather over at Blogroots as well as RSS-Dev.

Time to move on. Let Userland have RSS if they wish. The folks involved with RDF/RSS should come up with a different name, as simplified a syntax as possible that is still valid RDF, and let folks use what they want. If some folks want to use XSLT to transform RDF/RSS to Userland RSS, or the reverse, fine. But this is a technical trick and kludge and shouldn’t even be considered as part of a specification.

I would also strongly recommend that the newly renamed and reformed RDF/RSS working group define the intent and focus of RDF/RSS so that it doesn’t become “one XML to rule them all”, in their interest of creating the perfect syndication format. And since the group would be in the process of many changes, I would also suggest that the RDF/RSS working group move their discussions to another venue other than Yahoo groups, with all its many annoying ads. It’s becoming increasingly difficult to follow the threads: the quotes from previous messages overwhelm the new content, the mix of discussions about spec minutia and group working matters with grand overall schema changes is perplexing and off putting to new people getting involved, and on and on.

It’s also past time for the RDF folks, other than just Dan Brickley, to start getting involved. In particular, I wouldn’t mind seeing the RDF working group folks with weblogs. I have found this to be an excellent format for opening conversations with one’s target audience.

As for myself, I’ll only support an RDF-based aggregation newsfeed at my web sites because I believe this is the better approach. If this means my feeds aren’t readable by some aggregators, okay, I can live with this. This will be an unfortunate side effect on not being able to pull reasonable people together to come up with a combined specification (and note that I don’t consider that a lot of the players in this little farce to be ‘reasonable’, a statement thereby pissing off all participants equally).

Personally, I think a widening of this particular rift is a positive rather than a negative event.

Postscript: You know, there are no women involved in the RDF/RSS working group or the RDF working group. I think this should change. Perhaps I should lurk less and talk more. Any other lady techs in the audience wish to join me?

Categories
Standards Web

Issues of accessibility

Recovered from the Wayback Machine.

Unless you’ve been living under a rock, you’ve probably heard about Mark Pilgrim’s Thirty Days to a more Accessible Web. The series covers basic steps we can take to make sure our weblogs and web sites are accessible.

His first tip is on DOCTYPES.

I tested my weblog against the 508 accessibility test at Bobby and according to the results, not necessarily trivially easy to read, I should meet this standard. However, I don’t meet the Web Content Accessibility Guidelines 1.0 standard.

Does anyone meet the Web Content Accessibility Guidelines 1.0 standard?

Once I’m settled, I’m enlisting the help of experts among my virtual neighbors (weblog translation – I’m whining, begging, and groveling for help because everyone knows I’m a back-end developer and know shit about front end stuff) to make sure my weblog and web sites are accessible.

If you have a weblog, don’t you have something to do about now?

(And once you’re done with that, move your tushie over to AKMA’s and give him some requirements and suggestions for Thread the Needle.)

Categories
Web

Congrats, Sam Ruby

I consider Apache to be an excellent example of what the computer industry can accomplish when it pulls together to create a truly open product. When I heard that Sam Ruby was just elected to the Apache Board of Directors, I had to post a note about the event.

Congratulations, Sam! The Board will be richer for your presence. Of course, you can now kiss all your free time good-bye…

Categories
Web

Dot Com Bust Redux

I’m assuming the only reason that the RealNames failure is getting air time is because the former CEO has published its business dealings with Microsoft.

I glanced through Keith Teare’s papers at his personal web site, and just can’t see the fuss.

Microsoft chose to terminate the relationship with RealNames. With the nebulous nature of the product, the overall opinion against such centralized technology in today’s market, and the business proposal I don’t see how anyone could be surprised by this decision.

RealNames owed Microsoft $25.5m on May 2nd. They didn’t have it. They issued a counter-proposal. Microsoft wasn’t interested. RealNames bites the dust.

Teare believes that Microsoft isn’t demonstrating vision in its current direction, and is seeking solutions that it can control. Maybe so, but consider the proposed future direction for RealNames: Centralized, proprietary, flat architectured Keyword technology in partnership with a company such as Verisign.

I have a hard time identifying with one proprietary, centralized, patent-holding company fighting back at another proprietary, centralized, patent-holding company.

However, I do have sympathy for the 75 people in Redwood City that lost their jobs.