OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dsml message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: [dsml] DSMLv2-draft11


1. Per exchange between Rob and myself on the alias, incorporated Rob's
RegEx pattern for AttributeDescriptionValue.

2. Per implementors, made the "name" attribute required for the
AttributeValueAssertion, AttributeDescription, and SubstringFilter
elements.

3. Changed the "code" attribute to be required for the ResultCode
element.

4. Per implementors, the spec & examples appeared to alternate between
using "notAttempted" and "malformedRequest" as error types for syntax
errors.  Standardized on "malformedRequest".

5. Added the OASIS statements required by
http://www.oasis-open.org/who/intellectualproperty.shtml.

6. Per Christine's 11/9 mail issue #1, changed the name of the
"controlType" attibute in the spec to "type" to match the post-baseline
schema.

7. Per implementors and Christine's 11/9 mail issue #2, changed
lingering reference to "extendedReq" to "extendedRequest" in the schema.

8. Per Shon's 10/10 mail, changed xsi:type="base64binary" to
xsi:type="xsd:base64Binary" in spec examples.  (I missed this in the
prior revs.)

9. Per implementors, DsmlANY allows complex types (nested elements) but
does not allow simple types (xsd:string, xsd:base64Binary, etc.).
Therefore removed definition of DsmlANY and replaced references to it
with references to xsd:anyType, which allows both simple and complex
types.

### UNRESOLVED ###
Use of xsi:type as a union discriminator for instances of DsmlValue does
not appear to be allowed -- we've tried 3 different validators and this
is consistently rejected.  XML Schema appears to disallow use of
xsi:type as a union discriminator, though it works fine for refining
xsd:anyType instances and for specifying derived types.  One way or
another we must have a union discriminator for DsmlValue, even if it
requires going back to the "manual" discrimination used in the baseline
spec.  Andy is trying to get to the bottom of this, but if anyone has
any info to contribute please do.

Thanks,
-J

DSMLv2-draft11.doc

DSMLv2.xsd



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC