RE: [provision] Draft 10 of the XSDs...

["Jeff Bohren" <jbohren@opennetwork.com>]

The request and response element had to be removed regardless of what
(if anything) is put in its place. There is no reason to leave in
element definitions that are known to be incorrect.

The noSuchRequest was removed from the core error code because in draft
9 the CancelResultsType was added which has a noSuchRequest enumeration.

Jeff Bohren
Product Architect
OpenNetwork Technologies, Inc
 
Try the industry's only 100% .NET-enabled identity management software.
Download your free copy of Universal IdP Standard Edition today. Go to
www.opennetwork.com/eval.
 
 

-----Original Message-----
From: Gary P Cole [mailto:Gary.P.Cole@Sun.COM] 
Sent: Tuesday, December 07, 2004 6:25 AM
To: provision@lists.oasis-open.org
Subject: Re: [provision] Draft 10 of the XSDs...

I don't recall there being concensus (nor even a request) to:
- remove noSuchRequest from ErrorCode
- remove the request element of the BatchRequestType (and use OCM)
- remove the response element of the StatusResponseType (and use OCM)

I'll update the issues list to reflect the fixes in Draft 10.

Jeff Bohren wrote:

> Draft 10 of the XSDs is attached. This contains the changes we 
> discussed at the F2F today. There is a readme text file that lists the

> changes.
>
> Also included is a first draft at a capability for an RA to query a 
> PSP for changes that happened as a result of another RA, or changes to

> the underlying resource. This is named the "updates" capability for 
> now (for want of a better term).
>
> Jeff Bohren
>
> Product Architect
>
> OpenNetwork Technologies, Inc
>



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_wor
kgroup.php.