Spec issues draft 7 (attached).

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

AFAIK, only the following issues remain:
- #6,#7,#8 are minor. 
   (Hal: Security and Raj: Glossary & References).
- #10,#11,#16,#22,#23 now agreed. 
   (Draft 8 will address these.)
- #27 is largely addressed.
   (Jeff will send better text for effectiveDate-UTC.)
- #14 remains unaddressed.
   (Declaring the structure of complex reference data.)



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.

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.

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.

10. What if reference capability declaration contains no reference definition?
	[Ed. If the provider did not declare any typeOfReference within target2’s declaration 
	of the Reference Capability for Person, would this mean that an instance of Person on target2 
	may use any type of reference refer to an instance of any schema entity on any target?]
20050510 - Agreed during con-call to discuss this on the list.
20050512 - Sent email: "Spec issue #10: Reference capability declaration without..."
20050517 - AGREE. Specify that ref cap decl must contain 1+ <refDef>. 
20050517 - Gary to fix in Draft 8.

11. What if a reference definition does not specify a targetID on the canReferTo schema entity?
	[Ed. If the provider did not specify a targetID within “Person-owns-Account”, 
	would this be an error (since target2 does not support Account), or would this mean that 
	an instance of Person on target2 may use the “owns” type of reference refer to 
	an instance of Account on any target?]
20050510 - Agreed during con-call to discuss this on the list.
20050512 - Sent email: "Spec issue #11: Reference definition CanReferTo without targetID..."
20050516 - AGREE: Specify targetID is required if multiple targets.
20050516 - Gary to fix in Spec Draft 8.

14.  How does a provider declare the structure of reference data for complex references?
	Reference Definition contain xml schema (or refer to schema entity)?
20050510 - Agreed during con-call to discuss this on the list.
200500512 - Sent email: "Spec issue #14: Declaring the Structure of Complex Reference Data"

16. Line 559: the IdentifierType is used to identify targets, but is not limited
to targets. To date only targets are identified using an element of type
IdentifierType, but that may well change in the future. The type
IdentifierType should be considered a generic type for which
PSOIdentifierType is a specialization.
20050421 - DEFER. Sent email to list: "IdentifierType...".  Part of XSD issue #67 (targetID).
20050510 - Part of the "targetID" debate. (JeffB will publish side-by-side examples.)
Draft 18 - TargetID is now an attribute.  IdentifierType is used only by PSOIdentifierType.
20050517 - AGREE. Gary to fix in spec Draft 8.

22. Draft 6, Line 962: An add request MAY omit both the target ID and container ID if the
PSP has only one target and containment is not being specified. 
20050421 - Sent email to list: "AddRequest targetId, containerID and psoID."
20050512 - Re-sent email: "Spec issues #22 and #23: AddRequest targetId...."
20050516 - AGREE.  Gary to fix in spec Draft 8.

23. Draft 6, Line 962: An add request MAY contain a PSO ID. This section implies otherwise.
20050421 - Sent email to list: "AddRequest targetId, containerID and psoID."
20050512 - Re-sent email: "Spec issues #22 and #23: AddRequest targetId...."
20050516 - AGREE.  Gary to fix in spec Draft 8.

|27. Effective date must be UTC format date/time string (with no offsets).
|20050510 - (d07) AGREE.  Fixed in Draft 7. 
20050510 - OPEN. Jeff Bohren will send better sample text from SAML spec.