[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Re: [xsl] Re: Microsoft XML
Subject: Re: [xsl] Re: Microsoft XML From: "Robert Koberg" <rob@xxxxxxxxxx> Date: Wed, 15 Aug 2001 07:27:14 -0700 |
if it is XML it is XML. You can make your own set of tags to do what you want it to. For example XSLT is XML and Docbook (what Brett probably used to write his book) XML is XML. They are not interchangeable they have been designed for specific purposes. The statement you site below seems somewhat biased. Microsoft has conformance and then more on top of that... they even just announced w3c compliant schema support to the w3cschema list... but whatever... It sounds like you have a good grasp of what needs to be done. I forgot what your problem is/was and how it relates to XSL? ----- Original Message ----- From: "Mark Galbreath" <mgalbrea@xxxxxxxxxxxxxx> To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx> Sent: Wednesday, August 15, 2001 7:10 AM Subject: [xsl] Re: Microsoft XML > Admittedly, I am new to XML/XSL; this is from Brett McLaughlin's "Java and XML," (O'Reilly 2000): > > "The Microsoft parser has been intentionally left out of this list; from all appearances, Microsoft does not now or in the future intend to conform to W3C standards. Instead, Microsoft seems to be developing their own flavor of XML. We have seen this before...be careful if you are forced to use Microsoft's parser" (p. 24). > > Brett McLaughlin, as you probably know, has teamed up with Jason Hunter ("Java Servlet Programming" (O'Reilly 2001) and James Duncan Davidson (author of the JAXP specification) to create JDOM (now at RC-7). > > As for my requirements, the client has a legacy SQLServer 7.0 databse. The idea is to permit its web content authors to change text and graphics through an admin interface based on XML templates that are tranformed via XSLT to HTML. > > Cheers! > Mark > > > From: "Robert Koberg" <rob@xxxxxxxxxx> > > Date: 2001/08/15 Wed AM 09:27:09 EDT > > > > MS has no way to propriatize XML. If you are saying that Oracle has one way > > to handle XML and MS has another then you would be more accurate. > > > > First, why do you need SQL server? Are you going to store content as blobs > > or are you going to break apart the document for searches? What kind of > > documents? Are you sure the filesystem will not work (load the XML (or > > references to) at server startup)? This is often the best option especially > > for a pre-generated site. > > > > Here is a free middleware solution for XML to RDB: > > http://www.rpbourret.com/xmldbms/ -- this guy (Ron Bourret) also maintains a > > long list of XML DB solutions) > > > > There is also the Native XML DB option. But your client probabaly already > > owns MS SQL... > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] Re: Microsoft XML, Mark Galbreath | Thread | Re: [xsl] Re: Microsoft XML, Michael Beddow |
[xsl] Re: Microsoft XML, Mark Galbreath | Date | Re: [xsl] Re: Microsoft XML, Michael Beddow |
Month |