August 2003 Archives

Micah Dubinko

AddThis Social Bookmark Button

Related link: http://dubinko.info/writing/xforms/

XForms Essentials has been spotted in final printed form (pun intended) by a reader in Jackson, Tennessee.

I think it looks great…the quotations preceding each chapter are wonderful; shows true creativity–how on earth did you go about finding such appropriate quotations for each section?

Unlike many other books, you can see what you’re getting ahead of time. The full text of the book is up on my Web site. You can also order printed copies from there.

It’s been an amazing and fulfilling experience. -m

David A. Chappell

AddThis Social Bookmark Button

Related link: http://news.com.com/2100-1012_3-5069335.html?tag=fd_top

Check out the article on CNET today. IBM getting into the ESB market will most definitely help to legitimize the ESB as a technology category. I’m pretty psyched about it.
Dave

Simon St. Laurent

AddThis Social Bookmark Button

Related link: http://www.nytimes.com/2003/08/21/technology/circuits/21nett.html

Last week’s power blackout (not to mention recent worms) seems to have inspired some more critical coverage of the “network effects” whose positive impacts have become a mantra of tech business and politics.

First, we have the New York Times noting that:

last week’s blackout was vast precisely because of the interconnectedness that the network was meant to exploit and foster…. Taken together, the blackout and the worm underscore a far-reaching challenge in managing modern technological societies: the difficulty of reaping the benefits of networks - railroad networks, airline networks, telephone networks, power networks and computer networks, among others - while minimizing their vulnerabilities.

Then yesterday, over at Slate, Daniel Gross explores “the frailty, vulnerability, and age of the nation’s private energy networks.” Gross also explores the interconnectedness of our transportation and business networks, noting how the drive for efficiency (through centralized production and widespread distribution) comes with real costs.

I don’t think there’s a drastic change in the wind here, but it’s good to hear writers exploring the possibility that network effects aren’t all for the magically better.

Have you had to deal with the costs of network effects?

Simon St. Laurent

AddThis Social Bookmark Button

Related link: http://dannyayers.com/archives/001734.html

When we published Practical RDF last month, I had high hopes it would reach a lot of places. It never occurred to me that it might surface in the places Danny Ayers photographed. Remarkable.

Micah Dubinko

AddThis Social Bookmark Button

Related link: http://dubinko.info/writing/xforms/

My book, XForms Essentials, just went off to the printer. Writing a book has been an amazing experience. Here’s 10 things I’ve learned during the process:

10 Book-length writing is utterly different from writing shorter pieces. Like code, up-front design is worth every minute of investment. “Premature optimization” is evil, even in writing.

9 Straight-quotes vs. curly-quotes is the bane of technical writing.

8 Making your book available online before publication is a huge benefit for getting early feedback. I’d recommend it to anyone.

7 Writing a book proposal and getting a publisher to accept it can involve a substantial fraction of as much work as writing the book itself.

6 If you set up a private mailing list for your book, you will get some amazing and helpful responses. Treat your reviewers like royalty.

5 Your editor does a ton of work, but very little of it involves interrupting you. Your production editor, however, will have lots of small detail questions for you towards the end of the process.

4 When typing, I often leave off the las letter in a word without noticing it.

3 When negotiating a book contract, feel free to ask for changes in any unfavorable terms. You might get what you ask for. The worst that can happen is a ‘no’ response.

2 Looking through other books you like to see how Figures, Examples, Sidebars, and so on are arranged and referred to can give you a good idea how to plan things out in your book.

And the number one thing I learned:

1 Author obscurity is worse than percieved “piracy”. Unless you’re Stephen King, release your books under a free documentation license.

For details on the book, or even full text, visit my Web page. -m

Share your experiences with writing or publishing:

Bob DuCharme

AddThis Social Bookmark Button

Note that I said “linking from”—usually linking is about linking to
another web page, but TrackBack lets you link from someone else’s weblog to
your web page. It’s typically used to alert that weblog’s readers that you’ve linked to it because you had something to say about it, and then someone reading that weblog can follow your trackback link to see what you had
to say. This is what makes it
an interesting development in the history of web linking: the web’s lack of
two-way linking is a classic topic for Old Hypertext Guys to
complain about, but now we can do it. (Well, sort of.)

For example, I once
wrote a weblog entry titled Link Typing: Who
cares?
. Jeremy Smith posted
an entry
on his own weblog that commented on mine. To make it possible for
people reading my entry to find out about his comments, he added an entry to
the TrackBack
listing for “Link Typing: Who cares?”
that linked to his entry. By adding an
old-fashioned HTML link from his weblog entry to mine and a TrackBack link
from mine to his, he essentially created a two-way link. If I had written a
new entry responding to his comments, I could have added a TrackBack link from
the weblog entry with his comments back to my response. This can continue as a
linked “conversation,” and people have written software to follow these
threads.

TrackBack began as a feature of Movable Type, an application that helps
to automate weblog creation. The process of “pinging” a weblog, or
adding a link from a weblog entry’s TrackBack listing to your own
weblog or website, is simple and well-documented when you use Movable Type. The
Movable Type folks have also published the
details
of how a non-Movable Type system can implement TrackBack, but I
haven’t found a good explanation of how someone not using Movable Type can use
one of these implementations. This was particularly frustrating for O’Reilly Developer webloggers, because the weblogging system here doesn’t use Movable Type, but if you go to any O’Reilly Developer TrackBack page (for example, this one) and follow the “What is TrackBack?” link, it takes you to a Movable Type explanation aimed at Movable Type users.

Other weblogging tools have added the ability to ping weblogs, but you can do it without special client software. Many weblog sites,
including O’Reilly, offer a web form
interface
to a CGI script that can send a TrackBack ping linking any
weblog entry that supports TrackBack back to any other web page, but my favorite so
far is the one
at reedmaniac.com
, which documents the fields to fill out well enough that
I don’t have to explain most of them here. The first field, “TrackBack Ping
URL,” is the special URL that CGI scripts use to tell the weblog’s server
that that entry has been pinged. For example, let’s say you were going to add
a TrackBack link to the my first weblog entry. (And
please, go ahead, even if you just enter dummy text to get comfortable with TrackBack. I don’t
expect to see any substantive pings for that one. If you really are going to make comments in your weblog about what I say here, ping this one instead; that’s what TrackBack is for!) From that weblog entry
page, you would click “TrackBack” to go to its TrackBack
Display
page. The top of that page shows
http://alpha.oreillynet.com/cgi-bin/tb/tb.cgi/wlg_3035 as the “TrackBack URL
for this entry.” That’s what you would enter in the first field of the reedmaniac pinging
form
. The “Permalink URL” field at the end of the form is where you put the URL of your weblog
entry: the destination of the link created by the ping. While people usually discuss TrackBack in terms of linking one weblog entry to another, you can enter any URL you want in this last field, which means that a trackback link can link to anything, not just a weblog entry.

Some people claim that the conversations represented by TrackBack threads have replaced the comments once added to the end of weblogs. For example, if I want to make a point about something you said on your weblog, instead of adding a comment at the end, I might make my point on my own weblog and ping your entry so that you and others knew that I had done so. Despite hearing this, I’ve seen more comments than TrackBack pings on this weblog, and most TrackBack listings I’ve ever seen are empty, so this still needs to be proven to me.

I’m not really sure whether TrackBack is that popular, frankly. I thought
it was very cool how sixapart.com
posted a skeleton document with minimal content and encouraged OSCON 2002
attendees to ping it from their weblog postings about the conference, because
instead of a chunk of content with accompanying commentary, the corporately
authored table of contents
that grew around their skeleton became the primary
content. On the other hand, no one that I know of has done anything similar
since, and for OSCON 2003 Edd Dumbill and Dave Beckett used IRC instead of
TrackBack to collect contributed content into a central location. Still, TrackBack isn’t much more than a year old, and as more people learn how to use it we may see more interesting uses of it.

Do you know of interesting TrackBack applications like the OSCON 2002 one or thread crawlers? Do you think TrackBack’s use is growing, or has it leveled off?

Advertisement