Fujitsu Software Corporation announced the availability of Interstage Contentbiz v7, the newest version of Fujitsu’s application platform for enterprise content integration. Interstage Contentbiz v7 extends support for Web services and Service-Oriented Architectures (SOA), offers a new extensible audit trail and enhances integration capabilities. These features allow companies to more effectively access, modify and search structured and unstructured enterprise content resident in disparate, networked systems, independent of format or location. Key features and enhancements include: Bidirectional WebDAV Agent enables integration with any enterprise content management (ECM) system that complies with the Web Distributed Authoring and Versioning (WebDAV) standard; New Extensible Audit Trail ensures that proper audit trail information is maintained for all compliance documentation; Enhanced Web Services Interface enables enterprises to leverage a service-oriented architecture (SOA) to create Web services and integrate reusable content integration services with applications; New Web Content Agent extends the reach of content integration solutions to intranet and Internet content; and, New Content Portlets, which comply with JSR 168 (Java Specification Request for Portlet API), provide commonly used content navigation and search functionality that can be easily deployed on enterprise portals. http://www.fujitsu.com/interstage
XBRL is, in some ways, a funny kind of XML language. It doesn’t make much use
of the capabilities within XML Schema to express relationships such as
order, hierarchy, and so on. Viewed strictly as XML, XBRL looks pretty flat,
without a lot of contextual constraints.
But that’s nonsense, of course. Financial documents are highly constrained
and contain intricate interrelationships. XBRL expresses these relationships
within "taxonomies"–special XBRL constructs that define business
"concepts" and that relate these concepts to each other. The
relationships can, in fact, be really complex …more so than would be possible
within a strict XML Schema definition.
Once consequence of this decision to define the bulk of XBRL semantics
outside the range of standard XML semantics is that XSLT (XML Stylesheet
Language Translator) doesn’t work very well
as a way to transform XBRL documents into something that humans can read. Since
"understand" the information in the XBRL taxonomy, XSLT does not have
the information that it needs to present the "facts" in an XBRL instance
in a way that reflects the taxonomy relationships.
So, how do people produce formatted output from XBRL today? In a Wednesday morning session at the 11th
International XBRL Conference, Raymond Lam of BlastRadius
explained that the usual solution is to hard-wire all
the necessary contextual information into the XSLT rules. The result is an XSLT
stylesheet that contains nearly as many separate template rules as there are
separate facts to be presented. Bummer.
I remain a fan of Onfolio, which began life as kind of a personal knowledge manager for Web-based content, but has evolved to also handle RSS feeds and provide more publishing capabilities. I have used it for quite a while now to maintain my eForms Resources page, and am currently using the new version, 2.0, which supports Firefox, which is now my primary browser.
I’ve had some correspondence with Sebastian Gard, who does product marketing for Onfolio. He asked me for some feedback on 2.0 compared to the earlier version of the product, and I offered the following.