Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Schema, BNF and parsing

From: Andrew Jeavons <apj@-------------.--->
To: xml-dev@-----.---.---
Date: 3/4/2005 5:50:00 PM
First apologies if this is OT for this list or contains egregious 
assumptions and statements....I am not by any means a XML expert.

I have recently started working with a product which uses XML as the 
definition framework. We have a XML (QML we call it) which
describes how to ask questions. So QML has elements like "text", "sub 
question" and so on. We develop scripts which are validated for syntactic
validity and then passed to an execution engine. Of course the QML written 
has to conform to the schema defined. As far as I can currently work
out we use a 2666 line XLST script to check QML. QML is not a complex 
"language", it reminds me of IBM MVS JCL - 5 verbs and 200 qualifiers for 
the verbs.
2666 lines of anything to check this "language" seems extreme. I have 
written parsers using YACC in the past and it seems to me for numerous 
reasons using
some sort of BNF/EBNF defined grammer and Bison/YACC type tools will be 
VASTLY more efficient and flexible. What I would like to ask is are there any
tools anywhere to convert a schema to BNF/EBNF ?

thanks
andrew

Andrew Jeavons


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent