[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: 20041130 Working Group (Editor's) call.
Participants in this morning's working group call reviewed and discussed issues raised by the Bulk, Password, Reference, Search and Suspend subsections of the Protocol section of the draft SPMLv2 specification. Attendees: - Darran Rolls (Sun) - Gerry Woods (IBM) - Jeff Bohren (Open Networks) - Gary Cole (Sun) Issues: ------- 1) (XSD) Draft 7 of the XSD was in error. BatchRequestType should refer to an element of BatchableRequestType (rather than naming it "batchableRequest"). Draft 8 of the XSD corrects this. 2) (XSD) Rename elements of type PSOIdentifierType from "pso" to "psoId" in password capability and suspend capability. 3) (XSD) Camel-case 'oneLevel', 'subTree' and 'maxReturn' in search capability. 4) (XSD) Rename "state" namespace to "suspend" for suspend capability. 5) (XSD) The "active" attribute of ActiveResponse should be optional. - in case of error, any value of "active" could be misleading. 6) (Spec) The 'iterate' operation must be synchronous. 7) (Spec) In general, a requestor should ignore any content of an SPML response that specifies "error". 8) (Spec) The ID of an iterator may change as a result set is iterated. This allows the ID to encode (or map to) the *state* of a result set. 9) (XSD) Iterator should be *optional* in SearchResponseType. 10) (XSD) XSD should allow the provider to omit content for every response in case of error. (No response type should require a sub-element.) 11) (XSD) <pso> should be minOccurs="0" and maxOccurs="unbounded" in SearchResponseType. (A provider may return any number of objects.) 12) (XSD) <iterator> should be minOccurs="0" and maxOccurs="1" in SearchResponseType. (No need for provider to return an iterator if there is an error (or if the provider returns all matching objects). 13) (XSD) <modification> should be minOccurs="1" and maxOccurs="unbounded" in ModifyRequestType. (A requestor may specify multiple modifications for the same object.) 14) (XSD) The <component> element should be of type SelectionType (rather than IdentifierType) in ModifyRequestType. (A requestor may use an XPATH expression to specify the component of an object that the provider is to modify.) 15) (XSD) SelectionType should be enhanced to allow a requestor to specify any number of mappings from a prefix (used in the expression that is the value of the "path" attribute) to a namespace URI. 16) (Spec) Need examples of defining named reference types and modifying references. - define named reference type between specific schema entities? - specify direction for named reference type? - specify cardinality for named reference type? - specify inverse for named reference type? Action Items ------------ 1) Gary Cole to review Draft 8 of the XSD and to: - detect specific changes between Draft 7 and Draft 8. - remind Jeff Bohren of any pending XSD change not reflected in Draft 8. - apply changes in Draft 8 to draft specification. 2) Jeff Bohren to develop Draft 9 of the XSD and to: - address pending changes not reflected in Draft 8. - address XSD issues listed above. - itemize changes from Draft 8 to Draft 9. 3) Jeff Bohren to supply examples of defining named reference types and modifying references (per item 16 above).
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]