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: Re: [provision] spec issues.


Sorry; RichTextFormat made a hard-to-read attachment.  It's now flat text.

Gary P Cole wrote:

> I've collected all the red Editor's notes from the current draft of 
> the spec.  I've eliminated most duplicates--except where a duplicate 
> issue represents a fair amount of work (e.g., a new example). A few of 
> these are obviously TO-DOs for me, but most are real issues.
>
> Some of these issues may already have been answered in discussion on 
> the list (but I missed it or those resolutions haven't made it into 
> the draft).  A few depend on the Reference Capability. The vast 
> majority are wide open: take a shot at any you like.


1.1. Rami will send more on "Purpose of SPML" itself.

1.3. Rami will provide a draft of “Changes from SPML 1.0”.

2.1. Gerry will send UML diagram(s) to replace ERD.

2.1.3. Rami will draft content that further defines the term "capability". 
	   Same intent as extended operations in SPML1.0.

3.1.1. This implies that a multi-threaded provider must queue requests (by requestor). 
         Can we simply require requestID in RequestType?
         Jeff Larson said 'no'.  Imposes burden on requestor 
          that is unnecessary for simple requestor.

3.3. Use the correct terms for the long form and short-form of XPATH expressions.

3.3.1A. What is the 'namespaceURI' value for an XPath expression?

3.3.1B. What is the 'namespaceURI' value for a SPML1.0 (DSMLv2) attribute expression?

3.4.1.1.2. (See #51 in draft_13_xsd_issues.txt.)

3.4.1.2.2. (See #40 in draft_13_xsd_issues.txt.)

3.4.1.4.1. What does an instance of SelectionType <component> contain in the DSML Schema binding?
              For ‘modify’, <data> contains a DSML attributeModifier elements.

3.4.1.4.2. TO-DO: Discuss ErrorCode in Protocol general features.

3.4.1.4.3A. TO-DO: Since a modifyRequest can change the PSO-ID, 
              we should probably mention this, and show an example of 
              a modificationResponse returning the new PSO-ID.

3.4.1.4.3B. TO-DO: Show examples of adding and replacing a reference.
	  Should we show examples of modifying references where the cardinality assumptions differ?
	  Can one specify cardinality for a specific type of reference?
	 ** PENDING Reference Capability meta-data issues. **

3.4.1.5.2A. (See #55 in draft_13_xsd_issues.txt.)

3.4.1.5.2B. TO-DO: Discuss StatusCode in Protocol general features.

3.4.1.2.1. Do we need to give a reason why cancel must be synchronous?

3.4.2.2.1. Do we need to give a reason why status must be synchronous?

3.4.2.2.2. TO-DO: Link to discussion of RequestID.

3.4.3.1. TO-DO: Document as a general feature that we punt on logical unit of work--no UNDO.

3.4.4.1.3. A requestor can query for Person instances based on “owner” 
              only if the provider defines “owner” as an element or attribute of Person 
              in the schema for the target.  In such a case, what would the value of “owner” look like? 
              Would “owner=’joebob’ work?

3.4.4.1.3B. (Same as 3.4.1.4.3B above:  ** PENDING Reference Capability meta-data issues. **)

3.4.4.2.3. (Same as 3.4.3.1.3 above.)  

3.4.5.  Which password operations should be batchable?

3.4.5.4. (See #62 in draft_13_xsd_issues.txt.)

3.4.6. Reference Capability issues.  ** PENDING Reference Capability meta-data issues. **

3.4.7.1. Neither search nor iterate is batchable (for reasons of scale).
            (Combine with 3.4.5: Which operations of every capability are batchable?)

3.4.7.1.3. (Same as 3.4.4.1.3 above.)

3.4.7.2.1. Do we need to give a reason why iterate must be synchronous? 

3.4.7.2.2. A provider that changes the ID in an iterator each time can detect this.

3.4.8.1.2. May 'suspend' return an error when the object is already suspended? I think not.

3.4.8.2.2. May 'resume' return an error when the object is already resumed? I think not.

5. Do we need to update "Security and privacy considerations"?

Appendix I (throughout): Document references need validation and update.

Appendix K: Do we need new OASIS notices?  From where?

Appendix L: Glossary.  Definitions need review and update.

Appendix M: Requirements. TO-DO: Replace this section with SPML 2.0 requirements.


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