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)
-> + DB to XML convertion (6)
-> + Converting: How to handle data... (2)
-> + Toss Character Exception (2)
-> + EDI conversion COM segment (5)
-> - SS passing invalid CALS table ... (1)
-> + Carrier Related EDI SAP questi... (2)
-> + How to generate 1 output XML f... (2)
-> + Urgent Eval: How2 w/ Possibly ... (4)
-> + Preview Problems (7)
-> + Mapping to EDIFACT ORDERS UNT0... (8)
-> + Deploying Conversion XML to ED... (2)
-> + Use EDI Adapter within Sap BC (3)
-> + Uninstall->instal entepr. 2007 (2)
-> - xml data to sql 2000 table (1)
-> - Convert from Oracle DB to XML ... (1)
-> + NTFShardlink broken (5)
-> + Can't get catalog to work (3)
-> + Only One of each EDI segment g... (3)
-> + convert (2)
-> + convert (4)
-- Previous [1861-1880] [1881-1900] [1901-1920] 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)
Topic  
Postnext
Alex GuarneriSubject: EDIFACT to XSD problem
Author: Alex Guarneri
Date: 04 Dec 2006 04:55 AM
Hi!
I am trying the EDIFACT to XSD wizard, which is perfetcly workin' except for a couple of things:
1. the "Use long element names" option flag (which is not documented as far as I know) doesn't seem to really affect the final XSD. That is, I get short names for segments (such as "BGM") but not for fields under it: for instance, in place of "BGM01-DocumentMessageName" I'd expect only "BGM01", and so on.
2. I don't uderstand (I didn't find any documentation on this either) the difference between "batch" and "interactive" schema generation.

Thanks in advance.

Best Regards,
Alex

Postnext
Tony LavinioSubject: EDIFACT to XSD problem
Author: Tony Lavinio
Date: 04 Dec 2006 11:20 AM
>Hi!
>1. the "Use long element names" option flag (which is
>not documented as far as I know) doesn't seem to really
>affect the final XSD. That is, I get short names for segments
>(such as "BGM") but not for fields under it: for instance,
>in place of "BGM01-DocumentMessageName" I'd expect only "BGM01", and
>so on.

You're right; that seems to be broken. We'll get that fixed
right away. For some reason, it always seems to want to generate
the long names.

>2. I don't uderstand (I didn't find any documentation on this
>either) the difference between "batch" and "interactive"
>schema generation.

This is a property of the EDIFACT standard. EDIFACT messages
can use the 'batch' segments: UNB, UNH, UNT, UNZ, or the interactive
ones: UIB, UIH, UIT, UIZ. The latter are only available for syntax
level 4. See http://www.gefeg.com/jswg/v4/data/v4-9735-8.pdf

The use of these would depend on your producing or consuming
application.

Posttop
Alex GuarneriSubject: EDIFACT to XSD problem
Author: Alex Guarneri
Date: 04 Dec 2006 11:57 AM
Thanks a lot, Tony.
So I'll wait for an update from your side regarding "long" or "short" element names.

Best Regards,

Alex

   
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.