On 8/9/07, <b class="gmail_sendername">Agent Zhang</b> <<a href="mailto:agentzh@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">agentzh@gmail.com</a>> wrote:<div><span class="gmail_quote">
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 8/10/07, Andrew Sterling Hanenkamp <<a href="mailto:sterling@hanenkamp.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">sterling@hanenkamp.com</a>> wrote:<br>> Okay, so after discussions in the other thread about the
<br>> Template::Declare::Tags stuff, the revision here is that the
<br>> Template::Declare::XML would be used to declare a TagSet package that could<br>> then be imported into any template package.<br>><br><br>__And__ it can optionally generate a DTD spec and/or an XML schema file ;)
</blockquote><div><br>Sure, why not?<br><br>Now, should this be another class tied to Template::Declare or something separate? I thought about XML::Declare, but that sounds like you're building XML, which this isn't doing. Not a bad name overall, but I don't know if it's right. How about XML::TagSet as the top-level package and then XML::TagSet::Declare being the Object::Declare with the schema() sub:
<br><br>use XML::TagSet::Declare;<br>use XML::TagSet schema {<br> # blah blah<br>};<br></div><br></div><br>This becomes a supplement to Template::Declare, but as you mentioned, could also be a tool for generating a DTD spec or XML schema as additional parts that could be usable independently of Template::Declare. I dunno though. I think I'm going to give it a shot though, I have some time tonight to play around.
<br><br>Cheers,<br>Andrew<br>