[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsrp] [CR309] - Specify lax processing of extensions element
A possible issue is that this would rule
out "strict" enforcing of schema validation once extensions are
used. I appreciate that we do not have many validating parsers and that
specifying the location of extension schemas is itself a problem, but I would
think some use cases do require all values passed (including extensions) to be
validated. E.g. a Banking portlet with secure e-commerce extensions. How about
leaving the "strict" default and adding another container type to
relax validation? <complexType name="Extension">
<!-for validating extensions à <complexType name="OptionallyCheckedExtension">
<!-put this in an Extentions to relax à This 2nd extension type could instead
be defined by the extension schema. It would also serve as a warning to developers. Regards, Andre From: Rich Thompson
[mailto:richt2@us.ibm.com]
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]