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: Re: [provision] draft 13 xsd issues.


Re #55 - #57 - no issue
Re #58 - I like referenceData as the name
Re #59 - #62 - no issue

Thanks Gary & Jeff.  You guys are awesome!

Gary P Cole wrote:

> Draft 13 of the XSD:
> - fixes issues #28, #47, #48, #49, #50, #53, #54.
> - partially addresses issues #16 and  #52.
> - raises new issues #55 through #62.
>
> An updated list of issues is attached.
>
>
>------------------------------------------------------------------------
>
>
>*16. Don't need CancelResultsType; ResultCode and ErrorCode should suffice.
>20041201 - email: "Issue 16, cancel results..."
>20041207 - Left OPEN.  Jeff Bohren wants to think about it, and his 
>   	     proposal to remove async from the core could also affect this.
>20040125 - Agreed in Editor's call.
>Draft 13 - Almost done. Async still defines CancelResultsType.
>
>
>--------------------------
>From Face-to-Face 20041206 
>--------------------------
>
> 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.)
>
>  
>
>------------------------------------------------------------------------
>
>To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/provision/members/leave_workgroup.php.
>  
>



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