Altova Mailing List Archives


[xsl] documenting element syntax

From: martin@--------
To:
Date: 5/16/2002 1:39:00 AM
hi all,

i'm currently in the process of writing the specification for an xml-based
programming language using docbook, with the intent of producing both
printable (fo/pdf) and online (html) output.
however i've found no really good way to express the syntax/grammar of the
xml elements that make up an important part of the language. ebnf is not
well suited for the purpose and funcsynopsis obviously doesn't work at all.

before switching to docbook i played around with the w3c xmlspec format,
and came across something called ElementSyntax which perfectly captures
element syntax (the result can be seen in the xslt and xml schema
specifications, eg http://www.w3.org/TR/xslt#element-syntax-summary).
though i couldn't find any documentation or even an html stylesheet - and
i wouldn't have a clue how to integrate it with an existing docbook
document.

has anyone else done this sort of thing? advice would be much appreciated!

regards,

/m


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

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.