I haven't had any problems using xsl without xsd, and am planning to rework the jboss deployment process based on extensive use of xsl transformations, so in particular it would be very easy (supply an xsl script) to deploy stuff using your own in -house dd dtd or ???.
It looks to me as if xsd <--> dtd for schemas and xml <--> xml for documents What am I missing about xsd? david jencks On 2002.02.28 06:01:37 -0500 Holger Baxmann wrote: > another thought: > > is anybody aware of the adavntages of xsd instead of using dtd's ? > somebody is then able to use xsl for changing the underlying metadata > (i.e. jboss.xsd -> xslt -> jboss-ejb-jar.xsd -> xslt -> > any-believeable.xsd -> xslt -> my-prefered.xml). > > Am Don, 2002-02-28 um 02.58 schrieb Jason Dillon: > > It not about waiting or not. Shit man. I just had a thought and > wanted > > to let it out. No need to be so abrasive either. > > > > --jason > > > > > > marc fleury wrote: > > > > >|I believe that his idea would still require a JBoss specific dd, but > I > > > > > >so does yours, mother fucker. > > > > > >|could be wrong. Once that work starts moving then I will bring this > up > > >|again... unless I forget. > > > > > >wait for his unifying XSL thingy, I think there is value, and for what > it is > > >worth I was banging on him in Boston to make sure he keeps it as > backward > > >compatible as possible. > > > > > >marcf > > > > > > > > > > > _______________________________________________ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
