0
2
Over the weekend I finished the presentation and sample files for next week Thursday webcast
"Non-XML Data Processing (2/2) Advanced Webcast on Oct 13, 2011"
http://www.ibm.com/developerworks/forums/thread.jspa?threadID=390124
Tomorrow will be the first of the webcasts, see the dial in details under the following link
"Non-XML Data Processing (1/2) Basics and Encoding Webcast on Oct 6, 2011"
"Non-XML Data Processing (2/2) Advanced Webcast on Oct 13, 2011"
http://www.ibm.com/developerworks/forums/thread.jspa?threadID=390124
Tomorrow will be the first of the webcasts, see the dial in details under the following link
"Non-XML Data Processing (1/2) Basics and Encoding Webcast on Oct 6, 2011"
This is the Agenda for tomorrow
- DataPower Non-XML data processing
- Non-XML stylesheet I/O
- “secure” conversions
- FFD types “hexBinary” and “base64Binary”
- XML node types, BinaryNode DataPower extension
- FFD types “binaryNode” and “String”
- DataPower internal encoding is UTF-8
- magnifying-glass.xsl
- Non-XML stylesheet I/O completely based on shipped FFD
- Probe (Extension Trace)
- Safety of type=”String” input mappings
- validate.utf-8.input.xsl
You may find a different interesting topic in this posting and its attachment:
The question was "where to find the classes available for SOMA".
The 1st answer was "look into store:///xml-mgmt.xsd".
A better answer based on XPath expression even answers how many classes there are (varies by appliance model and firmware):
A better answer based on XPath expression even answers how many classes there are (varies by appliance model and firmware):
# xpath++ "count(//xs:complexType[xs:complexContent/xs:extension[starts-with(@base,'tns:Config') or starts-with(@base,'Config')]])" xml-mgmt.xsd
175
#
Attached to that posting is file classes.401.html, a "block" hierarchy diagram of DataPower class hierarchy
(everything staring at "ConfigBase").
In the following posting
http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14689773#14689773stylesheet classes.xsl which generated that diagram is attached and discussed a little bit.
You might be interested in "graph extraction" from XML data and Depth-First-Search traversal of the extracted graph
which was used to generate the "block" hierarchy diagram. Also the simple and nice heuristic which allows
which was used to generate the "block" hierarchy diagram. Also the simple and nice heuristic which allows
to allocate exactly the vertical space needed for a node in the diagram is interesting -- in "XML speak" instead of "graph speak"
it would be "count(descendant-or-self::*)" ...
Hermann.
Hermann.
