NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Or is it a BUG?"
"Let's call it an accidental feature. :-)"
--Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
[OT] Warning: Perl content (Score:2)
Could you extract the central ideas of that and possibly upload it as a module. I am forced to use XML-Schema at work, and would love to have more perl tools for it.
Yes I know that it is a mess. To quote Andy Wardley:
My conclusion, after spending nearly 6 months working on it, is that it is an utter bastard of a specification written by a committee of Java XML product vendors. 200+ pages of twisted specification(s) that attempts to account for anything that the committee could think they might want to add to their fancy products but wouldn't have a clue how to implement.
But any help would be better than none.
As a side note, I must confess that I enjoy the flame wars^Warguments^Wdiscussions your viewpoints conjure up; please do continue here.
Reply to This
Re:[OT] Warning: Perl content (Score:2)
I get the impression that XML Schema was designed in much the same manner...
-Dom
Re:[OT] Warning: Perl content (Score:3, Interesting)
It's not at all CPAN worthy. It currently only deals with a single namespace, and has some stuff hardwired for SVG (I needed the schema that is just enough to describe a bunch of SVG documents, not the complete one). Adding multinamespace support shouldn't be too hard, though the loops in the data structures will get a bit twisted. Here is the code, raw. It may help you in some ways, you never know, all help is good when it comes to XML Schema ;) If you don't understand the data structure which I know is
-- Robin Berjon [berjon.com]