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] Re: draft 10/9


The draft contains examples using xsd:type with xsd mapped to "http://www.w3.org/2001/XMLSchema". It should be xsi:type with xsi bound to "http://www.w3.org/2001/XMLSchema-instance" . xsd will still need to be mapped because the type value refers to it.

For example (from the first examples in 5. LDAP Operations)

Here are few examples of LDAP request elements: 

<batchResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema"
		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                        xmlns="urn:oasis:dsml:names:tc:DSML:2:0:core">
   <modifyRequest dn="CN=Joe Smith, OU=Dev, DC=Example, DC=Com">
       ...
   </modifyRequest>
   <addRequest  dn="OU=Sales,DC=Example, DC=Com">
     
   </addRequest>
   <delRequest dn="CN=Alice,OU=HR,DC=Example,DC=Com">
       <control>...</control>
       <control>...</control>
   </delRequest>
    <searchRequest>
       ...
       <control>...</control>
    </searchRequest>
</batchRequest>


Here is an example of an LDAP Control:

<control type="1.2.840.113556.1.4.619" criticality="true">
     <controlValue xsi:type="xsd:base64Binary">RFNNTHYyLjAgcm9ja3MhIQ==</controlValue>
</control>


The controlValue element is base64 encoded.



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> 10/09/01 05:25PM >>>
Attached is the next draft. Changes are tracked so you can see what I
did.

1) included Jeff's draft text for 7. File Binding - included as is
subject to comments from Shon & Pete
2) changed 'transport binding' to 'binding' throughout
3) added comments on authentication to section 6. SOAP Request/Response
Binding
4) corrected comment heading in schema above SearchResponse to say
Search Response instead of DSML ....
5) Added a comment at the end of the Search request concerning how to
control the size of SearchResponses and to indicate that it is
permissible to stream such responses if the binding permits
6) Added a section "5.1 Bind" to document the bindRequest

ciao,
Christine



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


Powered by eList eXpress LLC