Categories
Specs

Sometimes you feel like RDF, sometimes you don’t

Semaview came out with this illustrated RDF vs XML graphic showing the ‘differences’ between RDF and XML. At least one assumes this is the purpose of a graph so titled. This might be confusing for some people that assume RDF is XML, which isn’t entirely true: RDF is a model, RDF/XML is one serialization of that model.

(Still, when you have XML on one side and RDF/XML on the other, one does wonder where the concept of ‘versus’ enters the picture.)

Based on this illustration, Leigh Dobbs asked the question:

I’m working with RDF tools now, but thats because FOAF is an RDF vocabulary. I’m just using the right tools for the job. If I was given a task to design a new system I don’t have any feel for why I might choose RDF over XML. I haven’t had that “aha” moment yet.

Personally, I doubt there will ever be an ‘aha’ moment associated with any W3C specification, but that’s beside the point.

In response to Leigh’s question, I wrote the following in his comments:

Pat Hayes actually grabbed a quote from the book and posted at the RDF WG core mail list about RDF’s usefulness:

“RDF is a technique to record statements about resources so that machines can easily pick up the statements. Not only that, but RDF is based on a domain-neutral model that allows one set of statements to be merged with another set of statements, even though the information contained in each set of statements may differ dramatically.”

XML gives us the format to record domain-neutral data, but RDF gives us the methodology to record complete domain-neutral statements — data in action as it were.

Ontologies are then domain-specific views built on top of the domain-neutral model that is RDF.

It’s all layers. Taking a cross-section:

Knowledge can be split into domain-specific views (ontology) based on complete statements (RDF) consisting of separate pieces of syntactically valid data (XML).

Since the first moment that XML appeared a few years back, the first thing I, as a data, not a markup person, looked for was a data model making use of XML. To me, XML would never be anything more than interesting data formatted in an interesting manner; without rules to help that data form some cohesive pattern outside of the rules defined for each implementation of an XML vocabulary I doubted its usefulness. Still, the bugger caught on and achieved wide-spread use.

Such waste — all that machine accessible data and absolutely no way of merging it into one data store in any meaningful way. Worse, having to create algorithms to manage each specific XML vocabulary rather than having one set for all vocabularies.

To me, all these XML vocabularies are equivalent to throwing out our relational databases and going back to proprietary data structures in each of our applications. Change jobs, learn an all-new structure. Buy a new application, and face a huge learning curve just understanding the underlying data and how it’s interrelated.

I knew when RDF came out it was the missing link between XML as bits and pieces of data, and XML as information; this though RDF wasn’t necessarily created specifically to be used as a model for XML.

(Some would say that the marriage between RDF and XML was a shotgun wedding at best. I don’t care. The cake was good and the band played on; I had a good time.)

In an effort to answer Leigh, Dorothea Salo wrote:

First. If you must end up with something XML-valid, don�t bother with RDF. Just don�t. Yes, you can restrict the RDF/XML you produce to a specific syntax form; you just can�t expect anything you receive to be similarly restricted, because RDF/XML-generating tools can�t be made to give a damn about which form they output of the many possible syntax forms of a given set of RDF/XML statements.

What Dorothea is referencing specifically is that there are different forms of XML that can be used for a specific type of RDF construct, which means that the same RDF model can be serialized in four different forms, and each would be an accurate and valid rendition of that model. True, but that doesn’t preclude that all of the XML is valid and that all of it can be restricted through DTD’s and XML Schemas, and still be valid RDF/XML.

However, Dorothea is right in that RDF is not magic pixie dust. RDF is nothing more than a way of recording domain-neutral statements in such a way that they are merged with other domain-neutral statements, each statement adding to the others in a mounting knowledge base.

When she says:

Computers only know what you tell �em. They don�t automagically know foo from bar any more than humans do. Inference only gets you so far. Sure, it might be further than we�ve been yet; I�m inclined to think so, myself. At some point, though, somebody�s got to know what the bits of the vocabularies mean, and all the inferential power in the world won�t get that across.

XML gives us the ability to record bits and pieces of data in a valid manner. RDF then builds on the data, piecing the bits and pieces together into complete statements. Ontologies then take these statements and build machine-understandable inferential rules based around them. The result of all this working together is the wine scenario:

Information from a vineyard is recorded as XML, and the names of wine are recorded as XML Schema datatype strings. The XML ensures that the names are valid, and the data is accessible with any XML compliant parser. Another format could be used, but then if someone else wanted to access the data, they’d have to build parsers that can understand the proprietary format.

The RDF model then provides the means to incorporate those names into facts, such as “Chianti is a red wine”, using a serialization technique molded on to XML:

<rdf:Description rdf:ID=”chianti”>
<wine:category rdf:datatype=
“http://www.w3.org/2001/XMLSchema#string>white</wine:category>
</rdf:Description>

We could build the model on which the facts are based directly into the XML vocabulary. But then, we’d have to make sure the model and the facts were consistent regardless of use. And since it was proprietary, other tools would also have to build in the ability to produce or consume facts based on this proprietary model.

Finally, the ontology, such as DAML+OIL and the W3C’s OWL, pieces together the separate statements and facts into domain-specific knowledge, by applying rules that allow machines to make inferences on the data, such as the fact that a cheese and nut dessert course is a part of a formal meal and is an alternative to a sweet dessert, and wines served during this course should be red:

<rdfs:Class rdf:ID=”CHEESE-NUTS-DESSERT-COURSE”>
<daml:intersectionOf rdf:parseType=”daml:collection”>
<daml:Restriction>
<daml:onProperty rdf:resource=”#FOOD”/>
<daml:hasClass rdf:resource=”#CHEESE-NUTS-DESSERT”/>
</daml:Restriction>
<rdfs:Class rdf:about=”#MEAL-COURSE”/>
</daml:intersectionOf>
<rdfs:subClassOf rdf:resource=”#DRINK-HAS-RED-COLOR-RESTRICTION”/>
</rdfs:Class>
<rdfs:Class rdf:ID=”CHEESE-NUTS-DESSERT”>
<rdfs:subClassOf rdf:resource=”#DESSERT”/>
<daml:disjointWith rdf:resource=”#SWEET-DESSERT”/>
</rdfs:Class>

This type of information can never be recorded in ‘straight’ RDF/XML because you’d have to have the ability to record the inferential rules, and RDF focuses on recording statements. Additionally, the information could never be discovered in straight XML because you have to have the ability to record not only the rules but the statements, too. You would literally have to build a model and then find a way to serialize that model in XML. Just like RDF. If you used XML, you’d have to define the ability to record facts, and then on top of that, the ability to record the necessary information to perform inferential queries — something more esoteric than “what is a white wine”.

But using XML as a data format, and using RDF as a statement/model methodology and using OWL to record the domain-specific rules, you can go to the application such as the Wine Agent, ask for recommendations for a cheese desert wine within a certain region and get the following answer:

“Pairs well with sweet red varieties. Full-bodied wines featuring strong flavors match especially well.”

The local knowledge base particularly recommends the following:

TAYLOR PORT

The recommended wines can be found below, along with some comparable selections: (with link to selection)

The frosting on this particular layer cake is that anyone associated in some way with the wine industry — producing or consuming — could use the wine ontology, based on RDF, persisted in XML for their own applications and functionality. Better yet, another industry, let’s say the chocolate industry, can use the same XML/RDF/ontology combination, and the same tools that work with each, as a way of recording their domain-specific data.

And you’ll be able to know exactly which champagne to buy to go with that dark bitter-sweet chocolate covered orange peel you bought for that special someone.

Categories
Copyright RDF Writing

Checking in

Thanks for well wishing. The suggestion of tea was a good one, but unfortunately I can’t drink any acidic juice such as OJ, as it hurts my throat more than a little.

Doing a bit of catch up. There were a couple of items of RDF I had to respond to over at Practical RDF, both of them related to postings from editors on the book. My only comment in addition to my two postings is this: I have a great deal of respect for the RDF Working Group. They worked, hard, to reach Last Call status on the newest RDF specification documents. All that’s left is a few odds and ends, and they can call their job done. It would be a real shame if the group took all that hard work and drop kicked it off a cliff in a burst of tired arrogance at the end of the day.

Liz joined the fun on Creative Commons with a challenge to Jonathon and myself to provide reasons for why not to use the licenses:

 

How ‘bout a “non-shithouse” version of why people might choose not to use the license, that can live side-by-side with the CC discussion of why they should?

Well, you only have to search on “creative commons” among my archives to see my comments, though I’m not sure about their ‘shithouse’ status. I look to Jonathon to provide a better answer to Liz, if he wishes, as the RDF posts took my time tonight, and I’m to bed. However, it seems to me that if Creative Commons is to be effective, it’s up the members of the CC to detail the problems associated with the CC licenses as well as the advantages. I’ve pointed out to a couple of members the writing that Tim Hadley has done; hopefully they’ll consider writing a post or two on these issues to go with all the postings about this artist or that blogger that has attached a CC license to their work.

I was more interested in responding to the discussion Liz and Dorothea are having about about academia. Specifically, I wanted to pursue the thread off this conversation that Baldur started:

 

Everybody speaks the same, in the same way, about the same thing, with little to no variation. We could easily turn into the lightspeed version of the same unsubstantiated bullshit of postmodern academia, shedding even the pretense of giving ideas space and scope for discussion.

What killed the author and poisoned academia is trying to return through the violated corpses of a horde of ’blogger-zombies spouting inane commentary on the links of the day.

But as the popularity of weblogging increases, the number of meme-victims will rise and the blogdex top fifty will not only describe the fifty most popular subjects amongst webloggers…

It will describe the only subjects.

What I’ve tried to say in a thousand words, Baldur said in a few. I wanted to write in response, but lacked the energy to respond well. I couldn’t do justice to Baldur’s words.

But when I’m well, and have the energy to respond, to do Baldur’s writing true justice, should I?

Categories
Just Shelley

Down for the count

I thought I was lucky, getting only a mild case of flu and missing out on the misery Steve and AKMA and Halley and Loren and others have endured. I found out this morning that what I had this weekend was nothing more than a precursor for the real thing.

I’ve spent the day alternating between sleep and some over-due reading, too much of the former, not enough of the latter. I’d like to catch up on the reading (“Burning the Days”, “Happinesstm“, and “Austerlitz”), but I’d rather not be sick.

Categories
Burningbird Copyright

Domain for sale

Recovered from the Wayback Machine.

A quick note — Tim Hadley wrote a very detailed careful analysis of the Creative Commons license from the perspective of webloggers in general, Movable Type specifically. In particular the section that relates to the permanence of a CC license is worth extremely careful perusal if you’re thinking of pushing the button to have MT add CC licenses to your weblog.

Also, from what Dave Seidel said in my comments I could be looking at weeks of email spam problems. If this is a continuing problem, then it will show after midnight, as it did yesterday. We’ll see in the morning.

By default, I have all emails that don’t specifically go to anyone else come to me as main webmaster. This means, then, that the email spam messages come to the shelleyp AT burningbird DOT net email address.

As an interim solution, if you need to send an email to me, please use a new email address I created to bypass potential spam email floods: bb AT burningbird DOT net.

The yasd.com domain is coming up for renewing in 45 days. I consider this problem a sign of the times, and I’m going to look at either letting it expire, or the possibility of selling it. The acronym YASD does have significance to Japanese and other electronic game players, so I might be able to make a few bucks. Maybe enough for my server.

I hate to lose the domain, though, I’ve had it since early 1996.

Categories
Weblogging Writing

Google is not God, Webloggers are not capital-J journalists, the only thing emerging is my fear of war, and a headache

Recovered from the Wayback Machine.

Though my opinion will not be shared by the majority of those who read this, I greatly appreciated the article appearing in the BBC News, Is Google too Powerful. Not only did the writer, Bill Thompson, challenge this continuing nonsense about webloggers ‘replacing’ mainstream Captital-J Journalism, he also exposed the falsity of the godhood with which Google is treated.

Of the so called ‘superior accuracy’ of webloggers, he writes:

The much-praised reputation mechanism that is supposed to ensure that bloggers remain true, honest and factually-correct is, in fact, just the rule of the mob, where those who shout loudest and get the most links are taken more seriously.

It is the online equivalent of saying that The Sun newspaper always tells the truth because four million people read it, and The Guardian is intrinsically less trustworthy as it only sells half a million.

 

When it comes to world news and opinion, he or she who gets the most links, wins in the world of weblogging. Those with the pareto charts and your esoteric algorithims of popularity tend to prove this out. According to the charts, rather than a new form of connectivity, we’re really just another instance typical of medieval community: with the indifferent, smug supremacy of the elite at the top and rule by the mob at the bottom (we know about the viablity of mob rule for fair and ethical treatment of either person or subject).

Within this view, occasionally the mob and the elite might join forces, briefly, and we might help with a story, such as Trent Lott and his big mouth. For the most part, though, we’re a bunch of editorialists without much concern for research, fact checking, or accuracy. That’s okay, though, because I didn’t start writing this to become yet another journalist-wanna be. Nor an elite. Nor part of a mob.

I’ve heard two common threads this last week: Weblogging is a whole new form of individual expression, without hinderance from editor or government; weblogging is a movement with power to report and shape the news. You can’t have it both ways — either we’re individuals with individual interests and independent thoughts and writing, in which case we’ll seldom have impact on the accuracy or direction of the news; or we’re a mass mind with too little independence to think outside the herd, but with enough power to stop war, throw out presidents, and change the course of history.

You can’t have it both ways. Either we’re different and unique and independent. Or we’re not, and weblogging is nothing more than a variation on an all too common societal theme.

Michael O’Connor Clarke wrote about journalism’s failure to cover the story of the deaths of thousands of Iraqi soldiers during our first battle with Iraq. Michael writes:

This suggests an urgent need to recruit and train an army of Iraqi bloggers, either here in the ‘Free West’ (*cough*), with strong connections to feet & eyes still resident in their homeland, or preferably right there in the thick of the horror.

We should arm them with satellite WiFi blogging tools and digital cameras to record and publish the unvarnished, un-CNNed truth.

 

What Michael forgets is that there would have been no witnesses because the people would be dead. In the starry eyed rush to show the glory of weblogging, and it’s full unleashed power via Google, he neglected to remember that the people were dead. Dead people don’t weblog.

We’ve long had the ability for people to “get the story out”. We have telephones and cameras, and if anyone had access to this at this battle, the story would have gotten out. But the only people who witnessed this act were those who died, and those who buried them. And the reason we know the story now is that some of those who did the burying are speaking out.

Who would have blogged this? Ghostly fingers from a grave?

Forget the pareto charts, and the Google and Blogger crap and focus on what this war is going to be like. We, the US and a few allies will invade without UN support. We’ll start with a barrage of missles and remote weapons, battering the Iraqi until we bring them to their bloody knees. Using this approach we can, hopefully, minimize the number of our troops lost. Though I agree with protecting our troops, this tactic is also the one most likely to maximize the deaths of civilians, as well as the destruction of services necessary to the survival of the people.

In retaliation, Saddam Hussein will blow up the oil wells, the dams, and the bridges. He’ll deny food and services for millions, effectively creating a human wall of misery around himself to protect himself from the invading army. However, even those within his protective sphere won’t be undamaged, because they’ll be the ones being bombed.

Saddam Hussein will also release whatever chemical and biological weapons exist, and he’s not going to care who gets exposed. His own people, his neighbors, Israel, our soldiers. For the first time in history, there will be one thing commonly shared by the peoples of the Middle East — exposure to weapons that should never have been invented. Excuse me if I don’t clap.

During this battle, the Iranians will most likely make inroads into Iraq, and the Kurds will begin the battle for control of the country, since they’ve already been told by the White House that they’ll not be allowed to run the country after Saddam Hussein is gone. We’ve promised Saudi Arabia and Turkey there will be no elections, no democracy. In addition, the Kurds will have been treated badly and if there’s one thing we know about the Middle East, the concept “an eye for an eye” is alive and well in that region.

In the midst of what promises to be one of our more vile wars, with human warring against human in our most inhumane ways, we’ll find our lone bloggers, bravely sitting at laptop with satellite phone, blogging the story so the truth will be told. I don’t think so.

We won’t need the bloggers to tell us the truth. We’ll see the millions — yes, millions — who are starving, the soldiers as they suffer the effects for years to come of the agents used against them. We’ll be able to smell the smoke of the oil fires for years into the future, and we’ll feel the effects the smoke will have on our weather.

There will be no mass grave large enough to bury those that die in this war we say we want to fight for the good of humanity.

I don’t want to rain on the parades of the enthusiasts. I don’t want to dampen the spirits and enthusiasm of those, such as TomJeneane, Michael, Joi Ito, and others, who think everything will be different if we all just weblog. I admire and cherish their joy and dreams based on our connectivity.

Additionally, I don’t want to rain on the “Poets against War” and the “Readings against War” and the “nudity against war”, and the other refined forms of protests. Any sincere protestation of war should be respected.

I remember the starry eyed enthusiasm of those who protested against the Vietnamese war years ago. I remember because I was one of those who protested, one who placed a flower into the barrel of a guardsman’s rifle, who linked arms, who painted peace signs and flowers on my face, who sang “Give peace a chance”. Thankfully, I was not one of those who said just vile things to the war shocked, exhausted veterans as they came home.

But I was one of those who thought it was these protests that stopped the war, only to realize as the years advanced, that it was those who were silent, the vast majority who did not march, who stopped the war. And they did so because they became tired of the body bags coming home.

The St. Louis area has over 400,000 people, and of those, probably only a tenth, if that, have a computer. Of those, a scant 300 or 400 weblog. It is those who don’t weblog, who will stop the war in this country. And, if I may presume on some cultural similarities, it is the same type of person who will stop the war in other countries.

Joi Ito sees weblogging as small groups of people formed around shared experience or interest. Within these groups, he sees a positive feedback loop that pushes a signal above the noise, identifying important information for other weblogging groups to pick up. The signal grows in strength as more groups link to it and the signal eventually, if important enough, gets picked up my those outside of weblogging. As an example, he points to the recent anti-warpro-war debates

This is a good explanation of what happens with some of our interests, such as the recent Google/Blogger merger. However, this tends to only happen when we sustain the signal for a significant period of time, as we did with the Blogger/Google merger, and as we did with Trent Lott. It’s not enough that we push an item into the charts — it’s that we hold it there sufficiently long enough to attract the interest of others.

Unfortunately, webloggers are nothing if not little birdies easily distracted by some bright shiny new toy just around the corner. Frequently, we indulge in cross weblogging circle conversations; rarely do we do so for any sustained length of time.

As for the aforementioned debate, the quality of it is no better, nor worse, than what one hears on the street, or in the next booth at the local restaurant. This isn’t to detract from those who took the time to participate in this debate. It is to say, in effect, what makes anyone think we’re so erudite in our debates that anyone other than webloggers would want to stop long enough to hear what we have to say?

Joi Ito also writes:

Many bloggers begin their weblogs to communicate with their strong tie peers. They will mostly link to and communicate within their small group.

 

Of the group I linked to when I first started, half are no longer weblogging, and most of the rest, I no longer link to because of changed interests. Of the people I linked to a year ago, several quit weblogging, some went in directions I couldn’t follow, and others, well, for one reason or another, we just stopped communicating. Of the people I link to now, they’ll stay on my blogroll regardless of their views because will no longer de-link another active weblogger. Even if they go in directions I can’t follow, I’ll still read their adventures along the way. How will my blood flow except by the push it gets when I read words that make it boil?

Will I my blogroll grow? Sure, but I’ll manage.

My point is that whatever weblogging circle we’re in at any point in time, it isn’t a fixed circle, and neither is it harmonious. The ‘best’ weblogging circles, if best is the correct word, is one in which the members don’t all agree. Otherwise, reading each others posts would be like looking at ourselves in the mirror all throughout the day — no matter how vain we are, we’re going to get bored eventually.

This means though that seldom will we all agree and when we do, seldom will we sustain that agreement. And because of this individuality, seldom will we push a signal above the general noise long enough to be heard by others. Our acts of individuality counter-act the formation of a mass-mind with enough power to effect change globally, though we may wreck chaos, at times, about ourselves locally.

I started weblogging because I wanted to write, and I wanted to share what I write in the hopes that others might like it, be moved by it, even grow from it. I’d like to think I could stop this war with it, but I can’t. And nothing Google can do with weblogging will change that.

What irony: by being an individual and writing on what I want, when I want it, and encouraging others to do the same, I’m trying my best to disrupt this push for a mass-minded power capable of possibly changing the very war I fight with all my breath.

You know what moved me today? poem, a songa bit of writing, a shared picturespoken words, a giggle, a new story. That’s what moved me today. They won’t move the world, but they moved me.