Ballot Details: Resource shapes additional constraint (CLOSED)

Ballot 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.

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.
Ballot Options
VOTING CLOSED: Tuesday, 16 February 2016 @ 4:00 pm EST
Yes 7 100
No 0 0
Abstain 0
Open Date Tuesday, 9 February 2016 @ 4:00 pm EST
Close Date Tuesday, 16 February 2016 @ 4:00 pm EST
Ballot Type Official, as defined by organization policies and procedures

Voting Statistics

Number of votes cast (excluding abstentions) 7
Eligible members who have voted 7 of 8 87.5%
Eligible members who have not voted 1 of 8 12.5%

Voting Summary by Option

Options with highest number of votes are bold
Option # Votes % of Total
Yes 7 100%
No 0 0%
Abstain 0

Voting Details

Voter Name Company Vote * Time (UTC) Comments
* Amsden, James IBM Yes 2016-02-10 13:53:00 1
* Crossley, Nick IBM Yes 2016-02-12 18:38:00
* El-khoury, Jad Swedish Royal Institute of Technology Yes 2016-02-15 12:38:00
* Honey, David IBM Yes 2016-02-10 17:17:00
* Johnson, Jean-Luc Airbus Group SAS Yes 2016-02-15 18:46:00
* Krishnaswamy, Harish Software AG, Inc. Yes 2016-02-15 01:37:00
* Sarabura, Martin PTC Yes 2016-02-16 16:55:00
* green, ian IBM --

Voter Comments

Submitter Vote Comment
Amsden, James
Yes This clarifies the meaning of applicable shapes and opens the opportunity to specify oslc:range in Core and Domain shapes for additional useful information without over-constraining servers.