1358 deprecate setDataSetValues
- Created
- 27 Feb 2015
- Status
- In Force (green)Closed: the solution is part of the standard. No further comments are taken. Show the workflow
- Part
- Part 8-1 (2011; Edition 2)
- Links
- #1356 deprecate setDataSetValues
- Page
- Clause
- 14.3.2
- Paragraph
- Category
- Issue for edition 2 of this part
Issue
setDataSetValues does not map a listOfAccessResult although 7-2 (13.3.3.4) requires:
This list shall indicate, for each data object, either a confirmation that the service SetDataSetValues to the referenced instance succeeded or a reason why the service SetDataSetValues to the referenced data object failed.
Proposal
Because of the issues with setDataSetValues in 7-2 (see TISSUE 1356) it is proposed to deprecate setDataSetValues.
| Discussion | Created |
|---|---|
| In Force (green) | 12 May 15 |
|
Ballot Period
Final Proposal:
deprecate the mapping SetDataSetValues in 8-1 Ed2.1. There will be no standardized mapping to SetDataSetValues in 8-1. Keep the service in 7-2 whenever other mappings request its definition. |
23 Mar 15 |
|
Discussion (red)
I agree with the proposal.
The current SetDataSetValue does not map the 7-2 service properly. |
02 Mar 15 |