Skip to Content.
Sympa Menu

grouper-dev - [ldappc-ng] versioning spml requests/responses ?

Subject: Grouper Developers Forum

List archive

[ldappc-ng] versioning spml requests/responses ?


Chronological Thread 
  • From: Tom Zeller <>
  • To: Grouper Dev <>
  • Subject: [ldappc-ng] versioning spml requests/responses ?
  • Date: Wed, 7 Apr 2010 17:30:56 -0500
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; b=wRmtQGFUMm0OR2uPR/V7ltHNMELiMPkg89S/qLxi8fv15ZyC0UdZF2D5ipQk3LkQpd ZUQd7w7sDgfEOgzbF2FLwl2BzASRseFOtL4FTZoly48qrClylsDPSofnlow/Kxm/HtPe XD4S1MhCf0HiQEPBP1QrhFFibLoRV9hM2eZTo=

I have invented several xml representations of spml-ish requests and
responses for ldappc-ng. As these representations may need improvement
in the future, I'm looking for suggestions regarding versioning.

The following is a CalcResponse, which represents how a group should
be provisioned. Adding a version attribute seems straightforward :

<ldappc:calcResponse version="1.6.0" ...

Or perhaps we should mirror grouper-ws :

<ldappc:calcResponse
<version>v1_6_000</version>
...

Thanks,
TomZ

<ldappc:calcResponse
xmlns:ldappc='http://grouper.internet2.edu/ldappc' ID='edu:groupB'
status='success' requestID='REQUESTID_TEST' >
<ldappc:id ID='edu:groupB'/>
<ldappc:pso entityName='group'>
<psoID ID='cn=groupB,ou=edu,ou=testgroups,dc=internet2,dc=edu'
targetID='ldap'/>
<data>
<dsml:attr xmlns:dsml='urn:oasis:names:tc:DSML:2:0:core'
name='objectClass'>
<dsml:value>top</dsml:value>
<dsml:value>group</dsml:value>
</dsml:attr>
<dsml:attr xmlns:dsml='urn:oasis:names:tc:DSML:2:0:core' name='cn'>
<dsml:value>groupB</dsml:value>
</dsml:attr>
<dsml:attr xmlns:dsml='urn:oasis:names:tc:DSML:2:0:core'
name='description'>
<dsml:value>descriptionB</dsml:value>
</dsml:attr>
</data>
</ldappc:pso>
</ldappc:calcResponse>


  • [ldappc-ng] versioning spml requests/responses ?, Tom Zeller, 04/07/2010

Archive powered by MHonArc 2.6.16.

Top of Page