RE: [dsml] DSMLv2-draft14

[Shon Vella <SVELLA@novell.com>]

Answer to the first question is that either form is legal.

As far as schema goes, it is represented in DSMLv2 as operations and
query results on the subschema entry and subentries as defined in
RFC2251 section 3.2.2. I believe that it was the consensus of the TC
that further work needs to be done in this area, but that it was beyond
the scope of DSMLv2.

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> 12/12/01 11:19AM >>>
In this example shouldn't the values of the object class be within one
attr

   <searchResultEntry dn="CN=JSmith, OU=Finance,DC=Example,DC=COM">
      <attr name="objectclass"><value>top</value></attr>
      <attr name="objectclass"><value>person</value></attr>
      <attr
name="objectclass"><value>organizationalPerson</value></attr>
      <attr name="sn"><value>Smith</value></attr>
   </searchResultEntry>

Like this.

   <searchResultEntry dn="CN=JSmith, OU=Finance,DC=Example,DC=COM">
      <attr name="objectclass">
        <value>top</value>
        <value>person</value>
        <value>organizationalPerson</value>
        <value>Smith</value>
      </attr>
   </searchResultEntry>


Sorry if I missed this topic, but in DSML 1.0 there was a separate XML
schema for representing the LDAP Schema like this:


<dsml:directory-schema xmlns:dsml="http://www.dsml.org/DSML">
  <dsml:class dsml:id="nsmailsecurity" dsml:superior="#top"
dsml:type="structural">
    <dsml:name>nsMailSecurity</dsml:name>
    <dsml:description>Standard ObjectClass</dsml:description>
 
<dsml:object-identifier>2.16.840.1.113730.3.2.81</dsml:object-identifier>
    <dsml:attribute ref="#objectclass" required="true" />
    <dsml:attribute ref="#aci" required="false" />
    <dsml:attribute ref="#nsmsencryptoutgoingmail" required="false" />
   .........

Can someone verify for me that it was intentionally dropped? If so
then
perhaps
the spec should provide an example of a LDAP schema in DSML 2.0
format.

Would it look something like the following example? It seems a bit
funny
using the "dn"
as the objectclass name, but where would you put it? Also there no way
to
distinguish 
between an attribute definition and objectclass definition as in DSML
1.0.


  <SearchResultEntry dn="inetorgperson">
    <attr name="MUST">
      <value>objectclass</value>
      <value>sn</value>
      <value>cn</value>
    </attr>
    <attr name="SUP">
      <value>organizationalPerson</value>
    </attr>
    <attr name="NAME">
      <value>inetOrgPerson</value>
    </attr>
    <attr name="NUMERICOID">
      <value>2.16.840.1.113730.3.2.2</value>
    </attr>
    <attr name="DESC">
      <value>Standard ObjectClass</value>
    </attr>
    <attr name="MAY">
      <value>aci</value>
      <value>description</value>
      <value>seealso</value>
      <value>telephonenumber</value>
    .........
    


  Tom


-----Original Message-----
From: Jeff Parham [mailto:jeffparh@windows.microsoft.com] 
Sent: Thursday, November 29, 2001 12:24 PM
To: dsml@lists.oasis-open.org 
Subject: [dsml] DSMLv2-draft14


1. Per mail from Karl/Winston, added URL for errata.

2. Per mail from Rob/Christine, changed principal attribute to be of
syntax xsd:string.  Changed example in 5.1 to use principal="dn:CN=Bob
Rush,OU=Dev,DC=Example,DC=COM".  Added the following text to 5.1: "The
value of the principal attribute is an authzId, as defined by [RFC
2829]."  Added [RFC 2829] to the bibliography.

3. Changed the date and removed "draft".

-J

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