Re:RE: XSLT vs JSP

[KAREN_LEICHEL@xxxxxxxx]

Hi everyone,

I am one of those "editors" that "find DSSSL and XSL too difficult to use".
Actually, the market for editors/tech writers these days quite often demands
that these people have a working knowledge of not just one, but several
programming languages. I think it is to make up for engineers and SME's that do
not communicate well in English. Apparantly it is easier to teach programming to
writers than to teach communication in English to engineers. Tech writers need
to understand certain programming langueges (or so such companies as IBM and
Cisco think) to produce GUIs as well. In fact, knowing the programming languages
far outweighs having many years of graphics and design experience and a degree
in design when hiring.

I would not worry about the new breed of tech writers/editors having too much
trouble. At companies like mine, there will be one or two who can understand, or
the company will hire a consultant to deal with the DSSSL or XSL.

Having more power and more portability is incredibly important to United Defense
since we are working with extremely large, complex documents and the customer
(DOD) wants--demands--single source databases to make it harder to make
mistakes.

Karey Leichel

____________________Reply Separator____________________
Subject:    RE: XSLT vs JSP
Author: "Didier PH Martin" <martind@xxxxxxxxxxxxx>
Date:       6/27/99 8:09 PM

HI Sebastian,


The point was that DSSSL is too hard too learn for editors. I replied that
DSSSL and XSL both share the same level of difficulties. I'll be more
precise. CSS is easier to learn but also less powerful.  Both DSSSL and XSL
resolve problems you cannot resolve with CSS but also requires more
knowledge. Both DSSSL and XSL are more sophisticated languages than CSS
(this does not include STTS which does transformation).
Like all languages, it requires apprenticeship.

regards
Didier PH Martin
mailto:martind@xxxxxxxxxxxxx
http://www.netfolder.com
-----Original Message-----
From: owner-xsl-list@xxxxxxxxxxxxxxxx
[mailto:owner-xsl-list@xxxxxxxxxxxxxxxx]On Behalf Of Sebastian Rahtz
Sent: Tuesday, June 29, 1999 8:21 AM
To: xsl-list@xxxxxxxxxxxxxxxx
Subject: RE: XSLT vs JSP


Didier PH Martin writes:
 > probably rely on a much simple language like CSS. XSL and DSSSL have, at
 > first sight, for most people about the same level of difficulties. Also,
 > because CSS is based on a kind of property set approach, it can be easily
 > encapsulated with a UI and therefore be more accessible to people without
 > any programming knowledge.
 >
is true, the CSS style editor in XMetal is really rather useable. if
CSS is what you want.

take a fragment like <url doc="http://x.y.z"/>[1] and tell me how to
show the damned URL with CSS....

never mind taking  <x idref="XX"/> and replacing it with the contents
of <code id="XX">Goodbye Cruel World</code>!

sebastian

[1] so that doc can be declared as an ENTITY notation, forcing me to
store my URLs nicely somewhere


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
Received: from portal.udlp.com ([192.169.4.225]) by ccmail.udlp.com with SMTP
  (IMA Internet Exchange 3.12) id 00048010; Tue, 29 Jun 1999 07:55:47 -0500
Received: from portal.udlp.com (root@localhost)
    by portal.udlp.com with ESMTP id HAA11808
    for <KAREN_LEICHEL@xxxxxxxx>; Tue, 29 Jun 1999 07:57:28 -0500 (CDT)
Received: from web4-1.ability.net (web4-1.ability.net [216.32.69.9])
    by portal.udlp.com with ESMTP id HAA11798
    for <KAREN_LEICHEL@xxxxxxxx>; Tue, 29 Jun 1999 07:57:27 -0500 (CDT)
Received: from mulberrytech.com 
    by web4-1.ability.net (8.9.1/8.9.1) with ESMTP id HAA00841  Tue, 29 Jun 1999
07:52:23 -0400 (EDT)
Received: (from majordom@localhost)
    by mulberrytech.com (8.8.5/8.8.5) id HAA00839
    Tue, 29 Jun 1999 07:52:23 -0400 (EDT)
From: "Didier PH Martin" <martind@xxxxxxxxxxxxx>
To: <xsl-list@xxxxxxxxxxxxxxxx>
Subject: RE: XSLT vs JSP
Date: Sun, 27 Jun 1999 20:09:36 -0400
Message-ID: <NBBBJPGDLPIHJGEHAKBAIECBDKAA.martind@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2212 (4.71.2419.0)
In-reply-to: <14200.47640.153679.4943@xxxxxxxxxxxxxxxxxx>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-xsl-list@xxxxxxxxxxxxxxxx
Precedence: bulk
Reply-To: xsl-list@xxxxxxxxxxxxxxxx


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list