This is the official announcement that all ISIS Papyrus Platform products are fully compliant to open standard XML formats. To document that fact ISIS Papyrus Software AG has joined the most relevant standards organisations and will in future participate in the formation and evolution of these standards.
We have more important things to do than to waste time discussing the subject of XML with all related problems. The Papyrus Platform has since many years various XML supporting features that were quite extended in V7. Extensive SOAP, WSDL and UDDI support is one addition. Another is the ability to map freely any XML tag to any Papyrus internal object ID. Our rule language PQL was enhanced to allow the parsing of XML structures. Thus, the Papyrus ObjectSpace can be regarded as a fully-featured XML database, allowing queries for XML tags and values.
We will continue to recommend alternatives to XML where sensible, but happily spend the extra time and ressources to deal with XML if the project demands it. This is in principle the way we have been dealing with XML for the last ten years. Most Papyrus frameworks support since some time the use of XSD for data mapping and the use of XSL to define document components. There is no need to program XSLTs because the mapping into Papyrus object structures is automatic.
Finally: The ISIS Papyrus Platform can be considered to be fully OPEN and a STANDARD. As far as I was told that is what everyone is looking for. You ask and we give it to you!
I think I found this blog via the AIIM website:
My interest in ECM (enterprise content management) is purely based on the value it can deliver to the business. I think much progress has been made, but the focus is still very much on technology. I would start with your users and ask them what would make their lives easier – that would be my feature set. Some of the things business users often ask for seems impossible, but the basic theme I usually get is this: they want the system to handle the difficult, time consuming stuff and shift the complexity away from the human and put it onto the machine. To most users, this was the point of buying the system in the first place.
Here are some suggestions:
- A good ECM should ask the user what to do, rather than the user telling it what to do. For example, multiple choice questions rather than user input fields all over the screen (also called wizard or expert system).
- A good ECM should learn over time and predict answers. ECMs are currently pretty dumb and do not provide value above and beyond what is put into it. A good ECM would create more value in its output than was necessary to input.
- A good ECM should be knowledgeable and able to answer to intelligent queries (way smarter than askjeeves). Interacting with the system should be at least as simple as interacting with a person on the phone.
- In a good ECM, the interfaces that business users interact with should be as clean and simple as the interface to an iPod or Google. The usability bar has been raised.
- Content/Document tagging should be done on the fly by the ECM, not by the user. Business users cannot be in the job of data entry. A good ECM will be smart enough to appropriately tag all content with minimal human intervention.
- The user interface should not have to be upgraded twice a year or even once a year. A good ECM will learn and grow with the business. To business users, a good ECM will feel like we all feel about Google: it’s a part of my day and it’s not something I dread doing – because it does what I want it to do and it’s simple.
I know these are ambitious and it may take some time to get there, but these should be the goals of any future ECM strategy.
End of Quote:
As old as this entry is, it is as valid in 2009. Most ECM products can’t fulfil any of these points. Our Papyrus Platform has been delivering most of those functions for some time now and has added item 6 in 2008.
- ad 1) The Activity Recorder or the Natural Language Rule Editor can be used to create wizards or logic decision trees.
- ad 2) The patented User-Trained Agent actually learns from user activity directly and recommends actions to the business user of the same role.
- ad 3) The Natural Language Rule Editor enables business users to define semantically correct queries and commands based on the business taxonomy.
- ad 4) With the Papyrus EYE user interface an Apple iPhone or Google like GUI is extremely easy to setup without programming. Each user role can have its own specific GUI so that it is not one size fits all.
- ad 5) The content and text classification features of Papyrus can identify recurring content types (scan, email, PDF, more …) and extract the data that will be used to identify the business context of the content. In a new feature it will actually offer business context information while a user is writing an email!
- ad 6) The radically new Papyrus EYE user interface technology enables the business to create user-friendly GUI layouts that are customizable by the business user and support skins.