|
Apologies for cross posting. Announcing a new release of the “Xml Schema
Lightener” utility. It has been completely updated and is based on
XSLT 2.0. What it does ---------------- It takes an Xml Schema and creates a subset based on user
input by using an XSLT 2.0 stylesheet. Some refer to this with terms such
as a “subset Schema view”, “pruned Schema”,
“LiteBOD”, or “profiled Schema”. Why it does it ---------------- Consider these use cases: 1. You
have an Xml Schema and want to implement a subset (a selected portion) of the
data points. 2. You
have an internal data model in Schema and want to communicate to a trading
partner only the data points necessary for a particular data integration. 3. You
are implementing an Xml Schema acquired from somewhere else (i.e. from a
trading partner, or from a standards consortium such as OAGi, HR-XML, etc.) and
want to implement only the data points relevant to your business context. In all these cases, it would be
useful to create a Schema that shows these points and can be used for
validation. The Xml Schema Lightener allows you to create the contextual
Schema that each of these require. It does it using simple XSLT and
Xml. And a GUI is included to make it easy to use. Plus a second tool ---------------- This comes with a second useful utility, which is a Schema “Flattener”.
This is another XSLT 2.0 solution to the problem of nested includes in Xml
Schema. This takes a set of Schemas and merges all xsd:includes so as to
create the fewest number of schemas (or a stand alone one if there are no
xsd:imports). It performs the include wrap up on all dependent imports as
well. This is included as a free add-on to the Lightener. Cost effective ---------------- This utility is presented with its full functionality in a
very inexpensive package. The $29 (USD) price is not intended to make a
profit, and certainly does *not* cover the cost of development. It
is a simple way to offset a portion of its creation and allow me to keep
working on it. For more information ---------------- See http://www.xmlhelpline.com/tools/
for more information and an FAQ. Cheers, Paul Kiel ===================================================== |