Subject:XSD Package like XSLT Mapper Author:Norman Katz Date:04 Mar 2005 10:55 PM
I would like to see a way to create a "package" similar to the XSLT Mapper
that lets you bind a document to other documents. In the mapper, it lets
you bind an input file path and output file path to the XSL Transform.
In my requested feature, you could bind an XSD with an XML document (path) so that
you would not have to "associate" the xml document with the schema every time the
XML Document got updated. For instance, our content management system
produces a clean XML document whenever the content authors modify the source
data. The output of the source program does not put the schema in the
header (root node) so the user needs to load the new (clean) xml document into
Stylus Studio each time and then manually associate it with the XSD schema file
so that he can validate and save the schema reference in the header.
I think it makes perfect sense to be able to define a package for an XML document (path)
that automatically associates it with an XSD without having to manually
do the association via your GUI. I'm sure there are lots of other customers
that do XSD validation that would benefit from this feature as well.
Ultimately, it would be nice to build some of the turnkey orchestration
features that are found in your higher end ESB product to allow users to
create their own workflow and/or wizards to drive a whole series of documents
through a validation or transform. I know you've mentioned this to us
in the past so hopefully it is coming. But for now, the package associating
the XSD with my xml document would be very beneficial to our productivity.
Subject:XSD Package like XSLT Mapper Author:Minollo I. Date:04 Mar 2005 11:05 PM
If I well understand what you are asking, that's already possible in Stylus Studio:
- Create a new project folder
- Right click on the folder, and select "Associate Schemas to Folder..."
- Choose the schema(s) you want to validate against
- Add XML documents to the new project folder
Now when you hit "validate" on those XML documents, they will be validated against the schemas associated to the project folder even if the XML document doesn't explicitly reference such schemas.
As long as "workflow/orchestration" go, as promised we are working on XML pipelining; you'll see the results later this year.