On 9/19/05, Jacquo
Johnson <genxgeek@g...>
wrote:
Thanks
all. But how would I actually present the xsd or schema in a user
friendly format for newbies that just know how to send messages...i.e. in
some dumbed down html format? Kind of like what a web service
interface definition looks like when displayin the xml of what xml message
format the service will accept?
A common approach is to use a notation like that for describing
element structure in the XSLT spec:
<!-- Category:
instruction -->
<xsl:analyze-string
select =
expression
regex = { string
}
flags? = { string }>
<!--
Content: (http://www.w3.org/TR/xslt20/#element-matching-substring?, http://www.w3.org/TR/xslt20/#element-non-matching-substring?, http://www.w3.org/TR/xslt20/#element-fallback*)
-->
</xsl:analyze-string>
<xsl:matching-substring>
<!-- Content:
sequence-constructor
-->
</xsl:matching-substring>
<xsl:non-matching-substring>
<!-- Content:
sequence-constructor
-->
</xsl:non-matching-substring>
I don't think there's a standard, but I've seen lots of
flavours of this kind of notation.
Michael Kay
http://www.saxonica.com/
|
Cart
