Re: DsmlValue

[Shon Vella <SVELLA@novell.com>]

I would also propose adding a default value of xsd:string for valuetype, eg:

<!-- **** DSML Value **** -->

 <xsd:simpleType name="DSMLValueType">
  <xsd:union memberTypes="xsd:string xsd:base64Binary xsd:anyURI"/>
 </xsd:simpleType>

 <xsd:complexType name="DsmlValue">
  <xsd:attribute name="valuetype" type="DSMLValueType" default="xsd:string"/>
 </xsd:complexType>

Another issue is that it would seem to require the instance document to declare the schema namespace, and would require the client server to treat valuetype as a QName even though it isn't explicitly typed as such (though it could be). Since it isn't xsi:type it won't be used for schema validation, so I'm not sure what value it adds to have these be QNames rather just an enumeration of values that are mapped to the schema types.

Shon Vella
Software Engineer, Consultant
svella@novell.com
Novell, Inc., the leading provider of Net services software
www.novell.com 

>>> Christine Tomlinson <chris.tomlinson@sun.com> 09/19/01 09:48AM >>>
Both Jeff and Shon have pointed out the poor characteristics of the Sun proposal w.r.t. DsmlValue.

In the spirit of the observations, I'd like to propose the following change:

 <!-- **** DSML Value **** -->

 <xsd:simpleType name="DSMLValueType">
  <xsd:union memberTypes="xsd:string xsd:base64Binary xsd:anyURI"/>
 </xsd:simpleType>

 <xsd:complexType name="DsmlValue">
  <xsd:attribute name="valuetype" type="DSMLValueType"/>
 </xsd:complexType>

ciao,
Christine

Shon Vella wrote:

> The way that DsmlValue is currently defined would have an operation look something like:
>
> <addRequest
>     xmlns="urn:oasis-open:dsml:2"
>     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>     dn="cn=a, o=b">
>         <attr desc="objectclass">
>                 <value>
>                         <utf8>inetorgperson</utf8>
>                 </value>
>         </attr>
>         <attr desc="cn">
>                 <value>
>                         <utf8>a</utf8>
>                 </value>
>         </attr>
>         <attr desc="GUID">
>                 <value>
>                         <binary>bz5mv6g5BUWtMD0QomH1kQ==</binary>
>                 </value>
>         </attr>
> </addRequest>
>
> I can live with this, though for reasons that are purely aesthetic, I prefer the DSML 1.0 encoding of <value> which would look something like:
>
> <addRequest
>     xmlns="urn:oasis-open:dsml:2"
>     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>     dn="cn=a, o=b">
>         <attr desc="objectclass">
>                 <value>inetorgperson</value>
>         </attr>
>         <attr desc="cn">
>                 <value>a</value>
>         </attr>
>         <attr desc="GUID">
>                 <value encoding="base64">bz5mv6g5BUWtMD0QomH1kQ==</value>
>         </attr>
> </addRequest>
>
> or even maybe even:
>
> <addRequest
>     xmlns="urn:oasis-open:dsml:2"
>     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>     xmlns:xs="http://www.w3.org/2001/XMLSchema"
>     dn="cn=a, o=b">
>         <attr desc="objectclass">
>                 <value>inetorgperson</value>
>         </attr>
>         <attr desc="cn">
>                 <value>a</value>
>         </attr>
>         <attr desc="GUID">
>                 <value xsi:type="xs:base64Binary">bz5mv6g5BUWtMD0QomH1kQ==</value>
>         </attr>
> </addRequest>
>
> which would make it more amenable to schema validation than the 1.0 scheme, though less so than the current proposal.
>
> Any one else have any thoughts on this?
>
> Shon Vella
> Software Engineer, Consultant
> svella@novell.com 
> Novell, Inc., the leading provider of Net services software
> www.novell.com 
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>