For the nnnth time. Please consider using L I N K E D D A T A as foundation. - Aldo Bucchi from FriendFeed MT Plugin

@XBRLMeister I believe Linked Data DOES meet your business requirements. Can you be more specific? Whatever can be built on XML can be built on RDF. I am aware of the collaboration efforts and I use both techs on a daily basis. By using Linked Data / RDF you'd gain: * Access to maturing family of second generation middleware * Identifiers as endpoints that can be dereferenced ( w/o using proprietary protocols and conventions ) * Automatic mashing of the data ( both XBRL and any other, i.e corporate data or DBPedia ) * Querying over a graph based model using a well understood and characterized query language ( more expressive and powerful than the "X.." family ) ** Business reporting and aggregates are not part of the standard but they can be widely found. Moving a quad from-to relational models or OLAP is also quite straighforward. * Alignment with a rising community that is integrating RDF into many realms ( spreadsheets, social networks, desktop environments, etc ) * Lastly, the most valuable: Seren - Aldo Bucchi from FriendFeed MT Plugin

I am going to take a small step now and articulate how Linked Data's "serendipity" can add value to business data. The current financial turmoil is rooted in our inability to integrate *beyond* the expected lines. Not simply the complications of operating *within* the expected lines. Otherwise we never improve the paradigm ( until it proves itself flawed and you have Greenspan putting up a surprise face on national TV ). This is a complex system, we need to see data in context. Assume you have an epidemic hitting a certain region. What is the financial footprint? Who benefits? Who suffers? Can we understand the impact this has across borders, value chains, industries and throghout time? Can we see the ripples? If we operate on closed systems designed to reflect reality on a certain paradigmatic surface, we will always miss part of the picture. This is where Linked Data comes into scene. With linked data you could bring together biological data, protein data, geographic data and demographics ( which wer - Aldo Bucchi from FriendFeed MT Plugin

@XBRLMeister Please stop second guessing my intentions, leaving incomplete phrases and suggestions. This is not healthy debate. If you are going to engage in this kind of public discrediting, at least provide your name and affiliation. 1. I am NOT defending any particular entity with a bias. *You* brought one up and incorrectly "framed" them ( and continue to do it ). 2. I am not stating that XML should not be used. I am sure that much thought has gone into the current framework, and it makes no sense at all to throw it away. RDF can be serialized as XML and contain XML. You can mix and match both. So I repeat: "everything can be done". 3. URIs needn't be on the open web. They are, in essence, a global naming scheme ( with all the benefits that provides when it comes to integration ). With respect to security, the fact that there is one web does not preclude you from partitioning it into different communicational channels through different access strategies. That's how the web is built today ( private/pu - Aldo Bucchi from FriendFeed MT Plugin

@XMeister, Wouldn't it be nice if "@XMeister" was a conduit to a description of who you are? By this I mean it exposed your profile page? In a nutshell I wouldn't have to google in vain on the literal pattern which simple reveal nothing. Back to the topic at hand, XBRL, Data Access, and Data Joining. XBRL is simply an XML based approach to modeling financial reports. A financial report is a document about financial entities such as balance sheets, profit and loss statements, statements of applications of funds, and so on. If every entity in an XBRL instance document has an identifier, the relationships between these financial entities becomes clearer and navigating the relationship graph becomes feasible (what you do when you are looking for stuff in any realm). If every entity in an XBRL instance document has an HTTP based Identifier, we end up with the ability to reference said entities across an HTTP based network (external or internal). Likewise, the aforementioned graph is no longer localized (whic - Kingsley Idehen from FriendFeed MT Plugin