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 (1192)
- Stylus Studio Technical Forum (14621)
-> - Stylus Studio - Registrar en o... (1)
-> + Stylus Studio - Registrar en o... (2)
-> + Can a pipeline send a file by ... (2)
-> + After Updateing WIN10 to WIN11... (12)
-> + Where do I add the custom java... (3)
-> + Where is the Diagram tab? (5)
-> + Applying XSLT to Word DOCX/XML (2)
-> - CSV conversion via ConvertToXM... (1)
-> + Text symbols in SS not same as... (4)
-> + Exposing xquery as webservice ... (6)
-> + Syntax Identifier (2)
-> + Saving a Converted XML as an X... (5)
-> + Output document cannot be pars... (4)
-> - Archiving output from conversi... (1)
-> - EDIFACT guideline from Stylus ... (3)
-> ->EDIFACT guideline from St...
-> ->EDIFACT guideline from St...
-> + CSV file putting all the data ... (5)
-> + Can't install Home version 64b... (5)
-> + presale - Can I covers this sc... (5)
-> + Problem with UNB (5)
-> + Splitting EDIFACT files pipeli... (4)
-- [1-20] [21-40] [41-60] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Bruce CantorSubject: EDIFACT guideline from Stylus Studio
Author: Bruce Cantor
Date: 02 Dec 2021 11:41 AM

We have several EDI partners that are using EDIFACT.
Some of them do not have a guideline for the EDIFACT, so they ask us for one.

Currently we have defined the guidelines using an external tool, (https://app.truugo.com/) - the site has a nice interface where the EDIFACT subset can be defined and a link can be sent to the EDI partner.

Unfortunately this service is getting quite pricey, and we are therefore looking after another way to share the subset with our partners.

Looking at the Stylus Studio sef editor, I can create a XML schema from the editor. But an XML schema is not ideal when communicating with partners that only know about EDIFACT.

I was thinking that it should be possible to create an HTML from the XML schema, making it readable for non XML readers to understand. Have anybody created something that an EDIFACT developer would like to read? The standard documentation feature in Stylus is showing a lot XML related stuff that cannot be sent to a EDIFACT partner

Has anybody tried this, or do you have another preferred way to share your EDIFACT subsets with you partners?

Kind regards.

Ivan PedruzziSubject: EDIFACT guideline from Stylus Studio
Author: Ivan Pedruzzi
Date: 02 Dec 2021 05:31 PM

EDIFACT specs online here

Ivan Pedruzzi
Stylus Studio Team

Bruce CantorSubject: EDIFACT guideline from Stylus Studio
Author: Bruce Cantor
Date: 03 Dec 2021 12:39 PM
Originally Posted: 03 Dec 2021 09:59 AM
Hi Ivan

Yes, I know that.
The thing is this shows the general EDIFACT standard, what I want to send to my EDI partners are the subset that we are using.

E.g. we might only be allowing some of the types of code in NAD party code function qualifier (3035) .

The guideline would then state which code are allowed in which are not.
In the attached screen shot you can see how NAD can be documentet.

It should be possible to do something similar from the XML schema, and I was wondering if others have done that.


Actually, maybe some kind of lightweight SEF file reader/display tool that can show the SEF file in human readable way might be the way to go.

Then I can export the sef file to the partner and they create a message based on the SEF.


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!  

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.