> - you have <xs:choice minOccurs="0" maxOccurs="unbounded"> instead of
> just <xs:choice>. Could every dss:Parameter just have a single content
> element?
You're right, that's a cut and paste error (from Parameters); it should
just be <xs:choice>
> - why <xs:complexType mixed="true"> instead of just <xs:complexType>?
> - do we need <xs:attribute name="type" type="xs:anyURI"
> use="required"/>? Could the server just look at the name of its single
> content element?
Some parameters might just have content. For example
<dss:Parameter type="http://www.verisign.com/cps/foo">
here is the text of our certification practice
statement.
</dss:Parameter>
I'm not opposed to forcing that to be rewritten such that the interior
element defines the content:
<dss:Parameter>
<vrsn:cps xmlns:vrsn="http://www.verisign.com/cps/foo">
here is the text of our certification practice
statement.
</vrsn:cps>
</dss:Parameter>
But I felt more strongly about following the pattern of dsig:Transform
/r$
--
Rich Salz Chief Security Architect
DataPower Technology http://www.datapower.com
XS40 XML Security Gateway http://www.datapower.com/products/xs40.html
XML Security Overview http://www.datapower.com/xmldev/xmlsecurity.html
