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: Spec issues - Draft 9.


About a dozen issues remain open at this time (assuming that I've 
addressed issues with Draft 8 in a satisfactory manner).  We're 
definitely getting close.

Bohren, Jeffrey wrote:

> Call in info:
>
> Tel: 1-888-384-9090 or
>
> Tel: 1-719-955-1560       
>
> Passcode: 259989
>
>  
>
> Agenda,
>
>  
>
> 6)       SPML 2.0 Spec Draft 9 and issues [3]
>

|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.

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.

|9-13 CLOSED.

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.
20050512 - Sent email: "Spec issue #14: Declaring the Structure of Complex Reference Data"
20050531 - Resent email: "RESEND: Spec issue #14: Declaring the Structure of Complex Reference Data"
20050531 - Jeff Bohren suggested adding referenceDataType of SchemaEntityRefType to ReferenceDefinitionType.
20050601 - Gary Cole agreed.
20050605 - Draft 21 did not include this (xsd issue #92).
20050606 - (d09) Draft 9 assumes ReferenceDefinitionType#referenceDataType.

|15-39 CLOSED.

40. Ability to specify attributes that search should return is valuable.
20050531 - Jeff Bohren says that this is now profile-specific.
20050531 - Jeff Bohren will confirm that DSMLv2 Profile preserves this.
20050531 - Jeff Bohren will confirm that XSD Profile uses XPath to do this.

|41-44 CLOSED.

45. (3.5.4.1.3) Modify for capability data looks funny. Did we ever really figure that part out?

|46-47 CLOSED.

48. (3.5.7.1.2 and 3.5.7.2.2) Returning empty <psoID> elements when returnData='none' seems bogus.
20050606 - NOT SURE.  Sent email to list: "PSO elements and returnData option".

49. Returning empty <data> elements when returnData='none' or 'identifier' seems bogus. 
20050606 - NOT SURE.  Sent email to list: "PSO elements and returnData option".

|50-52 CLOSED.

53. (3.5.7.2.3) The count should be the number of entries that the next iterate request will return, 
where the total count should be to total number of entries. 
20050606 - DISAGREE. Sent email to Jeff Bohren: "Iterator, count and totalCount".

|54 CLOSED. 

55. Add a <closeIteratorRequest/Response> so that a well-behaved client can say he's done.

56. Remove all strikethrough and red formatting.

57. Correct <pso> elements: 'objectID' should be 'ID'.


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