Re: [oslc-core] Groups - Ballot opened: "Resource shapes additional cons

Subject: Re: [oslc-core] Groups - Ballot opened: "Resource shapes additional constraint"

The wording "client and server implementations MUST behave as described in the defining OSLC specifications" seems very vague.

(I had a quick look through the recent minutes to see if I could find any discussion on this that would clarify the intention, but I couldn't see any.)

As someone who isn't already aware of the intention of the new paragraph, it isn't clear to me from the proposed wording what the intention is. The proposed paragraph seems to be focused on the SHOULD - allowing implementations to determine for themselves what they should do with resources that don't satisfy their shapes. But the description of the ballot suggests that it's the insertion of the MUST that was the intention.

Martin

----- Original message -----
From: <tc_admin@oasis-open.org>
Sent by: workgroup_mailer@lists.oasis-open.org
To: Martin P Pain/UK/IBM@IBMGB
Cc:
Subject: [oslc-core] Groups - Ballot opened: "Resource shapes additional constraint"
Date: Tue, Feb 9, 2016 9:01 PM

"Resource shapes additional constraint" has opened.

Ballot Title: Resource shapes additional constraint

Closing Date: Tuesday, 16 February 2016 @ 4:00 pm EST

Description
Rather than allowing resource shape constraints to be optional (SHOULD) in all circumstances, the following proposal will constrain implementations further when the resource satisfies the shape.

https://tools.oasis-open.org/version-control/svn/oslc-core/trunk/specs/resource-shape.html#associating-and-applying-shapes

The proposed change is to add the following paragraph at the end of the clause:

If a resource satisfies its applicable shapes, client and server implementations MUST behave as described in the defining OSLC specifications. If a resource does not satisfy its applicable shapes, implementations SHOULD attempt to complete the operation with the given data if possible. Otherwise implementations MAY reject the operation.
Group: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
Date Opened: Tuesday, 9 February 2016 @ 4:00 pm EST

oslc-core message