RE: [xsl] xsl:sort in old MSXML

Subject: RE: [xsl] xsl:sort in old MSXML
From: "Claudio Russo" <crusso@xxxxxxxxxxxxxxxxx>
Date: Wed, 2 Jul 2003 09:52:18 -0300

Yes, I agree that XSLT fits right for the XML data than any other (language), since looks an extension of the grammatical rules that applies to XML.

Also, for sure, there would be application instances where one would like to have certain XSLT instructions inside an XML (eg: security constraints).

You mention also before "run on the XML source in batches". What do you mean by that?


-----Original Message-----
From: Wendell Piez [mailto:wapiez@xxxxxxxxxxxxxxxx]
Sent: Martes, 01 de Julio de 2003 06:18 p.m.
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE: [xsl] xsl:sort in old MSXML


Sorry I confused you with my typo.

At 03:54 PM 7/1/2003, you wrote:
>I don't get the Procedural one. In your msg you've said "write XML at home 
>and convert it into HTML". I think from this excerpt that you mean that 
>instructions can be kept and run inside an XML file. I still don't get 
>how. I only associate the process to de XSL language, providing an HTML output.

No, you're correct -- typically the instructions on how to get HTML out of 
XML will be kept outside the XML.

(Although to be complete, it should be mentioned that Architectural 
Forms-like techniques can be used to bind such "instructions" "within" the 
XML; in any case you'll still need some kind of external application to do 
the conversion.)

Don't make the mistake of assuming, however, that this architecture 
requires XSLT. There are many ways (as Jonathan R. has recently reminded 
us) of converting XML to HTML, such as Perl, Python or whatever. They're 
just not in scope for this list.

>This is why I asked David to let me know where on earth I can find a 
>conceptual model of the whole architecture.
>It still puzzels me how the data-process-presentation three tiered layout 
>is kept with all this tools/languages/transformations/schemas.

Conceptual architecture:

  XML           -->   XSLT engine       --> output (HTML, PDF etc.)
   ^ validation        ^ transformation
  schema              stylesheet

My only point is that the middle piece doesn't have to happen in a server 
or a client: it can be standalone and run on the XML source in batches.

Another point of confusion is that the middle part doesn't actually have to 
be XSLT, though XSLT excels at this role (since it was designed for it).


Wendell Piez                            mailto:wapiez@xxxxxxxxxxxxxxxx
Mulberry Technologies, Inc.      
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
   Mulberry Technologies: A Consultancy Specializing in SGML and XML

 XSL-List info and archive:

 XSL-List info and archive:

Current Thread