Friday Sep 25, 2009
Monday Sep 21, 2009
By billy.cripe on Sep 21, 2009
We are in the midst of a series investigating collaboration. We previously wrote about the two types of collaboration - intentional and accidental. INTENTIONAL: where we get together to achieve a goal and ACCIDENTAL: where you interact with something of mine and I am never aware of your interaction While intentional collaboration is good it is not where the bulk of untapped collaborative potential lies. Accidental collaboration is. But the challenge is to intentionally facilitate accidental collaboration. For the full list of 10 requirements see the original post. Last time I wrote about requirement #4: why we must be sure to enable the humans. While it is great if humans are empowered to consume, we must keep it easy for them to do so. Therefore enter requirement #5: the importance of data portability and ability to be referenced. After all, if we go to all that work to identify and extract data from content containers then it is a simple next step to ensure that the data is located where we want it when we need it. Well here we are. If you have followed along, we have identified data residing inside of documents, we have exploded content items, we have jail-breaked data-and-relationship assertions and made it easy for people to add their own experiences and expertise to those growing data sets. That is all well and good if and only if there is a consistent way to move that data around, to relate it to other data that may be and usually is in a different schema, and finally to address and obtain that data. This is practically taken for granted with traditional relational databases and on the web. After all, the primary key uniquely identifies a record, the URL uniquely identifies a document on the web. We can get it, move it and relate it to other bits of information. But isn't it curious that we reference items differently depending on where they're located. We need to know the structure of data first before we can even think about trying to reach it. Web pages have URLs, DB Records have primary keys, filing cabinet files have a physical location, you and I have a postal address. That makes it awfully hard to combine data sets, perform meaningful comparisons or combine expertise with the confidence that we're not leaving out the most important information available simply because it is addressed differently.[Read More]
Enterprise 2.0 and Content Management
- This blog is now closed.
- WebCenter PS3 - Navigation Models and Pure CSS3 Menus
- Officially Official - WebCenter PS3 is here!
- WebCenter - Exposing Twitter Data in an ADF WSRP2 Portlet
- Your Enterprise Web - Content, Portal or Both?
- Social BPM - Benefits & Getting Started
- Getting Started with Site Studio for External Applications (SSXA)
- Site Studio Mobile Example - WCM Reuse
- WebCenter .NET Accelerator - Microsoft SharePoint Data via WSRP
- WebCenter 11g UI Examples