RE: [Bug 8182] New: unclear if/when result of a fragment Put is XSD validated

Based on the resolution to 8183 today [1], I suggest we use the fault wst:InvalidRepresentation to handle the case where the resource manager detects that the supplied partial representation in the WS-Fragment Put operation resulted in an invalid update. Perhaps, the WS-Fragment specification can include a statement about this.

Thanks.

[1] Resolution of 8183

If an implementation that performs schema validation on a presented representation detects that the presented representation is invalid for the target resource, then the implementation MUST generate a wst:InvalidRepresentation fault.

From: Gilbert Pilz [mailto:gilbert.pilz@oracle.com]
Sent: Tuesday, January 05, 2010 2:06 PM
To: Ram Jeyaraman
Cc: public-ws-resource-access@w3.org
Subject: Re: [Bug 8182] New: unclear if/when result of a fragment Put is XSD validated

It's not clear to me whether the statement in WS-Transfer to which you refer is sufficient to cover all the cases that might arise. The problem is that we are talking about fragments of representation. It could be that the supplied /wst:Put/wsf:Fragment/wsf:Value is, in the abstract, a perfectly valid value for the target fragment but, in the context of the particular resource in question, putting that value in would cause the resource to become invalid.

I'm OK with the idea of leaving a check for such conditions in the hands of the resource manager, but I think we may need to define a new fault.

- gp

On 1/2/2010 8:55 AM, Ram Jeyaraman wrote:

It seems the resource manager may decide to schema validate the updates based on a number of internal and external triggers. For example, it may do consistency checks based on isolation / validation policies in place. It seems best to leave the choice to the resource manager on whether to schema validate upates.



WS-Transfer says "implementations MAY use the fault code wst:InvalidRepresentation if the presented representation is invalid for the target resource". This allows the resource manager to throw a fault if it detects an update is schema invalid.



-----Original Message-----

From: public-ws-resource-access-notifications-request@w3.org<mailto:public-ws-resource-access-notifications-request@w3.org> [mailto:public-ws-resource-access-notifications-request@w3.org] On Behalf Of bugzilla@wiggum.w3.org<mailto:bugzilla@wiggum.w3.org>

Sent: Wednesday, November 04, 2009 10:32 AM

To: public-ws-resource-access-notifications@w3.org<mailto:public-ws-resource-access-notifications@w3.org>

Subject: [Bug 8182] New: unclear if/when result of a fragment Put is XSD validated



http://www.w3.org/Bugs/Public/show_bug.cgi?id=8182



           Summary: unclear if/when result of a fragment Put is XSD

                    validated

           Product: WS-Resource Access

           Version: PR

          Platform: All

        OS/Version: All

            Status: NEW

          Severity: normal

          Priority: P2

         Component: Fragment

        AssignedTo: public-ws-resource-access-notifications@w3.org<mailto:public-ws-resource-access-notifications@w3.org>

        ReportedBy: gilbert.pilz@oracle.com<mailto:gilbert.pilz@oracle.com>

         QAContact: public-ws-resource-access-notifications@w3.org<mailto:public-ws-resource-access-notifications@w3.org>





When performing a WS-Fragment Put it is possible for the resulting document to be invalid against the schema that defines that document. There are cases where you would like the resource manager to check this and fault. There are other cases where you might not.



Strawman Proposal: Add a boolean attribute to /wsrt:Put/Fragment that indicates whether schema validation of the resulting document should be performed as part of the Put operation. Define a new fault for when schema validation is requested and fails.





--

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email

------- You are receiving this mail because: ------- You are the QA contact for the bug.

You are the assignee for the bug.