DsmlValue

[Shon Vella <SVELLA@novell.com>]

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