[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [bdxr] Minutes of BDXR TC meeting March 2, 2016
Dear all
Today we had a meeting with representatives of DIGST and the eHealth community of e-SENS regarding the change requests received as comments to SMP 1.0 CS 2.0. Participants were:
Jens Aabol
Kenneth Bengtsson
Erlend Klakegg Bergheim
Joao Cunha
Adrien Férial
Sander Fieten
Masi Massimiliano
Sven Rasmussen
Hugo Soares
We briefly went through the TC's resolutions of change requests CR002, CR003, CR004, CR006 and CR008 (as documented in the meeting minutes below), before going in to details with change requests CR001, CR005 and CR007:
CR001: Add an additional "status" metadata
It was clarified that the additional "status" element would be used exclusively to exchange connectivity information, and tentatives values would be "in accordance", "expired", "suspended", "revoked", "not in accordance". It was discussed that there are alternative
methods to accomplish the same functionality as described in the change request. We concluded that the present BDXR TC members had received sufficient information to be able to resolve the change request at our next TC meeting.
CR005: Change end record names from "Document" to "Resource"
It was clarified that a descriptive text in the SMP specification would be sufficient documenting that a "Document" element can also be used for a "Resource". It was proposed that the BDXR TC drafts such a text to be added
to the specification and shares with eHealth for their comment. To be resolved at our next TC meeting.
CR007: Multiple signatures
We had a long conversation to clarify the underlying requirement of the change request. It was contemplated if the requirement is of a character specific to eHealth so that a "workaround" (for example using extensions) could
be proposed from BDXR, or if the requested change has a broad enough scope so as to justify a change to the SMP specification. One proposed solution was to suggest a solution using the extension elements and to document
this in an official document from the BDXR TC. We concluded that the present BDXR TC members had received sufficient information to be able to resolve the change request at our next TC
meeting.
Any other business
The BDXR TC will publish an official comment resolution log documenting the change requests and the actions taken. The timeframe for implementing changes is approximately early April, after which the BDXR TC has to decide if material changes have been made.
If no material changes (as defined by the OASIS TC Process:
https://www.oasis-open.org/policies-guidelines/tc-process#definitions) have been made, the TC can request that OASIS set up a ballot for the approval of a new Committee Specification (approximately one week), and after approval the new Committee Specification
will be published by OASIS (typically 4-5 weeks).
Best regards,
Kenneth
From: <bdxr@lists.oasis-open.org> on behalf of Kenneth Bengtsson <kbengtsson@efact.pe>
Date: Thursday, March 3, 2016 at 9:07 AM To: "bdxr@lists.oasis-open.org" <bdxr@lists.oasis-open.org> Subject: [bdxr] Minutes of BDXR TC meeting March 2, 2016 MEETING MINUTES OF BDXR TC MEETING 2 MARCH 2016
ATTENDANCE
SMP 1.0 COMMENTS RECEIVED
BDE 1.1 STATUS
UPDATE ON BDXL AND SMP STATEMENTS OF USE
ANY OTHER BUSINESS
MEETING SCHEDULE
Kenneth Bengtsson
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]