[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: draft doc word format
The verbage for 5.2 Search regarding the attribute list has not been updated to reflect the schema, which calls for each attribute name to be delimited by and <attribute> element rather than commas. According to RFC2251 section 4.5.1, the special attribute OID "1.1" is used to specify that no attributes are to be returned. DSML could just defer to this, or could interpret <attribute/> to be a synonym for 1.1 or could introduce a different element to be a synonym for 1.1. I can understand wanting to use a more intuitively meaningful way to encode it, but don't know if I like the idea of having multiple ways to encode the same thing. Shon Vella Software Engineer, Consultant svella@novell.com Novell, Inc., the leading provider of Net services software www.novell.com >>> Tom Beauvais <tbeauvais@bowstreet.com> 09/21/01 09:00AM >>> Looks great. Here are a couple of questions/comments. In reference to section "5.2 Search" we say that "An empty LDAP attributes sequence requests all user attributes, so an empty DSMLv2 attributes string does the same thing." How are we suggesting that you specify that no attributes are to be returned. A couple of option are: <attributes>""</attributes> or what I prefer is: A missing attributes element will mean return all attributes and an empty element will specify that no attributes are to be returned. In the same section it says that the filter will be expressed using RFC 2255 instead of some complex XML nested filter. I definitely agree with this, but the SearchRequest example shows nested XML and the DSMLv2.xsd describes the filter as nested XML as well. Which is it? In several places in the document it states that DSMLv2 borrows the DSMLv1 directory-entry encoding, but I see a couple of inconsistencies in the examples. Sometimes we express the attr as: <attr name="sn"><value>Smith</value></attr> and other time it is expressed as: <attr desc="title"><value>Program Manager</value></attr> Also in DSMLv1 the objectclass values are expressed as: <dsml:objectclass> <dsml:oc-value>top</dsml:oc-value> <dsml:oc-value>person</dsml:oc-value> <dsml:oc-value>organizationalPerson</dsml:oc-value> <dsml:oc-value>inetOrgPerson</dsml:oc-value> </dsml:objectclass> Thanks, Tom -----Original Message----- From: Christine Tomlinson [mailto:chris.tomlinson@sun.com] Sent: Thursday, September 20, 2001 1:35 AM To: DSML version 2 Subject: draft doc word format attached is the word format draft ciao, Christine ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC