1 January 2010
We had deployed our services onto newer, faster Railo-powered server. Railo gaining more and more support as lowcost but powerful CFML engine. As dedicated CFML team, Ziost cannot stand apart of emerging technology and offering CFML development targeting Railo as well as Adobe Coldfusion.
Best wishes for 2010 for everyone !
29 July 2009
Ziost released it's content management system to public as open-source project. Ziost CMS is now available for download and free use: Ziost Labs announcement.
12 January 2009
Yesterday there was signed a contract between top management of
HIPAASpace - www.HIPAASpace.com (the largest provider of Medical Coding
and Billing solutions in US) and Ziost Technologies. As a part of this
contract Ziost will be a main vendor of Medical Coding and Billing SDK
for HIPAASpace products.
2 September 2008
Powerful CMS SDK with several base implementations for different domains has been recently released by Ziost Labs subdivision
23 May 2008
IBE Corp. is one of the biggest providers of media processing SDK and related solutions. IBE contracted Ziost to provide high-tech modules for the media conversion and on-line stream media processing modules.
|
Technology
XSL
XSL is a language for expressing style sheets. An XSL style sheet is, like with CSS, a file that describes how to display an XML document of a given type. XSL shares the functionality and is
compatible with CSS2 (although it uses a different syntax). It also
adds:
- A transformation language for XML documents: XSLT. Originally
intended to perform complex styling operations, like the generation of
tables of contents and indexes, it is now used as a general purpose XML
processing language. XSLT is thus widely used for purposes other than
XSL, like generating HTML web pages from XML data.
- Advanced styling features, expressed by an XML document type which
defines a set of elements called Formatting Objects, and attributes (in
part borrowed from CSS2 properties and adding more complex ones.
XSL uses a XML notation, CSS uses its own. In CSS, the formatting
object tree is almost the same as the source tree, and inheritance of
formatting properties is on the source tree. In XSL, the formatting
object tree can be radically different from the source tree, and
inheritance of formatting properties is on the formatting object tree.
Aside from these technical differences, mature implementations of
CSS1 and (parts of) CSS2 are available, whilst XSL is currently too new
to have mature browser and content-authoring support.
XSLT is designed for use as part of XSL, which is a stylesheet
language for XML. In addition to XSLT, XSL includes an XML vocabulary
for specifying formatting. XSL specifies the styling of an XML document
by using XSLT to describe how the document is transformed into another
XML document that uses the formatting vocabulary.
XSLT is also designed to be used independently of XSL. However, XSLT
is not intended as a completely general-purpose XML transformation
language. Rather it is designed primarily for the kinds of
transformations that are needed when XSLT is used as part of XSL.
This specification defines the syntax and semantics of the XSLT
language. A transformation in the XSLT language is expressed as a
well-formed XML document [XML] conforming to the Namespaces in XML
Recommendation [XML Names], which may include both elements that are
defined by XSLT and elements that are not defined by XSLT. XSLT-defined
elements are distinguished by belonging to a specific XML namespace
(see [2.1 XSLT Namespace]), which is referred to in this specification
as the XSLT namespace. Thus this specification is a definition of the
syntax and semantics of the XSLT namespace.
A transformation expressed in XSLT describes rules for transforming
a source tree into a result tree. The transformation is achieved by
associating patterns with templates. A pattern is matched against
elements in the source tree. A template is instantiated to create part
of the result tree. The result tree is separate from the source tree.
The structure of the result tree can be completely different from the
structure of the source tree. In constructing the result tree, elements
from the source tree can be filtered and reordered, and arbitrary
structure can be added.
A transformation expressed in XSLT is called a stylesheet. This is
because, in the case when XSLT is transforming into the XSL formatting
vocabulary, the transformation functions as a stylesheet.
A stylesheet contains a set of template rules. A template rule has
two parts: a pattern which is matched against nodes in the source tree
and a template which can be instantiated to form part of the result
tree. This allows a stylesheet to be applicable to a wide class of
documents that have similar source tree structures.
A template is instantiated for a particular source element to create
part of the result tree. A template can contain elements that specify
literal result element structure. A template can also contain elements
from the XSLT namespace that are instructions for creating result tree
fragments. When a template is instantiated, each instruction is
executed and replaced by the result tree fragment that it creates.
Instructions can select and process descendant source elements.
Processing a descendant element creates a result tree fragment by
finding the applicable template rule and instantiating its template.
Note that elements are only processed when they have been selected by
the execution of an instruction. The result tree is constructed by
finding the template rule for the root node and instantiating its
template.
In the process of finding the applicable template rule, more than
one template rule may have a pattern that matches a given element.
However, only one template rule will be applied.
A single template by itself has considerable power: it can create
structures of arbitrary complexity; it can pull string values out of
arbitrary locations in the source tree; it can generate structures that
are repeated according to the occurrence of elements in the source
tree. For simple transformations where the structure of the result tree
is independent of the structure of the source tree, a stylesheet can
often consist of only a single template, which functions as a template
for the complete result tree. Transformations on XML documents that
represent data are often of this kind. XSLT allows a simplified syntax
for such stylesheets.
When a template is instantiated, it is always instantiated with
respect to a current node and a current node list. The current node is
always a member of the current node list. Many operations in XSLT are
relative to the current node. Only a few instructions change the
current node list or the current node ; during the instantiation of one
of these instructions, the current node list changes to a new list of
nodes and each member of this new list becomes the current node in
turn; after the instantiation of the instruction is complete, the
current node and current node list revert to what they were before the
instruction was instantiated.
XSLT makes use of the expression language defined by [XPath] for
selecting elements for processing, for conditional processing and for
generating text.
XSLT provides two "hooks" for extending the language, one hook for
extending the set of instruction elements used in templates and one
hook for extending the set of functions used in XPath expressions.
These hooks are both based on XML namespaces. This version of XSLT does
not define a mechanism for implementing the hooks.
NOTE:The XSL WG intends to define such a mechanism in a future version of this specification or in a separate specification.
The MIME media types text/xml and application/xml [RFC2376] should
be used for XSLT stylesheets. It is possible that a media type will be
registered specifically for XSLT stylesheets; if and when it is, that
media type may also be used.
|
Small Business
We've started a programm of assisting for startup companies with
establishing their business at the IT sphere, this includes...
Big Companies
Business profit for big companies in working with Ziost can be shown in different approaches...
WORK FOR ZIOST
Junior Adobe Coldfusion Developer
Looking for the Adobe Coldfusion Developer. Base requirements: Adobe Coldfusion 8, Custom Tags development, CFC, MySQL, MS SQL.
Senior Java Developer
Senior Java Developer is needed for the full-time work. Base requirements: 3+ years of experience, J2EE 1.4, 1.5, 1.6; Java Beans, EJB, SOA, WebServices
Senior C# Developer
Ziost .NET Applications team is looking for the senior C# developer. Main domain of knowledge is UI WPF applications and ASP.NET/Silverlight applications.
Designer
Looking for web designer for creation of production-level visual design.
HTML/CSS coder
Looking for HTML/CSS coder for creating HTML layouts.
|