Skip to main content

Diigo Home

Reinventing Silos - The Diigo Meta page

www.fastforwardblog.com/...reinventing-silos - Cached - Annotated View

Bertrand Duperrin's personal annotations on this page

bertrandduperrin
Bertrandduperrin bookmarked on 2009-06-30 silos content formats enterprise2.0

Blogs and wikis provide specific formats to content. There are behavioral format clues that differentiate a blog from a wiki, but under the covers it’s all content. Content elements have value beyond the formats and applications that hold them hostage — they’re enterprise assets that can be repurposed in other formats. The specific format of content (.pdf .doc .html) is really only relevant for consumption — to associate the ‘viewing’ of the content with an application that can display it. The semantics of the content itself doesn’t really care about the format (don’t hold me to that when I’m telling you how to create semantically-relevant formats), just ask your favorite search engine — it’s all words to them.

  • Consider a simple ‘hostage’ example (one that I’ve been aghast as many UX designers have missed the significance of), a UI with the labels “Blog” and “Wiki” as two separate options for navigation.
  • Sure, 2.0 technologies can increase transparency across organizations, but that’s all lost as you move across ‘closed’ solutions or formats, with no architectural layer to synthesize it all. One silo is simply replaced by another.

This link has been bookmarked by 2 people . It was first bookmarked on 30 Jun 2009, by Bertrand Duperrin.

  • 01 Jul 09
    grlloyd
    Greg Lloyd

    The significance and potential power of a format-agnostic architecture is evidenced in the recent demos of Google Wave. What we don’t have are the corresponding ‘drivers ed car crash movies’ to illustrate the disastrous end to conversations that are locked and isolated in disparate tools and formats.

    socialsoftware enterprise20 analysis

    • The significance and potential power of a format-agnostic architecture is evidenced in the recent demos of Google Wave. What we don’t have are the corresponding ‘drivers ed car crash movies’ to illustrate the disastrous end to conversations that are locked and isolated in disparate tools and formats.
  • 30 Jun 09
    bertrandduperrin
    Bertrand Duperrin

    Blogs and wikis provide specific formats to content. There are behavioral format clues that differentiate a blog from a wiki, but under the covers it’s all content. Content elements have value beyond the formats and applications that hold them hostage — they’re enterprise assets that can be repurposed in other formats. The specific format of content (.pdf .doc .html) is really only relevant for consumption — to associate the ‘viewing’ of the content with an application that can display it. The semantics of the content itself doesn’t really care about the format (don’t hold me to that when I’m telling you how to create semantically-relevant formats), just ask your favorite search engine — it’s all words to them.

    silos content formats enterprise2.0

    • Consider a simple ‘hostage’ example (one that I’ve been aghast as many UX designers have missed the significance of), a UI with the labels “Blog” and “Wiki” as two separate options for navigation.
    • Sure, 2.0 technologies can increase transparency across organizations, but that’s all lost as you move across ‘closed’ solutions or formats, with no architectural layer to synthesize it all. One silo is simply replaced by another.

Top Tags