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: [no subject]


 32.	Allow 'status' operation to serve as 'statusAll'
	- 'asyncRequestID' becomes optional
	- if no 'asyncRequestID', return all
	- <nestedResponse minOccurs="0" maxOccurs="unbounded">
20041207 - Agreed.
Draft 11 - Not done.  asyncRequestID should be optional in StatusRequestType, StatusResponseType.
Draft 12 - Not done.  asyncRequestID is now optional in StatusRequestType but not StatusResponseType.
20040118 - Sent email: "Issue#32: StatusResponseType#asyncRequestID."
Draft 13 - Not done.  asyncRequestID is still required in StatusResponseType.


 40.	Requestor must "program-by-exception" wrt containment.  Is this okay?
	- nothing tells requestor whether target supports containment.
	- nothing tells requestor whether target schema entity supports containment.
	- Do we need a Containment capability to advertise either or both of these?
20041207 - Left OPEN.  Jeff Bohren wants to consider on this.
Draft 11 - Added to SchemaEntityRefType boolean attribute 'isContainer'.
Draft 11 - Added to ErrorCode a value of 'invalidContainment'.
Draft 12 - Do we need to say which supported schema entities each schema entity may contain?


----------------------------
Follow up on Draft 11
----------------------------

 51. 	When SchemaType#ref is a location (URL to a schema document),
	is this an alternative to including the schema document 
	as content of the <schema> element?
	Would it be clearer to have separate attributes (as we do for CapabilityType):
      - one that identifies the schema ('namespaceURI') and
      - another that gives the location of a schema document ('location')?

 52.	Rename "DataInclusionType" to "ReturnDataType"
	Rename "returns" to "returnData". (Parallel, explicit, imperative.)
Draft 13 - "DataInclusionType" renamed to "ReturnDataType".
		However, "returns" was not renamed to "returnData".


----------------------------
Follow up on Draft 13
----------------------------

 55.	Add 'recursive' attribute to BulkDeleteRequestType (just like DeleteRequestType).
20050112 - sent email to list: BulkDeleteRequestType#recursive.  Jeff Bohren agreed.

 56.	Remove minOccurs="0" from SearchRequestType#basePsoId and #baseTargetId.
      (Just like 53: AddRequestType choice of containerId and targetId.
	XML choice specifies that exactly one of these is required.)

 57.	Rename ReferenceType#psoID to "toPsoId".  
	(Make clear that this specifies the "to" object.)

 58.	Rename ReferenceType#data to "connectionData" or "referenceData".
	Distinguish this arbitrary payload from "data", which is schema-defined XML
	and from "capabilityData", which are specific to a supported capability.)

 59.	Declare ReferenceType#data (nee "connectionData" or "referenceData") as "minOccurs=0".
      This arbitrary payload is optional.

 60.	Rename ReferenceType#name to "typeOfReference".
	(Make clear that this is not the name of either object involved in the reference,
	but rather indicates the "type" of connection between the two objects.)

 61.	Remove default "minOccurs='1'" clauses from:
	SetPasswordRequestType#psoId
	SetPasswordRequestType#password
	ExpirePasswordRequestType#psoId
	ResetPasswordRequestType#psoId
	ValidatePasswordRequestType#psoId
	ValidatePasswordRequestType#password

 62.	Change ValidateResponseType#valid from element to an attribute.  
      (An element is overkill for boolean.)

--Boundary_(ID_s2ExQszBXSqR9PcgP6pcwg)--


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