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
Conferences Close Tree View
+ Stylus Studio Feature Requests (1141)
+ Stylus Studio Technical Forum (14070)
- Website Feedback (244)
-> - Chrome seems to post duplicate... (1)
-> - SSDN was under attack (1)
-> + Add SS to Wikipedia comparison... (2)
-> - can't uninstall StylusStudio (1)
-> - Hi (1)
-> - cannot get evaluation key (1)
-> + difficult (6)
-> - difficult (1)
-> - License Authentication Failed. (1)
-> + Msg for SSDN Admin (2)
-> - Where is there a Changelog for... (1)
-> - Stylus Studio amount of dedica... (1)
-> + Problems with Evaluation Key (3)
-> + AUP Upgrade to the Studio 2011... (2)
-> + Forum thread list: Add name to... (2)
-> + OSs Supported by Current Versi... (2)
-> + not able to email to stylusstu... (6)
-> + HTML to XSLT (2)
-> - Validate XML (1)
-> + Order of website search result... (2)
-> + ver 2010 download size (3)
-> + A system error occured while s... (2)
-> - email digest URLs (1)
-> + Questions on Licensing per use... (2)
-> + Unable to download Stylus Stud... (5)
-> + Contace Email Not Working (2)
-> + Phone Number (3)
-> + Can't find a form on the site ... (2)
-> + XSLT WYSIWYG (3)
-> - What powers this board? (1)
-> - Flash Demo on your site needs ... (1)
-> + error on opening Stylus Studio (6)
-> + Disappearing message contents ... (3)
-> + Inconsistent usage of quotes i... (5)
-> + Updates . Build version (web p... (4)
-> + ide.chm file (2)
-> + XmlDex list (2)
-> - Search options? (1)
-> + Endless loop in upload of atta... (7)
-> + http://www.stylusstudio.com/co... (3)
-> - From AOL/Google Sponsored Link... (1)
-> + Evaluation key not sent to my ... (2)
-> + New to this|| MySQL (3)
-> + trialware problem (2)
-> + Page Missing Link (2)
-> + email gateway only one way now... (3)
-> + XSLT Stylesheet Editor (2)
-> + Registering Stylus Studio (2)
-> + New to all this! (3)
-> + DTD Parser page - under constr... (2)
-> + fop component (2)
-> + Problem in converting XML Sche... (2)
-> + Problems with the java binding... (3)
-> + Questions/suggestions about th... (3)
-> + XML RECORD (2)
-> + SSDN Performance (2)
-> - X12 to XML (837) (7)
-> ->X12 to XML (837)
-> ->X12 to XML (837)
-> ->X12 to XML (837)
-> ->X12 to XML (837)
-> ->X12 to XML (837)
-> ->X12 to XML (837)
-> + Please describe summary of enh... (2)
-> + trailware problems (6)
-> + Typo in File upload window (2)
-> + Video plays too quickly (4)
-> + Privacy policy violated (3)
-> - Developer Network User Info di... (1)
-> + email postings to 'stylus-stud... (2)
-> + Possible to URL decode content... (4)
-> + What email address do I send p... (2)
-> + Error When Attempting to (2)
-> + Editing posts & a suggestion. (3)
-> - July Newsletter: The Stylus St... (1)
-> + Document Wizards: dtd to xml ... (2)
-> + Help documents not helpful (3)
-> - New Stylus Scoop Newsletter (1)
-> + How do I unsubscribe from your... (3)
-> - SSDN is now faster (1)
-> + Topic is truncated when doing ... (2)
-> + Posting on your conference boa... (2)
-> - What a scoop!! February Newsle... (1)
-> - Auto log out is VERY frustrati... (1)
-> - Focus on XQuery - Stylus Scoop... (1)
-> + Probs on competitive upgrade p... (2)
-> - December Newsletter - Focus on... (1)
-> + both pointers for xquery tutor... (4)
-> - Product Review: Stylus Studio ... (1)
-> - Thread deletion (1)
-> + Evaluation download (5)
-> - New Stylus Studio Ad - Solving... (1)
-> - October Stylus Studio Newslett... (1)
-> - New Parent treenode - most vie... (1)
-> + thanks for extra work (2)
-> + navigation javascript issues (4)
-> - The Stylus Scoop September Iss... (1)
-> + View thread by user (2)
-> + Folder marked as read (2)
-> - XML technology talk with Dr. M... (1)
-> + Set a thread flag to "review" (4)
-> - Stylus Studio Website now in B... (1)
-> + American date time format (4)
-> + Topics and their Date time sta... (2)
-> + Your website - great (2)
-> + Stylus Studio T-Shirts Have Be... (2)
-> - Links now working in SSDN XML ... (1)
-> + post text box way to narrow (3)
-- [1-20] [21-40] [41-60] Next
+ XSLT Help and Discussion (7505)
+ XQuery Help and Discussion (1890)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (361)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Dan CooperSubject: X12 to XML (837)
Author: Dan Cooper
Date: 08 May 2006 10:10 PM
I am a new user of the trial version and am exploring the features of Stylus. I am trying to convert an X12 to XML via EDI 837 adaptor. The 837 Schema looks good for my use with a few custom modification to fit our databases. However I seem to be missing a step. How do I apply the schema to a X12 file?

Postnext
Ivan PedruzziSubject: X12 to XML (837)
Author: Ivan Pedruzzi
Date: 08 May 2006 11:34 PM
Hi Dan,

What do you mean by "apply the schema to a X12 file"?

If you need to convert X12 to XML take a look at
http://www.stylusstudio.com/edi/X12_translate.html

You can also use the schema to validate the resulting XML document.

Hope this helps
Ivan Pedruzzi
Stylus Studio Team

Postnext
Dan CooperSubject: X12 to XML (837)
Author: Dan Cooper
Date: 09 May 2006 04:34 PM
Ivan, the first item I am trying to do is create an XML file from an X12 file using your 837 EDI convertor. I see the XSD created by Stylus but not the resultant XML. Then I would like to convert the XML to our in house format. How is this accomplished. XLST or modifing the 837 convertor to a customer convertor?

Postnext
Tony LavinioSubject: X12 to XML (837)
Author: Tony Lavinio
Date: 09 May 2006 04:54 PM
>Ivan, the first item I am trying to do is create an XML file from an
>X12 file using your 837 EDI convertor. I see the XSD created by
>Stylus but not the resultant XML.

Try File|Open, choose your EDI file, check the box that says 'open with
adapter', and then press Open. On the next dialog, choose EDI adapter
and press OK, and you will have the EDI as XML.

>Then I would like to convert the XML to our in house format. How
>is this accomplished. XLST or modifing the 837 convertor to
>a customer convertor?

Take that same URL that was just built (it will look like adapter:...)
and use it as the input to XSLT. Or, build the schema that corresponds
to the version of X12 you are using via the File|Document Wizards|X12
to XSD Wizard, and use that as the source for the XSLT mapper.

There should be no need for a custom converter.

Postnext
Dan CooperSubject: X12 to XML (837)
Author: Dan Cooper
Date: 10 May 2006 03:24 PM
I have created an XML document labeled 837XML from an X12 document based on the EDI 837 convertor. The result is as expected. Now I need to convert to our in-house format which is similiar to the standard the XML document created above (837XML). I have input the 837XML document as the source input to the XSLT mapper and a modified version of the 837XML XSD as the target document. Is there a way to map all common fields automatically (i.e., /+) rather than one at a time. I assume this will output an XML document in our in-house format. If so my thought is I can use the modified XSD directly rahter than the 837 convertor. Is this correct? If so, how.
Thanks

Postnext
Tony LavinioSubject: X12 to XML (837)
Author: Tony Lavinio
Date: 11 May 2006 12:58 AM
>I have created an XML document
>labeled 837XML from an X12
>document based on the EDI 837
>convertor. The result is as
>expected. Now I need to
>convert to our in-house format
>which is similiar to the
>standard the XML document
>created above (837XML). I
>have input the 837XML document
>as the source input to the
>XSLT mapper and a modified
>version of the 837XML XSD as
>the target document. Is there
>a way to map all common fields
>automatically (i.e., /+)
>rather than one at a time.

At this time, there is no automap feature.

>I
>assume this will output an XML
>document in our in-house
>format. If so my thought is I
>can use the modified XSD
>directly rahter than the 837
>convertor. Is this correct?
>If so, how.
>Thanks

Well, the adapter is always going to generate the XML in the format
of the XSD that we generate - that's why we give you the ability to
generate those XSDs for specific 'flavors' of EDI.

Let's give these things names: the original XSD that comes out of the
Stylus Studio X12 to XSD Wizard will be Tony.XSD, and the one you
modified to represent your ultimate XML will be Dan.XSD.

I would use Tony.XSD as the 'source' for the mapper, and Dan.XSD as
the target for the mapper. The 837XML document that is the output of
the adapter will always conform to the Tony.XSD.

That way, whatever EDI comes in will be mapped properly to your
specific XML needs.

And, doing the map backwards will let you translate your XML based on
Dan.XSD to EDI, if you need to go the other way.

Posttop
Tony LavinioSubject: X12 to XML (837)
Author: Tony Lavinio
Date: 11 May 2006 12:59 AM
But we should really continue this discussion under the Stylus Studio
Technical Forum, since this is the Website Feedback forum, and this isn't
website feedback. (And I'm the one who should know better :).)

   
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-2011 All Rights Reserved.