SSDN - EDIFACT guideline from Stylus Studio

XML Editor

Sign Up

Search

Options

Chat

Help

News

Log in

Not Logged in

Topic

Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Bruce Cantor

Subject: EDIFACT guideline from Stylus Studio
Author: Bruce Cantor
Date: 02 Dec 2021 11:41 AM

Hi

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.
Bruce

Ivan Pedruzzi

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

EDIFACT specs online here
http://www.stylusstudio.com/edifact/

Ivan Pedruzzi
Stylus Studio Team

Bruce Cantor

Subject: 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.

2021-12-03_113033.png
sample

Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

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 to Conference:

Log In Options Username: Password:

Site Map | Privacy Policy | Terms of Use | Trademarks

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.