Some of you might have experienced it, too. You work with an XML document whose structure is complicated. Constructing XPath queries becomes boring at last, even in an interactive XML processing tool like XML::XSH2. A diagram would help.
Here is a short xsh script that creates a dot source code. Just pipe its output to dot to get a nice graphical representation of the XML structure!
# xml2dot.xsh
# Author: E. Choroba 2013
open {$ARGV[0]} ;
my $count ;
def processNonRec $type $parent $node {
my $name = $type ;
perl { $name .= $count->{"*$type"}++ } ;
echo :s '"' $parent '"' " -> " '"' $name '"' ;
echo :s '"' $name '" [label="' $type '()"]' ;
}
def processNode $parent $node {
my $label = name($node);
my $name ;
perl { $name = $label."=".$count->{$label}++ } ;
echo :s '"' $parent '"' " -> " '"' $name '"' ;
if $node/self::* {
if (count($node/../*[name()=$label]) > 1) {
my $num = count($node/preceding-sibling::*[name()=$label])
+ ;
$label = concat($label,"[",$num+1,"]") ;
}
} else {
$label = concat("@",$label) ;
}
echo :s '"' $name '" [label="' $label '"]' ;
for ($node/*
| $node/@*
| $node/text()
| $node/comment()
| $node/processing-instruction()) {
if self::* processNode $name (.) ;
if count(.|../@*)=count(../@*) processNode $name (.) ;
if self::text() processNonRec 'text' $name (.) ;
if self::comment() processNonRec 'comment' $name (.) ;
if self::processing-instruction() processNonRec 'pi' $name (.)
+ ;
}
}
echo 'strict digraph' name() '{' ;
echo 'node [shape=box]' ;
processNode "document" /* ;
echo '}' ;
Example usage:
xsh -al xml2dot.xsh data.xml | dot -Tpng > data.png
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|