Tuesday, July 01, 2003

The unspoken of groups The unspoken of groups. Clay Shirky has posted his seminal keynote at the O'Reilly Emerging Tech conference: I want to talk a pattern I've seen over and over again in social software that supports large and long-lived groups. And that pattern is the pattern described in the title of this talk: "A Group Is Its Own Worst Enemy." So I just posted my comments from the same conference which were in some ways a response to Clay's presentation: I want to suggest there's a reason why we keep making the mistake that Clay specifically points to: the failure to adopt a group "constitution." It's... [Joho the Blog] 10:09:22 PM  comment []       [PhilWolff] "There's a concern that blog components may be "the semantic web" in sheeps clothes. Perhaps. I want to assure Echo has the hooks, flexibility, and extensibility to permit new kinds of xml packaging. There are solid business reasons for adding packages to an existing syndication mechanism. Let's make sure it happens around Echo. " Take a look at http://www.intertwingly.net/wiki/pie/ComponentBlog and http://www.intertwingly.net/wiki/pie/AdaptiveBlogosphere and give Phil some feedback. [PhilWolff] 9:28:13 PM  comment []       Arguments for supporting "content by reference" in ECHO The following are my lastest comments on the content discussion page at Sam Ruby's ECHO wiki. What I am saying above is don't give us less options to describe content than I already enjoy today in RSS. ECHO's definition of content has narrowed so much to the point I don't see how we can call it content. It should be called something like "content encoded". Others and I have expressed that we believe there also should exist a second type of content (a most likely others)in a feed named "content by reference". This is not a new invention in RSS as I have explained above (is available by using enclosures today in RSS). Putting file hrefs in chunks of html is not close to the same. That is as wrong as saying adding a BiblioGraphy module is the same as just adding the meta data title, subtitle, summary straight into the content. To get past this, I propose that we split content into two: "content encoded" and "content by reference" (these names could change but the principal should remain the same). Two tags that are children of entry that can coexist just as description and enclosure can today in RSS under item. Making the split would give equal weight to each type of content and satisfy the meeting of what is offered by enclosure in RSS today. I don't think anyone would argue that this split adds any additional levels of complexity on software authors. At a minimum it simplifies the identifing of file types in feeds. Notice also the complication of "unlimited content" especially as it applied to "content encoded" has been removed. Vote for the splitting of content into two over at content discussion page at Sam Ruby's ECHO wiki  One "content encoded" module that can be null and one "content by reference" module that can be null: Ref: Content types discussion at Sam Ruby's ECHO wiki: http://www.intertwingly.net/wiki/pie/content 9:06:18 PM  comment []

© Copyright 2003 Harold Gilchrist. Last update: 8/2/2003; 6:15:25 PM. This theme is based on the SoundWaves (blue) Manila theme.