Raw Minutes Chat for meeting #208 on 2018-04-30

["Mr. Stefan Hagen" <stefan@hagen.link>]

[18:00] Stefan Hagen: DSS-X Conference Call #208 (Conference Call)
[18:00] Stefan Hagen: Monday, 30 April 2018, 04:00pm to 05:00pm UTC
[18:00] Stefan Hagen: Agenda-Draft:
[18:00] Stefan Hagen: 1. Welcome by the chair (Stefan Hagen)

2. Minutes taker
All write into the chat, Stefan assembles and uploads into document area.

3. Roll call

4. Approval of the agenda

5. Approval of minutes from previous calls
5.1 Minutes from call #207 on 2018-04-16:
URL = https://www.oasis-open.org/committees/download.php/62893/chat_trace_dss_20180416_meeting-207_kavi.txt

6. Roadmap for 2018
6.1 Milestone DSS 2.0 Core/Base/MVP CSD01/CS01 stage
6.2 Milestone DSS 2.0 Popular Profiles CSD01 stage
6.3 Milestone DSS 2.0 other normative stages
6.4 Milestone DSS 2.0 supportive but supplementary non-normative materials

7. Core 2.0 issues discussion
7.1 Maintenance tasks

7.2 Topology of schemas - structure and relation

7.3 Editorial topics

7.4 Possible motion to progress core to CSD01 and request public review

8. Profiles

9. Next meeting
Suggested to meet again on 2018-MAY-14  (usual bi-weekly schedule)

10. AOB
[18:03] Stefan Hagen: 1. Welcome by the chair (Stefan Hagen)
[18:03] Stefan Hagen: 2. Minutes taker
All write into the chat, Stefan assembles and uploads into document area.

3. Roll call
[18:03] Stefan Hagen: Present all voting members: AK, DH, EJvN, SH
[18:03] Stefan Hagen: quorum reached
[18:03] Stefan Hagen: 4. Approval of the agenda
[18:03] Stefan Hagen: Agenda approved
[18:04] Stefan Hagen: 5. Approval of minutes from previous calls
5.1 Minutes from call #207 on 2018-04-16:
URL = https://www.oasis-open.org/committees/download.php/62893/chat_trace_dss_20180416_meeting-207_kavi.txt
[18:04] Stefan Hagen: Minutes approved
[18:04] Stefan Hagen: 6. Roadmap for 2018
6.1 Milestone DSS 2.0 Core/Base/MVP CSD01/CS01 stage
6.2 Milestone DSS 2.0 Popular Profiles CSD01 stage
6.3 Milestone DSS 2.0 other normative stages
6.4 Milestone DSS 2.0 supportive but supplementary non-normative materials
[18:04] Stefan Hagen: No discussion
[18:05] Stefan Hagen: 7. Core 2.0 issues discussion
7.1 Maintenance tasks
[18:05] Stefan Hagen: AK: Embedded discussion results from last meeting and is happy because no other comment came up
[18:05] Stefan Hagen: EJvN: Looks promising
[18:06] Stefan Hagen: AK: Will reflect EJvN remarks and offer a new revision by tomorrow to the earliest
[18:06] Stefan Hagen: 7.2 Topology of schemas - structure and relation
[18:07] Stefan Hagen: No discussion
[18:07] Stefan Hagen: 7.3 Editorial topics
[18:08] Stefan Hagen: None yet - Andreas will look into compliance with current OASIS rules and policies / guidelines for authoring of these artifacts
[18:08] Stefan Hagen: 7.4 Possible motion to progress core to CSD01 and request public review
[18:08] Stefan Hagen: Postponed
[18:11] Stefan Hagen: 8. Profiles
[18:11] Stefan Hagen: EJvN: Had detailed look into chip gateway proposal from Detlef and made comments - now hopes for feedback
[18:12] Stefan Hagen: EJvN: Chip gateway is quite complicated protocol (due to the use case it serves and current technology offerings)
[18:13] Stefan Hagen: DH: Looks forward offers time boxed processing
[18:13] Stefan Hagen: DH: Format still docbook
[18:13] Stefan Hagen: EJvN: Please let us first focus on essential content than tackle outer decsription format
[18:15] Stefan Hagen: All discuss
[18:16] Stefan Hagen: EJvN: If there are currently only JSON implementations then do we present also XML? ...
[18:16] Stefan Hagen: DH: Thinks that might no have many clients for implementation
[18:17] Stefan Hagen: EJvN: But we should offer consistency blueprints across technologies (XML and JSON)
[18:17] Stefan Hagen: EJvN: Maybe first JSON, then XML in next step
[18:18] Stefan Hagen: AK: Offers to help figuring out how XML would look like there
[18:18] Stefan Hagen: Stefan: Who if not us should be expected from market to specify an XML variant  ?
[18:20] Stefan Hagen: All agree on phase plan
[18:21] Stefan Hagen: DH: Will the Local Signature profile refer to old core (v1.0) or new core (v2.0)?
[18:21] Stefan Hagen: EJvN: Thinks this will for now technically not refer to v2.0
[18:22] Stefan Hagen: DH: Suggests to find out how to tackle things and for which formats, then fast change into the "new world" (i.e. v.2.0 of core)
[18:22] Stefan Hagen: EJvN: Thinks this is reasonable
[18:22] Stefan Hagen: AK: Will also take a look where he can help
[18:22] Stefan Hagen: All accept the suggestion
[18:22] Stefan Hagen: 9. Next meeting
Suggested to meet again on 2018-MAY-14  (usual bi-weekly schedule)
[18:23] Stefan Hagen: All agree
[18:23] Stefan Hagen: back to ADES
[18:24] Stefan Hagen: AK: Has no responses from DSS but has nags from ETSI/STF people to offer a version for the experts there to have a look
[18:24] Stefan Hagen: DH: Skimmed over it and saw many great points, and some minor points that might profit from discussion and changing before forwarding to ETSI
[18:25] Stefan Hagen: DH: 1) not refer to outdated ETSI specs but to current European norms
[18:25] Stefan Hagen: DH: Will happily provide the updated references :-?
[18:27] Stefan Hagen: DH: They are not easily mappable to the old ones, but he will offer also a mapping for Andreas to ease editorial work
[18:27] Stefan Hagen: DH: Signature Quality Level reference to a STORK EU Initiative FAQ (copied from a former editors draft and discussed with Juan Carlos before)
[18:27] Stefan Hagen: All discuss
[18:29] Stefan Hagen: DH: EIDAS world split in two parts: Normal, substantial and high 2) ES or Seal, ES or Seal advanced, Qualified ES or Seal, and others (e.g. focusing on the quality of the signing device etc.)
[18:30] Stefan Hagen: DH: Thinks this is not useful as parameter, because keys have some level of assurance or not, but it is not a runtime parameter that could change the behaviour of a service
[18:30] Stefan Hagen: All discuss
[18:34] Stefan Hagen: EJvN: There is use for parametrising this, but it is more about declaring intent
[18:35] Stefan Hagen: AK: One could use either a key selector or demand a minimum level of quality
[18:36] Stefan Hagen: AK: But this should not be an additional dimension of the key selector (the parameter discussed)
[18:36] Stefan Hagen: EJvN: Suggestiv to clarify the semantics as to what we want the client to be able to communicate (and not yet how)
[18:38] Stefan Hagen: DH: Suggests to look into binding closely to the European EIDAS notion
[18:38] Stefan Hagen: EJvN: Proposes to be open for the other Continents having different notions and to be adapted well to all of them
[18:40] Stefan Hagen: All: It is a question of priority and sequence. Suggested is first follow EIDAS to have a working and aligned profile, than at least try to provide means for others to align and map from whatever world standard is tried to map into DSS
[18:41] Stefan Hagen: AK: Next step is to look for some European quality levels identify the semantics and what? New component or Keyselector ... that would be a topic for core
[18:42] Stefan Hagen: DH: Happy with current progress in discussion
[18:43] Stefan Hagen: EJvN: Will need more time to provide feedback
[18:43] Stefan Hagen: All still are undecided if quality is attribute of key or a precondition for its selection in tutto
[18:46] Stefan Hagen: AK: Sugests to try including it in core as a new component with some explanatory text and all look into this and reflect their musings well if this solves it and the semantics are sufficiently clear
[18:47] Stefan Hagen: AK: Verification profile from ETSI workgroups inputs / feedback not available for now - so Andreas will continue to progress in isolation (that is TC only)
[18:48] Stefan Hagen: DH: Heard that there will be a new ETSI profile update at a meeting in June - so maybe we can ask him for stable parts?
[18:48] Stefan Hagen: AK: Tried this in the past, and does not want to wait for June
[18:48] Stefan Hagen: 10. AOB
[18:49] Stefan Hagen: None
[18:49] Stefan Hagen: Meeting adjourned