Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
First of all ++ to you for taking the time to raise such devious porpoises.
If you are going to build an module to turn XML elements and attributes into perl objects, you might as well base it on a wildely used DTD. It might be hard to generalize without using a solid reference point.

I've just started using DocBook as our DTD and I was surpirsed that there was only one module on the CPAN that specifically addressed DocBook. It is a big DTD with over 300 elements but, it could take you down some interesting roads. It is well documented and there is an active mailing list for you to talk with.

As XML becomes more widely used it seems there will be a need to write interfaces for specific DTDs. Personally I would love to see a module that would let me get/set Sect1 titles or get/set all the document authors and editors. People customize DocBook, and it would be cool if your module could read a DTD and provide an interface to all the elements and attributes that are being used.

I don't know how devious your porpoises are, but, it would be interesting to see if you could 'feed' your module a DTD and have it create an interface to the document.

my $parser = DeviousPorpoises->new(generic.dtd);
Get Strong Together!!

In reply to Re: handling my PerlSAX handler by aardvark
in thread handling my PerlSAX handler by Vynce

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others exploiting the Monastery: (5)
As of 2024-04-19 14:30 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found