|
|
 next
|
  Subject: Re: Stylus Studio Interoperability and Vendor Stability
Author: Minollo I.
Date: 08 Mar 2005 10:59 AM
|
Gene,
as already mentioned, Stylus Studio is an IDE targeted at XML
development; I would guess that the question about "interoperability" can
apply only to the following concepts:
- Stylus Studio supports standards: XML, XML Schema, DTD, XSLT, XQuery
- Stylus Studio supports several XQuery and XSLT processors out of the
box: Xalan-J, Saxon, MSXML, .NET processor, MarkLogic
- Stylus Studio supports several XML Schema validation engines out of
the box: Xerces C++, Xerces J, MSXML, .NET, XSV
- Stylus Studio supports an extended concept of "file system", and users
can extend it creating their own file system Java implementation
- Stylus Studio is able out of the box to manipulate data originated by
Web Service calls, stored in relational databases or in Sleepycat DB XML,
available through HTTP, HTTPS, FTP or stored on the local file system
- Stylus Studio file system and adapters are available as a Java API
that can be integrated in any Java application
You may want to direct Sonic Software questions to the Sonic organization
(http://www.sonicsoftware.com); Stylus Studio and Sonic Software share the
same parent company (Progress Corporation), but they are two separate
divisions (Stylus Studio is part of DataDirect). Sonic Software's
Integration Workbench is based on some of the Stylus Studio functionality
and UI.
Hope this helps,
Minollo
|
|
next
|
Subject: Re: Stylus Studio Interoperability and Vendor Stability
Author: Minollo I.
Date: 08 Mar 2005 11:29 AM
|
>...
>1) How well does Stylus Studio adhere to W3C standards?
Stylus Studio relies on components like Apache Xerces, Saxon, Apache FOP,
XSV (just to mention a few) that are recognized for their strict adherence
to standards.
>2) Does the Epic Editor have any proprietary extensions, i.e. is the
>tool output “vendor specific”? Is there any “vendor locking”? What
is
>it? Are there any vendor specific tags or code elements that would allow
>the tool output to be used only on vendor’s proprietary production
servers?
Epic Editor is a different product, unrelated to Stylus Studio.
If you meant to ask about the Stylus Studio editors, there is no vendor
specific locking.
>3) What are the XSL-FO processors supported by the software?
We bundle Apache FOP, but you can easily configure different processors,
like RenderX.
>4) Are there any samples (printer output –hard copy) of PDF or
>PostScript files generated by XSL-FO processor?
If you open the standard examples shipped with Stylus Studio, you will find
a couple of XSL-FO examples. Rendering of XSL-FO relies on 3rd party
components.
>5) Stylus Studio reuse transforms generated by other tools (from
>other vendors)?
As long as they are standard XSLT/XQuery, you will be able to use them
inside Stylus Studio.
>6) How many different software versions have been released from the
>moment of the product’s original design? Are there services
>packs/patches to compliment prior versions of the software?
Stylus Studio is shipping version 6 Release 2; the first version went out
in 1999; you can do some math to estimate how many versions have been
released since then. We regularly issue service packs for any version of
the software which hasn't been discontinued for more than one year (take a
look at http://www.stylusstudio.com/update for example).
Hope this helps,
Minollo
|
|
|
|
|
top