XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Show tree view Topic
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Postnext
Meeraj KunnumpurathSubject: Legacy Format Handling
Author: Meeraj Kunnumpurath
Date: 15 Feb 2012 05:29 AM
Hi,

I have the following need in an application implemented on the server using Java.

1. We have a canonical model described using XSD
2. Users can submit files in arbitrary formats as long as those formats are registered on the system
3. We need to transform the legacy format at runtime to the canonical internal format

The solution I have in mind is as follows ..

1. The users will use Stylus STudio to define the grammar for the legacy format and the translation to the canonical format
2. These assets are then registered on the system against a name identifier
3. They specify the format identifier from 2 when they submit a file
4. The system uses some Stylus API at runtime to parse and translate the file submitted by the user to the internal canonical XML format

This assumes ..

1. Stylus offers a means of mapping legacy formats to an XML format defined using XSD
2. These mapping can be exported to something that can be understood by a Stylus API at runtime
3. This API can be used at runtime for parsing and transforming files coming in the legacy format to the canonical XML format.

Could someone please confirm this is possible? If yes, where can I find further information on the details?

Kind regards
Meeraj

Postnext
Ivan PedruzziSubject: Legacy Format Handling
Author: Ivan Pedruzzi
Date: 15 Feb 2012 10:46 AM

Hi Meeraj,

What you are describing is one of the most common Stylus Studio use cases.

Here is one approach in broad strokes:

Your user should be allowed to register two kinds of information the inbound document type and a mapping designed with the Stylus Studio XQuery mapping tool.

The document type could either be a Stylus Studio built-in type ( CSV, EDI, SYLK, etc.) or a .conv file created with the Stylus Studio Convert to XML module.

On the server you could use our Java runtime components: XML Converters and DataDirect XQuery to convert and to translate the inbound documents into the canonical XML model.

If you desire to discuss such architecture in details please contact us at stylussupport@ivitechnologies.com

Hope this helps
Ivan Pedruzzi
Stylus Studio Team

Posttop
Meeraj KunnumpurathSubject: Legacy Format Handling
Author: Meeraj Kunnumpurath
Date: 16 Feb 2012 08:50 AM
Thanks Ivan for the quick reply. I have a couple more follow up questions, I assume the best way to take it is with the support email?

Kind regards
Meeraj

 
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.