Categories
People Writing

The Turbulent Waters of Families and Writing

In my trip last week, I started out with no specific destination — just a general need to get out on the road, have some time to myself, to think. I first thought about heading to Boston, but decided Spring is a better time to visit the East, so I headed west. I then thought about traveling through Canada, even driving to Alaska; however, I had forgotten my passport and supposedly you can’t re-enter the country now without showing proof of native birth or citizenship papers.

Ultimately, I found myself heading to Sandpoint, Idaho, the place that I’m sure was at the back of my mind during all my traveling decisions. Mom’s new home.

It has been years since I had seen my mother, though we talk relatively often on the phone. She hasn’t changed much, though I notice that she still starts drinking at 9:00 in the morning. Since this wasn’t anything new, and I was no longer dependent on her driving me anywhere, her early drinking was nothing for me to remark on.

Monday night Mom and I were home alone, planning on a visit to Kettle Falls the next day. Somehow the conversation veered about to Mom’s various boyfriends in the past, both the good and the bad. I really liked Jim, a forestry service employee who was comfortable and caring for I and my brother. However, Mom really liked Hernando, a Columbian bi-sexual child abuser with a brother who had a very dubious profession of “emerald importer”. Yeah, emerald importer.

Since Mom had been gently tippling all day, she was particularly garrulous about her various boyfriends, and her divorce from my father, her disastrous second marriage and violent divorce from Knut. The same Knut who would later go to prison for throwing his second wife down a set of stairs in an attempt to kill her.

During our talk, I told Mom that I was writing a book, a book about my childhood, our hometown, coming of age. We discussed some of the things I would include. I wasn’t asking permission to write these things — I was informing her of my intent. By the end of the evening I had made a decision to return to St. Louis the next day. We hugged good-bye the next morning, in mutual though uneasy accord.

Since family and writing were on my mind when I returned home, I was surprised when I read about Mike Golby’s difficulties with his family and his own writing. My first reaction was to say, “write what you want Mike, and damn the consequences”, but that’s a quick response, without a lot of thought.

Regardless of the genre or the story, the best writing always has a kernel of the writer’s life in their work. Even forms of writing such as science fiction encompass human emotions and every day events, connecting the reader to the story by placing the familiar within unfamiliar and outlandish settings.

How much the writer exposes themselves and their lives in their work is dependent on how much this exposure adds to the writing. Writing a throwaway statement that one’s girlfriend is on drugs or brother cheats on his taxes is nothing more than cheap sensationalism at the expense of others. However, exposing real pain and difficulty, in carefully considered phrases, with the express purpose of drawing the reader in with the words — this isn’t sensationalism, this is art. The truest form of art. The most difficult form of art.

Mike Golby writes about his family, the effects of alcohol abuse, his wife’s rape. Uncompromising subjects exposed to the metal. No fade away into black, no wind ruffling the curtains of the windows. This displeases his family. No, this angers his family, and they want him to stop.

In response, several weblogging neighbors of Mike have talked about the issue of families, and writing (well, weblogging but to me they’re one and the same). Dorothea wrote:

 

Blogging threatens such families for the same reasons it threatens PR-dependent corporations. It threatens the fiction, the public façade of perfection, the private walls around anger and pain and disagreement and error.

 

Jonathon continued this thought, focusing on society’s insistence on portraying families in a sentimental manner:

 

I’m not suggesting that happy families are impossible, or even unusual. Rather I’m protesting a pervasive myth based on what Dorothea Salo calls “clichés and polite fictions.” Nor am I saying there’s no room at all for sentimental depictions of the happy family but we live in cultures that—proportionately—offer hardly anything else: not just things that are “not entirely true” but things that are manifestly false. It’s this preponderance of family kitsch that makes a weblog like Mike Golby’s so precious. In Blogaria, most everybody aspires to be a journalist. Artists are distressingly rare.

 

AKMA continues Jonathon’s disagreement with Mike’s concern about free speechwriting:

 

Like Jonathon, I demur at the suggestion that Mike’s “right to free speech” warrants our support and intervention. I’m amenable to free speech, by all means, but (again, as Jonathon points out) the heart of the matter here concerns not Mike’s rights, but his practice of honesty (well, allowing for some occasional exaggeration). Where convention dictates that people pretend that the domestic relations of every family are jolly, cheery, polite, affectionate, sober, chaste, responsible, and commendable in every respect, Mike reminded us that few families actually live out that sentimental myth (Jonathon was right about “sentimentality,” too).

 

Not being a sentimental person, or having come from what one could term a ‘traditionally happy family’, I can agree with Dorothea, Jonathon, and AKMA; about sentiment, family, and honesty in writing.

However, I also agree with Loren when he writes:

 

Jonathon suggests the role of art is to show the truth about life, to strip away sentimentality, but I would argue that revealing the “truth” in this sense is only one aspect of art. An equally important role is to show what life “can be,” to hold up models of what we want our lives to become.

I would argue that both are real, and both are the domain of the true artist. The artist does not have to choose one or the other to be an “artist,” though contemporary art critics certainly seem to have come down on the side of angst and despair. Emphasizing one at the expense of the other, though, seems to be a distortion of reality, a distortion of truth, whatever that might be.

 

Perhaps the issue is more of rejecting that which is mawkish and maudlin, embracing instead fond reminisces and a hopeful disposition. (Though I’m not sure how fondly reminiscent or hopeful I am of Loren’s use of the phrase “pulling a Shelley” to denote putting one’s foot in one mouth.)

Mike, eloquence escapes me and I’m fresh out of the profound. I’m left with my original advice: write whatever you want, and to hell with the consequences.

 

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
Just Shelley

The Pend Oreille Loop

Recovered from the Wayback Machine.

Through an afternoon spent fighting torrential rains and aggressive truckers, I’m finally in my own comfy chair, computer on lap, and — wonders! — an internet connection. A week of not being connected, and my emails are still downloading. Hopefully I won’t accidentally delete anything important.

This last week I drove from Missouri to Illinois to Wisconsin to Minnesota to North Dakota to Montana and finally to Sandpoint Idaho, located on Pend Oreille (pronounced “ponderay”) lake, the Northwest’s largest lake. Sandpoint also happens to be my mother’s new home, the turn about point of my trip. Along the way I spent some time in Theodore Roosevelt National Park in North Dakota, home of the Bad Lands.

The trip out was lovely: uncrowded roads, great weather, terrific views, and friendly fellow travelers at breakfast in hotels/inns where I stayed.

On the return I went from Idaho to Montana to Wyoming to South Dakota to Iowa to Missouri. And hit storms almost the entire way except for the start of this day in South Dakota. Driving in the rain is fun; driving in storms with flooded roads and 60 MPH winds leaves a bit to be desired. Still, if one can specify no challenges, it wouldn’t be an adventure, would it?

I have a few stories to tell, nothing exciting. And I have a few photos to show, starting with these here. However, I have email to read, and other weblogs to catch up on. Not to mention the comments attached to the RDF posting (my, my, looks like lots of fun occurred there). Tomorrow.

Old Cabin in Field – North Dakota

Badlands

Badlands 2

Buffalo

Castle Rock – Wisconsin

Castle Rock Path

Montana Cabin

Categories
Places

Road Trip

Recovered from the Wayback Machine.

From this hour I ordain myself loos’d of limits and imaginary lines,
Going where I list, my own master total and absolute,
Listening to others, considering well what they say,
Pausing, searching, receiving, contemplating,
Gently, but with undeniable will, divesting myself of the holds that would hold me.
I inhale great draughts of space,
The east and the west are mine, and the north and the south are mine.

Walt Whitman, Song of the Open Road

In the morning I begin another one of my road trips, except this time I have no particular destination in mind, and journey for no purpose other than the feel of the road beneath my wheels. I’ll most likely be starting a new contract soon, and wanted to grab one more adventure before settling in behind cubical walls.

I promise copious photos and interesting stories from my (paper) journal when I return.

In the meantime, I owe some answers about RDF to some folks, as well as a couple of book reviews. I just finished the RDF posting, and I’m going to try for one of the reviews, but the other, on Geek Love will never occur, I’m afraid. I found I could not finish the book.

Geek Love is a story that’s based on the human drama, played out in a circus sideshow. Unfortunately, since I was a small child, I’ve always hated sideshows, freakshows, anything of this nature. I can’t stand Ripley’s Believe It or Not, and positively loath Ye Olde Curiosity Shoppe in Seattle. I once watched the Movie Freaks when I was younger, and had nightmares for months.

I have no doubt that Geek Love is wonderfully written — the reviews of it are incredible. But the subject defeats me, and I must apologetically and regretfully return the book to the library. Denise, sorry!

TTFN

Categories
Semantics Technology

RDF: As simple as A, B, C

When I demonstrated a very simplified RDF/RSS model last week, in the comments attached to the post, Ziv asked the following question:

One question of an RDF newbie: Why do we need that (rdf:Description) element? Why can’t we simply put the @rdf:about attribute on the (item)?

As I started to answer the question in the comments, I kept finding myself taking the question deeper and deeper into the meanings of RDF:

-The rdf:about attribute can’t be used directly on a property led to

-The RDF/XML follows a striped XML syntax of class/property/class/property, regardless of shortcuts led to

-The striped XML syntax is based on the pattern of node-edge-node in RDF led to

-The node-edge-node of RDF is based on a model

All of which led me to a truly definitive question about RDF — why? Why the use of rdf:about here rather than there. Why the syntax? Why the model? After all, XML is a piece of cake — an element here, an attribute there, slam dunk in some text and hey now, we got data. Why make things more complex than they need to be?

Why? Because XML is great about collecting data but is lousy about recording knowledge. There is no facility inherent within the plain vanilla flavor of XML that allows one to write or read assertions in such a way that these assertions (read this as ‘statements’) can be machine produced and machine-readable. And the machines need all the help they can get.

We humans don’t need a rigorous model to communicate. We have phonemes that form words that make up a vocabulary, members of which are then used to form sentences through the use of this really irritating set of rules called “grammar”. We’re programmed to apply these rules through years of instruction, using a neural networking technique called ‘education’. When programming is finished, and after passing certain quality assurance tests, we’re set upon the world. Once loosed from the constraints of the lab, we promptly and as quickly as possible throw out much of what we’ve learned in favor of imagination, creativity, and a dangerous little nugget called innovation.

I love it.

Dorothea wants to discuss her specific mindset related to ‘sexism’ and the concept of sexiness and uses a new word: grunch. This word doesn’t exist, but we as humans adapt to it, add it to our vocabulary (phonemes: grrr + unch). In future writings based on Dorothea’s original discussion, we know what grunch is. Humans adapt.

In 1986, Hans Gabler made 2000 ‘corrections’ to James Joyce’s Ulysses. Well, thank goodness he did because nobody read it the way it was, all those grammatical errors and typos kept getting in the way. Most likely no one even heard of this book until Mr. Gabler took it in hand. As grateful as I am, though, I have recently discovered an even better re-write of this classic: Ulysses for Dummies.

I digress. XML and RDF.

With XML I can record pieces of data such as date, an excerpt, a title, author, category and so on. The structure of the markup allows machines to read these individual facts, to verify that the recording meets certain simple rules. But what if I want a little more than just plain facts. What if I want to be able to take these facts out for a spin, kick the tires, check under the hood?

I have a web page. Facts about this page are: title, URL, date edited, category, and author.

Page has title. Page has URL. Page has edit date. Page has author.

Tarzan has Jane. Jane has Cheeta. Cheeta has banana. A pattern is beginning to emerge.

Every sentence has a subject and a predicate. The subject is the focus of the sentence, and the predicate says something about the subject. These two basic components work remarkably well in allowing us to communicate, to share amazingly complex knowledge.

Returning to RDF and XML, using straight XML is equivalent to only allowing communication with one verb — To Have. Following this, an XML translation of the previous paragraph would be:

Sentence has subject. Sentence has predicate. Sentence has focus. Subject has focus. Predicate has information. Subject has information. Predicate has subject. Components have power. Communication has components. We have each other.

As you can see, after a time, the simplicity breaks down — we need to increase our capabilities, even though doing so adds complexity.

Enter RDF, providing a structure and a meta-language to XML, a grammar if you will.

RDF has one pattern: (subject)(predicate)(object). However, this pattern gives us the tools to record data in such a way that knowledge can be inferred mechanically, merged via a well understood and defined logic with other knowledge, and so on. The subject is the noun, the focus of the statement; the predicate says something about the subject; the object is what is said.

Taking the test paragraph, it can be re-written into the following RDF-like statements:

(Sentence) (has a component)(which is a subject)
(Sentence) (has a component)(which is a predicate)

— no, no, don’t worry — it does get better

(The subject)(is the focus of)(the sentence)
(The subject)(is described by)(the predicate)
(Sentence Components)(enable)(communication)
(Sentence Components)(enable sharing)(of knowledge)

By providing the ability to record this subject-predicate-object pattern, RDF allows us to expand on the depth of information we gather. The more complex the information, the deeper the pattern is applied, but it is still this triple. In a graphical context, the subject-predicate-object form into a node-edge-node that allows us to build new statements on previously occurring ones.

The focus OF the sentence IS the subject DESCRIBED BY the predicate WHICH IS a component OF a sentence. Consider in this sentence that the predicates are the capitalized value, the graphical notation of this could be: node-predicate-node-predicate-node-predicate-node-predicate-node-predicate. Nothing more than a repetition of our friend the triple, connected end to end.

Representing this within XML requires a set of syntactic rules that ensure we don’t accidentally shove a predicate next to a predicate and so on. There are rules for how to identify a subject, and how to add a predicate. There are rules for how to repeat properties (predicate-object pairs), and how to group properties. There are even rules for how to create a statement about a statement (known in RDF as ‘reification’, though I prefer ‘RDF’s Big Ugly’, myself). But fundamentally the rules break down into nothing more than node-edge-node-edge-node, forming a particularly interesting XML pattern called The Striped RDF/XML syntax.

Rule’s that basically say that predicates can’t be nested directly beneath predicates (edges next to edges) or that whole node-edge-node thing gets blown out of the water. And rules that state when an rdf:about attribute can be applied. In my simplified RDF/RSS, the rdf:about attribute can’t be applied directly to the ITEM element because ITEM in this instance is acting as a predicate, with an implied URI of “item” — it can’t act as a new subject, too. Edge-edge.

So, with a little tweaking (adding the subject within a generic RDF resource statement, as in example 1, or using a shortcut as in example 2), the rules are met and the knowledge can be processed.

(Check out the example RDF files with the RDF Validator to see a graphical demonstration of node-edge-node.)

Once you’ve described one data set with these rules, interferences can be made to other data sets made with the same rules.

As an example, RSS is nothing more than a quick news blurb that gets consumed in less than 24 hours and doesn’t persist. The power of RDF isn’t necessary for RSS used by aggregators, primarily because the data doesn’t persist and one thing about the search for knowledge: it does require that the bits of the knowledge stick around long enough to be discovered.

However, RSS captures a rich set of information about a specific web page or weblog posting: the author and creation date, as well as category, and possibly even links to other resources. What a pity to put this into a form that will only be thrown away.

Well, who says it has to be thrown away? We’s all bosses here, we is. If I says to keep it, I’s boss, and you listen up or Bird be real angry, she will. Real angry. Hissy fit angry.

I modified my individual weblog posting archives to include a bit of RDF in the header that contains the same information used to produce the RSS files that aggregators so callously consume and toss aside. Since this modification was in the template, this RDF is generated for each page automatically. And once persisted in the archive page, it’s there for anyone to discover, providing a richer set of data than just that assumed with keywords pulled from the text.

In this RDF is an identification of the author, an entity which is rounded out by a FOAF (Friend-of-a-Friend) RDF file; knowledge of me, who I am, adds depth and categorization to my Book Recommendation list RDF, and so on and on — a vicious cycle of knowledge acquisition.

(Archived page and comments at Wayback Machine)