OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

provision message

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


Subject: [provision] - Comments on draft-pstc-spml-core-07.doc


Hi Darran, some comments against draft-pstc-spml-core-07.doc
 
0) editorial - bunch of 'SMPL' references
 
1) Section 5.1.1.17 - I question use of 'authority' in the name 'Requesting Authority'. Over what is this entity authoritative? While I see that in some cases the request will carry user attributes for which the client is (in some sense) asserting to be 'true', I suggest that the term authority has connotations that don't intuitively combine  with 'requestor'
 
2) Line 229 - the statement 'when System Two implemented its service at Resource E, it DID NOT use an SPML protocol message' gives the impression that SPML cannot be applied here, rather than merely that System 2 is not forced to use SPML for communicating with Resource E once it used SPML to communicate with System One.
 
3) Line 348 - use of 'service requestor' should be replaced with RA for consistency
 
4) Line 431 - suggest adding DSML namespace prefix to appropriate elements
 
5) Section 7.3.4 - SPML Search Operations - After explicitly calling out the symmetry of the filtering (e. g that filters can be applied to both the search criteria and to the returned attributes), the schema treats these differently. Why?
 
Additionally, do we need to provide a processing rule to indicate what the SPML server should do if no filtering attributes are listed in the request.
 
6) Line 486 - the searchResponse example lists the returned attributes in the opposite order as to which they were specified in the request, e.g . 'cn' & 'email' We should clarify what, if anything, is meant by the order of listing.
 
7) line 541 - the example extendedRequest incorrectly shows an operationIDType on the spml:identifier element rather than the spml:operationIdentifier
 
Additionally, the example of extended request demonstrates a mail server purge. Perhaps we should mention that this operation could (I believe) have been performed by a delete request with appropriate operationalAttributes? iis this a general phenomena? Alternatively (and preferably in my opinion), could we not come up with an example that couldn't be similarly broken down (although I can't come up with one)
 
8) Line 623 - the schema snippet conflicts with that of Line 741.
 
paul
-----------------------------------------------------------------
Paul Madsen
e:  p.madsen@entrust.com
p:  613-270-2632
Entrust
Securing Digital Identities
& Information
http://www.entrust.com
 
 


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