Spec issues.

[Gary P Cole <Gary.P.Cole@Sun.COM>]

Of the recent issues, only #45 has not been addressed.

At this point, the key question is whether we should specify a general 
mechanism for modifying capability data.
We have in mind a modification semantic based on name-value pairs 
(similar to the LDAP attribute model).
The modify operation would maintain a unique set of values for each name 
(within each capability and object).

It would be ideal if that general mechanism would support the Reference 
Capability.
The "typeOfReference" attribute maps pretty well to a(n attribute) "name".
Unfortunately, the <toPsoID> does not map cleanly to a flat string "value".


|1-5 CLOSED.

6. Update "Security and privacy considerations".
20050215 - Darran says that we should update this.  Wants a volunteer.
20050222 - Hal Lockhart volunteered to update this. Keep this in the spec.
20050329 - Hal thinks he can do this during this week.
20050607 - Hal thinks he can do this next day or two.
20050621 - Hal will send this by Thursday, 6/23.

7. Appendix I (throughout): Document references need validation and update.
20050329 - Raj volunteered during the con-call to do this.
20050510 - Hal: Beware normative references to non-std docs.
20050621 - Raj will send this by Thursday, 6/23.

8. Appendix L: Glossary.  Definitions need review and update.
20050222 - Point to a separate document for Glossary.
20050329 - Raj volunteered during the con-call to do this.
20050621 - Raj will do this by Thursday, 6/23.

|9-44 CLOSED.

45. (3.5.4.1.3) Modifying capability data may require capability-specific mechanism.
20050614 - Modifying a subset of capabilityData may require capability-specific mechanism.
20050615 - Each item should be wrapped in a separate <capabilityData> element.
20050620 - (d10) Wrapped each <reference> in a separate <capabilityData> element.
20050621 - Agreed during con-call to discuss this on the LIST.
20050811 - Sent email: "Spec issue 45..." (no replace, no wildcard-delete).
20050812 - JeffB says 1) cap-spec.  2) references a la LDAP attributes.
20050812 - JeffB sent examples.  Basically, key=typeOfReference+toPsoID.
20050815 - Slight PROBLEM: ReferenceType requires <toPsoID>.
20050815 - Specify that ReferenceType requires <toPsoID>; optional in XSD.
20050818 - Must address XSD issues #122-126.  Need for spec and examples.
20050822 - Agreed that each <capabilityData> wraps all data for a single capability.
20050822 - Agreed that "mustUnderstand" is an attribute of the wrapper.
20050822 - (xsd123). Add "capabilityURI" attribute to CapabilityDataType.
20050822 - Do we need/want a general mechanism for capability data?
 
|46-57 CLOSED.

|58. Provider may need to know requestor's profile.
|20050513 - Sent email: "Provider may need to know requestor's profile".
|20050513 - Jeff Bohren agreed (in a reply to the list).
|20050608 - Reminded Jeff Bohren (in another email) that we forgot this.
|20050614 - DEFER past COMMITTEE DRAFT.  Jeff Bohren wants to ponder it.
|20050812 - Sent email to list: "Spec issue #58..."
|           Add profile attr to ListTargetsRequestType and TargetType.
|           If profile specified, response contains only suitable targets.
|20050815 - AGREE.  Draft 27 adds profile attribute(s) and ErrorCode.
|20050818 - (d12) Added "profile" topic to listTargetsRequest.
|		Added "Target profile" in listTargetsResponse.
|           Enhanced listTargets Examples to discuss target profile.

|59-61 CLOSED.

|62.  SearchRequestType#query should be optional. Omitted means "all".
|20050818 - DISPUTED. Weird to need <query> to specify targetID. 
|           Move "targetID" to SearchRequestType?
|20050818 - Nowhere else can you omit targetID if multiple targets
|          (for <supportedSchemaEntity>, context implies containing target).
|           Search operation should not span multiple targets.
|           Each target could support a different profile.
|20050819 - (d12) FIXED. <query> is optional in search and updates requests.
|           If provider exposes more than one target, 
|           then <query> is required and must specify "targetID".

|63.  deleteResponse element is of type ResponseType (not DeleteResponseType).
|20050812 - FIXED in Draft 12.

|64.  (Examples) "path" must precede "namespaceURI" in any <select> element.
|20050818 - Draft 12: Updated <select> and <component> elements in examples.

|65.  XSD 26: SearchQueryType#basePsoID minOccurs=0.
|20050818 - Draft 12: Updated XSD snippets and Appendices.

|66.  (=XSD#119) LookupResponse contains at most one <pso>.  Clarify text.
|20050815 - (d12) Also updated XSD snippets and Appendix A.

|67.  Line 2044 "Batch Capability" should say "Bulk Capability".
|20050812 - FIXED in Draft 12.

|68.  Can modify add/replace/delete an XML *attribute* (or only an element)?
|     Jeff Bohren review comments on examples say only an XML *element*.
|     Careful: Refer to profile-spec for normative specifics.
|20050818 - (d12) FIXED. Added "Depends on profile" topic to normative sections 
| "SelectionType in a Request", "Selection Type Processing" and "SelectionType Errors".

|69.  Async Capability needs Resource Considerations (like those in Search).
|20050818 - (d12) FIXED. Async Intro has "Resource Considerations" topic.

|70.  Discuss ErrorMessages after Status and Error.
|20050813 - Added section entitled "ErrorMessage (normative)".

|71.  Add SPMLv2-UPDATES to "Namespaces".
|20050815 - (d12). FIXED in Draft 12.

|72.  Add SPMLv2-SUSPEND and SPMLv2-UPDATES to "References".
|20050815 - (d12). FIXED in Draft 12.

|73.  Mention Updates Capability at the top of "Operations" section.
|20050815 - (d12). FIXED in Draft 12.

|74.  Replace references to "execution" attribute with "executionMode".
|20050815 - (d12). FIXED in Draft 12.

|75.  Provider must honor any <psoID> supplied in <addRequest>.
|20050815 - (d12) FIXED. Reworked addRequest and addResponse sections to discuss.
|20050815 - XSD 27 adds ErrorCode#invalidIdentifier and #alreadyExists.

|76.  Discuss new maxSelect attribute of UpdatesRequestType (new in XSD 27).
|20050818 - (d12) FIXED. updatesRequest and updatesResponse discuss maxSelect.

|77.  Document new closeIterator operation of UpdatesCapability.
|20050818 - (d12) FIXED. Draft 12 has new "closeIterator" section.

|78.  Consistently use XML element font for enclosing brackets.
|79. line 661: "existing object that exists on a target" is redundant.
|80. line 1705: deleteResponse returns "requestID" (not "asyncRequestID").
|81. line 1739: statusRequest MUST return status of (not cancel) the operation.
|82. line 1799: response for pending must contain *initial* subset of output.
|83. line 1908: Section 7.3.6 does not exist. Paragraph is redundant.  Rewrite.
|84. line 1917: No such as batchableRequest.  Relabel as "Nested requests".
|85. line 1919: batchRequest MUST contain at least one request. 
|    Combine this sentence with the previous sentence.
|86. line 1928: Add spmlupdates:UpdatesRequestType, IterateRequestType
|    and CloseIteratorRequestType to the list that must not be batched.
|87. line 2007: delete unmatched parenthesis in "described by a) nested".
|88. line 2216: setPassword must change password for (not enable) object.
|89. line 2268: expirePassword invalidates password for (not enables) object.
|90. line 2316: must should be all capitals (because it is normative).
|91. line 2360: validatePassword tests the value (not changes password).
|92. line 2363: delete paragraph (copied from resetPassword).
|93. line 2528: complexType RacfGroupMembership should be RacfGroupMembershipType.
|94. line 2571: complexType RacfGroupMembership should be RacfGroupMembershipType.
|95. line 2585: complexType RacfGroupMembership should be RacfGroupMembershipType.
|96. line 2784 (and throughout): "status set" should be "result set".
|97. line 2834 (and in section): iterate returns next set of items (not next item).
|98. line 2869: Clarify time when "one object remains".  Tense is ambiguous.
|99. line 2872: Clarify time when "no object remains".  Tense is ambiguous.
|100. line 2919 (and in section): searchResponse should be iterateResponse.
|101. line 2933: Remove "requestor cannot specify "ID". Confusing.
|102. line 3427: Remove "requestor cannot specify "ID". Confusing.
|103. line 3464 (and in section): iterateResponse returns updates (not objects).
|104. line 3484 (and in section): "updates set" should be "result set".
|105. line 3507 (and in section): iterate returns next set of items (not next item).
|106. line 3516: Clarify time when "one object (update) remains".  Tense is ambiguous.
|107. line 3519: Clarify time when "no object (update) remains".  Tense is ambiguous.
|108. line 3524: Remove "PSO and ReturnData" section. Copied from search iteration.
|109. line 3524: Remove "PSO capability-specific Data..." section.
|110. line 3580: Remove "requestor cannot specify "ID". Confusing.
|20050817 - Draft 12 addresses issues 78-110.

|111. Add contributors Robert Boucher, Cal Collingham, James Hu, Prateek Mishra.
|	Alphabetize contributors by last name.
|20050822 - (d12) Draft 12 adds these (and alphabetizes) contributors.