Michal Migurski's notebook, listening post, and soapbox. Subscribe to this blog. Check out the rest of my site as well.

Jun 24, 2005 2:15am

reblg, again

Marc Canter posted a lengthy reply to my previous post about reblg. It's a great point-by-point answer, and has been clarified somewhat through conversation as well. He really has a grand vision of a microcontent mesh, and it's both aspirational and achievable, so I'm into it. There are still a few difficulties I'm having with it, though, mostly of the "metacrap" variety.

Overall I'm really into the possibilities here, because I think that microformats have great potential to pick up some of the sem-web slack in a way that's incrementally reachable.

Marc lists a few benefits for content creators in addition to the ones I mentioned. One is:

It's imperative that the structure of the microformat or micro-content be maintained. This is the 'challange' that RSS has put us into - services like UpComing.org enable subscription to one's personal events, but the structure of the event is lost. That's gotta stop. We NEED to maintain the structure of stuctured content!

Okay, yes. But right now I subscribe to an iCal version of my Upcoming.org events, and they appear in my calendar app along with all my other events and appointments. That's not just structure, it's structure in a format I can use directly. hCal isn't there just yet, and it's the easiest one of the microformats to render unambiguously. Imagine hReview butting up against straw man #7.

Something else he says, later:

Going back to the islands of functionality..... For us (as an industry) to equal Longhorn and whatever Apple comes up with - it's imperative that we come up with techniques to implement the mesh. A mesh that inter-connects tools togfether. That's the infrastructure we're proposing.

I'm curious why Google isn't on the list with Apple and Microsoft. I view them as being in the best possible position to provide the kinds of aggregation services that microformats need, and the least likely to cooperate openly. Just as tags are useless without a Del.icio.us or Flickr to provide a comparative context, semantic microcontent requires that like be compared with like for it to make any sense. A decent search engine that was microcontent-aware would certainly help, and this seems to be exactly what Marc's proposing.

I bet it would take Google a month tops to implement the expected response for a search like "format:hcal san francisco skinny puppy shows".

Marc pledges not to commericialize the data, which is a bit of a bummer to me. Having a plan for commercialization up-front means that you're prepared for the eventuality (because it always comes up), and you're talking about it from day one so nobody from the information-wants-to-be-free crowd freaks out down the line.

Anyway, it's a lot to digest. Especially as it relates to ReBlog, because there's so much overlap it's scary. He's right that we're converging on the same spot from different direction - ReBlg has the big picture with not a lot of proof-of-concept, while ReBlog has been working pretty well for a year now in the specific domain of RSS content curation. It's a few plug-ins and bookmarklets away from realizing half this stuff.


Sorry, no new comments on old posts.

October 2015
Su M Tu W Th F Sa

Recent Entries

  1. the bike rack burrito n’ beer box
  2. a historical map for moving bodies, moving culture
  3. the other openstreetmap churches post
  4. platforminess, smartness, and meaningfulness
  5. writing a new continuous integration service for openaddresses
  6. state of the map 2015
  7. bike ten: schwinn touring, v2
  8. blog all oft-played tracks VI
  9. 2015 fellowship reader
  10. bike ten: schwinn touring
  11. more open address machine
  12. open address machine
  13. making the right job for the tool
  14. the hard part
  15. end the age of gotham-everywhere
  16. on this day
  17. write code
  18. managers are awesome / managers are cool when they’re part of your team
  19. bike eight: french parts
  20. being a client