Description
 

Welcome to my Blogroll
Important statements
Cool Tools
Our stuff
Current Collaborators
True Nerds to know
Open Technologies
In Rotation
Occasionally
Resources






June 2003
Sun Mon Tue Wed Thu Fri Sat
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30          
May   Jul



Click here to visit the Radio UserLand website.

Subscribe to "Marc's Voice" in Radio UserLand.

Click to see the XML version of this web page.

Click here to send an email to the editor of this weblog.

Marc's Voice
Home LANs + Broadband + Devices

Thursday, June 26, 2003
FOAF barn raising / autodiscovery link.

Today Mark Pilgrim posted:

Dan Brickley: New version of XML:FOAF in CPAN. Looks like that syntax for FOAF autodiscovery is the de facto standard now.

So, I updated my about / people page with the autodiscovery syntax, which looks like this*:

<link rel="meta" type="application/rdf+xml" title="FOAF" href="foaf.rdf" />

But, for the moment, my FOAF file looks like I have no friends, and this makes me not like FOAF! OK, I actually like FOAF or want to like it, but maybe we need to all get on an IRC chat and help each other create references to each other?

I put my FOAF file online a while ago, with the intention of starting to add some people's names to it. I saw that Marc Canter mentioned he was starting to do this in his FOAF Time post, but looking at Marc's FOAF file, it looks like he hasn't gotten to it yet.

Danny Ayers has his FOAF file on his site, and looking at it confirms what I think I need to do to add friends to my FOAF file. But, in terms of people whom I have some interaction with, Danny has been into FOAF way longer than I have, and his FOAF file makes him look pretty friendless too (which is not true)!

So, what is up with this? Do we need to have a FOAF barn-raising?

I was thinking we could change FOAF to mean something like "Friendless' Obsolete Annoying File" if no one uses it. I guess if TypePad uses it, a lot of people will use it. I want to support it in the iCite net, so I am curious to see where it is at.

* The New version of XML:FOAF in CPAN page shows a link using an attribute called "ref", which actually should be "href". You can see the correct version in the XML::FOAF spec. The way I show the link in this post is the correct form.

There is more discussion of the XML::FOAF module on Six Apart's Fun with FOAF page.

[the iCite net development blog]

Coolio here we go.  Clearly the goal is discoverability!

My FOAF file now has only one friend - Morten.  I want to add Danny, Jonathan Peterson and Jay - but what a hassle!  There are actually two ways to 'make friends' - and I'm still trying to figure out the 'other' syntax (other than the one that Morten gave me.)  Clearly it has something to do with seeAlso.  But I'm surprised that all this isn't more together.

Maybe we can even get to be friends with Aaron Schwartz.

HELP!  FOAF Explorer works cool though.

Everything Must Go.

Attention Shoppers: Winer Tentatively Ratifies Echo, Pledges Perpetual RSS 2.0 Support

"But I can support Echo because it appears to be respecting the Roadmap in RSS 2.0. That's much appreciated. Thank you."

Thank you, Dave.

[Steve Gillmor's Emerging Opps]

And I thank Dave too.

 Dan Brickley | FOAF | Friendster | GPS 
mobile meta?.

35PG0105.jpg

if the photo software in this p800 camera-phone knew how to talk to a bluetooth GPS, ...

someday... foaf + location + photos ...

not yet... when? [RDFWeb and Friend of a Friend (FOAF)]

lib-foaf-flag-small.jpgIt's great to see Dan Brickley use images.  Most of these semantic web bloggers have such bloodey boring blogs.  You know BBBs.

He brings up a good point about finding people, GPS and FOAF.  He also points to - earlier - to a post by PlayaInfo about FOAF at Burning Man.  The expectations these people have is tremendous - now we just gotta get it all working!  Connecting FOAF to Friendster is great, but I wonder if these folks have ever met Jonathan Abrams?

Boy are they in for a surpirse!

RSS = Readily Significant Schizophrenia.

After reading Sam Ruby's post called There is no FAQ, about what the RSS link element was/is for, and subsequent comments, it is clearer to me now that Really Simple Syndication isn't the right way to do Rich Site Summary, or vice versa.

So, I think two different concerns are up against each other, and they shouldn't be blended, though they would ideally be complimentary: content use and metadata.

I am new to the verb / noun concept, but from what I understand about it, Really Simple Syndication (which I will just abbreviate RSS 2.0) is a verb oriented concept and Rich Site Summary (which I will just abbreviate RSS 1.0) is a noun oriented concept.

In other words, RSS 2.0 is designed for the action of syndication and RSS 1.0 is designed for the metadata of site summaries.

RSS 1.0 data are site summaries, and RSS 2.0 is a mechanism to syndicate a site. People use RSS 1.0 as if it were in the same vein as RSS 2.0 (i.e., for syndication), and it happens to work for that in some ways. And, people also use RSS 2.0 as if it were in the same vein as RSS 1.0 (i.e., for site summaries), and it happens to work for that in some ways too.

Sam's posts and the subsequent comments reference comments from Dave Winer on the link element, and I think these altogether are an effort to clarify the vagueness in the current RSS where the same link element can function as either "pure" metadata (i.e., a permalink as identifier) or for functional content uses (i.e., a link to a relevant article or the original post).

In particular, the vagueness between "pure" metadata and functional content use is like a schizophrenia. And, I think that the way to resolve these two sides, metadata/data and content use, is to first make sure they aren't blended, and then look to improve each using an appropriate methodology, say, data modeling and application modeling respectively.

Obviously, the data model affects the application model, and vice versa. So, this Echo Project effort isn't off track in looking at everything. But, I think a good next step might be to fully recognize and move forward with the understanding that site summaries and site syndication might overlap but aren't the same thing.

I have mentioned Ian Davis' UnifiedRSS a few times, and I appreciate now that Ian really had an insight into this distinction between RSS Metadata and RSS Content. Maybe Echo can be a singular format rather than the two that Ian suggests, but I think the distinction Ian is making is a necessary one.

So, I have a schizophrenic wish list for RSS. First, what I want from Really Simple Syndication:

  1. Resolve the use and function of markup in syndicated content
  2. Support relative links
  3. Provide a modular way to include additional, functionally useful, content elements (e.g., if I want to have more than one link in the vein of Radio Userland)

And, what I want from Rich Site Summary:

  1. Support URI to the presentation summarized (i.e., a permalink)
  2. Support URI to the summary itself (i.e., a permalink to the RSS)
  3. Provide a modular way to include additional metadata

Obviously, if these end up being two different formats along the lines Ian suggests, then I would want them to be able to provide references to each other.

[the iCite net development blog]

Right on to Jay - for rapping it out so succinctly.

I myself vote for Faces - as identifiers - so we can put a human face to our channels (or a logo for the publisher/entity.)

Apple Core.

Bulletin: Apple ships Safari SDK

It's hard to describe the famous reality distortion field that Steve Jobs sets up with his biannual keynotes. The elements are classic--one part software, one part hardware, one part power user, one part invented here. Jobs has a quick wit, good presentation tools, and a hand-picked audience of the faithful.

What could go wrong? Not much. For a brief shining moment--in this case 2 hours plus--we are hurtled back into Camelot., where computers make work seem elegant and time a dimension to be bent and shaped. Each time Jobs does this trick, I sit back and enjoy the ride, knowing full well the spell will shimmer and then dissipate.

But the field is changing--less distortion, more reality. The long-foreshadowed partnership with IBM is now real, with the "world's fastest desktop machine" promised to get 50% faster within a year. The iChat video-conferencing we've been trying to get work with NetMeeting for 5 years is shipping at prices Grandma can afford and business will certainly use in the boardroom.

Panther--the next rev of OS/X--adds incremental improvements that sound less impressive on paper than they add up to on screen. An improved Finder--now that would be easy. Expose--you mean you can actually find that screen with a quick gesture without rearranging every other one? Threaded mail? Autosyncing files to the .Mac cloud and back?

But Jobs is reaching the same tipping point he's rendered with Pixar. Toy Story is still in my 2.5 year old's rotation--averaging pickage once every ten or so "pick me up Daddy--let me see..." trips to the video library. The key here is longevity, not opening week. It's the blend of technology, design, humor, and music that creates the virtuous circle.

"One more thing..." says Jobs as he announces the core of today's hardware, the next-gen G5. The power is in the rhythm, building on the methodical march of the software platform. Yes, Microsoft can clone the innovations as they occur, but with the loss of excitement, the promise of empowerment, the joy of beating time at its inexorable game.

It's impressive to watch the G5 best the dual-processor Xeon at Photoshop rendering, 3D, and synthesized sequencing. But it's more devastating than that--it's funny and gut-wrenching as we see our life slipping away in Windows while the G5 waits for more ideas. The new XCode tools shave hours off compile times with predictive and on-the-fly repair and recompiles, and Distributed Build bootstraps Rendezvous to spread the work across multiple systems.

The Safari SDK is music to the ears of both developers and users, particularly Brent Simmons of NetNewsWire fame and authors of those RSS channels that deliver full-text and graphics feeds. Now if we could get spell-checking services in the Safari container, I'd be just that much closer to the place Jim Allchin won't go. Already I'm enjoying Safari's tabbed windows to spotcheck this story as it unfolds on the CRN site. Bye bye IE.

Jon Markoff of the Times asked the core question: will all this increase their market share? Yes, I told him, it will add to the more than 50% share of laptops at most tech conferences. Yes, I guessed, to the corporate communications nodes that will spring up around executive video-conferencing, interactive sales presentations, and remote office collaboration suites.

But Jobs hinted at another avenue of adoption when he showed the iChat AV video-conferencing extensions and clip-on iSight camera. First he gave one to each of the developers in the room, betting that they would be the perfect evangelists to spread the word. Then he suggested that, like iTunes, this would first be available to Apple users only, but would spread to the rest of the market when they "adopted the open standards" of the technology.

Until recently, I would have laughed that one off, given Microsoft's effective firewall with Dell et al. But with Sun's success in planting its JVM on HP and Dell machines, an avenue for development is now seeded on the PC across Redmond's DMZ. When I chided Sun's EVP of Software, Jonathan Schwartz, on not fully leveraging the synergies between Apple and Sun, he agreed with me. "I've got some work to do there," he said.

After the keynote, Apple's corresponding software guru Avie Tevanian asked me what I thought. I told him much of the above, pausing only to reinforce my delight that the Safari SDK was shipping earlier than expected. I predicted that Apple success at extending its core set of services would provide an opening for the company in the emerging RSS architecture that others, particularly Microsoft, could not exploit.

Like Schwartz, I expected some pushback. Like Schwartz, I didn't get it. Instead, I got a request for the Allchin Tax URI. I'll just bounce over to the Emerging Opps tab.... Here it is, Avie.

[Steve Gillmor's Emerging Opps]

The new Safari breaks our WebOutliner product.  After carefully tracking their progress and keeping up with their whacky new browser - we were f*cked by Apple - once again.  God bless um.

Just to be clear - there's no way in HELL we'd ever support a Mac only API.  We'll copy it, clone it, help others copy them, steal from one to help another and in general play the innovation game and make what they have available to everyone else - but it's all about cross-platform - baby.  It has been since 1988 - when we showed the first cross-platform multimedia player.

And as long as Apple doesn't license their OS and keeps it to themselves - they'll always be - just Apple.  They do have a play in the digial lifestyle arena - and I might even buy one of those - someday - but it'd BETTER be based upon 'open standards'.  Not Quicktime.

I just wanna know how long they're gonna 'give away' their video chat bandwidth before their buddies at Akamai start asking to get paid (since they have to pay for the bandwidth - too!)

Our host at reBoot in Copenhagen. I had a great day with Thomas on Sunday, walking around Copenhagen and Christiania.  We got on a water taxi and there was a camera crew videotaping - getting everyone to sing along. The interviewer asked me: "do you know any songs?" at which point I launched into :20 minutes of Opera, Gilbert & Sullivan, Cole Porter and the Sex Pistols.

It was fun.

Anyway here's Thomas on one of Copenhagen's 'canals' - drinking Elderberry wine (or some sort of Viking concoction.....)

Howard Dean Top 10 On David Letterman. Uh oh. Looks like I'm going to have to start keeping a better eye on the Letterman Show. Tuesday, June 24, Letterman did a "Top Ten Signs You're In Love With Democratic Presidential Candidate Howard Dean." If anyone got a recording of this, please email me with your demands for a copy!

Top Ten Signs You're In Love With Democratic Presidential Candidate Howard Dean

10. You've actually heard of him.

9. Whenever he discusses plans to revitalize economy, you get goosebumps.

8. Named your cats "Howard," "Dean" and "Six-Term Governor Howard Dean."

7. You'll only watch movies featuring Ron Howard or Harry Dean Stanton.

6. When you hear a report on the radio about a highway accident, you murmur, "Please, god, don't let Howard Dean be involved."

5. Constantly complain rival candidate Dennis Kucinich isn't "Howardly" enough.

4. Changed outfit four times before watching Dean's appearance on "Meet the Press."

3. You stand by him despite the fact his infidelities embarrassed you in front of the entire...oh wait, wrong Democrat.

2. When he announced his candidacy, you didn't laugh your ass off.

1. You're actually considering wasting a vote on him. [On Lisa Rein's Radar]

FOAF iconFOAF Project revamp.

Dan Brickley's had a good clear up on the rdfweb site (the home of FOAF). The front page is now the MT blog, which he's been busy with - looks like we might be seeing daily tips ;-)

RDFWeb: Friend of a Friend (FOAF) Project [Raw Blog]

Just starting to grok this FOAF scene out.  My conversation with Morten Fredericksen was enlightening.  Now I see that their 'face' is coming together.  Soon (maybe) they'll even be a FOAF.org  so if someone wants to find out (discover) something on FOAF - they don't have to Google it.  All standards should have it's own .org page.

That leads one to wonder about Echo.org - which is currently under control of some......

foaf sample

Anyway - back to FOAF.  So I went to add some 'friends' to my FOAF list last night and sure enough - there are two ways to do that!  Just when I thought I had a handle on it - it goes meta on me!

Hopefully by the end of today:

     - I'll have resolved these two ways of depicting friends and have added Danny and Jonathan

     - Then I can start on becoming friends with Aaron, Libby, Dan and others - so I can eventually add them as well

     - I'll spend some time grokking afew more FOAF:types - like nearest airport.....

     - And stand in line and wait for the new FOAF-a-matic

     - and MOST IMPORTANTLY start thinking about using FOAF.....

     - because as you all well know, TypePad will be using FOAF for blogrolls and......

Morten turned me onto a XML version of the FOAF bulletin board, which could then (concievably) be used for that horrible of all horrible concepts - centralized discoverability!  "Oh my"  "Heaven forbid!"

[FoaF Explorer] And for the record - the SVG stuff doesn't work.  I've tried four times to load it - on three different machines.  So I can't get FOAFnaut to work.

Here's a dumb question - representation of more than one degree of friendship?  Has anyone 'done' that yet?  Yet another level of hierarchy?   Formalised at all - yet?

 Dave Winer | Echo | Jon Udell | Sam Ruby 

Fixing RSS's public-relations problem

Yesterday I spoke with two acquaintances, both of whom have decades-long track records in the high-tech biz, and neither of whom has ever used an RSS newsreader. When I mentioned RSS as an alternative to mailing lists, both said the same thing: "But I don't have time to visit 30 different websites in order to find things out." Of course, that is exactly the problem that RSS solves. And has been solving, for me, since 1999.

Over the years, people have asked me which version of RSS to use. I've always said it doesn't matter, they all do the same thing. But the question always annoys me, because while I've tried to pretend otherwise, the fragmentation of RSS really is a problem. I think it's part of the reason my two acquaintances aren't using RSS today. And if they're not, how can we really expect Tim Bray's Mr. Safe to jump onboard?

Despite the confusion, a very notable Mr. Safe -- the BBC -- just did jump aboard. Given a choice of three formats -- RSS .9x, 1.0, and 2.0 -- the BBC opted for the safe choice: .9x. That's sad in a couple of ways. First, because people at the BBC even had to worry about this choice at all. Second, because 2.0 has a stronger core and a well-defined mechanism for extension. It should have been the safe choice.

I'm delighted to see that Sam Ruby has launched a collaborative effort to review the RSS core and delineate its periphery. According to Tim, Sam's employer -- IBM -- has given him the go-ahead to work fulltime on the project. This is huge. I'm equally delighted to see that Dave Winer is both reporting on and contributing to the discussion.

If the goal of this effort is to nail down what last year's RSS 2.0 process also aimed to achieve -- a solid and universally-acknowledged RSS core, freely extensible in a solid and universally-acknowledged way -- then I hope it moves swiftly to achieve that. The existing core, in my view, requires few (if any) changes. What we need is consensus on the core, the sooner the better.

The periphery is vast. It includes commenting, threaded discussions, semantic modeling, authentication and encryption, and an endless amount of other stuff. All that can come in due course.

Let's be clear: RSS is in no way broken. I, for example, will be using RSS to monitor this current round of analysis and specification. I don't really care whether tags are written as mixed-case or lowercase. But there are issues in the core, and issues related to the delineation of the periphery, that do matter to me. RSS will empower me to tune into its own review process in the most efficient way. What's broken is that not nearly enough people know about, or use, this model of awareness diffusion. That's a public-relations problem, not a technology problem, and one that I hope will at last be fixed.  [Jon's Radio]

Jon Udell says it like it has to be said.  Hopefully Echo will appear shortly - and include faces..... :-)


Updated: 9/17/2003; 12:22:29 PM.