Interop - DSML Schema.

Does it make sense to define a DSML schema for the Interop
(so that each of the participants can refer to that schema
rather than including the schema in each target)?

Since we have deferred the issue of listTargetsRequest specifying profile
(and/or each provider target specifying profile), recognizing the schema
may be the only way to recognize an appropriate target.

Based on the Interop document, I cooked up a DSML schema like the following.
(Not sure it's right, but it's probably close.)

    <spmldsml:schema>
        <spmldsml:attributeDefinition name="cn" description="Common Name" />
        <spmldsml:attributeDefinition name="uid" description="User ID" />
        <spmldsml:attributeDefinition name="email" description="Email 
Address" />
        <spmldsml:objectClassDefinition name="account">
            <spmldsml:memberAttributes>
                   <spmldsml:memberAttributes  name="cn"  required="true" />
                   <spmldsml:memberAttributes  name="uid"/>
                   <spmldsml:memberAttributes  name="email"/>
               </spmldsml:memberAttributes>
        </spmldsml:objectClassDefinition>
        <spmldsml:objectClassDefinition name="role">
            <spmldsml:memberAttributes>
                   <spmldsml:memberAttributes  name="cn"  required="true" />
                   <spmldsml:memberAttributes  name="description>
               </spmldsml:memberAttributes>
        </spmldsml:objectClassDefinition>
    </spmldsml:schema>