Categories
Political

Please invade this city

Recovered from the Wayback Machine.

The President focused his weekly radio address on Iraq and the need to remove Saddam Hussein. He also issued promises to the Iraqi people that he will not leave them to suffer from this war:

Rebuilding Iraq will require a sustained commitment from many nations, including our own. We will remain in Iraq as long as necessary, and not a day more.

He equates the situation in Iraq to that of Japan and Germany following World War II. All that’s needed is for us to enter Iraq, with or without the UN, and this country, too, will soon be on its way to prosperity and peace:

America has made and kept this kind of commitment before – in the peace that followed World War II. After defeating enemies, we did not leave behind occupying armies; we left constitutions and parliaments. We did not leave behind permanent foes; we found new friends and allies.

As part of the requirements for a modern history class I took in college, the professor gave us an assignment to interview two people from the period of time we were most interested in. My focus in that class was on World War II and I interviewed my father, who had been part of the 82nd Airborne. I also interviewed Frank Turner, my sociology teacher who had lied about his age and fought during the end of the war, serving as part of the occupational forces.

During the interview, Frank told me about one event in particular. He was riding on a train that also contained food and canned milk destined for occupation forces and their families. At a stop along the way there was a large crowd of people from the surrounding communities, all hungry, all seeking help from the occupation forces. The crowd begged the soldiers for food or milk for their children, and pressed in against the train. In the panic, the soldiers fired, both into the air and into the crowd.

Frank told me that he didn’t see anyone killed. He didn’t believe anyone was killed.

There are so many differences between the situation in Germany and Japan at the end of World War II, and an invasion of Iraq today, that to compare the two situations is ludicrous. Both Germany and Japan had been aggressors in a war that involved the world. The US involvement in the occupation of both Germany and Japan not only had the support of all the allies and other countries, but most of the people in these countries, too.

John Dower, who wrote the book, “Embracing Defeat: Japan in the Wake of World War II”, has denied any similarity between Japan post World War II and the Iraq of today. In an opinion he wrote for the New York Time in October last year, Dower said:

Contrary to what self-anointed “realists” seem to be suggesting today, however, most of the factors that contributed to the success of nation-building in occupied Japan would be absent in an Iraq militarily defeated by the United States.

When war ended in 1945, the United States-dominated occupation of Japan had enormous moral as well as legal legitimacy in the eyes of the rest of the world. This was certainly true throughout Asia, so recently savaged by the Japanese war machine. It was true among America’s European allies as well. There was a level of unequivocal regional and global support that a projected United States war against Saddam Hussein does not enjoy.

The occupation also had legitimacy in the eyes of almost all Japanese. The Japanese government formally accepted this when it surrendered. Emperor Hirohito, great weather-vane that he was, gave his significant personal endorsement to the conquerors. And Japanese at all levels of society quickly blamed their own militaristic leaders for having initiated a miserable, unwinnable war. Saddam Hussein will never morph into a Hirohito figure, and a pre-emptive war will surely alienate great numbers of Iraqis, even many who might otherwise welcome Mr. Hussein’s removal.

We are different from the America of long ago. Back then we were a country fresh from victory in a difficult war. We could afford to be compassionate because we had seen for ourselves the terrible price the Japanese paid for their invasion of Pearl Harbor, and the Germans paid for their aggression. We, who did not suffer the damages of most of the our allies, urged reform and pushed to bring about self-rule. As Dower wrote:

The great legal and institutional reforms that continue to define Japanese democracy today reflected liberal New Deal policies that now seem testimony to a bygone age: land reform that eliminated widespread rural tenancy at a stroke; serious encouragement of organized labor; the drafting of a new constitution that not only outlawed belligerence by the state, but also guaranteed an extremely progressive range of civil rights to all citizens; restructuring of schools and rewriting of textbooks; revision of both the civil and penal codes, and so on. It is hard to imagine today’s “realists” making this sort of lasting, progressive agenda their primary concern.

Japan has been strongly supportive of the US in its plans for an invasion of Iraq, and even sees itself being part of the postwar forces, a bit of irony if there is one. However, when one considers that one of the countries most vehemently against a US-based invasion of Iraq is Germany, the other ‘poster child’ of American occupational benevolence, one has to wonder exactly who the President is trying to convince with this eleventh hour urgency to help the Iraqi people?

However, if its true that the President will provide help to the people of a region after an invasion than I have a request for Mr. Bush: invade us.

California just updated its unemployment rates to find out that the earlier estimates of the unemployed were off by as much as 150%. This only adds to the general fear about jobs in this country. Petroleum prices are rising, and more and more people can’t afford to buy the medicine they need. To bad some of the money going for unwanted smallpox vaccinations couldn’t be used to help the people who are dying now.

Even Armani is feeling the pinch as fashion sales decline due to a the continuing discussion of war. Today’s new pink is definitely not orange.

If the only way that we the people of this country can get the attention of our president is to be invaded then so be it. Mr. President, please invade St. Louis. We need your help.

Categories
RDF Writing

Mardi Gras Blues

I had hoped to attend the Captain Morgan Mardi Gras parade, but this flu seems to be quite partial to my body, and has decided to take an extended vacation among my various crevices. Right now, I believe it’s paying a protracted visit to my lungs and throat. However, I have high hopes of making it to the traditional Mardi Gras parade Tuesday night, flu or not.

I am determined to pick up one strand of genuine Mardi Gras beads. Just one. Hopefully I won’t have to flash a breast to achieve it.

The enforced stay at home has been productive from a book stand point. I’m finishing up the first round edits in preparation for the chapters being reviewed one more time by a ’subject matter expert’, and then to my editor for the final edits and pre-production readiness.

If you’re interested, I just posted a note about the process in more detail, as well as an HTML version of the first chapter, in the book weblog. The chapter still needs some editing but it’s getting there.

In the edited introductory chapter, I put more focus on the purpose of the book, as well as the section on when to use RDF/XML and when to stay with straight XML. I also incorporated information that explains my interest in RDF/XML.

If I have any edge at all with writing about RDF/XML, it’s that I come from a politically neutral position in the battle between the semantic web folks on one end and the markup folks on the other. I’m neither semantic web nor markup; I’m a data person, with many years of experience working with data at different levels and for different companies. Because of this neutrality, I think I can safely represent all interests or biases in the material. Or perhaps a better way of saying this is: I piss everyone off equally.

But, you know, I can live with this.

Besides, people haven’t necessarily been beating down the doors to write books on RDF. If you go out to Amazon and search on the term ‘RDF’ only a few books get pulled up, and they haven’t been exactly flying off the shelves. Of course, this will change when my book comes out and all of you go out and buy your copies of the book. And, no, Amazon still hasn’t corrected the author list, removing Ray as a co-author. I told you his name would be there forever. Grrr.

As usual when I mention the book, I have to again send kudos to Simon St. Laurent, my editor. This last week he helped me deal with the rather detailed criticism of the book I received from some of my reviewers – something that’s not always easy for an author to absorb.

Simon is what is known in our industry as and a Good Man and a Very Cool Dude. I owe him a box of my favorite chocolates – as soon as I get my advance and can pay for it. Or maybe I should send him a box of Tim Tams?

There’s a funny story associated with the list of books at Amazon on RDF. If you look at this one you’ll see that it’s ‘authored’ by Dan Brickley. The story behind this is that the publisher grabbed the W3C specifications, which were, I believe, public domain or at least allowed this type of re-publication, and then did nothing more than reprint them in the book, exactly. They plunked Dan Brickley’s name on it since he was one of the co-authors of the original specification. This action pissed Mr. Brickley off quite a bit, as you can imagine.

Cheesy thing to do? Damn right it was. But also an excellent example of what can happen to material once it’s in the public domain.

Categories
Weblogging

From the ashes came the re-born, born dying

Recovered from the Wayback Machine.

I have to return to Baldur’s posting, Death of the Blogger, and his discussions about the dangers of memes, those Thought-viruses, which have undermined the craft of academia (referencing, research, analysis and debate) and doomed most of academic practice into irrelevance. The same memes that Baldur sees threatening weblogging:

 

The meme-plague is the only thing which can destroy the weblogging revolution, murder it in its tracks.

 

However, it’s difficult to figure out how to proceed, because even a rejection of memes becomes a meme itself over time.

Last year we waged a battle to pull weblogging out from under the link-and-comment crowd, and breath fresh life into it by opening the doors to communication. I pushed comments and trackback as deligently as any dealer on the corner selling crack. I was joined by others just as interested in establishing a community online, and we have succeeded. Sticky Strands are here to stay.

I write, and Scott comments, and then Dan comments, and possibly MarkKarl writes in response, and Liz, and Phil reply and various folks chime it, and it’s all Good. The community that grows up around the conversation isn’t exclusive, as anyone can trackback to the posts, anyone can comment. We are self-forming.

Power to the People. If we didn’t topple the empire built on the Link-and-Comment, we at least irritated it enough to be noticed. “Hiya! Just passing through. Don’t mind us. Continue doing whatever, hmm, it is, ah, that you’re doing. I’m sure it’s all very interesting…to someone.”

We dripped scorn as we enabled the technology to build the neighborhoods. We raised our lips everytime someone introduced a quiz. We lapped up the media spotlight. We googled and daypopped. We brought up ‘cat’ as our secret insider joke, and it was funny.

It’s still funny. Cat. Cat. Cat.

Cracks me up.

We asked each other questions and we debated on topics small and large, and with the same level of ernestness regardless of whether the topic was the new Movable Type release, Creative Commons licenses, sexism, Postmodernism, the beauty of ugliness, or the War in Iraq. And we are eloquent, and learned, and profound, and well written of that I have no doubt. I am surrounded by people who are, in a benevolent sense, scary-smart.

Still, too much of anything is not a good thing and it seems lately, as if we’re all stuck in the strands, caught in the web of our weaving. I look back on my recent posts and find that lately all I talk about is weblogging, and all I’ve done is link and comment.

See! I’m doing it again!

Perhaps we laughed at the old school too soon. Perhaps the Original Meme of Weblogging, like the Original Sin of Man, still exists, but has gone underground.

Lately, when I stumble across a weblog posting that writes in-depth on something of personal interest to the author but completely unrelated to whatever is the ‘hot topics’ of the day, I just sit and savor it as an unexpected treat. Treat? It’s as if the more we communicate, the less original writing there is. We’ve become those people at parties, you know the type; the ones who in the interests of making sure someone isn’t left out, holler out to the person standing in the corner, “Hey, get your butt over here. Join the conversation!”

But what if the person in the corner prefers to be in the corner? What if they don’t want to join the conversation. What if I don’t want to respond in comments? What if you don’t want to join the cross-weblog conversation? Whatever happened to the tales of Korea, and the story of World War II? Whatever happened to the simple discussions about personal belief, and the stories from our youth? What if today, I want to write about a river flowing past a field and under a bridge in the dead of winter?

When did communication go from being something shared and warm and glorious to something dutiful and required, like sex between a couple after the love is gone?

But, but, there’s always the but…

It is the communication between us that makes the writing that much more special. I can read absolutely beautiful things from someone I don’t know, and be moved by them. But when people I’ve come to know write beautiful things, it becomes that much more personal and special.

I was never one for poetry because poems seemed so intellectual and my roots as a high school drop out are never very far. Yet through Loren’s gentle introduction to the poets he loves, I have found not only a new appreciation for poetry, but an actual liking for it; not one based on trying to impress anyone, but based on sheer joy in the music and artistry of the words. Without meaning to put Loren to the blush (but then, embarrassing people has never stopped me in the past), I can’t speak for his previous students, but he made an impact on a 40-ish unemployed computer consultant who writes technical books and hikes a bit.

No matter the skill and the introduction, I never would have looked at Loren’s writing and the poetry if I hadn’t ‘met’ Loren through comments and cross-blog discussions. I would have seen the poetry and tuned out, instantly. The same can be said on so many topics I’ve been exposed to, from movies, to books, to marketing, to religion, and yes, even postmodernism.

The Meme bring. The Meme taketh away.

Jeremy Zawodny recently wrote a posting called The 10 Habits of Highly Annoying Bloggers, which, as you can imagine quickly went from “posting” to “meme” status. As would be expected with this type of posting, much of the humor attached to it appears in the comments, which is as it should be. Other than wondering what a ‘FontBitch’ was, and deciding to use this as my ‘about me’ link, it was the survey that Eric’s Weblog posted about the 10 habits that truly fascinated me. This survey allows people to ‘vote’ on which of the habits is most significant to them.

According to this survey, people were vastly more annoyed by the mechancs of weblogging, such as comments, RSS, font size, and the about page, then they were about the person providing original content. Original writing lost out to FontBitch and comments, RSS and “about me”

I have seen the Meme, and it is us.

Which leads me back to Baldur’s posting and the discussion of memes and original writing. I wrote a great deal in this posting, much more than the …short volleys of 80 word meme brain-boils where the thought-virus biomass simmers under the thin skin of comments and trackbacks. However, I’ve only referenced Baldur’s writing at the very beginning and the very end. And this was supposed to be about Baldur’s posting. And it is.

 


photo of river in winter
 

 

 

Categories
Political

Can’t sleep might as well write

I gave up trying to sleep and since I was in a writing mood I thought I would put my sleeplessness to good effect. Besides, I forgot to mention that I was interviewed by Newsweek yesterday for a story on weblogging.

(Of course the interview was for a story on weblogging. Did you think that Newsweek would be interviewing me for my views on the President? The Iraqi war? The current domestic situation in the country?)

The reporter was writing a story for an international edition of Newsweek, European I believe, about weblogging and how to start a weblog. He found me through the Essential Blogging book and when he asked about ‘blogging etiquette’ I knew I wasn’t the only weblogger interviewed. The term ‘etiquette’ was a dead giveaway.

I laughed when he asked that question, which probably lessened my chances of appearing in the interview. (I’ve been interviewed for major publications before, and have had my sound bites left lying on the cutting room floor.) Still, etiquette.

I told him that the reason we’re weblogging is because we want to be able to publish online without having to follow any rules. To be independent. Free thinkers and writers — as long as we write in reverse chronological order, provide perma-links, link to interesting stories or other weblogs, comment on same, attribute other sources, never delete postings, maintain archives, write only the truth, have a blogroll, and never write about cats or what we had for lunch, we can weblog anyway we want.

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.