Categories
RDF

RDF: Binary XML

Recovered from the Wayback Machine.

Tim Bray has had a couple of essays on RDF, including an offer of a domain, RDF.net, to someone who invents an RDF tool he would like to use. I wonder if he likes poetry? I wonder if I’m interested in yet another domain?

Tim’s pushback isn’t against RDF, which he seems to like. His pushback centers on the serialization technique for RDF — RDF/XML.

He writes:

 

RDF has ignored what I consider to be the central lesson of the World Wide Web, the “View Source” lesson. The way the Web grew was, somebody pointed their browser at a URI, were impressed by what they saw, wondered “How’d they do that?”, hit View Source, and figured it out by trial and error.

This hasn’t happened and can’t happen with RDF, for two reasons. First of all, the killer app that would make you want to View Source hasn’t arrived. Second, if it had, nobody could possibly figure out what the source was trying to tell them. I don’t know how to fix the no-killer-apps problem, but I’m pretty sure it’s not worth trying until we fix the uglified-syntax problem.

It’s not surprising that there isn’t a killer app for RDF — though the specification has been around a long time, it’s also been in committee and under development almost the entire time. Now that we’re finally heading into what should be a stable RDF specification, I think we’ll start to see more and more applications such as MIT’s DSpace, RDF Gateway, Siderean Software’s Seamark, Plugged In’s Tucana KnowledgeStore, Mozilla and other applications that are based in some part on RDF.

As for the syntax being unreadable, which he reiterates today (“RDF/XML syntax, blecch”), Tim makes the statement that the concept of “View Source” is essential for any web-based specification or application to succeed. He writes:

 

The Web grew because people could generate it by hand, and did.

By this I assume he means that a person inexperienced with the technology can learn about it by viewing the source, as people learned about web page creation through viewing HTML.

I have to disagree with Tim on this. Sure, View Source is how people learned to create web pages, or to manually create simple repetitive XML such as that found in RSS files — but the concept falters when you look at the back-end mechanics that have made the Web truly viable. There is no “View Source” for Perl/CGI, or JSP, or ASP, or PHP pages. There is no “View Source” for the code for the Apache web server, or the protocols, or the browsers.

The web page is only one part of the web — the user interface. So much of the web is either compiled code, or text that requires training and experience in order to read and understand.

Did I learn HTML from View Source? Yup. However, when I work with JSP, I rarely view the generated Java classes because even though they support the application they aren’t meaningful for me. I do know Java, so I can look at them –it’s just that I have better things to do with my time. Did I learn how to code JSP by looking at existing JSP pages? Sometimes, but much of the knowledge came from looking at the documentation.

In addition, is the data in a Berkely DB or MySql database in a format easily read or written manually? Or do we use applications to access the data?

We need to stop treating RDF/XML as yet another variation of tags similiar to HTML and start looking at it as a form of virtual binary code — machine generated and consumed, but output in plain text. Until we do, we’ll never get to the point of creating that killer app that Tim wants.

My advice to Tim is reap the benefits of RDF from the applications I’m sure he’ll be inundated with, and treat the serialization format as another incomprehensible machine language that just happens to use angle brackets.

(Thanks to Sam for link to Tim’s articles. Also see Danny’s take.)

Categories
Writing

The wise person finds the simple path

Recovered from the Wayback Machine.

I picked up a couple of books from the library yesterday that I’d ordered based on their being mentioned in other weblogs. One was Le Ton beau de Marot: In Praise of the Music of Language by Douglas Hofstadter. I would give credit to the person who mentioned this, in either a posting or a comment, but I can’t remember exactly where I heard of this book; the people I read tend to drop titles as frequently as Hantzel and Gretel dropped bread crumbs, and for about the same reason — to mark a path.

Well, if you recognize yourself as the person, give yourself a bow, because this book is an absolute delight. Here is a person, Hofstadter, discussing the principles of translation based on a small French poem, but doing so in a manner that is both engaging as well as enlightening. Rather than make the topic more complex and obscure, he simplifies, and in the process creates something infinitely richer.

In the introduction, Hofstadter discusses his obsession with controlling the layout and format of the published book, not just the content. He writes:

 

I know this sounds quite nutty, but it is me to the core. This is my style at its more pure, and, I must say, at its most joyous. Paradoxical thought it surely sounds, I feel at my freest, my most exuberant, and my most creative when operating under a set of heavy self-imposed constraints. I suspect that the welcoming of constraints is, at bottom, the deepest secret of creativity — and that, of course, is why poetry, building on a foundation of constraints, is so central to this book. Translation, too, is a dense fabric of constraints — and thus, needless, to say, the merging of translation with poetry gives rise to such a rich mesh of interlocking constraints that the mind goes a bit berserk in a mixture of frustration of delight.

I’ll relate just one example of the strangely twisty effects of my many self-composed constraints. Early on, I decided, just for the fun of it, to begin each chapter with a bit of a flourish — a few large letters that grandually would shirnk down to the size of the normal text. I soon realized that I had to avoid descenders in those first few letters — in other words, no “g”, no “y”, and so forth — in order to prevent collisions with letters just below. Well, this tiny constraint had quite a big effect in the case of Chapter 2.

An early draft of the chapters started out with a word that had a letter with a descender in it, and my search for a way to reword that first sentence to get rid of the lone descender led to a totally unexpected, unplanned style for that paragraph, which set a distinct opening tone for the chapter, which led to a curiously assonant three-word section head, which then suggested to me the idea of repeating that three-word pattern for all of the section heads in the chapter, and then the various section heads that I created in the appealing mold of that pattern would up exerting a considerable influence on what I actually said in the sections that they headed. Thust the trivial avoidance of one descender in the first five letters had a major impact on the ideas expressed in that chapter. Though this may seem bizarre, it is in fact absolutely typical. It is one of the more easily explained examples, but is not exceptional.

I was charmed by Hofstadster’s admission of this fact — I wonder how many writers would? — but I was hooked when he used ‘twisty’.

The book is ostensibly about the experience and effort of translating one small French poem. I don’t know French, nor is it a topic of particular interest; and my knowledge of poetry is limited. But from the first I was engaged and now can’t wait to finish the book. On a topic I have little interest in. Can you think of a higher compliment to give a writer?

I started this post last night, but left the finishing it to today. This morning, while doing my weblog reading, I found this at Loren’s about the poet Ezra Pound:

 

As I read the Cantos, I constantly wondered whom Pound considered his audience. I’ve had seven years of college English, with a focus on poetry. I’ve had two grad-level courses in Chinese Literature taught by a brilliant Korean professor. I’ve read a wide range of poetry for over twenty years. Yet, I felt totally inadequate when faced with the Cantos. Who, then, did Pound think would read his poem? Did he really expect anyone to be cognizant of all the literary influences found in the poems? Or did he think that, like a prophet, scribes would meticulously study his poems for years, annotating them so that the faithful could begin to truly comprehend his message? At the very least, the poem seems directed at a small, elite group of artist-scholars who believed, as Pound apparently did, that the great poets are seers.

The small, elite group.

I respect the need for any scholar to communicate with those of like mind in order to increase the base of knowledge. But I reserve my highest acclaim for the person who can write something like “Postmodernism for Dummies”, without condescending to the audience, or lessening the topic.

 

 

Categories
Just Shelley

The wise person finds the simple path

I picked up a couple of books from the library yesterday that I’d ordered based on their being mentioned in other weblogs. One was Le Ton beau de Marot: In Praise of the Music of Language by Douglas Hofstadter. I would give credit to the person who mentioned this, in either a posting or a comment, but I can’t remember exactly where I heard of this book; the people I read tend to drop titles as frequently as Hantzel and Gretel dropped breadcrumbs, and for the same reason — to mark a path.

Well, if you recognize yourself as the person, give yourself a bow, because this book is an absolute delight. Here is a person, Hofstadter, discussing the principles of translation based on a small French poem, but doing so in a manner that is both engaging as well as enlightening. Rather than make the topic more complex and obscure, he simplifies, and in the process creates something infinitely richer.

In the introduction, Hofstadter discusses his obsession with controlling the layout and format of the published book, not just the content. He writes:

I know this sounds quite nutty, but it is me to the core. This is my style at its more pure, and, I must say, at its most joyous. Paradoxical thought it surely sounds, I feel at my freest, my most exuberant, and my most creative when operating under a set of heavy self-imposed constraints. I suspect that the welcoming of constraints is, at bottom, the deepest secret of creativity — and that, of course, is why poetry, building on a foundation of constraints, is so central to this book. Translation, too, is a dense fabric of constraints — and thus, needless, to say, the merging of translation with poetry gives rise to such a rich mesh of interlocking constraints that the mind goes a bit berserk in a mixture of frustration of delight.

I’ll relate just one example of the strangely twisty effects of my many self-composed constraints. Early on, I decided, just for the fun of it, to begin each chapter with a bit of a flourish — a few large letters that grandually would shirnk down to the size of the normal text. I soon realized that I had to avoid descenders in those first few letters — in other words, no “g”, no “y”, and so forth — in order to prevent collisions with letters just below. Well, this tiny constraint had quite a big effect in the case of Chapter 2.

An early draft of the chapters started out with a word that had a letter with a descender in it, and my search for a way to reword that first sentence to get rid of the lone descender led to a totally unexpected, unplanned style for that paragraph, which set a distinct opening tone for the chapter, which led to a curiously assonant three-word section head, which then suggested to me the idea of repeating that three-word pattern for all of the section heads in the chapter, and then the various section heads that I created in the appealing mold of that pattern would up exerting a considerable influence on what I actually said in the sections that they headed. Thust the trivial avoidance of one descender in the first five letters had a major impact on the ideas expressed in that chapter. Though this may seem bizarre, it is in fact absolutely typical. It is one of the more easily explained examples, but is not exceptional.

I was charmed by Hofstadster’s admission of this fact — I wonder how many writers would? — but I was hooked when he used ‘twisty’.

The book is ostensibly about the experience and effort of translating one small French poem. I don’t know French, nor is it a topic of particular interest; and my knowledge of poetry is limited. But from the first, I was engaged and now can’t wait to finish the book. On a topic I have little interest in. Can you think of a higher compliment to give a writer?

I started this post last night but left the finishing it to today. This morning, while doing my weblog reading, I found this at Loren’s about the poet Ezra Pound:

As I read the Cantos, I constantly wondered whom Pound considered his audience. I’ve had seven years of college English, with a focus on poetry. I’ve had two grad-level courses in Chinese Literature taught by a brilliant Korean professor. I’ve read a wide range of poetry for over twenty years. Yet, I felt totally inadequate when faced with the Cantos. Who, then, did Pound think would read his poem? Did he really expect anyone to be cognizant of all the literary influences found in the poems? Or did he think that, like a prophet, scribes would meticulously study his poems for years, annotating them so that the faithful could begin to truly comprehend his message? At the very least, the poem seems directed at a small, elite group of artist-scholars who believed, as Pound apparently did, that the great poets are seers.

The small, elite group.

I respect the need for any scholar to communicate with those of like mind in order to increase the base of knowledge. But I reserve my highest acclaim for the person who can write something like “Postmodernism for Dummies”, without condescending to the audience, or lessen the topic.

Archived with comments at the Wayback Machine

Categories
Diversity

Women in IT Stuff

Recovered from the Wayback machine.

update

This discussion in Kevin’s comments has quickly degenerated into how women and men are different, physically, and how women can’t do math and engineering. I would stay to uphold the fight against this attitude, but I have to go to work. Doing the thing I should not be able to do, being a woman and not having the brain for the work.

Earlier

Kevin Drum, aka Calpundit, reflected on an article out today in the LA Times about the lack of women in IT, saying it reminded him of the previous writing I did, Outside even among the Outsiders. He writes:

I imagine this is at least part of the reason for the relative lack of women in IT: they feel enormously pressured by the obsessive, almost semi-autistic nature of some of their prospective IT colleagues. In most of the IT groups that I’ve been involved with, you have to be willing to engage in rhetorical near-war in order to be heard, and you have to put up with challenges to your ideas that are so aggressive, so intense, and so basically anti-social that it’s almost impossible not to take them as personal affronts.

I have seen this aggressive behavior, frequently, in IT. However, as one person mentioned in the comments attached to Kevin’s post, women in IT can also demonstrate this same aggressive behavior. Perhaps it has something to do with getting instant obedience from our computers, and demanding the same from those we work with?

I do know that IT is very competitive, a culture I think that originated with the early computer people, part of the older scientific community’s need to prove my brain is bigger than yours. This competition is probably responsible for 80% of our innovation. However, it’s also probably responsible for 80% of our inability to agree on standards, as well as 80% of application development failures.

Anyway, interesting and thoughtful post and discussion at Kevin’s on this topic.

Categories
Just Shelley Weblogging

Happily Busy

Just a ramble:

Had a grand celebration meal with roommate last night: caesar salad and prime rib rubbed with seasons and lightly grilled, accompanied by margaritas made with Sauza Tres Generaciones Anejo tequila and Grand Marnier.

Since I start my new job tomorrow, I am happily busy today, though I hope to get out for a nice walk later. Lest you all think my walking will be drastically curtailed once I start working, my new office location is in the midst of parks with over 16 miles of trailway, rough and paved. If anything, I think I’ll be walking more, not less.

With such a quick start date, I only have one day to break some of my bad habits. For instance, tomorrow when I wake up, I must immediately put on clothes rather than around the home flops. And when I’m working on the computer, I must stop talking to it. I especially must not sing to it.

I also need to get my butt in gear and finish installing the software on the new server, disabling root access, enabling FTP and so on. For some odd reason, this has all become that much more enjoyable now.

We moved the Renaissance Web discussion group to a JournURL site, but aren’t quite sure who made the move over with us. Rick Thomas and I had a lovely discussion about the Semantic Web and Natural Language, including Poetry Finder, and he promised to return in a couple of days with talk about organic semantics.

Speaking of technology, I may be spinning the semantic web posts, including RDF for Poets and the Finder, to a separate weblog again. Hard to say, but I am all enthused to branch out and have fun again.

And speaking of fun: evil twin’s having fun in the comments in Farrago’s (Lynette’s) new experimental photo blog. She be teaching the twin how to make sisterfritters.