Dick Annicchiarico 25.Jul.05 05:59 PM Lotus Notes Applications Development All Releases All Platforms
I'm taking this informal survey as to what XML/DXL features you would like to see in N/D post-7.0. If you use XML/DXL features or have investigated using them, please take a moment to ponder this list and give your top 3 (or so) answers. Replies that say "I want them all" are not really that helpful (sorry).
Here is a brief list of ideas we have heard from customers and/or come up with ourselves, with a one or two sentence description. This list does not represent any commitment whatsoever from N/D Development.
If you have other ideas, please be as specific as possible as to what you'd like to see.
In no particular order...
?SearchViewEntries: Like ?ReadViewEntries, but view contents are determined by a full-text search. (Is this needed from Exporter APIs as well (in addition to the Web Server))?
?ReadDXL: URL command to get the DXL representation of a document or design element. What are your security concerns? 1+ would be a parameter that could apply an XSLT transform to the DXL and return the result -- how important is the 1+?
DXL Import/Export capability from the Notes Client. Ability to import from DXL files into document(s), ability to export document(s) to DXL files. What are your security / usuability concerns? 1+ would be to apply XSL as well, "E&T" = Export to DXL, Transform, write to file, "T&I" = read from file, Transform to DXL, Import -- how important is the 1+? (Note: XSLT style sheets for transforms would be user-supplied, not part of N/D.)
Ability for all of the Exporter / Importer APIs to easily include transform(s) -- similar to E&T and T&I from previous item. Convenience feature. You can accomplish the same thing with existing APIs, but with a little more work because you have to code up the transformer logic yourself.
HTML generation from DXL: What level of fidelity do you require? 1+ would be to support other formats (e.g. PDF) -- how important is the 1+, and to which formats? Is there alternate format that is more suitable; for example XSL:FO generation from DXL? (Then use any transforms available in the industry to go from XSL:FO to HTML et. al.) Are there open source solutions that eliminate this requirement?
XSLT Style Sheet design element: Possibly needed to support 2., 3., and 4., and maybe 5., if we want the ability for the XSLT style sheet to come from the database rather than a filesystem file or elsewhere.
"URL" class in LotusScript and Java: At a minimum, this would work in conjunction with NotesStream / Stream so that those classes could read a stream of input data from a URL. Major use would be to get input for XML parsers, DXL Importer, or XSLT Transformer from URLs.
Import DXL into some sort of a memory object: Instead of directly creating notes in a database. Pretty sketchy how this would work at this point, but is it an idea worth pursuing?
Mechanism to generate LotusScript/Java classes for working with XML: Idea here would be to take any XML vocabulary (not DXL) and automatically generate (from its schema) classes with properties and methods that allow one to work with the XML data in a language-specific way rather than dealing with the XML directly. Deserialize method would go from XML to objects and serialize from objects to XML.
Provide DXL Exporter capability for transforming notesbitmap to jpeg and/or png. (Already can do notesbitmap -> gif.)
Enhance DXL to improve on some of its quirks. Which quirks of the language bug you? (One example, the structure of a list really isn't well-represented in DXL.) May be a prerequisite to certain items like 5.
DXL Exporter Filtering: Ways to export partial notes by criteria such as "export everything but xyz" or "export only xyz". Largest anticipated usage would be to filter out attachments and graphics, but goal would be to do something more generic than that.
Implement DXL for features that don't yet have a high-level representation in DXL. List includes calendar view, MIME, web service, shared column, OLE, file resource, style sheet resource, layer, outline, replication formula, layout regions, database icon, viewentries, navigator. Are any of these important to you and if so, which few are the most important and how do they balance against the other features above?