Home Home Page Concepts, terms and bases Java-skriptovanija Use XML/XSL for the publication in Web Chemistry XML/XSL Transparency in CSS Opera Mozilla Attribute HTTP-EQUIV Keywords for beginning Example of a universal script for processing HTML-forms Variable CGI environments Windows CGI the interface How to use Javascript a file from resources Script of management of a tree The simple search engine on Perl Format and syntax Cookie Effective links It is necessary to refer to what sites? (proceeding links) Meta-search - the best friend Pro and contra meta-search engines Links

topic

Chemistry XML/XSL



Chemistry on the party{side} of the client


Last process - process of transformation - can be carried out on the party{side} of the client: the newest browsers understand xml and styles for them, able to connect styles to xml-documents and to form the final document. The principle of job is similar that occurs to a html-file and prilinkovannym to it{him} a css-file. Now xml/xsl-transformation can carry out IE 5 +, Netscape 6, Mozilla.


The variant of transformation on the party{side} of the client is rather attractive. Modern computers are powerful enough to cope with such problem{task}. Thus loading is essentially reduced to the server, and the style table is loaded only once. However now still{even} early to publish XML-documents in the Internet " it is simple so " - for Web is HTML, means it{him} and it is necessary to give the user. And besides, what to do{make} in case of those browsers which do not understand high-grade HTML and cannot carry out xmlxsl-transformation? For this purpose the application of style to the XML-document is carried out on the server.



Chemistry on the party{side} of the server


Be done{made} it can in two ways: manually, or automatically.


You can collect a collection of xml-files and style tables and manually otkompilirovat` them, and on the server to lay out only the received files. But it can be made and automatically. For this purpose the special system as which example can serve Cocoon is used.


The system is engaged in that, that, working on the web-server, does{makes} required transformation of the xml-document automatically before giving his{its} user. Technically accommodation of similar system on the web-server differs nothing from installation SSI or PHP3 processors. Thus resources at the user are not selected and, that the most important, to the user is not required the browser, capable to carry out xsl-transformation. Also, if to us will want to use most the newest both fast xml-parserom and the xsl-converter - to us of it{him} enough to establish on the server and to not worry about that, for example, whether owner IE5 has updated the parser, that went complete with a browser, up to the freshest version which corresponds{meets} to standards W3C.


The Web-server in this variant turns to system of the publication (Publishing Framework). As against usual servers which in reply to search give out a file stored{kept} on the server, publishing the web-server gives out the "published" version of a file which corresponds{meets} to parameters of search, to a browser of the visitor, his{its} adjustments and-or preferences. For example, if the search is done{made} by program Acrobat Reader, the published page will come to the visitor in format PDF. of the WAP-device (Wireless Application Protocol) will receive WML-starnicu (Wireless Markup Language), and a usual Web-browser - the HTML-page, more advanced - XHTML-page.


In a case with a Web-browser it is possible even to choose between various variants and even versions of the program. And to give out the various document depending on, whether there has come search from browser Lynx which can show only the text, from Netscape Navigator 3/4.7/6.2 or from Microsoft Internet Explorer. The visitor of a site does not see the initial version of a file (stored{kept} in xml), she to him and it is not required, but at the same time he does not specify obviously, that the xml-file needs to be transformed to any version. All this is done{made} completely automatically.


Certainly loading because of it grows by the server, but also advantages in it too are. The same xml-document with ease can be sent as supernavorochennomu to a browser (IE), and to the elementary variant (Lynx, Netscape 3), or to their microcolleagues - to the browsers which have been built - in mobile phones (WAP/i-mode), or in general such exotic variants, as to voice browsers or browsers for blind (code Brejlja). Moreover with use of special libraries and small shifts it is possible to separate really the maintenance{contents} of the document from his{its} performance and to submit it{him} as a pdf-file or a Excel-file, gif/png/jpeg/svg - a picture.

Back to production of a problem{task}


I not vedu speech about a platform for the publication of any content for any browser though in the theory and it is possible. The content for mobile phones and for high-grade browsers should be miscellaneous. Differences consist in volume of the submitted information, in the order and logic of its{her} performance, in registration and navigation. Founders of texts for a site always should write the different texts intended for usual browsers and for their truncated colleagues. If someone comes to you and speaks, that " having bought our product, you can write the text once, and he will be automatically altered under any known browser ", know, to you simply hang up noodles on ears. I can save the text of " the Divine comedy " dante in HTML and hang out on a site, and users IE and Netscape though and creaking teeth, but can load and read 200 pages of the text. And now present what will read this text in a browser, whose window on the size is equal match a box.


Therefore our purpose - to submit the same content for polytypic browsers of one order. Or we create a site which the same maintenance{contents} for all high-grade browsers (IE, Netscape, Mozilla, Opera, Lynx and so forth can give), or a site which gives out the same maintenance{contents} for all "truncated" browsers (various mobile phones, PDA, voice browsers and so forth).

... By the way


Except for problems{tasks} of visual performance of the information, the XML-technology can be used with success in the decision of problems{tasks} of an exchange and a data storage. XML can be used, for example, for storage of the configuration information. It is provided with that, that functions parsera (interpreter) XML are built - in many means of development of applications. And the most important, that, that the XML-document can be edited with the help of the most usual text editor. I.e. the data stored{kept} in the XML-document can be passed from the program in the program and remain thus understandable to the person (human readable).